Terminal and wireless communication method

Abstract

This terminal receives first downlink control information for an individual terminal and second downlink control information that is for data distribution and directed to a plurality of terminals. The terminal performs scheduling of a downlink data channel on the basis of an assumption that the size of the first downlink control information is adjusted to the size of the second downlink control information.

Description

Terminal and wireless communication method

[0001] The present disclosure relates to a terminal and a wireless communication method that support multicast / broadcast services.

[0002] The 3rd Generation Partnership Project (3GPP) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP Release 17 targets a service (provisional name: MBS: Multicast and Broadcast Services) that simultaneously transmits (also called distribution) data to multiple specified or unspecified terminals (User Equipment, UE) in NR (Non-Patent Document 1).

[0004] In MBS, it is assumed that scheduling will be supported using at least DCI format 1_0 (hereinafter referred to as DCI 1_0 as appropriate, and the same will be used for other DCI formats as appropriate) for the downlink data channel (PDSCH) among the existing downlink control information (DCI) formats.

[0005] Furthermore, in MBS, support for DCI 1_1 and DCI 1_2, which are also DCIs for PDSCH but have different sizes (number of bits), is also being considered.

[0006] "New Work Item on NR support of Multicast and Broadcast Services", RP-193248, 3GPP TSG RAN Meeting #86, 3GPP, December 2019

[0007] However, as the number of candidate DCIs in MBS increases, the number of blind detections performed when receiving DCIs also increases, which may result in performance degradation.

[0008] On the other hand, in the case of non-MBS DCI for individual UEs, it is desirable to ensure the flexibility to freely set the size.

[0009] Therefore, the following disclosure has been made in consideration of this situation, and aims to provide a terminal and a wireless communication method that can avoid performance degradation associated with an increase in the number of blind detections in a simultaneous data transmission service to multiple specific or unspecified terminals while ensuring flexibility in DCI size setting.

[0010] One aspect of the present disclosure is a terminal (UE200) that includes a receiving unit (control signal / reference signal processing unit 240) that receives first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals, and a control unit (control unit 270) that performs scheduling of a downlink data channel, assuming that the size of the first downlink control information is adjusted to the size of the second downlink control information.

[0011] One aspect of the present disclosure is a terminal (UE200) that includes a receiving unit (control signal / reference signal processing unit 240) that receives first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals, and a control unit (control unit 270) that performs scheduling of a downlink data channel, assuming that the size of the second downlink control information is adjusted to the size of the first downlink control information.

[0012] One aspect of the present disclosure is a terminal (UE200) that includes a receiving unit (control signal / reference signal processing unit 240) that receives first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals, and a control unit (control unit 270) that performs scheduling of a downlink data channel, assuming that the size of the first downlink control information and the size of the second downlink control information are the same.

[0013] One aspect of the present disclosure is a wireless communication method including the steps of receiving first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals, and performing scheduling of a downlink data channel, assuming that the size of the second downlink control information is adjusted to the size of the first downlink control information.

[0014] One aspect of the present disclosure is a wireless communication method including the steps of receiving first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals, and performing scheduling of a downlink data channel, assuming that the size of the second downlink control information is adjusted to the size of the first downlink control information.

[0015] One aspect of the present disclosure is a wireless communication method including the steps of receiving first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals, and performing scheduling of a downlink data channel, assuming that the size of the first downlink control information and the size of the second downlink control information are the same.

[0016] FIG. 1 is a diagram illustrating an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram illustrating an example configuration of a radio frame, a subframe, and a slot used in the wireless communication system 10. FIG. 3 is a diagram illustrating an example configuration of PTM transmission method 1 and PTM transmission method 2. FIG. 4 is a functional block configuration diagram of a gNB 100 and a UE 200. FIG. 5 is a diagram illustrating an example sequence of PDCCH, PDSCH, and HARQ feedback in MBS. FIG. 6 is a diagram illustrating an example of a correspondence relationship between an RNTI and a DCI format when MBS is supported. FIG. 7 is a diagram illustrating an example in which a common DCI size is applied between UEs associated with a G-RNTI when MBS is supported. FIG. 8 is a diagram illustrating an example of a correspondence relationship between an RNTI and a DCI format according to an operation example 1-1. FIG. 9 is a diagram illustrating an example of a correspondence relationship between an RNTI and a DCI format according to an operation example 1-2. FIG. 10 is a diagram illustrating an example of a correspondence relationship between an RNTI and a DCI format according to an operation example 2. FIG. 11 is a diagram illustrating an example of a hardware configuration of a gNB 100 and a UE 200.

[0017] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0018] (1) Overall Schematic Configuration of Wireless Communication System (1.1) System Configuration Example Fig. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a plurality of terminals 200 (User Equipment 200, hereinafter, UE 200).

[0019] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0020] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG. 1 .

[0021] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G core network (5GC, not shown). The NG-RAN 20 and the 5GC may also be simply referred to as a "network."

[0022] The gNB100 is a radio base station that complies with NR and performs NR-compliant radio communication with the UE 200. The gNB100 and UE 200 are capable of supporting Massive MIMO, which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and multiple NG-RAN nodes.

[0023] The wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR (Frequency Range) are as follows:

[0024] FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz to 52.6 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (including 240 kHz), and a bandwidth (BW) of 50 to 400 MHz.

[0025] Furthermore, the wireless communication system 10 may also support a frequency band higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support a frequency band exceeding 52.6 GHz up to 114.25 GHz. The wireless communication system 10 may also support a frequency band between FR1 and FR2.

[0026] Alternatively, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied, and DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).

[0027] FIG. 2 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10.

[0028] As shown in Figure 2, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the number of symbols constituting one slot does not necessarily have to be 14 (e.g., 28 or 56 symbols). The number of slots per subframe may also vary depending on the SCS. Furthermore, the SCS may be wider than 240 kHz (e.g., 480 kHz or 960 kHz, as shown in Figure 2).

[0029] The time direction (t) shown in Fig. 2 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a resource block group, a subcarrier, a BWP (Bandwidth part), a subchannel, a common frequency resource, etc.

[0030] (1.2) Providing MBS The wireless communication system 10 may provide multicast and broadcast services (MBS).

[0031] For example, in a stadium or a hall, it is assumed that a large number of UEs 200 are located within a certain geographical area and receive the same data simultaneously. In such a case, it is effective to use MBS instead of unicast.

[0032] Note that unicast may be interpreted as one-to-one communication with the network, in which a specific UE 200 is designated (identification information unique to the UE 200 may be designated).

[0033] Multicast may be interpreted as one-to-many (specified many) communication with a network, specifying a specific number of UEs 200 (identification information for multicast may be specified). Note that the number of UEs 200 receiving the received multicast data may ultimately be one.

[0034] Broadcasting may be interpreted as one-to-one communication between the network and all UEs 200. The multicast / broadcast data may be identical copies of the data, but some parts of the data, such as the header, may be different. The multicast / broadcast data may be simultaneously transmitted (distributed), but strict simultaneity is not necessarily required, and propagation delays and / or processing delays within the RAN node may be included.

[0035] The target UE 200 may be in a radio resource control (RRC) layer state of an idle state (RRC idle), a connected state (RRC connected), or another state (e.g., an inactive state). The inactive state may be interpreted as a state in which some RRC settings are maintained.

[0036] In MBS, the following three methods are assumed for scheduling multicast / broadcast PDSCH (Physical Downlink Shared Channel), specifically, scheduling MBS packets (which may be read as data). Note that RRC connected UE may also be read as RRC idle UE or RRC inactive UE.

[0037] PTM transmission method 1 (PTM-1): Schedules a group-common PDSCH for an MBS group of RRC connected UEs using a group-common PDCCH (Physical Downlink Control Channel).

[0038] The CRC (Cyclic Redundancy Checksum) of the PDCCH and the PDSCH are scrambled using a group-common RNTI (Radio Network Temporary Identifier).

[0039] PTM transmission method 2 (PTM-2): Schedules a group-common PDSCH for an MBS group of an RRC connected UE using a UE-specific PDCCH.

[0040] The CRC of the PDCCH is scrambled by the UE-specific RNTI.

[0041] - PDSCH is scrambled by the group-common RNTI.

[0042] PTP transmission method: For RRC connected UEs, UE-specific PDSCH is scheduled using UE-specific PDCCH.

[0043] The CRC of the PDCCH and the PDSCH are scrambled by a UE-specific RNTI, which may mean that the MBS packet is transmitted by unicast.

[0044] 3 shows configuration examples of PTM transmission method 1 and PTM transmission method 2. Note that the UE-specific PDCCH / PDSCH can be identified by the target UE, but does not need to be identified by other UEs in the same MBS group. The group-common PDCCH / PDSCH is transmitted in the same time / frequency resource and can be identified by all UEs in the same MBS group. Note that the names of PTM transmission methods 1 and 2 are tentative names, and they may be called by different names as long as the above-mentioned operations are performed.

[0045] Note that in point-to-point (PTP) delivery, the RAN node may deliver individual copies of the MBS data packet over the air to individual UEs, and in point-to-multipoint (PTM) delivery, the RAN node may deliver a single copy of the MBS data packet over the air to a set of UEs.

[0046] Furthermore, in order to improve the reliability of MBS, the following two feedback methods are envisaged for HARQ (Hybrid Automatic repeat request) feedback, specifically, HARQ feedback for multicast / broadcast PDSCH.

[0047] ・Option 1: Feedback both ACK / NACK (ACK / NACK feedback) ・UEs that successfully receive and decode PDSCH send ACK ・UEs that fail to receive and decode PDSCH send NACK ・PUCCH (Physical Uplink Control Channel) resource configuration: PUCCH-Config can be set for multicast ・PUCCH resources: Shared / orthogonal between UEs is determined by the network configuration ・HARQ-ACK CB (codebook): Supports type-1 and type-2 (CB decision algorithm (specified in 3GPP TS38.213)) ・Multiplexing: Unicast or multicast can be applied ・Option 2: Feedback only NACK (NACK-only feedback) ・UEs that successfully receive and decode PDSCH do not send ACK (do not send a response) ・UEs that fail to receive and decode PDSCH send NACK ・For a given UE, PUCCH resource configuration can be set separately by unicast or groupcast (multicast) Note that ACK is a positive A positive acknowledgement (NACK) may be referred to as a negative acknowledgement (NACK), and a HARQ may be referred to as an automatic repeat request (HARQ).

[0048] Enabling / Disabling of Option 1 or Option 2 may be applied in any of the following ways:

[0049] RRC and Downlink Control Information (DCI) RRC only Furthermore, the following is assumed for SPS (Semi-persistent Scheduling) of multicast / broadcast PDSCH.

[0050] - Uses SPS group-common PDSCH - Multiple SPS group-common PDSCHs can be configured as UE capability - HARQ feedback for SPS group-common PDSCH is possible - Activation / deactivation is possible using at least the group-common PDCCH Note that deactivation may be interpreted as other synonymous terms such as release. For example, activation may be interpreted as start, start, trigger, etc., and deactivation may further be interpreted as end, stop, etc.

[0051] SPS is a scheduling method used in contrast to dynamic scheduling, and may also be called semi-fixed, semi-persistent, or semi-persistent scheduling, and may be interpreted as Configured Scheduling (CS).

[0052] Scheduling may be interpreted as the process of allocating resources for transmitting data. Dynamic scheduling may be interpreted as a mechanism in which all PDSCHs are scheduled by DCI (e.g., DCI 1_0, DCI 1_1, or DCI 1_2). SPS may be interpreted as a mechanism in which PDSCH transmissions are scheduled by higher layer signaling, such as RRC messages.

[0053] Also, for the physical layer, there may be scheduling categories of time domain scheduling and frequency domain scheduling.

[0054] Furthermore, multicast, groupcast, broadcast, and MBS may be interchangeable. A multicast PDSCH (which may include a group-common PDSCH and an SPS group-common PDSCH), an MBS PDSCH, and a PDSCH scrambled with a group-common RNTI (which may be referred to as a G-RNTI) may be interchangeable.

[0055] Furthermore, the terms data and packet may be read interchangeably and may be interpreted as synonymous with terms such as signal, data unit, etc. Also, send, receive, transmit, and deliver may be read interchangeably.

[0056] (2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.

[0057] Fig. 4 is a functional block diagram of the gNB 100 and the UE 200. The following describes the UE 200. As shown in Fig. 4, the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0058] It should be noted that Fig. 4 shows only main functional blocks relevant to the description of the embodiment, and that the UE 200 has other functional blocks (e.g., a power supply unit, etc.). Fig. 4 also shows the functional block configuration of the UE 200 (gNB 100), and for the hardware configuration, please refer to Fig. 17.

[0059] The radio signal transmission / reception unit 210 transmits and receives radio signals conforming to NR. The radio signal transmission / reception unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0060] Furthermore, the radio signal transmitting and receiving unit 210 supports MBS and can receive a downlink channel that is common to a terminal group (group common) in data distribution to multiple UEs 200. In this embodiment, the radio signal transmitting and receiving unit 210 may constitute a receiving unit.

[0061] The radio signal transceiver 210 can receive a downlink data channel (PDSCH) common to a terminal group, specifically a group-common PDSCH (which may include an SPS group-common PDSCH). The radio signal transceiver 210 can also receive a downlink control channel common to a terminal group, specifically a group-common PDCCH.

[0062] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0063] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0064] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0065] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0066] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0067] DMRS is a terminal-specific reference signal (pilot signal) known between the base station and the terminal to estimate the fading channel used for data demodulation, while PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

[0068] In addition to DMRS and PTRS, the reference signals may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for position information.

[0069] The channels include a control channel and a data channel, and the control channel may include a PDCCH, a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel, Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.

[0070] Furthermore, the data channel includes a PDSCH, a PUSCH (Physical Uplink Shared Channel), etc. Data may refer to data transmitted via a data channel.

[0071] In this embodiment, the control signal and reference signal processor 240 may constitute a receiver that receives downlink control information (DCI). Specifically, the control signal and reference signal processor 240 can receive DCI for a downlink data channel. The downlink data channel may refer to a PDSCH, and (scheduling) DCI for the PDSCH may be, for example, DCI format 1_0 (DCI 1_0). Note that the DCI for the PDSCH may include DCI 1_1 and DCI 1_2. Furthermore, the DCI may include DCI format 2_x (for convenience, referred to as DCI 2_x) that notifies DCI to multiple UEs, such as a slot format.

[0072] DCI 1_0, 1_1, and 1_2 may all be DCIs for scheduling PDSCHs in one cell, but DCI 1_0 may be defined as the DCI with the smallest size among them. That is, DCI 1_0 may be defined as the DCI (downlink control information) with the smallest size for PDSCHs (downlink data channels). DCI 1_0 may also be a DCI format for scheduling PDSCHs when performing system information or random access. DCI 1_0 may also be a DCI format in which multiple UEs within a BWP / cell assume the same DCI size.

[0073] In addition, the control signal / reference signal processing unit 240 may receive DCI for an individual UE 200 (which may also be called first downlink control information) and DCI for data distribution to multiple UEs 200, i.e., MBS (which may also be called second downlink control information).

[0074] The DCI for individual UE 200 may refer to DCI CRC-scrambled by a UE-specific RNTI (e.g., C(Cell)-RNTI), and may correspond to the above-mentioned DCI 1_0, DCI 1_1, or DCI 1_2. Alternatively, the DCI may correspond to DCI 2_0, DCI 2_1, etc.

[0075] The DCI for MBS may refer to DCI CRC scrambled by a group common RNTI (G-RNTI), and may be DCI 1_0, DCI 1_1, or DCI 1_2 described above. In addition, the DCI for MBS may include other DCIs such as DCI 2_0.

[0076] The size of the DCI for each individual UE 200 may be changed for each UE, i.e., the DCI may have a variable length, whereas the DCI for the MBS may have a common size for multiple UEs (which may be interpreted as UEs in a group).

[0077] The DCI size adjustment may be performed, for example, as follows: If the sizes of DCI 0_0 and DCI 1_0 (UE specific search space: USS) and DCI 0_0 and 1_0 (Common search space: CSS) are different, DCI 0_0 / 1_0 (USS) may be adjusted to the size of DCI 0_0 / 1_0 (CSS). In CSS, the bit size of the Frequency Domain Resource Allocation (FDRA) is determined based on the frequency width / Physical RB (PRB) size of the initial BWP, and in USS, the bit size of the FDRA is determined based on the frequency width / PRB size of the configured BWP. Therefore, the DCI size may differ between CSS and USS.

[0078] The DCI sizes monitored using the C-RNTI include, for example, the following types:

[0079] ・0_0 / 1_0 (CSS / USS) ・0_1 / 1_1 ・0_2 / 1_2 Note that DCI 0_0 and DCI 0_1 may be specific to a cell, not to a UE. Also, DCI not related to the G-RNTI may be determined cell-specific.

[0080] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB 100 or another gNB).

[0081] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0082] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0083] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 executes control related to scheduling of downlink channels for MBSs and HARQ feedback of the channels.

[0084] The control unit 270 executes control corresponding to the scheduling of a downlink data channel that is common to a terminal group (group common) in the MBS, that is, data delivery to a plurality of UEs 200. Specifically, the control unit 270 can execute control corresponding to the scheduling of a group-common PDCCH and a group-common PDSCH.

[0085] In addition, the control unit 270 can perform scheduling of downlink channels, specifically downlink data channels such as PDSCH (which may include group-common PDSCH and SPS group-common PDSCH, the same applies below), based on the DCI received by the control signal / reference signal processing unit 240.

[0086] The DCI may be scrambled by the G-RNTI together with the CRC (DCI format with CRC scrambled by the G-RNTI). The G-RNTI is an RNTI associated with a terminal group and may be called by another name.

[0087] The control unit 270 may assume that the size of DCI (which may be a DCI format) associated with the G-RNTI is common among UEs associated with the same G-RNTI, while the control unit 270 may assume that the size of DCI not associated with the G-RNTI (for example, DCI CRC-scrambled with the C-RNTI) is set individually for each UE.

[0088] Specifically, the control unit 270 may perform scheduling of the downlink data channel (PDSCH) assuming that the size of the DCI (first downlink control information) for an individual UE 200 has been adjusted to the size of the DCI (second downlink control information) for the MBS.

[0089] More specifically, it may be assumed that padding bits for size adjustment are added to the DCI for individual UE 200 (CRC scrambled by UE specific RNTI). The DCI for individual UE 200 may be interpreted as a DCI format not related to the G-RNTI (e.g., DCI format x CRC scrambled with the C-RNTI). Here, DCI format x may mean one or more specific DCI format(s) (e.g., DCI format 1_0, etc.).

[0090] By adding the padding bits, the size of the DCI may be adjusted to be the same as (the same as) the DCI for MBS (CRC scrambled by group common RNTI). The DCI for MBS may be interpreted as a DCI format related to the G-RNTI (for example, DCI format x CRC scrambled with the G-RNTI).

[0091] The padding bits may be fixed (0, 1) to predetermined bits (predetermined bits), or may be a bit sequence (for example, a pseudorandom (PN) code) generated using a conversion formula or the like.

[0092] Alternatively, the control unit 270 may perform scheduling of the downlink data channel (PDSCH) assuming that the size of the DCI (second downlink control information) for the MBS is adjusted to the size of the DCI (first downlink control information) for an individual UE 200, in the opposite manner to the method described above.

[0093] In this case, it may be assumed that padding bits for size adjustment are added to the DCII (CRC scrambled by group common RNTI) for MBS.

[0094] Furthermore, the control unit 270 may perform scheduling of the downlink data channel (PDSCH) assuming that the size of the DCI (first downlink control information) for the individual UE 200 and the size of the DCI (second downlink control information) for the MBS are the same. Here, "the sizes of both DCIs are the same" may be interpreted as the size of the DCI for the MBS (DCI format x associated with the G-RNTI) and the size of the DCI for the individual UE 200 (for example, DCI format 2_x not associated with the G-RNTI) being the same (matching). That is, in this case, padding bits may not be used.

[0095] In this case, the DCI for MBS may be limited to DCI 1_1 or DCI 1_2. Also, in this case, DCI 1_0 for MBS may be assumed as the C-RNTI, and DCI 1_1 or DCI 1_2 for MBS may be assumed as another RNTI.

[0096] Furthermore, the control unit 270 may perform PDSCH scheduling based on antenna port information included in the DCI. The information on the antenna port information may be represented by one bit or two bits. The (number of) the antenna port may be interpreted as the (number of) the DMRS port.

[0097] The control unit 270 may determine whether or not the DCI includes antenna port information based on at least one of control information of a higher layer (e.g., RRC) and identification information used for scrambling the DCI, specifically, the RNTI. That is, whether or not the DCI includes a field for the antenna port may be determined based on the control information or the RNTI.

[0098] In this case, the DCI (for example, DCI 1_0) may be limited to MBS use, that is, to scheduling of multicast PDSCH. Thus, in this case, the PDSCH may be interpreted as a PDSCH for MBS (multicast PDSCH), and may be a PDSCH associated (scrambled) with an RNTI, such as a G-RNTI, that is assigned to multiple UEs.

[0099] The gNB 100 can also perform the above-described downlink channel scheduling and HARQ-related control. For example, the gNB 100 may include a transmitter (control signal / reference signal processor 240) that transmits downlink control information (DCI) for the downlink data channel. As described above, padding bits may be added to the DCI to adjust its size.

[0100] (3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of the scheduling of downlink channels related to MBS, specifically, the operation of scheduling MBS PDSCH more flexibly than DCI 1_0.

[0101] 5 shows an example of a sequence of PDCCH, PDSCH, and HARQ feedback in MBS. As shown in FIG. 5, PDCCH (which may include DCI) and PDSCH may be transmitted by unicast or multicast (broadcast). UE 200 may also transmit HARQ feedback (ACK / NACK) for the channel (transport block (TB) received via the channel).

[0102] Note that although it appears in Fig. 5 that both a unicast PDSCH and a multicast PDSCH are transmitted after one PDCCH / DCI, either a unicast PDSCH or a multicast PDSCH may be transmitted after one PDCCH / DCI. In other words, one PDCCH / DCI may schedule either a unicast PDSCH or a multicast PDSCH. In the above-mentioned PTM-1, DCI 1_0 may be supported. Specifically, in PTM-1, DCI 1_0 may be scrambled with CRC by G-RNTI (DCI 1_0 with CRC scrambled by G-RNTI).

[0103] The G-RNTI may be used for group-common PDCCH CRC scrambling and / or PDSCH data scrambling of the MBS. The G-RNTI may be configured by control information of a higher layer (e.g., RRC). Note that the G-RNTI may be an RNTI related to the group-common PDCCH and / or group-common PDSCH (which may include the SPS group-common PDSCH) (the same applies hereinafter).

[0104] 6 is a diagram showing an example of the correspondence relationship between RNTI and DCI format when MBS is supported. As described above, for the MBS PDSCH, at least DCI 1_0 may be used, and DCI 1_1 and DCI 1_2 may also be used.

[0105] On the other hand, increasing the size of candidate DCIs is undesirable because it increases the number of blind detections (BDs). Therefore, for a specific UE, it is desirable that the DCI sizes of DCI format x for scheduling unicast PDSCH and DCI format x for scheduling multicast PDSCH be equal.

[0106] However, for DCI format x that schedules Unicast PDSCH, the DCI size may differ for each UE. For example, for DCI 1_0, the FDRA field is variable depending on the BWP size (total DCI size is also variable). For DCI 1_1 or DCI 1_2, various fields are variable depending on the RRC settings (total DCI size is also variable).

[0107] On the other hand, the DCI (DCI format) (with CRC scrambled by group common RNTI (e.g., G-RNTI)) that schedules the multicast PDSCH must have the same DCI size among the UEs associated with the common G-RNTI, since multiple UEs receive (measure) the common DCI.

[0108] FIG. 7 shows an example in which a common DCI size is applied between UEs associated with a G-RNTI when MBS is supported.

[0109] In 3GPP Releases 15 and 16, the size of DCI not related to the G-RNTI (e.g., DCI CRC-scrambled with the C-RNTI) can be configured individually for each UE, but due to the above-mentioned constraints, the DCI size must be common (identical) among UEs related to the G-RNTI.

[0110] This means that supporting MBS imposes restrictions on the DCI format for scheduling unicast PDSCH, which is undesirable. In the example shown in Figure 7, the number of BDs for UE#1 increases.

[0111] Therefore, below, we will explain an example of operation in which the size of DCI not related to G-RNTI (e.g., DCI CRC-scrambled with C-RNTI) can be set individually for each UE, while DCI related to G-RNTI has a common (same) size among UEs related to the same G-RNTI.

[0112] (3.1) Operation Example 1 In this operation example, the size of DCI not related to G-RNTI (e.g., DCI CRC-scrambled with C-RNTI) can be configured individually for each UE (as in Releases 15 and 16), and padding bits configurable by a higher layer (e.g., RRC) are inserted after the DCI.

[0113] Target DCI formats may include 1_0, 1_1, 1_2, 2_0, 2_1, etc. Note that the CSS of DCI 0_0 / 0_1 may be cell-specific rather than UE-specific. Also, DCI not related to the G-RNTI may be determined cell-specific.

[0114] (3.1.1) Operation Example 1-1 Fig. 8 is a diagram showing an example of the correspondence relationship between RNTIs and DCI formats according to Operation Example 1-1. As shown in Fig. 8, padding bits (PAD) may be added to DCI format x that is not associated with a G-RNTI (for example, DCI format x that is CRC-scrambled with a C-RNTI). This makes the DCI size common to DCI format x that is associated with a G-RNTI (for example, DCI format x that is CRC-scrambled with a G-RNTI).

[0115] A predetermined bit (0, 1) may be inserted into the padding bit field, or a bit sequence (such as a PN code) generated using a conversion formula may be inserted into the field.

[0116] Furthermore, the number of padding bits may be explicitly set by a higher layer (RRC), or may be implicitly set without being explicitly set.

[0117] If not explicitly configured, UE200 may determine the size of padding bits so that the total DCI size of each DCI field configured in DCI format x associated with the G-RNTI (e.g., DCI format x CRC-scrambled with the G-RNTI) is equal to the total DCI size obtained by adding padding bits to DCI format x not associated with the G-RNTI (e.g., DCI format x CRC-scrambled with the C-RNTI).

[0118] Furthermore, the insertion position of padding bits is usually after the DCI (later in the time direction), but may be before the DCI or in the middle of the DCI. Padding bits may also be called additional bits, surplus bits, additional bits, etc. Padding bits may not be used for information transfer, or may be used for some kind of information transfer.

[0119] (3.1.2) Operation Example 1-2 Fig. 9 is a diagram showing an example of the correspondence relationship between RNTIs and DCI formats according to Operation Example 1-2. Operation example 1-1 shows an example in which the size of DCI format x not associated with a G-RNTI is smaller than the size of DCI format x associated with a G-RNTI, but this is not limiting. As shown in Fig. 9, UE 200 may assume that padding bits are added in the same way even in the reverse case.

[0120] The size of DCI not associated with the G-RNTI (e.g., DCI CRC-scrambled with the C-RNTI) is configurable by the UE (similar to Releases 15 and 16), and padding bits configurable by higher layers (e.g., RRC) may be inserted after the DCI format x associated with the G-RNTI.

[0121] Specifically, as shown in FIG. 9, padding bits may be added to DCI format x associated with the G-RNTI (e.g., DCI format x CRC-scrambled with the G-RNTI), making it possible to make the DCI size common to DCI format x not associated with the G-RNTI (e.g., DCI format x CRC-scrambled with the C-RNTI).

[0122] As in Operation Example 1-1, predetermined bits (0, 1) may be inserted into the padding bit field. Alternatively, a bit sequence (such as a PN code) generated using a conversion formula or the like may be inserted into the field.

[0123] Furthermore, the number of padding bits may be explicitly set by a higher layer (RRC), or may be implicitly set without being explicitly set.

[0124] If not explicitly configured, the size of the padding bits may be determined so that the total DCI size of each DCI field configured for DCI format x not related to the G-RNTI (e.g., DCI format x CRC-scrambled with the C-RNTI) is equal to the total DCI size obtained by adding padding bits to DCI format x related to the G-RNTI (e.g., DCI format x CRC-scrambled with the G-RNTI).

[0125] Note that if the format size of the G-RNTI is larger than the format size of the C-RNTI (or vice versa), it may be treated as an error case (UE 200 does not need to consider such a case). This makes it possible to have no particular effect on the existing C-RNTI format.

[0126] Also, as described above, the padding bits may not specifically indicate information, and the UE 200 does not need to measure the padding bit field and perform control using the DCI indicated by the padding bit field.

[0127] Although operational examples 1-1 and 1-2 show examples in which a padding bit field is provided only in either DCI format x not associated with a G-RNTI or DCI format x associated with a G-RNTI, the padding bit field may be provided after both DCIs. In other words, the padding bit field may be inserted into both DCI format x not associated with a G-RNTI and DCI format x associated with a G-RNTI.

[0128] In this case, the size of DCI format 1_2 not associated with the G-RNTI may be made variable for each UE, while the size of DCI format 1_2 associated with the G-RNTI may be made uniform between UEs, and within a specific UE, the size of DCI format 1_2 associated with the G-RNTI and the size of DCI format 1_2 not associated with the G-RNTI may be made uniform.

[0129] In this case, the higher layer (RRC) may notify the UE 200 of the number of padding bits for each of the DCI format x not associated with the G-RNTI and the DCI format x associated with the G-RNTI. Alternatively, the number of padding bits for only one of the DCI formats may be notified, and the other may be adjusted to match the notified number of padding bits. Furthermore, not only the number of padding bits but also the total DCI size may be notified.

[0130] (3.2) Operation Example 2 In this operation example, UE 200 may assume that the size of DCI format x associated with the G-RNTI is the same as the size of DCI format 2_x (group common PDCCH) that is not associated with the G-RNTI. In other words, padding bits do not need to be inserted, as in operation example 1.

[0131] Fig. 10 is a diagram illustrating an example of the correspondence relationship between RNTIs and DCI formats according to operation example 2. As illustrated in Fig. 10, UE 200 may assume that the size of DCI format 1_2 associated with a G-RNTI is the same as the size of DCI format 2_0 not associated with a G-RNTI.

[0132] Note that the DCI size may be made the same as that of DCI 2_x only for DCI 1_1 / 1_2 CRC-scrambled by the G-RNTI. DCI 1_0 CRC-scrambled by the G-RNTI may have the same size as the existing DCI 1_0 (C-RNTI, CSS).

[0133] That is, DCI 1_0 for MBS may be counted as a C-RNTI, and DCI 1_1 / 1_2 for MBS may be counted as other RNTIs such as a G-RNTI.

[0134] The size of DCI format 2_x (for example, DCI format 2_0: maximum 128 bits, DCI format 2_1: maximum 126 bits) may be determined by a parameter of a higher layer (RRC), or may be the same size as DCI 1_0.

[0135] Because DCI format 2_x (group common PDCCH) is common among multiple UEs (however, not necessarily common among UEs associated with the same G-RNTI), it is easy to make DCI format x associated with a G-RNTI common among UEs. Note that, because this DCI format is not necessarily common among UEs associated with the same G-RNTI, in addition to this operation example, padding bits as shown in operation example 1 may be added to at least one of DCI format x associated with the G-RNTI or DCI format 2_x (group common PDCCH) not associated with a G-RNTI.

[0136] (3.3) Modifications In the above-described operation examples 1 and 2, as described above, only DCI 1_1 / 1_2 that has been CRC-scrambled by the G-RNTI may be targeted, and the DCI size may be made the same as that of DCI 2_x.

[0137] DCI 1_0 CRC-scrambled by G-RNTI may have the same size as the existing DCI 1_0 (C-RNTI, CSS). The size of the existing DCI 1_0 (C-RNTI, CSS) may be a common size among multiple UEs (UEs within a cell).

[0138] Furthermore, the operations of operation examples 1 and 2 may be switched (used appropriately) depending on the DCI format for MBS (multicast). For example, if the DCI format for MBS is DCI 1_0, operation example 2 may be applied, and if the DCI format for MBS is DCI 1_1 / 1_2, operation example 1 may be applied.

[0139] Alternatively, the operations of Operation Examples 1 and 2 may be applied simultaneously to a DCI format for MBS, or only one of them may be applied. Furthermore, when both are applied simultaneously to a common DCI format, which operation to apply may be specified by the 3GPP specifications or may be set by the network on a case-by-case basis.

[0140] (4) Actions and Effects According to the above-described embodiment, the following actions and effects can be obtained: Specifically, the UE 200 may perform scheduling of the downlink data channel (PDSCH) assuming that the size of the DCI (first downlink control information) for the individual UE 200 is adjusted to the size of the DCI (second downlink control information) for the MBS.

[0141] Alternatively, UE200 may perform scheduling of the downlink data channel (PDSCH) assuming that the size of the DCI (second downlink control information) for MBS has been adjusted to the size of the DCI (first downlink control information) for individual UE200.

[0142] Furthermore, the UE 200 may perform scheduling of the downlink data channel, assuming that the size of the first downlink control information and the size of the second downlink control information are the same.

[0143] Therefore, even if the number of candidate DCIs in MBS increases, the number of blind detections when receiving DCI can be reduced, and degradation of performance can be avoided.

[0144] (5) Other Embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments, and that various modifications and improvements are possible.

[0145] In the above-described embodiment, DCI format 1_0 / 1_1 / 1_2 that is CRC scrambled by the G-RNTI has been described as an example, but the DCI format may be called by a different name.

[0146] For example, DCI format 1_0 CRC-scrambled by the G-RNTI may be expressed as "a format with a small payload size among one or more DCI formats scrambled by the G-RNTI" or "a format that does not include a specific field among formats scrambled by the G-RNTI", etc. Furthermore, DCI format 1_1 / 1_2 CRC-scrambled by the G-RNTI may be expressed as "a format with a large payload size among one or more DCI formats scrambled by the G-RNTI" or "a format that includes a specific field among formats scrambled by the G-RNTI", etc.

[0147] In addition, in the above-described embodiment, the MBS PDSCH has been described as an example, but at least one of the above-described operation examples may be applied to other downlink channels such as the MBS PDCCH. Furthermore, the above-described operation examples may be combined and applied in a composite manner as long as no contradiction occurs.

[0148] In the above description, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0149] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0150] The block diagram ( FIG. 4 ) used to explain the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0151] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0152] Furthermore, the gNB 100 and the UE 200 described above may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 11 is a diagram showing an example of the hardware configuration of the device. As shown in Fig. 11, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0153] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0154] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0155] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0156] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0157] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0158] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0159] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0160] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0161] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0162] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0163] Furthermore, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0164] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0165] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0166] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.

[0167] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0168] In the present disclosure, a specific operation described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., MME and S-GW) may also be used.

[0169] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input and output via multiple network nodes.

[0170] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be transmitted to another device.

[0171] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0172] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0173] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0174] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0175] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0176] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0177] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0178] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0179] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0180] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0181] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0182] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0183] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0184] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0185] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0186] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel (or sidelink).

[0187] Similarly, a mobile station in the present disclosure may be interpreted as a base station. In this case, the base station may be configured to have the functions of a mobile station. A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0188] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0189] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol, a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.) A slot may be a numerology-based time unit.

[0190] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0191] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0192] For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0193] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

[0194] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0195] In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling, and the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0196] A TTI having a time length of 1 ms may be referred to as a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be referred to as a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0197] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0198] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0199] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI, each of which may consist of one or more resource blocks.

[0200] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0201] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0202] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0203] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0204] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0205] The above-described structures of the radio frame, subframe, slot, minislot, and symbol are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations may be changed in various ways.

[0206] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0207] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.

[0208] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0209] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0210] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0211] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0212] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0213] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0214] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0215] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0216] 10 Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitting / receiving unit 220 Amplifier unit 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transmitting / receiving unit 270 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus

Claims

1. A terminal comprising: a receiving unit that receives first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals; and a control unit that performs scheduling of a downlink data channel, assuming that the size of the first downlink control information is adjusted to the size of the second downlink control information.

2. A terminal comprising: a receiving unit that receives first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals; and a control unit that performs scheduling of a downlink data channel, assuming that the size of the second downlink control information is adjusted to the size of the first downlink control information.

3. A terminal comprising: a receiving unit that receives first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals; and a control unit that performs scheduling of downlink data channels, assuming that the size of the first downlink control information and the size of the second downlink control information are the same.

4. A wireless communication method comprising: a step of receiving first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals; and a step of performing scheduling of a downlink data channel, assuming that the size of the second downlink control information is adjusted to the size of the first downlink control information.

5. A wireless communication method comprising: receiving first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals; and performing scheduling of a downlink data channel, assuming that the size of the second downlink control information is adjusted to the size of the first downlink control information.

6. A wireless communication method comprising: a step of receiving first downlink control information for an individual terminal and second downlink control information for data distribution to multiple terminals; and a step of scheduling a downlink data channel, assuming that the size of the first downlink control information and the size of the second downlink control information are the same.

Images