WO2021152804A1 - Terminal, procédé de communication sans fil, et station de base - Google Patents

Terminal, procédé de communication sans fil, et station de base Download PDF

Info

Publication number
WO2021152804A1
WO2021152804A1 PCT/JP2020/003563 JP2020003563W WO2021152804A1 WO 2021152804 A1 WO2021152804 A1 WO 2021152804A1 JP 2020003563 W JP2020003563 W JP 2020003563W WO 2021152804 A1 WO2021152804 A1 WO 2021152804A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
ack
feedback
transmission
codebook
Prior art date
Application number
PCT/JP2020/003563
Other languages
English (en)
Japanese (ja)
Inventor
優元 ▲高▼橋
聡 永田
シャオホン ジャン
リフェ ワン
ギョウリン コウ
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Priority to PCT/JP2020/003563 priority Critical patent/WO2021152804A1/fr
Priority to CN202080095110.4A priority patent/CN115023967A/zh
Publication of WO2021152804A1 publication Critical patent/WO2021152804A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/04—Error control

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.
  • the UE When the UE supports (or uses) multiple service types, it is assumed that the HARQ-ACK codebook used for the feedback of HARQ-ACK is set for each service type. Further, in the future wireless communication system, it is considered that the UE performs HARQ-ACK feedback for a plurality of HARQ processes at one time.
  • one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately provide HARQ-ACK feedback even when communicating using a plurality of service types. Let's do it.
  • the terminal includes a receiving unit that receives downlink control information that triggers feedback of one shot of HARQ-ACK, and a plurality of services when feedback of HARQ-ACK is performed based on the downlink information. It is characterized by having a HARQ-ACK corresponding to each type or a control unit for controlling feedback of HARQ-ACK having different priorities by using a common codebook.
  • HARQ-ACK feedback can be appropriately provided even when communication is performed using a plurality of service 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 1-shot HARQ-ACK feedback control according to the first aspect.
  • FIG. 4 is a diagram showing another example of the one-shot HARQ-ACK feedback control according to the first aspect.
  • FIG. 5 is a diagram showing another example of the one-shot HARQ-ACK feedback control according to the first aspect.
  • FIG. 6 is a diagram showing an example of 1-shot HARQ-ACK feedback control according to the second aspect.
  • 7A and 7B are diagrams showing another example of the one-shot HARQ-ACK feedback control according to the second aspect.
  • FIG. 8A-8C are diagrams showing another example of the one-shot HARQ-ACK feedback control according to the second aspect.
  • 9A-9C are diagrams showing another example of the one-shot HARQ-ACK feedback control according to the second aspect.
  • 10A-10C are diagrams showing another example of the one-shot HARQ-ACK feedback control according to the second aspect.
  • 11A-11C are diagrams showing another example of the one-shot HARQ-ACK feedback control according to the second aspect.
  • FIG. 12 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
  • FIG. 13 is a diagram showing an example of the configuration of the base station according to the embodiment.
  • FIG. 14 is a diagram showing an example of the configuration of the user terminal according to the embodiment.
  • FIG. 15 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 reliability requirement of URLLC may also include a 32-byte error rate of 10-5 at a U-plane delay of 1 ms.
  • 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.
  • priorities may be set for the HARQ-ACK codebooks corresponding to these HARQ-ACKs.
  • 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, UL transmission having a high priority may be performed, and UL transmission having a low priority may not be performed (for example, dropping). Alternatively, the transmission timing of the UL transmission having a low priority may be changed (for example, postponed or shifted).
  • Collision of different UL signals / UL channels means that the time resources (or time resources and frequency resources) of different UL signals / UL channels overlap, or the transmission timings of different UL signals / UL channels overlap. May be.
  • 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
  • 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 (eg, 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 the 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 set) (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 include 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.
  • a plurality of systems such as a Wi-Fi system and a system supporting Licensed-Assisted Access (LAA) (LAA system) coexist. Therefore, it is considered that collision avoidance and / or interference control of transmission between the plurality of systems is required.
  • LAA Licensed-Assisted Access
  • the data transmitter is a device of another device (eg, base station, user terminal, Wi-Fi device, etc.) before transmitting the data in the unlicensed band.
  • Listening Listen Before Talk (LBT), Clear Channel Assessment (CCA), carrier sense, channel sensing, sensing, channel access procedure) to confirm the presence or absence of transmission is performed.
  • LBT Listen Before Talk
  • CCA Clear Channel Assessment
  • carrier sense carrier sense, channel sensing, sensing, channel access procedure
  • the transmitting device may be, for example, a base station (for example, gNB: gNodeB) for downlink (DL) and a user terminal (for example, User Equipment (UE)) for uplink (UL).
  • a base station for example, gNB: gNodeB
  • UE User Equipment
  • the receiving device that receives the data from the transmitting device may be, for example, a user terminal in DL and a base station in UL.
  • the transmitting device starts data transmission after a predetermined period (for example, immediately after or during the backoff period) after the LBT detects that there is no transmission of another device (idle state). ..
  • unlicensed bands are also being considered in future wireless communication systems (for example, 5G, 5G +, New Radio (NR), 3GPP Rel.15 or later, etc.).
  • the NR system using the unlicensed band may be called an NR-Unlicensed (U) system, an NR LAA system, or the like.
  • Dual Connectivity (DC) between the licensed band and the unlicensed band, Stand-Alone (SA) of the unlicensed band, etc. may also be included in NR-U.
  • the node for example, base station, UE
  • the node starts transmission after confirming that the channel is free (idle) by LBT for coexistence with another system or another operator.
  • the base station for example, gNB or the UE acquires a transmission opportunity (Transmission Opportunity: TxOP) when the LBT result is idle and performs transmission.
  • TxOP Transmission Opportunity
  • the base station or UE does not transmit when the LBT result is busy (LBT-busy).
  • the time of the transmission opportunity is called Channel Occupancy Time (COT).
  • LBT-idle may be read as LBT success.
  • LBT-busy may be read as LBT failure.
  • 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 process eg, DL HARQ-ACK process
  • the HARQ-ACK process may be the 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.
  • the UE feeds back one HARQ-ACK codebook based on a request or trigger for one-shot HARQ-ACK feedback notified by a DCI, how should the HARQ-ACK included in the HARQ-ACK codebook be included? The problem is whether to control it.
  • 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.
  • HARQ-ACK feedback based on a one-shot HARQ-ACK feedback request will be described as an example, but the present embodiment is not limited to this. For example, it may be applied to HARQ-ACK feedback other than 1-shot HARQ-ACK feedback.
  • the UE uses one (or common) HARQ-ACK codebook to transmit HARQ-ACK corresponding to different service types based on the request for one-shot HARQ-ACK feedback.
  • a case of performing (for example, Re-Tx HARQ-ACK) will be described.
  • the network may instruct the UE to request or trigger a one-shot HARQ-ACK feedback using at least one of DCI and higher layer signaling.
  • the UE may determine the presence or absence of feedback of a 1-shot HARQ-ACK based on the value of a predetermined field (for example, a 1-shot HARQ-ACK request field) included in the predetermined DCI format.
  • the predetermined DCI format may be a DCI format used for PDSCH scheduling (for example, at least one of DCI formats 1_0, 1_1 and 1_2). Further, whether or not the DCI includes a predetermined field may be notified or set from the base station to the UE by using higher layer signaling.
  • a UE that requests (or triggers) feedback on a one-shot HARQ-ACK may include one or more HARQ-ACKs in one (or common) HARQ-ACK codebook (CB) for feedback. good.
  • 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 uses one HARQ-ACK codebook to provide HARQ-ACK feedback, even if the HARQ-ACK corresponding to a given HARQ-ACK process corresponds to different service types or different priorities. It may be good (see FIG. 3).
  • the PUCCH of each service type may be specified or set by a DCI (eg, PUCCH resource indicator field) or the like that schedules the PDSCH of each service type.
  • the UE Before receiving the 1-shot HARQ-ACK feedback request, the UE transmits the HARQ-ACK for each service type by using the PUCCH resource set for each.
  • the UE controls to use one HARQ-ACK codebook to provide feedback of HARQ-ACK of PDSCH for eMBB and HARQ-ACK of PDSCH for URLLC. ..
  • the HARQ-ACK codebook used for one-shot HARQ-ACK feedback contains HARQ-ACK of multiple service types (for example, CC used for transmission of each service type, and the number of HARQ-ACK processes applied). It may be a HARQ-ACK codebook set in consideration.
  • a HARQ-ACK codebook type for example, a quasi-static HARQ-ACK codebook (type 1) and a dynamic HARQ-ACK codebook (type 2)
  • a HARQ-ACK codebook type for example, a quasi-static HARQ-ACK codebook (type 1) and a dynamic HARQ-ACK codebook (type 2)
  • a particular codebook type eg, type 1) may be selected, or a codebook type corresponding to a particular service type may be selected.
  • the codebook type to be applied may be defined in the specification in advance, or the base station may notify the UE using DCI and higher layer signaling.
  • the UE uses a PUCCH setting parameter (or PUCCH parameter) to be used for transmitting HARQ-ACK based on a predetermined condition. May be judged.
  • the PUCCH configuration parameter (for example, PUCCH configuration parameter) includes the PUCCH resource (or PUCCH resource set) applied to the transmission of HARQ-ACK, the PUCCH transmission timing (for example, K1 set), and the maximum coding rate (for example, max-). It may be at least one of the code rate) and the transmission power of the PUCCH.
  • the UE may determine the PUCCH setting parameter to be used for HARQ-ACK feedback by using at least one of the following options 1-1 to 1-3.
  • the UE may apply the PUCCH configuration parameters corresponding to the HARQ-ACK of a particular service type (see FIG. 4).
  • the first PUCCH setting parameter here, the first PUCCH resource set
  • HARQ-ACK for URLLC
  • eMBB HARQ- for eMBB
  • the second PUCCH setting parameter here, the second PUCCH resource set
  • the first PUCCH resource set may be set by at least one of DCI and higher layer signaling that schedules PDSCH for URLLC.
  • the second PUCCH resource set may also be set by at least one of DCI and higher layer signaling to schedule the PDSCH for eMBB.
  • the UE may be controlled to always use the first PUCCH resource when transmitting a codebook containing HARQ-ACK for URLLC and HARQ-ACK for eMBB by a one-shot HARQ-ACK feedback request (option). 1-1-1).
  • the PUCCH resource of the HARQ-ACK feedback the PUCCH resource set in consideration of high reliability and low delay can be applied.
  • a codebook containing HARQ-ACK for URLLC and HARQ-ACK for eMBB may be controlled to always use the second PUCCH resource (option 1). 1-2).
  • the UE may determine the PUCCH (or PUCCH setting parameter) to be applied to the one-shot HARQ-ACK feedback based on the notification from the base station.
  • PUCCH setting parameters set for each search type which PUCCH setting parameter is applied may be notified or set from the base station to the UE by using higher layer signaling (option 1). -2-1).
  • the base station may instruct the UE from the base station which PUCCH setting parameter is to be applied among the PUCCH setting parameters set for each search type (option 1-2-2). ).
  • the DCI used for notification may be a DCI (or PDCCH) that makes a one-shot HARQ-ACK feedback request (see FIG. 5).
  • a predetermined PUCCH setting parameter may be specified by using a predetermined field of DCI that makes a one-shot HARQ-ACK feedback request.
  • the predetermined field may be a field for notifying the priority (for example, a PriorityIndicator field) or a newly set field. For example, when the bit value of the predetermined field is "1", the UE applies the PUCCH setting parameter (for example, the first PUCCH resource) corresponding to HARQ-ACK for URLLC (see FIG. 5). When the bit value of the predetermined field is "0", the UE applies the PUCCH setting parameter (for example, the second PUCCH resource) corresponding to HARQ-ACK for eMBB.
  • the UE may select the PUCCH configuration parameter corresponding to the HARQ-ACK for a particular service type.
  • the specific service type may be defined in advance in the specifications, or may be notified or set from the base station to the UE by higher layer signaling or the like.
  • the UE may apply a combination of PUCCH configuration parameters corresponding to each service type.
  • the UE has a part of PUCCH setting parameters corresponding to HARQ-ACK for URLLC (for example, PUCCH resource set, maximum code rate) and a part of PUCCH setting parameters corresponding to HARQ-ACK for eMBB (for example,).
  • PUCCH power parameters K1 set may be applied in combination.
  • the PUCCH setting parameter selected from each service type may be defined in advance in the specifications, or may be notified or set from the base station to the UE by higher layer signaling or the like.
  • At least one of the PUCCH setting information applied to the one-shot HARQ-ACK feedback is newly set by at least one of DCI (for example, DCI used for the one-shot HARQ-ACK feedback request) and upper layer signaling. May be done.
  • the PUCCH setting parameter can be flexibly set for the codebook including the HARQ-ACK of a plurality of service types.
  • each UE utilizes a separate HARQ-ACK codebook (or PUCCH configuration parameter) for different service types (or priorities) based on a request for one-shot HARQ-ACK feedback.
  • HARQ-ACK codebook or PUCCH configuration parameter
  • the base station may instruct the UE to request or trigger a one-shot HARQ-ACK feedback using at least one of DCI and higher layer signaling.
  • the UE may determine the presence or absence of feedback of a 1-shot HARQ-ACK based on the value of a predetermined field (for example, a 1-shot HARQ-ACK request field) included in the predetermined DCI format.
  • the predetermined DCI format may be a DCI format used for PDSCH scheduling (for example, at least one of DCI formats 1_0, 1_1 and 1_2). Further, whether or not the DCI includes a predetermined field may be notified or set from the base station to the UE by using higher layer signaling.
  • the UE for which 1-shot HARQ-ACK feedback is requested (or triggered) may provide feedback using a HARQ-ACK codebook (CB) that differs for each service type (or priority). Further, the feedback of 1-shot HARQ-ACK may be requested (or triggered) separately for each service type. In this case, the UE may apply different PUCCH configuration parameters (eg, PUCCH resources) to the HARQ-ACK of each service type for which the one-shot HARQ-ACK feedback request is notified separately.
  • CB HARQ-ACK codebook
  • a HARQ-ACK codebook containing only HARQ-ACK for eMBB may be reported in the PUCCH resource for eMBB.
  • the HARQ-ACK codebook containing only the HARQ-ACK for URLLC may be reported in the PUCCH resource for URLLC.
  • the UE performs HARQ-ACK feedback using the PUCCH resource set for each service type before receiving the one-shot HARQ-ACK feedback request.
  • the UE uses a separate HARQ-ACK codebook (and PUCCH resource) for each service type to use HARQ-ACK for PDSCH for eMBB and HARQ-ACK for PDSCH for URLLC-. Control ACK feedback separately.
  • the DCI requesting the 1-shot HARQ-ACK feedback may be transmitted separately for each service type.
  • one-shot HARQ-ACK feedback for multiple service types may be performed, respectively, based on one DCI.
  • the HARQ-ACK codebook that provides 1-shot HARQ-ACK feedback contains HARQ-ACK of a specific service type, it corresponds to the specific service type as before receiving the 1-shot HARQ-ACK feedback request.
  • PUCCH resources may be applied.
  • the correspondence (or mapping) between the request or trigger DCI (request / trigger DCI) for one-shot HARQ-ACK feedback and the HARQ-ACK bits may be determined based on a predetermined field of the DCI. (See FIGS. 7A and 7B).
  • the predetermined field may be a field for notifying the priority (for example, PriorityIndicator field).
  • a service type for performing 1-shot HARQ-ACK feedback is specified based on a field for instructing a 1-shot HARQ-ACK request (for example, One-shot HARQ-ACK request) and a predetermined field. do.
  • a service type for performing HARQ-ACK feedback is specified based on a predetermined field.
  • the DCI used for PDSCH scheduling may not include a field for instructing a one-shot HARQ-ACK request (for example, a One-shot HARQ-ACK request) (see FIGS. 7A and 7B). ).
  • HARQ-ACK codebook When transmitting 1-shot HARQ-ACK feedback on request and transmitting HARQ-ACK corresponding to each service type using separate HARQ-ACK codebooks, the UE shall use the following options 2-1 to 2- At least one of 4 may be applied.
  • the HARQ-ACK process number and CC set in the UE are dynamically scheduled (or applied) for a plurality of service types. That is, it is assumed that the same HARQ-ACK process number and CC can be applied to a plurality of service types. Further, it is assumed that the HARQ-ACK codebook size is set quasi-statically based on the number of CCs, the number of HARQ-ACK processes, and the like.
  • the HARQ-ACK codebook (or 1-shot HARQ-ACK feedback) may be requested or specified based on DCI.
  • the HARQ-ACK codebook may be configured to include all HARQ-ACK process numbers in the CC configured on the UE.
  • the UE may also determine the configuration of the HARQ-ACK codebook based on the DCI (request / trigger DCI) requesting the one-shot HARQ-ACK feedback (or HARQ-ACK codebook) (FIG. See 8A).
  • FIG. 8A shows a case where two CCs (CC # 1 and CC # 2) are set for a UE that supports eMBB and URLLC, and eight HARQ-ACK processes can be set for each CC. ing.
  • PDSCH for eMBB (corresponding to HARQ-ACK process # 1) is scheduled in CC # 1
  • PDSCH for eMBB corresponding to HARQ-ACK process # 3
  • CC # 2 corresponding to URLLC
  • the UE performs one shot based on a predetermined field (for example, Priority Indicator) of the DCI.
  • a predetermined field for example, Priority Indicator
  • the service type (or priority) to which the HARQ-ACK feedback is applied may be determined.
  • the UE reports HARQ-ACK for URLLC as a valid HARQ-ACK value. May (or may be included in the codebook).
  • the HARQ-ACK for URLLC may be mapped to a predetermined position in the codebook based on at least one of the HARQ-ACK process number and the CC index (see FIG. 8B).
  • FIG. 8B shows an example of a HARQ-ACK codebook (CB # 1) corresponding to URLLC.
  • the UE includes HARQ-ACK for URLLC (here, HARQ-ACK processes # 5 and # 6 of CC # 2) in CB # 1 as a valid HARA-ACK value.
  • the UE may be configured not to report the HARQ-ACK process for eMBB or other unscheduled HARQ-ACK processes as a valid HARQ-ACK.
  • the UE may report a value of HARQ-ACK that is not reported as a valid HARQ-ACK as a fixed value (eg, either NACK or ACK).
  • the location of each HARQ-ACK process in the codebook may be determined based on at least one of the HARQ-ACK process number and the CC index.
  • the UE does not enable the HARQ-ACK for eMBB (here, the HARQ-ACK process # 1 of CC # 1 and the HARQ-ACK process # 3 of CC # 2) to enable the HARA-ACK value (here, NACK). ) Is included in CB # 1.
  • the UE may report HARQ-ACK for eMBB as a valid HARQ-ACK value. (Alternatively, it may be included in the codebook). In this case, the HARQ-ACK for the eMBB may be mapped to a predetermined position in the codebook based on at least one of the HARQ-ACK process number and the CC index (see FIG. 8C).
  • FIG. 8C shows an example of the HARQ-ACK codebook (CB # 2) corresponding to eMBB.
  • the UE includes HARQ-ACK for eMBB (here, HARQ-ACK process # 1 of CC # 1 and HARQ-ACK process # 3 of CC # 2) as a valid HARA-ACK value in CB # 2.
  • the UE may be configured not to report the HARQ-ACK process for URLLC or other unscheduled HARQ-ACK processes as a valid HARQ-ACK.
  • FIG. 8C when the UE includes HARQ-ACK for URLLC (here, HARQ-ACK processes # 5 and # 6 of CC # 2) in CB # 2 as an invalid HARA-ACK value (here, NACK). Is shown.
  • the HARQ-ACK codebook corresponding to each service type can be appropriately set. ..
  • PDSCH corresponding to each service type is scheduled in a different frequency domain (for example, a different CC). That is, it is assumed that one of the PDSCH for eMBB and the PDSCH for URLLC is scheduled in a certain CC (for example, CC # 1), and the other is scheduled in another CC (for example, CC # 2).
  • the PDSCH of any service type is scheduled for each CC may be defined in advance in the specifications, or may be notified or set from the base station to the UE by higher layer signaling or the like. However, the UE may be notified by the request / trigger DCI.
  • FIG. 9A shows a case where two CCs (CC # 1 and CC # 2) are set for a UE that supports eMBB and URLLC, and eight HARQ-ACK processes can be set for each CC. ing. Further, the PDSCH for eMBB is scheduled in CC # 1, and the PDSCH for URLLC is scheduled in CC # 2. Here, two PDSCHs for eMBB (corresponding to HARQ-ACK processes # 1 and # 3) are scheduled in CC # 1, and two PDSCHs for URLLC (corresponding to HARQ-ACK processes # 5 and # 3) in CC # 2. (Corresponding to # 6) is scheduled.
  • the HARQ-ACK codebook (or 1-shot HARQ-ACK feedback) for the eMBB may be requested or specified by the DCI for the eMBB.
  • the HARQ-ACK codebook may be configured to include all HARQ-ACK processes corresponding to the CC of eMBB.
  • the HARQ-ACK codebook (or 1-shot HARQ-ACK feedback) for URLLC may be requested or specified by the DCI for URLLC.
  • the HARQ-ACK codebook may be configured to include all HARQ-ACK processes corresponding to the CC of URLLC.
  • the UE performs one shot based on a predetermined field (for example, Priority Indicator) of the DCI.
  • a predetermined field for example, Priority Indicator
  • the service type (or priority) to which the HARQ-ACK feedback is applied may be determined.
  • the UE reports HARQ-ACK for URLLC as a valid HARQ-ACK value. May be good.
  • the HARQ-ACK for URLLC may be mapped to a predetermined position in the codebook based on at least one of the HARQ-ACK process number and the CC index on which the URLLC is scheduled (see FIG. 9B).
  • FIG. 9B shows an example of a HARQ-ACK codebook (CB # 1) corresponding to URLLC.
  • the HARQ-ACK codebook size is the number of CCs scheduled for URLLC (here, 1 (CC # 2)) and the number of HARQ-ACK processes supported by the CC (here, 8 (# 0 to)). It may be determined based on # 7)).
  • the UE includes HARQ-ACK for URLLC (here, HARQ-ACK processes # 5 and # 6 of CC # 2) in CB # 1 as a valid HARA-ACK value.
  • the UE may report HARQ-ACK for eMBB as a valid HARQ-ACK value. ..
  • the HARQ-ACK for the eMBB may be mapped to a predetermined position in the codebook based on at least one of the HARQ-ACK process number and the CC index (see FIG. 9C).
  • FIG. 9C shows an example of the HARQ-ACK codebook (CB # 2) corresponding to eMBB.
  • the HARQ-ACK codebook size is the number of CCs scheduled for eMBB (here, 1 (CC # 1)) and the number of HARQ-ACK processes supported by the CC (here, 8 (# 0 to)). It may be determined based on # 7)).
  • the UE includes HARQ-ACK for eMBB (here, HARQ-ACK processes # 1 and # 3 of CC # 1) in CB # 2 as a valid HARA-ACK value.
  • the codebook to be applied in the HARQ-ACK feedback is determined to be quasi-static (for example, the number of CCs and the number of HARQ-ACK processes). Even so, the codebook size can be reduced.
  • the HARQ-ACK process number set for each CC is associated with the service type (or is grouped according to the service type). That is, in a certain CC, a first HARQ-ACK process group (one or more HARQ-ACK process numbers) is set for eMBB, and a second HARQ-ACK process group (for example, another HARQ) is set for URLLC. -ACK process number) may be set.
  • the HARQ-ACK process group may be referred to as the HARQ-ACK process set.
  • an odd HARQ-ACK process number is set to one service type (eg eMBB) and an even HARQ-ACK process number is set to the other service type (eg URLLC).
  • the number of HARQ-ACK process numbers associated with each service type may be set to be equal, or may be set to be large for one service type (for example, URLLC). ..
  • the HARQ-ACK process number associated with each service type may be defined in the specification or from the base station to the UE using at least one of higher layer signaling and DCI (eg, request / trigger DCI). May be notified to. Further, the HARQ-ACK process number corresponding to each service type may be set differently for each CC, or the HARQ-ACK process number corresponding to the service type may be set in common in a plurality of CCs.
  • Only the HARQ-ACK process number in the HARQ-ACK process group (HARQ-ACK procedures set / group) set in the service type may be applied to the PDSCH corresponding to each service type scheduled in the UE.
  • CC # 1 and CC # 2 are set for the UE supporting eMBB and URLLC, eight HARQ-ACK processes in CC # 1, and four in CC # 2. Shows the case where the HARQ-ACK process can be set.
  • the first HARQ-ACK process group ⁇ # 0, # 2, # 4, # 6 ⁇ is set for URLLC
  • the second HARQ-ACK process group ⁇ # for eMBB It shows the case where 1, # 3, # 5, # 7 ⁇ is set.
  • two PDSCHs for eMBB (corresponding to HARQ-ACK processes # 1 and # 3) and PDSCHs for URLLC (HARQ-ACK process # 6) are scheduled in CC # 1, and in CC # 2. It shows the case where PDSCH for URLLC (corresponding to HARQ-ACK process # 2) is scheduled.
  • the HARQ-ACK codebook (or 1-shot HARQ-ACK feedback) for the eMBB may be requested or specified by the DCI for the eMBB.
  • the HARQ-ACK codebook may be configured to include a HARQ-ACK process included in the HARQ-ACK process group for eMBB in the CC set in the UE.
  • the HARQ-ACK codebook (or 1-shot HARQ-ACK feedback) for URLLC may be requested or specified by the DCI for URLLC.
  • the HARQ-ACK codebook may be configured to include a HARQ-ACK process included in the HARQ-ACK process group for URLLC in the CC set in the UE.
  • the UE performs one shot based on a predetermined field (for example, Priority Indicator) of the DCI.
  • a predetermined field for example, Priority Indicator
  • the service type (or priority) to which the HARQ-ACK feedback is applied may be determined.
  • the UE reports HARQ-ACK for URLLC as a valid HARQ-ACK value. May be good.
  • the HARQ-ACK for URLLC may be mapped to a predetermined position in the codebook based on at least one of the CC index and the HARQ-ACK process number set in the UE (see FIG. 10B).
  • FIG. 10B shows an example of a HARQ-ACK codebook (CB # 1) corresponding to URLLC.
  • the HARQ-ACK codebook size is the number of CCs set in the UE (here, 2) and the number of HARQ-ACK processes included in the HARQ-ACK process group for URLLC in each CC (here, CC # 1). 4 in, and 2 in CC # 2).
  • the UE includes HARQ-ACK for URLLC (here, HARQ-ACK process # 6 of CC # 1 and HARQ-ACK process # 2 of CC # 2) in CB # 1 as a valid HARA-ACK value.
  • the UE may report HARQ-ACK for eMBB as a valid HARQ-ACK value. ..
  • the HARQ-ACK for the eMBB may be mapped to a predetermined position in the codebook based on at least one of the CC index and the HARQ-ACK process number set in the UE (see FIG. 10C).
  • FIG. 10C shows an example of the HARQ-ACK codebook (CB # 2) corresponding to eMBB.
  • the HARQ-ACK codebook size is the number of CCs set in the UE (here, 2) and the number of HARQ-ACK processes included in the HARQ-ACK process group for eMBB in each CC (here, CC # 1). 4 in, and 2 in CC # 2).
  • the UE includes HARQ-ACK for eMBB (here, HARQ-ACK processes # 1 and # 3 of CC # 1) in CB # 2 as a valid HARA-ACK value.
  • the codebook applied in the HARQ-ACK feedback is determined to be quasi-static (for example, the number of CCs and the number of HARQ-ACK processes). Even in this case, the codebook size can be reduced.
  • the HARQ-ACK process number and CC set in the UE are dynamically scheduled for a plurality of service types. That is, it is assumed that the same HARQ-ACK process number and CC can be applied to a plurality of service types. Further, it is assumed that the HARQ-ACK codebook size is dynamically set based on the scheduled PDSCH.
  • the UE may control the HARQ-ACK feedback (for example, HARQ-ACK codebook generation) based on the counter DAI and the total DAI included in the DCI.
  • the HARQ-ACK codebook size is determined by the total DAI contained in the request / trigger DCI, and the position of the HARQ-ACK in the codebook is determined based on the counter DAI contained in the DAI scheduling the PDSCH. It may be (see FIG. 11A).
  • the UE When the UE receives a request / trigger DCI requesting 1-shot HARQ-ACK feedback for URLLC, the UE receives HARQ-ACK for URLLC (here, # 2, # 3) based on the request / trigger DCI. Is included in the URLLC codebook (CB # 1) (see FIG. 11B). The codebook size of CB # 1 may be determined based on the total DAI included in the request / trigger DCI.
  • the position of HARQ-ACK corresponding to each PDSCH in the codebook may be determined based on the counter DAI included in the DCI that schedules the PDSCH.
  • a case is shown in which HARQ-ACK corresponding to PDSCH # 2 having a small counter DAI value is mapped to the position of # 0, and HARQ-ACK corresponding to PDSCH # 3 is mapped to the position of # 1.
  • the UE uses HARQ-ACK for eMBB (here, # 1) for eMBB based on the request / trigger DCI. Included in the codebook (CB # 2) (see FIG. 11C). The codebook size of CB # 2 may be determined based on the total DAI included in the request / trigger DCI.
  • the position of HARQ-ACK corresponding to each PDSCH in the codebook may be determined based on the counter DAI included in the DCI that schedules the PDSCH.
  • the case where HARQ-ACK corresponding to PDSCH # 1 is mapped to the position of # 0 is shown.
  • the codebook size of the 1-shot HARQ-ACK feedback is determined based on the total DAI included in the request / trigger DCI is shown, but the present invention is not limited to this.
  • the codebook size may be determined based on the total DAI included in the last DCI that schedules PDSCH for each service type.
  • the HARQ-ACK codebook applied to the 1-shot HARQ-ACK feedback has been described, but the HARQ-ACK codebook is the HARQ-ACK feedback performed before the 1-shot HARQ-ACK feedback request. May be applied.
  • the one-shot HARQ-ACK feedback shown in the first aspect and the one-shot HARQ-ACK feedback shown in the second aspect may be applied in combination (for example, by switching).
  • the base station may notify the UE whether the one-shot HARQ-ACK feedback includes multiple service types (eMBB and URLLC) using at least one of higher layer signaling and L1 signaling. ..
  • the L1 signaling may be DCI (eg, request / trigger DCI).
  • a new field or an existing field may be used to specify whether the 1-shot HARQ-ACK feedback supports a configuration including a plurality of service types. Even if the request / trigger DCI is provided with a predetermined bit field (for example, a 2-bit field) to notify information about the service type to which the one-shot HARQ-ACK feedback (or one HARQ-ACK codebook) is applied. good.
  • a predetermined bit field for example, a 2-bit field
  • the 1-shot HARQ-ACCK feedback supports a plurality of service types
  • the predetermined bit field is "01”
  • the 1-shot HARQ-ACK feedback includes only eMBB, and when it is "10". It may mean that the one-shot HARQ-ACK feedback includes only URLLC.
  • 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. 12 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 between a plurality of Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)).
  • 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).
  • -UTRA Dual Connectivity (NE-DC) may be included.
  • 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 to detect PDCCH.
  • CORESET corresponds to a resource that searches for 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 for example.
  • Uplink Control Information (UCI) including at least one of SR) may be transmitted.
  • 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. 13 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 transform, 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 measuring 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 transmitting unit and the receiving 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 transmit downlink control information that triggers feedback of HARQ-ACK of one shot.
  • the control unit 110 controls the reception of the HARQ-ACK corresponding to each of the plurality of service types or the codebook containing the HARQ-ACK having different priorities. You may.
  • the control unit 110 separately includes HARQ-ACK corresponding to a plurality of service types or HARQ-ACK having different priorities. Reception may be controlled.
  • FIG. 14 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 transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may be composed of at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.
  • the transmission / reception unit 220 receives the downlink control information that triggers the feedback of HARQ-ACK of one shot.
  • control unit 210 gives feedback of HARQ-ACK based on downlink information
  • the control unit 210 gives feedback of HARQ-ACK corresponding to a plurality of service types or HARQ-ACK having different priorities by using a common codebook. You may control it.
  • HARQ-ACK corresponding to a plurality of service types or HARQ-ACK having different priorities may be simultaneously triggered by downlink control information.
  • the control unit 210 may determine the uplink shared channel to be used for the feedback of HARQ-ACK based on the uplink control channel setting information set for a specific service type or a specific priority. Alternatively, the control unit 210 may determine the uplink shared channel to be used for the feedback of the HARQ-ACK based on the downlink control information.
  • control unit 210 when the control unit 210 gives feedback of HARQ-ACK based on the downlink information, the control unit 210 feeds back HARQ-ACK corresponding to a plurality of service types or HARQ-ACK having different priorities by using different codebooks. May be controlled. HARQ-ACK corresponding to a plurality of service types or HARQ-ACK having different priorities may be separately triggered by downlink control information.
  • At least one of a common HARQ-ACK process number and a common component carrier may be applied.
  • at least one of different HARQ-ACK process numbers and different component carriers may be applied.
  • 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. 15 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, such as 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 terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings.
  • channels, symbols and signals may be read interchangeably.
  • the signal may be a message.
  • the reference signal may be abbreviated as RS, and may be referred to as a pilot, a pilot signal, or the like depending on the applied standard.
  • the component carrier Component Carrier (CC)
  • CC Component Carrier
  • 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 transceiver in the frequency domain, a specific windowing process performed by the transceiver 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. Further, the mini slot may be referred to as a sub slot. A minislot may consist of a smaller number of symbols than the slot.
  • the PDSCH (or PUSCH) transmitted in time units larger than the minislot may be referred to as 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.
  • TTIs shorter than normal TTIs may be referred to as shortened TTIs, short TTIs, partial TTIs (partial or fractional TTIs), shortened subframes, short subframes, minislots, subslots, slots, and 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, etc.) 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 the number of RBs.
  • 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 other devices.
  • 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-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. Can be used as an antenna.
  • 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”).
  • an uplink channel, a downlink 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)
  • LTE 802.16 WiMAX (registered trademark)
  • 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.
  • connection are any direct or indirect connection or connection between two or more elements. Means, and can include the presence of one or more intermediate elements between two elements that are “connected” or “joined” to each other.
  • the connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection” may be read as "access”.
  • the radio frequency 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

Un terminal selon un aspect de la présente divulgation comprend : une unité de réception pour recevoir des informations de commande de liaison descendante en tant que déclenchement d'une rétroaction HARQ-ACK unique; et une unité de commande pour commander une rétroaction sur un HARQ-ACK pour de multiples types de service ou un HARQ-ACK avec différentes priorités au moyen d'un livre de codes commun dans le cas d'une rétroaction sur le HARQ-ACK sur la base des informations de liaison descendante.
PCT/JP2020/003563 2020-01-30 2020-01-30 Terminal, procédé de communication sans fil, et station de base WO2021152804A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2020/003563 WO2021152804A1 (fr) 2020-01-30 2020-01-30 Terminal, procédé de communication sans fil, et station de base
CN202080095110.4A CN115023967A (zh) 2020-01-30 2020-01-30 终端、无线通信方法以及基站

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/003563 WO2021152804A1 (fr) 2020-01-30 2020-01-30 Terminal, procédé de communication sans fil, et station de base

Publications (1)

Publication Number Publication Date
WO2021152804A1 true WO2021152804A1 (fr) 2021-08-05

Family

ID=77079729

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/003563 WO2021152804A1 (fr) 2020-01-30 2020-01-30 Terminal, procédé de communication sans fil, et station de base

Country Status (2)

Country Link
CN (1) CN115023967A (fr)
WO (1) WO2021152804A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220240274A1 (en) * 2021-01-26 2022-07-28 Qualcomm Incorporated Feedback methods for subband full duplex systems

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190364543A1 (en) * 2018-05-22 2019-11-28 Mediatek Singapore Pte. Ltd. Method And Apparatus For Reporting Hybrid Automatic Repeat Request-Acknowledgement Information For Different Service Types In Mobile Communications

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190364543A1 (en) * 2018-05-22 2019-11-28 Mediatek Singapore Pte. Ltd. Method And Apparatus For Reporting Hybrid Automatic Repeat Request-Acknowledgement Information For Different Service Types In Mobile Communications

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "UCI Enhancements for eURLLC", 3GPP DRAFT; R1-1912960, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, Nevada, USA; 20191118 - 20191122, 9 November 2019 (2019-11-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051823722 *
XIAOMI: "Discussion on UCI enhancement for URLLC", 3GPP DRAFT; R1-1911994, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051819889 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220240274A1 (en) * 2021-01-26 2022-07-28 Qualcomm Incorporated Feedback methods for subband full duplex systems
US11716753B2 (en) * 2021-01-26 2023-08-01 Qualcomm Incorporated Feedback methods for subband full duplex systems

Also Published As

Publication number Publication date
CN115023967A (zh) 2022-09-06

Similar Documents

Publication Publication Date Title
WO2021152805A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2020245973A1 (fr) Terminal et procédé de communication sans fil
WO2020240868A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2020225917A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2020217408A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2020110244A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2022039164A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2020188821A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2020202478A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2020188644A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2020095457A1 (fr) Terminal utilisateur
WO2021255936A1 (fr) Terminal, procédé de communication radio et station de base
JP7351921B2 (ja) 端末、無線通信方法、基地局及びシステム
JP7490641B2 (ja) 端末、無線通信方法及びシステム
WO2021053734A1 (fr) Terminal et procédé de communication sans fil
WO2021053733A1 (fr) Terminal et procédé de communication sans fil
WO2020188666A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2020202448A1 (fr) Terminal utilisateur et procédé de communication sans fil
WO2021152804A1 (fr) Terminal, procédé de communication sans fil, et station de base
WO2022009315A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2022009346A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2022009347A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2022074802A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2022024224A1 (fr) Terminal, procédé de communication sans fil et station de base
WO2021186701A1 (fr) Terminal, procédé de communication sans fil et station de base

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: 20916808

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20916808

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP