WO2022239086A1 - 端末及び無線通信方法 - Google Patents
端末及び無線通信方法 Download PDFInfo
- Publication number
- WO2022239086A1 WO2022239086A1 PCT/JP2021/017774 JP2021017774W WO2022239086A1 WO 2022239086 A1 WO2022239086 A1 WO 2022239086A1 JP 2021017774 W JP2021017774 W JP 2021017774W WO 2022239086 A1 WO2022239086 A1 WO 2022239086A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- feedback
- nack
- dci
- pdsch
- information
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 238000004891 communication Methods 0.000 title description 52
- 238000009826 distribution Methods 0.000 claims abstract description 19
- 230000008569 process Effects 0.000 claims description 11
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 94
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 94
- 230000005540 biological transmission Effects 0.000 description 33
- 238000012545 processing Methods 0.000 description 24
- 238000010586 diagram Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 11
- 230000011664 signaling Effects 0.000 description 7
- 230000004913 activation Effects 0.000 description 6
- 125000004122 cyclic group Chemical group 0.000 description 5
- 230000009849 deactivation Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- OHVLMTFVQDZYHP-UHFFFAOYSA-N 1-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)-2-[4-[2-[[3-(trifluoromethoxy)phenyl]methylamino]pyrimidin-5-yl]piperazin-1-yl]ethanone Chemical compound N1N=NC=2CN(CCC=21)C(CN1CCN(CC1)C=1C=NC(=NC=1)NCC1=CC(=CC=C1)OC(F)(F)F)=O OHVLMTFVQDZYHP-UHFFFAOYSA-N 0.000 description 3
- VZSRBBMJRBPUNF-UHFFFAOYSA-N 2-(2,3-dihydro-1H-inden-2-ylamino)-N-[3-oxo-3-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)propyl]pyrimidine-5-carboxamide Chemical compound C1C(CC2=CC=CC=C12)NC1=NC=C(C=N1)C(=O)NCCC(N1CC2=C(CC1)NN=N2)=O VZSRBBMJRBPUNF-UHFFFAOYSA-N 0.000 description 3
- AFCARXCZXQIEQB-UHFFFAOYSA-N N-[3-oxo-3-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)propyl]-2-[[3-(trifluoromethoxy)phenyl]methylamino]pyrimidine-5-carboxamide Chemical compound O=C(CCNC(=O)C=1C=NC(=NC=1)NCC1=CC(=CC=C1)OC(F)(F)F)N1CC2=C(CC1)NN=N2 AFCARXCZXQIEQB-UHFFFAOYSA-N 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000008054 signal transmission Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000001174 ascending effect 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
- 230000001934 delay Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- HMUNWXXNJPVALC-UHFFFAOYSA-N 1-[4-[2-(2,3-dihydro-1H-inden-2-ylamino)pyrimidin-5-yl]piperazin-1-yl]-2-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)ethanone Chemical compound C1C(CC2=CC=CC=C12)NC1=NC=C(C=N1)N1CCN(CC1)C(CN1CC2=C(CC1)NN=N2)=O HMUNWXXNJPVALC-UHFFFAOYSA-N 0.000 description 1
- LDXJRKWFNNFDSA-UHFFFAOYSA-N 2-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)-1-[4-[2-[[3-(trifluoromethoxy)phenyl]methylamino]pyrimidin-5-yl]piperazin-1-yl]ethanone Chemical compound C1CN(CC2=NNN=C21)CC(=O)N3CCN(CC3)C4=CN=C(N=C4)NCC5=CC(=CC=C5)OC(F)(F)F LDXJRKWFNNFDSA-UHFFFAOYSA-N 0.000 description 1
- WZFUQSJFWNHZHM-UHFFFAOYSA-N 2-[4-[2-(2,3-dihydro-1H-inden-2-ylamino)pyrimidin-5-yl]piperazin-1-yl]-1-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)ethanone Chemical compound C1C(CC2=CC=CC=C12)NC1=NC=C(C=N1)N1CCN(CC1)CC(=O)N1CC2=C(CC1)NN=N2 WZFUQSJFWNHZHM-UHFFFAOYSA-N 0.000 description 1
- IHCCLXNEEPMSIO-UHFFFAOYSA-N 2-[4-[2-(2,3-dihydro-1H-inden-2-ylamino)pyrimidin-5-yl]piperidin-1-yl]-1-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)ethanone Chemical compound C1C(CC2=CC=CC=C12)NC1=NC=C(C=N1)C1CCN(CC1)CC(=O)N1CC2=C(CC1)NN=N2 IHCCLXNEEPMSIO-UHFFFAOYSA-N 0.000 description 1
- YLZOPXRUQYQQID-UHFFFAOYSA-N 3-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)-1-[4-[2-[[3-(trifluoromethoxy)phenyl]methylamino]pyrimidin-5-yl]piperazin-1-yl]propan-1-one Chemical compound N1N=NC=2CN(CCC=21)CCC(=O)N1CCN(CC1)C=1C=NC(=NC=1)NCC1=CC(=CC=C1)OC(F)(F)F YLZOPXRUQYQQID-UHFFFAOYSA-N 0.000 description 1
- MKYBYDHXWVHEJW-UHFFFAOYSA-N N-[1-oxo-1-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)propan-2-yl]-2-[[3-(trifluoromethoxy)phenyl]methylamino]pyrimidine-5-carboxamide Chemical compound O=C(C(C)NC(=O)C=1C=NC(=NC=1)NCC1=CC(=CC=C1)OC(F)(F)F)N1CC2=C(CC1)NN=N2 MKYBYDHXWVHEJW-UHFFFAOYSA-N 0.000 description 1
- NIPNSKYNPDTRPC-UHFFFAOYSA-N N-[2-oxo-2-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)ethyl]-2-[[3-(trifluoromethoxy)phenyl]methylamino]pyrimidine-5-carboxamide Chemical compound O=C(CNC(=O)C=1C=NC(=NC=1)NCC1=CC(=CC=C1)OC(F)(F)F)N1CC2=C(CC1)NN=N2 NIPNSKYNPDTRPC-UHFFFAOYSA-N 0.000 description 1
- 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
- 238000004364 calculation method Methods 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000008859 change Effects 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
- 230000009467 reduction Effects 0.000 description 1
- 238000013468 resource allocation Methods 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1887—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
- H04L1/1614—Details of the supervisory signal using bitmaps
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1854—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1861—Physical mapping arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1864—ARQ related signaling
-
- 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/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
-
- 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/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
-
- 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/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0058—Allocation criteria
- H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L2001/0092—Error control systems characterised by the topology of the transmission link
- H04L2001/0093—Point-to-multipoint
-
- 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
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
- MBS for example, studies are underway on scheduling UE groups to be served and improving reliability (for example, HARQ (Hybrid Automatic repeat request) feedback to the radio base station (gNB)).
- HARQ Hybrid Automatic repeat request
- the UE selects an appropriate method, such as how to apply which method, for example, whether it is basically fixed to one method (semi-fixed), or whether to dynamically switch between both methods. There is a problem that cannot be selected.
- the following disclosure is made in view of this situation, and aims to provide a terminal and a wireless communication method that can properly use ACK/NACK feedback and NACK-only feedback properly.
- 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, based on information related to the priority related to the downlink control information and a control unit (control unit 270) that determines the automatic repeat request feedback method in the downlink channel (UE 200).
- 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, information on an uplink control channel related to the downlink control information is A terminal (UE 200) including a control unit (control unit 270) that determines an automatic repeat request feedback scheme based on the above.
- 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, the format of the downlink control information, the downlink control information and a control unit (control unit 270) that determines an automatic repeat request feedback scheme based on settings related to reception of the automatic repeat request or the automatic repeat request process.
- One aspect of the present disclosure is a transmitting unit (data transmitting/receiving unit 260) that transmits automatic repeat request feedback, and when different methods are applied to automatic repeat request feedback in downlink channels in data distribution for multiple terminals. , and a control unit (control unit 270) that does not assume multiplexing of the feedback information of the different schemes.
- One aspect of the present disclosure is a step of receiving downlink control information, and in data distribution for a plurality of terminals, based on information related to priority related to the downlink control information, feedback of automatic repeat request in a downlink channel. and determining a scheme.
- One aspect of the present disclosure is a step of receiving downlink control information, and in data distribution for a plurality of terminals, based on information on an uplink control channel related to the downlink control information, feedback of an automatic repeat request in a downlink channel determining the scheme of the wireless communication method.
- 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 correspondence between the Priority indicator and HARQ feedback according to Operation Example 1-1 and Operation Example 1-2.
- FIG. 7 is a diagram showing an example of a DCI field (item) according to operation example 2-0.
- FIG. 8 is a diagram showing an example of conditions under which multiplexing of HARQ feedback of different schemes is permitted according to operation example 4-2.
- FIG. 9 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 and may use an SCS of 60 or 120 kHz (240 kHz may be included) and a bandwidth (BW) of 50-400 MHz.
- 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. Also, the radio communication system 10 may support a frequency band between FR1 and FR2.
- 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, BWP (Bandwidth part), subchannel, common frequency resource, and the like.
- 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
- 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 where all PDSCHs are scheduled by DCI (eg DCI 1_0, DCI 1_1 or DCI 1_2).
- SPS may be interpreted as a mechanism by which PDSCH transmissions are scheduled by higher layer signaling such as RRC messages.
- 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. 9 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 downlink control information
- control signal/reference signal processing unit 240 may receive, in RRC, a message indicating activation or deactivation of a function whose activation or deactivation of HARQ feedback is indicated by DCI.
- 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.
- the data transmission/reception unit 260 may constitute a transmission unit.
- 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 performs control corresponding to scheduling of downlink data channels that are 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 assumes that the SPS of the downlink data channel (PDSCH) for the terminal group, that is, the semi-fixed scheduling activation/deactivation is applied on a terminal group basis. You can
- control unit 270 may determine a HARQ (automatic repeat request) feedback method (scheme) in the downlink channel in data distribution for a plurality of terminals, that is, in MBS. Specifically, control section 270 determines the HARQ feedback scheme in PDSCH (specifically, MBS PDSCH) based on a priority field included in DCI (downlink control information) in MBS. you can HARQ feedback scheme may mean ACK/NACK feedback or NACK-only feedback.
- HARQ feedback scheme may mean ACK/NACK feedback or NACK-only feedback.
- Control unit 270 controls ACK/NACK feedback or NACK-only for MBS PDSCH based on the content of information (which may be read as a field or a signal) related to priority among the fields included in the DCI. feedback may be applied.
- DCI is not particularly limited as long as it is a scheduling DCI, but specifically, it may be a DCI (or DCI format) that schedules MBS PDSCH. Any field that indicates For example, the field may be called a Priority indicator field, or may be another field for indicating Priority. Alternatively, it may be predetermined information related to DCI instead of a field in DCI.
- the control unit 270 may select ACK/NACK feedback when the priority is high, and select NACK-only feedback when the priority is low. Alternatively, the control unit 270 may assume ACK/NACK feedback or NACK-only feedback for each value of the Priority indicator field. It should be noted that control section 270 may assume that ACK/NACK feedback or NACK-only feedback is specified by DCI or RRC parameters when DCI does not include a Priority indicator field.
- control unit 270 may determine the HARQ feedback method in the downlink channel based on information related to the PUCCH (uplink control channel) included in the DCI in the MBS.
- control section 270 supports MBS PDSCH reception based on fields (signals) related to slot/resource determination to which PUCCH is assigned, among DCI (or DCI format) fields for scheduling MBS PDSCH.
- ACK/NACK feedback or NACK-only feedback may be determined.
- control unit 270 may determine the HARQ feedback method in the downlink channel based on the DCI format, DCI reception settings, or the HARQ process in the MBS.
- control unit 270 may assume different DCI formats for ACK/NACK feedback and NACK-only feedback with respect to HARQ feedback.
- the settings related to DCI reception include, for example, RNTI (Radio Network Temporary Identifier) that scrambles DCI CRC (Cyclic Redundancy Checksum), control resource sets (CORESET: control resource sets) or search space for transmitting DCI, DCI may include PDSCH resources and the like notified by.
- RNTI Radio Network Temporary Identifier
- CRC Cyclic Redundancy Checksum
- CORESET control resource sets
- search space for transmitting DCI DCI may include PDSCH resources and the like notified by.
- CORESET may be interpreted as a set of physical resources (specifically, specific areas on the DL resource grid) and parameters used to transmit PDCCH (including DCI). Note that the settings related to DCI reception may include other settings necessary for receiving DCI.
- a HARQ process may typically be a HARQ process number, but other information (e.g. Redundancy Version (RV), codebook ( CB) number, etc.).
- control unit 270 may perform operations related to multiplexing of the corresponding HARQ-ACK bits and transmit them.
- control unit 270 does not need to assume that HARQ-ACK bits of different schemes are multiplexed on the same channel.
- HARQ-ACK bits may be multiplexed on the same channel to perform HARQ feedback.
- control section 270 when a plurality of TBs are received and HARQ feedback schemes for each of the TBs are different, control section 270 performs HARQ processing based on predetermined DCI information if predetermined conditions are satisfied for HARQ feedback of different schemes.
- a feedback method may be determined, HARQ-ACK bits corresponding to the plurality of TBs may be multiplexed on the same channel, and HARQ feedback may be performed.
- control section 270 drops the feedback of one of the schemes if a predetermined condition is satisfied for the different schemes of HARQ feedback. , may send only the feedback of the other.
- the gNB 100 can execute the above-described downlink channel scheduling, HARQ control, and the like.
- 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.
- HARQ feedback ⁇ ACK/NACK feedback, NACK-only feedback ⁇ corresponding to MBS PDSCH reception is specified ( may be read as determination, selection, etc.).
- the UE 200 may operate according to operation examples 1-0 to 1-6.
- the signal related to priority may be the priority indicator field in DCI, or may be another field related to the priority indicator field or another related to the priority instruction.
- field may be the priority of HARQ feedback or PUCCH (hereinafter referred to as HARQ feedback/PUCCH) corresponding to the scheduled PDSCH.
- HARQ feedback ⁇ ACK/NACK feedback, NACK-only feedback corresponding to MBS PDSCH reception by at least one of the following operation examples 1-1 to 1-4 ⁇ may be specified.
- HARQ feedback ⁇ ACK/NACK feedback, NACK-only feedback ⁇ is set for each priority indicator value (Operation example 1-4): For each priority indicator value ( at least one of 0, 1), it is set whether the HARQ feedback scheme is indicated by the DCI.
- a field defined for indication of the HARQ feedback scheme (e.g. 1 bit) ⁇ Fields already present in DCI format scrambled by C (Cell)-RNTI ⁇ DCI format ⁇ RNTI scrambling CRC of DCI - CORESET/search space to transmit DCI - PDSCH resource (time/frequency/code/space) signaled by DCI ⁇ PUCCH resources (time/frequency/code/space) signaled by DCI (Operation example 1-5): If the DCI that schedules the MBS PDSCH does not include a priority indicator field, ⁇ ACK/NACK feedback, NACK-only feedback ⁇ set by the RRC parameter may be applied.
- RRC parameter If ⁇ ACK/NACK feedback, NACK-only feedback ⁇ is not set by , a predetermined value, specifically, a method defined by default may be used (for example, ACK/NACK feedback or NACK-only feedback).
- NACK-only feedback ⁇ may be determined If the Priority is not set by the RRC parameters, it may be a predetermined value (eg, ACK/NACK feedback or NACK-only feedback).
- the HARQ feedback method can be appropriately determined according to Priority.
- ⁇ ACK/NACK feedback, NACK-only feedback ⁇ may be determined based on the priority of HARQ feedback/PUCCH set or predefined by the RRC parameter.
- the UE 200 may operate according to operation examples 1'-1 and 1'-2.
- Priority may be set for each predetermined parameter For example, priority may be set for each CORESET index, CORESET pool index, and SS (Synchronization Signal) index.
- Priority may be defined to be determined based on a predetermined rule In this case, Priority does not have to be explicitly set. For example, rules based on CORESET index, CORESET pool index, SS index. Specifically, it may be a CORESET index for Multicast or a CORESET index for Unicast. Alternatively, both indices may be used.
- it may be a CORESET pool index for Multicast or a CORESET pool index for Unicast. Alternatively, both indices may be used.
- Priority may be a layer 1 (L1) priority or a layer 2 (L2) priority (logical channel priority).
- HARQ feedback ⁇ ACK/NACK feedback, NACK-only feedback corresponding to MBS PDSCH reception, based on a signal related to PUCCH slot/resource determination among fields in DCI or DCI format that schedules MBS PDSCH. ⁇ may be specified.
- the UE 200 may operate according to operation examples 2-0 to 2-2.
- the signal related to PUCCH slot / resource determination may be at least one of the specific fields of DCI, or another field related to the PUCCH slot / resource determination instruction
- FIG. 7 shows an example of a DCI field (item) according to Operation Example 2-0.
- the UE 200 may determine the HARQ feedback scheme for MBS PDSCH reception based on the contents of at least one field of PUCCH resource indicator or PDSCH-to-HARQ_feedback timing indicator.
- PUCCH resource indicator and PDSCH-to-HARQ_feedback timing indicator are specified in 3GPP TS38.213.
- slot to which the PUCCH is assigned is a predetermined slot (or has a slot offset), it may be a predetermined value (eg, ACK/NACK feedback or NACK-only feedback). slots may be set in advance, or may be set each time by DCI, RRC, or the like.
- the resource to which PUCCH is assigned is a predetermined resource, it may be a predetermined value (eg, ACK/NACK feedback or NACK-only feedback). Note that the predetermined resource is set in advance. or may be set on a case-by-case basis by DCI, RRC, or the like.
- a predetermined value is associated with a PUCCH resource, a PUCCH resource set, or a PUCCH format (PF), and a PUCCH resource is specified (by DCI, RRC parameters or CCE (Control channel element) index) or the PUCCH resource set is determined. , may be applied.
- the HARQ feedback method can be flexibly switched according to the situation.
- HARQ feedback corresponding to MBS PDSCH reception is based on at least one of DCI format, DCI reception settings, or HARQ process.
- ⁇ ACK/NACK feedback, NACK-only feedback ⁇ may be specified.
- the UE 200 may operate according to operation examples 3-1 to 3-5.
- DCI format ACK/NACK feedback and NACK-only feedback may be specified by different DCI formats. That is, ACK/NACK feedback and NACK-only feedback may be specified by separate DCI formats. In this case, the DCI format used may not be particularly limited, but DCI 1_0, DCI 1_1 or DCI 1_2, or a new DCI format may be used.
- UE 200 performs ACK/NACK feedback for MBS PDSCHs scheduled according to a predetermined DCI format, and performs NACK-only feedback for MBS PDSCHs scheduled according to a DCI format other than the predetermined DCI format.
- the above formats may be distinguished by the payload size, or may be distinguished by the format indicator.
- RNTI for scrambling DCI CRC G1-RNTI is defined as group-common RNTI and may be used for scheduling of Group-common PDSCH with ACK/NACK feedback. Also, G2-RNTI is defined as a group-common RNTI and may be used for scheduling of Group-common PDSCH with NACK-only feedback.
- the HARQ feedback method depends on the reliability requirement for traffic, but according to this operation example, the HARQ feedback method can be selected based on parameters that can differ for each traffic. It becomes possible.
- the UE 200 may operate according to operation examples 4-1 to 4-5.
- ⁇ (Operation example 4-2) When multiple TBs are received and the HARQ feedback method for each of the TBs is different (for example, ACK/NACK feedback is specified for some of the multiple TBs, and the rest NACK-only feedback is specified), if a specific condition for HARQ feedback of different schemes is satisfied, HARQ-ACK bits of different schemes are multiplexed on the same channel as a predetermined value, and HARQ feedback is performed. In other words, if the predetermined value indicates ACK/NACK feedback, all multiplexed bits may be generated as ACK/NACK feedback. Note that the predetermined value referred to here may be ACK/NACK feedback or NACK-only feedback. Also, the PUCCH resource/resource set may be determined by a parameter associated with the predetermined value.
- FIG. 8 shows an example of conditions under which multiplexing of HARQ feedback of different methods according to operation example 4-2 is permitted.
- If a specific condition for different HARQ feedback methods is satisfied may mean that at least one of the conditions 1 to 6 shown in FIG. 8 is satisfied. However, it may be based on a combination of multiple conditions.
- the predetermined DCI may be the last DCI in the time and frequency domains among DCIs corresponding to multiplexed bits.
- the last DCI may mean the last DCI format defined in 3GPP TS38.213 or the like. For example, it may be a DCI determined by the following, and the parameter names may be different.
- detected DCI formats are first indexed in an ascending order across serving cells indexes for a same PDCCH monitoring occasion and are then indexed in an ascending order across PDCCH monitoring occasion indexes.
- the PUCCH resource/resource set may be determined by parameters associated with the HARQ feedback scheme for a given DCI.
- ⁇ (Operation example 4-4) When multiple TBs are received and the HARQ feedback method for each of the TBs is different (for example, ACK/NACK feedback is specified for some of the multiple TBs, and the rest NACK-only feedback is specified), if a predetermined condition is met for HARQ feedback of different schemes, feedback of either scheme may be dropped and only feedback of the other scheme may be sent. For example, NACK Bits associated with -only feedback may be dropped. Alternatively, bits related to ACK/NACK feedback may be dropped.
- At least two of operation examples 4-1 to 4-4 may be switched by a predetermined method. It may be switched by an instruction from a CE (Control Element).
- this operation example may be applied in combination with the other operation examples described above.
- operation examples 1 to 3 the operation when multiplexing and/or priority processing for PUCCH resources according to different HARQ feedback schemes is required becomes clear, and the UE 200 can appropriately perform HARQ feedback. .
- the UE 200 can determine the HARQ feedback method in the MBS PDSCH based on the priority field included in the DCI in the MBS. Also, the UE 200 may determine the HARQ feedback scheme in the downlink channel based on a field related to PUCCH (uplink control channel) included in the DCI in the MBS.
- PUCCH uplink control channel
- the UE 200 can also determine the HARQ feedback method in the downlink channel based on the DCI format, DCI reception settings, or the HARQ process in the MBS. Also, it can be assumed that UE 200 applies different schemes to HARQ feedback in the downlink channel and multiplexes the feedback results when a specific condition is satisfied in MBS.
- UE 200 can properly use ACK/NACK feedback and NACK-only feedback properly.
- 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). .
- 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 is implemented by any combination of at least one of hardware and software.
- the method of implementing each functional block is not particularly limited. That is, 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. 9 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, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, 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フィードバックに関する動作について説明する。
本動作例では、MBS PDSCHをスケジュールするDCIまたはDCIフォーマットにおけるフィールドのうち、Priorityに係る信号に基づいて、MBS PDSCH受信に対応するHARQ feedback = {ACK/NACK feedback, NACK-only feedback}が指定(決定、選択などと読み替えてもよい)されてよい。
priority indicator fieldまたはPriorityの指示に係る別のフィールドによって指示されるPriorityは、スケジューリングされたPDSCHに対応するHARQ feedbackまたはPUCCH(以下、HARQ feedback/PUCCH)のPriorityであってもよい。
・(動作例1-2): Priorityが低い場合(e.g. priority indicator = 0)、NACK-only feedbackとする
図6は、動作例1-1及び動作例1-2に係るPriority indicatorとHARQフィードバックとの対応例を示す。図6に示すように、priority indicator = 1の場合、ACK/NACK feedbackとし、priority indicator = 0の場合、NACK-only feedbackとしてよい。
・(動作例1-4):priority indicatorの値毎に(少なくとも0, 1の何れかについて)、DCIによってHARQフィードバック方式が指示されるか否かが設定される
当該指示は、次の何れかによって行われてよい。
・C (Cell)-RNTIによってスクランブリングされたDCIフォーマットに既に存在するフィールド
・DCIフォーマット
・DCIのCRCをスクランブリングするRNTI
・DCIを送信するCORESET/サーチスペース
・DCIによって通知されるPDSCHリソース(time/frequency/code/space)
・DCIによって通知されるPUCCHリソース(time/frequency/code/space)
・(動作例1-5):MBS PDSCHをスケジュールするDCIにpriority indicator fieldが含まれない場合、RRCパラメータによって設定された{ACK/NACK feedback, NACK-only feedback}が適用されてもよい
RRCパラメータによって{ACK/NACK feedback, NACK-only feedback}が設定されない場合、所定値、具体的には、デフォルトで規定された方式としてもよい(例えば、ACK/NACK feedbackまたはNACK-only feedback)。
RRCパラメータによって当該Priorityが設定されない場合、所定値としてもよい(例えば、ACK/NACK feedbackまたはNACK-only feedback)。
本動作例では、RRCパラメータによって設定、または予め定義されたHARQ feedback/PUCCHのPriorityに基づいて、{ACK/NACK feedback, NACK-only feedback}が決定されてもよい。
例えば、CORESET index、CORESET pool index、SS (Synchronization Signal) index毎にPriorityが設定されてよい。
この場合、Priorityは、明示的に設定されなくてもよいことを意味する。例えば、CORESET index、CORESET pool index、SS indexに基づくルールでもよい。具体的には、Multicast用のCORESET indexでもよいし、Unicast用のCORESET indexでもよい。或いは、両方のindexでもよい。
本動作例では、MBS PDSCHをスケジュールするDCIまたはDCIフォーマットにおけるフィールドのうち、PUCCHスロット/リソース決定に係る信号に基づいて、MBS PDSCH受信に対応するHARQ feedback = {ACK/NACK feedback, NACK-only feedback}が指定されてもよい。
図7は、動作例2-0に係るDCIフィールド(item)の例を示す。図7に示すように、UE200は、PUCCH resource indicatorまたはPDSCH-to-HARQ_feedback timing indicatorの少なくとも何れかのフィールドの内容に基づいて、MBS PDSCH受信に対応するHARQフィードバックの方式を決定してよい。
なお、所定のスロットは、予め設定されていてもよいし、DCIまたはRRCなどによってその都度設定されてもよい。
なお、所定のリソースは、予め設定されていてもよいし、DCIまたはRRCなどによってその都度設定されてもよい。
本動作例では、MBS PDSCHをスケジュールするDCI受信に係る信号または情報のうち、DCIのフォーマット、DCIの受信に関する設定、またはHARQのプロセスの少なくとも何れかに基づいて、MBS PDSCH受信に対応するHARQ feedback = {ACK/NACK feedback, NACK-only feedback}が指定されてもよい。
ACK/NACK feedbackとNACK-only feedbackとは、異なるDCIフォーマットによって指定されてよい。つまり、ACK/NACK feedbackとNACK-only feedbackとは、別々のDCIフォーマットによって指定されてよい。この場合、用いられるDCIフォーマットは、特に限定されなくてもよいが、DCI 1_0、DCI 1_1またはDCI 1_2、或いは新規なDCIフォーマットが用いられてもよい。
group-common RNTIとして、G1-RNTIが定義され、Group-common PDSCH with ACK/NACK feedbackのスケジューリングに使用されてよい。また、group-common RNTIとして、G2-RNTIが定義され、Group-common PDSCH with NACK-only feedbackのスケジューリングに使用されてよい。
・(動作例3-4):DCIによって通知されるPDSCHリソース(time/frequency/code/space)
・(動作例3-5):HARQ process number
なお、上述した各動作例におけるHARQフィードバック方式との対応付けは、予め定義されてもよいし、RRCなどの上位レイヤのパラメータによって設定されてもよい。
本動作例では、MBS PDSCH受信に対応する2種類のHARQフィードバック方式(ACK/NACK feedback, NACK-only feedback)に係るHARQ-ACKビット(フィードバック結果)が多重されてよい。
例えば、UE200は、同じスロット(またはサブスロット)において異なる方式のHARQ-ACKビットに係るフィードバックを実行する設定/指示を想定しなくてよい。また、UE200は、異なる方式のHARQ-ACKビットに係る、設定/指示されたフィードバック用のリソースが重複(overlap)することを想定しなくてよい。
つまり、所定値がACK/NACK feedbackを示している場合、多重するビットは、全てACK/NACK feedbackとして生成されてよい。なお、ここでいう所定値は、ACK/NACK feedbackまたはNACK-only feedbackであってもよい。また、PUCCHリソース/リソースセットは、当該所定値に関連付けられたパラメータによって決定されてもよい。
つまり、所定のDCIに係るHARQフィードバック方式がACK/NACK feedbackの場合、多重するビットは、全てACK/NACK feedbackとして生成されてよい。
また、PUCCHリソース/リソースセットは、所定のDCIに係るHARQフィードバック方式に関連付けられたパラメータによって決定されてよい。
例えば、NACK-only feedbackに係るビットがドロップされてもよい。或いは、ACK/NACK feedbackに係るビットがドロップされてもよい。
例えば、RRCパラメータによる設定によって切り替えられてもよいし、DCIまたはMAC-CE(Control Element)による指示によって切り替えられてもよい。
上述した実施形態によれば、以下の作用効果が得られる。具体的には、UE200は、MBSにおいて、DCIに含まれる優先度に関するフィールドに基づいて、MBS PDSCHにおけるHARQのフィードバックの方式を決定できる。また、UE200は、MBSにおいて、DCIに含まれるPUCCH(上り制御チャネル)に関するフィールドに基づいて、下りチャネルにおけるHARQのフィードバックの方式を決定してもよい。
以上、実施形態について説明したが、当該実施形態の記載に限定されるものではなく、種々の変形及び改良が可能であることは、当業者には自明である。
無線フレームは時間領域において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 |
---|---|---|---|
JP2023520605A JPWO2022239086A1 (ja) | 2021-05-10 | 2021-05-10 | |
PCT/JP2021/017774 WO2022239086A1 (ja) | 2021-05-10 | 2021-05-10 | 端末及び無線通信方法 |
EP21941820.9A EP4340442A1 (en) | 2021-05-10 | 2021-05-10 | Terminal and wireless communication method |
CN202180097603.6A CN117242820A (zh) | 2021-05-10 | 2021-05-10 | 终端及无线通信方法 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2021/017774 WO2022239086A1 (ja) | 2021-05-10 | 2021-05-10 | 端末及び無線通信方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022239086A1 true WO2022239086A1 (ja) | 2022-11-17 |
Family
ID=84028460
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2021/017774 WO2022239086A1 (ja) | 2021-05-10 | 2021-05-10 | 端末及び無線通信方法 |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP4340442A1 (ja) |
JP (1) | JPWO2022239086A1 (ja) |
CN (1) | CN117242820A (ja) |
WO (1) | WO2022239086A1 (ja) |
-
2021
- 2021-05-10 WO PCT/JP2021/017774 patent/WO2022239086A1/ja active Application Filing
- 2021-05-10 JP JP2023520605A patent/JPWO2022239086A1/ja active Pending
- 2021-05-10 CN CN202180097603.6A patent/CN117242820A/zh active Pending
- 2021-05-10 EP EP21941820.9A patent/EP4340442A1/en active Pending
Non-Patent Citations (6)
Title |
---|
"New Work Item on NR support of Multicast and Broadcast Services", RP-193248, 3GPP TSG RAN MEETING #86, December 2019 (2019-12-01) |
3GPP TS 38.213 |
3GPP TS38.213 |
CATT, CBN: "Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS", 3GPP DRAFT; R1-2102610, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 7 April 2021 (2021-04-07), XP052177256 * |
INTEL CORPORATION: "Mechanisms to Improve Reliability of NR MBS for RRC_CONNECTED UEs", 3GPP DRAFT; R1-2103051, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 7 April 2021 (2021-04-07), XP052177859 * |
ZTE: "Discussion on mechanisms to Improve Reliability for RRC_CONNECTED UEs", 3GPP DRAFT; R1-2100107, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 19 January 2021 (2021-01-19), XP051970812 * |
Also Published As
Publication number | Publication date |
---|---|
CN117242820A (zh) | 2023-12-15 |
EP4340442A1 (en) | 2024-03-20 |
JPWO2022239086A1 (ja) | 2022-11-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022234622A1 (ja) | 端末及び無線通信方法 | |
WO2022195713A1 (ja) | 端末及び無線通信方法 | |
WO2022195885A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022190389A1 (ja) | 端末及び無線通信方法 | |
WO2022239086A1 (ja) | 端末及び無線通信方法 | |
WO2022239084A1 (ja) | 端末及び無線通信方法 | |
WO2022195711A1 (ja) | 端末及び無線通信方法 | |
WO2022239085A1 (ja) | 端末及び無線通信方法 | |
WO2023021855A1 (ja) | 端末及び無線通信方法 | |
WO2023022135A1 (ja) | 端末及び無線通信方法 | |
WO2023012982A1 (ja) | 端末及び無線通信方法 | |
WO2022234670A1 (ja) | 端末及び無線通信方法 | |
WO2022239083A1 (ja) | 端末及び無線通信方法 | |
WO2022195884A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022195883A1 (ja) | 端末及び無線通信システム | |
WO2022269933A1 (ja) | 端末及び無線通信方法 | |
WO2022249749A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022244497A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2023026968A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2023026941A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022269910A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022239078A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2023026975A1 (ja) | 端末、無線通信システム及び無線通信方法 | |
WO2022215272A1 (ja) | 端末、基地局、無線通信システム及び無線通信方法 | |
US20240235745A1 (en) | Terminal and radio communication method |
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: 21941820 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2023520605 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180097603.6 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021941820 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021941820 Country of ref document: EP Effective date: 20231211 |