WO2023012982A1 - 端末及び無線通信方法 - Google Patents
端末及び無線通信方法 Download PDFInfo
- Publication number
- WO2023012982A1 WO2023012982A1 PCT/JP2021/029181 JP2021029181W WO2023012982A1 WO 2023012982 A1 WO2023012982 A1 WO 2023012982A1 JP 2021029181 W JP2021029181 W JP 2021029181W WO 2023012982 A1 WO2023012982 A1 WO 2023012982A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pdsch
- lowest
- resource
- resource block
- control information
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims description 52
- 238000000034 method Methods 0.000 title claims description 25
- 230000005540 biological transmission Effects 0.000 description 31
- 238000012545 processing Methods 0.000 description 22
- 238000010586 diagram Methods 0.000 description 18
- 230000006870 function Effects 0.000 description 10
- 230000011664 signaling Effects 0.000 description 9
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 7
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 7
- 125000004122 cyclic group Chemical group 0.000 description 5
- 238000013507 mapping Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000013468 resource allocation Methods 0.000 description 4
- 230000004913 activation Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000008054 signal transmission Effects 0.000 description 3
- 238000012384 transportation and delivery Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000009849 deactivation Effects 0.000 description 2
- 230000001934 delay Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 101150071746 Pbsn gene Proteins 0.000 description 1
- LELQZCNRZHLYFG-ZDVGBALWSA-N [(4e,7e)-trideca-4,7-dienyl] acetate Chemical compound CCCCC\C=C\C\C=C\CCCOC(C)=O LELQZCNRZHLYFG-ZDVGBALWSA-N 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005562 fading Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000006249 magnetic particle Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
- H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0091—Signaling for the administration of the divided path
- H04L5/0094—Indication of how sub-channels of the path are allocated
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/40—Connection management for selective distribution or broadcast
Definitions
- the present disclosure relates to terminals and wireless communication methods compatible with multicast/broadcast services.
- the 3rd Generation Partnership Project (3GPP) has specified the 5th generation mobile communication system (also called 5G, New Radio (NR) or Next Generation (NG)), and the next generation specification called Beyond 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G We are also proceeding with 5G, 5G Evolution or 6G
- Non-Patent Document 1 simultaneous data transmission (also called distribution) services (MBS: Multicast and Broadcast Services) (tentative name) to multiple specified or unspecified terminals (User Equipment, UE) in NR. is targeted (Non-Patent Document 1).
- MMS Multicast and Broadcast Services
- Non-Patent Document 2 DCI format 1_0 and DCI format 1_1 as formats for downlink control information (DCI: Downlink Control Information)
- multiple UEs configured with the same identification information (group-common RNTI (Radio Network Temporary Identifier, also known as G-RNTI)) share common frequency resource (CFR). It has also been agreed to assume a downlink data channel for MBS using .
- group-common RNTI Radio Network Temporary Identifier, also known as G-RNTI
- CFR common frequency resource
- the resource block (RB) numbering of the PDSCH scheduled in the Common Search Space (CSS) is the lowest RB of the control resource sets (CORESET) that received the DCI.
- CCS Common Search Space
- the following disclosure is made in view of this situation, and provides 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. aim.
- One aspect of the present disclosure is a receiving unit (control signal/reference signal processing unit 240) that receives downlink control information, and in data distribution for a plurality of terminals, when the downlink control information is in a specific format,
- a terminal (UE 200) including a control unit (control unit 270) that assumes a resource block for a downlink data channel based on the lowest resource block for data distribution.
- One aspect of the present disclosure is a receiving unit (control signal/reference signal processing unit 240) that receives downlink control information, and in data distribution for a plurality of terminals, when the downlink control information is in a specific format,
- a terminal (UE 200) including a control unit (control unit 270) that assumes that the lowest resource block of a control resource set is equal to or less than the lowest resource block for data distribution.
- One aspect of the present disclosure is a receiving unit (control signal/reference signal processing unit 240) that receives downlink control information, and in data distribution for a plurality of terminals, when the downlink control information is in a specific format, a control unit (control unit 270) that assumes a downlink data channel resource block based on the lowest resource block of a control resource set, and the control unit assumes that at least the lowest resource block of the control resource set has a negative value.
- a terminal UE 200 assumed to be indicated by .
- One aspect of the present disclosure is a receiving unit (control signal/reference signal processing unit 240) that receives downlink control information, and in data distribution for a plurality of terminals, when the downlink control information is in a specific format, a control unit (control unit 270) that assumes a resource block of a downlink data channel based on the lowest resource block of the control resource set, and the control unit selects the frequency resource for data distribution or the specified bandwidth part. In the range, it is a terminal (UE 200) that assumes display of resource blocks based on the control resource set.
- One aspect of the present disclosure is the step of receiving downlink control information, and in data distribution for a plurality of terminals, when the downlink control information is in a specific format, the lowest resource block for data distribution is used as a reference and estimating resource blocks of a downlink data channel as .
- One aspect of the present disclosure is a step of receiving downlink control information, and in data distribution for a plurality of terminals, when the downlink control information is in a specific format, the lowest resource block of a control resource set is the and assuming no more than the lowest resource block for data delivery.
- FIG. 1 is an overall schematic configuration diagram of a radio communication system 10.
- FIG. 2 is a diagram showing a configuration example of radio frames, subframes and slots used in the radio communication system 10.
- FIG. 3 is a diagram showing a configuration example of PTM transmission scheme 1 and PTM transmission scheme 2.
- FIG. 4 is a functional block configuration diagram of gNB100 and UE200.
- FIG. 5 is a diagram showing a sequence example of PDCCH, PDSCH and HARQ feedback in MBS.
- 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.
- FIG. 1 is an overall schematic configuration diagram of a radio communication system 10.
- FIG. 2 is a diagram showing a configuration example of radio frames, subframes and slots used in the radio communication system 10.
- FIG. 3 is a diagram showing a configuration example of PTM transmission scheme 1 and PTM transmission scheme 2.
- FIG. 4 is a functional block configuration diagram of gNB100 and UE
- FIG. 7 is a diagram illustrating an example (part 1) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 1;
- FIG. 8 is a diagram illustrating an example (part 2) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 1.
- FIG. 9 is a diagram illustrating an example (part 3) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 1;
- FIG. 10 is a diagram illustrating an example of the relationship between CORESET resource blocks and CFR resource blocks according to Operation Example 2.
- FIG. 11 is a diagram illustrating an example of the relationship between CORESET resource blocks and CFR resource blocks according to Operation Example 3.
- FIG. 12 is a diagram illustrating an example (part 1) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 4;
- FIG. 13 is a diagram illustrating an example (part 2) of the relationship between CORESET resource blocks and CFR resource blocks according to Operation Example 4.
- FIG. 14 is a diagram showing an example of the hardware configuration of gNB100 and UE200.
- FIG. 1 is an overall schematic configuration diagram of a radio communication system 10 according to the present embodiment.
- the radio communication system 10 is a radio communication system according 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). include.
- NR 5G New Radio
- NG-RAN 20 Next Generation-Radio Access Network 20
- UE 200 User Equipment 200
- the wireless communication system 10 may be a wireless communication system according to a system called Beyond 5G, 5G Evolution, or 6G.
- NG-RAN 20 includes a radio base station 100 (hereinafter gNB 100).
- gNB 100 radio base station 100
- 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.
- 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). Note that NG-RAN 20 and 5GC may simply be referred to as a "network”.
- gNBs or ng-eNBs
- 5GC 5G-compliant core network
- the gNB100 is an NR-compliant radio base station and performs NR-compliant radio communication with the UE200.
- the gNB100 and UE200 use Massive MIMO, which generates beams with higher directivity by controlling radio signals transmitted from multiple antenna elements, and Carrier Aggregation (CA), which bundles multiple component carriers (CC). , and dual connectivity (DC) in which communication is performed simultaneously between the UE and each of a plurality of NG-RAN Nodes.
- Massive MIMO which generates beams with higher directivity by controlling radio signals transmitted from multiple antenna elements
- CA Carrier Aggregation
- CC component carriers
- DC dual connectivity
- the wireless communication system 10 supports FR1 and FR2.
- the frequency bands of each FR are as follows.
- FR1 410MHz to 7.125GHz
- FR2 24.25 GHz to 52.6 GHz
- SCS Sub-Carrier Spacing
- BW bandwidth
- FR2 is a higher frequency than FR1, with an SCS of 60 or 120 kHz (240 kHz may be included) and a bandwidth (BW) of 50-400 MHz may be used.
- the wireless communication system 10 may also support a higher frequency band than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands above 52.6 GHz and up to 114.25 GHz. The wireless communication system 10 may support frequency bands between FR1 and FR2. FR2 may also include FR2-1 (24.25-52.6 GHz) and FR2-2 (52.6-71 GHz).
- Cyclic Prefix-Orthogonal Frequency Division Multiplexing CP-OFDM
- DFT-S-OFDM Discrete Fourier Transform-Spread
- SCS Sub-Carrier Spacing
- DFT-S-OFDM may be applied not only to the uplink (UL) but also to the downlink (DL).
- FIG. 2 shows a configuration example of radio frames, subframes and slots used in the radio communication system 10.
- 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 forming one slot does not necessarily have to be 14 symbols (for example, 28 or 56 symbols). Also, the number of slots per subframe may vary depending on the SCS. Additionally, the SCS may be wider than 240kHz (eg, 480kHz, 960kHz, as shown in Figure 2).
- time direction (t) shown in FIG. 2 may be called the time domain, symbol period, symbol time, or the like.
- the frequency direction may also be referred to as frequency domain, resource block, resource block group, subcarrier, bandwidth part (BWP), subchannel, common frequency resource, and so on.
- the wireless communication system 10 may provide Multicast and Broadcast Services (MBS).
- MBS Multicast and Broadcast Services
- unicast may be interpreted as one-to-one communication with a network by specifying one specific UE 200 (identification information unique to the UE 200 may be specified).
- Multicast may be interpreted as communication performed one-to-many (specified many) with the network by designating a plurality of specific UEs 200 (identification information for multicast may be designated). Note that the number of UEs 200 that receive received multicast data may eventually be one.
- Broadcast may be interpreted as one-to-unspecified communication with the network for all UE 200.
- the data to be multicast/broadcast may have the same copied content, but may have different content such as a header.
- multicast/broadcast data may be sent (delivered) at the same time, but does not necessarily require strict concurrency and may include propagation delays and/or processing delays within the RAN nodes, and the like.
- the radio resource control layer (RRC) state of the target UE 200 is either an idle state (RRC idle), a connected state (RRC connected), or another state (eg, inactive state). good too.
- the inactive state may be interpreted as a state in which some RRC settings are maintained.
- MBS Physical Downlink Shared Channel
- MBS PDSCH Physical Downlink Shared Channel
- Multicast PDSCH Physical Downlink Shared Channel
- RRC connected UE may be read as RRC idle UE and RRC inactive UE.
- ⁇ PTM transmission method 1 (PTM-1): - A group-common PDSCH is scheduled using a group-common PDCCH (Physical Downlink Control Channel) for the MBS group of the RRC connected UE.
- PTM-1 A group-common PDSCH is scheduled using a group-common PDCCH (Physical Downlink Control Channel) for the MBS group of the RRC connected UE.
- PDCCH Physical Downlink Control Channel
- group-common RNTI Radio Network Temporary Identifier, also called G-RNTI
- ⁇ PTM transmission method 2 (PTM-2): - A group-common PDSCH is scheduled using terminal specific (UE-specific) PDCCH with respect to the MBS group of RRC connected UE.
- ⁇ PDSCH is scrambled by group-common RNTI.
- ⁇ PTP transmission method - Schedule a UE-specific PDSCH using a UE-specific PDCCH for an RRC connected UE.
- - PDCCH CRC and PDSCH are scrambled by UE-specific RNTI. In other words, it may mean that MBS packets are transmitted by unicast.
- FIG. 3 shows a configuration example of PTM transmission method 1 and PTM transmission method 2.
- the UE-specific PDCCH/PDSCH can be identified by the target UE, but may not be identified by other UEs within the same MBS group.
- a group common PDCCH/PDSCH is transmitted on the same time/frequency resource and can be identified by all UEs within the same MBS group.
- the names of the PTM transmission methods 1 and 2 are tentative names, and may be called by other names as long as the above-described operations are performed.
- RAN nodes may deliver individual copies of MBS data packets to individual UEs over the air.
- PTM point-to-multipoint
- a RAN node may deliver a single copy of MBS data packets over the air to a set of UEs.
- HARQ Hybrid Automatic repeat request
- ACK/NACK feedback Both ACK/NACK feedback (ACK/NACK feedback) ⁇ UEs that successfully receive/decode PDSCH transmit ACK. ⁇ UEs that fail to receive/decode PDSCH transmit NACK.
- PUCCH-Config Physical Uplink Control Channel
- - PUCCH resource Shared/orthogonal between UEs depends on network settings - HARQ-ACK CB (codebook): 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 ⁇ A UE that has successfully received and decoded PDSCH does not transmit an ACK (does not transmit a response). ⁇ A UE that fails to receive or decode PDSCH transmits NACK. ⁇ In a given UE, PUCCH resource settings can be set separately by unicast or groupcast (multicast). ACK is a positive acknowledgment. , NACK may be called a negative acknowledgment. HARQ may be referred to as automatic repeat request.
- ⁇ RRC and downlink control information (DCI: Downlink Control Information) • RRC only Also, the following content is assumed for SPS (Semi-persistent Scheduling) of multicast/broadcast PDSCH.
- DCI Downlink Control Information
- ⁇ SPS group-common PDSCH (may be called group common SPS PDSCH) is adopted ⁇ Multiple SPS group-common PDSCHs can be configured as UE capabilities ⁇ HARQ feedback for SPS group-common PDSCH is possible ⁇ At least activation/deactivation by group-common PDCCH (downlink control channel) is possible. good. For example, activation may be read as activation, start, trigger, etc., and deactivation may be further read as end, stop, etc. FIG.
- SPS is a scheduling used in contrast to dynamic scheduling, and may be called semi-fixed, semi-persistent or semi-persistent scheduling, or interpreted as Configured Scheduling (CS) good.
- CS Configured Scheduling
- Scheduling may be interpreted as the process of allocating resources for transmitting data.
- Dynamic scheduling may be interpreted as a mechanism whereby all PDSCHs are scheduled by DCI (eg DCI format 1_0, DCI format 1_1).
- SPS may be interpreted as a mechanism by which PDSCH transmissions are scheduled by higher layer signaling such as RRC messages.
- multiple UEs configured with the same identification information may assume MBS PDSCH using a common frequency resource (CFR: common frequency resource).
- CFR common frequency resource
- Multicast SPS PDSCH reception may mean group common SPS PDSCH reception, may be SPS PDSCH received by multiple terminals, and may be G-RNTI or G-CS-RNTI (that is, multiple terminals may be SPS PDSCH reception associated with the associated RNTI). Also, Multicast may be read as Broadcast.
- multicast, groupcast, broadcast, and MBS may be read interchangeably.
- Multicast PDSCH and PDSCH scrambled by group common RNTI may be read interchangeably.
- data and packet may be read interchangeably, and may be interpreted as being synonymous with terms such as signal and data unit.
- transmission, reception, transmission and distribution may be read interchangeably.
- FIG. 4 is a functional block configuration diagram of gNB100 and UE200.
- the UE 200 will be described below.
- the UE 200 includes a radio signal transmission/reception unit 210, an amplifier unit 220, a modem unit 230, a control signal/reference signal processing unit 240, an encoding/decoding unit 250, a data transmission/reception unit 260, and a control unit 270. .
- FIG. 4 shows only main functional blocks related to the description of the embodiment, and that the UE 200 has other functional blocks (for example, power supply section, etc.). Also, FIG. 4 shows the functional block configuration of the UE 200 (gNB 100), and please refer to FIG. 14 for the hardware configuration.
- the radio signal transmitting/receiving unit 210 transmits/receives radio signals according to NR.
- the radio signal transmitting/receiving unit 210 supports Massive MIMO, CA that bundles multiple CCs, and DC that simultaneously communicates between the UE and each of the two NG-RAN Nodes.
- 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 for multiple UEs 200 .
- the radio signal transmitting/receiving unit 210 can receive a downlink data channel (PDSCH) in MBS, that is, data distribution for multiple terminals.
- PDSCH downlink data channel
- the radio signal transmitting/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 terminal groups.
- a group-common PDSCH which may include an SPS group-common PDSCH
- PDSCH downlink data channel
- radio signal transmitting/receiving section 210 can receive a downlink control channel common to a terminal group, specifically group-common PDCCH, and can receive a terminal-specific downlink control channel, specifically UE-specific PDCCH. .
- the amplifier section 220 is configured by a PA (Power Amplifier)/LNA (Low Noise Amplifier) and the like. Amplifier section 220 amplifies the signal output from modem section 230 to a predetermined power level. In addition, amplifier section 220 amplifies the RF signal output from radio signal transmission/reception section 210 .
- PA Power Amplifier
- LNA Low Noise Amplifier
- the modulation/demodulation unit 230 executes data modulation/demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100, etc.).
- the modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform-Spread (DFT-S-OFDM). Also, DFT-S-OFDM may be used not only for uplink (UL) but also for downlink (DL).
- the control signal/reference signal processing unit 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.
- control signal/reference signal processing unit 240 receives various control signals transmitted from the gNB 100 via a predetermined control channel, for example, radio resource control layer (RRC) control signals (messages). . Also, the control signal/reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.
- RRC radio resource control layer
- the control signal/reference signal processing unit 240 executes processing using reference signals (RS) such as Demodulation Reference Signal (DMRS) and Phase Tracking Reference Signal (PTRS).
- RS reference signals
- DMRS Demodulation Reference Signal
- PTRS Phase Tracking Reference Signal
- a DMRS is a known reference signal (pilot signal) between a terminal-specific base station and a terminal for estimating the fading channel used for data demodulation.
- PTRS is a terminal-specific reference signal for estimating phase noise, which is a problem in high frequency bands.
- reference signals may include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), Positioning Reference Signal (PRS) for position information, and the like.
- CSI-RS Channel State Information-Reference Signal
- SRS Sounding Reference Signal
- PRS Positioning Reference Signal
- control channels include PDCCH, PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI)), and Physical Broadcast Channel (PBCH) may be included.
- PDCCH Physical Uplink Control Channel
- RACH Random Access Channel
- DCI Downlink Control Information
- RA-RNTI Random Access Radio Network Temporary Identifier
- PBCH Physical Broadcast Channel
- data channels include PDSCH and PUSCH (Physical Uplink Shared Channel).
- Data may refer to data transmitted over a data channel.
- control signal/reference signal processing unit 240 may constitute a receiving unit that receives downlink control information (DCI).
- DCI may target all formats defined in 3GPP TS38.212, but in this embodiment, in particular, the control signal/reference signal processing unit 240 receives DCI conforming to DCI format 1_0 and DCI format 1_1. You can For MBS, DCI format 1_0 or DCI format 1_1 may be used.
- DCI format 1_0 may be used for PDSCH scheduling within a cell.
- DCI format 1_1 may also be used for PDSCH scheduling within a cell.
- DCI format 1_0 may have fewer bits than DCI format 1_1 (and other DCI formats).
- the DCI format includes 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 (Modulation and coding scheme) may be included.
- the encoding/decoding unit 250 performs data segmentation/concatenation, channel coding/decoding, etc. for each predetermined communication destination (gNB 100 or other gNB).
- the encoding/decoding unit 250 divides the data output from the data transmission/reception unit 260 into pieces of a predetermined size, and performs channel coding on the divided data. Also, encoding/decoding section 250 decodes the data output from modem section 230 and concatenates the decoded data.
- the data transmission/reception unit 260 executes transmission/reception of Protocol Data Unit (PDU) and Service Data Unit (SDU). Specifically, the data transmitting/receiving unit 260 performs PDU/SDU in multiple layers (medium access control layer (MAC), radio link control layer (RLC), packet data convergence protocol layer (PDCP), etc.). Assemble/disassemble etc.
- the data transmission/reception unit 260 also performs data error correction and retransmission control based on hybrid ARQ (Hybrid automatic repeat request). Specifically, the data transmitter/receiver 260 can transmit HARQ (automatic repeat request) feedback.
- HARQ automatic repeat request
- the control unit 270 controls each functional block that configures the UE200.
- the control unit 270 executes control for downlink channel scheduling for MBS and HARQ feedback for this channel.
- the control unit 270 executes control corresponding to downlink channel scheduling common to a terminal group (group common) in MBS, that is, data distribution for a plurality of UEs 200 .
- control section 270 can perform control corresponding to scheduling of group-common PDCCH and group-common PDSCH.
- the control unit 270 may assume resource blocks (RB) of the downlink data channel based on the lowest resource block for MBS. For example, when DCI format 1_0 is used in MBS, control unit 270 determines that RB numbering of PDSCH (MBS PDSCH) scheduled using DCI format 1_0 in common search space (CSS) is We may assume that the lowest RB is the reference. Note that the DCI format is not necessarily limited to DCI format 1_0, and may be DCI format 1_1 or the like (same below).
- RB numbering may mean directly or indirectly indicating the RB number (or RB index) to which the PDSCH is assigned.
- RB numbers may be indicated by arbitrary numbers such as 0 to x, and may substantially correspond to subcarriers.
- Downlink (DL) radio resources used for PDCCH transmission can be specified by control resource sets (CORESET). That is, CORESET may be interpreted as a set of physical resources (specifically, specific regions on the DL resource grid) and parameters used to transmit PDCCH (including DCI).
- CORESET may be interpreted as a set of physical resources (specifically, specific regions on the DL resource grid) and parameters used to transmit PDCCH (including DCI).
- UE 200 can assume the specific area to which CORESET is assigned based on the timing and period specified by CSS.
- the control unit 270 may assume that the lowest resource block for CORESET is equal to or less than the lowest resource block for data distribution when DCI is in a specific format in MBS. For example, when DCI format 1_0 is used in MBS and scheduling is performed using DCI format 1_0 in CSS, control section 270 may assume that the lowest RB of CORESET is equal to or less than the lowest RB of CFR.
- control unit 270 may assume that CORESET lowest RB ⁇ CFRlowest RB when scheduling is performed using DCI format 1_0 in CSS. That is, you can assume that the CORESET lowest RB number is always less than or equal to the CFRlowest RB.
- control unit 270 may assume the RB of the MBS PDSCH based on the resource block with the lowest CORESET (CORESET lowest RB). .
- CORESET lowest RB Such behavior is the same as specified in 3GPP TS38.214 such as Release-16.
- control section 270 may assume that at least the lowest CORESET resource block (CORESETlowest RB) is indicated by a negative value. That is, some RB numbers on the low frequency side of CORESET may be indicated by negative values.
- control section 270 may assume MBS PDSCH RBs based on the resource block with the lowest CORESET (CORESET lowest RB). However, within the frequency resource (CFR) for the MBS or the defined bandwidth part (BWP), we may assume the representation of resource blocks relative to CORESET. Note that the BWP band (the number of RBs) may be wider than the CFR band (the number of RBs).
- control section 270 specifies the RB number based on CORESET lowest RB, and when one end of CFR in the frequency direction (either on the high frequency side or the low frequency side) is reached. , move to the opposite end of the CFR, and the RB numbers may be consecutive (may be called mod operation).
- control section 270 reaches one end of the BWP in the frequency direction (either on the high frequency side or the low frequency side).
- RB numbers may be consecutive (may be called mod operation).
- FIG. 5 shows a sequence example of PDCCH, PDSCH and HARQ feedback in MBS.
- PDCCH which may include DCI
- PDSCH may be transmitted by unicast or multicast (broadcast).
- the UE 200 may transmit HARQ feedback (ACK/NACK) for (the transport block (TB) received via) the channel.
- ACK/NACK HARQ feedback
- both unicast PDSCH and multicast PDSCH are transmitted after one PDCCH/DCI, but either unicast PDSCH or multicast PDSCH is transmitted after one PDCCH/DCI. may be sent. That is, one PDCCH/DCI may schedule either unicast PDSCH or multicast PDSCH.
- the same RNTI (eg, G-RNTI) may be set for multiple UEs targeted for MBS, and each UE may blind-decode DCI based on the G-RNTI.
- MBS agrees to use at least DCI format 1_0 or DCI format 1_1.
- 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.
- the DCI format 1_0 may be the DCI with the smallest size among the DCIs.
- multiple UEs configured with the same identification information assume a common frequency resource (CFR: common frequency resource), use the CFR, MBS PDSCH ( Multicast PDSCH) resources may be indicated and controlled.
- CFR common frequency resource
- Fig. 6 shows an example of the relationship between CORESET resource blocks and CFR resource blocks when DCI format 1_0 is used.
- the UE 200 When the UE 200 receives a scheduling grant in DCI format 1_0, it may use downlink resource allocation type 1 (see 3GPP TS38.214 Section 5.1.2.2).
- RB numbering may start from the lowest RB of CORESET that received DCI. Otherwise, the RB number may start from the lowest RB of the determined DL BWP.
- the UE 200 may assume that the RB number is determined based on the lowest RB of the CFR. Note that the lowest RB may be interpreted as the RB with the lowest frequency in the frequency band (for example, the CFR frequency band) (same below).
- FIG. 7 shows an example (part 1) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 1.
- FIG. 7 shows an example (part 1) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 1.
- FIG. 7 PDSCH RB numbering scheduled by DCI format 1_0 in PDCCH common search space (CSS) may be based on the lowest RB of CFR.
- SCS PDCCH common search space
- the CFR may be set by higher layer (RRC, etc.) signaling, or may be determined by the UE 200 itself by a predetermined method.
- RRC higher layer
- the operation based on the CFRlowest RB for RB numbering of PDSCH may be limited to the case of CRC (Cyclic Redundancy Checksum) scrambled by G-RNTI.
- CRC Cyclic Redundancy Checksum
- CORESETlowest RB may be used as a reference (similar to Release-16, etc.) except when CRC scrambled by G-RNTI.
- the operation based on CFRlowest RB for PDSCH RB numbering may be limited to cases where CFRlowest RB ⁇ CORESETlowest RB, that is, when the frequency of CFR lowest RB is lower than the frequency of CORESET lowest RB.
- FIG. 8 shows an example (part 2) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 1.
- FIG. 9 shows an example (part 3) of the relationship between the CORESET resource blocks and the CFR resource blocks according to the first operation example.
- CORESETlowest RB may be used as the standard (similar to Release-16, etc.).
- CFR lowest RB when CORESETlowest RB ⁇ CFRlowest RB, CFR lowest RB may be used as a reference.
- CORESETlowest RB or CFRlowest RB is used as a reference may be defined in advance by the 3GPP specifications, or may be set by higher layer signaling.
- FIG. 10 shows an example of the relationship between CORESET resource blocks and CFR resource blocks according to Operation Example 2.
- UE 200 When scheduled by DCI format 1_0 in the PDCCH common search space (CSS), UE 200 can always assume that CORESETlowest RB (PRB) ⁇ CFRlowest RB (PRB), as shown in FIG. That is, the PDSCH RB numbering (RB numbering) scheduled by DCI format 1_0 in the PDCCH common search space (CSS) may be assumed to be CORESET lowest PRB ⁇ CFR lowest PRB.
- the UE 200 does not have to assume a CFR setting that is not CORESETlowestPRB ⁇ CFRlowestPRB. Also, the above assumption may be limited to the case where the MBS PDSCH is configured (which may also be referred to as the case where the CFR is configured).
- the above assumption may be limited to the case of CRC scrambled by G-RNTI.
- UE 200 does not have to make the above assumptions except when CRC scrambled by G-RNTI.
- UE 200 may assume MBS PDSCH RBs based on CORESET lowest RB, but may assume that the CORESET RB number (RB index) is indicated by a negative value.
- FIG. 11 shows an example of the relationship between CORESET resource blocks and CFR resource blocks according to Operation Example 3.
- the RB number (RB index) may be set to a negative value so that the CFR can be indicated.
- the RB index of CORESET lowest RB is 0, and RBs with CFR lower than CORESET lowest RB are designated by negative values (-1 to -10).
- Such a negative RB index may be designated as a negative PRB index by FDRA set by RRC. Also, the maximum negative value may be CFRlowest RB.
- the operation of applying a negative value to the RB number (RB index) of CORESET may be limited to the case where MBS PDSCH is set (which can be rephrased as the case where CFR is set).
- the operation of applying a negative value to the RB number (RB index) of CORESET may be limited to cases where it is CRC scrambled by G-RNTI.
- CORESETlowest RB is used as the standard (similar to Release-16, etc.), and negative values may not be set.
- UE 200 may assume MBS PDSCH RBs based on CORESET lowest RB, but may assume an RB number (RB index) based on CORESET in the range of CFR or BWP.
- FIG. 12 shows an example (part 1) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 4.
- FIG. 13 shows an example (part 2) of the relationship between CORESET resource blocks and CFR resource blocks according to operation example 4.
- UE 200 when scheduling is performed by DCI format 1_0 in the PDCCH common search space (CSS), UE 200 sets PDSCH RB numbering (RB number) scheduled by DCI format 1_0 to CORESET
- RB number PDSCH RB numbering
- the lowest RB can be used as a standard (similar to Release-16, etc.), but the RB number (RB index) reaches the edge of the CFR or BWP (the right edge in Figures 12 and 13) and then the opposite direction so that the CFR can be indicated. side (left end), and the RB numbers may be consecutive (this may be called mod operation).
- the operation of applying the RB number mod operation may be limited to cases where it is CRC-scrambled by the G-RNTI.
- CORESETlowest RB may be used as a reference (similar to Release-16, etc.).
- the PRB allocation may not be a sequential number, so the operation of applying such RB number mod operation may be limited to non-contiguous PRB allocation.
- the RRC state of UE200 may be RRC_IDLE or RRC_INACTIVE.
- INACTIVE may be interpreted as a state in which all RRC settings are not released and some settings are maintained, like RRC_IDLE.
- the number of bits in the FDRA field of DCI format 1_0 sent in CSS may be determined as follows based on the size of CORESET0 when CORESET0 is set.
- CORESET0 is a special CORESET that is different from normal CORESET. Such a specific CORESET may be interpreted as a CORESET transmitting PDCCH for SIB (System Information Block) 1 scheduling.
- SIB System Information Block
- 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.
- the PDSCH allocation granularity may be interpreted as a CFR size up to 127 RBs that can be efficiently covered by a 13-bit RIV (Resource Indication Value). Therefore, if the CORESET0 size is 96 RBs and the CFR is larger than 127 RBs, there is a possibility that some RBs cannot be allocated with the allocation granularity of 1 RB.
- UE 200 may assume PDSCH RBs based on CFRlowest RBs.
- the UE 200 may assume that CORESET lowest RB ⁇ CFRlowest RB when DCI is DCI format 1_0 in MBS.
- UE 200 may assume MBS PDSCH RBs based on CORESET lowest RB, and assume that part of CORESETlowest RB is indicated by a negative value.
- UE 200 assumes RB of MBS PDSCH based on CORESET lowest RB, and assumes display of RB based on CORESET in the range of CFR or BWP. good too.
- the names PDCCH and PDSCH are used as downlink channels, but other names may be used as long as they are downlink control channels or downlink data channels (or shared channels). .
- 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.).
- configure, activate, update, indicate, enable, specify, and select may be read interchangeably. good.
- link, associate, correspond, and map may be read interchangeably to allocate, assign, monitor. , map, may also be read interchangeably.
- each functional block may be implemented using one device physically or logically coupled, or directly or indirectly using two or more physically or logically separate devices (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices.
- a functional block may be implemented by combining software in the one device or the plurality of devices.
- Functions include judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't
- a functional block (component) that performs transmission is called a transmitting unit or transmitter.
- the implementation method is not particularly limited.
- FIG. 14 is a diagram showing an example of the hardware configuration of the device.
- the device may be configured as a computing 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, and the like.
- the term "apparatus” can be read as a circuit, device, unit, or the like.
- the hardware configuration of the device may be configured to include one or more of each device shown in the figure, or may be configured without some of the devices.
- 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.
- each function of the device is implemented by causing the processor 1001 to perform calculations, controlling communication by the communication device 1004, and controlling the It is realized by controlling at least one of data reading and writing in 1002 and storage 1003 .
- a processor 1001 operates an operating system and controls the entire computer.
- the processor 1001 may be configured by a central processing unit (CPU) including interfaces with peripheral devices, a control unit, an arithmetic unit, registers, and the like.
- CPU central processing unit
- the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them.
- programs program codes
- software modules software modules
- data etc.
- the various processes described above may be executed by one processor 1001, or may be executed by two or more processors 1001 simultaneously or sequentially.
- Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.
- the memory 1002 is a computer-readable recording medium, and is composed of at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. may be
- ROM Read Only Memory
- EPROM Erasable Programmable ROM
- EEPROM Electrically Erasable Programmable ROM
- RAM Random Access Memory
- the memory 1002 may also be called a register, cache, main memory (main storage device), or the like.
- the memory 1002 can store programs (program code), software modules, etc. capable of executing a method according to an embodiment of the present disclosure.
- the storage 1003 is a computer-readable recording medium, for example, an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disc, a magneto-optical disc (for example, a compact disc, a digital versatile disc, a Blu-ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like.
- Storage 1003 may also be referred to as an auxiliary storage device.
- the recording medium described above may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003 .
- the communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like.
- the communication device 1004 includes a high-frequency switch, duplexer, filter, frequency synthesizer, etc., for realizing at least one of frequency division duplex (FDD) and time division duplex (TDD).
- FDD frequency division duplex
- TDD time division duplex
- the input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside.
- the output device 1006 is an output device (eg, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).
- 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 devices.
- the device includes hardware such as a microprocessor, digital signal processor (DSP), application specific integrated circuit (ASIC), programmable logic device (PLD), field programmable gate array (FPGA), etc.
- DSP digital signal processor
- ASIC application specific integrated circuit
- PLD programmable logic device
- FPGA field programmable gate array
- notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods.
- the notification of information may include 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 combinations thereof, and RRC signaling may also be referred to as RRC messages, e.g., RRC Connection Setup ) message, RRC Connection Reconfiguration message, or the like.
- DCI Downlink Control Information
- UCI Uplink Control Information
- RRC signaling e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), other signals, or combinations thereof
- RRC signaling may also be referred to as RRC messages, e.g., RRC Connection Setup ) message, R
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- SUPER 3G IMT-Advanced
- 4G 4th generation mobile communication system
- 5G 5th generation mobile communication system
- Future Radio Access FAA
- New Radio NR
- W-CDMA registered trademark
- GSM registered trademark
- CDMA2000 Code Division Multiple Access 2000
- UMB Ultra Mobile Broadband
- IEEE 802.11 Wi-Fi (registered trademark)
- IEEE 802.16 WiMAX®
- IEEE 802.20 Ultra-WideBand (UWB), Bluetooth®, other suitable systems, and/or next-generation systems enhanced therefrom.
- a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G).
- a specific operation that is performed by a base station in the present disclosure may be performed by its upper node in some cases.
- various operations performed for communication with a terminal may be performed by the base station and other network nodes other than the base station (e.g. MME or S-GW, etc., but not limited to).
- MME or S-GW network nodes
- the case where there is one network node other than the base station is exemplified above, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).
- Information, signals can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may be input and output via multiple network nodes.
- Input/output information may be stored in a specific location (for example, memory) or managed using a management table. Input and output information may be overwritten, updated, or appended. The output information may be deleted. The entered information may be transmitted to other devices.
- the determination may be made by a value represented by one bit (0 or 1), by a true/false value (Boolean: true or false), or by numerical comparison (for example, a predetermined value).
- notification of predetermined information is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.
- Software whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.
- software, instructions, information, etc. may be transmitted and received via a transmission medium.
- the Software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to access websites, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.
- wired technology coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.
- wireless technology infrared, microwave, etc.
- data, instructions, commands, information, signals, bits, symbols, chips, etc. may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of
- the channel and/or symbols may be signaling.
- a signal may also be a message.
- a component carrier may also be called a carrier frequency, a cell, a frequency carrier, or the like.
- system and “network” used in this disclosure are used interchangeably.
- 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.
- radio resources may be indexed.
- base station BS
- radio base station fixed station
- NodeB NodeB
- eNodeB eNodeB
- gNodeB gNodeB
- a base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.
- a base station can accommodate one or more (eg, three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area corresponding to a base station subsystem (e.g., a small indoor base station (Remote Radio)). Head: RRH) can also provide communication services.
- a base station subsystem e.g., a small indoor base station (Remote Radio)
- Head: RRH can also provide communication services.
- cell refers to part or all of the coverage area of at least one of a base station and base station subsystem that provides communication services in this coverage.
- MS Mobile Station
- UE User Equipment
- a mobile station is defined 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 It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.
- At least one of the base station and mobile station may be called a transmitting device, a receiving device, a communication device, or the like.
- At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like.
- the mobile body may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile body (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ).
- at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations.
- at least one of the base station and mobile station may be an Internet of Things (IoT) device such as a sensor.
- IoT Internet of Things
- the base station in the present disclosure may be read as a mobile station (user terminal, hereinafter the same).
- communication between a base station and a mobile station is replaced with communication between multiple mobile stations (for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.)
- the mobile station may have the functions that the base station has.
- words such as "up” and “down” may be replaced with words corresponding to inter-terminal communication (for example, "side”).
- uplink channels, downlink channels, etc. may be read as side channels (or sidelinks).
- a radio frame may consist of one or more frames in the time domain. Each frame or frames in the time domain may be referred to as a subframe. A subframe may also consist of one or more slots in the time domain. A subframe may be a fixed time length (eg, 1 ms) independent of numerology.
- a numerology may be a communication parameter that applies to the transmission and/or reception of a signal or channel. Numerology, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, transmission and reception specific filtering operations performed by the receiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, and/or the like.
- SCS subcarrier spacing
- TTI transmission time interval
- number of symbols per TTI radio frame structure
- transmission and reception specific filtering operations performed by the receiver in the frequency domain specific windowing operations performed by the transceiver in the time domain, and/or the like.
- a slot may consist of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain.
- OFDM Orthogonal Frequency Division Multiplexing
- SC-FDMA Single Carrier Frequency Division Multiple Access
- a slot may be a unit of time based on numerology.
- a slot may contain multiple mini-slots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be referred to as a subslot. A minislot may consist of fewer symbols than a slot.
- a PDSCH (or PUSCH) that is transmitted in time units larger than a minislot may be referred to as PDSCH (or PUSCH) mapping type A.
- PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (or PUSCH) mapping type B.
- Radio frames, subframes, slots, minislots and symbols all represent time units when transmitting signals. Radio frames, subframes, slots, minislots and symbols may be referred to by other corresponding designations.
- one subframe may be called a transmission time interval (TTI)
- TTI transmission time interval
- multiple consecutive subframes may be called a TTI
- one slot or one minislot may be called a TTI. That is, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, may be a period shorter than 1ms (eg, 1-13 symbols), or a period longer than 1ms may be Note that the unit representing the TTI may be called a slot, minislot, or the like instead of a subframe.
- TTI refers to, for example, the minimum scheduling time unit in wireless communication.
- a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis.
- radio resources frequency bandwidth, transmission power, etc. that can be used by each user terminal
- the TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, codewords, etc., or may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport block locks, codewords, etc. are actually mapped may be shorter than the TTI.
- one slot or one minislot is called a TTI
- one or more TTIs may be the minimum scheduling time unit.
- the number of slots (the number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
- a TTI with a time length of 1 ms may be called a normal TTI (TTI in LTE Rel.8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc.
- TTI that is shorter than a regular TTI may also be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, and so on.
- long TTI for example, normal TTI, subframe, etc.
- short TTI for example, shortened TTI, etc.
- a TTI having a TTI length greater than or equal to this value may be read as a replacement.
- a resource block 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 neurology, and may be 12, for example.
- the number of subcarriers included in an RB may be determined based on neumerology.
- the time domain of an RB may include one or more symbols and may be 1 slot, 1 minislot, 1 subframe, or 1 TTI long.
- One TTI, one subframe, etc. may each consist of one or more resource blocks.
- One or more RBs are physical resource blocks (Physical RB: PRB), sub-carrier groups (SCG), resource element groups (REG), PRB pairs, RB pairs, etc. may be called.
- PRB Physical resource blocks
- SCG sub-carrier groups
- REG resource element groups
- PRB pairs RB pairs, etc.
- a resource block may be composed of one or more resource elements (Resource Element: RE).
- RE resource elements
- 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.
- a Bandwidth Part (which may also be called a Bandwidth Part) represents a subset of contiguous common resource blocks (RBs) for a neumerology in a carrier. good.
- the common RB may be identified by an RB index based on the common reference point of the carrier.
- PRBs may be defined in a BWP and numbered within that BWP.
- BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP).
- BWP may include BWP for UL (UL BWP) and BWP for DL (DL BWP).
- One or more BWPs may be configured in one carrier for a UE.
- 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.
- BWP bitmap
- radio frames, subframes, slots, minislots and symbols described above are only examples.
- 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 Configurations such as the number of subcarriers and the number of symbols in a TTI, symbol length, cyclic prefix (CP) length, etc.
- CP cyclic prefix
- connection means any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being “connected” or “coupled.” Couplings or connections between elements may be physical, logical, or a combination thereof. For example, “connection” may be read as "access”.
- two elements are defined using at least one of one or more wires, cables and printed electrical connections and, as some non-limiting and non-exhaustive examples, in the radio frequency domain. , electromagnetic energy having wavelengths in the microwave and light (both visible and invisible) regions, and the like.
- the reference signal can also be abbreviated as Reference Signal (RS), and may also be called Pilot depending on the applicable standard.
- RS Reference Signal
- any reference to elements using the "first,” “second,” etc. designations used in this disclosure 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, references to first and second elements do not imply that only two elements may be employed therein or that the first element must precede the second element in any way.
- determining and “determining” used in this disclosure may encompass a wide variety of actions.
- “Judgement” and “determination” are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure), ascertaining as “judged” or “determined”, and the like.
- "judgment” and “determination” are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgment” or “decision” has been made.
- judgment and “decision” are considered to be “judgment” and “decision” by resolving, selecting, choosing, establishing, comparing, etc. can contain.
- judgment and “decision” may include considering that some action is “judgment” and “decision”.
- judgment (decision) may be read as “assuming”, “expecting”, “considering”, or the like.
- a and B are different may mean “A and B are different from each other.”
- the term may also mean that "A and B are different from C”.
- Terms such as “separate,” “coupled,” etc. may also be interpreted in the same manner as “different.”
- Radio communication system 20 NG-RAN 100 gNB 200UE 210 radio signal transmission/reception unit 220 amplifier unit 230 modulation/demodulation unit 240 control signal/reference signal processing unit 250 encoding/decoding unit 260 data transmission/reception unit 270 control unit 1001 processor 1002 memory 1003 storage 1004 communication device 1005 input device 1006 output device 1007 bus
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
(1.1)システム構成例
図1は、本実施形態に係る無線通信システム10の全体概略構成図である。無線通信システム10は、5G New Radio(NR)に従った無線通信システムであり、Next Generation-Radio Access Network 20(以下、NG-RAN20、及び複数の端末200(User Equipment 200、以下、UE200)を含む。
・FR2:24.25 GHz~52.6 GHz
FR1では、15, 30または60kHzのSub-Carrier Spacing(SCS)が用いられ、5~100MHzの帯域幅(BW)が用いられてもよい。FR2は、FR1よりも高周波数であり、60または120kHz(240kHzが含まれてもよい)のSCSが用いられ、50~400MHzの帯域幅(BW)が用いられてもよい。
無線通信システム10では、マルチキャスト/ブロードキャスト・サービス(MBS:Multicast and Broadcast Services)が提供されてよい。
・RRC connected UEのMBS groupに対して、グループ共通(group-common)PDCCH(Physical Downlink Control Channel)を用いてgroup-common PDSCHをスケジューリングする。
・RRC connected UEのMBS groupに対して、端末固有(UE-specific)PDCCHを用いてgroup-common PDSCHをスケジューリングする。
・RRC connected UEに対して、UE-specific PDCCHを用いてUE-specific PDSCHをスケジューリングする。
・PDSCH受信・復号に成功したUEは、ACKを送信する
・PDSCH受信・復号に失敗したUEは、NACKを送信する
・PUCCH(Physical Uplink Control Channel)リソース設定:マルチキャスト向けにPUCCH-Configを設定できる
・PUCCHリソース:UE間の共有/直交(shared/orthogonal)は、ネットワークの設定による
・HARQ-ACK CB (codebook):type-1及びtype-2(CB決定アルゴリズム(3GPP TS38.213において規定))をサポート
・多重化:ユニキャストまたはマルチキャストを適用可
・オプション2:NACKのみをフィードバック(NACK-only feedback)
・PDSCH受信・復号に成功したUEは、ACKを送信しない(応答を送信しない)
・PDSCH受信・復号に失敗したUEは、NACKを送信する
・所定のUEにおいて、PUCCHリソース設定は、ユニキャストまたはグループキャスト(マルチキャスト)によって別々に設定できる
なお、ACKは、positive acknowledgement(肯定応答)、NACKは、negative acknowledgement(否定応答)と呼ばれてもよい。HARQは、自動再送要求と呼ばれてもよい。
・RRCのみ
また、マルチキャスト/ブロードキャストPDSCHのSPS(Semi-persistent Scheduling)について、次のような内容が想定されている。
・UE能力(capability)として、複数のSPS group-common PDSCHが設定できる
・SPS group-common PDSCHに対するHARQフィードバックが可能
・少なくともgroup-common PDCCH(下り制御チャネル)によるアクティブ化/非アクティブ化(activation/deactivation)が可能
なお、非アクティブ化(deactivation)は、解放(release)などの他の同義の用語に読み替えられてもよい。例えば、アクティブ化は、起動、開始、トリガーなど、非アクティブ化は、さらに、終了、停止などに読み替えられてもよい。
次に、無線通信システム10の機能ブロック構成について説明する。具体的には、gNB100及びUE200の機能ブロック構成について説明する。
次に、無線通信システム10の動作について説明する。具体的には、MBSに関する下りチャネルのスケジューリング及び当該チャネルのHARQフィードバックに関する動作について説明する。
図5は、MBSにおけるPDCCH、PDSCH及びHARQ feedbackのシーケンス例を示す。図5に示すように、PDCCH(DCIを含んでよい)及びPDSCHは、ユニキャストまたはマルチキャスト(ブロードキャスト)によって送信されてよい。また、UE200は、当該チャネル(を介して受信したトランスポートブロック(TB))に対するHARQフィードバック(ACK/NACK)を送信してよい。
以下では、MBSにおいて、特定のフォーマットのDCI、具体的には、DCI format 1_0が用いられる場合におけるRB番号の取扱いに関する動作について説明する。
本動作例では、UE200は、RB番号がCFRの最低RB(lowest RB)が基準として決定されると想定してよい。なお、lowest RBとは、当該周波数帯域(例えば、CFRの周波数帯域)の中で最も周波数が低いRBと解釈されてよい(以下同)。また、基準とは、基準となるPRB indexを「PRB index = 0」とし、PDSCHのリソースが割り当てられてよい(以下同)。
本動作例では、UE200は、CORESET lowest RB≦CFRlowest RBであると想定してよい。図10は、動作例2に係るCORESETのリソースブロックとCFRのリソースブロックとの関係例を示す。
本動作例では、UE200は、CORESET lowest RBを基準としてMBS PDSCHのRBを想定してもよいが、CORESETのRB番号(RB index)が負の値によって示されると想定してよい。
本動作例では、UE200は、CORESET lowest RBを基準としてMBS PDSCHのRBを想定してもよいが、CFRまたはBWPの範囲において、CORESETを基準としたRB番号(RB index)を想定してよい。
上述した動作例は、MBSにおけるRRC_CONNECTED状態のUE200だけでなく、他のRRCの状態、具体的には、MBSにおけるRRC_IDLE及び/またはRRC_INACTIVE状態のUE200にも適用されてよい。
・48RB:11ビット
・96RB:13ビット
なお、CORESET0は、通常のCORESETと異なる特別なCORESETである。このような特定のCORESETは、SIB(System Information Block)1スケジューリング用にPDCCHを送信するCORESETと解釈されてよい。
また、PDSCH割り当て粒度(granularity)は、13ビットのRIV(Resource Indication Value)によって無駄なくカバーできるCFRサイズは、127RBまでと解釈されてもよい。このため、CORESET0サイズが96RBであり、CFRが127RBより大きい場合、1RBの割り当て粒度では割り当てられないRBが発生する可能性がある。
・RB割り当て粒度を複数RB単位にする(または、RB割り当て粒度/単位を大きくする)
上述した実施形態によれば、以下の作用効果が得られる。具体的には、UE200は、MBSにおいて、DCIがDCI format 1_0である場合、CFRlowest RBを基準としてPDSCHのRBを想定してよい。
以上、実施形態について説明したが、当該実施形態の記載に限定されるものではなく、種々の変形及び改良が可能であることは、当業者には自明である。
無線フレームは時間領域において1つまたは複数のフレームによって構成されてもよい。時間領域において1つまたは複数の各フレームはサブフレームと呼ばれてもよい。サブフレームはさらに時間領域において1つまたは複数のスロットによって構成されてもよい。サブフレームは、ニューメロロジー(numerology)に依存しない固定の時間長(例えば、1ms)であってもよい。
20 NG-RAN
100 gNB
200 UE
210 無線信号送受信部
220 アンプ部
230 変復調部
240 制御信号・参照信号処理部
250 符号化/復号部
260 データ送受信部
270 制御部
1001 プロセッサ
1002 メモリ
1003 ストレージ
1004 通信装置
1005 入力装置
1006 出力装置
1007 バス
Claims (6)
- 下りリンク制御情報を受信する受信部と、
複数の端末向けのデータ配信において、前記下りリンク制御情報が特定のフォーマットである場合、前記データ配信用の最も低いリソースブロックを基準として下りデータチャネルのリソースブロックを想定する制御部と
を備える端末。 - 下りリンク制御情報を受信する受信部と、
複数の端末向けのデータ配信において、前記下りリンク制御情報が特定のフォーマットである場合、制御リソースセットの最も低いリソースブロックが、前記データ配信用の最も低いリソースブロック以下であると想定する制御部と
を備える端末。 - 下りリンク制御情報を受信する受信部と、
複数の端末向けのデータ配信において、前記下りリンク制御情報が特定のフォーマットである場合、制御リソースセットの最も低いリソースブロックを基準として下りデータチャネルのリソースブロックを想定する制御部と
を備え、
前記制御部は、少なくとも前記制御リソースセットの最も低いリソースブロックが負の値によって示されると想定する端末。 - 下りリンク制御情報を受信する受信部と、
複数の端末向けのデータ配信において、前記下りリンク制御情報が特定のフォーマットである場合、制御リソースセットの最も低いリソースブロックを基準として下りデータチャネルのリソースブロックを想定する制御部と
を備え、
前記制御部は、前記データ配信用の周波数リソースまたは規定の帯域幅部分の範囲において、前記制御リソースセットを基準としたリソースブロックの表示を想定する端末。 - 下りリンク制御情報を受信するステップと、
複数の端末向けのデータ配信において、前記下りリンク制御情報が特定のフォーマットである場合、前記データ配信用の最も低いリソースブロックを基準として下りデータチャネルのリソースブロックを想定するステップと
を含む無線通信方法。 - 下りリンク制御情報を受信するステップと、
複数の端末向けのデータ配信において、前記下りリンク制御情報が特定のフォーマットである場合、制御リソースセットの最も低いリソースブロックが、前記データ配信用の最も低いリソースブロック以下であると想定するステップと
を含む無線通信方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2023539495A JPWO2023012982A1 (ja) | 2021-08-05 | 2021-08-05 | |
EP21952807.2A EP4383886A1 (en) | 2021-08-05 | 2021-08-05 | Terminal and wireless communication method |
PCT/JP2021/029181 WO2023012982A1 (ja) | 2021-08-05 | 2021-08-05 | 端末及び無線通信方法 |
CN202180100945.9A CN117716765A (zh) | 2021-08-05 | 2021-08-05 | 终端及无线通信方法 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/029181 WO2023012982A1 (ja) | 2021-08-05 | 2021-08-05 | 端末及び無線通信方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023012982A1 true WO2023012982A1 (ja) | 2023-02-09 |
Family
ID=85154474
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/029181 WO2023012982A1 (ja) | 2021-08-05 | 2021-08-05 | 端末及び無線通信方法 |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP4383886A1 (ja) |
JP (1) | JPWO2023012982A1 (ja) |
CN (1) | CN117716765A (ja) |
WO (1) | WO2023012982A1 (ja) |
-
2021
- 2021-08-05 EP EP21952807.2A patent/EP4383886A1/en active Pending
- 2021-08-05 CN CN202180100945.9A patent/CN117716765A/zh active Pending
- 2021-08-05 WO PCT/JP2021/029181 patent/WO2023012982A1/ja active Application Filing
- 2021-08-05 JP JP2023539495A patent/JPWO2023012982A1/ja active Pending
Non-Patent Citations (5)
Title |
---|
"3GPP TS 38.214" |
"R1-2102281, 3GPP TSG RAN WG1 Meeting #104bis-e", April 2021, 3GPP, article "Final Report of 3GPP TSG RAN WG1 #104-e v 1.0.0" |
"R1-2104151, 3GPP TSG RAN WG1 Meeting #105-e", May 2021, 3GPP, article "Final Report of 3GPP TSG RAN WG1 #104bis-e v 1.0.0" |
"RP-193248, 3GPP TSG RAN Meeting #86", December 2019, 3GPP, article "New Work Item on NR support of Multicast and Broadcast Services" |
NOKIA, NOKIA SHANGHAI BELL: "Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED UEs", 3GPP DRAFT; R1-2104550, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210519 - 20210527, 11 May 2021 (2021-05-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052006215 * |
Also Published As
Publication number | Publication date |
---|---|
JPWO2023012982A1 (ja) | 2023-02-09 |
EP4383886A1 (en) | 2024-06-12 |
CN117716765A (zh) | 2024-03-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022195713A1 (ja) | 端末及び無線通信方法 | |
WO2022234622A1 (ja) | 端末及び無線通信方法 | |
WO2022190389A1 (ja) | 端末及び無線通信方法 | |
WO2022195885A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2023012982A1 (ja) | 端末及び無線通信方法 | |
WO2022239083A1 (ja) | 端末及び無線通信方法 | |
WO2022234670A1 (ja) | 端末及び無線通信方法 | |
WO2022239086A1 (ja) | 端末及び無線通信方法 | |
WO2022195711A1 (ja) | 端末及び無線通信方法 | |
WO2022239084A1 (ja) | 端末及び無線通信方法 | |
WO2023022135A1 (ja) | 端末及び無線通信方法 | |
WO2023021855A1 (ja) | 端末及び無線通信方法 | |
WO2022269933A1 (ja) | 端末及び無線通信方法 | |
WO2022239085A1 (ja) | 端末及び無線通信方法 | |
US20240236975A1 (en) | Terminal and radio communication method | |
WO2022195884A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022195883A1 (ja) | 端末及び無線通信システム | |
WO2022239082A1 (ja) | 端末及び無線通信方法 | |
WO2022269910A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
US20240235745A1 (en) | Terminal and radio communication method | |
WO2023026941A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022201404A1 (ja) | 端末 | |
WO2022239078A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022244497A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022190377A1 (ja) | 端末、無線通信システム及び無線通信方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21952807 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023539495 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180100945.9 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021952807 Country of ref document: EP Effective date: 20240305 |