WO2021176723A1 - 端末、無線通信方法及び基地局 - Google Patents
端末、無線通信方法及び基地局 Download PDFInfo
- Publication number
- WO2021176723A1 WO2021176723A1 PCT/JP2020/009851 JP2020009851W WO2021176723A1 WO 2021176723 A1 WO2021176723 A1 WO 2021176723A1 JP 2020009851 W JP2020009851 W JP 2020009851W WO 2021176723 A1 WO2021176723 A1 WO 2021176723A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- harq
- ack
- dci
- transmission
- resource
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
- H04L1/1816—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of the same, encoded, message
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1858—Transmission or retransmission of more than one copy of acknowledgement message
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1854—Scheduling and prioritising arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1861—Physical mapping arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1867—Arrangements specially adapted for the transmitter end
- H04L1/1896—ARQ related signaling
-
- 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/04—Wireless resource allocation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
Definitions
- This disclosure relates to terminals, wireless communication methods and base stations in next-generation mobile communication systems.
- LTE Long Term Evolution
- 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), New Radio (NR), 3GPP Rel.15 or later, etc.) is also being considered.
- 5G 5th generation mobile communication system
- 5G + plus
- NR New Radio
- 3GPP Rel.15 or later, etc. is also being considered.
- a configuration in which the retransmission of the PDSCH is controlled by the UE feeding back a delivery confirmation signal (HARQ-ACK, ACK / NACK or A / N) to the DL data (for example, PDSCH) is supported. Has been done.
- future wireless communication systems for example, 5G, NR, etc.
- high speed and large capacity for example, eMBB: enhanced Mobile Broad Band
- super large number of terminals for example, mMTC: massive Machine Type Communication, IoT: Internet of Things
- Ultra-high reliability and low latency for example, URLLC: Ultra Reliable and Low Latency Communications
- multiple traffic types with different requirements also called services, types, service types, communication types, or use cases. Is expected to be mixed.
- a priority is set for a predetermined signal (for example, HARQ-ACK) according to a predetermined traffic type or requirement condition, and transmission processing or reception processing (transmission processing or reception processing) is performed based on the priority. For example, processing at the time of collision of a plurality of signals) is being studied.
- one of the purposes of the present disclosure is to provide a terminal, a wireless communication method, and a base station capable of appropriately performing communication even when communicating using a plurality of traffic types.
- the terminal When a delivery confirmation signal (HARQ-ACK) collides with another UL transmission, the terminal according to one aspect of the present disclosure includes a transmission unit that transmits the UL transmission and information regarding retransmission of the HARQ-ACK. It is characterized by having a receiving unit that receives control information and a control unit that controls retransmission of the HARQ-ACK by using the resource notified by the downlink control information.
- HARQ-ACK delivery confirmation signal
- communication can be appropriately performed even when communication is performed using a plurality of traffic types.
- FIG. 1 is a diagram showing an example of performing HARQ-ACK feedback for each service type.
- FIG. 2 is a diagram showing an example of 1-shot HARQ-ACK feedback control.
- FIG. 3 is a diagram showing an example of a case where HARQ-ACKs (or PUCCH resources) having different priorities collide.
- FIG. 4 is a diagram showing an example of retransmission control of HARQ-ACK according to the first aspect.
- FIG. 5 is a diagram showing another example of the retransmission control of HARQ-ACK according to the first aspect.
- FIG. 6 is a diagram showing an example of retransmission control of HARQ-ACK according to the second aspect.
- FIG. 7 is a diagram showing another example of the retransmission control of HARQ-ACK according to the second aspect.
- FIG. 8 is a diagram showing an example of retransmission control of HARQ-ACK according to the third aspect.
- FIG. 9 is a diagram showing an example of retransmission control of HARQ-ACK according to the fourth aspect.
- FIG. 10 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
- FIG. 11 is a diagram showing an example of the configuration of the base station according to the embodiment.
- FIG. 12 is a diagram showing an example of the configuration of the user terminal according to the embodiment.
- FIG. 13 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment.
- future wireless communication systems eg, NR
- further sophistication of mobile broadband eg enhanced Mobile Broadband (eMBB)
- machine type communication that realizes multiple simultaneous connections eg massive Machine Type Communications (mMTC)
- Traffic types also referred to as types, services, service types, communication types, use cases, etc.
- IoT of Things
- high-reliability and low-latency communications eg, Ultra-Reliable and Low-Latency Communications (URLLC)
- URLLC Ultra-Reliable and Low-Latency Communications
- the traffic type may be identified at the physical layer based on at least one of the following: -Logical channels with different priorities-Modulation and Coding Scheme (MCS) table (MCS index table) -Channel Quality Indication (CQI) table-DCI format-Used for scramble (mask) of Cyclic Redundancy Check (CRC) bits included (added) in the DCI (DCI format).
- MCS Modulation and Coding Scheme
- CQI Channel Quality Indication
- CRC Cyclic Redundancy Check
- the HARQ-ACK (or PUCCH) traffic type for PDSCH may be determined based on at least one of the following: An MCS index table (for example, MCS index table 3) used to determine at least one of the PDSCH modulation order, target code rate, and transport block size (TBS).
- An MCS index table for example, MCS index table 3
- TBS transport block size
- -RNTI used for CRC scrambling of DCI used for scheduling the PDSCH (for example, whether CRC scrambled by C-RNTI or MCS-C-RNTI).
- the traffic type may be associated with communication requirements (requirements such as delay and error rate, requirement conditions), data type (voice, data, etc.) and the like.
- the difference between the URLLC requirement and the eMBB requirement may be that the URLLC latency is smaller than the eMBB delay, or that the URLLC requirement includes a reliability requirement.
- the eMBB user (U) plane delay requirement may include that the downlink U-plane delay is 4 ms and the uplink U-plane delay is 4 ms.
- the URLLC U-plane delay requirement may include that the downlink U-plane delay is 0.5 ms and the uplink U-plane delay is 0.5 ms.
- the URLLC reliability requirement may also include a 32-byte error rate of 10-5 for a 1 ms U-plane delay.
- HARQ-ACK Codebook The UE transmits HARQ-ACK feedback using one PUCCH resource in units of HARQ-ACK codebooks composed of bits of one or more delivery confirmation information (eg, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK)). You may.
- the HARQ-ACK bit may be referred to as HARQ-ACK information, HARQ-ACK information bit, or the like.
- 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 (Transport Block (TB)). )), And a bit for HARQ-ACK in at least one unit of the code block group (Code Block Group (CBG)) constituting the TB may be included.
- the HARQ-ACK codebook may simply be referred to as a codebook.
- 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 HARQ-ACK codebook whose size is determined quasi-statically is also called a quasi-static HARQ-ACK codebook, a type 1 HARQ-ACK codebook, or the like.
- the HARQ-ACK codebook whose size is dynamically determined is also called a dynamic HARQ-ACK codebook, a type 2 HARQ-ACK 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 using the upper layer parameter (for example, pdsch-HARQ-ACK-Codebook).
- the UE has a PDSCH candidate (or PDSCH) corresponding to the predetermined range in a predetermined range (for example, a range set based on the upper layer parameter) regardless of whether PDSCH is scheduled or not.
- a 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 (occasion) for receiving a candidate PDSCH or a predetermined number of monitoring opportunities (monitoring occurrence) of the 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 whether or not spatial bundling is applied.
- the predetermined range is also referred to as a HARQ-ACK window, a HARQ-ACK bundling window, a HARQ-ACK feedback window, or the like.
- the UE allocates the HARQ-ACK bit for the PDSCH in the codebook as long as it is within a predetermined range even if there is no PDSCH scheduling for the UE.
- the UE determines that the PDSCH is not actually scheduled, the UE can feed back the bit as a NACK bit.
- the UE may feed back the HARQ-ACK bit for the scheduled PDSCH within the above predetermined range.
- the UE may determine the number of bits in the Type 2 HARQ-ACK codebook based on a predetermined field in the DCI (for example, the Downlink Assignment Indicator (Index) (DAI)) field). good.
- the DAI field may include a counter DAI (Counter DAI (C-DAI)) and a total DAI (Total DAI (T-DAI)).
- C-DAI may indicate a counter value of downlink transmission (PDSCH, data, TB) scheduled within a predetermined period.
- the C-DAI in the DCI that schedules data within the predetermined period may indicate the number counted first in the frequency domain (eg, CC) and then in the time domain within the predetermined period.
- C-DAI may correspond to a value obtained by counting PDSCH reception or SPS release in ascending order of serving cell index and then in ascending order of PDCCH monitoring opportunity for one or more DCIs included in a predetermined period.
- T-DAI may indicate the total value (total number) of data scheduled within a predetermined period.
- a T-DAI in a DCI that schedules data in a time unit (eg, PDCCH monitoring opportunity) within the predetermined period is scheduled by the time unit (also referred to as point, timing, etc.) within the predetermined period.
- the total number of data collected may be shown.
- the HARQ-ACK codebook is set separately for different service types (or PDSCH or HARQ-ACK with different priorities) (see FIG. 1). That is, it is conceivable that a plurality of HARQ-ACK codebooks are simultaneously configured to support a plurality of service types (or a plurality of priorities). For example, a first HARQ-ACK codebook (CB # 1) corresponding to URLLC (eg, first priority) and a second HARQ-ACK code corresponding to eMBB (eg, second priority). A book (CB # 2) may be constructed.
- the first PUCCH configuration parameter (for example, PUCCH configuration or PUCH configuration parameters) corresponding to the first HARQ-ACK codebook and the second PUCCH configuration parameter corresponding to the second HARQ-ACK codebook.
- the PUCCH setting parameters are the PUCCH resource (or PUCCH resource set) applied to the transmission of HARQ-ACK, the PUCCH transmission timing (for example, K1 set), the maximum coding rate (for example, max-code rate), and the PUCCH transmission. It may be at least one of the electric power.
- the first PUCCH setting information may be applied to the HARQ-ACK feedback for URLLC
- the second PUCCH setting information may be applied to the HARQ-ACK feedback for eMBB.
- HARQ process> For UEs configured with Carrier Aggregation (CA) or Dual Connectivity (DC), there may be one independent HARQ entity for each cell (CC) or cell group (CG).
- the HARQ entity may manage multiple HARQ processes in parallel.
- FIG. 1 is a diagram showing an example of the relationship between HARQ entities, HARQ processes and DCI.
- a HARQ process number (HARQ Process Number (HPN)) is given to the HARQ process.
- the DCI includes a 4-bit HARQ process number field indicating the HARQ process number used for current data transmission.
- the HARQ entity manages a plurality of (up to 16) HARQ processes in parallel. That is, the HARQ process numbers exist from HPN0 to HPN15.
- the HARQ process number is also called a HARQ process ID (HARQ process identifier).
- TB transport blocks
- MAC Media Access Control
- HARQ (retransmission) control may be performed for each TB, or for each code block group (Code Block Group (CBG)) including one or more code blocks (Code Block (CB)) in the TB. It may be done.
- CBG Code Block Group
- CB Code Block
- the user terminal outputs information indicating an acknowledgment (Positive Acknowledgement (ACK)) / negative response (Negative Acknowledgement (NACK)) of HARQ indicating whether or not the DL transport block received using the PDSCH has been successfully decoded. , PUCCH (Physical Uplink Control Channel) or PUSCH, etc. to transmit to the base station.
- ACK acknowledgement
- NACK Negative Acknowledgement
- a single HARQ process corresponds to one transport block (TB).
- TB transport block
- a single HARQ process may correspond to one or more transport blocks (TB).
- HARQ-ACK feedback ⁇ 1 shot HARQ-ACK feedback> Rel. From 16 onwards, in order to provide a transmission opportunity for HARQ-ACK feedback due to LBT failure in the UE or PUCCH detection error in the base station, the feedback of the HARQ-ACK codebook including all HARQ-ACK processes is given to the UE. Requests or triggers are being considered (see Figure 2).
- the HARQ-ACK process (eg, DL HARQ-ACK process) may be to HARQ-ACK in all CCs configured on the UE in the PUCCH group.
- FIG. 2 shows a case where the HARQ-ACK processes # 0, # 2, and # 4 are fed back in response to a request for 1-shot HARQ-ACK feedback.
- the feedback of HARQ-ACK (or HARQ-ACK codebook) including all HARQ-ACK processes in all CCs may be referred to as one-shot HARQ-ACK feedback.
- the one-shot HARQ-ACK feedback may be notified from the base station to the UE using a predetermined DCI format.
- the predetermined DCI format may be a UE-specific DCI format (eg, DCI format 1-11).
- a UE requesting or triggering one-shot HARQ-ACK feedback may use PUCCH to feed back a codebook containing a plurality of (for example, all) HARQ-ACK processes in each configured CC.
- the one-shot HARQ-ACK feedback may be referred to as a single HARQ-ACK feedback, a single HARQ-ACK feedback, a one-shot HARQ-ACK, or the like.
- NR ⁇ Priority setting> Rel.
- a plurality of levels for example, 2 levels
- communication is controlled by setting different priorities for each signal or channel corresponding to different traffic types (also referred to as services, service types, communication types, use cases, etc.) (for example, transmission control in the event of a collision). Is expected to be done. This makes it possible to control communication by setting different priorities for the same signal or channel according to the service type and the like.
- the priority may be set for a signal (for example, UCI such as HARQ-ACK, a reference signal, etc.), a channel (PDSCH, PUSCH, etc.), a HARQ-ACK codebook, or the like.
- the priority may be defined by a first priority (for example, High) and a second priority (for example, Low) that is lower than the first priority.
- a first priority for example, High
- a second priority for example, Low
- three or more types of priorities may be set.
- Information about the priority may be notified from the base station to the UE using at least one of higher layer signaling and DCI.
- priorities may be set for the dynamically scheduled HARQ-ACK for PDSCH, HARQ-ACK for semi-persistent PDSCH (SPS PDSCH), and HARQ-ACK for SPS PDSCH release.
- a priority may be set for the HARQ-ACK codebook corresponding to these HARQ-ACK.
- the priority of the PDSCH may be read as the priority of HARQ-ACK with respect to the PDSCH.
- the UE may control UL transmission based on priority when different UL signals / UL channels collide. For example, it may be controlled so that the UL transmission having a high priority is performed and the UL transmission having a low priority is not performed (for example, dropping).
- the collision of different UL signals / UL channels may be the case where the resources corresponding to the different UL signals / UL channels overlap, or the transmission timings of the different UL signals / UL channels overlap.
- the resource may be, for example, a time resource, or a time resource and a frequency resource.
- the base station uses higher layer signaling to determine whether or not a bit field (for example, Priority indicator) for notifying the priority is set to the DCI from the base station to the UE. Notifications or settings may be made.
- a bit field for example, Priority indicator
- the UE uses the first resource to transmit the first HARQ-ACK and controls so that the second HARQ-ACK is not transmitted (for example, drop).
- the DL transmission for example, PDSCH
- the HARQ-ACK for the retransmitted PDSCH for example, eMBB
- eMBB retransmitted PDSCH
- the present inventors how to transmit the plurality of HARQ-ACKs when the transmission processing or the feedback processing is controlled according to the traffic type (or priority) when a plurality of HARQ-ACKs collide. We examined whether to control it, and came up with the present embodiment.
- a / B may be read as at least one of A and B
- a / B / C may be read as at least one of A, B and C.
- the first priority (High) and the second priority (Low) are given as examples as examples, but the number and type of priorities are not limited to this. Three or more priorities (or three levels) may be applied. Further, the priority set for each signal or channel may be set for the UE by higher layer signaling or the like.
- eMBB and URLLC two service types, eMBB and URLLC, will be described as an example, but the types and number of service types are not limited to this.
- the service type may also be set in association with the priority. Further, in the following description, the drop may be read as canceled or non-transmitted.
- HARQ-ACK will be described as an example of the signal to be retransmitted, but the signal / channel to which this embodiment can be applied is not limited to HARQ-ACK.
- the present embodiment may be applied to other signals / channels.
- the UE When the UE receives a DCI (or PDCCH) instructing to retransmit a predetermined HARQ-ACK, the UE controls to retransmit (or retransmit, feed back, transmit) the predetermined HARQ-ACK based on the DCI. You may.
- the predetermined HARQ-ACK may be a HARQ-ACK that was not transmitted (eg, dropped or postponed) due to a collision with another UL transmission.
- the DCI (hereinafter, also referred to as request DCI) that instructs the retransmission of the predetermined HARQ-ACK may be a DCI that does not schedule PDSCH.
- the request DCI may be UE-specific (eg, specific or dedicated), and for example, at least one of DCI format 1-11 and DCI format 1-22 may be utilized.
- the request DCI reports the channel state information reference signal (for example, CSI-RS) / channel state information (for example, A) in addition to the configuration in which the PDSCH is not scheduled (or instead of the configuration in which the PDSCH is not scheduled).
- -CSI report may also be configured without schedule / instruction.
- the UE may determine whether or not the received DCI is a request DCI based on a predetermined field included in the DCI. For example, when a field related to a HARQ-ACK retransmission request (for example, requestHarqReTx) is set to DCI and the bit of the field is "1", it functions as a request DCI, and when the bit is "0", it functions as a request DCI. It may be a configuration that does not function as. Alternatively, other fields may be used to notify whether the request is DCI or not. Alternatively, RNTI applied to DCI may be used to notify whether or not the request DCI is made.
- a field related to a HARQ-ACK retransmission request for example, requestHarqReTx
- the UE may resend a predetermined HARQ-ACK using a predetermined resource.
- the resource used for retransmission of HARQ-ACK is at least partially different (or partially the same) from the resource set for transmitting the dropped HARQ-ACK (hereinafter, also referred to as the original HARQ-ACK). It may be a new resource.
- the resource may be read as a PUCCH resource.
- the new resource used to retransmit the HARQ-ACK is based on at least one of the HARQ-ACK timing information (eg, K1) and the PUCCH resource identifier (PUCCH Resource Indicator (PRI)) field contained in the request DCI. It may be decided.
- K1 the HARQ-ACK timing information
- PRI PUCCH Resource Indicator
- the first HARQ-ACK corresponds to the first PDSCH scheduled in the first DCI, and the first resource may be specified in the first DCI (and higher layer signaling).
- the second HARQ-ACK corresponds to the second PDSCH scheduled in the second DCI, and the second resource may be specified in the second DCI (and higher layer signaling).
- the priority of the first HARQ-ACK may be notified by the first DCI and the priority of the second HARQ-ACK may be notified by the second DCI.
- the UE uses the first resource to transmit the first HARQ-ACK and does not transmit the second HARQ-ACK (or does not transmit the HARQ-ACK using the second resource). ) May be controlled.
- the UE receives the request DCI (for example, the third DCI) instructing the retransmission of the HARQ-ACK, the UE controls to transmit the second HARQ-ACK by using the resource specified by the request DCI. You may.
- the UE may determine the HARQ-ACK (for example, the dropped second HARQ-ACK) to be retransmitted based on the request DCI based on at least one of the following options 1-1 to 1-3. good.
- the UE may control to feed back a plurality of HARQ-ACKs (for example, a plurality of HARQ-ACKs having a low priority) based on the request DCI instructing the retransmission of the HARQ-ACK.
- the base station may request (or trigger) the feedback of 1-shot HARQ-ACK from the UE by using the request DCI. That is, the HARQ-ACK bit for which retransmission is requested in the request DCI may be the DL HARQ-ACK process in all CCs set in the UE in a predetermined group (for example, PUCCH group).
- the UE for which the feedback of 1-shot HARQ-ACK is requested by the request DCI may include one or more HARQ-ACKs in one (or common) HARQ-ACK codebook to provide feedback.
- the HARQ-ACK included in one HARQ-ACK codebook may be a HARQ-ACK corresponding to a predetermined HARQ-ACK process (or a predetermined HARQ-ACK process number).
- the predetermined HARQ-ACK process may be, for example, a HARQ-ACK process corresponding to the PDSCH scheduled in the UE.
- HARQ-ACK corresponding to the HARQ-ACK process in the plurality of CCs may be included in one HARQ-ACK codebook.
- the UE may control to feed back (eg, retransmit) the latest (eg, latest) dropped HARQ-ACK based on the request DCI (see FIG. 4). That is, when there are a plurality of HARQ-ACKs that have not been transmitted, the UE controls to retransmit the HARQ-ACK that was not transmitted last (or the HARQ-ACK that was dropped last).
- HARQ-ACK # 1 (or PUCCH resource # 1) corresponding to PDSCH # 1 collides with another high-priority UL transmission (for example, PUCCH resource # 0a for URLLC) and is dropped. Shows the case.
- HARQ-ACK # 2 (or PUCCH resource # 2) corresponding to PDSCH # 2 and HARQ-ACK # 3 (or PUCCH resource # 3) corresponding to PDSCH # 3 are other UL transmissions having high priority.
- PUCCH resource # 0b for URLLC PUCCH resource # 0b for URLLC
- FIG. 4 shows a case where the request DCI is transmitted after HARQ-ACK # 2 and # 3 are dropped. That is, after HARQ-ACK # 1 is dropped, HARQ-ACK # 2 and # 3 are dropped before the request DCI is transmitted.
- the UE when the UE receives the request DCI, if there are a plurality of dropped HARQ-ACKs, the last dropped HARQ-ACK (or the HARQ- corresponding to the last PUCCH resource not used for transmission). You may control to retransmit ACK).
- the HARQ-ACK to be resent may be determined for each PUCCH resource. That is, when the HARQ-ACK corresponding to the same PUCCH resource (or the PUCCH resource set in the same slot) is dropped (HARQ-ACK # 2 and # 3 in FIG. 4), the plurality of HARQ-ACKs are used. It may be controlled to retransmit.
- the UE since HARQ-ACK # 2 and # 3 correspond to the last dropped PUCCH resource, the UE retransmits the HARQ-ACK # 2 and # 3 using the resource specified in the request DCI. It may be controlled as follows.
- the resource specified in the request DCI (for example, here, PUCCH resource # 4) is the HARQ-ACK timing information (for example, K1) and the PUCCH resource identifier (PUCCH Resource Indicator (PRI)) field included in the request DCI. It may be determined based on at least one of.
- the UE may use the resource condition (for example, PRI) set for the dropped HARQ-ACK (for example, the original HARQ-ACK). For example, the UE determines the retransmission timing (for example, retransmission slot) of HARQ-ACK based on the information regarding the HARQ-ACK timing included in the request DCI (for example, K1), and determines the already specified PRI (for example, PDSCH).
- the resource to be used for retransmission of HARQ-ACK may be determined based on the PRI notified by DCI).
- the request DCI may be configured so that the PRI is not included.
- the UE may ignore the PRI field contained in the request DCI. As a result, it is possible to suppress an increase in the overhead of the request DCI.
- the last dropped HARQ-ACK (or PUCCH resource) may be determined based on the timing at which the HARQ-ACK is transmitted (or the time domain in which the PUCCH resource is set). Alternatively, it may be determined based on the DCI transmission timing or PDSCH transmission timing corresponding to the HARQ-ACK (or PUCCH resource).
- HARQ-ACK to be retransmitted can be flexibly controlled based on the transmission timing of the request DCI. As a result, it is possible to suppress an increase in the overhead of HARQ-ACK to be retransmitted and a decrease in throughput.
- the UE may determine HARQ-ACK to perform retransmission based on the information notified from the base station.
- the information notified from the base station may be at least one of DCI and higher layer signaling.
- the UE may determine the HARQ-ACK to be retransmitted based on the request DCI instructing the retransmission of the HARQ-ACK (see FIG. 5).
- the request DCI may include information that specifies the original HARQ-ACK (original HARQ-ACK) of the HARQ-ACK to be resent.
- the case where the information regarding the offset between the request DCI and the original HARQ-ACK (or the original PUCCH resource) is included in the request DCI and notified to the UE is shown.
- HARQ-ACK # 1 (or PUCCH resource # 1) corresponding to PDSCH # 1 and HARQ-ACK # 2 (or PUCCH resource # 2) corresponding to PDSCH # 2 have other high priorities. It shows the case where it collides with UL transmission (for example, PUCCH resource # 0 for URLLC) and is dropped.
- PUCCH resource # 0 for URLLC
- the UE may control to retransmit the HARQ-ACK specified in the request DCI.
- the request DCI may specify the time interval (eg, index m) at which the HARQ-ACK (or dropped HARQ-ACK) to be resent was scheduled to be transmitted.
- the time interval may be at least one of slots, subslots or symbols.
- the request DCI may include an offset between the request DCI and the dropped HARQ-ACK (or PUCCH resource).
- the offset may be referred to as a timing offset (eg, ⁇ t).
- the UE may determine the HARQ-ACK (or the original HARQ-ACK) to be retransmitted based on the timing offset included in the request DCI.
- the timing offset (eg, ⁇ t) may be set in a new field in the request DCI (eg DCI format 1-11, or 1-2) or in an existing field (eg, time allocation field (TDRA field)). ..
- the timing offset value included in the request DCI is used to notify the interval between the slot in which the request DCI (or PDCCH) is transmitted and the slot in which the original HARQ-ACK is transmitted is shown. , Not limited to this.
- information regarding HARQ-ACK requesting retransmission may be included in the request DCI and notified to the UE.
- the UE may determine the HARQ-ACK to be retransmitted based on the information regarding the timing offset notified in the upper layer.
- the timing offset (eg, ⁇ t) may be the interval between the slot in which the request DCI (or PDCCH) is transmitted and the slot in which the original HARQ-ACK is transmitted.
- the UE may control to retransmit HARQ-ACK in slot n- ⁇ t.
- the base station may set a plurality of timing offset values (candidate values) in the UE by higher layer signaling, and notify the UE of a specific candidate value by using DCI (for example, request DCI). This makes it possible to flexibly set the timing offset.
- the UE may determine the HARQ-ACK (or original HARQ-ACK) to be retransmitted based on a preset value (eg, default value) when the timing offset is not notified by DCI or higher layer signaling. ..
- the priority of the retransmitted HARQ-ACK may be set to the same as that of the original HARQ-ACK (dropped HARQ-ACK), or may be different. Priority may be set.
- the request DCI may be configured not to include the priority information (for example, PriorityIndicator) field. As a result, it is possible to suppress an increase in the overhead of the request DCI.
- the priority information for example, PriorityIndicator
- the priority of the retransmitted HARQ-ACK may be set high. For example, even if the priority of the original HARQ-ACK (dropped HARQ-ACK) is low, a high priority (for example, high) may be set when retransmitting the dropped HARQ-ACK. .. A high priority may be set by the request DCI, or the priority of HARQ-ACK retransmitted on the UE side may be assumed to be high without including information on the priority in the request DCI. As a result, the retransmission of HARQ-ACK can be prioritized.
- the request DCI may be a DCI that schedules PDSCH.
- the request DCI may be UE-specific (eg, specific or dedicated), and for example, at least one of DCI format 1-11 and DCI format 1-22 may be utilized.
- the request DCI reports the channel state information reference signal (for example, CSI-RS) / channel state information (for example, A) in addition to the configuration for scheduling the PDSCH (or instead of the configuration for scheduling the PDSCH).
- CSI report may also be configured to schedule / instruct.
- the UE may determine whether or not the received DCI is a request DCI based on a predetermined field included in the DCI. For example, when a field related to a HARQ-ACK retransmission request (for example, requestHarqReTx) is set to DCI and the bit of the field is "1", it functions as a request DCI, and when the bit is "0", it functions as a request DCI. It may be a configuration that does not function as. Alternatively, other fields may be used to notify whether the request is DCI or not. Alternatively, RNTI applied to DCI may be used to notify whether or not the request DCI is made.
- a field related to a HARQ-ACK retransmission request for example, requestHarqReTx
- the UE may resend a predetermined HARQ-ACK using a predetermined resource.
- the new resource used to retransmit the HARQ-ACK is based on at least one of the HARQ-ACK timing information (eg, K1) and the PUCCH resource identifier (PUCCH Resource Indicator (PRI)) field contained in the request DCI. It may be decided.
- K1 the HARQ-ACK timing information
- PRI PUCCH Resource Indicator
- the first HARQ-ACK corresponds to the first PDSCH scheduled in the first DCI, and the first resource may be specified in the first DCI (and higher layer signaling).
- the second HARQ-ACK corresponds to the second PDSCH scheduled in the second DCI, and the second resource may be specified in the second DCI (and higher layer signaling).
- the priority of the first HARQ-ACK may be notified by the first DCI and the priority of the second HARQ-ACK may be notified by the second DCI.
- the UE uses the first resource to transmit the first HARQ-ACK and does not transmit the second HARQ-ACK (or does not transmit the HARQ-ACK using the second resource). ) May be controlled.
- the UE receives the request DCI (for example, the third DCI) instructing the retransmission of the HARQ-ACK, the UE controls to transmit the second HARQ-ACK by using the resource specified by the request DCI. You may.
- the UE controls the reception of the PDSCH scheduled by the request DCI.
- the HARQ-ACK for the PDSCH scheduled by the request DCI may be configured to be transmitted using a predetermined resource, or may be configured not to be transmitted.
- the UE may apply at least one of the following options 2-1 to 2-2 to the HARQ-ACK for the PDSCH scheduled in the request DCI.
- the UE may use the resource specified in the request DCI to retransmit the dropped HARQ-ACK and may not use it to transmit the HARQ-ACK to the PDSCH scheduled in the request DCI (see FIG. 6). In this case, the UE may control the request DCI not to send (or not report, drop) HARQ-ACK for the newly scheduled PDSCH.
- HARQ-ACK # 1 (or PUCCH resource # 1) corresponding to PDSCH # 1 and HARQ-ACK # 2 (or PUCCH resource # 2) corresponding to PDSCH # 2 have other high priorities. It shows the case where it collides with UL transmission (for example, PUCCH resource # 0 for URLLC) and is dropped.
- PUCCH resource # 0 for URLLC
- the case where the PUCCH resource # 1 and the PUCCH resource # 2 are the same PUCCH resource (or the PUCCH resource set in the same slot) is shown.
- FIG. 6 shows a case where the request DCI is transmitted after HARQ-ACK # 1 and # 2 are dropped. It also indicates that PDSCH # 3 is scheduled by request DCI.
- the UE controls to retransmit HARQ-ACK # 1 and # 2 by using the resource specified in the request DCI (here, PUCCH resource # 3).
- PUCCH resource # 3 the resource specified in the request DCI
- HARQ-ACK # 3 for PDSCH # 3 scheduled by the request DCI is controlled not to be transmitted in the PUCCH resource # 3.
- the UE controls not to map or multiplex the HARQ-ACK for the PDSCH scheduled by the request DCI and the HARQ-ACK for resending to the same resource (here, PUCCH resource # 3).
- HARQ-ACK # 3 may be controlled to be transmitted by another resource, or may be controlled not to be transmitted itself.
- the resource specified in the request DCI may be determined based on at least one of the K1 and PRI fields included in the request DCI. Also, the HARQ-ACK bit (or HARQ-ACK payload) transmitted by PUCCH resource # 3 takes into account the dropped HARQ-ACK or the original HARQ-ACK (without considering HARQ-ACK # 3). ) May be decided.
- the PDSCH # 3 scheduled in the request DCI or HARQ-ACK # 3 for the PDSCH # 3 may be a PDSCH or HARQ-ACK with a low priority. That is, the PDSCH scheduled in the request DCI or the priority set in HARQ-ACK for the PDSCH may be limited (for example, limited to low). As a result, it is possible to prevent the HARQ-ACK having a high priority from being transmitted or being delayed.
- the UE may use the resource specified in the request DCI to retransmit the dropped HARQ-ACK and to transmit the HARQ-ACK to the PDSCH scheduled in the request DCI (see FIG. 7).
- the UE may control the HARQ-ACK for the PDSCH newly scheduled in the request DCI and the HARQ-ACK to be retransmitted to be included in the same HARQ-ACK codebook and transmitted.
- HARQ-ACK # 1 (or PUCCH resource # 1) corresponding to PDSCH # 1 and HARQ-ACK # 2 (or PUCCH resource # 2) corresponding to PDSCH # 2 have other high priorities. It shows the case where it collides with UL transmission (for example, PUCCH resource # 0 for URLLC) and is dropped.
- PUCCH resource # 0 for URLLC
- the case where the PUCCH resource # 1 and the PUCCH resource # 2 are the same PUCCH resource (or the PUCCH resource set in the same slot) is shown.
- FIG. 7 shows a case where the request DCI is transmitted after HARQ-ACK # 1 and # 2 are dropped. It also indicates that PDSCH # 3 is scheduled by request DCI.
- the UE controls to retransmit HARQ-ACK # 1 and # 2 and transmit HARQ-ACK # 3 by using the resource specified in the request DCI (here, PUCCH resource # 3). That is, the UE controls to map or multiplex the HARQ-ACK for the PDSCH scheduled in the request DCI and the HARQ-ACK for resending to the same resource (here, PUCCH resource # 3).
- the PDSCH # 3 scheduled in the request DCI or HARQ-ACK # 3 for the PDSCH # 3 may be a PDSCH or HARQ-ACK with a low priority. That is, the PDSCH scheduled in the request DCI or the priority set in HARQ-ACK for the PDSCH may be limited (for example, limited to low). This makes it possible to match the priority of HARQ-ACK that maps or multiplexes to the same resource.
- the UE determines the HARQ-ACK (for example, the dropped second HARQ-ACK) to be retransmitted based on the request DCI based on at least one of options 1-1 to 1-3 of the first aspect. You may. That is, the UE may apply the option 2-1 or 2-2 in combination with at least one of the options 1-1 to 1-3 of the first aspect.
- the UE When the UE receives the request DCI (or PDCCH) instructing the retransmission of the predetermined HARQ-ACK, the UE so as to retransmit (or retransmit, feedback, transmit) the predetermined HARQ-ACK based on the request DCI. It may be controlled to.
- the predetermined HARQ-ACK may be a HARQ-ACK that was not transmitted (eg, dropped or postponed) due to a collision with another UL transmission.
- the request DCI may be a DCI that does not schedule UL data (eg, UL-SCH).
- the request DCI may be UE-specific (eg, specific or dedicated), and for example, at least one of DCI format 0_1 and DCI format 0_2 may be utilized.
- the request DCI reports the channel state information reference signal (for example, CSI-RS) / channel state information (for example, in addition to the configuration in which the UL data is not scheduled) (or instead of the configuration in which the UL data is not scheduled).
- CSI-RS channel state information reference signal
- A-CSI report may also be configured without schedule / instruction.
- the UE may determine whether or not the received DCI is a request DCI based on a predetermined field included in the DCI. For example, when a field related to a HARQ-ACK retransmission request (for example, requestHarqReTx) is set to DCI and the bit of the field is "1", it functions as a request DCI, and when the bit is "0", it functions as a request DCI. It may be a configuration that does not function as. Alternatively, other fields may be used to notify whether the request is DCI or not. Alternatively, RNTI applied to DCI may be used to notify whether or not the request DCI is made.
- a field related to a HARQ-ACK retransmission request for example, requestHarqReTx
- the UE may resend a predetermined HARQ-ACK using a predetermined resource.
- the resource used for retransmission of HARQ-ACK may be PUSCH scheduled or set in the request DCI.
- the resource may be read as a PUSCH resource.
- the PUSCH resource used for retransmission of HARQ-ACK may be determined based on at least one of the time allocation field and the frequency allocation field included in the request DCI. Further, HARQ-ACK to be retransmitted is mapped to the PUSCH resource, and UL data / A-CSI / SRS may not be mapped.
- the first HARQ-ACK corresponds to the first PDSCH scheduled in the first DCI, and the first resource may be specified in the first DCI (and higher layer signaling).
- the second HARQ-ACK corresponds to the second PDSCH scheduled in the second DCI, and the second resource may be specified in the second DCI (and higher layer signaling).
- the priority of the first HARQ-ACK may be notified by the first DCI and the priority of the second HARQ-ACK may be notified by the second DCI.
- the UE uses the first resource to transmit the first HARQ-ACK and does not transmit the second HARQ-ACK (or does not transmit the HARQ-ACK using the second resource). ) May be controlled.
- the UE receives the request DCI (for example, the third DCI) instructing the retransmission of the HARQ-ACK
- the UE uses the resource (for example, PUSCH) specified by the request DCI to perform the second HARQ-ACK. It may be controlled to transmit.
- the UE determines the HARQ-ACK (for example, the dropped second HARQ-ACK) to be retransmitted based on the request DCI based on at least one of options 1-1 to 1-3 of the first aspect. You may. For example, in option 1-1 to option 1-3 of the first aspect, the resource set in the request DCI may be replaced with the PUCCH resource from the PUCCH resource.
- FIG. 8 shows an example in which HARQ-ACK is retransmitted using the PUSCH resource by applying option 1-2 of the first aspect. That is, FIG. 8 shows a case where the UE controls to feed back (for example, retransmit) the latest (for example, latest) dropped HARQ-ACK based on the request DCI.
- HARQ-ACK # 1 (or PUCCH resource # 1) corresponding to PDSCH # 1 collides with another high-priority UL transmission (for example, PUCCH resource # 0a for URLLC) and is dropped. Shows the case.
- HARQ-ACK # 2 (or PUCCH resource # 2) corresponding to PDSCH # 2 and HARQ-ACK # 3 (or PUCCH resource # 3) corresponding to PDSCH # 3 are other UL transmissions having high priority.
- PUCCH resource # 0b for URLLC PUCCH resource # 0b for URLLC
- FIG. 8 shows a case where the request DCI is transmitted after HARQ-ACK # 2 and # 3 are dropped. That is, after HARQ-ACK # 1 is dropped, HARQ-ACK # 2 and # 3 are dropped before the request DCI is transmitted.
- the UE when the UE receives the request DCI, if there are a plurality of dropped HARQ-ACKs, the last dropped HARQ-ACK (or the HARQ- corresponding to the last PUCCH resource not used for transmission). You may control to retransmit ACK).
- the HARQ-ACK to be resent may be determined for each PUCCH resource. That is, when the HARQ-ACK corresponding to the same PUCCH resource (or the PUCCH resource set in the same slot) is dropped (HARQ-ACK # 2 and # 3 in FIG. 8), the plurality of HARQ-ACKs are used. It may be controlled to retransmit.
- the UE since HARQ-ACK # 2 and # 3 correspond to the last dropped PUCCH resource, the UE retransmits the HARQ-ACK # 2 and # 3 using the PUSCH resource specified in the request DCI. It may be controlled to do so.
- the resource specified in the request DCI (for example, here, the PUSCH resource) may be determined based on the PUSCH allocation information included in the request DCI.
- HARQ-ACK to be retransmitted can be flexibly controlled based on the transmission timing of the request DCI. As a result, it is possible to suppress an increase in the overhead of HARQ-ACK to be retransmitted and a decrease in throughput.
- the UE When the UE receives the request DCI (or PDCCH) instructing the retransmission of the predetermined HARQ-ACK, the UE so as to retransmit (or retransmit, feedback, transmit) the predetermined HARQ-ACK based on the request DCI. It may be controlled to.
- the predetermined HARQ-ACK may be a HARQ-ACK that was not transmitted (eg, dropped or postponed) due to a collision with another UL transmission.
- the request DCI may be a DCI that schedules UL data (eg, UL-SCH).
- the request DCI may be UE-specific (eg, specific or dedicated), and for example, at least one of DCI format 0_1 and DCI format 0_2 may be utilized.
- the request DCI reports the channel state information reference signal (for example, CSI-RS) / channel state information (for example, in addition to the configuration for scheduling UL data) in addition to the configuration for scheduling UL data (or instead of the configuration for scheduling UL data).
- CSI-RS channel state information reference signal
- A-CSI report may be scheduled / instructed.
- the UE may determine whether or not the received DCI is a request DCI based on a predetermined field included in the DCI. For example, when a field related to a HARQ-ACK retransmission request (for example, requestHarqReTx) is set to DCI and the bit of the field is "1", it functions as a request DCI, and when the bit is "0", it functions as a request DCI. It may be a configuration that does not function as. Alternatively, other fields may be used to notify whether the request is DCI or not. Alternatively, RNTI applied to DCI may be used to notify whether or not the request DCI is made.
- a field related to a HARQ-ACK retransmission request for example, requestHarqReTx
- the UE may resend a predetermined HARQ-ACK using a predetermined resource.
- the resource used for retransmission of HARQ-ACK may be PUSCH scheduled or set in the request DCI.
- the resource may be read as a PUSCH resource.
- the PUSCH resource used for retransmission of HARQ-ACK may be determined based on at least one of the time allocation field and the frequency allocation field included in the request DCI. Further, the retransmitted HARQ-ACK and UL data / A-CSI / SRS may be mapped to the PUSCH resource.
- the first HARQ-ACK corresponds to the first PDSCH scheduled in the first DCI, and the first resource may be specified in the first DCI (and higher layer signaling).
- the second HARQ-ACK corresponds to the second PDSCH scheduled in the second DCI, and the second resource may be specified in the second DCI (and higher layer signaling).
- the priority of the first HARQ-ACK may be notified by the first DCI and the priority of the second HARQ-ACK may be notified by the second DCI.
- the UE uses the first resource to transmit the first HARQ-ACK and does not transmit the second HARQ-ACK (or does not transmit the HARQ-ACK using the second resource). ) May be controlled.
- the UE receives the request DCI (for example, the third DCI) instructing the retransmission of the HARQ-ACK
- the UE uses the resource (for example, PUSCH) specified by the request DCI to perform the second HARQ-ACK. It may be controlled to transmit.
- the UE determines the HARQ-ACK (for example, the dropped second HARQ-ACK) to be retransmitted based on the request DCI based on at least one of options 1-1 to 1-3 of the first aspect. You may. For example, in option 1-1 to option 1-3 of the first aspect, the resource set in the request DCI may be replaced with the PUCCH resource from the PUCCH resource.
- FIG. 9 shows an example in which HARQ-ACK is retransmitted using the PUSCH resource by applying option 1-2 of the first aspect. That is, FIG. 9 shows a case where the UE controls to feed back (for example, retransmit) the latest (for example, latest) dropped HARQ-ACK based on the request DCI.
- HARQ-ACK # 1 (or PUCCH resource # 1) corresponding to PDSCH # 1 collides with another high-priority UL transmission (for example, PUCCH resource # 0a for URLLC) and is dropped. Shows the case.
- HARQ-ACK # 2 (or PUCCH resource # 2) corresponding to PDSCH # 2 and HARQ-ACK # 3 (or PUCCH resource # 3) corresponding to PDSCH # 3 are other UL transmissions having high priority.
- PUCCH resource # 0b for URLLC PUCCH resource # 0b for URLLC
- FIG. 9 shows a case where the request DCI is transmitted after HARQ-ACK # 2 and # 3 are dropped. That is, after HARQ-ACK # 1 is dropped, HARQ-ACK # 2 and # 3 are dropped before the request DCI is transmitted.
- the UE when the UE receives the request DCI, if there are a plurality of dropped HARQ-ACKs, the last dropped HARQ-ACK (or the HARQ- corresponding to the last PUCCH resource not used for transmission). You may control to retransmit ACK).
- the HARQ-ACK to be resent may be determined for each PUCCH resource. That is, when the HARQ-ACK corresponding to the same PUCCH resource (or the PUCCH resource set in the same slot) is dropped (HARQ-ACK # 2 and # 3 in FIG. 9), the plurality of HARQ-ACKs are used. It may be controlled to retransmit.
- the UE since HARQ-ACK # 2 and # 3 correspond to the last dropped PUCCH resource, the UE retransmits the HARQ-ACK # 2 and # 3 using the PUSCH resource specified in the request DCI. It may be controlled to do so.
- the resource specified in the request DCI (for example, here, the PUSCH resource) may be determined based on the PUSCH allocation information included in the request DCI.
- the UE may map or multiplex the UL data scheduled by the request DCI and HARQ-ACK # 2 and # 3 to the PUSCH resource specified by the request DCI.
- HARQ-ACK to be retransmitted can be flexibly controlled based on the transmission timing of the request DCI. As a result, it is possible to suppress an increase in the overhead of HARQ-ACK to be retransmitted and a decrease in throughput.
- the UE may retransmit the HARQ-ACK that was not transmitted (or dropped) in the first to fourth aspects described above, but the present invention is not limited to this. Even if the UE transmits HARQ-ACK, if the base station cannot receive the HARQ-ACK, the base station may instruct the retransmission of the HARQ-ACK using the request DCI. .. In this case, the UE may retransmit the transmitted HARQ-ACK.
- the retransmission of HARQ-ACK may be instructed by using DCI which is not used for scheduling DL transmission or UL transmission.
- the base station may notify the UE of HARQ-ACK corresponding to the HARQ-ACK process number / CC index to be retransmitted by using the predetermined field of the request DCI.
- HARQ-ACK may be a HARQ-ACK bit for PDSCH.
- the predetermined field may be a new field composed of predetermined bits (x bits).
- the predetermined field is Rel.
- the existing field defined in 15 (for example, at least one of the TDRA field, the TDRA table, and the field for the HARQ-ACK process number) may be read and used. The replacement of existing fields may be set by higher layer signaling.
- a case where retransmission is performed for HARQ-ACK having a low priority (for example, low) is shown, but the present invention is not limited to this. It may be controlled to retransmit the HARQ-ACK having a high priority (for example, high). Alternatively, the HARQ-ACK that is retransmitted by the request DCI may be limited to the HARQ-ACK having a low priority.
- the retransmission of HARQ-ACK When the retransmission of HARQ-ACK is instructed regardless of the priority of HARQ-ACK, the retransmission of HARQ-ACK of either one of the priorities may be instructed for each request DCI.
- the UE may determine which priority retransmission is instructed based on the request DCI.
- whether or not the predetermined HARQ-ACK retransmission control or retransmission operation is applied may be notified or set from the base station to the UE by higher layer signaling.
- a predetermined HARQ-ACK retransmission control may be supported for a certain UE, and a predetermined HARQ-ACK retransmission control may not be supported for another UE.
- the presence or absence of support for a predetermined HARQ-ACK retransmission control may be controlled for each UE based on the UE capability / upper layer signaling.
- 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. 10 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 radio communication system 1 may support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between a plurality of Radio Access Technologies (RATs).
- MR-DC is dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), and dual connectivity between NR and LTE (NR-E).
- E-UTRA Evolved Universal Terrestrial Radio Access
- EN-DC E-UTRA-NR 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 macro cell C1 having a relatively wide coverage, and a base station 12 (12a-12c) that is arranged in the macro cell C1 and forms a small cell C2 that is narrower than the macro cell 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 the 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 macro cell 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 FR2 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 that supports 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.
- downlink shared channels Physical Downlink Shared Channel (PDSCH)
- broadcast channels Physical Broadcast Channel (PBCH)
- downlink control channels Physical Downlink Control
- Channel PDCCH
- 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.
- PDSCH 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.
- MIB Master Information Block
- PBCH Master Information Block
- 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, etc.
- the DCI that schedules PUSCH may be called UL grant, UL DCI, etc.
- the PDSCH may be read as DL data
- 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 (UCI) 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" at 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 demodulation reference signal (DeModulation).
- CRS Cell-specific Reference Signal
- CSI-RS Channel State Information Reference Signal
- DeModulation Demodulation reference signal
- Reference Signal (DMRS)), positioning reference signal (Positioning Reference Signal (PRS)), phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), and the like may be transmitted.
- 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. 11 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.
- this example mainly shows the functional blocks of the feature portion in the present embodiment, 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 transmitter / receiver 120 includes a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitter / receiver circuit, and the like, which are described based on common recognition in the technical fields 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 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.
- the base band signal may be output by performing processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, digital-analog conversion, and other transmission processing.
- IFFT inverse fast Fourier transform
- 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) on 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 and the like, and provides user data (user plane data) and control plane for the user terminal 20. 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 transmission / reception unit 120 may receive the UL transmission.
- the transmission / reception unit 120 may transmit downlink control information including information regarding retransmission of HARQ-ACK.
- the control unit 110 may control the reception of the HARQ-ACK that is retransmitted by using the resource notified by the downlink control information.
- FIG. 12 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.
- this example mainly shows the functional blocks of the feature portion in the present embodiment, 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 and 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 transmitter / receiver 220 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitter / receiver 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 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 (transmission processing unit 2211) performs 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.
- RLC layer processing for example, RLC retransmission control
- MAC layer processing for example, for data, control information, etc. acquired from the control unit 210.
- HARQ retransmission control HARQ retransmission control
- 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 the 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 transmitter and receiver of the user terminal 20 in the present disclosure may be composed of at least one of the transmitter / receiver 220 and the transmitter / receiver antenna 230.
- the transmission / reception unit 220 may transmit the UL transmission.
- the transmission / reception unit 220 may receive downlink control information including information regarding retransmission of HARQ-ACK.
- the control unit 210 may control the retransmission of the HARQ-ACK by using the resource notified by the downlink control information.
- the downlink control information may have a configuration that does not instruct the schedule of the downlink shared channel.
- the control unit 210 When the downlink control information indicates the schedule of the downlink shared channel, the control unit 210 does not transmit the HARQ-ACK to the downlink shared channel, or uses the resource used for retransmission of the HARQ-ACK to the downlink shared channel. It may be controlled to transmit HARQ-ACK.
- control unit 210 may control the retransmission of the HARQ-ACK by using the uplink shared channel.
- each functional block may be realized by using one device that is physically or logically connected, or directly or indirectly (for example, by two or more devices that are physically or logically separated). , 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 (constituent unit) for functioning transmission may be referred to as a transmitting unit (transmitting unit), a transmitter (transmitter), or the like.
- the method of realizing each of them 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. 13 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 of 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
- 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 (EPROM), 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 (registered trademark) disk, an optical magnetic disk (for example, a compact disc (Compact Disc ROM (CD-ROM)), a digital versatile disk, etc.). At least one of Blu-ray® disks, removable disks, optical disc drives, smart cards, flash memory devices (eg cards, sticks, key drives), magnetic stripes, databases, servers, and other suitable storage media. It may be composed of.
- 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 includes, 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 from 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 receives 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 wireless frame may be composed of one or more periods (frames) in the time domain.
- Each of the one or more periods (frames) constituting the wireless 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 is independent of 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 domain (Orthogonal Frequency Division Multiple Access (OFDMA) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.).
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single Carrier Frequency Division Multiple Access
- the slot may be a time unit based on numerology.
- the slot may include a plurality of mini slots. Each minislot may consist of one or more symbols in the time domain.
- the mini-slot may also 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 minislot 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.
- the wireless frame, subframe, slot, minislot and symbol all represent the time unit when transmitting a signal.
- the radio frame, subframe, slot, minislot and symbol may have 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. It 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.
- the 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.
- a TTI shorter than a normal TTI may be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a minislot, a subslot, a slot, or the like.
- the long TTI (for example, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and the short TTI (for example, shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms. It may be read as a 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.
- Physical RB Physical RB (PRB)
- SCG sub-carrier Group
- REG resource element group
- 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 wireless frame the number of slots per subframe or wireless frame, the number of minislots contained in a slot, the number of symbols and RBs contained in a slot or minislot, and included in the RB.
- the number of subcarriers, the number of symbols in the TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.
- the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values from predetermined values, or using other corresponding information. It may be represented. For example, radio resources may be indicated by a given 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 another device.
- the notification of information is not limited to the mode / embodiment described in the present disclosure, and may be performed by using other methods.
- 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 called an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (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 whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name, is an instruction, instruction set, code, code segment, program code, program, subprogram, software module.
- Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, features, etc. should be broadly interpreted.
- software, instructions, information, etc. may be transmitted and received via a transmission medium.
- a transmission medium For example, a website where software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.).
- wired technology coaxial cable, fiber optic cable, twisted 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
- radio base station fixed station
- NodeB NodeB
- eNB eNodeB
- gNB gNodeB
- Access point "Transmission point (Transmission Point (TP))
- RP 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 (for example, three) cells.
- a base station accommodates multiple cells, the entire coverage area of the base station 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 the base stations and base station subsystems that provide 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, the mobile body itself, or the like.
- the moving body may be a vehicle (for example, a car, an airplane, etc.), an unmanned moving body (for example, a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned type). ) 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.
- the communication between the base station and the user terminal is replaced with the communication between a plurality of user terminals (for example, it may be called 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 "up” and “down” may be read as words corresponding to communication between terminals (for example, "side”).
- the upstream channel, the downstream channel, and the like may be read as a side 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 performed by the base station and 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 switched with 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
- Future Radio Access FAA
- New-Radio Access Technology RAT
- NR New Radio
- NX New radio access
- Future generation radio access FX
- GSM Global System for Mobile communications
- CDMA2000 Code Division Multiple Access
- UMB Ultra Mobile Broadband
- IEEE 802.11 Wi-Fi (registered trademark)
- IEEE 802.16 WiMAX (registered trademark)
- Ultra-WideBand (UWB), Bluetooth®, other systems utilizing appropriate wireless communication methods, next-generation systems extended based on these, and the like may be applied.
- a plurality of systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).
- 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”.
- 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 “judgment (decision)” 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 radio frequency domain microwaves. It can be considered to be “connected” or “coupled” to each other using frequency, electromagnetic energy having wavelengths in the 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
将来の無線通信システム(例えば、NR)では、モバイルブロードバンドのさらなる高度化(例えば、enhanced Mobile Broadband(eMBB))、多数同時接続を実現するマシンタイプ通信(例えば、massive Machine Type Communications(mMTC)、Internet of Things(IoT))、高信頼かつ低遅延通信(例えば、Ultra-Reliable and Low-Latency Communications(URLLC))などのトラフィックタイプ(タイプ、サービス、サービスタイプ、通信タイプ、ユースケース、等ともいう)が想定される。例えば、URLLCでは、eMBBより小さい遅延及びより高い信頼性が要求される。
・異なる優先度(priority)を有する論理チャネル
・変調及び符号化方式(Modulation and Coding Scheme(MCS))テーブル(MCSインデックステーブル)
・チャネル品質指示(Channel Quality Indication(CQI))テーブル
・DCIフォーマット
・当該DCI(DCIフォーマット)に含まれる(付加される)巡回冗長検査(CRC:Cyclic Redundancy Check)ビットのスクランブル(マスク)に用いられる(無線ネットワーク一時識別子(RNTI:System Information-Radio Network Temporary Identifier))
・RRC(Radio Resource Control)パラメータ
・特定のRNTI(例えば、URLLC用のRNTI、MCS-C-RNTI等)
・サーチスペース
・DCI内の所定フィールド(例えば、新たに追加されるフィールド又は既存のフィールドの再利用)
・当該PDSCHの変調次数(modulation order)、ターゲット符号化率(target code rate)、トランスポートブロックサイズ(TBS:Transport Block size)の少なくとも一つの決定に用いられるMCSインデックステーブル(例えば、MCSインデックステーブル3を利用するか否か)
・当該PDSCHのスケジューリングに用いられるDCIのCRCスクランブルに用いられるRNTI(例えば、C-RNTI又はMCS-C-RNTIのどちらでCRCスクランブルされるか)
・上位レイヤシグナリングで設定される優先度
UEは、1以上の送達確認情報(例えば、Hybrid Automatic Repeat reQuest ACKnowledgement(HARQ-ACK))のビットから構成されるHARQ-ACKコードブック単位で、1つのPUCCHリソースを用いてHARQ-ACKフィードバックを送信してもよい。HARQ-ACKビットは、HARQ-ACK情報、HARQ-ACK情報ビットなどと呼ばれてもよい。
キャリアアグリゲーション(CA)またはデュアルコネクティビティ(DC)が設定されたUEに対し、セル(CC)またはセルグループ(CG)ごとに1つの独立したHARQエンティティ(entity)が存在してもよい。HARQエンティティは、複数のHARQプロセスを並行して管理してもよい。
Rel.16以降では、UEにおけるLBTの失敗又は基地局におけるPUCCHの検出ミスによるHARQ-ACKフィードバック用の送信機会を提供するために、全てのHARQ-ACKプロセスを含むHARQ-ACKコードブックのフィードバックをUEに要求又はトリガすることが検討されている(図2参照)。HARQ-ACKプロセス(例えば、DL HARQ-ACKプロセス)は、PUCCHグループにおいてUEに設定された全てのCCにおけるHARQ-ACKにであってもよい。
Rel.16以降のNRでは、所定の信号又はチャネルに対して複数レベル(例えば、2レベル)の優先度を設定することが検討されている。例えば、異なるトラフィックタイプ(サービス、サービスタイプ、通信タイプ、ユースケース等ともいう)にそれぞれ対応する信号又はチャネル毎に別々の優先度を設定して通信を制御(例えば、衝突時の送信制御等)を行うことが想定される。これにより、同じ信号又はチャネルに対して、サービスタイプ等に応じて異なる優先度を設定して通信を制御することが可能となる。
第1の態様では、DLデータ(例えば、DL-SCH)又はPDSCHのスケジュールを行わないDCIを利用して、HARQ-ACKの再送の指示(又は、要求/トリガ)を制御する場合について説明する。以下の説明では、DCIによりPDSCHがスケジュールされない場合を例に挙げて説明する。
UEは、HARQ-ACKの再送を指示するリクエストDCIに基づいて、複数のHARQ-ACK(例えば、優先度が低い複数のHARQ-ACK)をフィードバックするように制御してもよい。例えば、基地局は、リクエストDCIを利用して1ショットHARQ-ACKのフィードバックをUEに要求(又は、トリガ)してもよい。つまり、リクエストDCIで再送が要求されるHARQ-ACKビットは、所定グループ(例えば、PUCCHグループ)においてUEに設定された全てのCCにおけるDL HARQ-ACKプロセスであってもよい。
UEは、リクエストDCIに基づいて、最新(例えば、latest)にドロップされたHARQ-ACKをフィードバック(例えば、再送)するように制御してもよい(図4参照)。つまり、UEは、送信を行わなかったHARQ-ACKが複数存在する場合、最後に送信を行わなかったHARQ-ACK(又は、最後にドロップしたHARQ-ACK)を再送するように制御する。
UEは、基地局から通知される情報に基づいて再送を行うHARQ-ACKを決定してもよい。基地局から通知される情報は、DCI及び上位レイヤシグナリングの少なくとも一つであってもよい。
UEは、HARQ-ACKの再送を指示するリクエストDCIに基づいて、再送を行うHARQ-ACKを決定してもよい(図5参照)。例えば、再送を行うHARQ-ACKの元のHARQ-ACK(オリジナルHARQ-ACK)を指定する情報がリクエストDCIに含まれていてもよい。以下の説明では、リクエストDCIとオリジナルHARQ-ACK(又は、オリジナルPUCCHリソース)間のオフセットに関する情報をリクエストDCIに含めてUEに通知する場合を示す。
UEは、上位レイヤで通知されるタイミングオフセットに関する情報に基づいて、再送を行うHARQ-ACKを決定してもよい。タイミングオフセット(例えば、Δt)は、リクエストDCI(又は、PDCCH)が送信されるスロットと、オリジナルHARQ-ACKが送信されるスロットの間隔であってもよい。
基地局は、複数のタイミングオフセット値(候補値)を上位レイヤシグナリングでUEに設定し、DCI(例えば、リクエストDCI)を利用して特定の候補値をUEに通知してもよい。これにより、タイミングオフセットを柔軟に設定することが可能となる。
リクエストDCIに基づいてHARQ-ACKの再送を指示する場合、再送するHARQ-ACKの優先度は、オリジナルHARQ-ACK(ドロップされたHARQ-ACK)と同じ優先度が設定されてもよいし、異なる優先度が設定されてもよい。
第2の態様では、DLデータ(例えば、DL-SCH)又はPDSCHのスケジュールを行うDCIを利用して、HARQ-ACKの再送の指示(又は、要求/トリガ)を制御する場合について説明する。
UEは、リクエストDCIで指定されたリソースをドロップされたHARQ-ACKの再送に利用し、当該リクエストDCIでスケジュールされたPDSCHに対するHARQ-ACKの送信に利用しなくてもよい(図6参照)。この場合、UEは、リクエストDCIで新規にスケジュールされたPDSCHに対するHARQ-ACKを送信しない(又は、報告しない、ドロップする)ように制御してもよい。
UEは、リクエストDCIで指定されたリソースをドロップされたHARQ-ACKの再送と、当該リクエストDCIでスケジュールされたPDSCHに対するHARQ-ACKの送信と、に利用してもよい(図7参照)。この場合、UEは、リクエストDCIで新規にスケジュールされたPDSCHに対するHARQ-ACKと、再送するHARQ-ACKを同じHARQ-ACKコードブックに含めて送信するように制御してもよい。
UEは、リクエストDCIに基づいて再送を行うHARQ-ACK(例えば、ドロップした第2のHARQ-ACK)について、第1の態様のオプション1-1~オプション1-3の少なくとも一つに基づいて決定してもよい。つまり、UEは、オプション2-1又は2-2と、第1の態様のオプション1-1~オプション1-3の少なくとも一つと、を組み合わせて適用すればよい。
第3の態様では、ULデータ(例えば、UL-SCH)又はPUSCHのスケジュールを行わないDCIを利用して、HARQ-ACKの再送の指示(又は、要求/トリガ)を制御する場合について説明する。以下の説明では、DCIによりPUSCHはスケジュールされるが、ULデータ(PUSCH)が送信(又は、スケジュール)されない場合を例に挙げて説明する。
第4の態様では、ULデータ(例えば、UL-SCH)のスケジュールを行うDCIを利用して、HARQ-ACKの再送の指示(又は、要求/トリガ)を制御する場合について説明する。以下の説明では、DCIによりPUSCHで送信されるULデータがスケジュールされる場合を例に挙げて説明する。
上記第1の態様~第4の態様において、UEが送信しなかった(又は、ドロップした)HARQ-ACKを再送する場合を示したが、これに限られない。仮にUEがHARQ-ACKを送信する場合であっても基地局側で当該HARQ-ACKを受信できなかった場合、基地局はリクエストDCIを利用して当該HARQ-ACKの再送を指示してもよい。この場合、UEは、送信を行ったHARQ-ACKを再度送信してもよい。
以下、本開示の一実施形態に係る無線通信システムの構成について説明する。この無線通信システムでは、本開示の上記各実施形態に係る無線通信方法のいずれか又はこれらの組み合わせを用いて通信が行われる。
図11は、一実施形態に係る基地局の構成の一例を示す図である。基地局10は、制御部110、送受信部120、送受信アンテナ130及び伝送路インターフェース(transmission line interface)140を備えている。なお、制御部110、送受信部120及び送受信アンテナ130及び伝送路インターフェース140は、それぞれ1つ以上が備えられてもよい。
図12は、一実施形態に係るユーザ端末の構成の一例を示す図である。ユーザ端末20は、制御部210、送受信部220及び送受信アンテナ230を備えている。なお、制御部210、送受信部220及び送受信アンテナ230は、それぞれ1つ以上が備えられてもよい。
なお、上記実施形態の説明に用いたブロック図は、機能単位のブロックを示している。これらの機能ブロック(構成部)は、ハードウェア及びソフトウェアの少なくとも一方の任意の組み合わせによって実現される。また、各機能ブロックの実現方法は特に限定されない。すなわち、各機能ブロックは、物理的又は論理的に結合した1つの装置を用いて実現されてもよいし、物理的又は論理的に分離した2つ以上の装置を直接的又は間接的に(例えば、有線、無線などを用いて)接続し、これら複数の装置を用いて実現されてもよい。機能ブロックは、上記1つの装置又は上記複数の装置にソフトウェアを組み合わせて実現されてもよい。
なお、本開示において説明した用語及び本開示の理解に必要な用語については、同一の又は類似する意味を有する用語と置き換えてもよい。例えば、チャネル、シンボル及び信号(シグナル又はシグナリング)は、互いに読み替えられてもよい。また、信号はメッセージであってもよい。参照信号(reference signal)は、RSと略称することもでき、適用される標準によってパイロット(Pilot)、パイロット信号などと呼ばれてもよい。また、コンポーネントキャリア(Component Carrier(CC))は、セル、周波数キャリア、キャリア周波数などと呼ばれてもよい。
Claims (6)
- 送達確認信号(HARQ-ACK)と他のUL送信とが衝突する場合、前記UL送信を送信する送信部と、
前記HARQ-ACKの再送に関する情報を含む下り制御情報を受信する受信部と、
前記下り制御情報で通知されるリソースを利用して前記HARQ-ACKの再送を制御する制御部と、を有することを特徴とする端末。 - 前記下り制御情報は、下り共有チャネルのスケジュールを指示しないことを特徴とする請求項1に記載の端末。
- 前記下り制御情報が下り共有チャネルのスケジュールを指示する場合、前記制御部は、前記下り共有チャネルに対するHARQ-ACKの送信を行わない、又は前記HARQ-ACKの再送に利用するリソースを利用して前記下り共有チャネルに対するHARQ-ACKを送信するように制御することを特徴とする請求項1に記載の端末。
- 前記下り制御情報が上り共有チャネルのスケジュールを指示する場合、前記制御部は、前記上り共有チャネルを利用して前記第HARQ-ACKの再送を制御することを特徴とする請求項1に記載の端末。
- 送達確認信号(HARQ-ACK)と他のUL送信とが衝突する場合、前記UL送信を送信する工程と、
前記HARQ-ACKの再送に関する情報を含む下り制御情報を受信する工程と、
前記下り制御情報で通知されるリソースを利用して前記HARQ-ACKの再送を制御する工程と、を有することを特徴とする端末の無線通信方法。 - 送達確認信号(HARQ-ACK)と他のUL送信とが衝突する場合、前記UL送信を受信する受信部と、
前記HARQ-ACKの再送に関する情報を含む下り制御情報を送信する送信部と、
前記下り制御情報で通知するリソースを利用して再送される前記HARQ-ACKの受信を制御する制御部と、を有することを特徴とする基地局。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2022504945A JPWO2021176723A1 (ja) | 2020-03-06 | 2020-03-06 | |
CN202080100565.0A CN115552958A (zh) | 2020-03-06 | 2020-03-06 | 终端、无线通信方法以及基站 |
US17/908,377 US20230113163A1 (en) | 2020-03-06 | 2020-03-06 | Terminal, radio communication method, and base station |
PCT/JP2020/009851 WO2021176723A1 (ja) | 2020-03-06 | 2020-03-06 | 端末、無線通信方法及び基地局 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2020/009851 WO2021176723A1 (ja) | 2020-03-06 | 2020-03-06 | 端末、無線通信方法及び基地局 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021176723A1 true WO2021176723A1 (ja) | 2021-09-10 |
Family
ID=77613295
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2020/009851 WO2021176723A1 (ja) | 2020-03-06 | 2020-03-06 | 端末、無線通信方法及び基地局 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20230113163A1 (ja) |
JP (1) | JPWO2021176723A1 (ja) |
CN (1) | CN115552958A (ja) |
WO (1) | WO2021176723A1 (ja) |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019186676A (ja) * | 2018-04-05 | 2019-10-24 | シャープ株式会社 | 基地局装置および端末装置 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9357537B2 (en) * | 2012-06-19 | 2016-05-31 | Lg Electronics Inc. | Method and apparatus for transmitting uplink data |
US20150173102A1 (en) * | 2013-12-12 | 2015-06-18 | Sharp Kabushiki Kaisha | Terminal apparatus, base station apparatus, communication system, communication method, and integrated circuit |
JP6907117B2 (ja) * | 2015-08-21 | 2021-07-21 | 株式会社Nttドコモ | 端末、基地局及び無線通信方法 |
US10602537B2 (en) * | 2015-11-02 | 2020-03-24 | Lg Electronics Inc. | Method and user equipment for receiving downlink channel, and method and base station for transmitting downlink channel |
-
2020
- 2020-03-06 US US17/908,377 patent/US20230113163A1/en active Pending
- 2020-03-06 JP JP2022504945A patent/JPWO2021176723A1/ja active Pending
- 2020-03-06 CN CN202080100565.0A patent/CN115552958A/zh active Pending
- 2020-03-06 WO PCT/JP2020/009851 patent/WO2021176723A1/ja active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019186676A (ja) * | 2018-04-05 | 2019-10-24 | シャープ株式会社 | 基地局装置および端末装置 |
Non-Patent Citations (3)
Title |
---|
"Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8", 3GPP TS 36.300, April 2010 (2010-04-01) |
NTT DOCOMO, INC.: "DL/UL scheduling and HARQ management", 3GPP TSG RAN WG1 #90BIS, R1-1718217, 13 October 2017 (2017-10-13), XP051352925, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_90b/Docs/R1-1718217.zip> [retrieved on 20200915] * |
OPPO: "UCI enhancements for URLLC", 3GPP TSG RAN WG1 #98BIS, R1-1910620, 20 October 2019 (2019-10-20), XP051789412, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_ran/WG1_RL1/TSGR1_98b/Docs/R1-1910620.zip> [retrieved on 20200915] * |
Also Published As
Publication number | Publication date |
---|---|
US20230113163A1 (en) | 2023-04-13 |
JPWO2021176723A1 (ja) | 2021-09-10 |
CN115552958A (zh) | 2022-12-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021152805A1 (ja) | 端末、無線通信方法及び基地局 | |
JP7168676B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
JP7269331B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
WO2022163559A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022039164A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2020202478A1 (ja) | ユーザ端末及び無線通信方法 | |
WO2020188821A1 (ja) | ユーザ端末及び無線通信方法 | |
WO2020095457A1 (ja) | ユーザ端末 | |
WO2022130629A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2021255936A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022024379A1 (ja) | 端末、無線通信方法及び基地局 | |
JP7351921B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
WO2020188666A1 (ja) | ユーザ端末及び無線通信方法 | |
WO2020202448A1 (ja) | ユーザ端末及び無線通信方法 | |
WO2022074802A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2021152804A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022009347A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022009346A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022059110A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2022009315A1 (ja) | 端末、無線通信方法及び基地局 | |
WO2021186701A1 (ja) | 端末、無線通信方法及び基地局 | |
JP7335349B2 (ja) | 端末、無線通信方法、基地局及びシステム | |
JP7230179B2 (ja) | 端末、無線通信方法及びシステム | |
WO2021064961A1 (ja) | 端末及び無線通信方法 | |
WO2021176723A1 (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: 20922965 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2022504945 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2020922965 Country of ref document: EP Effective date: 20221006 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20922965 Country of ref document: EP Kind code of ref document: A1 |