WO2022137304A1 - 端末、無線通信方法及び基地局 - Google Patents
端末、無線通信方法及び基地局 Download PDFInfo
- Publication number
- WO2022137304A1 WO2022137304A1 PCT/JP2020/047766 JP2020047766W WO2022137304A1 WO 2022137304 A1 WO2022137304 A1 WO 2022137304A1 JP 2020047766 W JP2020047766 W JP 2020047766W WO 2022137304 A1 WO2022137304 A1 WO 2022137304A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- pucch
- ack
- harq
- channel
- transmission
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims description 60
- 238000000034 method Methods 0.000 title claims description 47
- 230000005540 biological transmission Effects 0.000 claims abstract description 148
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims description 3
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 52
- 230000006870 function Effects 0.000 description 20
- 238000005259 measurement Methods 0.000 description 18
- 238000013507 mapping Methods 0.000 description 17
- 230000011664 signaling Effects 0.000 description 17
- 238000010586 diagram Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 11
- 230000009977 dual effect Effects 0.000 description 10
- 125000004122 cyclic group Chemical group 0.000 description 9
- 238000001914 filtration Methods 0.000 description 9
- 238000010295 mobile communication Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 5
- 238000007726 management method Methods 0.000 description 5
- 230000003321 amplification Effects 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 238000012790 confirmation Methods 0.000 description 4
- 238000012937 correction Methods 0.000 description 4
- 238000003199 nucleic acid amplification method Methods 0.000 description 4
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000012384 transportation and delivery Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 238000002716 delivery method Methods 0.000 description 2
- 238000009795 derivation Methods 0.000 description 2
- 238000009792 diffusion process Methods 0.000 description 2
- 230000007274 generation of a signal involved in cell-cell signaling Effects 0.000 description 2
- 238000011835 investigation Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 241001633942 Dais Species 0.000 description 1
- 108700026140 MAC combination Proteins 0.000 description 1
- 101150071746 Pbsn gene Proteins 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000006249 magnetic particle Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/04—Error control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
Definitions
- This disclosure relates to terminals, wireless communication methods and base stations in next-generation mobile communication systems.
- LTE Long Term Evolution
- UMTS Universal Mobile Telecommunications System
- 3GPP Rel.10-14 LTE-Advanced (3GPP Rel.10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).
- a successor system to LTE for example, 5th generation mobile communication system (5G), 5G + (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel.15 or later, etc.
- 5G 5th generation mobile communication system
- 6G 6th generation mobile communication system
- NR New Radio
- a future wireless communication system for example, NR
- a plurality of user terminals (user terminal, User Equipment (UE)) communicate in an ultra-high density and high traffic environment.
- UE User Equipment
- HARQ-ACK hybrid automatic repeat reQuest acknowledgment
- one of the purposes of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately process HARQ-ACK for multicast downlink data.
- the physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgment (HARQ-ACK) information to the multicast physical downlink shared channel (PDSCH) is up in the time domain.
- PUCCH physical uplink control channel
- HARQ-ACK hybrid automatic repeat reQuest acknowledgment
- PDSCH physical downlink shared channel
- HARQ-ACK for multicast downlink data can be appropriately processed.
- FIG. 1 is a diagram showing an example of the PTM transmission method 1.
- FIG. 2 is a diagram showing an example of the PTM transmission method 2.
- FIG. 3 is a diagram showing an example of a collision between PUCCH and PUSCH corresponding to the multicast PDSCH according to the first embodiment.
- FIG. 4 is a diagram showing an example of a collision between a PUCCH and a UL channel corresponding to the multicast PDSCH according to the second embodiment.
- 5A to 5C are diagrams showing an example of a collision between the PUCCH corresponding to the unicast PDSCH and the PUCCH corresponding to the multicast PDSCH according to the third embodiment.
- FIG. 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
- FIG. 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
- FIG. 7 is a diagram showing an example of the configuration of the base station according to the embodiment.
- FIG. 8 is a diagram showing an example of the configuration of the user terminal according to the embodiment.
- FIG. 9 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment.
- PUCCH format In future wireless communication systems (eg, Rel.15 and later, 5G, NR, etc.), configurations (formats, PUCCH formats (PFs)) for uplink control channels (eg, PUCCH) used to transmit uplink control information (UCI). ) Etc.) are being considered.
- PFs PUCCH formats
- UCI uplink control information
- Etc. Etc.
- Rel. It is being considered to support 5 types of PF0 to 4 in 15 NR.
- the names of the PFs shown below are merely examples, and different names may be used.
- PF0 and 1 are PFs used for transmitting UCI of 2 bits or less (up to 2 bits).
- UCI is at least one of delivery confirmation information (also referred to as Hybrid Automatic Repeat reQuest-Acknowledgement (HARQ-ACK), acknowledgment (ACK) or negative-acknowledgement (NACK), etc.) and scheduling request (SR). May be.
- delivery confirmation information also referred to as Hybrid Automatic Repeat reQuest-Acknowledgement (HARQ-ACK), acknowledgment (ACK) or negative-acknowledgement (NACK), etc.
- SR scheduling request
- PF0 can be assigned to 1 or 2 symbols, it is also called a short PUCCH or a sequence-based short PUCCH or the like.
- PF1 can be assigned to 4-14 symbols, it is also called a long PUCCH or the like.
- PF0 uses a cyclic shift (cyclic shift (CS) index, a cyclic shift based on at least one of a UCI value, a slot number, and a symbol number, and a cyclic shift (base sequence).
- the sequence obtained by the shift may be transmitted.
- multiple user terminals are code-division multiple access (PRB) within the same physical resource block (PRB) due to block diffusion of the time domain using at least one of CS and time domain (TD) -orthogonal cover code (OCC).
- CDM code-division multiple access
- PF2-4 is used for transmission of UCI (for example, Channel State Information (CSI)) exceeding 2 bits (more than 2 bits) or at least one of CSI, HARQ-ACK and SR).
- UCI for example, Channel State Information (CSI)
- CSI Channel State Information
- PF to be Since PF2 can be assigned to 1 or 2 symbols, it is also called a short PUCCH or the like. On the other hand, since PF3 and PF4 can be assigned to 4-14 symbols, they are also called long PUCCH or the like.
- PF4 a plurality of user terminals may be CDMed by using the block diffusion (frequency domain (FD) -OCC) before DFT.
- FD frequency domain
- Intra-slot frequency hopping may be applied to PF1, PF3, and PF4. Assuming that the length of PUCCH is N symb , the length before frequency hopping (first hop) may be floor (N symb / 2), and the length after frequency hopping (second hop) is ceil (N). It may be symb / 2).
- the waveforms of PF0, PF1 and PF2 may be Cyclic Prefix (CP) -Orthogonal Frequency Division Multiplexing (OFDM).
- the waveforms of PF3 and PF4 may be Discrete Fourier Transform (DFT) -spread (s) -OFDM.
- DFT Discrete Fourier Transform
- Allocation of resources (for example, PUCCH resources) used for transmission of the uplink control channel is performed using higher layer signaling and / or downlink control information (DCI).
- the upper layer signaling is, for example, at least one of RRC (Radio Resource Control) signaling, system information (for example, RMSI: Remaining Minimum System Information, OSI: Other System Information, MIB: Master Information Block, SIB: System Information Block).
- RRC Radio Resource Control
- system information for example, RMSI: Remaining Minimum System Information
- OSI System Information
- MIB Master Information Block
- SIB System Information Block
- PBCH Physical Broadcast Channel
- the number of symbols assigned to PUCCH (which may be referred to as PUCCH assigned symbols, PUCCH symbols, etc.) can be determined by slot-specific, cell-specific, user terminal-specific, or a combination thereof. Since it is expected that the communication distance (coverage) increases as the number of PUCCH symbols increases, it is assumed that the number of symbols increases as the user terminal is farther from the base station (for example, eNB, gNB).
- the user terminal In NR, the user terminal (UE: User Equipment) has delivery confirmation information (Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK), ACKnowledge / Non-ACK) for the downlink shared channel (also referred to as Physical Downlink Shared Channel (PDSCH)).
- delivery confirmation information Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK), ACKnowledge / Non-ACK
- PDSCH Physical Downlink Shared Channel
- a mechanism for feeding back also referred to as ACK / NACK
- HARQ-ACK information also referred to as report or transmission
- the value of the predetermined field in the DCI indicates the feedback timing of HARQ-ACK for the PDSCH.
- the value of the predetermined field may be mapped to the value of k.
- the predetermined field is referred to as, for example, a PDSCH-HARQ feedback timing instruction (PDSCH-to-HARQ_feedback timing indicator) field or the like.
- the PUCCH resource to be used for the feedback of HARQ-ACK for the PDSCH is determined based on the value of the predetermined field in the DCI (for example, DCI format 1_0 or 1-11) used for scheduling the PDSCH.
- the predetermined field may be referred to as, for example, a PUCCH resource indicator (PUCCH resource indicator (PRI)) field, an ACK / NACK resource indicator (ACK / NACK resource indicator (ARI)) field, or the like.
- the value of the predetermined field may be referred to as PRI, ARI, or the like.
- the PUCCH resource mapped to each value of the predetermined field may be configured in the UE in advance by the upper layer parameter (for example, ResourceList in the PUCCH-ResourceSet). Further, the PUCCH resource may be set in the UE for each set (PUCCH resource set) including one or more PUCCH resources.
- the upper layer parameter for example, ResourceList in the PUCCH-ResourceSet.
- NR Rel. In 15 it is considered that the UE does not expect to transmit more than one uplink control channel (Physical Uplink Control Channel (PUCCH)) having HARQ-ACK in a single slot. ..
- PUCCH Physical Uplink Control Channel
- the HARQ-ACK codebook includes a time domain (for example, a slot), a frequency domain (for example, a component carrier (CC)), a spatial domain (for example, a layer), and a transport block (TB). )), And may be configured to include a bit for HARQ-ACK in at least one unit of a group of code blocks constituting TB (Code Block Group (CBG)).
- the CC is also called a cell, a serving cell, a carrier, or the like.
- the bit is also referred to as a HARQ-ACK bit, a HARQ-ACK information, a HARQ-ACK information bit, or the like.
- the HARQ-ACK codebook is also called a PDSCH-HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook), a codebook, a HARQ codebook, a HARQ-ACK size, or the like.
- the number of bits (size) and the like included in the HARQ-ACK codebook may be determined quasi-statically (semi-statically) or dynamically (dynamically).
- the quasi-static HARQ-ACK codebook is also called a type-1 HARQ-ACK codebook, a quasi-static codebook, or the like.
- the dynamic HARQ-ACK codebook is also called a type-2 HARQ-ACK codebook, a dynamic codebook, or the like.
- Whether to use the type 1 HARQ-ACK codebook or the type 2 HARQ-ACK codebook may be set in the UE by the upper layer parameter (for example, pdsch-HARQ-ACK-Codebook).
- the UE has a HARQ-ACK bit corresponding to the predetermined range (for example, a range set based on the upper layer parameter) regardless of whether PDSCH is scheduled or not. May be fed back.
- the predetermined range for example, a range set based on the upper layer parameter
- the predetermined range is set or activated in the UE for a predetermined period (for example, a set of a predetermined number of opportunities for receiving a candidate PDSCH or a predetermined number of monitoring opportunities for PDCCH). It may be determined based on at least one of the number of CCs, the number of TBs (number of layers or ranks), the number of CBGs per TB, and the presence or absence of spatial bundling.
- the predetermined range is also referred to as a HARQ-ACK bundling window, a HARQ-ACK feedback window, a bundling window, a feedback window, or the like.
- the UE feeds back the NACK bit as long as it is within a predetermined range even if there is no PDSCH scheduling for the UE. Therefore, when using the type 1 HARQ-ACK codebook, it is expected that the number of HARQ-ACK bits to be fed back will increase.
- the UE may feed back the HARQ-ACK bit for the scheduled PDSCH within the above predetermined range.
- the UE determines the number of bits of the type 2 HARQ-ACK codebook based on a predetermined field in the DCI (for example, a DL allocation index (Downlink Assignment Indicator (Index) (DAI)) field). May be good.
- the DAI field may be split into a counter DAI (counter DAI (cDAI)) and a total DAI (total DAI (tDAI)).
- the counter DAI may indicate a counter value for downlink transmission (PDSCH, data, TB) scheduled within a predetermined period.
- the counter DAI in the DCI that schedules data within the predetermined period is the number counted first in the frequency domain (eg, in CC index order) and then in the time domain (in time index order) within the predetermined period. May be shown.
- the total DAI may indicate the total value (total number) of data scheduled within a predetermined period.
- the total DAI in the DCI that schedules data in a predetermined time unit (for example, PDCCH monitoring opportunity) within the predetermined period is by the predetermined time unit (also referred to as point, timing, etc.) within the predetermined period. It may indicate the total number of scheduled data.
- the UE sets a code block group (CBG) -based transmission (CBG-based HARQ-ACK codebook determination (determination)) by an upper layer parameter (PDSCH code block group transmission information element, PDSCH-CodeBlockGroupTransmission). If not, the UE assumes transport block (TB) based (TB-based) transmission (TB-based HARQ-ACK codebook determination). That is, the UE generates a HARQ-ACK information bit for each TB.
- CBG code block group
- PDSCH-CodeBlockGroupTransmission PDSCH code block group transmission information element
- the UE When the UE is provided with the upper layer parameter of the PDSCH code block group transmission information element to the serving cell (Component Carrier: CC), the UE receives the PDSCH including a plurality of CBGs of one TB.
- the PDSCH code block group transmission information element includes the maximum number of CBGs (maxCodeBlockGroupsPerTransportBlock) in one TB.
- the UE generates each HARQ-ACK information bit of a plurality of CBGs for TB reception of the serving cell, and generates a HARQ-ACK codebook containing the maximum number of CBG HARQ-ACK information bits.
- the UE sets one or more HARQ-ACK bits determined (generated) based on the above type 1 or type 2 HARQ-ACK codebook as an uplink control channel (Physical Uplink Control Channel (PUCCH)) and an uplink shared channel. (Physical Uplink Shared Channel (PUSCH)) may be used for transmission.
- PUCCH Physical Uplink Control Channel
- PUSCH Physical Uplink Shared Channel
- the DCI format 0_1 (UL grant) used for PUSCH scheduling is a 1- or 2-bit 1st downlink assignment index (1st DAI) field and a 0 or 2-bit 2nd downlink assignment index (2nd DAI) field. And, including.
- the first DAI for the semi-static HARQ-ACK codebook (type 1 HARQ-ACK codebook) is 1 bit.
- the first DAI for the dynamic HARQ-ACK codebook (type 2 HARQ-ACK codebook) is 2 bits.
- the second DAI for a dynamic HARQ-ACK codebook with two HARQ-ACK subcodebooks is 2 bits. Other than that, the second DAI is 0 bit.
- a UE configured with a quasi-static HARQ-ACK codebook multiplexes HARQ-ACK information within a PUSCH transmission scheduled by DCI format 0_1, the value VT of the DAI field (1st DAI) in DCI format 0_1 -If DAI , mUL is 1, the UE may generate the HARQ-ACK codebook using the first DAI instead of the total DAI.
- the UE configured with the dynamic HARQ-ACK codebook multiplexes the HARQ-ACK information within the PUSCH transmission scheduled by DCI format 0_1, the UE will use the value of the DAI field (1st DAI) in DCI format 0_1.
- the HARQ-ACK codebook may be generated using the first DAI instead of the total DAI based on the VT -DAI, mUL .
- the DCI format 0_1 corresponds to the first HARQ-ACK subcodebook and the second DAI corresponding to the second HARQ-ACK subcodebook. And, including.
- the UE receives 1-bit UL DAI (1st DAI) in the UL grant for scheduling PUSCH.
- the UE piggybacks HARQ-ACK to the PUSCH (UCI on PUSCH, HARQ-). ACK on PUSCH).
- the UL DAI value is 1, the base station assumes that the HARQ-ACK is piggybacked to the PUSCH regardless of whether the PUCCH and the PUSCH collide, and the UL-SCH carried by the PUSCH. Rate matching may be performed. Even if the UE fails to detect the PDCCH corresponding to HARQ-ACK and the PUCCH does not collide with the PUSCH, the UE may transmit the NACK on the PUSCH for rate matching.
- the UE receives a 2-bit UL DAI (1st DAI) in the UL grant for PUSCH scheduling.
- This UL DAI indicates the number of HARQ-ACKs (total DAI) that are piggybacked to the PUSCH.
- the UE piggybacks the number of HARQ-ACKs indicated in UL DAI to the PUSCH.
- the base station assumes that the number of HARQ-ACKs indicated in UL DAI is piggybacked to PUSCH regardless of whether PUCCH and PUSCH collide, and rate matching of UL-SCH carried by the PUSCH.
- the UE Even if the UE fails to detect the PDCCH corresponding to HARQ-ACK and the PUCCH does not collide with the PUSCH, the UE transmits the number of NACKs indicated in UL DAI for rate matching on the PUSCH. You may.
- the UE receives 2-bit UL DAI (1st DAI) and 2-bit UL DAI (2nd DAI) in the UL grant for scheduling PUSCH.
- the first DAI indicates the number of first HARQ-ACK subcodebooks that are piggybacked to the PUSCH.
- the second DAI indicates the number of second HARQ-ACK subcodebooks that are piggybacked to the PUSCH.
- the base station assumes that the number of HARQ-ACKs shown in the first DAI and the second DAI is piggybacked to the PUSCH regardless of whether the PUCCH and the PUSCH collide, and the UL-SCH carried by the PUSCH. Rate matching may be performed. Even if the UE fails to detect the PDCCH corresponding to HARQ-ACK and the PUCCH does not collide with the PUSCH, the UE will PUSCH the number of NACKs shown in the 1st DAI and 2nd DAI for rate matching. May be sent above.
- the UE determines whether to piggyback HARQ-ACK to the PUSCH based on the UL DAI in the UL grant for scheduling the PUSCH.
- the transmission of at least one of the signal and the channel (hereinafter referred to as a signal / channel) from the NW to the UE is basically unicast transmission.
- the same downlink (DL) data signal / channel eg, downlink shared channel (PDSCH)
- PDSCH downlink shared channel
- a group scheduling mechanism for receiving multicast / broadcast service (MBS) to multiple UEs is being studied.
- DCI payload size, overhead
- a RAN node In point-to-point (PTP) transmission (delivery method), a RAN node (eg, a base station) wirelessly transmits separate copies of MBS data packets to individual UEs.
- PTP point-to-point
- a RAN node In a point-to-multipoint (PTM) transmission (delivery method), a RAN node (eg, a base station) wirelessly transmits a single copy of an MBS data packet to a set of UEs.
- PTP transmission may be referred to as unicast transmission.
- PTP transmission uses a UE-specific PDCCH to schedule a UE-specific PDSCH for multiple RRC connected UEs (RRC_CONNECTED UEs), where the UE-specific PDCCH is a UE-specific radio network temporary identifier (RNTI) (eg, C-RNTI). ) Has a cyclic redundancy check (CRC), and it is considered that the UE-specific PDSCH is scrambled using the same UE-specific RNTI.
- RNTI radio network temporary identifier
- CRC cyclic redundancy check
- PTM transmission method 1 uses group common PDCCH to schedule group-common PDSCH for multiple RRC connected UEs in the same MBS group, group common PDCCH is scrambled by group common RNTI. It has been investigated that the group common PDSCH having a CRC and being scrambled using the same group common RNTI (Fig. 1).
- the PTM transmission method 2 uses the UE-specific PDCCH to schedule the group-common PDSCH for multiple RRC connected UEs in the same MBS group, and the UE-specific PDCCH is scrambled by the UE-specific RNTI (eg, C-RNTI). It has been investigated that the group common PDSCH having the CRC is scrambled using the group common RNTI (Fig. 2).
- the group common PDSCH having the CRC is scrambled using the group common RNTI (Fig. 2).
- the UE-specific PDCCH / PDSCH can be identified by the target UE, but cannot be identified by other UEs in the same MBS group.
- the group common PDCCH / PDSCH is transmitted at the same time / frequency resource and can be identified by all UEs in the same MBS group.
- HARQ feedback is being considered to improve the reliability of MBS.
- At least the PTM transmission method 1 may support at least one of the following feedback methods 1 and 2.
- the UE that succeeds in decrypting the PDSCH transmits an ACK.
- the UE that fails to decrypt the PDSCH transmits NACK.
- the UE operation when the PUCCH including HARQ-ACK corresponding to the multicast PDSCH collides with another UL channel in the time domain is not clear.
- the following problems 1 to 3 may occur.
- the UE transmits HARQ-ACK it is not clear whether the UE transmits HARQ-ACK.
- the base station does not know whether NACK is transmitted or not. In this case, the UL DAI value is not clear.
- the throughput may decrease.
- the present inventors have conceived an overlap (collision) resolution method between the multicast PDSCH and other UL channels.
- a / B / C and “at least one of A, B and C” may be read interchangeably.
- the cell, serving cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be read as each other.
- the index, the ID, the indicator, and the resource ID may be read as each other.
- support, control, controllable, working, working may be read interchangeably.
- configuration, activate, update, indicate, enable, specify, and select may be read as each other.
- link, associate, correspond, and map may be read as each other.
- “allocate”, “assign”, “monitor”, and “map” may be read as each other.
- the upper layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, or a combination thereof.
- RRC Radio Resource Control
- MAC Medium Access Control
- RRC, RRC signaling, RRC parameters, higher layers, higher layer parameters, RRC information elements (IE), and RRC messages may be read interchangeably.
- MAC CE MAC Control Element
- PDU MAC Protocol Data Unit
- the broadcast information includes, for example, a master information block (Master Information Block (MIB)), a system information block (System Information Block (SIB)), a minimum system information (Remaining Minimum System Information (RMSI)), and other system information ( Other System Information (OSI)) may be used.
- MIB Master Information Block
- SIB System Information Block
- RMSI Minimum System Information
- OSI Other System Information
- MAC CE and activation / deactivation commands may be read interchangeably.
- PUCCH, PUSCH, repeat, and transmission occasion may be read as each other.
- multicast, group cast, broadcast, and MBS may be read as each other.
- the multicast PDSCH and the PDSCH scrambled by the group common RNTI may be read as each other.
- HARQ-ACK, HARQ-ACK information, HARQ, ACK / NACK, ACK, NACK, and UCI may be read as each other.
- common, shared, group-common, UE common, and UE shared may be read as each other.
- the UE individual DCI and the DCI having the CEC scrambled by the UE individual RNTI may be read as each other.
- the UE individual RNTI may be, for example, C-RNTI.
- the UE common DCI and the DCI having the CEC scrambled by the UE common RNTI may be read as each other.
- the UE common RNTI may be, for example, multicast-RNTI.
- the cast type of PDSCH may indicate whether the PDSCH is unicast or multicast.
- mapping HARQ-ACK information to PUSCH, multiplexing HARQ-ACK information and data (UL-SCH) on PUSCH, and transmitting HARQ-ACK information on PUSCH are interchangeably read as follows. good.
- mapping HARQ-ACK information to PUCCH, multiplexing HARQ-ACK information with other UCIs on PUCCH, and transmitting HARQ-ACK information on PUCCH may be read interchangeably.
- puncturing the PUSCH by the HARQ-ACK information, mapping the data (uplink (UL) -shared channel (SCH)) to the PUSCH, and then overwriting the HARQ-ACK information to the PUSCH, may be read as each other. good.
- the UE may follow at least one of aspects 1-1 to 1-8 below.
- the UE maps the HARQ-ACK to the PUSCH (multiplexes the HARQ-ACK and the data (UL-SCH) in the PUSCH) and does not transmit the PUCCH.
- the UE does not map the HARQ-ACK to the PUSCH, but transmits the PUCCH.
- the UE may or may not transmit the PUSCH.
- the UE maps the HARQ-ACK to the PUSCH and simultaneously transmits the PUCCH.
- the UE does not map its HARQ-ACK to its PUSCH and does not transmit its PUCCH.
- the UE may or may not transmit the PUSCH.
- the UE uses any of aspects 1-1 to 1-4 (determined / applied / selected) based on whether the HARQ-ACK transmission method is ACK / NACK feedback or NACK-only feedback.
- the UE uses any of aspects 1-1 to 1-4 (determined / applied / selected) based on the number of bits of the HARQ-ACK.
- the UE uses any of aspects 1-1 to 1-4 (determined / applied / selected) based on the PUCCH format of its PUCCH.
- the UE uses any of aspects 1-1 to 1-4 based on the RRC parameter / MAC CE / DCI format / DCI field / PDCCH (DCI CRC) scrambling RNTI / CORESET / search space / UE capability ( Determine / Apply / Select).
- DCI CRC DCI format / DCI field / PDCCH
- the operation is the HARQ- corresponding to the unicast PDSCH. It may be the same as the operation (Rel.15 / 16) when there is a PUSCH that collides with the PUCCH including ACK in the time domain.
- the UE operation becomes clear.
- mapping HARQ-ACK to PUSCH the operation is common to that of unicast PDSCH, so that UE operation can be simplified.
- transmitting HARQ-ACK using PUCCH it is not necessary to change the base station operation in the common PUCCH resource.
- the UE may comply with at least one of the following aspects 2a and 2b.
- ⁇ Aspect 2a When the UL channel that collides with the PUCCH including the HARQ-ACK corresponding to the multicast PDSCH in the time domain is the PUSCH, the UE may follow at least one of the following aspects 2a-1 to 2a-12.
- the UE maps the HARQ-ACK to the PUSCH (multiplexes the HARQ-ACK and the data (UL-SCH) in the PUSCH) and does not transmit the PUCCH.
- the UE does not map the HARQ-ACK to the PUSCH, but transmits the PUCCH.
- the UE may or may not transmit the PUSCH.
- the UE maps the HARQ-ACK to the PUSCH and simultaneously transmits the PUCCH.
- the UE does not map its HARQ-ACK to its PUSCH and does not transmit its PUCCH.
- the UE may or may not transmit the PUSCH.
- the UE uses any of aspects 2a-1 to 2a-4 (determines / applies / selects) depending on whether the PDSCH reception / decoding is successful (whether NACK is generated or not). ..
- the UE may use the aspect 2a-4. If the reception / decoding of the PDSCH fails, the UE may use aspect 2a-1. In this case, the UE can provide NACK-only feedback on the PUSCH and can always send data.
- the UE may use the aspect 2a-4. If the reception / decoding of the PDSCH fails, the UE may use aspect 2a-2. In this case, the NACK-only feedback behavior does not change due to the collision.
- the UE uses any of aspects 2a-1 to 2a-3 (determined / applied / selected) based on the number of bits of the HARQ-ACK.
- the UE may use aspect 2a-1. If the HARQ-ACK is more than 2 bits, the UE may use aspect 2a-4 (the HARQ-ACK does not have to be mapped to the PUSCH).
- the base station can use the UL-SCH without knowing whether the HARQ-ACK is mapped. You can know the mapping.
- the UE uses any of aspects 2a-1 to 2a-4 (determined / applied / selected) based on the PUCCH format of its PUCCH.
- the UE uses any of aspects 2a-1 to 2a-4 based on the RRC parameter / MAC CE / DCI format / DCI field / PDCCH (DCI CRC) scrambling RNTI / CORESET / search space / UE capability ( Determine / Apply / Select).
- DCI CRC DCI format / DCI field / PDCCH
- the mapping method is different from the method of mapping the HARQ-ACK of the unicast PDSCH to the PUSCH.
- the UE may puncture the PUSCH regardless of the number of HARQ-ACK bits (the UL-SCH may be mapped to the PUSCH and then the HARQ-ACK may be overwritten on the PUSCH).
- the UL-SCH mapping position does not depend on whether HARQ-ACK is mapped or not.
- the UL DAI in the UL Grant (DCI) that schedules the PUSCH may be a value assuming that HARQ-ACK is mapped to the PUSCH.
- the UL DAI in the UL Grant (DCI) that schedules the PUSCH may be a value assuming that HARQ-ACK is not mapped to the PUSCH.
- the UE may process HARQ-ACK based on UL DAI.
- the UE may map HARQ-ACK to the PUSCH based on the UL DAI at the UL Grant (DCI) that schedules the PUSCH.
- the UE does not have to map HARQ-ACK to the PUSCH based on the UL DAI at the UL Grant (DCI) that schedules the PUSCH.
- the UE receives a DCI (DL assignment) that schedules a multicast PDSCH corresponding to the HARQ-ACK that will be transmitted on the PUCCH that overlaps the PUSCH (in the time domain). It may be specified that it is not assumed. It may be specified that the UE does not expect to receive a DCI indicating a HARQ-ACK that overlaps (in the time domain) with its PUSCH after the UL grant.
- a DCI DL assignment
- the UE may transmit ACK. For example, if the UE decides to send a PUSCH that collides with the PUCCH (eg, aspect 2a-1), the UE may map the ACK for the multicast PDSCH to that PUSCH.
- the PUCCH eg, aspect 2a-1
- the UE may transmit ACK regardless of the setting / instruction of NACK-only feedback. .. For example, if the UE decides to send a PUSCH that collides with the PUCCH (eg, aspect 2a-1), it will ACK the multicast PDSCH, regardless of the NACK-only feedback setting / instruction for the multicast PDSCH. You may map to.
- the PUCCH eg, aspect 2a-1
- the operation is common to that of unicast PDSCH, and the UE configuration can be simplified.
- HARQ-ACK is up to 2 bits, it is not necessary to change the base station operation even when NACK-only feedback from a plurality of UEs is multiplexed.
- mapping HARQ-ACK to PUCCH it is not necessary to change the UE operation related to NACK-only feedback.
- PUCCH Y may include at least one of scheduling request (SR) and channel state information (CSI).
- SR scheduling request
- CSI channel state information
- the UE multiplexes PUCCH X and PUCCH Y into at least one PUCCH of PUCCH X, PUCCH Y, and another PUCCH Z.
- the UE may map the UCI of PUCCH X (eg, HARQ-ACK) and the UCI of PUCCH Y (eg, SR / CSI) to at least one of PUCCH X, PUCCH Y, and PUCCH Z.
- the PUCCH that maps UCI may be specified in the specification or may be a PUCCH associated with a higher priority.
- the UE does not have to transmit one or both of PUCCH X and PUCCH Y.
- the UE transmits one of PUCCH X and PUCCH Y and drops the other. Which of PUCCH X and PUCCH Y is given priority for transmission may be specified in the specifications. Each of PUCCH X and PUCCH Y may be associated with a priority (the DCI that schedules each of PUCCH X and PUCCH Y may include a priority indicator field). If the priority of PUCCH X and the priority of PUCCH Y are equal, the UE may give priority to one of PUCCH X and PUCCH Y specified in the specification. When the priority of PUCCH X and the priority of PUCCH Y are different, the PUCCH having the higher priority may be prioritized among PUCCH X and PUCCH Y.
- the UE does not multiplexed PUCCH X and PUCCH Y (maps UCI for PUCCH X to PUCCH X, maps UCI for PUCCH Y to PUCCH Y), and transmits PUCCH X and PUCCH Y (simultaneously).
- the UE uses any of aspects 2b-1 to 2b-3 (determines / applies / selects) depending on whether the PDSCH has been successfully received / decoded (whether NACK is generated). ..
- the UE uses any of aspects 2b-1 to 2b-3 based on the number of bits of its HARQ-ACK or the total number of bits of UCI for PUCCH X and UCI for PUCCH Y (determination / application / selection). do).
- the UE uses any of aspects 2b-1 to 2b-3 (determined / applied / selected) based on at least one PUCCH format of PUCCH X and PUCCH Y.
- the UE uses any of aspects 2b-1 to 2b-3 based on the RRC parameter / MAC CE / DCI format / DCI field / PDCCH (DCI CRC) scrambling RNTI / CORESET / search space / UE capability ( Determine / Apply / Select).
- DCI CRC DCI format / DCI field / PDCCH
- the UE may transmit ACK regardless of the setting / instruction of NACK-only feedback. .. For example, if the UE decides to send a PUCCH Y that collides with the PUCCH X, it may map the ACK for the multicast PDSCH to the PUCCH Y regardless of the NACK-only feedback setting / instruction for the multicast PDSCH. ..
- the UE configuration when only NACK is sent or when one PUCCH is dropped, the UE configuration can be simplified.
- the UE may follow at least one of the following aspects 3a to 3c.
- ⁇ Aspect 3a When PUCCH A including HARQ-ACK A corresponding to unicast PDSCH and PUCCH B including HARQ-ACK B corresponding to multicast PDSCH collide in the time domain (Fig. 5A, Case 1 of Problem 3), UE. May follow at least one of the following aspects 3a-1 to 3a-7.
- the UE multiplexes HARQ-ACK A and HARQ-ACK B into at least one PUCCH of PUCCH A, PUCCH B, and another PUCCH C.
- the UE maps HARQ-ACK A and HARQ-ACK B to at least one PUCCH of PUCCH A, PUCCH B and PUCCH C, and transmits at least one PUCCH of PUCCH A, PUCCH B and PUCCH C. May be good.
- the PUCCH that maps HARQ-ACK may be specified in the specification or may be a PUCCH associated with a higher priority.
- the UE does not have to transmit one or both of PUCCH A and PUCCH B.
- the UE transmits one of PUCCH A and PUCCH B (HARQ-ACK A and HARQ-ACK B) and drops the other.
- Which of HARQ-ACK A and HARQ-ACK B is given priority for transmission may be specified in the specifications.
- Each of HARQ-ACK A and HARQ-ACK B may have a priority associated with it (the DCI scheduling each of PUCCH A and PUCCH B may include a priority indicator field). ). If the priority of HARQ-ACK A and the priority of PUCCH B are equal, the UE may prefer one of HARQ-ACK A and HARQ-ACK B as specified in the specification. If the priority of HARQ-ACK A and the priority of PUCCH B are different, the UE may give priority to HARQ-ACK having the higher priority among HARQ-ACK A and HARQ-ACK B.
- the UE does not multiplex HARQ-ACK A and HARQ-ACK B (map HARQ-ACK A to PUCCH A, map HARQ-ACK B to PUCCH B), and transmit PUCCH A and PUCCH B (simultaneously). do.
- the UE is based on the number of bits of HARQ-ACK A and HARQ-ACK B, or the total number of bits of HARQ-ACK A and HARQ-ACK B (UCI of PUCCH A and PUCCH B). To 3a-3 is used (determine / apply / select).
- the UE uses any of aspects 3a-1 to 3a-3 (determined / applied / selected) based on at least one PUCCH format of PUCCH A and PUCCH B.
- the UE uses any of aspects 3a-1 to 3a-3 based on the RRC parameter / MAC CE / DCI format / DCI field / PDCCH (DCI CRC) scrambling RNTI / CORESET / search space / UE capability ( Determine / Apply / Select).
- DCI CRC DCI format / DCI field / PDCCH
- the UE uses any of aspects 3a-1 to 3a-3 (determined / applied / selected) based on the HARQ-ACK codebook type.
- the communication quality can be maintained or improved.
- the UE operation can be simplified.
- ⁇ Aspect 3b >> PUCCH A containing HARQ-ACK corresponding to unicast PDSCH and PUSCH collide in the time domain, and PUCCH B containing HARQ-ACK corresponding to multicast PDSCH and the same PUSCH collide in the time domain. , PUCCH A and PUCCH B do not collide in the time domain (FIG. 5B, Case 2 of Problem 3), the UE may follow at least one of aspects 3b-1 to 3b-9 below.
- the UE multiplexes HARQ-ACK A and HARQ-ACK B in its PUSCH to its PUSCH.
- the UE maps HARQ-ACK A and HARQ-ACK B to its PUSCH and transmits the PUSCH.
- the UE does not have to transmit at least one of PUCCH A and PUCCH B.
- the UE drops one of HARQ-ACK A and HARQ-ACK B, maps the other to its PUSCH, and transmits its PUSCH.
- Which of HARQ-ACK A and HARQ-ACK B is given priority for transmission may be specified in the specifications.
- Each of HARQ-ACK A and HARQ-ACK B may have a priority associated with it (the DCI scheduling each of PUCCH A and PUCCH B may include a priority indicator field). ). If the priority of HARQ-ACK A and the priority of PUCCH B are equal, the UE may prefer one of HARQ-ACK A and HARQ-ACK B as specified in the specification. If the priority of HARQ-ACK A and the priority of PUCCH B are different, the UE may give priority to HARQ-ACK having the higher priority among HARQ-ACK A and HARQ-ACK B.
- the UE does not multiplex HARQ-ACK A and HARQ-ACK B (map HARQ-ACK A to PUCCH A, map HARQ-ACK B to PUCCH B), and map PUCCH A, PUCCH B and their PUSCH. (Simultaneously) Send.
- the UE does not multiplex HARQ-ACK A and HARQ-ACK B (map HARQ-ACK A to PUCCH A, map HARQ-ACK B to PUCCH B), transmit PUCCH A and PUCCH B, and transmit it. Drop the PUSCH.
- the UE is based on the number of bits of HARQ-ACK A and HARQ-ACK B, or the total number of bits of HARQ-ACK A and HARQ-ACK B (UCI of PUCCH A and PUCCH B). Use any of 3b-4 from (determine / apply / select).
- the UE uses any of aspects 3b-1 to 3b-4 based on at least one PUCCH format of PUCCH A and PUCCH B (determination / application / selection).
- the UE uses any of aspects 3b-1 to 3b-4 based on the RRC parameter / MAC CE / DCI format / DCI field / PDCCH (DCI CRC) scrambling RNTI / CORESET / search space / UE capability ( Determine / Apply / Select).
- DCI CRC DCI format / DCI field / PDCCH
- the UE uses any of aspects 3b-1 to 3b-4 (determined / applied / selected) based on the HARQ-ACK codebook type.
- the UL DAI in the UL Grant (DCI) that schedules the PUSCH is a value corresponding to the HARQ-ACK to be transmitted.
- DCI UL Grant
- one (one set) UL DAI obtained from both HARQ-ACK A and HARQ-ACK B may be included in the UL grant, or HARQ-ACK A and HARQ-ACK B.
- Two UL DAIs (two sets) obtained from each may be included in the UL grant.
- the UE may map HARQ-ACK to its PUSCH based on UL DAI.
- the communication quality can be maintained or improved.
- the UE operation can be simplified.
- Aspect 3c >> PUCCH A containing HARQ-ACK corresponding to unicast PDSCH and PUCCH C collide in the time domain, and PUCCH B containing HARQ-ACK corresponding to multicast PDSCH and PUCCH C collide in the time domain.
- PUCCH A and PUCCH B do not collide in the time domain (FIG. 5C, Case 3 of Problem 3)
- the UE may follow at least one of aspects 3c-1 to 3c-8 below.
- the UE is multiplexed with HARQ-ACK A, HARQ-ACK B, and UCI of PUCCH C, and transmits at least one PUCCH of PUCCH A, PUCCH B, PUCCH C, and another PUCCH D. ..
- the UE maps at least two of HARQ-ACK A, HARQ-ACK B, and UCI of PUCCH C to at least one PUCCH of PUCCH A, PUCCH B, PUCCH C, and PUCCH D, and PUCCH A.
- PUCCH B and PUCCH C and PUCCH D may transmit at least one PUCCH.
- the PUCCH that maps HARQ-ACK A, HARQ-ACK B, and UCI of PUCCH C may be specified in the specification or is higher. It may be a PUCCH associated with a priority.
- the UE does not have to transmit at least one of PUCCH A, PUCCH B, and PUCCH C.
- the UE drops one of HARQ-ACK A and HARQ-ACK B, maps the other to PUCCH C or another PUCCH D, and transmits PUCCH C or PUCCH D.
- Which of HARQ-ACK A and HARQ-ACK B is given priority for transmission may be specified in the specifications.
- Each of HARQ-ACK A and HARQ-ACK B may have a priority associated with it (the DCI scheduling each of PUCCH A and PUCCH B may include a priority indicator field). ). If the priority of HARQ-ACK A and the priority of PUCCH B are equal, the UE may prefer one of HARQ-ACK A and HARQ-ACK B as specified in the specification. If the priority of HARQ-ACK A and the priority of PUCCH B are different, the UE may give priority to HARQ-ACK having the higher priority among HARQ-ACK A and HARQ-ACK B.
- the UE does not multiplex HARQ-ACK A and HARQ-ACK B (map HARQ-ACK A to PUCCH A, map HARQ-ACK B to PUCCH B), and PUCCH A, PUCCH B, and PUCCH C. (Simultaneously) Send.
- the UE does not multiplex HARQ-ACK A and HARQ-ACK B (map HARQ-ACK A to PUCCH A, map HARQ-ACK B to PUCCH B), transmit PUCCH A and PUCCH B, and PUCCH. Drop C.
- the UE is the number of bits of HARQ-ACK A and HARQ-ACK B, or the total number of bits of HARQ-ACK A and HARQ-ACK B (UCI of PUCCH A and PUCCH B), or the bit of UCI of PUCCH C. Any of aspects 3c-1 to 3c-4, based on the number, or the total number of bits of the UCI of HARQ-ACK A, HARQ-ACK B, and PUCCH C (UCI of PUCCH A, PUCCH B, and PUCCH C). (Determine / Apply / Select).
- the UE uses any of aspects 3c-1 to 3c-4 based on at least one PUCCH format of PUCCH A and PUCCH B (determination / application / selection).
- the UE uses any of aspects 3c-1 to 3c-4 based on the RRC parameter / MAC CE / DCI format / DCI field / PDCCH (DCI CRC) scrambling RNTI / CORESET / search space / UE capability ( Determine / Apply / Select).
- DCI CRC DCI format / DCI field / PDCCH
- the UE uses any of aspects 3c-1 to 3c-4 (determined / applied / selected) based on the HARQ-ACK codebook type.
- the communication quality can be maintained or improved.
- the UE operation can be simplified.
- Upper layer parameters (RRC information elements) / UE capabilities corresponding to at least one function (feature) in the first to third embodiments may be specified.
- UE capability may indicate that it supports this feature.
- the UE for which the upper layer parameter corresponding to the function is set may perform the function. It may be specified that the UE for which the upper layer parameter corresponding to the function is not set does not perform the function.
- the UE that reports the UE capability indicating that it supports the function may perform the function.
- UEs that do not report UE capabilities that indicate support for that feature may be specified not to perform that feature.
- the UE may perform the function. If the UE reports a UE capability indicating that it supports the feature, or if a higher layer parameter corresponding to the feature is set, the UE may be specified not to perform the feature.
- the function may be simultaneous transmission of PUCCH and PUSCH.
- the function may be the simultaneous transmission of PUCCH and PUCCH.
- the same beam / QCL / TCI state / spatial relationship is set / notified / instructed to multiple (for example, two) channels transmitted simultaneously (beams / QCL / TCI state / spatial relationship of multiple channels transmitted simultaneously). If the QCL relationship is the same, or if the beams / QCL / TCI state / spatially related QCL reference destination RS of multiple channels to be transmitted simultaneously are common), the UE has that function (the simultaneous transmission). May be done. According to this condition, the UE does not need to transmit using a plurality of different beams at the same time.
- This condition may be limited to frequencies above a specific frequency (for example, frequency range (FR) 2 / FR4). This condition may not be present at frequencies lower than the specific frequency (for example, FR1).
- the specific frequency may be any one of 7.152 GHz, 24.25 GHz, and 52.6 GHz.
- the UE may perform the function (the simultaneous transmission). .. This operation is suitable when the UE can transmit one channel per beam (when the UE has a multi-panel configuration).
- the PUSCH if the PUSCH can be skipped, for example, if there is no data to be transmitted, the PUSCH is not skipped, and HARQ-ACK corresponding to the multicast PDSCH is mapped (multiplexed) to the PUSCH and transmitted. good. This behavior may be applied regardless of the setting / instruction of NACK-only feedback for the multicast PDSCH.
- the UE can realize the above functions while maintaining compatibility with existing specifications.
- wireless communication system Wireless communication system
- communication is performed using any one of the wireless communication methods according to each of the above-described embodiments of the present disclosure or a combination thereof.
- FIG. 6 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
- the wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by Third Generation Partnership Project (3GPP). ..
- the wireless communication system 1 may support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between a plurality of Radio Access Technologies (RATs).
- MR-DC is a dual connectivity (E-UTRA-NR Dual Connectivity (EN-DC)) between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR, and a dual connectivity (NR-E) between NR and LTE.
- E-UTRA-NR Dual Connectivity Evolved Universal Terrestrial Radio Access (E-UTRA)
- NR-E dual connectivity
- NE-DC -UTRA Dual Connectivity
- the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)).
- the base station (gNB) of NR is MN
- the base station (eNB) of LTE (E-UTRA) is SN.
- the wireless communication system 1 has dual connectivity between a plurality of base stations in the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) in which both MN and SN are NR base stations (gNB). )) May be supported.
- a plurality of base stations in the same RAT for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) in which both MN and SN are NR base stations (gNB). )
- NR-NR Dual Connectivity NR-DC
- gNB NR base stations
- the wireless communication system 1 includes a base station 11 that forms a macrocell C1 having a relatively wide coverage, and a base station 12 (12a-12c) that is arranged in the macrocell C1 and forms a small cell C2 that is narrower than the macrocell C1. You may prepare.
- the user terminal 20 may be located in at least one cell. The arrangement, number, and the like of each cell and the user terminal 20 are not limited to the mode shown in the figure.
- the base stations 11 and 12 are not distinguished, they are collectively referred to as the base station 10.
- the user terminal 20 may be connected to at least one of a plurality of base stations 10.
- the user terminal 20 may use at least one of carrier aggregation (Carrier Aggregation (CA)) and dual connectivity (DC) using a plurality of component carriers (Component Carrier (CC)).
- CA Carrier Aggregation
- DC dual connectivity
- CC Component Carrier
- Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)).
- the macrocell C1 may be included in FR1 and the small cell C2 may be included in FR2.
- FR1 may be in a frequency band of 6 GHz or less (sub 6 GHz (sub-6 GHz)), and FR 2 may be in a frequency band higher than 24 GHz (above-24 GHz).
- the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.
- the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
- TDD Time Division Duplex
- FDD Frequency Division Duplex
- the plurality of base stations 10 may be connected by wire (for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication).
- wire for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.
- NR communication for example, when NR communication is used as a backhaul between base stations 11 and 12, the base station 11 corresponding to the higher-level station is an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to a relay station (relay) is IAB. It may be called a node.
- IAB Integrated Access Backhaul
- relay station relay station
- the base station 10 may be connected to the core network 30 via another base station 10 or directly.
- the core network 30 may include at least one such as Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
- EPC Evolved Packet Core
- 5GCN 5G Core Network
- NGC Next Generation Core
- the user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.
- a wireless access method based on Orthogonal Frequency Division Multiplexing may be used.
- OFDM Orthogonal Frequency Division Multiplexing
- DL Downlink
- UL Uplink
- CP-OFDM Cyclic Prefix OFDM
- DFT-s-OFDM Discrete Fourier Transform Spread OFDM
- OFDMA Orthogonal Frequency Division Multiple. Access
- SC-FDMA Single Carrier Frequency Division Multiple Access
- the wireless access method may be called a waveform.
- another wireless access system for example, another single carrier transmission system, another multi-carrier transmission system
- the UL and DL wireless access systems may be used as the UL and DL wireless access systems.
- a downlink shared channel Physical Downlink Shared Channel (PDSCH)
- a broadcast channel Physical Broadcast Channel (PBCH)
- a downlink control channel Physical Downlink Control
- PDSCH Physical Downlink Control
- the uplink shared channel Physical Uplink Shared Channel (PUSCH)
- the uplink control channel Physical Uplink Control Channel (PUCCH)
- the random access channel shared by each user terminal 20 are used.
- Physical Random Access Channel (PRACH) Physical Random Access Channel or the like may be used.
- User data, upper layer control information, System Information Block (SIB), etc. are transmitted by PDSCH.
- User data, upper layer control information, and the like may be transmitted by the PUSCH.
- the Master Information Block (MIB) may be transmitted by the PBCH.
- Lower layer control information may be transmitted by PDCCH.
- the lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information of at least one of PDSCH and PUSCH.
- DCI Downlink Control Information
- the DCI that schedules PDSCH may be called DL assignment, DL DCI, or the like, and the DCI that schedules PUSCH may be called UL grant, UL DCI, or the like.
- the PDSCH may be read as DL data, and the PUSCH may be read as UL data.
- a control resource set (COntrol REsource SET (CORESET)) and a search space (search space) may be used for PDCCH detection.
- CORESET corresponds to a resource for searching DCI.
- the search space corresponds to the search area and search method of PDCCH candidates (PDCCH candidates).
- One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a search space based on the search space settings.
- One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels.
- One or more search spaces may be referred to as a search space set.
- the "search space”, “search space set”, “search space setting”, “search space set setting”, “CORESET”, “CORESET setting”, etc. of the present disclosure may be read as each other.
- channel state information (Channel State Information (CSI)
- delivery confirmation information for example, it may be called Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.
- scheduling request (Scheduling Request).
- Uplink Control Information including at least one of SR)
- the PRACH may transmit a random access preamble to establish a connection with the cell.
- downlinks, uplinks, etc. may be expressed without “links”. Further, it may be expressed without adding "Physical" to the beginning of various channels.
- a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), and the like may be transmitted.
- the DL-RS includes a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), and a reference signal for demodulation (DeModulation).
- CRS Cell-specific Reference Signal
- CSI-RS Channel State Information Reference Signal
- DMRS positioning reference signal
- PRS Positioning Reference Signal
- PTRS phase tracking reference signal
- the synchronization signal may be, for example, at least one of a primary synchronization signal (Primary Synchronization Signal (PSS)) and a secondary synchronization signal (Secondary Synchronization Signal (SSS)).
- PSS Primary Synchronization Signal
- SSS Secondary Synchronization Signal
- the signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be referred to as SS / PBCH block, SS Block (SSB) and the like.
- SS, SSB and the like may also be called a reference signal.
- a measurement reference signal Sounding Reference Signal (SRS)
- a demodulation reference signal DMRS
- UL-RS Uplink Reference Signal
- UE-specific Reference Signal UE-specific Reference Signal
- FIG. 7 is a diagram showing an example of the configuration of the base station according to the embodiment.
- the base station 10 includes a control unit 110, a transmission / reception unit 120, a transmission / reception antenna 130, and a transmission line interface 140.
- the control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140 may each be provided with one or more.
- the functional block of the characteristic portion in the present embodiment is mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.
- the control unit 110 controls the entire base station 10.
- the control unit 110 can be composed of a controller, a control circuit, and the like described based on the common recognition in the technical field according to the present disclosure.
- the control unit 110 may control signal generation, scheduling (for example, resource allocation, mapping) and the like.
- the control unit 110 may control transmission / reception, measurement, and the like using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140.
- the control unit 110 may generate data to be transmitted as a signal, control information, a sequence, and the like, and transfer the data to the transmission / reception unit 120.
- the control unit 110 may perform call processing (setting, release, etc.) of the communication channel, state management of the base station 10, management of radio resources, and the like.
- the transmission / reception unit 120 may include a baseband unit 121, a Radio Frequency (RF) unit 122, and a measurement unit 123.
- the baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212.
- the transmission / reception unit 120 includes a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, etc., which are described based on the common recognition in the technical field according to the present disclosure. be able to.
- the transmission / reception unit 120 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit.
- the transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122.
- the receiving unit may be composed of a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.
- the transmitting / receiving antenna 130 can be composed of an antenna described based on the common recognition in the technical field according to the present disclosure, for example, an array antenna.
- the transmission / reception unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like.
- the transmission / reception unit 120 may receive the above-mentioned uplink channel, uplink reference signal, and the like.
- the transmission / reception unit 120 may form at least one of a transmission beam and a reception beam by using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), and the like.
- digital beamforming for example, precoding
- analog beamforming for example, phase rotation
- the transmission / reception unit 120 processes, for example, Packet Data Convergence Protocol (PDCP) layer processing and Radio Link Control (RLC) layer processing (for example, RLC) for data, control information, etc. acquired from control unit 110.
- PDCP Packet Data Convergence Protocol
- RLC Radio Link Control
- MAC Medium Access Control
- HARQ retransmission control HARQ retransmission control
- the transmission / reception unit 120 performs channel coding (may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (Discrete Fourier Transform (DFT)) for the bit string to be transmitted. Processing (if necessary), inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-analog transformation may be performed, and the baseband signal may be output.
- channel coding may include error correction coding
- modulation modulation
- mapping mapping, filtering
- DFT discrete Fourier Transform
- IFFT inverse Fast Fourier Transform
- precoding coding
- transmission processing such as digital-analog transformation
- the transmission / reception unit 120 may perform modulation, filtering, amplification, etc. on the baseband signal to the radio frequency band, and transmit the signal in the radio frequency band via the transmission / reception antenna 130. ..
- the transmission / reception unit 120 may perform amplification, filtering, demodulation to a baseband signal, or the like on the signal in the radio frequency band received by the transmission / reception antenna 130.
- the transmission / reception unit 120 (reception processing unit 1212) performs analog-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) for the acquired baseband signal. )) Processing (if necessary), filtering, decoding, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing are applied. User data and the like may be acquired.
- FFT fast Fourier transform
- IDFT inverse discrete Fourier transform
- the transmission / reception unit 120 may perform measurement on the received signal.
- the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, or the like based on the received signal.
- the measuring unit 123 has received power (for example, Reference Signal Received Power (RSRP)) and reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)).
- RSRP Reference Signal Received Power
- RSSQ Reference Signal Received Quality
- SINR Signal to Noise Ratio
- Signal strength for example, Received Signal Strength Indicator (RSSI)
- propagation path information for example, CSI
- the measurement result may be output to the control unit 110.
- the transmission line interface 140 transmits / receives signals (backhaul signaling) to / from a device included in the core network 30, another base station 10, etc., and user data (user plane data) for the user terminal 20 and a control plane. Data or the like may be acquired or transmitted.
- the transmission unit and the reception unit of the base station 10 in the present disclosure may be composed of at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140.
- the physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgment (HARQ-ACK) information to the multicast physical downlink shared channel (PDSCH) overlaps with the uplink channel in the time domain. If so, at least one channel of the PUCCH and the uplink channel may be determined.
- the transmission / reception unit 120 may receive the channel.
- FIG. 8 is a diagram showing an example of the configuration of the user terminal according to the embodiment.
- the user terminal 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230.
- the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may each be provided with one or more.
- the functional block of the feature portion in the present embodiment is mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.
- the control unit 210 controls the entire user terminal 20.
- the control unit 210 can be composed of a controller, a control circuit, and the like described based on the common recognition in the technical field according to the present disclosure.
- the control unit 210 may control signal generation, mapping, and the like.
- the control unit 210 may control transmission / reception, measurement, and the like using the transmission / reception unit 220 and the transmission / reception antenna 230.
- the control unit 210 may generate data to be transmitted as a signal, control information, a sequence, and the like, and transfer the data to the transmission / reception unit 220.
- the transmission / reception unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223.
- the baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212.
- the transmission / reception unit 220 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmission / reception circuit, and the like, which are described based on the common recognition in the technical field according to the present disclosure.
- the transmission / reception unit 220 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit.
- the transmission unit may be composed of a transmission processing unit 2211 and an RF unit 222.
- the receiving unit may be composed of a receiving processing unit 2212, an RF unit 222, and a measuring unit 223.
- the transmitting / receiving antenna 230 can be composed of an antenna described based on the common recognition in the technical field according to the present disclosure, for example, an array antenna.
- the transmission / reception unit 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like.
- the transmission / reception unit 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.
- the transmission / reception unit 220 may form at least one of a transmission beam and a reception beam by using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), and the like.
- digital beamforming for example, precoding
- analog beamforming for example, phase rotation
- the transmission / reception unit 220 processes, for example, PDCP layer processing, RLC layer processing (for example, RLC retransmission control), and MAC layer processing (for example, for data, control information, etc. acquired from the control unit 210). , HARQ retransmission control), etc., to generate a bit string to be transmitted.
- the transmission / reception unit 220 (transmission processing unit 2211) performs channel coding (may include error correction coding), modulation, mapping, filtering processing, DFT processing (if necessary), and IFFT processing for the bit string to be transmitted. , Precoding, digital-to-analog conversion, and other transmission processing may be performed to output a baseband signal.
- Whether or not to apply the DFT process may be based on the transform precoding setting.
- the transmission / reception unit 220 transmits the channel using the DFT-s-OFDM waveform.
- the DFT process may be performed as the transmission process, and if not, the DFT process may not be performed as the transmission process.
- the transmission / reception unit 220 may perform modulation, filtering, amplification, etc. on the baseband signal to the radio frequency band, and transmit the signal in the radio frequency band via the transmission / reception antenna 230. ..
- the transmission / reception unit 220 may perform amplification, filtering, demodulation to a baseband signal, or the like on the signal in the radio frequency band received by the transmission / reception antenna 230.
- the transmission / reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering processing, demapping, demodulation, and decoding (error correction) for the acquired baseband signal. Decoding may be included), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.
- the transmission / reception unit 220 may perform measurement on the received signal.
- the measuring unit 223 may perform RRM measurement, CSI measurement, or the like based on the received signal.
- the measuring unit 223 may measure received power (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), propagation path information (for example, CSI), and the like.
- the measurement result may be output to the control unit 210.
- the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmission / reception unit 220 and the transmission / reception antenna 230.
- the control unit When the physical uplink control channel (PUCCH) for transmitting hybrid automatic repeat reQuest acknowledgment (HARQ-ACK) information to the multicast physical downlink shared channel (PDSCH) overlaps with the uplink channel in the time domain, the control unit.
- the 210 may determine at least one channel of the PUCCH and the uplink channel.
- the transmission / reception unit 220 may transmit the channel.
- the PUCCH resource may be shared among a plurality of terminals (first embodiment).
- a method of transmitting only a negative acquisition (NACK) to the PUCCH may be applied (second embodiment).
- the uplink channel may be either a second PUCCH for transmitting the second HARQ-ACK information to the unicast PDSCH and a channel that overlaps the second PUCCH in the time domain (third implementation). form).
- each functional block is realized using one physically or logically coupled device, or two or more physically or logically separated devices can be directly or indirectly (eg, for example). , Wired, wireless, etc.) and may be realized using these plurality of devices.
- the functional block may be realized by combining the software with the one device or the plurality of devices.
- the functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and deemed. , Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc.
- a functional block (configuration unit) for functioning transmission may be referred to as a transmitting unit (transmitting unit), a transmitter (transmitter), or the like.
- the realization method is not particularly limited.
- the base station, user terminal, and the like in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure.
- FIG. 9 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment.
- the base station 10 and the user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. ..
- the hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.
- processor 1001 may be a plurality of processors. Further, the processing may be executed by one processor, or the processing may be executed simultaneously, sequentially, or by using other methods by two or more processors.
- the processor 1001 may be mounted by one or more chips.
- the processor 1001 For each function in the base station 10 and the user terminal 20, for example, by loading predetermined software (program) on hardware such as the processor 1001 and the memory 1002, the processor 1001 performs an operation and communicates via the communication device 1004. It is realized by controlling at least one of reading and writing of data in the memory 1002 and the storage 1003.
- predetermined software program
- the processor 1001 operates, for example, an operating system to control the entire computer.
- the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, and the like.
- CPU central processing unit
- control unit 110 210
- transmission / reception unit 120 220
- the like may be realized by the processor 1001.
- the processor 1001 reads a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these.
- a program program code
- the control unit 110 may be realized by a control program stored in the memory 1002 and operating in the processor 1001, and may be realized in the same manner for other functional blocks.
- the memory 1002 is a computer-readable recording medium, for example, at least a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), or any other suitable storage medium. It may be composed of one.
- the memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like.
- the memory 1002 can store a program (program code), a software module, or the like that can be executed to implement the wireless communication method according to the embodiment of the present disclosure.
- the storage 1003 is a computer-readable recording medium, and is, for example, a flexible disk, a floppy disk (registered trademark) disk, an optical magnetic disk (for example, a compact disc (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, etc.). At least one of Blu-ray® discs, removable discs, optical disc drives, smart cards, flash memory devices (eg cards, sticks, key drives), magnetic stripes, databases, servers, and other suitable storage media. May be configured by.
- the storage 1003 may be referred to as an auxiliary storage device.
- the communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like.
- the communication device 1004 has, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (Frequency Division Duplex (FDD)) and time division duplex (Time Division Duplex (TDD)). May be configured to include.
- FDD Frequency Division Duplex
- TDD Time Division Duplex
- the transmission / reception unit 120 (220), the transmission / reception antenna 130 (230), and the like described above may be realized by the communication device 1004.
- the transmission / reception unit 120 (220) may be physically or logically separated by the transmission unit 120a (220a) and the reception unit 120b (220b).
- the input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts an input from the outside.
- the output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside.
- the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
- each device such as the processor 1001 and the memory 1002 is connected by the bus 1007 for communicating information.
- the bus 1007 may be configured by using a single bus, or may be configured by using a different bus for each device.
- the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (Digital Signal Processor (DSP)), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), and the like. It may be configured to include hardware, and a part or all of each functional block may be realized by using the hardware. For example, processor 1001 may be implemented using at least one of these hardware.
- DSP Digital Signal Processor
- ASIC Application Specific Integrated Circuit
- PLD Programmable Logic Device
- FPGA Field Programmable Gate Array
- the terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings.
- channels, symbols and signals may be read interchangeably.
- the signal may be a message.
- the reference signal may be abbreviated as RS, and may be referred to as a pilot, a pilot signal, or the like depending on the applied standard.
- the component carrier CC may be referred to as a cell, a frequency carrier, a carrier frequency, or the like.
- the wireless frame may be configured by one or more periods (frames) in the time domain.
- Each of the one or more periods (frames) constituting the radio frame may be referred to as a subframe.
- the subframe may be composed of one or more slots in the time domain.
- the subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
- the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel.
- Numerology includes, for example, subcarrier spacing (SubCarrier Spacing (SCS)), bandwidth, symbol length, cyclic prefix length, transmission time interval (Transmission Time Interval (TTI)), number of symbols per TTI, and wireless frame configuration.
- SCS subcarrier Spacing
- TTI Transmission Time Interval
- a specific filtering process performed by the transmitter / receiver in the frequency domain, a specific windowing process performed by the transmitter / receiver in the time domain, and the like may be indicated.
- the slot may be composed of one or more symbols in the time area (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.). Further, the slot may be a time unit based on numerology.
- OFDM Orthogonal Frequency Division Multiplexing
- SC-FDMA Single Carrier Frequency Division Multiple Access
- the slot may include a plurality of mini slots.
- Each minislot may be composed of one or more symbols in the time domain. Further, the mini-slot may be referred to as a sub-slot.
- a minislot may consist of a smaller number of symbols than the slot.
- a PDSCH (or PUSCH) transmitted in a time unit larger than the mini slot may be referred to as a PDSCH (PUSCH) mapping type A.
- the PDSCH (or PUSCH) transmitted using the minislot may be referred to as PDSCH (PUSCH) mapping type B.
- Wireless frames, subframes, slots, mini slots and symbols all represent time units when transmitting signals.
- the radio frame, subframe, slot, minislot and symbol may use different names corresponding to each.
- the time units such as frames, subframes, slots, mini slots, and symbols in the present disclosure may be read as each other.
- one subframe may be called TTI
- a plurality of consecutive subframes may be called TTI
- one slot or one minislot may be called TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms. May be.
- the unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.
- TTI refers to, for example, the minimum time unit of scheduling in wireless communication.
- the base station schedules each user terminal to allocate radio resources (frequency bandwidth that can be used in each user terminal, transmission power, etc.) in TTI units.
- the definition of TTI is not limited to this.
- TTI may be a transmission time unit such as a channel-encoded data packet (transport block), a code block, or a code word, or may be a processing unit such as scheduling or link adaptation.
- the time interval for example, the number of symbols
- the transport block, code block, code word, etc. may be shorter than the TTI.
- one or more TTIs may be the minimum time unit for scheduling. Further, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
- a TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in 3GPP Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like.
- TTI shorter than normal TTI may be referred to as shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, minislot, subslot, slot and the like.
- the long TTI (eg, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms
- the short TTI eg, shortened TTI, etc.
- TTI having the above TTI length may be read as TTI having the above TTI length.
- a resource block is a resource allocation unit in the time domain and the frequency domain, and may include one or a plurality of continuous subcarriers in the frequency domain.
- the number of subcarriers contained in the RB may be the same regardless of the numerology, and may be, for example, 12.
- the number of subcarriers contained in the RB may be determined based on numerology.
- the RB may include one or more symbols in the time domain, and may have a length of 1 slot, 1 mini slot, 1 subframe or 1 TTI.
- Each 1TTI, 1 subframe, etc. may be composed of one or a plurality of resource blocks.
- one or more RBs are a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, and an RB. It may be called a pair or the like.
- PRB Physical RB
- SCG sub-carrier Group
- REG resource element group
- PRB pair an RB. It may be called a pair or the like.
- the resource block may be composed of one or a plurality of resource elements (Resource Element (RE)).
- RE Resource Element
- 1RE may be a radio resource area of 1 subcarrier and 1 symbol.
- Bandwidth Part (which may also be called partial bandwidth) represents a subset of consecutive common resource blocks (RBs) for a neurology in a carrier. May be good.
- the common RB may be specified by the index of the RB with respect to the common reference point of the carrier.
- PRBs may be defined in a BWP and numbered within that BWP.
- the BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL).
- BWP UL BWP
- BWP for DL DL BWP
- One or more BWPs may be set in one carrier for the UE.
- At least one of the configured BWPs may be active and the UE may not expect to send or receive a given signal / channel outside the active BWP.
- “cell”, “carrier” and the like in this disclosure may be read as “BWP”.
- the above-mentioned structures such as wireless frames, subframes, slots, mini slots, and symbols are merely examples.
- the number of subframes contained in a radio frame the number of slots per subframe or radioframe, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in the RB.
- the number of subcarriers, the number of symbols in the TTI, the symbol length, the cyclic prefix (CP) length, and the like can be changed in various ways.
- the information, parameters, etc. described in the present disclosure may be expressed using an absolute value, a relative value from a predetermined value, or another corresponding information. It may be represented.
- the radio resource may be indicated by a predetermined index.
- the information, signals, etc. described in this disclosure may be represented using any of a variety of different techniques.
- data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may be represented by a combination of.
- information, signals, etc. can be output from the upper layer to the lower layer and from the lower layer to at least one of the upper layers.
- Information, signals, etc. may be input / output via a plurality of network nodes.
- Input / output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, signals, etc. can be overwritten, updated, or added. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.
- the notification of information is not limited to the embodiment / embodiment described in the present disclosure, and may be performed by using another method.
- the notification of information in the present disclosure includes physical layer signaling (for example, downlink control information (DCI)), uplink control information (Uplink Control Information (UCI))), and higher layer signaling (for example, Radio Resource Control). (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals or combinations thereof. May be carried out by.
- DCI downlink control information
- UCI Uplink Control Information
- RRC Radio Resource Control
- MIB Master Information Block
- SIB System Information Block
- MAC Medium Access Control
- the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), and the like.
- the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
- MAC signaling may be notified using, for example, a MAC control element (MAC Control Element (CE)).
- CE MAC Control Element
- the notification of predetermined information is not limited to the explicit notification, but implicitly (for example, by not notifying the predetermined information or another information). May be done (by notification of).
- the determination may be made by a value represented by 1 bit (0 or 1), or by a boolean value represented by true or false. , May be done by numerical comparison (eg, comparison with a given value).
- software, instructions, information, etc. may be transmitted and received via a transmission medium.
- the software uses at least one of wired technology (coaxial cable, fiber optic cable, twist pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.) on the website.
- wired technology coaxial cable, fiber optic cable, twist pair, digital subscriber line (DSL), etc.
- wireless technology infrared, microwave, etc.
- the terms “system” and “network” used in this disclosure may be used interchangeably.
- the “network” may mean a device (eg, a base station) included in the network.
- precoding "precoding weight”
- QCL Quality of Co-Co-Location
- TCI state Transmission Configuration Indication state
- space "Spatial relation”, “spatial domain filter”, “transmission power”, “phase rotation”, "antenna port”, “antenna port group”, “layer”, “number of layers”
- Terms such as “rank”, “resource”, “resource set”, “resource group”, “beam”, “beam width”, “beam angle”, "antenna”, “antenna element", “panel” are compatible.
- base station BS
- wireless base station fixed station
- NodeB NodeB
- eNB eNodeB
- gNB gNodeB
- Access point "Transmission point (Transmission Point (TP))
- Reception point Reception Point
- TRP Transmission / Reception Point
- Panel , "Cell”, “sector”, “cell group”, “carrier”, “component carrier” and the like
- Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.
- the base station can accommodate one or more (eg, 3) cells.
- a base station accommodates multiple cells, the entire base station coverage area can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a small indoor base station (Remote Radio). Communication services can also be provided by Head (RRH))).
- RRH Head
- the term "cell” or “sector” refers to part or all of the coverage area of at least one of a base station and a base station subsystem that provides communication services in this coverage.
- MS mobile station
- UE user equipment
- terminal terminal
- Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , Handset, user agent, mobile client, client or some other suitable term.
- At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like.
- At least one of the base station and the mobile station may be a device mounted on the mobile body, a mobile body itself, or the like.
- the moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ) May be.
- at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation.
- at least one of the base station and the 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 by the user terminal.
- communication between a base station and a user terminal has been replaced with communication between a plurality of user terminals (for example, it may be referred to as Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.).
- D2D Device-to-Device
- V2X Vehicle-to-Everything
- Each aspect / embodiment of the present disclosure may be applied to the configuration.
- the user terminal 20 may have the function of the base station 10 described above.
- words such as "uplink” and "downlink” may be read as words corresponding to communication between terminals (for example, "sidelink”).
- the uplink channel, the downlink channel, and the like may be read as the side link channel.
- the user terminal in the present disclosure may be read as a base station.
- the base station 10 may have the functions of the user terminal 20 described above.
- the operation performed by the base station may be performed by its upper node (upper node) in some cases.
- various operations performed for communication with a terminal are a base station, one or more network nodes other than the base station (for example,).
- Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. can be considered, but it is not limited to these), or it is clear that it can be performed by a combination thereof.
- Each aspect / embodiment described in the present disclosure may be used alone, in combination, or may be switched and used according to the execution. Further, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in the present disclosure present elements of various steps using exemplary order, and are not limited to the particular order presented.
- LTE Long Term Evolution
- LTE-A LTE-Advanced
- SUPER 3G IMT-Advanced
- 4G 4th generation mobile communication system
- 5G 5th generation mobile communication system
- 6G 6th generation mobile communication system
- xG xG (xG (x is, for example, an integer or a fraction)
- Future Radio Access FAA
- RAT New -Radio Access Technology
- NR New Radio
- NX New radio access
- FX Future generation radio access
- GSM registered trademark
- CDMA2000 Code Division Multiple Access
- UMB Ultra Mobile Broadband
- UMB Ultra Mobile Broadband
- LTE 802.11 Wi-Fi®
- LTE 802.16 WiMAX®
- LTE 802.20 Ultra-WideBand (UWB), Bluetooth®, and other suitable radios.
- UMB Ultra Mobile Broadband
- references to elements using designations such as “first” and “second” as used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not mean that only two elements can be adopted or that the first element must somehow precede the second element.
- determining used in this disclosure may include a wide variety of actions.
- judgment (decision) means judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigation (investigating), search (looking up, search, inquiry) ( For example, searching in a table, database or another data structure), ascertaining, etc. may be considered to be “judgment (decision)”.
- judgment (decision) includes receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access (for example). It may be regarded as “determining” such as accessing) (for example, accessing data in memory).
- judgment (decision) is regarded as “judgment (decision)” of solving, selecting, selecting, establishing, comparing, and the like. May be good. That is, “judgment (decision)” may be regarded as “judgment (decision)” of some action.
- the "maximum transmission power" described in the present disclosure may mean the maximum value of the transmission power, may mean the nominal UE maximum transmit power, or may mean the rated maximum transmission power (the). It may mean rated UE maximum transmit power).
- connection are any direct or indirect connections or connections between two or more elements. Means, and can include the presence of one or more intermediate elements between two elements that are “connected” or “bonded” to each other.
- the connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection” may be read as "access”.
- the radio frequency region when two elements are connected, one or more wires, cables, printed electrical connections, etc. are used, and as some non-limiting and non-comprehensive examples, the radio frequency region, microwaves. It can be considered to be “connected” or “coupled” to each other using electromagnetic energy having wavelengths in the region, light (both visible and invisible) regions, and the like.
- the term "A and B are different” may mean “A and B are different from each other”.
- the term may mean that "A and B are different from C”.
- Terms such as “separate” and “combined” may be interpreted in the same way as “different”.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
将来の無線通信システム(例えば、Rel.15以降、5G、NRなど)では、uplink control information(UCI)の送信に用いられる上りリンク制御チャネル(例えば、PUCCH)用の構成(フォーマット、PUCCHフォーマット(PF)等ともいう)が検討されている。例えば、Rel.15 NRでは、5種類のPF0~4をサポートすることが検討されている。なお、以下に示すPFの名称は例示にすぎず、異なる名称が用いられてもよい。
NRでは、ユーザ端末(UE:User Equipment)は、下り共有チャネル(Physical Downlink Shared Channel(PDSCH)等ともいう)に対する送達確認情報(Hybrid Automatic Repeat reQuest-ACKnowledge(HARQ-ACK)、ACKnowledge/Non-ACK(ACK/NACK)、HARQ-ACK情報又は、A/N等ともいう)をフィードバック(報告(report)又は送信等ともいう)するメカニズムが検討されている。
Rel.16までのNRにおいて、NWからUEに対する信号及びチャネルの少なくとも一方(以下、信号/チャネルと表現する)の送信は、ユニキャスト送信が基本である。この場合、NWから複数のUEに対して送信される同一の下りリンク(DL)データ信号/チャネル(例えば、下りリンク共有チャネル(PDSCH))を、NWの複数のビーム(又は、パネル)に対応する複数の受信機会(受信オケージョン)を用いて、各UEが受信することが想定される。
PDSCHの復号に成功したUEは、ACKを送信する。PDSCHの復号に失敗したUEは、NACKを送信する。
PDSCHの復号に成功したUEは、ACKを送信しない。PDSCHの復号に失敗したUEは、NACKを送信する。
マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCHに対し、送信に用いられるPUCCHリソースが複数UE間において共有される(共通である)場合の、あるUEにおいて、そのPUCCHと時間ドメインにおいて衝突するPUSCHが存在する場合(図3)のUE動作が明らかでない。
マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCHに対し、NACK-onlyフィードバックが設定/指示された場合の、あるUEにおいて、そのPUCCHリソースと時間ドメインにおいて衝突するULチャネルが存在する場合(図4)のUE動作が明らかでない。
ユニキャストPDSCHに対応するHARQ-ACKと、マルチキャストPDSCHに対応するHARQ-ACKと、に係る衝突に対するUE動作が明らかでない。この衝突は、以下のケース1から3の少なくとも1つであってもよい。
[[ケース1]]ユニキャストPDSCHに対応するHARQ-ACKを含むPUCCH Aと、マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCH Bと、が衝突する(図5A)。
[[ケース2]]ユニキャストPDSCHに対応するHARQ-ACKを含むPUCCH Aと、PUSCHと、が衝突し、マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCH Bと、同じPUSCHと、が衝突する。PUCCH AとPUCCH Bは衝突しない(図5B)。
[[ケース3]]ユニキャストPDSCHに対応するHARQ-ACKを含むPUCCH Aと、PUCCH Cと、が衝突し、マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCH Bと、PUCCH Cと、が衝突する。PUCCH AとPUCCH Bは衝突しない(図5C)。
マルチキャストPDSCHに対応するHARQ-ACK送信のためのPUCCHと、別のULチャネルとが、少なくとも時間ドメインにおいてオーバーラップする場合、UEは、条件に基づいてオーバーラップ解決を行う。
マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCHに対し、そのPUCCHリソースが複数UE間において共有される(共通である)場合の、あるUEにおいて、そのPUCCHと時間ドメインにおいて衝突するPUSCHが存在する場合(図3、問題1)、UEは、以下の態様1-1から1-8の少なくとも1つに従ってもよい。
UEは、そのHARQ-ACKをそのPUSCHへマップし(PUSCHにおいてHARQ-ACKとデータ(UL-SCH)を多重し)、そのPUCCHを送信しない。
UEは、そのHARQ-ACKをそのPUSCHへマップせず、そのPUCCHを送信する。UEは、そのPUSCHを送信してもよいし、そのPUSCHを送信しなくてもよい。
UEは、そのHARQ-ACKをそのPUSCHへマップし、同時にそのPUCCHを送信する。
UEは、そのHARQ-ACKをそのPUSCHへマップせず、そのPUCCHも送信しない。UEは、そのPUSCHを送信してもよいし、そのPUSCHを送信しなくてもよい。
UEは、HARQ-ACK送信方法がACK/NACKフィードバックであるかNACK-onlyフィードバックであるかに基づいて、態様1-1から1-4のいずれかを用いる(決定/適用/選択する)。
UEは、そのHARQ-ACKのビット数に基づいて、態様1-1から1-4のいずれかを用いる(決定/適用/選択する)。
UEは、そのPUCCHのPUCCHフォーマットに基づいて、態様1-1から1-4のいずれかを用いる(決定/適用/選択する)。
UEは、RRCパラメータ/MAC CE/DCIフォーマット/DCIフィールド/PDCCH(DCIのCRC)スクランブリングRNTI/CORESET/サーチスペース/UE能力に基づいて、態様1-1から1-4のいずれかを用いる(決定/適用/選択する)。
マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCHに対し、NACK-onlyフィードバックが設定/指示された場合の、あるUEにおいて、そのPUCCHリソースと時間ドメインにおいて衝突するULチャネルが存在する場合(図4、問題2)において、UEは、以下の態様2a及び2bの少なくとも1つに従ってもよい。
マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCHと時間ドメインにおいて衝突するULチャネルが、PUSCHである場合、UEは、以下の態様2a-1から2a-12の少なくとも1つに従ってもよい。
UEは、そのHARQ-ACKをそのPUSCHへマップし(PUSCHにおいてHARQ-ACKとデータ(UL-SCH)を多重し)、そのPUCCHを送信しない。
UEは、そのHARQ-ACKをそのPUSCHへマップせず、そのPUCCHを送信する。UEは、そのPUSCHを送信してもよいし、そのPUSCHを送信しなくてもよい。
UEは、そのHARQ-ACKをそのPUSCHへマップし、同時にそのPUCCHを送信する。
UEは、そのHARQ-ACKをそのPUSCHへマップせず、そのPUCCHも送信しない。UEは、そのPUSCHを送信してもよいし、そのPUSCHを送信しなくてもよい。
UEは、そのPDSCHの受信/復号が成功したか否か(NACKが生成されるか否か)に応じて、態様2a-1から2a-4のいずれかを用いる(決定/適用/選択する)。
UEは、そのHARQ-ACKのビット数に基づいて、態様2a-1から2a-3のいずれかを用いる(決定/適用/選択する)。
UEは、そのPUCCHのPUCCHフォーマットに基づいて、態様2a-1から2a-4のいずれかを用いる(決定/適用/選択する)。
UEは、RRCパラメータ/MAC CE/DCIフォーマット/DCIフィールド/PDCCH(DCIのCRC)スクランブリングRNTI/CORESET/サーチスペース/UE能力に基づいて、態様2a-1から2a-4のいずれかを用いる(決定/適用/選択する)。
そのHARQ-ACKがそのPUSCHにマップされる場合、マッピング(多重)方法は、ユニキャストPDSCHのHARQ-ACKをPUSCHへマップする方法と異なる。
そのPUSCHをスケジュールするULグラント(DCI)におけるUL DAIは、HARQ-ACKをPUSCHへマップすることを想定した値であってもよい。そのPUSCHをスケジュールするULグラント(DCI)におけるUL DAIは、HARQ-ACKをPUSCHへマップしないことを想定した値であってもよい。
UEは、そのPDSCHの受信/復号が成功し、HARQ-ACKを送信する(HARQ-ACKの送信機会がある)場合、ACKを送信してもよい。例えば、UEは、PUCCHと衝突するPUSCHを送信することを決定した場合(例えば、態様2a-1)、UEは、マルチキャストPDSCHに対するACKを、そのPUSCHへマップしてもよい。
UEは、そのPDSCHの受信/復号が成功し、HARQ-ACKを送信する(HARQ-ACKの送信機会がある)場合、NACK-onlyフィードバックの設定/指示に関わらず、ACKを送信してもよい。例えば、UEは、PUCCHと衝突するPUSCHを送信することを決定した場合(例えば、態様2a-1)、マルチキャストPDSCHに対するNACK-onlyフィードバックの設定/指示に関わらず、マルチキャストPDSCHに対するACKを、そのPUSCHへマップしてもよい。
マルチキャストPDSCHに対応するHARQ-ACKを含むPUCCH Xと時間ドメインにおいて衝突するULチャネルがPUCCH Yである場合、UEは、以下の態様2b-1から2b-9の少なくとも1つに従ってもよい。PUCCH Yは、scheduling request(SR)及びchannel state information(CSI)の少なくとも1つを含んでもよい。
UEは、PUCCH X及びPUCCH Yを、PUCCH Xと、PUCCH Yと、別のPUCCH Zと、の少なくとも1つのPUCCHへ多重する。UEは、PUCCH XのUCI(例えば、HARQ-ACK)と、PUCCH YのUCI(例えば、SR/CSI)とを、PUCCH XとPUCCH YとPUCCH Zとの少なくとも1つへマップしてもよい。PUCCH XとPUCCH YとPUCCH Zとのうち、UCI(HARQ-ACK)をマップするPUCCHは、仕様に規定されてもよいし、より高い優先度に関連付けられたPUCCHであってもよい。UEは、PUCCH XとPUCCH Yの一方又は両方を送信しなくてもよい。
UEは、PUCCH X及びPUCCH Yの一方を送信し、他方をドロップする。PUCCH X及びPUCCH Yのいずれを優先して送信するかは、仕様に規定されてもよい。PUCCH X及びPUCCH Yのそれぞれが優先度に関連付けられてもよい(PUCCH X及びPUCCH YのそれぞれをスケジュールするDCIが優先度(priority indicator field)を含んでもよい)。PUCCH Xの優先度とPUCCH Yの優先度とが等しい場合、UEは、PUCCH X及びPUCCH Yのうち、仕様に規定された一方を優先してもよい。PUCCH Xの優先度とPUCCH Yの優先度とが異なる場合、PUCCH X及びPUCCH Yのうち、高い優先度を有するPUCCHを優先してもよい。
UEは、PUCCH X及びPUCCH Yを多重せず(PUCCH Xに対するUCIをPUCCH Xへマップし、PUCCH Yに対するUCIをPUCCH Yへマップし)、PUCCH X及びPUCCH Yを(同時)送信する。
UEは、そのPDSCHの受信/復号が成功したか否か(NACKが生成されるか否か)に応じて、態様2b-1から2b-3のいずれかを用いる(決定/適用/選択する)。
UEは、そのHARQ-ACKのビット数、又は、PUCCH Xに対するUCIとPUCCH Yに対するUCIとの総ビット数に基づいて、態様2b-1から2b-3のいずれかを用いる(決定/適用/選択する)。
UEは、PUCCH X及びPUCCH Yの少なくとも1つのPUCCHフォーマットに基づいて、態様2b-1から2b-3のいずれかを用いる(決定/適用/選択する)。
UEは、RRCパラメータ/MAC CE/DCIフォーマット/DCIフィールド/PDCCH(DCIのCRC)スクランブリングRNTI/CORESET/サーチスペース/UE能力に基づいて、態様2b-1から2b-3のいずれかを用いる(決定/適用/選択する)。
UEは、そのPDSCHの受信/復号が成功し、HARQ-ACKを送信する(HARQ-ACKの送信機会がある)場合、PUCCH Xと、PUCCH Yと、別のPUCCH Zと、の少なくとも1つにおいてACKを送信してもよい。例えば、UEは、PUCCH Xと衝突するPUCCH Yを送信することを決定した場合、マルチキャストPDSCHに対するACKを、PUCCH Yへマップしてもよい。
UEは、そのPDSCHの受信/復号が成功し、HARQ-ACKを送信する(HARQ-ACKの送信機会がある)場合、NACK-onlyフィードバックの設定/指示に関わらず、ACKを送信してもよい。例えば、UEは、PUCCH Xと衝突するPUCCH Yを送信することを決定した場合、マルチキャストPDSCHに対するNACK-onlyフィードバックの設定/指示に関わらず、マルチキャストPDSCHに対するACKを、PUCCH Yへマップしてもよい。
ユニキャストPDSCHに対応するHARQ-ACKと、マルチキャストPDSCHに対応するHARQ-ACKと、に係る衝突に対し、UEは、以下の態様3aから3cの少なくとも1つに従ってもよい。
ユニキャストPDSCHに対応するHARQ-ACK Aを含むPUCCH Aと、マルチキャストPDSCHに対応するHARQ-ACK Bを含むPUCCH Bと、が時間ドメインにおいて衝突する場合(図5A、問題3のケース1)、UEは、以下の態様3a-1から3a-7の少なくとも1つに従ってもよい。
UEは、HARQ-ACK A及びHARQ-ACK Bを、PUCCH Aと、PUCCH Bと、別のPUCCH Cと、の少なくとも1つのPUCCHへ多重する。UEは、HARQ-ACK A及びHARQ-ACK Bを、PUCCH AとPUCCH BとPUCCH Cとの少なくとも1つのPUCCHへマップし、PUCCH AとPUCCH BとPUCCH Cとの少なくとも1つのPUCCHを送信してもよい。PUCCH AとPUCCH BとPUCCH Cとのうち、HARQ-ACKをマップするPUCCHは、仕様に規定されてもよいし、より高い優先度に関連付けられたPUCCHであってもよい。UEは、PUCCH AとPUCCH Bの一方又は両方を送信しなくてもよい。
UEは、PUCCH A及びPUCCH B(HARQ-ACK A及びHARQ-ACK B)の一方を送信し、他方をドロップする。HARQ-ACK A及びHARQ-ACK Bのいずれを優先して送信するかは、仕様に規定されてもよい。HARQ-ACK A及びHARQ-ACK Bのそれぞれが優先度に関連付けられてもよいを有してもよい(PUCCH A及びPUCCH BのそれぞれをスケジュールするDCIが優先度(priority indicator field)を含んでもよい)。HARQ-ACK Aの優先度とPUCCH Bの優先度とが等しい場合、UEは、HARQ-ACK A及びHARQ-ACK Bのうち、仕様に規定された一方を優先してもよい。HARQ-ACK Aの優先度とPUCCH Bの優先度とが異なる場合、UEは、HARQ-ACK A及びHARQ-ACK Bのうち、より高い優先度を有するHARQ-ACKを優先してもよい。
UEは、HARQ-ACK A及びHARQ-ACK Bを多重せず(HARQ-ACK AをPUCCH Aへマップし、HARQ-ACK BをPUCCH Bへマップし)、PUCCH A及びPUCCH Bを(同時)送信する。
UEは、HARQ-ACK A及びHARQ-ACK Bのそれぞれのビット数、又は、HARQ-ACK A及びHARQ-ACK B(PUCCH A及びPUCCH BのUCI)の総ビット数に基づいて、態様3a-1から3a-3のいずれかを用いる(決定/適用/選択する)。
UEは、PUCCH A及びPUCCH Bの少なくとも1つのPUCCHフォーマットに基づいて、態様3a-1から3a-3のいずれかを用いる(決定/適用/選択する)。
UEは、RRCパラメータ/MAC CE/DCIフォーマット/DCIフィールド/PDCCH(DCIのCRC)スクランブリングRNTI/CORESET/サーチスペース/UE能力に基づいて、態様3a-1から3a-3のいずれかを用いる(決定/適用/選択する)。
UEは、HARQ-ACKコードブックタイプに基づいて、態様3a-1から3a-3のいずれかを用いる(決定/適用/選択する)。
ユニキャストPDSCHに対応するHARQ-ACKを含むPUCCH Aと、PUSCHと、が時間ドメインにおいて衝突し、且つマルチキャストPDSCHに対応するHARQ-ACKを含むPUCCH Bと、同じPUSCHと、が時間ドメインにおいて衝突し、PUCCH A及びPUCCH Bが時間ドメインにおいて衝突しない場合(図5B、問題3のケース2)、UEは、以下の態様3b-1から3b-9の少なくとも1つに従ってもよい。
UEは、そのPUSCHにおいてHARQ-ACK A及びHARQ-ACK Bを、そのPUSCHへ多重する。UEは、HARQ-ACK A及びHARQ-ACK Bを、そのPUSCHへマップし、そのPUSCHを送信する。UEは、PUCCH A及びPUCCH Bの少なくとも1つを送信しなくてもよい。
UEは、HARQ-ACK A及びHARQ-ACK Bの一方をドロップし、他方をドそのPUSCHへマップし、そのPUSCHを送信する。HARQ-ACK A及びHARQ-ACK Bのいずれを優先して送信するかは、仕様に規定されてもよい。HARQ-ACK A及びHARQ-ACK Bのそれぞれが優先度に関連付けられてもよいを有してもよい(PUCCH A及びPUCCH BのそれぞれをスケジュールするDCIが優先度(priority indicator field)を含んでもよい)。HARQ-ACK Aの優先度とPUCCH Bの優先度とが等しい場合、UEは、HARQ-ACK A及びHARQ-ACK Bのうち、仕様に規定された一方を優先してもよい。HARQ-ACK Aの優先度とPUCCH Bの優先度とが異なる場合、UEは、HARQ-ACK A及びHARQ-ACK Bのうち、より高い優先度を有するHARQ-ACKを優先してもよい。
UEは、HARQ-ACK A及びHARQ-ACK Bを多重せず(HARQ-ACK AをPUCCH Aへマップし、HARQ-ACK BをPUCCH Bへマップし)、PUCCH AとPUCCH BとそのPUSCHとを(同時)送信する。
UEは、HARQ-ACK A及びHARQ-ACK Bを多重せず(HARQ-ACK AをPUCCH Aへマップし、HARQ-ACK BをPUCCH Bへマップし)、PUCCH A及びPUCCH Bを送信し、そのPUSCHをドロップする。
UEは、HARQ-ACK A及びHARQ-ACK Bのそれぞれのビット数、又は、HARQ-ACK A及びHARQ-ACK B(PUCCH A及びPUCCH BのUCI)の総ビット数に基づいて、態様3b-1から3b-4のいずれかを用いる(決定/適用/選択する)。
UEは、PUCCH A及びPUCCH Bの少なくとも1つのPUCCHフォーマットに基づいて、態様3b-1から3b-4のいずれかを用いる(決定/適用/選択する)。
UEは、RRCパラメータ/MAC CE/DCIフォーマット/DCIフィールド/PDCCH(DCIのCRC)スクランブリングRNTI/CORESET/サーチスペース/UE能力に基づいて、態様3b-1から3b-4のいずれかを用いる(決定/適用/選択する)。
UEは、HARQ-ACKコードブックタイプに基づいて、態様3b-1から3b-4のいずれかを用いる(決定/適用/選択する)。
そのPUSCHをスケジュールするULグラント(DCI)におけるUL DAIは、送信するHARQ-ACKに対応する値である。例えば、態様3b-1において、HARQ-ACK A及びHARQ-ACK Bの両方から求まる1つ(1セット)のUL DAIがULグラントに含まれてもよいし、HARQ-ACK A及びHARQ-ACK Bからそれぞれ求まる2つ(2セット)のUL DAIがULグラントに含まれてもよい。UEは、UL DAIに基づいてHARQ-ACKをそのPUSCHへマップしてもよい。
ユニキャストPDSCHに対応するHARQ-ACKを含むPUCCH Aと、PUCCH Cと、が時間ドメインにおいて衝突し、且つマルチキャストPDSCHに対応するHARQ-ACKを含むPUCCH Bと、PUCCH Cと、が時間ドメインにおいて衝突し、PUCCH A及びPUCCH Bが時間ドメインにおいて衝突しない場合(図5C、問題3のケース3)、UEは、以下の態様3c-1から3c-8の少なくとも1つに従ってもよい。
UEは、HARQ-ACK Aと、HARQ-ACK Bと、PUCCH CのUCIと、多重し、PUCCH Aと、PUCCH Bと、PUCCH Cと、別のPUCCH Dと、の少なくとも1つのPUCCHを送信する。UEは、HARQ-ACK Aと、HARQ-ACK Bと、PUCCH CのUCIと、の少なくとも2つを、PUCCH AとPUCCH BとPUCCH CとPUCCH Dとの少なくとも1つのPUCCHへマップし、PUCCH AとPUCCH BとPUCCH CとPUCCH Dとの少なくとも1つのPUCCHを送信してもよい。PUCCH AとPUCCH BとPUCCH CとPUCCH Dとのうち、HARQ-ACK Aと、HARQ-ACK Bと、PUCCH CのUCIと、をマップするPUCCHは、仕様に規定されてもよいし、より高い優先度に関連付けられたPUCCHであってもよい。UEは、PUCCH AとPUCCH BとPUCCH Cとの少なくとも1つを送信しなくてもよい。
UEは、HARQ-ACK A及びHARQ-ACK Bの一方をドロップし、他方をドPUCCH C又は別のPUCCH Dへマップし、PUCCH C又はPUCCH Dを送信する。HARQ-ACK A及びHARQ-ACK Bのいずれを優先して送信するかは、仕様に規定されてもよい。HARQ-ACK A及びHARQ-ACK Bのそれぞれが優先度に関連付けられてもよいを有してもよい(PUCCH A及びPUCCH BのそれぞれをスケジュールするDCIが優先度(priority indicator field)を含んでもよい)。HARQ-ACK Aの優先度とPUCCH Bの優先度とが等しい場合、UEは、HARQ-ACK A及びHARQ-ACK Bのうち、仕様に規定された一方を優先してもよい。HARQ-ACK Aの優先度とPUCCH Bの優先度とが異なる場合、UEは、HARQ-ACK A及びHARQ-ACK Bのうち、より高い優先度を有するHARQ-ACKを優先してもよい。
UEは、HARQ-ACK A及びHARQ-ACK Bを多重せず(HARQ-ACK AをPUCCH Aへマップし、HARQ-ACK BをPUCCH Bへマップし)、PUCCH AとPUCCH BとPUCCH Cとを(同時)送信する。
UEは、HARQ-ACK A及びHARQ-ACK Bを多重せず(HARQ-ACK AをPUCCH Aへマップし、HARQ-ACK BをPUCCH Bへマップし)、PUCCH A及びPUCCH Bを送信し、PUCCH Cをドロップする。
UEは、HARQ-ACK A及びHARQ-ACK Bのそれぞれのビット数、又は、HARQ-ACK A及びHARQ-ACK B(PUCCH A及びPUCCH BのUCI)の総ビット数、又はPUCCH CのUCIのビット数、又はHARQ-ACK AとHARQ-ACK BとPUCCH CのUCIと(PUCCH AとPUCCH BとPUCCH CとのUCI)の総ビット数、に基づいて、態様3c-1から3c-4のいずれかを用いる(決定/適用/選択する)。
UEは、PUCCH A及びPUCCH Bの少なくとも1つのPUCCHフォーマットに基づいて、態様3c-1から3c-4のいずれかを用いる(決定/適用/選択する)。
UEは、RRCパラメータ/MAC CE/DCIフォーマット/DCIフィールド/PDCCH(DCIのCRC)スクランブリングRNTI/CORESET/サーチスペース/UE能力に基づいて、態様3c-1から3c-4のいずれかを用いる(決定/適用/選択する)。
UEは、HARQ-ACKコードブックタイプに基づいて、態様3c-1から3c-4のいずれかを用いる(決定/適用/選択する)。
第1から第3の実施形態における少なくとも1つの機能(特徴、feature)に対応する上位レイヤパラメータ(RRC情報要素)/UE能力(capability)が規定されてもよい。UE能力は、この機能をサポートすることを示してもよい。
以下、本開示の一実施形態に係る無線通信システムの構成について説明する。この無線通信システムでは、本開示の上記各実施形態に係る無線通信方法のいずれか又はこれらの組み合わせを用いて通信が行われる。
図7は、一実施形態に係る基地局の構成の一例を示す図である。基地局10は、制御部110、送受信部120、送受信アンテナ130及び伝送路インターフェース(transmission line interface)140を備えている。なお、制御部110、送受信部120及び送受信アンテナ130及び伝送路インターフェース140は、それぞれ1つ以上が備えられてもよい。
図8は、一実施形態に係るユーザ端末の構成の一例を示す図である。ユーザ端末20は、制御部210、送受信部220及び送受信アンテナ230を備えている。なお、制御部210、送受信部220及び送受信アンテナ230は、それぞれ1つ以上が備えられてもよい。
なお、上記実施形態の説明に用いたブロック図は、機能単位のブロックを示している。これらの機能ブロック(構成部)は、ハードウェア及びソフトウェアの少なくとも一方の任意の組み合わせによって実現される。また、各機能ブロックの実現方法は特に限定されない。すなわち、各機能ブロックは、物理的又は論理的に結合した1つの装置を用いて実現されてもよいし、物理的又は論理的に分離した2つ以上の装置を直接的又は間接的に(例えば、有線、無線などを用いて)接続し、これら複数の装置を用いて実現されてもよい。機能ブロックは、上記1つの装置又は上記複数の装置にソフトウェアを組み合わせて実現されてもよい。
なお、本開示において説明した用語及び本開示の理解に必要な用語については、同一の又は類似する意味を有する用語と置き換えてもよい。例えば、チャネル、シンボル及び信号(シグナル又はシグナリング)は、互いに読み替えられてもよい。また、信号はメッセージであってもよい。参照信号(reference signal)は、RSと略称することもでき、適用される標準によってパイロット(Pilot)、パイロット信号などと呼ばれてもよい。また、コンポーネントキャリア(Component Carrier(CC))は、セル、周波数キャリア、キャリア周波数などと呼ばれてもよい。
Claims (6)
- マルチキャスト物理下りリンク共有チャネル(PDSCH)に対するhybrid automatic repeat reQuest acknowledgement(HARQ-ACK)情報の送信のための物理上りリンク制御チャネル(PUCCH)が、時間ドメインにおいて上りリンクチャネルとオーバーラップする場合、前記PUCCHと前記上りリンクチャネルとの少なくとも1つのチャネルを決定する制御部と、
前記チャネルを送信する送信部と、を有する端末。 - 前記PUCCHのリソースは、複数の端末の間において共有される、請求項1に記載の端末。
- 前記PUCCHに対し、negative acknowledgement(NACK)のみを送信する方法が適用される、請求項1に記載の端末。
- 前記上りリンクチャネルは、ユニキャストPDSCHに対する第2HARQ-ACK情報の送信のための第2PUCCHと、前記第2PUCCHと時間ドメインにおいてオーバーラップするチャネルと、のいずれかである、請求項1に記載の端末。
- マルチキャスト物理下りリンク共有チャネル(PDSCH)に対するhybrid automatic repeat reQuest acknowledgement(HARQ-ACK)情報の送信のための物理上りリンク制御チャネル(PUCCH)が、時間ドメインにおいて上りリンクチャネルとオーバーラップする場合、前記PUCCHと前記上りリンクチャネルとの少なくとも1つのチャネルを決定するステップと、
前記チャネルを送信するステップと、を有する、端末の無線通信方法。 - マルチキャスト物理下りリンク共有チャネル(PDSCH)に対するhybrid automatic repeat reQuest acknowledgement(HARQ-ACK)情報の送信のための物理上りリンク制御チャネル(PUCCH)が、時間ドメインにおいて上りリンクチャネルとオーバーラップする場合、前記PUCCHと前記上りリンクチャネルとの少なくとも1つのチャネルを決定する制御部と、
前記チャネルを受信する受信部と、を有する基地局。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202080108405.0A CN116848882A (zh) | 2020-12-21 | 2020-12-21 | 终端、无线通信方法以及基站 |
PCT/JP2020/047766 WO2022137304A1 (ja) | 2020-12-21 | 2020-12-21 | 端末、無線通信方法及び基地局 |
JP2022570789A JPWO2022137304A5 (ja) | 2020-12-21 | 端末、無線通信方法、基地局及びシステム |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2020/047766 WO2022137304A1 (ja) | 2020-12-21 | 2020-12-21 | 端末、無線通信方法及び基地局 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022137304A1 true WO2022137304A1 (ja) | 2022-06-30 |
Family
ID=82159116
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2020/047766 WO2022137304A1 (ja) | 2020-12-21 | 2020-12-21 | 端末、無線通信方法及び基地局 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN116848882A (ja) |
WO (1) | WO2022137304A1 (ja) |
-
2020
- 2020-12-21 CN CN202080108405.0A patent/CN116848882A/zh active Pending
- 2020-12-21 WO PCT/JP2020/047766 patent/WO2022137304A1/ja active Application Filing
Non-Patent Citations (1)
Title |
---|
CMCC: "Discussion on reliability improvement", 3GPP DRAFT; R1-2008035, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20201026 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051945323 * |
Also Published As
Publication number | Publication date |
---|---|
JPWO2022137304A1 (ja) | 2022-06-30 |
CN116848882A (zh) | 2023-10-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020110244A1 (ja) | ユーザ端末及び無線通信方法 | |
US20220191900A1 (en) | User terminal and radio communication method | |
WO2020188822A1 (ja) | ユーザ端末及び無線通信方法 | |
JP2023182693A (ja) | 端末、無線通信方法、基地局及びシステム | |
JPWO2020166025A1 (ja) | ユーザ端末及び無線通信方法 | |
WO2020235454A1 (ja) | ユーザ端末及び無線通信方法 | |
JP7197678B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
JP7337837B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
WO2020202478A1 (ja) | ユーザ端末及び無線通信方法 | |
WO2020194400A1 (ja) | ユーザ端末及び無線通信方法 | |
WO2022130629A1 (ja) | 端末、無線通信方法及び基地局 | |
JPWO2020166023A1 (ja) | ユーザ端末及び無線通信方法 | |
JP7355812B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
JP7351921B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
JP7490641B2 (ja) | 端末、無線通信方法及びシステム | |
JP7273140B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
JP2023156318A (ja) | 端末、無線通信方法及びシステム | |
WO2022074802A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2021205572A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2020235453A1 (ja) | ユーザ端末及び無線通信方法 | |
JP7230179B2 (ja) | 端末、無線通信方法及びシステム | |
JP7265001B2 (ja) | 端末、無線通信方法及びシステム | |
WO2022137304A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022137402A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022130630A1 (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: 20966802 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022570789 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202080108405.0 Country of ref document: CN |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20966802 Country of ref document: EP Kind code of ref document: A1 |