Terminal and wireless communication method

Abstract

This terminal receives downlink control information. When the downlink control information is in a specific format in data distribution for a plurality of terminals, resource blocks of a downlink data channel are assumed on the basis of a lowest resource block for data distribution.

Description

[Technical Field]

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

[0002] The 3rd Generation Partnership Project (3GPP) has developed 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 simultaneous data transmission (also called distribution) services (provisional name: MBS: Multicast and Broadcast Services) in NR to multiple specified or unspecified terminals (User Equipment, UE) (Non-Patent Document 1).

[0004] In MBS, it has been agreed that DCI format 1_0 and DCI format 1_1 will be used as formats for downlink control information (DCI) (Non-Patent Document 2).

[0005] It has also been agreed that in MBS, multiple UEs to which the same identification information (group-common RNTI (Radio Network Temporary Identifier, which may also be called G-RNTI) is set) will use a downlink data channel for MBS (Physical Downlink Shared Channel, which may also be called Multicast PDSCH) using a common frequency resource (CFR) (Non-Patent Document 3). [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] "New Work Item on NR support of Multicast and Broadcast Services", RP-193248, 3GPP TSG RAN Meeting #86, 3GPP, December 2019 [Non-patent document 2] "Final Report of 3GPP TSG RAN WG1 #104-e v1.0.0", R1-2102281, 3GPP TSG RAN WG1 Meeting #104bis-e, 3GPP, April 2021 [Non-patent document 3] "Final Report of 3GPP TSG RAN WG1 #104bis-e v1.0.0", R1-2104151, 3GPP TSG RAN WG1 Meeting #105-e, 3GPP, May 2021 Summary of the Invention

[0007] In DCI format 1_0, the resource block (RB) numbering of the PDSCH scheduled in the Common Search Space (CSS) is based on the lowest RB of the control resource set (CORESET) in which the DCI is received (see 3GPP TS38.214, Chapter 5.1.2.2).

[0008] Here, if the band (RB) of the CFR is wider than the band (RB) of the CORESET, it may not be possible to display all the CFRs, and some CFRs (RBs) may not be able to be allocated.

[0009] Therefore, the following disclosure has been made in consideration of such circumstances, and aims to provide a terminal and a wireless communication method that can more reliably schedule Multicast PDSCH even when a specific DCI such as DCI format 1_0 is used.

[0010] One aspect of the present disclosure is a terminal (UE200) including a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information, and a control unit (control unit 270) that, when distributing data to multiple terminals, assumes resource blocks of a downlink data channel based on the lowest resource block for the data distribution when the downlink control information is in a specific format.

[0011] One aspect of the present disclosure is a terminal (UE200) including a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information, and a control unit (control unit 270) that assumes that, in data distribution to multiple terminals, when the downlink control information is in a specific format, the lowest resource block of a control resource set is equal to or lower than the lowest resource block for the data distribution.

[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 downlink control information, and a control unit (control unit 270) that, when the downlink control information is in a specific format in data distribution to multiple terminals, assumes a resource block of a downlink data channel based on the lowest resource block of a control resource set, and that assumes that at least the lowest resource block of the control resource set is indicated by a negative value.

[0013] One aspect of the present disclosure is a terminal (UE) that includes a receiving unit (control signal / reference signal processing unit 240) that receives downlink control information, and a control unit (control unit 270) that, when the downlink control information is in a specific format for data distribution to multiple terminals, assumes resource blocks of a downlink data channel based on the lowest resource block of a control resource set, and the control unit assumes display of resource blocks based on the control resource set within the range of frequency resources for the data distribution or a specified bandwidth portion.

[0014] One aspect of the present disclosure is a wireless communication method including: receiving downlink control information; and, in data distribution to multiple terminals, if the downlink control information is in a specific format, estimating resource blocks of a downlink data channel based on the lowest resource block for the data distribution.

[0015] One aspect of the present disclosure is a wireless communication method including: receiving downlink control information; and, in data distribution to multiple terminals, assuming that, if the downlink control information is in a specific format, the lowest resource block of a control resource set is equal to or less than the lowest resource block for the data distribution. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing an example of the configuration of PTM transmission method 1 and PTM transmission method 2. In FIG. [Figure 4] Figure 4 is a functional block diagram of gNB100 and UE200. [Figure 5] FIG. 5 is a diagram showing an example of a sequence of PDCCH, PDSCH and HARQ feedback in MBS. [Figure 6] FIG. 6 is a diagram showing an example of the relationship between CORESET resource blocks and CFR resource blocks when DCI format 1_0 is used. [Figure 7] FIG. 7 is a diagram showing an example (part 1) of the relationship between resource blocks of CORESET and resource blocks of CFR according to the first operation example. [Figure 8] FIG. 8 is a diagram showing a second example of the relationship between resource blocks of CORESET and resource blocks of CFR according to the first operation example. [Figure 9] FIG. 9 is a diagram illustrating a third example of the relationship between resource blocks of CORESET and resource blocks of CFR according to the first operation example. [Figure 10] FIG. 10 is a diagram illustrating an example of the relationship between resource blocks of CORESET and resource blocks of CFR according to the second operation example. [Figure 11] FIG. 11 is a diagram illustrating an example of the relationship between resource blocks of CORESET and resource blocks of CFR according to the third operation example. [Figure 12] FIG. 12 is a diagram illustrating an example (part 1) of the relationship between resource blocks of CORESET and resource blocks of CFR according to the fourth operation example. [Figure 13] FIG. 13 is a diagram illustrating a second example of the relationship between resource blocks of CORESET and resource blocks of CFR according to the fourth operation example. [Figure 14] FIG. 14 is a diagram showing an example of the hardware configuration of gNB100 and UE200. DETAILED DESCRIPTION OF THE INVENTION

[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 configuration of the wireless communication system (1.1) System configuration example 1 is a schematic diagram of the overall configuration 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.

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

[0022] The gNB 100 is a radio base station that complies with NR and performs NR-compliant radio communication with the UE 200. The gNB 100 and the 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 and uses 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~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. FR2 may also include FR2-1 (24.25 to 52.6 GHz) and FR2-2 (52.6 to 71 GHz).

[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. Furthermore, 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 a radio frame, a subframe, and a slot used in the radio communication system 10. In FIG.

[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 symbols (e.g., 28 or 56 symbols). The number of slots per subframe may differ 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] 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 bandwidth part (BWP), a subchannel, a common frequency resource, etc.

[0030] (1.2) Provision of 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, specifying one specific UE 200 (identification information unique to the UE 200 may be specified).

[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 transmitted (distributed) simultaneously, 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, which may also be called MBS PDSCH or Multicast PDSCH), specifically, for scheduling MBS packets (which may also 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): · For the MBS group of RRC connected UEs, the group-common PDSCH is scheduled using the group-common PDCCH (Physical Downlink Control Channel).

[0038] The CRC of the PDCCH and the PDSCH are scrambled by a group-common RNTI (which may also be called a Radio Network Temporary Identifier, G-RNTI).

[0039] ·PTM transmission method 2 (PTM-2): · For the MBS group of RRC connected UE, the group-common PDSCH is scheduled using the UE-specific PDCCH.

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

[0041] The PDSCH is scrambled using 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] Figure 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. The names of PTM transmission methods 1 and 2 are tentative, 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 and NACK (ACK / NACK feedback) UE that successfully receives and decodes PDSCH sends ACK · UEs that fail to receive and decode PDSCH send NACK PUCCH (Physical Uplink Control Channel) resource configuration: PUCCH-Config can be configured for multicast. PUCCH resources: shared / orthogonal between UEs, depending on 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: NACK-only feedback · UE that successfully receives and decodes PDSCH does not send ACK (does not send a response) · UEs that fail to receive and decode PDSCH send NACK For a given UE, PUCCH resource configuration can be configured separately via unicast or groupcast (multicast) Note that ACK may be called a positive acknowledgement, and NACK may be called a negative acknowledgement. HARQ may be called an automatic repeat request.

[0048] To enable or disable option 1 or option 2, one of the following may be applied:

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

[0050] -SPS group-common PDSCH (also called group common SPS PDSCH) is used Multiple SPS group-common PDSCHs can be configured as UE capabilities. HARQ feedback for SPS group-common PDSCH is possible Activation / deactivation is possible via at least the group-common PDCCH (downlink control channel) Note that deactivation may be interpreted as another synonymous term such as release. For example, activation may be interpreted as start, start, trigger, etc., and deactivation may 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 also be interpreted as Configured Scheduling (CS).

[0052] Scheduling may be interpreted as a 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 format 1_0, DCI format 1_1). SPS may be interpreted as a mechanism in which PDSCH transmissions are scheduled by higher layer signaling such as RRC messages.

[0053] Furthermore, in MBS, it may be assumed that a plurality of UEs configured with the same identification information (G-RNTI) use an MBS PDSCH using a common frequency resource (CFR).

[0054] Note that multicast SPS PDSCH reception may refer to group common SPS PDSCH reception, may be an SPS PDSCH received by multiple terminals, or may be SPS PDSCH reception associated with a G-RNTI or G-CS-RNTI (i.e., an RNTI associated with multiple terminals). Also, multicast may be read as broadcast.

[0055] For the physical layer, there may be scheduling categories of time domain scheduling and frequency domain scheduling.

[0056] Furthermore, multicast, groupcast, broadcast, and MBS may be interchangeable. Multicast PDSCH and PDSCH scrambled with a group-common RNTI may be interchangeable.

[0057] 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.

[0058] (2) Functional block configuration of wireless communication system Next, a description will be given of the functional block configuration of the wireless communication system 10. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.

[0059] 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.

[0060] It should be noted that Fig. 4 shows only the 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. 14.

[0061] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving 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.

[0062] The radio signal transmitting / 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.

[0063] Furthermore, the radio signal transmitting and receiving unit 210 can receive a downlink data channel (PDSCH) in MBS, that is, data distribution to multiple terminals.

[0064] Specifically, the radio signal transmitting and receiving unit 210 can receive a group-common PDSCH (which may include an SPS group-common PDSCH), which is a downlink data channel (PDSCH) common to a terminal group.

[0065] Furthermore, the radio signal transmitting and receiving unit 210 can receive a downlink control channel common to a terminal group, specifically a group-common PDCCH, and can receive a downlink control channel specific to a terminal, specifically a UE-specific PDCCH.

[0066] 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.

[0067] 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 uplink (UL) but also for downlink (DL).

[0068] The control signal / reference signal processor 240 performs 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 .

[0069] Specifically, the control signal / reference signal processor 240 receives various control signals, such as control signals (messages) of the radio resource control layer (RRC), transmitted from the gNB 100 via a predetermined control channel. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

[0070] 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).

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

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

[0073] The channels include a control channel and a data channel. The control channels 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.

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

[0075] In this embodiment, the control signal and reference signal processor 240 may constitute a receiver that receives downlink control information (DCI). DCI may be in any format defined in 3GPP TS38.212, but in this embodiment, the control signal and reference signal processor 240 may particularly receive DCI in accordance with DCI format 1_0 and DCI format 1_1. In MBS, DCI format 1_0 or DCI format 1_1 may be used.

[0076] DCI format 1_0 may be used for scheduling PDSCHs within a cell. DCI format 1_1 may also be used for scheduling PDSCHs within a cell. DCI format 1_0 may have fewer bits than DCI format 1_1 (and other DCI formats). The DCI format may include frequency domain resource allocation (FDRA), time domain resource allocation (TDRA), virtual resource block (VRB) to physical resource block (PRB) mapping (VRB-PRB mapping), modulation and coding scheme, etc.

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

[0078] 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.

[0079] 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 (HARQ). Specifically, the data transmitter / receiver 260 can transmit HARQ (Automatic Repeat Request) feedback.

[0080] 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.

[0081] The control unit 270 executes control corresponding to the scheduling of a downlink 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.

[0082] When DCI is in a specific format in an MBS, the control unit 270 may assume the resource blocks (RBs) of the downlink data channel based on the lowest resource block for the MBS. For example, when DCI format 1_0 is used in an MBS, the control unit 270 may assume that the RB numbering of a PDSCH (MBS PDSCH) scheduled using DCI format 1_0 in a common search space (CSS) is based on the lowest RB of the CFR. Note that the DCI format is not necessarily limited to DCI format 1_0, and may be DCI format 1_1 or the like (the same applies below).

[0083] RB numbering may refer to directly or indirectly indicating the RB number (or RB index) to which the PDSCH is allocated. The RB number may be indicated by any number such as 0 to x, and may substantially correspond to a subcarrier, etc.

[0084] The downlink (DL) radio resources used for transmitting the PDCCH can be specified by a control resource set (CORESET), which may be interpreted as a set of physical resources (specifically, a specific region on the DL resource grid) and parameters used to transmit the PDCCH (including the DCI).

[0085] The UE 200 can assume the particular region to which the CORESET is assigned based on the timing and periodicity specified by the CSS.

[0086] When DCI is in a specific format in an MBS, the control unit 270 may assume that the lowest resource block of CORESET is equal to or less than the lowest resource block for data delivery. For example, when DCI format 1_0 is used in an MBS and scheduling is performed using DCI format 1_0 in a CSS, the control unit 270 may assume that the lowest RB of CORESET is equal to or less than the lowest RB of CFR.

[0087] More specifically, when scheduling is performed using DCI format 1_0 in the CSS, the control unit 270 may assume that CORESET lowest RB≦CFRlowest RB, i.e., the number of the CORESET lowest RB is always equal to or less than the CFRlowest RB.

[0088] Alternatively, when DCI in an MBS has a specific format (for example, DCI format 1_0), the control unit 270 may determine the RBs of the MBS PDSCH based on the lowest resource block of the CORESET (CORESET lowest RB). Such an operation is similar to the specifications of 3GPP TS38.214 such as Release-16. However, in this case, the control unit 270 may determine that at least the lowest resource block of the CORESET (CORESETlowest RB) is indicated by a negative value. In other words, some RB numbers on the low frequency side of the CORESET may be indicated by negative values.

[0089] Furthermore, when DCI is in a specific format (for example, DCI format 1_0) in an MBS, control unit 270 may assume RBs for the MBS PDSCH based on the lowest resource block of CORESET (CORESET lowest RB), but may also assume display of resource blocks based on CORESET within the range of the frequency resource for MBS (CFR) or the specified bandwidth portion (BWP). Note that the bandwidth (number of RBs) of the BWP may be wider than the bandwidth (number of RBs) of the CFR.

[0090] Specifically, the control unit 270 identifies the RB number based on the CORESET lowest RB, and when it reaches one end of the CFR in the frequency direction (which may be the high frequency side or the low frequency side), it moves to the opposite end of the CFR, and the RB numbers may become continuous (this may be called a mod operation).

[0091] Alternatively, the control unit 270 may identify the RB number based on the CORESETlowest RB, and when it reaches one end of the BWP in the frequency direction (which may be the high frequency side or the low frequency side), it may move to the opposite end of the BWP, making the RB numbers continuous (this may be called a mod operation).

[0092] A specific example of such a mod operation will be described later.

[0093] (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 operation relating to scheduling of a downlink channel for MBS and HARQ feedback of that channel.

[0094] (3.1) Prerequisites and Issues 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).

[0095] 5, it appears that both a unicast PDSCH and a multicast PDSCH are transmitted after one PDCCH / DCI, but 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.

[0096] In 3GPP, the same RNTI (for example, G-RNTI) may be configured for multiple UEs that are targets of MBS, and each UE may blindly decode DCI based on the G-RNTI. As described above, it has been agreed that at least DCI format 1_0 or DCI format 1_1 will be used in MBS. Note that the DCI for MBS may include DCI format 1_2, which is DCI for PDSCH, instead of DCI format 1_0 or DCI format 1_1. Furthermore, DCI format 1_0 may be the DCI with the smallest size among the DCIs.

[0097] As described above, in MBS, multiple UEs configured with the same identification information (G-RNTI) may assume a common frequency resource (CFR), and the resources of the MBS PDSCH (Multicast PDSCH) may be indicated and controlled using the CFR.

[0098] FIG. 6 shows an example of the relationship between CORESET resource blocks and CFR resource blocks when DCI format 1_0 is used.

[0099] When UE 200 receives a scheduling grant in DCI format 1_0, UE 200 may use downlink resource allocation type 1 (see 3GPP TS38.214, Chapter 5.1.2.2).

[0100] For a PDSCH scheduled by DCI format 1_0 in any type of PDCCH common search space (CSS), the RB numbering may start from the lowest RB of the CORESET in which the DCI is received, regardless of whether any BWP is an active BWP, as shown in Figure 6. Otherwise, the RB numbering may start from the lowest RB of the determined DL BWP.

[0101] For this reason, as shown in FIG. 6, when CFR is larger than CORESET (bandwidth is wide), there is a possibility that RBs that cannot be allocated (cannot be specified by RB numbers) may occur.

[0102] Below, an example of operation that allows appropriate setting (scheduling) of MBS PDSCH (Multicast PDSCH) even in such a case will be described.

[0103] (3.2) Example of operation The following describes operations related to handling of RB numbers when DCI of a specific format, specifically DCI format 1_0, is used in MBS.

[0104] (3.2.1) Example 1 In this operation example, it may be assumed that UE 200 determines the lowest RB (lowest RB) with an RB number of CFR as a reference. Note that the lowest RB may be interpreted as the RB with the lowest frequency in the frequency band (e.g., the CFR frequency band) (same below). Also, the reference may be that the reference PRB index is "PRB index = 0" and PDSCH resources are allocated (same below).

[0105] Fig. 7 shows an example (part 1) of the relationship between resource blocks of CORESET and resource blocks of CFR according to operation example 1. As shown in Fig. 7, the RB numbering (RB number) of the PDSCH scheduled by DCI format 1_0 in the PDCCH common search space (CSS) may be based on the lowest RB of CFR.

[0106] The CFR may be set by signaling of a higher layer (such as RRC), or may be determined by the UE 200 itself using a predetermined method.

[0107] Note that the operation of setting the RB numbering of the PDSCH based on the CFR lowest RB may be limited to the case where an MBS PDSCH is configured (or in other words, the case where a CFR is configured).

[0108] Alternatively, the operation of using the CFRlowest RB as the basis for the RB numbering of the PDSCH may be limited to the case where CRC (Cyclic Redundancy Checksum) scrambling is performed by the G-RNTI. On the other hand, in cases other than the case where CRC scrambling is performed by the G-RNTI, the CORESETlowest RB may be used as the basis (similar to Release-16, etc.).

[0109] In addition, the operation of numbering the RBs of PDSCH based on the CFR lowest RB may be limited to the case where CFR lowest RB < CORESET lowest RB, that is, when the frequency of the CFR lowest RB is lower than the frequency of the CORESET lowest RB.

[0110] FIG. 8 shows an example of the relationship (Part 2) between the resource blocks of the CORESET according to Operation Example 1 and the resource blocks of the CFR. FIG. 9 shows an example of the relationship (Part 3) between the resource blocks of the CORESET according to Operation Example 1 and the resource blocks of the CFR.

[0111] As shown in FIG. 8, when CORESET lowest RB ≤ CFR lowest RB, CORESET lowest RB may be used as a reference (similar to Release-16, etc.).

[0112] Also, as shown in FIG. 9, when CORESET lowest RB ≤ CFR lowest RB, CFR lowest RB may be used as a reference.

[0113] Regarding whether to use either CORESET lowest RB or CFR lowest RB as a reference, it may be defined in advance by the 3GPP specifications or set by upper-layer signaling.

[0114] (3.2.2) Operation Example 2 In this operation example, UE200 may assume that CORESET lowest RB ≤ CFR lowest RB. FIG. 10 shows an example of the relationship between the resource blocks of the CORESET according to Operation Example 2 and the resource blocks of the CFR.

[0115] When scheduled by DCI format 1_0 in the PDCCH common search space (CSS), UE 200 may always assume that CORESET lowest RB (PRB)≦CFR lowest RB (PRB), as shown in Fig. 10. That is, the RB numbering (RB number) of the PDSCH scheduled by DCI format 1_0 in the PDCCH common search space (CSS) may be assumed to be CORESET lowest PRB≦CFR lowest PRB.

[0116] In this way, UE 200 does not need to assume a CFR setting other than CORESETlowest PRB≦CFRlowest PRB. Also, the above assumption may be limited to a case where an MBS PDSCH is configured (or, in other words, a case where a CFR is configured).

[0117] Alternatively, the above assumption may be limited to the case where CRC scrambling is performed by the G-RNTI. On the other hand, the UE 200 may not make the above assumption in cases other than the case where CRC scrambling is performed by the G-RNTI.

[0118] (3.2.3) Example 3 In this operation example, UE 200 may assume the RBs of the MBS PDSCH based on the CORESET lowest RB, and may assume that the RB index of CORESET is indicated by a negative value.

[0119] FIG. 11 shows an example of the relationship between resource blocks of CORESET and resource blocks of CFR according to the third operation example.

[0120] When scheduled by DCI format 1_0 in the PDCCH common search space (CSS), as shown in FIG. 11, UE 200 may use the CORESET lowest RB as a reference for the RB numbering (RB number) of the PDSCH scheduled by DCI format 1_0 (similar to Release-16, etc.), but may set a negative value to the RB index so that CFR can be indicated.

[0121] In the example shown in FIG. 11, the RB index of the CORESET lowest RB is 0, and RBs with a CFR lower than the CORESET lowest RB are designated by negative values ​​(-1 to -10).

[0122] Such a negative RB index may be indicated as a negative PRB index by the FDRA configured by the RRC, and the maximum negative value may be the CFRlowest RB.

[0123] Note that the operation of applying a negative value to the RB index of CORESET may be limited to the case where MBS PDSCH is configured (or in other words, the case where CFR is configured).

[0124] Alternatively, the operation of applying a negative value to the RB number (RB index) of CORESET may be limited to the case where CRC scrambling is performed by the G-RNTI. On the other hand, in cases other than the case where CRC scrambling is performed by the G-RNTI, the CORESETlowest RB may be used as the basis (similar to Release-16, etc.), and negative values ​​may not be allowed to be set.

[0125] (3.2.4) Example 4 In this operation example, UE 200 may assume RBs of MBS PDSCH based on CORESET lowest RB, but may assume RB numbers (RB indexes) based on CORESET within the range of CFR or BWP.

[0126] 12 shows an example (part 1) of the relationship between resource blocks of CORESET and resource blocks of CFR according to operation example 4. FIG. 13 shows an example (part 2) of the relationship between resource blocks of CORESET and resource blocks of CFR according to operation example 4.

[0127] In this operation example, as in operation example 3, when scheduling is performed using DCI format 1_0 in the PDCCH common search space (CSS), UE 200 may use the CORESET lowest RB as the reference for the RB numbering (RB number) of the PDSCH scheduled using DCI format 1_0 (as in Release-16, etc.), but in order to indicate the CFR, the RB number (RB index) may wrap around to the opposite side (left end) after reaching the end of the CFR or BWP (the right end in Figures 12 and 13), and the RB numbers may be continuous (this may be called a mod operation).

[0128] FIG. 12 shows an example in which the RB numbers reach the right end of the CFR (RB index=40), then move to the left end of the CFR where the RB numbers continue (RB index=41). The RBs from the CFR lowest (RB index=41) to just before the CORESET lowest RB (RB index=50) are indicated by negative values. Note that the right end of the CFR may be interpreted as the end on the high frequency side, and the left end of the CFR may be interpreted as the end on the low frequency side.

[0129] 13 shows an example in which the RB numbers continue from the right end of the BWP (RB index=50) to the left end of the BWP (RB index=51). The RBs from the lowest RB of the BWP (RB index=51) to just before the CORESET lowest RB (RB index=70) are indicated by negative values.

[0130] Note that the operation of applying such a mod operation of the RB number may be limited to the case where an MBS PDSCH is set (or in other words, the case where a CFR is set).

[0131] Alternatively, the application of the mod operation of the RB number may be limited to the case where CRC scrambling is performed by the G-RNTI. On the other hand, in cases other than the case where CRC scrambling is performed by the G-RNTI, the CORESETlowest RB may be used as the criterion (similar to Release-16, etc.).

[0132] Furthermore, even if the PRB index is a consecutive number, the PRB allocation may not be a consecutive number. Therefore, the operation of applying the mod operation of such an RB number may be limited to the case of non-contiguous PRB allocation.

[0133] (3.2.5) Examples of changes The above-described operation example may be applied not only to UE 200 in the RRC_CONNECTED state in the MBS, but also to UE 200 in other RRC states, specifically, to UE 200 in the RRC_IDLE and / or RRC_INACTIVE state in the MBS.

[0134] That is, the RRC state of the UE 200 may be RRC_IDLE or RRC_INACTIVE. Note that INACTIVE may be interpreted as a state in which, like RRC_IDLE, all RRC settings are not released and some settings are maintained.

[0135] Furthermore, when CORESET0 is set, the number of bits of the FDRA field of DCI format 1_0 transmitted in the CSS may be determined as follows based on the size of CORESET0.

[0136] 24RB: 9 bits 48RB: 11 bits 96RB: 13 bits Note that CORESET0 is a special CORESET that is different from a normal CORESET. Such a special CORESET may be interpreted as a CORESET that transmits a PDCCH for SIB (System Information Block) 1 scheduling.

[0137] On the other hand, if CORESET0 is not set, the number of bits in the FDRA field of DCI format 1_0 may be determined as follows based on the initial DL BWP size.

[0138] 275RB: 16-bit Furthermore, the PDSCH allocation granularity may be interpreted as a CFR size that can be covered without waste by a 13-bit RIV (Resource Indication Value) of up to 127 RBs. Therefore, if the CORESET0 size is 96 RBs and the CFR is larger than 127 RBs, there may be RBs that cannot be allocated with an allocation granularity of 1 RB.

[0139] Therefore, at least one of the following measures may be taken.

[0140] Increase the number of bits in the FDRA field - Set the RB allocation granularity to multiple RB units (or increase the RB allocation granularity / unit)

[0141] (4) Actions and Effects According to the above-described embodiment, the following advantageous effects can be obtained: Specifically, when DCI is DCI format 1_0 in an MBS, the UE 200 may estimate the RBs of the PDSCH based on the CFRlowest RB.

[0142] Furthermore, in the MBS, when the DCI is DCI format 1_0, the UE 200 may assume that CORESET lowest RB≦CFRlowest RB.

[0143] Furthermore, when DCI is DCI format 1_0 in an MBS, UE 200 may assume RBs of the MBS PDSCH based on CORESET lowest RBs and assume that some of CORESETlowest RBs are indicated by negative values. Alternatively, when DCI is DCI format 1_0 in an MBS, UE 200 may assume RBs of the MBS PDSCH based on CORESET lowest RBs and assume that RBs are displayed based on CORESET within the range of CFR or BWP.

[0144] Therefore, even if a specific DCI with a small size, such as DCI format 1_0, is used and the CFR band (RB) is wider than the CORESET band (RB), an appropriate CFR can be assigned, and the MBS PDSCH (Multicast PDSCH) can be scheduled more reliably.

[0145] (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.

[0146] For example, in the above-described embodiment, the names PDCCH and PDSCH are used as downlink channels, but the downlink control channel or downlink data channel (which may be a shared channel) may be called by another name.

[0147] Furthermore, as described above, the target DCI format is not limited to DCI format 1_0, but may be other DCI formats (DCI format 1_1, DCI format 1_2, etc.).

[0148] Also, 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 also 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] Furthermore, the block diagram (FIG. 4) used in the description of the above-described embodiment shows functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of 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 connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

[0151] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, 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 UE 200 described above may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 14 is a diagram showing an example of the hardware configuration of the device. As shown in Fig. 9, the device may be configured as a computer 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, a register, and the like.

[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-mentioned embodiments. Furthermore, the various processes described above may be executed by one 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, for example, at least one of 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 can store a program (program code), a software module, etc., that can execute 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 appropriate 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 (for example, 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 (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0163] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to 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 extended 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 (for example, an MME or an 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 (for example, an MME and an 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 / output via multiple network nodes.

[0170] The input and output information may be stored in a specific location (for example, 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 sent 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] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by 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 explained 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, relative values ​​from a predetermined value, or 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 called 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, or the mobile object itself. 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 interpreted 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 interpreted as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be interpreted as a side channel (or side link).

[0187] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may 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 a communication parameter applied to at least one of transmission and 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 a transceiver in the frequency domain, and specific windowing operations performed by a 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 called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called 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 performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. However, 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 word, etc. is actually mapped may be shorter than the TTI.

[0195] 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. Also, 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 called 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 called 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 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 also be determined based on numerology.

[0199] The time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each TTI, subframe, etc. may be composed 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, or the like.

[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 can 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 also 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 used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" 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. [Explanation of symbols]

[0216] 10. Wireless communication systems 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus

Claims

1. a receiver for receiving downlink control information for scheduling downlink data channels for a plurality of terminals; a control unit that determines, in data delivery to the plurality of terminals when the RRC state of the terminals is RRC_IDLE or RRC_INACTIVE, resource blocks of the downlink data channel based on a lowest resource block of a common frequency resource (CFR) for the data delivery, based on a format of the downlink control information; The common frequency resource (CFR) is configured by higher layer signaling; The common frequency resource (CFR) is wider than the bandwidth of the control resource set (CORESET), The control unit determines the number of bits of a frequency domain resource allocation (FDRA) field of the downlink control information based on an initial downlink (DL) bandwidth portion (BWP) size when a CORESET for transmitting a downlink control channel (PDCCH) is not set for scheduling of a system information block.

2. a receiving step of receiving downlink control information scheduling downlink data channels for a plurality of terminals; and determining a resource block of a downlink data channel based on a format of the downlink control information, using the lowest resource block of a common frequency resource (CFR) for the data delivery as a reference, in data delivery to the plurality of terminals when the RRC state of the terminal is RRC_IDLE or RRC_INACTIVE; The common frequency resource (CFR) is configured by higher layer signaling; The common frequency resource (CFR) is wider than the bandwidth of the control resource set (CORESET), The determining step is a wireless communication method for a terminal, in which, when a CORESET for transmitting a downlink control channel (PDCCH) for scheduling a system information block is not set, the number of bits in a frequency domain resource allocation (FDRA) field of the downlink control information is determined based on an initial downlink (DL) bandwidth portion (BWP) size.

3. a base station that transmits higher layer signaling and downlink control information that schedules downlink data channels for multiple terminals; a receiving unit that receives the downlink control information from the base station; a control unit that determines a resource block of a downlink data channel based on a format of the downlink control information, using the lowest resource block of a common frequency resource (CFR) for data delivery as a reference, in data delivery to a plurality of terminals when the RRC state of the terminal is RRC_IDLE or RRC_INACTIVE; The common frequency resource (CFR) is configured by signaling of the higher layer; The common frequency resource (CFR) is wider than the bandwidth of the control resource set (CORESET), The control unit determines the number of bits of a frequency domain resource allocation (FDRA) field of the downlink control information based on an initial downlink (DL) bandwidth portion (BWP) size when a CORESET that transmits a downlink control channel (PDCCH) for scheduling of a system information block is not set.

Images