WO2022009346A1 - Terminal, wireless communication method, and base station - Google Patents

Terminal, wireless communication method, and base station Download PDF

Info

Publication number
WO2022009346A1
WO2022009346A1 PCT/JP2020/026739 JP2020026739W WO2022009346A1 WO 2022009346 A1 WO2022009346 A1 WO 2022009346A1 JP 2020026739 W JP2020026739 W JP 2020026739W WO 2022009346 A1 WO2022009346 A1 WO 2022009346A1
Authority
WO
WIPO (PCT)
Prior art keywords
harq
ack
priority
dci
pdsch
Prior art date
Application number
PCT/JP2020/026739
Other languages
French (fr)
Japanese (ja)
Inventor
優元 ▲高▼橋
慎也 熊谷
聡 永田
Original Assignee
株式会社Nttドコモ
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 株式会社Nttドコモ filed Critical 株式会社Nttドコモ
Priority to PCT/JP2020/026739 priority Critical patent/WO2022009346A1/en
Publication of WO2022009346A1 publication Critical patent/WO2022009346A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14Spectrum sharing arrangements between different networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/04Error control

Definitions

  • This disclosure relates to terminals, wireless communication methods and base stations in next-generation mobile communication systems.
  • LTE Long Term Evolution
  • UMTS Universal Mobile Telecommunications System
  • 3GPP Rel.10-14 LTE-Advanced (3GPP Rel.10-14) has been specified for the purpose of further increasing the capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).
  • a successor system to LTE for example, 5th generation mobile communication system (5G), 5G + (plus), 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.
  • future wireless communication systems for example, 5G, NR, etc.
  • high speed and large capacity for example, enhanced Mobile Broad Band (eMBB)
  • ultra-many terminals for example, massive Machine Type Communication (mMTC), Internet of Things).
  • IoT ultra-high reliability and low latency
  • URLLC Ultra Reliable and Low Latency Communications
  • multiple services also referred to as use cases, communication types, etc.
  • priorities are set for signals / channels, and it is considered to control communication based on the priorities set for each signal / channel. For example, when a plurality of signals / channels overlap, it is assumed that transmission / reception is controlled based on the priority of each signal / channel.
  • HARQ-ACKs or HARQ-ACKs corresponding to one or more downlink shared channels respectively
  • feed back one or more HARQ-ACKs or HARQ-ACKs corresponding to one or more downlink shared channels respectively.
  • one of the purposes of the present disclosure is to provide a terminal, a wireless communication method, and a base station capable of appropriately controlling one or more UL transmissions for which priority setting is supported.
  • the terminal includes a receiving unit that receives downlink control information instructing a one-shot HARQ-ACK (Hybrid Automatic Repeat reQuest ACK knowledgement), and information regarding the priority of UL transmission that can be acquired from the downlink control information. Based on this, it is characterized by having a control unit for determining the priority of the one-shot HARQ-ACK.
  • HARQ-ACK Hybrid Automatic Repeat reQuest ACK knowledgement
  • one or more UL transmissions for which priority setting is supported can be appropriately controlled.
  • FIG. 1A and 1B are diagrams showing an example of UL transmission control based on priority.
  • 2A-2C are diagrams showing other examples of UL transmission control based on priority.
  • FIG. 3 is a diagram showing an example of an enhanced dynamic HARQ feedback method.
  • FIG. 4 is a diagram showing an example of a one-shot HARQ feedback method.
  • FIG. 5 is a diagram showing an example of a case where a plurality of HARQ-ACK codebooks are transmitted in a predetermined slot.
  • FIG. 6 is a diagram showing an example of UL transmission control according to the first aspect.
  • FIG. 7 is a diagram showing an example of UL transmission control according to the second aspect.
  • FIG. 8 is a diagram showing another example of UL transmission control according to the second aspect.
  • FIG. 9 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
  • FIG. 10 is a diagram showing an example of the configuration of a base station according to an embodiment.
  • FIG. 11 is a diagram showing an example of the configuration of the user terminal according to the embodiment.
  • FIG. 12 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment.
  • ⁇ Traffic type> In future wireless communication systems (eg, NR), further advancement of mobile broadband (eg enhanced Mobile Broadband (eMBB)), machine type communication that realizes multiple simultaneous connections (eg massive Machine Type Communications (mMTC), Internet) Assumed traffic types (also referred to as services, service types, communication types, use cases, etc.) such as of Things (IoT)), high-reliability and low-latency communication (eg, Ultra-Reliable and Low-Latency Communications (URLLC)). Will be done. For example, URLLC requires less delay and higher reliability than eMBB.
  • IoT of Things
  • 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 traffic type for PDSCH may be determined based on at least one of the following: An MCS index table (eg, 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 eg, 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 SR traffic type may be determined based on the upper layer parameter used as the SR identifier (SR-ID).
  • the upper layer parameter may indicate whether the SR traffic type is eMBB or URLLC.
  • the CSI traffic type may be determined based on the configuration information (CSIreportSetting) related to the CSI report, the DCI type used for the trigger, the DCI transmission parameter, and the like.
  • the setting information, DCI type, etc. may indicate whether the traffic type of the CSI is eMBB or URLLC. Further, the setting information may be an upper layer parameter.
  • the traffic type of PUSCH may be determined based on at least one of the following.
  • -The MCS index table used to determine at least one of the modulation order, target code rate, and TBS of the PUSCH for example, whether or not to use the MCS index table 3.
  • RNTI used for CRC scrambling of DCI used for scheduling the PUSCH 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 the URLLC requirement may include 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 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 service, service type, communication type, use case, 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 is a signal (for example, UCI such as HARQ-ACK, a reference signal, etc.), a channel (PDSCH, PUSCH, PUCCH, etc.), a reference signal (for example, a channel state information (CSI), a sounding reference signal (SRS), etc.). , Scheduling Request (SR), and HARQ-ACK Codebook. Further, priorities may be set for PUCCH used for SR transmission, PUCCH used for HARQ-ACK transmission, and PUCCH used for CSI transmission.
  • the priority may be defined by a first priority (for example, high) and a second priority (for example, low) which 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.
  • priorities may be set for the dynamically scheduled HARQ-ACK for PDSCH, HARQ-ACK for semi-persistent PDSCH (SPS PDSCH), and HARQ-ACK for SPS PDSCH release.
  • a priority may be set for the HARQ-ACK codebook corresponding to these HARQ-ACKs.
  • the priority of the PDSCH may be read as the priority of HARQ-ACK for the PDSCH.
  • the priority may be set for the dynamic grant-based PUSCH, the setting grant-based PUSCH, and the like.
  • the priority of the scheduling request may be set by a higher layer parameter (for example, schedulingRequestPriority).
  • the priority of the HARQ-ACK over the PDSCH scheduled by the DCI (eg, the dynamic PDSCH) may be notified by the DCI.
  • the priority of HARQ-ACK for SPS PDSCH may be set by a higher parameter (for example, HARQ-ACK-Codebook-indicator-forSPS), or may be notified by DCI instructing activation of SPS PDSCH.
  • a predetermined priority (for example, low) may be set for the P-CSI / SP-CSI transmitted by PUCCH.
  • the A-CSI / SP-CSI transmitted by PUSCH may be notified of the priority by DCI (for example, DCI for triggering or DCI for activation).
  • the priority of the dynamic grant-based PUSCH may be notified by the DCI that schedules the PUSCH.
  • Setting Grant-based PUSCH priority may be set by a higher layer parameter (eg, priority).
  • A-SRS triggered by P-SRS / SP-SRS, DCI (eg, DCI format 0_1 / DCI format 2_3) may be set to a predetermined priority (eg, low).
  • the UE may control UL transmission based on priority when multiple UL signals / UL channels overlap (or collide).
  • time resources When multiple UL signals / UL channels overlap, the time resources (or time resources and frequency resources) of multiple UL signals / UL channels overlap, or the transmission timing of multiple UL signals / UL channels is different. It may be the case of overlapping.
  • a time resource may be read as a time domain or a time domain. Time resources may be in symbol, slot, subslot, or subframe units.
  • Overlapping of multiple UL signals / UL channels in the same UE means that multiple UL signals / UL channels overlap at least in the same time resource (eg, symbol). You may. Also, collision of UL signals / UL channels in different UEs (eg, inter-UE) means that multiple UL signals / UL channels are overloaded in the same time resource (eg, symbol) and frequency resource (eg, RB). It may mean to wrap.
  • the UE controls to multiplex the plurality of UL signals / UL channels to one UL channel for transmission (multiplex). See FIG. 1A).
  • HARQ-ACK (or PUCCH for HARQ-ACK transmission) in which the first priority (high) is set and UL data / UL-SCH in which the first priority (high) is set. (Or PUSCH for UL data / UL-SCH transmission) overlaps.
  • the UE multiplexes (or maps) the HARQ-ACK to the PUSCH and transmits both the UL data and the HARQ-ACK.
  • the UE When multiple UL signals / UL channels with different priorities overlap, the UE performs a higher priority UL transmission (eg, prioritizes a higher priority UL transmission) and a lower priority UL transmission. It may be controlled so that it does not exist (for example, it drops) (see FIG. 1B).
  • the UL data / HARQ-ACK (or the UL channel for UL data / HARQ-ACK transmission) in which the first priority (high) is set and the second priority (low) are set.
  • the case where the UL data / HARQ-ACK (or the UL channel for UL data / HARQ-ACK transmission) overlaps is shown.
  • the UE controls to drop the UL data / HARQ-ACK having a low priority and prioritize and transmit the UL data / HARQ-ACK having a high priority.
  • the UE may change (for example, postpone or shift) the transmission timing of the UL transmission having a low priority.
  • transmission may be controlled by two steps.
  • UL channels having the same priority are multiplexed into one UL channel (see FIG. 2B).
  • UL transmissions having different priorities may be controlled so as to preferentially transmit UL transmissions having higher priority and drop UL transmissions having lower priority (see FIG. 2C).
  • Unlicensed band In the unlicensed band (for example, 2.4 GHz band, 5 GHz band, 6 GHz band, etc.), 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 transmission device 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
  • the transmitting device may be, for example, a base station (for example, gNB: gNodeB) for the downlink (DL) and a user terminal (for example, User Equipment (UE)) for the 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 a backoff period) after the LBT detects that there is no transmission of another device (idle state). ..
  • unlicensed bands are also being considered for 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.
  • NR-U may also include dual connectivity (DC) between licensed bands and unlicensed bands, and stand-alone (Stand-Alone (SA)) unlicensed bands.
  • DC dual connectivity
  • SA stand-alone
  • the node for example, base station, UE
  • NR-U confirms that the channel is free (idle) by LBT for coexistence with other systems or other operators, and then starts transmission.
  • 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 may be referred to as channel occupation time (Channel Occupancy Time (COT)).
  • LBT-idle may be read as the success of LBT (LBT success).
  • LBT-busy may be read as LBT failure.
  • 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 (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 be simply referred to as a codebook.
  • the number of bits (size) and the like included in the HARQ-ACK codebook may be determined quasi-static (semi-static) or dynamically (dynamic).
  • 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 will have a PDSCH candidate (or PDSCH opportunity) corresponding to that range, with or without PDSCH scheduling, in a range (eg, a range set based on higher layer parameters).
  • a range eg, a range set based on higher layer parameters.
  • the HARQ-ACK bit for (occasion)) may be fed back.
  • the range is a set of a specific number of opportunities for receiving candidate PDSCHs, or a specific number of monitoring opportunities for a Physical Downlink Control Channel (PDCCH) for a period of time (eg, a specific number of opportunities for receiving a candidate PDSCH (PDCCH). Monitoring occasion)), the number of CCs set or activated in the UE, the number of TBs (number of layers or ranks), the number of CBGs per TB, and the presence or absence of spatial bundling. You may.
  • the specific range is also referred to as a HARQ-ACK window, a HARQ-ACK bundling window, a HARQ-ACK feedback window, and the like.
  • the UE allocates the HARQ-ACK bit for the PDSCH in the codebook even if there is no PDSCH scheduling for the UE. If 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 specific range.
  • the UE determines the number of bits in the Type 2 HARQ-ACK codebook based on a particular field in the DCI (eg, the Downlink Assignment Indicator (Index) (DAI) field). May be 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 specific period.
  • a C-DAI in a DCI that schedules data within that particular period may indicate a number that is first counted in the frequency domain (eg, CC) and then in the time domain within that particular period. good.
  • C-DAI may receive PDSCH or semi-persistent scheduling (SPS) for one or more DCIs included in a particular period in ascending order of serving cell index and then in ascending order of PDCCH monitoring opportunities. It may correspond to the value obtained by counting the releases.
  • SPS semi-persistent scheduling
  • T-DAI may indicate the total value (total number) of data scheduled within a specific period.
  • a T-DAI in a DCI that schedules data in a time unit (eg, PDCCH monitoring opportunity) within that particular period may be up to that time unit (also referred to as point, timing, etc.) within that particular period. It may indicate the total number of scheduled data.
  • the HARQ-ACK codebook is set separately for different service types (or PDSCH or HARQ-ACK with different priorities). 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 corresponding to URLLC (eg, first priority) and a second HARQ-ACK codebook corresponding to eMBB (eg, second priority) are configured. May be good.
  • the first PUCCH setting parameter corresponding to the first HARQ-ACK codebook (for example, PUCCH configuration or PUCH configuration parameters) and the second PUCCH setting parameter corresponding to the second HARQ-ACK codebook. May be supported or configured separately.
  • the PUCCH setting parameters are the PUCCH resource (or PUCCH resource set) applied to the HARQ-ACK transmission, the PUCCH transmission timing (for example, K1 set), the maximum coding rate (for example, max-code rate), and the PUCCH transmission. It may be at least one of the electric power.
  • the first PUCCH setting information may be applied to the HARQ-ACK feedback for URLLC
  • the second PUCCH setting information may be applied to the HARQ-ACK feedback for eMBB.
  • HARQ process For UEs configured with Carrier Aggregation (CA) or Dual Connectivity (DC), there may be one independent HARQ entity for each cell (CC) or cell group (CG).
  • CA Carrier Aggregation
  • DC Dual Connectivity
  • the HARQ entity may manage multiple HARQ processes in parallel.
  • DCI downlink control information
  • HPN downlink control information
  • HPN downlink control information
  • the HARQ entity manages multiple (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 identifier (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 was successfully decoded.
  • ACK acknowledgement
  • NACK Negative Acknowledgement
  • PUCCH Physical Uplink Control Channel
  • PUSCH Physical Uplink Control Channel
  • 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 Enhanced Dynamic HARQ Feedback
  • a HARQ-ACK codebook containing multiple HARQ-ACK processes to provide a transmission opportunity for HARQ-ACK feedback due to LBT failure in the UE or PUCCH detection error in the base station. It is being considered to request or trigger the UE to provide feedback.
  • the HARQ-ACK process (eg, DL HARQ-ACK process) may be HARQ-ACK in all CCs configured on the UE in the PUCCH group.
  • HARQ-ACK (or HARQ-ACK codebook) feedback that includes multiple HARQ-ACK processes includes enhanced dynamic HARQ-ACK feedback, enhanced dynamic HARQ feedback, and group-based.
  • HARQ feedback, enhanced dynamic HARQ-ACK codebook, etc. may be referred to.
  • Enhanced dynamic HARQ feedback may be notified from the base station to the UE using a specific DCI format.
  • the particular DCI format may be a UE-specific DCI format (eg, DCI format 1-11).
  • a particular DCI format may include a particular field to signal (request or trigger) enhanced dynamic HARQ feedback.
  • the specific field may be at least one of a PDSCH group index (PDSCH group index) field and a number of requested PDSCH group (s) fields.
  • a specific field (eg, PDSCH group index field, Number of requested PDSCH group (s) field) contained in a specific DCI format (for example, DCI format 1-11) is a specific field.
  • the higher layer parameter pdsch-HARQ-ACK-Codebook
  • enhanced dynamics eg enhancedDynamic-r16, enhancedDynamic
  • the PDSCH group index may be an index that identifies a group of PDSCHs scheduled by DCI including the PDSCH group index.
  • the UE will provide one or more HARQ feedback to the PDSCH group scheduled by that DCI in a resource. You may go.
  • the UE has one or more for the PDSCH group scheduled by the DCI and a PDSCH group different from the PDSCH group scheduled by the DCI.
  • HARQ feedback may be given at a resource. In other words, if the value of the requested PDSCH group number field in the DCI is "1", the UE may provide HARQ feedback to the PDSCH where the PDSCH group indexes "0" and "1" are set in a resource. good.
  • the specific DCI format may include a specific field (for example, a new feedback indicator (NFI) field).
  • NFI new feedback indicator
  • a specific upper layer parameter (pdsch-HARQ-ACK-Codebook) is set to the enhanced dynamic (enhancedDynamic-r16), and another field is used. If the upper layer parameter (NFI-TotalDAI-Included-r16) is not set, it may have a bit length of 1 bit, and in other cases, it may be 0 bit.
  • the other upper layer parameter includes the NFI and the T-DAI field of the unscheduled PDSCH group in the non-fallback DL grant DCI (eg DCI format 1-11). It may be a parameter indicating whether or not.
  • a UE requesting or triggering enhanced dynamic HARQ feedback may feed back a codebook containing one or more HARQ-ACK processes using PUCCH / PUSCH.
  • FIG. 3 is a diagram showing an example of an enhanced dynamic HARQ feedback method.
  • the UE monitors PDCCH1 and PDCCH2 in COT # 0 and monitors PDCCH3 in COT # 1.
  • PDSCH1, PDSCH2 and PDSCH3 are scheduled by DCI transmitted in each of PDCCH1, PDCCH2 and PDCCH3.
  • the PDSCH group index indicated for PDSCH1 is 0, and the PDSCH group index indicated for PDSCH2 and PDSCH3 is 1.
  • the UE starts LBT at the start symbols of PDCCH1 and PDCCH3.
  • the UE is instructed by PDCCH1 to transmit HARQ-ACK1 for PDSCH (PDSCH1) of group 0 in the HARQ-ACK transmission resource in COT # 0 (HARQ feedback timing (PDSCH-to-HARQ_feedback timing indicator)).
  • K1 is 2).
  • the UE does not transmit HARQ-ACK1 if the LBT at COT # 0 fails.
  • the UE when the HARQ feedback timing value (K1) included in the DCI received by the PDCCH2 is inapplicable for HARQ-ACK2 for the PDSCH (PDSCH2) of the group 1, the UE is determined. , HARQ-ACK2 is not transmitted (HARQ-ACK2 is retained) in the HARQ-ACK transmission resource in COT # 0.
  • the UE is instructed by PDCCH3 to transmit HARQ-ACK3 for the PDSCH (PDSCH3) of group 1 in the HARQ-ACK transmission resource in COT # 1 (K1 is 2).
  • the PDCCH group (PDSCH group 1) scheduled by the PDCCH 3 and the PDCCH 3 are not scheduled in the HARQ-ACK transmission resource in COT # 1.
  • the PDSCH group (PDSCH group 0) and the HARQ-ACK for the corresponding PDSCH are transmitted.
  • the UE when the UE succeeds in LBT in COT # 1, it transmits HARQ-ACK3. At this time, the UE multiplexes the HARQ-ACK1 that was not transmitted due to the failure of the LBT in COT # 0 and the held HARQ-ACK2 to the transmission resource of the HARK-ACK3, and transmits the HARQ-ACK1.
  • the UE may control one or more HARQ-ACK feedback in units of PDSCH groups based on the number of requested PDSCH groups included in the DCI.
  • HARQ-ACK codebook containing multiple (eg, all) HARQ-ACK processes to provide a transmission opportunity for HARQ-ACK feedback due to an LBT failure in the UE or a PUCCH detection error in the base station. It is being considered to request or trigger feedback from the UE.
  • the HARQ-ACK process (eg, DL HARQ-ACK process) may be HARQ-ACK in multiple (eg, all) CCs configured on the UE in the PUCCH group.
  • the feedback of HARQ-ACK (or HARQ-ACK codebook) including multiple (eg, all) HARQ-ACK processes in multiple (eg, all) CCs is one-shot (One-shot) HARQ.
  • -ACK feedback One-shot (One-shot) HARQ feedback may be referred to as HARQ-ACK one-shot feedback.
  • the one-shot HARQ feedback may be notified from the base station to the UE using a specific DCI format.
  • the particular DCI format may be a UE-specific DCI format (eg, DCI format 1-11).
  • a particular DCI format may include a particular field to signal one-shot HARQ-ACK feedback.
  • the specific field may be a one-shot HARQ-ACK request field.
  • a specific field (eg, a one-shot HARQ-ACK request field) contained in a specific DCI format (eg, DCI format 1-11) is a specific upper layer parameter (pdsch-HARQ-ACK).
  • pdsch-HARQ-ACK a specific upper layer parameter
  • -OneShotFeedback-r16 When -OneShotFeedback-r16 is set, it may have a bit length of 1 bit, and in other cases, it may be 0 bit.
  • the one-shot HARQ-ACK request may be a parameter that requests or triggers the UE to transmit a plurality of (for example, all) HARQ processes in a certain resource.
  • the UE will provide HARQ feedback to the PDSCH scheduled by the DCI containing the one-shot HARQ-ACK request in a resource. You may go. If the value of the one-shot HARQ-ACK request is "1", the UE has untransmitted HARQ feedback for the PDSCH and HARQ feedback for the PDSCH scheduled by the DCI containing the one-shot HARQ-ACK request. It may be done in resources.
  • a UE requesting or triggering one-shot HARQ feedback may use PUCCH / PUSCH to feed back a codebook containing a plurality of (for example, all) HARQ-ACK processes in each configured CC.
  • a new data indicator (New Data Indicator (NDI)) in the feedback, it is possible to avoid HARQ inconsistency between the UE and gNB.
  • NDI New Data Indicator
  • FIG. 4 is a diagram showing an example of a one-shot HARQ feedback method.
  • the arrangement of each channel resource and the timing of LBT in the example of FIG. 4 are the same as those of FIG.
  • the UE does not transmit HARQ-ACK1 if the LBT at COT # 0 fails. Further, regarding HARQ-ACK2 for PDSCH2, when the HARQ feedback timing value (K1) included in the DCI received by PDCCH2 is inapplicable, the UE performs the HARQ-ACK transmission resource in COT # 0. , Do not send HARQ-ACK2 (hold HARQ-ACK2).
  • the UE is instructed by PDCCH3 to transmit HARQ-ACK3 for the PDSCH (PDSCH3) of group 1 in the HARQ-ACK transmission resource in COT # 1 (K1 is 2). ).
  • the UE succeeds in LBT in COT # 1, it transmits HARQ-ACK3.
  • the UE receives HARQ-ACK1 which was not transmitted due to the failure of the LBT and HARQ-ACK2 which is held in COT # 0. It is multiplexed with the transmission resource of HARK-ACK3 and transmitted.
  • the UE may control one or more HARQ-ACK feedbacks based on the one-shot HARQ-ACK request contained in the DCI.
  • N Multiple HARQ-ACK Codebook Rel. From 16 onwards, it may be permissible to configure up to N HARQ-ACK codebooks in a predetermined slot (eg, 1 slot). N may be 2, for example. For example, when N is 2, the UE configures two codebooks for HARQ-ACK having different priorities (or codebooks corresponding to different priorities / different service types) in a predetermined slot, and the code concerned. You may feed back the book.
  • the UE generates a HARQ-ACK codebook (for example, HARQ-ACK in the HARQ-ACK codebook) based on the value of the priority notification field (for example, Priority Indicator field) included in the DCI corresponding to each PDSCH. Bit generation) may be controlled.
  • FIG. 5 shows an example of generating / feeding back two HARQ-ACK codebooks (here, CB # 0 and CB # 1) corresponding to different priorities in slot # n.
  • CB # 0 corresponds to a second priority (low) or eMBB
  • CB # 1 corresponds to a first priority (high) or URLLC.
  • the UE may generate and feed back two HARQ-ACK codebooks (CB # 0 and CB # 1) in slot # n.
  • HARQ- is based on the priority corresponding to HARQ-ACK (or CB). You may control the transmission of ACK.
  • multiple HARQ-ACKs are fed back together (for example, when performing one-shot HARQ-ACK feedback or HARQ-ACK feedback based on a PDSCH group), multiple HARQ-ACKs are used for each code. It may be included in the book. In such a case, how to apply / control the priority of UL transmission becomes a problem.
  • 1-shot HARQ-ACK feedback when applying 1-shot HARQ-ACK feedback, it is used for the priority of each HARQ-ACK included in the 1-shot HARQ-ACK feedback, or for 1-shot HARQ-ACK feedback (or 1-shot HARQ-ACK feedback).
  • the problem is how to set / apply the priority corresponding to the codebook).
  • the priority of each HARQ-ACK included in the PDSCH group or the HARQ-ACK corresponding to the PDSCH group (or the codebook of the HARQ-ACK) is supported.
  • the problem is how to set / apply the priority to be applied.
  • the present inventors have a priority over HARQ-ACK (or HARQ-ACK codebook) that feeds back in response to a one-shot HARQ-ACK feedback request, or the HARQ-ACK codebook.
  • the priority of HARQ-ACK to be included in the above was examined, and one aspect of the present embodiment was conceived.
  • the present inventors have a priority on HARQ-ACK (or HARQ-ACK codebook) that provides feedback based on a predetermined group (for example, PDSCH group) unit, or The priority of each HARQ-ACK corresponding to the PDSCH group was examined, and another aspect of this embodiment was conceived.
  • a predetermined group for example, PDSCH group
  • a / B may be read as at least one of A and B
  • a / B / C may be read as at least one of A, B and C.
  • the present disclosure can be applied not only to a wireless communication system to which NR-U is applied, but also to a wireless communication system to which NR-U is not applied.
  • the priority of the HARQ-ACK codebook (or the priority of HARQ-ACK) is the priority of PUCCH used for HARQ-ACK transmission or PUSCH used for HARQ-ACK transmission. It may be read as the priority of.
  • the UE may control one or more HARQ-ACKs to be fed back with a predetermined resource based on the one-shot HARQ-ACK request field included in the DCI (see FIG. 6).
  • FIG. 6 shows HARQ-ACK # 1 corresponding to PDSCH # 1 and HARQ-ACK # 2 corresponding to PDSCH # 2 based on the one-shot HARQ-ACK request included in DCI # 3 that schedules PDSCH # 3.
  • the case where HARQ-ACK # 3 corresponding to PDSCH # 3 is fed back by using a predetermined UL resource is shown.
  • DCI may be read as PDCCH.
  • the UL resource may be read as a HARQ-ACK codebook, a PUCCH resource, or a PUSCH resource.
  • the priority of HARQ-ACK (or HARQ-ACK codebook) to be fed back based on the one-shot HARQ-ACK request may be determined based on predetermined conditions.
  • the UE may determine the priority of HARQ-ACK to be fed back based on the 1-shot HARQ-ACK request based on the DCI (DCI # 3 in FIG. 6) including the 1-shot HARQ-ACK request field. ..
  • the UE may determine the priority for the one-shot HARQ-ACK based on the priority indicator field (for example, Priority Indicator field) included in the DCI (option 1-1).
  • the UE may determine the priority for 1-shot HARQ-ACK based on the configuration / parameters applied to the DCI (eg, DCI format) (option 1-2).
  • the UE may determine the priority of the HARQ-ACK codebook transmitted by the 1-shot HARQ-ACK based on the priority instruction field included in the DCI indicating the 1-shot HARQ-ACK request.
  • a first priority (high) or a second priority (low) may be set by the priority indicating field included in the DCI.
  • the priority is not limited to 2 levels, and any of 3 levels or higher may be notified.
  • the UE may control to feed back a plurality of HARQ-ACKs having different priorities at once ( Option 1-1-1).
  • the UE may control to select and feed back the HARQ-ACK of a specific priority. Good (option 1-1-2).
  • the UE feeds back one or more target HARQ-ACKs (for example, HARQ-ACK # 1, # 2, # 3 in FIG. 3) regardless of the priority. It may be controlled as follows.
  • the HARQ-ACK to be fed back includes a first HARQ-ACK with a first priority (high) and a second HARQ-ACK with a second priority (low).
  • the UE may control the first HARQ-ACK and the second HARQ-ACK to be transmitted together (for example, included in the same HARQ-ACK codebook).
  • the UE When the first priority (high) is indicated by the DCI instructing the one-shot HARQ-ACK request, the UE is of the first priority (high) HARQ-ACK and the second priority (low). At least one of HARQ-ACK may be included in the HARQ-ACK codebook and controlled to be fed back. In this case, the first priority (high) may be set as the priority of the HARQ-ACK codebook to be fed back in response to the one-shot HARQ-ACK request.
  • the UE is of the first priority (high) HARQ-ACK and the second priority (low) when the second priority (low) is indicated by the DCI instructing the one-shot HARQ-ACK request.
  • At least one of HARQ-ACK may be included in the HARQ-ACK codebook and controlled to be fed back.
  • a second priority (low) may be set as the priority of the HARQ-ACK codebook to be fed back in response to the one-shot HARQ-ACK request.
  • the priority of each HARQ-ACK subject to the one-shot HARQ-ACK feedback may be determined based on the DCI that schedules the PDSCH corresponding to each HARQ-ACK.
  • the HARQ-ACK to be included in the 1-shot HARQ-ACK feedback is determined based on the priority value (eg i) specified in the priority indicator field included in the DCI that directs the 1-shot HARQ-ACK request. You may. For example, even if HARQ-ACK having a priority equal to or higher than the value of the priority indicating field (for example, i) included in the DCI for instructing the one-shot HARQ-ACK request is selected and fed back as one-shot HARQ-ACK. good.
  • the UE selects HARQ-ACK with a priority of 2 or higher (eg, 1 or 2) and 1-shot HARQ-ACK feedback. May be applied. This allows one-shot HARQ-ACK feedback to be applied by selecting a particular priority HARQ-ACK.
  • the UE may control to select and feed back the HARQ-ACK of a specific priority.
  • HARQ-ACK For example, as HARQ-ACK to be the target of 1-shot HARQ-ACK feedback, a first HARQ-ACK having a first priority (high) and a second HARQ-ACK having a second priority (low) are used. It is assumed that it is included. In such a case, the UE should send the HARQ-ACKs having either priority (first priority or second priority) together (for example, included in the same HARQ-ACK codebook). You may control it. In this case, the one-shot HARQ-ACK feedback may not be applied to the HARQ-ACK having another priority.
  • 1-shot HARQ-ACK feedback may be applied to HARQ-ACK having the first priority (high).
  • the UE may select one or more HARQ-ACKs having a first priority (high) to provide one-shot HARQ-ACK feedback.
  • the priority of each HARQ-ACK subject to the one-shot HARQ-ACK feedback may be determined based on the DCI that schedules the PDSCH corresponding to each HARQ-ACK.
  • the first priority may be set for the HARQ-ACK codebook to be fed back.
  • the DCI for instructing the one-shot HARQ-ACK feedback may not include the priority instruction field.
  • the UE may not expect / expect that one-shot HARQ-ACK feedback is indicated if the DCI includes a priority indicator field.
  • 1-shot HARQ-ACK feedback may be applied to HARQ-ACK having a second priority (low).
  • the UE may select one or more HARQ-ACKs having a second priority (low) to provide one-shot HARQ-ACK feedback.
  • the HARQ-ACK codebook to be fed back may be set to the second priority.
  • the DCI for instructing the one-shot HARQ-ACK feedback may not include the priority instruction field.
  • the UE may not expect / expect that one-shot HARQ-ACK feedback is indicated if the DCI includes a priority indicator field.
  • the priority of HARQ-ACK to which the one-shot HARQ-ACK feedback is applied may be notified / set to the UE by using the upper layer signaling / DCI.
  • the DCI for instructing the one-shot HARQ-ACK feedback may not include the priority instruction field.
  • the UE may not expect / expect that one-shot HARQ-ACK feedback is indicated if the DCI includes a priority indicator field.
  • the UE may determine the HARQ-ACK to which the 1-shot HARQ-ACK feedback is applied based on a predetermined field (for example, a priority instruction field) included in the DCI that instructs the 1-shot HARQ-ACK request. If the DCI indicating the one-shot HARQ-ACK request indicates a first priority (high), the UE selects one or more HARQ-ACKs with the first priority (high) and 1 Shot HARQ-ACK feedback may be given. Further, the HARQ-ACK codebook (or PUCCH / PUSCH) used for the one-shot HARQ-ACK may have a first priority set.
  • a predetermined field for example, a priority instruction field
  • the UE selects one or more HARQ-ACKs with the second priority (low).
  • One-shot HARQ-ACK feedback may be given.
  • the HARQ-ACK codebook (or PUCCH / PUSCH) used for the one-shot HARQ-ACK may have a second priority set.
  • the 1-shot HARQ-ACK feedback can be flexibly controlled based on the priority.
  • the UE may determine the priority for the 1-shot HARQ-ACK based on the format of the DCI indicating the 1-shot HARQ-ACK request.
  • a first priority (high) or a second priority (low) may be set based on the DCI format.
  • the priority is not limited to 2 levels, and any of 3 levels or higher may be notified.
  • the first DCI format eg DCI format 1_2
  • the second DCI format eg DCI format 1_1
  • the UE may control to feed back a plurality of HARQ-ACKs having different priorities at once ( Option 1-2-1).
  • the UE may control to select and feed back the HARQ-ACK of a specific priority. Good (option 1-2-2).
  • the UE feeds back one or more target HARQ-ACKs (for example, HARQ-ACK # 1, # 2, # 3 in FIG. 3) regardless of the priority. It may be controlled as follows.
  • HARQ-ACK For example, as HARQ-ACK to be the target of 1-shot HARQ-ACK feedback, a first HARQ-ACK having a first priority (high) and a second HARQ-ACK having a second priority (low) are used. It is assumed that it is included. In such a case, the UE may control the first HARQ-ACK and the second HARQ-ACK to be transmitted together (for example, included in the same HARQ-ACK codebook).
  • the UE When the first priority (high) is specified by the DCI format (for example, DCI format 1_2) instructing the one-shot HARQ-ACK request, the UE has the first priority (high) HARQ-ACK and the first. At least one of the 2 low priority HARQ-ACKs may be included in the HARQ-ACK codebook and controlled to be fed back. In this case, the first priority (high) may be set as the priority of the HARQ-ACK codebook) that feeds back in response to the one-shot HARQ-ACK request.
  • the UE has a first priority (high) HARQ-ACK and a second. At least one of the 2 low priority HARQ-ACKs may be included in the HARQ-ACK codebook and controlled to be fed back. In this case, a second priority (low) may be set as the priority of the HARQ-ACK codebook to be fed back in response to the one-shot HARQ-ACK request.
  • the priority of each HARQ-ACK subject to the one-shot HARQ-ACK feedback may be determined based on the DCI (for example, DCI format) that schedules the PDSCH corresponding to each HARQ-ACK.
  • the HARQ-ACK to be included in the 1-shot HARQ-ACK feedback may be determined based on the priority value (eg, i) determined based on the DCI format indicating the 1-shot HARQ-ACK request. For example, a HARQ-ACK having a priority value equal to or higher than the priority value (for example, i) determined based on the DCI format indicating the 1-shot HARQ-ACK request is selected and fed back as a 1-shot HARQ-ACK. You may.
  • the UE may select HARQ-ACK with a priority of 2 or higher (eg, 1 or 2) and apply 1-shot HARQ-ACK feedback. .. This allows one-shot HARQ-ACK feedback to be applied by selecting a particular priority HARQ-ACK.
  • the UE may control to select and feed back the HARQ-ACK of a specific priority.
  • HARQ-ACK For example, as HARQ-ACK to be the target of 1-shot HARQ-ACK feedback, a first HARQ-ACK having a first priority (high) and a second HARQ-ACK having a second priority (low) are used. It is assumed that it is included. In such a case, the UE should send the HARQ-ACKs having either priority (first priority or second priority) together (for example, included in the same HARQ-ACK codebook). You may control it. In this case, the one-shot HARQ-ACK feedback may not be applied to the HARQ-ACK having another priority.
  • 1-shot HARQ-ACK feedback may be applied to HARQ-ACK having the first priority (high).
  • the UE may select one or more HARQ-ACKs having a first priority (high) to provide one-shot HARQ-ACK feedback.
  • the priority of each HARQ-ACK subject to the one-shot HARQ-ACK feedback may be determined based on the DCI format that schedules the PDSCH corresponding to each HARQ-ACK.
  • the first priority may be set for the HARQ-ACK codebook to be fed back.
  • 1-shot HARQ-ACK feedback may be applied to HARQ-ACK having a second priority (low).
  • the UE may select one or more HARQ-ACKs having a second priority (low) to provide one-shot HARQ-ACK feedback.
  • the HARQ-ACK codebook to be fed back may be set to the second priority.
  • the priority of HARQ-ACK to which the one-shot HARQ-ACK feedback is applied may be notified / set to the UE by using the upper layer signaling / DCI.
  • the DCI format for instructing the one-shot HARQ-ACK feedback may utilize at least one of the first DCI format and the second DCI format.
  • the UE may determine the HARQ-ACK to which the 1-shot HARQ-ACK feedback is applied based on the DCI format instructing the 1-shot HARQ-ACK request. If a first priority (high) is indicated by a DCI format (eg, DCI format 1_2) instructing a one-shot HARQ-ACK request, the UE has one or more HARQs with the first priority (high). -ACK may be selected to provide 1-shot HARQ-ACK feedback. Further, the HARQ-ACK codebook used for the one-shot HARQ-ACK may have a first priority set.
  • a DCI format eg, DCI format 1_2
  • HARQ-ACK may be selected to provide one-shot HARQ-ACK feedback. Further, the HARQ-ACK codebook used for the one-shot HARQ-ACK may have a second priority set.
  • the 1-shot HARQ-ACK feedback can be flexibly controlled based on the priority.
  • the priority of the 1-shot HARQ-ACK feedback may be determined by using either the option 1-1 or the option 1-2 described above. In this case, the UE may be notified / set by higher layer signaling as to whether option 1-1 or option 1-2 is to be used.
  • a predetermined upper layer parameter for example, PriorityIndicator-ForDCIFormatX_Y
  • a priority specification field exists in the DCI format X_Y
  • the above option 1-1 is used to provide 1-shot HARQ-ACK feedback. You may decide the priority. In other cases (for example, when a predetermined upper layer parameter is not set), the above option 1-2 may be used to determine the priority of the 1-shot HARQ-ACK feedback.
  • option 1-1 or option 1-2 may be applied to the HARQ-ACK fed back by the one-shot HARQ-ACK feedback.
  • option 1-1 and option 1-2 may be applied in combination as appropriate.
  • the priority of the one-shot HARQ-ACK feedback itself is determined based on the format of the DCI that directs the one-shot HARQ-ACK feedback.
  • the priority of each HARQ-ACK may be determined based on the priority specification field included in the DCI that schedules the PDSCH corresponding to each HARQ-ACK.
  • the priority of the 1-shot HARQ-ACK feedback itself is determined based on the priority specification field included in the DCI that indicates the 1-shot HARQ-ACK feedback.
  • the priority of each HARQ-ACK may be determined based on the format of the DCI that schedules the PDSCH corresponding to each HARQ-ACK.
  • the UE may determine the HARQ-ACK to be fed back based on the number of requested PDSCH group (s) field included in the DCI. For example, if the UE has a value of "0" in the Number of requested PDSCH group (s) field, the UE has one or more HARQ feedbacks for the PDSCH groups scheduled by its DCI. This may be done in resources (see Figure 7).
  • FIG. 7 corresponds to a PDSCH group (here, PDSCH group # 1) corresponding to PDSCH # 3 scheduled by DCI # 3, based on the number of requested PDSCH groups included in DCI # 3 that schedules PDSCH # 3. Shows a case where one or more HARQ-ACKs (here, HARQ-ACK # 2 and # 3) are fed back by using a predetermined UL resource.
  • a PDSCH group here, PDSCH group # 1
  • Shows a case where one or more HARQ-ACKs here, HARQ-ACK # 2 and # 3 are fed back by using a predetermined UL resource.
  • the UE when the value of the request PDSCH group number field in the DCI is "1", the UE has a PDSCH group scheduled by the DCI and a PDSCH group different from the PDSCH group scheduled by the DCI.
  • One or more HARQ feedbacks to a resource may be given at a resource (see Figure 8).
  • FIG. 8 shows a PDSCH group (here, PDSCH group # 1) corresponding to PDSCH # 3 scheduled by DCI # 3, based on the number of requested PDSCH groups included in DCI # 3 that schedules PDSCH # 3.
  • One or more HARQ-ACKs (here, HARQ-ACK # 1, # 2, # 3) corresponding to different PDSCH groups (here, PDSCH group # 0) are fed back using predetermined UL resources. Shows the case.
  • the PDSCH group index may notify the UE using the DCI that schedules the PDSCH. Further, the PDSCH group index may be a predetermined number (for example, two). When there are two PDSCH group indexes set (for example, indexes 0 and 1) and the value of the requested PDSCH group number field in the DCI is "1", the UE has PDSCH group indexes 0 and 1. HARQ feedback for the set PDSCH may be performed at a certain resource.
  • the request PDSCH group number field included in the DCI feeds back one or more HARQ-ACKs to the PDSCH group scheduled by the DCI (Case 1), and the PDSCH group scheduled by the DCI.
  • HARQ-ACKs A case where one or more HARQ-ACKs are fed back to a PDSCH group different from the PDSCH group (Case 2) will be described as an example.
  • HARQ-ACK (or PDSCH) having different priorities may correspond to the same group (option 2-1).
  • a plurality of priorities eg, two priorities
  • Option 2-2 may be used. In this case, only the same priorities (eg, one priority) are classified / matched within the same PDSCH group. For example, in FIG. 7, PDSCH # 2 (or HARQ-ACK # 2) and PDSCH # 3 (or HARQ-ACK # 3) are set to have the same priority.
  • the UE may provide HARQ-ACK feedback using a plurality of HARQ-ACK codebooks corresponding to each priority. For example, the UE is specified by the number of requested PDSCH groups using the first HARQ-ACK codebook corresponding to the first priority and the second HARQ-ACK codebook corresponding to the second priority.
  • the HARQ-ACK corresponding to the PDSCH group (for example, PDSCH group # 1 in FIG. 7) may be fed back.
  • the priority of each HARQ-ACK codebook may be determined based on the priority of HARQ-ACK included in each HARQ-ACK codebook. For example, the first HARQ-ACK codebook may be set to a first priority (high) and the second HARQ-ACK codebook may be set to a second priority (low). Alternatively, a common priority may be set for the first HARQ-ACK codebook and the second HARQ-ACK codebook.
  • the UE may control to feed back a plurality of HARQ-ACKs having different priorities by using a common HARQ-ACK codebook.
  • the priority of the HARQ-ACK codebook containing a plurality of HARQ-ACKs having different priorities is the priority specification field included in the DCI (for example, the DCI including the request PDSCH group number field), or the format of the DCI. It may be determined based on.
  • each HARQ-ACK (or HARQ-ACK corresponding to each PDSCH) contained in the same PDSCH group is determined based on the priority specification field included in the DCI corresponding to each PDSCH or the DCI format. You may. PDSCHs are accumulated in the same PDSCH group regardless of the priority of the PDSCH.
  • the UE When the UE detects a DCI containing a requested PDSCH group number field (for example, “0”), the UE controls to give feedback on HARQ-ACK corresponding to the PDSCH group scheduled in the DCI regardless of priority. do.
  • a DCI containing a requested PDSCH group number field for example, “0”
  • the priority and PDSCH group can be flexibly set. Further, when performing HARQ-ACK feedback using the PDSCH group unit, it is possible to feed back HARQ-ACK regardless of the priority by feeding back HARQ-ACK of a plurality of priorities.
  • the UE may control to select and feed back HARQ-ACK of a specific priority based on the request PDSCH group number field included in the DCI (option 2-1-2). That is, HARQ-ACK of a predetermined priority may be selectively fed back while supporting the association of a plurality of priorities with respect to the predetermined group.
  • the priority of HARQ-ACK to give feedback may be defined in advance in the specification (for example, high is feedback), or may be determined based on DCI / upper layer signaling. For example, when the first priority and the second priority correspond to the same PDSCH group, either the HARQ-ACK corresponding to the first priority or the HARQ-ACK corresponding to the second priority is fed back. It may be determined based on DCI / upper layer signaling.
  • each HARQ-ACK (or HARQ-ACK corresponding to each PDSCH) included in the PDSCH group is determined based on the priority specification field included in the DCI corresponding to each PDSCH or the DCI format. good. PDSCHs are accumulated in the same PDSCH group regardless of the priority of the PDSCH.
  • the UE If the UE detects a DCI containing a requested PDSCH group number field (eg, “0”), the UE will have a particular priority HARQ-ACK of the HARQ-ACKs corresponding to the PDSCH groups scheduled in the DCI. It may be controlled to feed back only.
  • a DCI containing a requested PDSCH group number field eg, “0”
  • the specific priority may be determined based on the priority specification field included in the DCI including the request PDSCH group number field (eg, "0"), or the format of the DCI.
  • the particular priority is a priority specification field contained in at least one of the DCIs used for scheduling PDSCHs belonging to the PDSCH group (eg, the last transmitted DCI), or the format of the DCI. It may be determined based on.
  • the specific priority may be set as the priority of the HARQ-ACK codebook used for the feedback.
  • the HARQ-ACK feedback of a specific priority is selected and fed back to control the HARQ-ACK feedback according to the priority. It becomes possible.
  • the HARQ-ACK corresponding to each PDSCH group may be controlled to be fed back based on the DCI including.
  • one PDSCH group may correspond to the first priority, and the other PDSCH group may correspond to the second priority.
  • the same priority may correspond to a plurality of PDSCH groups.
  • Information about the PDSCH group and the corresponding priority may be notified / set to the UE using higher layer signaling / DCI.
  • the priority of the PDSCH scheduled by DCI becomes the second priority (low), it may correspond to a specific PDSCH group (for example, index “0”).
  • the priority specification field included in the DCI (for example, the DCI including the DCI / request PDSCH group number field for scheduling PDSCH) is set to "0" (or the DCI format is 1-1-1) and is included in the DCI.
  • the PDSCH group index field may be set to "0".
  • the priority of the PDSCH scheduled by DCI is the first priority (high), it may correspond to a specific PDSCH group (for example, index “1”).
  • the priority specification field included in the DCI (for example, the DCI including the DCI / request PDSCH group number field for scheduling PDSCH) is set to "1" (or the DCI format is 1_2) and is included in the DCI.
  • the PDSCH group index field may be set to "1".
  • the UE When the UE detects a DCI containing a requested PDSCH group number field (eg, “0”), the UE controls to feed back one or more HARQ-ACKs corresponding to PDSCH group # 1 scheduled in the DCI. do.
  • a DCI containing the request PDSCH group number field eg DCI # 3 specifies a second priority (low) and another DCI transmitted prior to the DCI # 3 (eg DCI # 2).
  • the UE uses the same HARQ-ACK codebook for HARQ-ACK corresponding to PDSCH # 2 scheduled in DCI # 2 and HARQ-ACK # 3 corresponding to PDSCH # 3 scheduled in DCI # 3. You may include it in and give feedback. In addition, a second priority may be set in the HARQ-ACK codebook.
  • the UE may feed back one or more HARQ-ACKs corresponding to the PDSCH group # 1 scheduled in the DCI.
  • a DCI containing the request PDSCH group number field eg DCI # 3 specifies a first priority (high) and another DCI transmitted prior to the DCI # 3 (eg DCI # 2).
  • the UE performs the same HARQ-ACK # 2 corresponding to PDSCH # 2 scheduled by DCI # 2 and HARQ-ACK # 3 corresponding to PDSCH # 3 scheduled by DCI # 3. You may include it in the codebook and give feedback. Further, the first priority may be set in the HARQ-ACK codebook.
  • the UE is assigned to a predetermined PDSCH group based on a priority value (eg, i) determined from a DCI (eg, a DCI indicating the number of requested PDSCH groups, or a DCI scheduling PDSCHs contained in a predetermined PDSCH group).
  • the HARQ-ACK to be fed back may be determined. For example, a HARQ-ACK having a priority value (eg, i) or higher obtained from the DCI may be selected and included in the HARQ-ACK feedback for a predetermined PDSCH group.
  • the UE detects a DCI containing a requested PDSCH group number field (eg, “0”), the UE has a HARQ-ACK (or a priority equal to or higher than the priority of PDSCH group # 1 scheduled in the DCI).
  • the PDSCH group's HARQ-ACK is controlled to be fed back.
  • a DCI (DCI # 3) containing the request PDSCH group number field specifies a second priority (low), which is higher than the second priority by DCI # 2 transmitted prior to DCI # 3. It is assumed that PDSCH # 2 (and the first priority) having a priority is specified.
  • the UE may include HARQ-ACK # 2 corresponding to PDSCH # 2 and HARQ-ACK # 3 corresponding to PDSCH # 3 in the same HARQ-ACK codebook for feedback. Further, a first priority or a second priority may be set in the HARQ-ACK codebook.
  • the priority instruction field "0" and the PDSCH group index "0" correspond to each other and the priority instruction field "1" and the PDSCH group index "1" correspond to each other is shown, but the present invention is limited to this. No.
  • the priority instruction field "0" may correspond to the PDSCH group index "1”
  • the priority instruction field "1" may correspond to the PDSCH group index "0".
  • the DCI format 1_1 may correspond to the PDSCH group index “0”, and the DCI format 1_2 may correspond to the PDSCH group index “1”.
  • the DCI format 1_1 may correspond to the PDSCH group index “1”, and the DCI format 1_2 may correspond to the PDSCH group index “0”.
  • the association between the DCI format and the PDSCH group index may be notified / set to the UE by using higher layer signaling or the like.
  • the PDSCH group index field (for example, PDSCH group index field) may not exist or may not be set to "0".
  • the PDSCH group may be configured to have restrictions on the priority to be set, or may be configured not to be restricted.
  • the restriction for example, one of the two PDSCH groups may correspond to the first priority (high) and the other may correspond to the second priority (low). ..
  • an unrestricted configuration for example, a configuration in which the same priority (for example, high) corresponds to both of two PDSCH groups may be used.
  • Case 2 corresponds to the case where one or more HARQ-ACKs are fed back to the PDSCH group scheduled by the DCI and the PDSCH group different from the PDSCH group by the request PDSCH group number field included in the DCI. (See, for example, FIG. 8).
  • HARQ-ACK (or PDSCH) having different priorities may correspond to the same group (option 2-1).
  • a plurality of priorities eg, two priorities
  • PDSCH # 2 (or HARQ-ACK # 2) and PDSCH # 3 (or HARQ-ACK # 3) included in group # 1 may have different priorities.
  • (Option 2-2) may be used.
  • only the same priorities eg, one priority
  • PDSCH # 2 (or HARQ-ACK # 2) and PDSCH # 3 (or HARQ-ACK # 3) are set to have the same priority.
  • the UE may provide HARQ-ACK feedback using a plurality of HARQ-ACK codebooks corresponding to each priority / each PDSCH group. For example, the UE is specified by the number of requested PDSCH groups using the first HARQ-ACK codebook corresponding to the first priority and the second HARQ-ACK codebook corresponding to the second priority.
  • the HARQ-ACK corresponding to the PDSCH group (for example, PDSCH groups # 0 and # 1 in FIG. 8) may be fed back.
  • the priority of each HARQ-ACK codebook may be determined based on the priority of HARQ-ACK included in each HARQ-ACK codebook. For example, the first HARQ-ACK codebook may be set to a first priority (high) and the second HARQ-ACK codebook may be set to a second priority (low). Alternatively, a common priority may be set for the first HARQ-ACK codebook and the second HARQ-ACK codebook.
  • the UE uses a first HARQ-ACK codebook corresponding to the first PDSCH group and a second HARQ-ACK codebook corresponding to the second PDSCH group to correspond to each PDSCH group.
  • HARQ-ACK may be fed back.
  • the first HARQ-ACK codebook may contain a plurality of HARQ-ACKs having different priorities.
  • the second HARQ-ACK codebook may contain a plurality of HARQ-ACKs having different priorities.
  • the priority of a HARQ-ACK codebook containing multiple HARQ-ACKs with different priorities is based on the priority specification field contained in the DCI (eg, the DCI containing the requested PDSCH group number field) or the format of the DCI. It may be decided. Alternatively, it may be determined based on the priority corresponding to each PDSCH group.
  • each HARQ-ACK (or HARQ-ACK corresponding to each PDSCH) included in the PDSCH group is determined based on the priority specification field included in the DCI corresponding to each PDSCH or the DCI format. good.
  • Each PDSCH is accumulated in the corresponding PDSCH group regardless of the priority of the PDSCH.
  • the UE If the UE detects a DCI containing a requested PDSCH group number field (eg, value "1"), the UE will include HARQ-ACK # 2, # 3, corresponding to PDSCH group # 1 scheduled in the DCI, and the said. It is controlled so that the HARQ-ACK # 1 corresponding to the PDSCH group # 0 different from the PDSCH group # 1 is fed back regardless of the priority.
  • a DCI containing a requested PDSCH group number field eg, value "1”
  • the priority and PDSCH group can be flexibly set. Further, when performing HARQ-ACK feedback using the PDSCH group unit, it is possible to feed back HARQ-ACK regardless of the priority by feeding back HARQ-ACK of a plurality of priorities.
  • the UE may control to select and feed back HARQ-ACK of a specific priority based on the request PDSCH group number field included in the DCI (option 2-1-2).
  • the priority of HARQ-ACK to give feedback may be defined in advance in the specification (for example, high is feedback), or may be determined based on DCI / upper layer signaling. For example, when the first priority and the second priority correspond to the same PDSCH group, either the HARQ-ACK corresponding to the first priority or the HARQ-ACK corresponding to the second priority is fed back. It may be determined based on DCI / upper layer signaling.
  • each HARQ-ACK (or HARQ-ACK corresponding to each PDSCH) included in the PDSCH group is determined based on the priority specification field included in the DCI corresponding to each PDSCH or the DCI format. good.
  • the PDSCH is accumulated in the corresponding PDSCH group regardless of the priority of the PDSCH.
  • the UE If the UE detects a DCI containing a requested PDSCH group number field (eg, “1”), the UE will have a particular priority HARQ-ACK of the HARQ-ACK corresponding to the PDSCH group # 1 scheduled in the DCI. It is controlled to feed back only the HARQ-ACK of a specific priority among the ACK and the HARQ-ACK corresponding to another PDSCH group # 0.
  • a DCI containing a requested PDSCH group number field eg, “1”
  • the specific priority may be determined based on the priority specification field included in the DCI including the request PDSCH group number field (eg, "1"), or the format of the DCI.
  • the particular priority is a priority specification field contained in at least one of the DCIs used for scheduling PDSCHs belonging to the PDSCH group (eg, the last transmitted DCI), or the format of the DCI. It may be determined based on.
  • the specific priority may be determined based on the PDSCH group (eg, PDSCH group index).
  • Information regarding the correspondence between the priority and the PDSCH group may be notified / set to the UE by higher layer signaling.
  • the priority of the HARQ-ACK codebook used for the feedback may be set to a specific priority.
  • the HARQ-ACK feedback of a specific priority is selected and fed back to control the HARQ-ACK feedback according to the priority. It becomes possible.
  • the HARQ-ACK corresponding to each PDSCH group may be controlled to be fed back based on the DCI including.
  • one PDSCH group may correspond to the first priority, and the other PDSCH group may correspond to the second priority.
  • the same priority may correspond to a plurality of PDSCH groups.
  • Information about the PDSCH group and the corresponding priority may be notified / set to the UE using higher layer signaling / DCI.
  • the priority of the PDSCH scheduled by DCI becomes the second priority (low), it may correspond to a specific PDSCH group (for example, index “0”).
  • the priority specification field included in the DCI (for example, the DCI including the DCI / request PDSCH group number field for scheduling PDSCH) is set to "0" (or the DCI format is 1-1-1) and is included in the DCI.
  • the PDSCH group index field may be set to "0".
  • the priority of the PDSCH scheduled by DCI is the first priority (high), it may correspond to a specific PDSCH group (for example, index “1”).
  • the priority specification field included in the DCI (for example, the DCI including the DCI / request PDSCH group number field for scheduling PDSCH) is set to "1" (or the DCI format is 1_2) and is included in the DCI.
  • the PDSCH group index field may be set to "1".
  • the UE detects a DCI # 3 containing a requested PDSCH group number field (eg, “1”), the UE has one or more HARQ-ACK # 2 corresponding to the PDSCH group # 1 scheduled in the DCI # 3. , # 3 and HARQ-ACK # 1 corresponding to another PDSCH group # 0 are controlled to be fed back.
  • a second priority (low) is specified by DCI # 3 including the request PDSCH group number field, and another PDSCH group # 0 (and a second) by DCI # 1 transmitted prior to DCI # 3.
  • Priority or first priority is specified.
  • the UE has HARQ-ACK # 2 and # 3 for PDSCH group # 1 including PDSCH # 3 scheduled in DCI # 3, and PDSCH # 1 (PDSCH group # 0) scheduled in DCI # 1.
  • HARQ-ACK # 1 may be included in the same or different HARQ-ACK codebooks for feedback. When transmitting with a different HARQ-ACK codebook, even if the priority corresponding to each PDSCH group or the priority specified by the DCI that schedules the PDSCH of each PDSCH group is set to the corresponding HARQ-ACK codebook. good.
  • the first priority (high) is specified by DCI # 3 including the request PDSCH group number field, and another PDSCH group # 0 (and the first PDSCH group # 0) is specified by DCI # 1 transmitted before the DCI # 3. It is assumed that a priority or a second priority) is specified.
  • the UE has HARQ-ACK # 2 and # 3 for PDSCH group # 1 including PDSCH # 3 scheduled in DCI # 3, and PDSCH # 1 (PDSCH group # 0) scheduled in DCI # 1.
  • HARQ-ACK # 1 may be included in the same or different HARQ-ACK codebooks for feedback. When transmitting with a different HARQ-ACK codebook, even if the priority corresponding to each PDSCH group or the priority specified by the DCI that schedules the PDSCH of each PDSCH group is set to the corresponding HARQ-ACK codebook. good.
  • the UE is assigned to a predetermined PDSCH group based on a priority value (eg, i) determined from a DCI (eg, a DCI indicating the number of requested PDSCH groups, or a DCI scheduling PDSCHs contained in a predetermined PDSCH group).
  • the HARQ-ACK to be fed back may be determined. For example, a HARQ-ACK having a priority value (eg, i) or higher obtained from the DCI may be selected and included in the HARQ-ACK feedback for a predetermined PDSCH group.
  • the UE detects a DCI # 3 containing a requested PDSCH group number field (eg, “1”), the UE has a HARQ-that has a priority equal to or higher than the priority of the PDSCH group # 1 scheduled in the DCI # 3. Control to feed back ACK and HARQ-ACK corresponding to another PDSCH group # 0.
  • the HARQ-ACK corresponding to the other PDSCH group # 0 may be a HARQ-ACK having a priority equal to or higher than the priority of the PDSCH group # 1.
  • DCI # 3 including the request PDSCH group number field specifies a second priority (low), and DCI # 1 transmitted prior to DCI # 3 gives a higher priority than the second priority. It is assumed that the PDSCH group # 0 (and the first priority) to have is specified. In such a case, the UE has the same or different HARQ-ACK # 3 (and # 2) corresponding to the PDSCH group # 1 scheduled in DCI # 3 and HARQ-ACK # 1 scheduled in DCI # 1. You may include it in the ACK codebook and give feedback. Further, a first priority or a second priority may be set in the HARQ-ACK codebook.
  • the priority instruction field "0" and the PDSCH group index "0" correspond to each other and the priority instruction field "1" and the PDSCH group index "1" correspond to each other is shown, but the present invention is limited to this. No.
  • the priority instruction field "0" may correspond to the PDSCH group index "1”
  • the priority instruction field "1" may correspond to the PDSCH group index "0".
  • the DCI format 1_1 may correspond to the PDSCH group index “0”, and the DCI format 1_2 may correspond to the PDSCH group index “1”.
  • the DCI format 1_1 may correspond to the PDSCH group index “1”, and the DCI format 1_2 may correspond to the PDSCH group index “0”.
  • the association between the DCI format and the PDSCH group index may be notified / set to the UE by using higher layer signaling or the like.
  • the PDSCH group index field (for example, PDSCH group index field) may not exist or may not be set to "0".
  • the PDSCH group may be configured to have restrictions on the priority to be set, or may be configured not to be restricted.
  • the restriction for example, one of the two PDSCH groups may correspond to the first priority (high) and the other may correspond to the second priority (low). ..
  • an unrestricted configuration for example, a configuration in which the same priority (for example, high) corresponds to both of two PDSCH groups may be used.
  • 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. 9 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment.
  • the wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by Third Generation Partnership Project (3GPP). ..
  • the wireless communication system 1 may support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between a plurality of Radio Access Technologies (RATs).
  • MR-DC is a dual connectivity (E-UTRA-NR Dual Connectivity (EN-DC)) between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR, and a dual connectivity (NR-E) between NR and LTE.
  • E-UTRA-NR Dual Connectivity Evolved Universal Terrestrial Radio Access (E-UTRA)
  • NR-E dual connectivity
  • NE-DC -UTRA Dual Connectivity
  • the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)).
  • the base station (gNB) of NR is MN
  • the base station (eNB) of LTE (E-UTRA) is SN.
  • the wireless communication system 1 has dual connectivity between a plurality of base stations in the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) in which both MN and SN are NR base stations (gNB). )) May be supported.
  • a plurality of base stations in the same RAT for example, dual connectivity (NR-NR Dual Connectivity (NN-DC)) in which both MN and SN are NR base stations (gNB). )
  • NR-NR Dual Connectivity NR-DC
  • gNB NR base stations
  • the wireless communication system 1 includes a base station 11 that forms a macrocell C1 having a relatively wide coverage, and a base station 12 (12a-12c) that is arranged in the macrocell C1 and forms a small cell C2 that is narrower than the macrocell C1. You may prepare.
  • the user terminal 20 may be located in at least one cell. The arrangement, number, and the like of each cell and the user terminal 20 are not limited to the mode shown in the figure.
  • the base stations 11 and 12 are not distinguished, they are collectively referred to as the base station 10.
  • the user terminal 20 may be connected to at least one of a plurality of base stations 10.
  • the user terminal 20 may use at least one of carrier aggregation (Carrier Aggregation (CA)) and dual connectivity (DC) using a plurality of component carriers (Component Carrier (CC)).
  • CA Carrier Aggregation
  • DC dual connectivity
  • CC Component Carrier
  • Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)).
  • the macrocell C1 may be included in FR1 and the small cell C2 may be included in FR2.
  • FR1 may be in a frequency band of 6 GHz or less (sub 6 GHz (sub-6 GHz)), and FR 2 may be in a frequency band higher than 24 GHz (above-24 GHz).
  • the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.
  • the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • the plurality of base stations 10 may be connected by wire (for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.) or wirelessly (for example, NR communication).
  • wire for example, optical fiber compliant with Common Public Radio Interface (CPRI), X2 interface, etc.
  • NR communication for example, when NR communication is used as a backhaul between base stations 11 and 12, the base station 11 corresponding to the higher-level station is an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to a relay station (relay) is IAB. It may be called a node.
  • IAB Integrated Access Backhaul
  • relay station relay station
  • the base station 10 may be connected to the core network 30 via another base station 10 or directly.
  • the core network 30 may include at least one such as Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
  • EPC Evolved Packet Core
  • 5GCN 5G Core Network
  • NGC Next Generation Core
  • the user terminal 20 may be a terminal 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.
  • a downlink shared channel Physical Downlink Shared Channel (PDSCH)
  • a broadcast channel Physical Broadcast Channel (PBCH)
  • a downlink control channel Physical Downlink Control
  • PDSCH Physical Downlink Control
  • the uplink shared channel Physical Uplink Shared Channel (PUSCH)
  • the uplink control channel Physical Uplink Control Channel (PUCCH)
  • the random access channel shared by each user terminal 20 are used.
  • Physical Random Access Channel (PRACH) Physical Random Access Channel or the like may be used.
  • User data, upper layer control information, System Information Block (SIB), etc. are transmitted by PDSCH.
  • User data, upper layer control information, and the like may be transmitted by the PUSCH.
  • the Master Information Block (MIB) may be transmitted by the PBCH.
  • Lower layer control information may be transmitted by PDCCH.
  • the lower layer control information may include, for example, downlink control information (Downlink Control Information (DCI)) including scheduling information of at least one of PDSCH and PUSCH.
  • DCI Downlink Control Information
  • the DCI that schedules PDSCH may be called DL assignment, DL DCI, or the like, and the DCI that schedules PUSCH may be called UL grant, UL DCI, or the like.
  • the PDSCH may be read as DL data, and the PUSCH may be read as UL data.
  • a control resource set (COntrol REsource SET (CORESET)) and a search space (search space) may be used for PDCCH detection.
  • CORESET corresponds to a resource for searching DCI.
  • the search space corresponds to the search area and search method of PDCCH candidates (PDCCH candidates).
  • One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a search space based on the search space settings.
  • One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels.
  • One or more search spaces may be referred to as a search space set.
  • the "search space”, “search space set”, “search space setting”, “search space set setting”, “CORESET”, “CORESET setting”, etc. of the present disclosure may be read as each other.
  • channel state information (Channel State Information (CSI)
  • delivery confirmation information for example, it may be called Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.
  • scheduling request 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" to the beginning of various channels.
  • a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), and the like may be transmitted.
  • the DL-RS includes a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), and a reference signal for demodulation (DeModulation).
  • CRS Cell-specific Reference Signal
  • CSI-RS Channel State Information Reference Signal
  • DMRS positioning reference signal
  • PRS Positioning Reference Signal
  • PTRS phase tracking reference signal
  • the synchronization signal may be, for example, at least one of a primary synchronization signal (Primary Synchronization Signal (PSS)) and a secondary synchronization signal (Secondary Synchronization Signal (SSS)).
  • PSS Primary Synchronization Signal
  • SSS Secondary Synchronization Signal
  • the signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be referred to as SS / PBCH block, SS Block (SSB) and the like.
  • SS, SSB and the like may also be called a reference signal.
  • a measurement reference signal Sounding Reference Signal (SRS)
  • a demodulation reference signal DMRS
  • UL-RS Uplink Reference Signal
  • UE-specific Reference Signal UE-specific Reference Signal
  • FIG. 10 is a diagram showing an example of the configuration of a base station according to an embodiment.
  • the base station 10 includes a control unit 110, a transmission / reception unit 120, a transmission / reception antenna 130, and a transmission line interface 140.
  • the control unit 110, the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140 may each be provided with one or more.
  • the functional block of the characteristic portion in the present embodiment is mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.
  • the control unit 110 controls the entire base station 10.
  • the control unit 110 can be composed of a controller, a control circuit, and the like described based on the common recognition in the technical field according to the present disclosure.
  • the control unit 110 may control signal generation, scheduling (for example, resource allocation, mapping) and the like.
  • the control unit 110 may control transmission / reception, measurement, and the like using the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission line interface 140.
  • the control unit 110 may generate data to be transmitted as a signal, control information, a sequence, and the like, and transfer the data to the transmission / reception unit 120.
  • the control unit 110 may perform call processing (setting, release, etc.) of the communication channel, status 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 the common recognition in the technical field according to the present disclosure. be able to.
  • the transmission / reception unit 120 may be configured as an integrated transmission / reception unit, or may be composed of a transmission unit and a reception unit.
  • the transmission unit may be composed of a transmission processing unit 1211 and an RF unit 122.
  • the receiving unit may be composed of a receiving processing unit 1212, an RF unit 122, and a measuring unit 123.
  • the transmitting / receiving antenna 130 can be composed of an antenna described based on the common recognition in the technical field according to the present disclosure, for example, an array antenna.
  • the transmission / reception unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like.
  • the transmission / reception unit 120 may receive the above-mentioned uplink channel, uplink reference signal, and the like.
  • the transmission / reception unit 120 may form at least one of a transmission beam and a reception beam by using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), and the like.
  • digital beamforming for example, precoding
  • analog beamforming for example, phase rotation
  • the transmission / reception unit 120 processes, for example, Packet Data Convergence Protocol (PDCP) layer processing and Radio Link Control (RLC) layer processing (for example, RLC) for data, control information, etc. acquired from control unit 110.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • HARQ retransmission control HARQ retransmission control
  • the transmission / reception unit 120 performs channel coding (may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (Discrete Fourier Transform (DFT)) for the bit string to be transmitted. Processing (if necessary), inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-analog transformation may be performed, and the baseband signal may be output.
  • channel coding may include error correction coding
  • modulation modulation
  • mapping mapping, filtering
  • DFT discrete Fourier Transform
  • IFFT inverse Fast Fourier Transform
  • precoding coding
  • transmission processing such as digital-analog transformation
  • the transmission / reception unit 120 may perform modulation, filtering, amplification, etc. on the baseband signal to the radio frequency band, and transmit the signal in the radio frequency band via the transmission / reception antenna 130. ..
  • the transmission / reception unit 120 may perform amplification, filtering, demodulation to a baseband signal, or the like on the signal in the radio frequency band received by the transmission / reception antenna 130.
  • the transmission / reception unit 120 (reception processing unit 1212) performs analog-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) for the acquired baseband signal. )) Processing (if necessary), filtering, decoding, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing are applied. User data and the like may be acquired.
  • FFT fast Fourier transform
  • IDFT inverse discrete Fourier transform
  • the transmission / reception unit 120 may perform measurement on the received signal.
  • the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, or the like based on the received signal.
  • the measuring unit 123 has received power (for example, Reference Signal Received Power (RSRP)) and reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)).
  • RSRP Reference Signal Received Power
  • RSSQ Reference Signal Received Quality
  • SINR Signal to Noise Ratio
  • Signal strength for example, Received Signal Strength Indicator (RSSI)
  • propagation path information for example, CSI
  • the measurement result may be output to the control unit 110.
  • the transmission line interface 140 transmits / receives signals (backhaul signaling) to / from a device included in the core network 30, another base station 10, etc., and user data (user plane data) for the user terminal 20 and a control plane. Data or the like may be acquired or transmitted.
  • the transmission unit and the reception unit of the base station 10 in the present disclosure may be composed of at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140.
  • the transmission / reception unit 120 may transmit downlink control information instructing 1-shot HARQ-ACK.
  • the transmission / reception unit 120 may transmit downlink control information including information indicating the group number of the downlink shared channel and information regarding the group of the downlink shared channel that performs HARQ-ACK feedback.
  • the control unit 110 may control the reception of the one-shot HARQ-ACK whose priority is determined based on the information regarding the priority of UL transmission notified by the downlink control information.
  • control unit 110 may control the reception of HARQ-ACK that is fed back based on at least one of the information regarding the priority of UL transmission notified by the downlink control information and the information regarding the group.
  • FIG. 11 is a diagram showing an example of the configuration of the user terminal according to the embodiment.
  • the user terminal 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230.
  • the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may each be provided with one or more.
  • the functional block of the feature portion in the present embodiment is mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.
  • the control unit 210 controls the entire user terminal 20.
  • the control unit 210 can be composed of a controller, a control circuit, and the like described based on the common recognition in the technical field according to the present disclosure.
  • the control unit 210 may control signal generation, mapping, and the like.
  • the control unit 210 may control transmission / reception, measurement, and the like using the transmission / reception unit 220 and the transmission / reception antenna 230.
  • the control unit 210 may generate data to be transmitted as a signal, control information, a sequence, and the like, and transfer the data to the transmission / reception unit 220.
  • the transmission / reception unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223.
  • the baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212.
  • the 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 the common recognition in the technical field according to the present disclosure, for example, an array antenna.
  • the transmission / reception unit 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, and the like.
  • the transmission / reception unit 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.
  • the transmission / reception unit 220 may form at least one of a transmission beam and a reception beam by using digital beamforming (for example, precoding), analog beamforming (for example, phase rotation), and the like.
  • digital beamforming for example, precoding
  • analog beamforming for example, phase rotation
  • the transmission / reception unit 220 processes, for example, PDCP layer processing, RLC layer processing (for example, RLC retransmission control), and MAC layer processing (for example, for data, control information, etc. acquired from the control unit 210). , HARQ retransmission control), etc., to generate a bit string to be transmitted.
  • the transmission / reception unit 220 (transmission processing unit 2211) performs channel coding (may include error correction coding), modulation, mapping, filtering processing, DFT processing (if necessary), and IFFT processing for the bit string to be transmitted. , Precoding, digital-to-analog conversion, and other transmission processing may be performed, and the baseband signal may be output.
  • Whether or not to apply the DFT process may be based on the transform precoding setting.
  • the transmission / reception unit 220 transmits the channel using the DFT-s-OFDM waveform.
  • the DFT process may be performed as the transmission process, and if not, the DFT process may not be performed as the transmission process.
  • the transmission / reception unit 220 may perform modulation, filtering, amplification, etc. on the baseband signal to the radio frequency band, and transmit the signal in the radio frequency band via the transmission / reception antenna 230. ..
  • the transmission / reception unit 220 may perform amplification, filtering, demodulation to a baseband signal, or the like on the signal in the radio frequency band received by the transmission / reception antenna 230.
  • the transmission / reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering processing, demapping, demodulation, and decoding (error correction) for the acquired baseband signal. Decoding may be included), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing may be applied to acquire user data and the like.
  • the transmission / reception unit 220 may perform measurement on the received signal.
  • the measuring unit 223 may perform RRM measurement, CSI measurement, or the like based on the received signal.
  • the measuring unit 223 may measure received power (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), propagation path information (for example, CSI), and the like.
  • the measurement result may be output to the control unit 210.
  • the transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmission / reception unit 220 and the transmission / reception antenna 230.
  • the transmission / reception unit 220 may receive downlink control information instructing 1-shot HARQ-ACK.
  • the transmission / reception unit 220 may receive downlink control information including information indicating the group number of the downlink shared channel and information regarding the group of the downlink shared channel that provides feedback of HARQ-ACK.
  • the control unit 210 may determine the priority of the one-shot HARQ-ACK based on the information regarding the priority of UL transmission that can be acquired from the downlink control information. For example, the control unit 210 may control one or more HARQ-ACKs specified by the one-shot HARQ-ACK so as to feed back regardless of the priority of each HARQ-ACK. The control unit 210 may determine the HARQ-ACK to be fed back based on the priority of each HARQ-ACK for one or more HARQ-ACKs specified by the one-shot HARQ-ACK. The control unit 210 may determine the priority of the one-shot HARQ-ACK based on at least one of the information that specifies the priority of UL transmission included in the downlink control information and the format of the downlink control information.
  • the control unit 210 may control the feedback of HARQ-ACK based on at least one of the information regarding the priority of UL transmission that can be acquired from the downlink control information and the information regarding the group. At least one configuration of downlink shared channels with different priorities and HARQ-ACK with different priorities may be supported for the same group. At least one of a downlink shared channel having the same priority and HARQ-ACK having the same priority may be set for the same group. The control unit 210 may control to feed back HARQ-ACK having the same priority to the same group.
  • each functional block is realized using one physically or logically coupled device, or two or more physically or logically separated devices can be directly or indirectly (eg, for example). , Wired, wireless, etc.) and may be realized using these plurality of devices.
  • the functional block may be realized by combining the software with the one device or the plurality of devices.
  • the functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and deemed. , Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc.
  • a functional block (configuration unit) for functioning transmission may be referred to as a transmitting unit (transmitting unit), a transmitter (transmitter), or the like.
  • the realization method is not particularly limited.
  • the base station, user terminal, and the like in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure.
  • FIG. 12 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment.
  • the base station 10 and the user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. ..
  • the hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.
  • processor 1001 may be a plurality of processors. Further, the processing may be executed by one processor, or the processing may be executed simultaneously, sequentially, or by using other methods by two or more processors.
  • the processor 1001 may be mounted by one or more chips.
  • the processor 1001 For each function in the base station 10 and the user terminal 20, for example, by loading predetermined software (program) on hardware such as the processor 1001 and the memory 1002, the processor 1001 performs an operation and communicates via the communication device 1004. It is realized by controlling at least one of reading and writing of data in the memory 1002 and the storage 1003.
  • predetermined software program
  • the processor 1001 operates, for example, an operating system to control the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, and the like.
  • CPU central processing unit
  • control unit 110 210
  • transmission / reception unit 120 220
  • the like may be realized by the processor 1001.
  • the processor 1001 reads a program (program code), a software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these.
  • a program program code
  • the control unit 110 may be realized by a control program stored in the memory 1002 and operating in the processor 1001, and may be realized in the same manner for other functional blocks.
  • the memory 1002 is a computer-readable recording medium, for example, at least a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), or any other suitable storage medium. It may be composed of one.
  • the memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like.
  • the memory 1002 can store a program (program code), a software module, or the like that can be executed to implement the wireless communication method according to the embodiment of the present disclosure.
  • the storage 1003 is a computer-readable recording medium, and is, for example, a flexible disk, a floppy disk (registered trademark) disk, an optical magnetic disk (for example, a compact disc (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, etc.). At least one of Blu-ray® discs), removable discs, optical disc drives, smart cards, flash memory devices (eg cards, sticks, key drives), magnetic stripes, databases, servers and other suitable storage media. May be configured by.
  • the storage 1003 may be referred to as an auxiliary storage device.
  • the communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like.
  • the communication device 1004 has, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (Frequency Division Duplex (FDD)) and time division duplex (Time Division Duplex (TDD)). May be configured to include.
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • the transmission / reception unit 120 (220), the transmission / reception antenna 130 (230), and the like described above may be realized by the communication device 1004.
  • the transmission / reception unit 120 (220) may be physically or logically separated by the transmission unit 120a (220a) and the reception unit 120b (220b).
  • the input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts an input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside.
  • the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
  • each device such as the processor 1001 and the memory 1002 is connected by the bus 1007 for communicating information.
  • the bus 1007 may be configured by using a single bus, or may be configured by using a different bus for each device.
  • the base station 10 and the user terminal 20 include a microprocessor, a digital signal processor (Digital Signal Processor (DSP)), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), and the like. It may be configured to include hardware, and a part or all of each functional block may be realized by using the hardware. For example, processor 1001 may be implemented using at least one of these hardware.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • PLD Programmable Logic Device
  • FPGA Field Programmable Gate Array
  • the terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings.
  • channels, symbols and signals may be read interchangeably.
  • the signal may be a message.
  • the reference signal may be abbreviated as RS, and may be referred to as a pilot, a pilot signal, or the like depending on the applied standard.
  • the component carrier CC may be referred to as a cell, a frequency carrier, a carrier frequency, or the like.
  • the wireless frame may be configured by one or more periods (frames) in the time domain.
  • Each of the one or more periods (frames) constituting the radio frame may be referred to as a subframe.
  • the subframe may be composed of one or more slots in the time domain.
  • the subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
  • the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel.
  • Numerology is, for example, subcarrier interval (SubCarrier Spacing (SCS)), bandwidth, symbol length, cyclic prefix length, transmission time interval (Transmission Time Interval (TTI)), number of symbols per TTI, wireless frame configuration.
  • SCS subcarrier Spacing
  • TTI Transmission Time Interval
  • a specific filtering process performed by the transmitter / receiver in the frequency domain, a specific windowing process performed by the transmitter / receiver in the time domain, and the like may be indicated.
  • the slot may be composed of one or more symbols in the time domain (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.). Further, the slot may be a time unit based on numerology.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the slot may include a plurality of mini slots. Each minislot may be composed of one or more symbols in the time domain. Further, the mini slot may be referred to as a sub slot. The 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 use different names corresponding to each.
  • the time units such as frames, subframes, slots, mini slots, and symbols in the present disclosure may be read as each other.
  • one subframe may be called TTI
  • a plurality of consecutive subframes may be called TTI
  • one slot or one minislot may be called TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms. May be.
  • the unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.
  • TTI refers to, for example, the minimum time unit of scheduling in wireless communication.
  • the base station schedules each user terminal to allocate radio resources (frequency bandwidth that can be used in each user terminal, transmission power, etc.) in TTI units.
  • the definition of TTI is not limited to this.
  • TTI may be a transmission time unit such as a channel-encoded data packet (transport block), a code block, or a code word, or may be a processing unit such as scheduling or link adaptation.
  • the time interval for example, the number of symbols
  • the transport block, code block, code word, etc. may be shorter than the TTI.
  • one or more TTIs may be the minimum time unit for scheduling. Further, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.
  • a TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in 3GPP Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like.
  • a TTI shorter than a normal TTI may be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.
  • the long TTI (eg, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms
  • the short TTI eg, shortened TTI, etc.
  • TTI having the above TTI length may be read as TTI having the above TTI length.
  • a resource block is a resource allocation unit in the time domain and the frequency domain, and may include one or a plurality of continuous subcarriers in the frequency domain.
  • the number of subcarriers contained in the RB may be the same regardless of the numerology, and may be, for example, 12.
  • the number of subcarriers contained in the RB may be determined based on numerology.
  • the RB may include one or more symbols in the time domain, and may have a length of 1 slot, 1 mini slot, 1 subframe or 1 TTI.
  • Each 1TTI, 1 subframe, etc. may be composed of one or a plurality of resource blocks.
  • one or more RBs are a physical resource block (Physical RB (PRB)), a sub-carrier group (Sub-Carrier Group (SCG)), a resource element group (Resource Element Group (REG)), a PRB pair, and an RB. It may be called a pair or the like.
  • PRB Physical RB
  • SCG sub-carrier Group
  • REG resource element group
  • PRB pair an RB. It may be called a pair or the like.
  • the resource block may be composed of one or a plurality of resource elements (Resource Element (RE)).
  • RE Resource Element
  • 1RE may be a radio resource area of 1 subcarrier and 1 symbol.
  • Bandwidth Part (which may also be called partial bandwidth) represents a subset of consecutive common resource blocks (RBs) for a neurology in a carrier. May be good.
  • the common RB may be specified by the index of the RB with respect to the common reference point of the carrier.
  • PRBs may be defined in a BWP and numbered within that BWP.
  • the BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL).
  • BWP UL BWP
  • BWP for DL DL BWP
  • One or more BWPs may be set in one carrier for the UE.
  • At least one of the configured BWPs may be active and the UE may not expect to send or receive a given signal / channel outside the active BWP.
  • “cell”, “carrier” and the like in this disclosure may be read as “BWP”.
  • the above-mentioned structures such as wireless frames, subframes, slots, mini-slots, and symbols are merely examples.
  • the number of subframes contained in a radio frame the number of slots per subframe or radioframe, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in the RB.
  • the number of subcarriers, the number of symbols in 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.
  • the radio resource 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 embodiment / embodiment described in the present disclosure, and may be performed by using another method.
  • the notification of information in the present disclosure includes physical layer signaling (for example, downlink control information (DCI)), uplink control information (Uplink Control Information (UCI))), and higher layer signaling (for example, Radio Resource Control). (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals or combinations thereof. May be carried out by.
  • DCI downlink control information
  • UCI Uplink Control Information
  • RRC Radio Resource Control
  • MIB Master Information Block
  • SIB System Information Block
  • MAC Medium Access Control
  • the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), and the like.
  • the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
  • MAC signaling may be notified using, for example, a MAC control element (MAC Control Element (CE)).
  • CE MAC Control Element
  • the notification of predetermined information is not limited to the explicit notification, but implicitly (for example, by not notifying the predetermined information or another information). May be done (by notification of).
  • the determination may be made by a value represented by 1 bit (0 or 1), or by a boolean value represented by true or false. , May be done by numerical comparison (eg, comparison with a given value).
  • Software whether called software, firmware, middleware, microcode, hardware description language, or other names, is an instruction, instruction set, code, code segment, program code, program, subprogram, software module.
  • Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, features, etc. should be broadly interpreted.
  • software, instructions, information, etc. may be transmitted and received via a transmission medium.
  • a transmission medium For example, a website where software uses at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.).
  • wired technology coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.
  • wireless technology infrared, microwave, etc.
  • the terms “system” and “network” used in this disclosure may be used interchangeably.
  • the “network” may mean a device (eg, a base station) included in the network.
  • precoding "precoding weight”
  • QCL Quality of Co-Co-Location
  • TCI state Transmission Configuration Indication state
  • space "Spatial relation”, “spatial domain filter”, “transmission power”, “phase rotation”, "antenna port”, “antenna port group”, “layer”, “number of layers”
  • Terms such as “rank”, “resource”, “resource set”, “resource group”, “beam”, “beam width”, “beam angle”, "antenna”, “antenna element", “panel” are compatible.
  • base station BS
  • wireless base station fixed station
  • NodeB NodeB
  • eNB eNodeB
  • gNB gNodeB
  • Access point "Transmission point (Transmission Point (TP))
  • Reception point Reception Point
  • TRP Transmission / Reception Point
  • Panel , "Cell”, “sector”, “cell group”, “carrier”, “component carrier” and the like
  • Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.
  • the base station can accommodate one or more (eg, 3) cells.
  • a base station accommodates multiple cells, the entire 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 Remote Radio Head
  • the term "cell” or “sector” refers to a portion or all of the coverage area of at least one of a base station and a base station subsystem that provides communication services in this coverage.
  • MS mobile station
  • UE user equipment
  • terminal terminal
  • Mobile stations include subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals. , Handset, user agent, mobile client, client or some other suitable term.
  • At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like.
  • At least one of the base station and the mobile station may be a device mounted on the mobile body, a mobile body itself, or the like.
  • the moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ) May be.
  • at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation.
  • at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
  • IoT Internet of Things
  • the base station in the present disclosure may be read by the user terminal.
  • 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.
  • the words such as "up” and “down” may be read as words corresponding to the communication between terminals (for example, "side”).
  • the upstream channel, the downstream channel, and the like may be read as a side channel.
  • the user terminal in the present disclosure may be read as a base station.
  • the base station 10 may have the functions of the user terminal 20 described above.
  • the operation performed by the base station may be performed by its upper node (upper node) in some cases.
  • various operations performed for communication with a terminal are a base station, one or more network nodes other than the base station (for example,).
  • Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. can be considered, but it is not limited to these), or it is clear that it can be performed by a combination thereof.
  • Each aspect / embodiment described in the present disclosure may be used alone, in combination, or may be switched and used according to the execution. Further, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in the present disclosure present elements of various steps using exemplary order, and are not limited to the particular order presented.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • SUPER 3G IMT-Advanced
  • 4G 4th generation mobile communication system
  • 5G 5th generation mobile communication system
  • 6G 6th generation mobile communication system
  • xG xG (xG (x is, for example, an integer or a fraction)
  • Future Radio Access FAA
  • RAT New -Radio Access Technology
  • NR New Radio
  • NX New radio access
  • FX Future generation radio access
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access
  • UMB Ultra Mobile Broadband
  • UMB Ultra Mobile Broadband
  • LTE 802.11 Wi-Fi®
  • LTE 802.16 WiMAX®
  • LTE 802.20 Ultra-WideBand (UWB), Bluetooth®, and other suitable radios.
  • UMB Ultra Mobile Broadband
  • references to elements using designations such as “first” and “second” as used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not mean that only two elements can be adopted or that the first element must somehow precede the second element.
  • determining used in this disclosure may include a wide variety of actions.
  • judgment (decision) means judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigation (investigating), search (looking up, search, inquiry) ( For example, searching in a table, database or another data structure), ascertaining, etc. may be considered to be "judgment”.
  • judgment (decision) includes receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access (for example). It may be regarded as “determining” such as accessing) (for example, accessing data in memory).
  • judgment (decision) is regarded as “judgment (decision)” of solving, selecting, selecting, establishing, comparing, and the like. May be good. That is, “judgment (decision)” may be regarded as “judgment (decision)” of some action.
  • the "maximum transmission power" described in the present disclosure may mean the maximum value of the transmission power, may mean the nominal UE maximum transmit power, or may mean the rated maximum transmission power (the). It may mean rated UE maximum transmit power).
  • connection are any direct or indirect connections or connections between two or more elements. Means, and can include the presence of one or more intermediate elements between two elements that are “connected” or “bonded” to each other.
  • the connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection” may be read as "access”.
  • the radio frequency domain microwaves. It can be considered to be “connected” or “coupled” to each other using frequency, electromagnetic energy having wavelengths in the region, light (both visible and invisible) regions, and the like.
  • the term "A and B are different” may mean “A and B are different from each other”.
  • the term may mean that "A and B are different from C”.
  • Terms such as “separate” and “combined” may be interpreted in the same way as “different”.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

A terminal according to one aspect of the present disclosure has: a reception unit that receives downlink control information for instructing a one-shot Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK); and a control unit that determines a priority of the one-shot HARQ-ACK, on the basis of information that is about a priority of UL transmission and that can be acquired from the downlink control information.

Description

端末、無線通信方法及び基地局Terminals, wireless communication methods and base stations
 本開示は、次世代移動通信システムにおける端末、無線通信方法及び基地局に関する。 This disclosure relates to terminals, wireless communication methods and base stations in next-generation mobile communication systems.
 Universal Mobile Telecommunications System(UMTS)ネットワークにおいて、更なる高速データレート、低遅延などを目的としてLong Term Evolution(LTE)が仕様化された(非特許文献1)。また、LTE(Third Generation Partnership Project(3GPP) Release(Rel.)8、9)の更なる大容量、高度化などを目的として、LTE-Advanced(3GPP Rel.10-14)が仕様化された。 Long Term Evolution (LTE) has been specified for the purpose of higher data rate, lower latency, etc. in the Universal Mobile Telecommunications System (UMTS) network (Non-Patent Document 1). In addition, 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).
 LTEの後継システム(例えば、5th generation mobile communication system(5G)、5G+(plus)、New Radio(NR)、3GPP Rel.15以降などともいう)も検討されている。 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、NRなど)では、例えば、高速及び大容量(例えば、enhanced Mobile Broad Band(eMBB))、超多数端末(例えば、massive Machine Type Communication(mMTC)、Internet of Things(IoT))、超高信頼及び低遅延(例えば、Ultra Reliable and Low Latency Communications(URLLC))など、通信要件(requirement)が異なる複数のサービス(ユースケース、通信タイプ、等ともいう)が混在すること想定される。 In future wireless communication systems (for example, 5G, NR, etc.), for example, high speed and large capacity (for example, enhanced Mobile Broad Band (eMBB)), ultra-many terminals (for example, massive Machine Type Communication (mMTC), Internet of Things). (IoT)), ultra-high reliability and low latency (for example, Ultra Reliable and Low Latency Communications (URLLC)), and multiple services (also referred to as use cases, communication types, etc.) with different communication requirements are mixed. It is assumed.
 例えば、Rel.16以降では、信号/チャネルに対して優先度が設定され、各信号/チャネルにそれぞれ設定された優先度に基づいて通信を制御することが検討されている。例えば、複数の信号/チャネルがオーバーラップした場合に、各信号/チャネルの優先度に基づいて送受信が制御されることが想定される。 For example, Rel. In 16 and later, priorities are set for signals / channels, and it is considered to control communication based on the priorities set for each signal / channel. For example, when a plurality of signals / channels overlap, it is assumed that transmission / reception is controlled based on the priority of each signal / channel.
 また、1以上のHARQ-ACK(又は、1以上の下り共有チャネルにそれぞれ対応するHARQ-ACK)をまとめてフィードバックすることが検討されている。あるいは、下り共有チャネルをグループに分類し、グループ単位で下り共有チャネルに対応するHARQ-ACKをフィードバックすることが検討されている。 Further, it is being considered to feed back one or more HARQ-ACKs (or HARQ-ACKs corresponding to one or more downlink shared channels respectively) collectively. Alternatively, it is being considered to classify the downlink shared channels into groups and feed back the HARQ-ACK corresponding to the downlink shared channels on a group-by-group basis.
 しかし、複数のUL送信(例えば、HARQ-ACK)をまとめてフィードバックする場合に、各UL送信の優先度を国旅してどのようにフィードバックを制御するかについて十分に検討されていない。 However, when multiple UL transmissions (for example, HARQ-ACK) are fed back together, how to control the feedback by traveling the country with the priority of each UL transmission has not been sufficiently examined.
 そこで、本開示は、優先度の設定がサポートされる1以上のUL送信を適切に制御することができる端末、無線通信方法及び基地局を提供することを目的の一つとする。 Therefore, one of the purposes of the present disclosure is to provide a terminal, a wireless communication method, and a base station capable of appropriately controlling one or more UL transmissions for which priority setting is supported.
 本開示の一態様に係る端末は、1ショットHARQ-ACK(Hybrid Automatic Repeat reQuest ACKnowledgement)を指示する下り制御情報を受信する受信部と、前記下り制御情報から取得できるUL送信の優先度に関する情報に基づいて、前記1ショットHARQ-ACKの優先度を判断する制御部と、を有することを特徴とする。 The terminal according to one aspect of the present disclosure includes a receiving unit that receives downlink control information instructing a one-shot HARQ-ACK (Hybrid Automatic Repeat reQuest ACK knowledgement), and information regarding the priority of UL transmission that can be acquired from the downlink control information. Based on this, it is characterized by having a control unit for determining the priority of the one-shot HARQ-ACK.
 本開示の一態様によれば、優先度の設定がサポートされる1以上のUL送信を適切に制御することができる。 According to one aspect of the present disclosure, one or more UL transmissions for which priority setting is supported can be appropriately controlled.
図1A及び図1Bは、優先度に基づくUL送信制御の一例を示す図である。1A and 1B are diagrams showing an example of UL transmission control based on priority. 図2A-図2Cは、優先度に基づくUL送信制御の他の例を示す図である。2A-2C are diagrams showing other examples of UL transmission control based on priority. 図3は、エンハンスドダイナミックHARQフィードバック方法の一例を示す図である。FIG. 3 is a diagram showing an example of an enhanced dynamic HARQ feedback method. 図4は、1ショットHARQフィードバック方法の一例を示す図である。FIG. 4 is a diagram showing an example of a one-shot HARQ feedback method. 図5は、所定スロットにおいて複数のHARQ-ACKコードブックが送信される場合の一例を示す図である。FIG. 5 is a diagram showing an example of a case where a plurality of HARQ-ACK codebooks are transmitted in a predetermined slot. 図6は、第1の態様に係るUL送信制御の一例を示す図である。FIG. 6 is a diagram showing an example of UL transmission control according to the first aspect. 図7は、第2の態様に係るUL送信制御の一例を示す図である。FIG. 7 is a diagram showing an example of UL transmission control according to the second aspect. 図8は、第2の態様に係るUL送信制御の他の例を示す図である。FIG. 8 is a diagram showing another example of UL transmission control according to the second aspect. 図9は、一実施形態に係る無線通信システムの概略構成の一例を示す図である。FIG. 9 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. 図10は、一実施形態に係る基地局の構成の一例を示す図である。FIG. 10 is a diagram showing an example of the configuration of a base station according to an embodiment. 図11は、一実施形態に係るユーザ端末の構成の一例を示す図である。FIG. 11 is a diagram showing an example of the configuration of the user terminal according to the embodiment. 図12は、一実施形態に係る基地局及びユーザ端末のハードウェア構成の一例を示す図である。FIG. 12 is a diagram showing an example of the hardware configuration of the base station and the user terminal according to the embodiment.
<トラフィックタイプ>
 将来の無線通信システム(例えば、NR)では、モバイルブロードバンドのさらなる高度化(例えば、enhanced Mobile Broadband(eMBB))、多数同時接続を実現するマシンタイプ通信(例えば、massive Machine Type Communications(mMTC)、Internet of Things(IoT))、高信頼かつ低遅延通信(例えば、Ultra-Reliable and Low-Latency Communications(URLLC))などのトラフィックタイプ(サービス、サービスタイプ、通信タイプ、ユースケース、等ともいう)が想定される。例えば、URLLCでは、eMBBより小さい遅延及びより高い信頼性が要求される。
<Traffic type>
In future wireless communication systems (eg, NR), further advancement of mobile broadband (eg enhanced Mobile Broadband (eMBB)), machine type communication that realizes multiple simultaneous connections (eg massive Machine Type Communications (mMTC), Internet) Assumed traffic types (also referred to as services, service types, communication types, use cases, etc.) such as of Things (IoT)), high-reliability and low-latency communication (eg, Ultra-Reliable and Low-Latency Communications (URLLC)). Will be done. For example, URLLC requires less delay and higher reliability than eMBB.
 トラフィックタイプは、物理レイヤにおいては、以下の少なくとも一つに基づいて識別されてもよい。
・異なる優先度(priority)を有する論理チャネル
・変調及び符号化方式(Modulation and Coding Scheme(MCS))テーブル(MCSインデックステーブル)
・チャネル品質指示(Channel Quality Indication(CQI))テーブル
・DCIフォーマット
・当該DCI(DCIフォーマット)に含まれる(付加される)巡回冗長検査(CRC:Cyclic Redundancy Check)ビットのスクランブル(マスク)に用いられる(無線ネットワーク一時識別子(RNTI:System Information-Radio Network Temporary Identifier))
・RRC(Radio Resource Control)パラメータ
・特定のRNTI(例えば、URLLC用のRNTI、MCS-C-RNTI等)
・サーチスペース
・DCI内の所定フィールド(例えば、新たに追加されるフィールド又は既存のフィールドの再利用)
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). (RNTI: System Information-Radio Network Temporary Identifier)
-RRC (Radio Resource Control) parameters-Specific RNTI (for example, RNTI for URLLC, MCS-C-RNTI, etc.)
-Search space-A predetermined field in DCI (for example, reuse of a newly added field or an existing field)
 具体的には、PDSCHに対するHARQ-ACKのトラフィックタイプは、以下の少なくとも一つに基づいて決定されてもよい。
・当該PDSCHの変調次数(modulation order)、ターゲット符号化率(target code rate)、トランスポートブロックサイズ(TBS:Transport Block size)の少なくとも一つの決定に用いられるMCSインデックステーブル(例えば、MCSインデックステーブル3を利用するか否か)
・当該PDSCHのスケジューリングに用いられるDCIのCRCスクランブルに用いられるRNTI(例えば、C-RNTI又はMCS-C-RNTIのどちらでCRCスクランブルされるか)
Specifically, the HARQ-ACK traffic type for PDSCH may be determined based on at least one of the following:
An MCS index table (eg, MCS index table 3) used to determine at least one of the PDSCH modulation order, target code rate, and transport block size (TBS). Whether or not to use)
RNTI used for CRC scrambling of DCI used for scheduling the PDSCH (for example, whether CRC scrambled by C-RNTI or MCS-C-RNTI).
 また、SRのトラフィックタイプは、SRの識別子(SR-ID)として用いられる上位レイヤパラメータに基づいて決定されてもよい。当該上位レイヤパラメータは、当該SRのトラフィックタイプがeMBB又はURLLCのいずれであるかを示してもよい。 Further, the SR traffic type may be determined based on the upper layer parameter used as the SR identifier (SR-ID). The upper layer parameter may indicate whether the SR traffic type is eMBB or URLLC.
 また、CSIのトラフィックタイプは、CSI報告に関する設定(configuration)情報(CSIreportSetting)、トリガに利用されるDCIタイプ又はDCI送信パラメータ等に基づいて決定されてもよい。当該設定情報、DCIタイプ等は、当該CSIのトラフィックタイプがeMBB又はURLLCのいずれであるかを示してもよい。また、当該設定情報は、上位レイヤパラメータであってもよい。 Further, the CSI traffic type may be determined based on the configuration information (CSIreportSetting) related to the CSI report, the DCI type used for the trigger, the DCI transmission parameter, and the like. The setting information, DCI type, etc. may indicate whether the traffic type of the CSI is eMBB or URLLC. Further, the setting information may be an upper layer parameter.
 また、PUSCHのトラフィックタイプは、以下の少なくとも一つに基づいて決定されてもよい。
・当該PUSCHの変調次数、ターゲット符号化率、TBSの少なくとも一つの決定に用いられるMCSインデックステーブル(例えば、MCSインデックステーブル3を利用するか否か)
・当該PUSCHのスケジューリングに用いられるDCIのCRCスクランブルに用いられるRNTI(例えば、C-RNTI又はMCS-C-RNTIのどちらでCRCスクランブルされるか)
Further, the traffic type of PUSCH may be determined based on at least one of the following.
-The MCS index table used to determine at least one of the modulation order, target code rate, and TBS of the PUSCH (for example, whether or not to use the MCS index table 3).
RNTI used for CRC scrambling of DCI used for scheduling the PUSCH (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.
 URLLCの要件とeMBBの要件の違いは、URLLCの遅延(latency)がeMBBの遅延よりも小さいことであってもよいし、URLLCの要件が信頼性の要件を含むことであってもよい。 The difference between the URLLC requirement and the eMBB requirement may be that the URLLC latency is smaller than the eMBB delay, or the URLLC requirement may include a reliability requirement.
 例えば、eMBBのuser(U)プレーン遅延の要件は、下りリンクのUプレーン遅延が4msであり、上りリンクのUプレーン遅延が4msであること、を含んでもよい。一方、URLLCのUプレーン遅延の要件は、下りリンクのUプレーン遅延が0.5msであり、上りリンクのUプレーン遅延が0.5msであること、を含んでもよい。また、URLLCの信頼性の要件は、1msのUプレーン遅延において、32バイトの誤り率が10-5であることを含んでもよい。 For example, 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. On the other hand, 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. Also, the reliability requirement of URLLC may include a 32-byte error rate of 10-5 at a U-plane delay of 1 ms.
 また、enhanced Ultra Reliable and Low Latency Communications(eURLLC)として、主にユニキャストデータ用のトラフィックの信頼性(reliability)の高度化が検討されている。以下において、URLLC及びeURLLCを区別しない場合、単にURLLCと呼ぶ。 Also, as enhanced Ultra Reliable and Low Latency Communications (eURLLC), the improvement of traffic reliability mainly for unicast data is being considered. In the following, when URLLC and eURLLC are not distinguished, they are simply referred to as URLLC.
<優先度の設定>
 Rel.16以降のNRでは、所定の信号又はチャネルに対して複数レベル(例えば、2レベル)の優先度を設定することが検討されている。例えば、異なるトラフィックタイプ(サービス、サービスタイプ、通信タイプ、ユースケース等ともいう)にそれぞれ対応する信号又はチャネル毎に別々の優先度を設定して通信を制御(例えば、衝突時の送信制御等)することが想定される。これにより、同じ信号又はチャネルに対して、サービスタイプ等に応じて異なる優先度を設定して通信を制御することが可能となる。
<Priority setting>
Rel. In NR after 16 it is considered to set a plurality of levels (for example, 2 levels) of priority for a predetermined signal or channel. For example, communication is controlled by setting different priorities for each signal or channel corresponding to different traffic types (also referred to as service, service type, communication type, use case, 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.
 優先度は、信号(例えば、HARQ-ACK等のUCI、参照信号等)、チャネル(PDSCH、PUSCH、PUCCH等)、参照信号(例えば、チャネル状態情報(CSI)、サウンディング参照信号(SRS)等)、スケジューリングリクエスト(SR)、及びHARQ-ACKコードブックの少なくとも一つに対して設定されてもよい。また、SRの送信に利用されるPUCCH,HARQ-ACKの送信に利用されるPUCCH,CSIの送信に利用されるPUCCHに対して優先度がそれぞれ設定されてもよい。 The priority is a signal (for example, UCI such as HARQ-ACK, a reference signal, etc.), a channel (PDSCH, PUSCH, PUCCH, etc.), a reference signal (for example, a channel state information (CSI), a sounding reference signal (SRS), etc.). , Scheduling Request (SR), and HARQ-ACK Codebook. Further, priorities may be set for PUCCH used for SR transmission, PUCCH used for HARQ-ACK transmission, and PUCCH used for CSI transmission.
 優先度は、第1の優先度(例えば、high)と、当該第1の優先度より優先度が低い第2の優先度(例えば、low)で定義されてもよい。あるいは、3種類以上の優先度が設定されてもよい。 The priority may be defined by a first priority (for example, high) and a second priority (for example, low) which is lower than the first priority. Alternatively, three or more types of priorities may be set.
 例えば、動的にスケジュールされるPDSCH用のHARQ-ACK、セミパーシステントPDSCH(SPS PDSCH)用のHARQ-ACK、SPS PDSCHリリース用のHARQ-ACKに対して優先度が設定されてもよい。あるいは、これらのHARQ-ACKに対応するHARQ-ACKコードブックに対して優先度が設定されてもよい。なお、PDSCHに優先度を設定する場合、PDSCHの優先度を当該PDSCHに対するHARQ-ACKの優先度と読み替えてもよい。 For example, 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. Alternatively, a priority may be set for the HARQ-ACK codebook corresponding to these HARQ-ACKs. When setting the priority in the PDSCH, the priority of the PDSCH may be read as the priority of HARQ-ACK for the PDSCH.
 また、動的グラントベースのPUSCH、設定グラントベースのPUSCH等に対して優先度が設定されてもよい。 Further, the priority may be set for the dynamic grant-based PUSCH, the setting grant-based PUSCH, and the like.
 優先度に関する情報は、上位レイヤシグナリング及びDCIの少なくとも一つを利用して基地局からUEに通知されてもよい。例えば、スケジューリングリクエストの優先度は、上位レイヤパラメータ(例えば、schedulingRequestPriority)で設定されてもよい。DCIでスケジュールされるPDSCH(例えば、ダイナミックPDSCH)に対するHARQ-ACKの優先度は、当該DCIで通知されてもよい。SPS PDSCHに対するHARQ-ACKの優先度は、上位パラメータ(例えば、HARQ-ACK-Codebook-indicator-forSPS)で設定されてもよいし、SPS PDSCHのアクティブ化を指示するDCIで通知されてもよい。PUCCHで送信されるP-CSI/SP-CSIは所定の優先度(例えば、low)が設定されてもよい。一方で、PUSCHで送信されるA-CSI/SP-CSIは、DCI(例えば、トリガ用DCI又はアクティブ化用DCI)で優先度が通知されてもよい。 Information on the priority may be notified from the base station to the UE using at least one of higher layer signaling and DCI. For example, the priority of the scheduling request may be set by a higher layer parameter (for example, schedulingRequestPriority). The priority of the HARQ-ACK over the PDSCH scheduled by the DCI (eg, the dynamic PDSCH) may be notified by the DCI. The priority of HARQ-ACK for SPS PDSCH may be set by a higher parameter (for example, HARQ-ACK-Codebook-indicator-forSPS), or may be notified by DCI instructing activation of SPS PDSCH. A predetermined priority (for example, low) may be set for the P-CSI / SP-CSI transmitted by PUCCH. On the other hand, the A-CSI / SP-CSI transmitted by PUSCH may be notified of the priority by DCI (for example, DCI for triggering or DCI for activation).
 ダイナミックグラントベースのPUSCHの優先度は、当該PUSCHをスケジュールするDCIで通知されてもよい。設定グラントベースのPUSCHの優先度は、上位レイヤパラメータ(例えば、priority)で設定されてもよい。P-SRS/SP-SRS、DCI(例えば、DCIフォーマット0_1/DCIフォーマット2_3)でトリガされるA-SRSは、所定の優先度(例えば、low)が設定されてもよい。 The priority of the dynamic grant-based PUSCH may be notified by the DCI that schedules the PUSCH. Setting Grant-based PUSCH priority may be set by a higher layer parameter (eg, priority). A-SRS triggered by P-SRS / SP-SRS, DCI (eg, DCI format 0_1 / DCI format 2_3) may be set to a predetermined priority (eg, low).
(UL送信のオーバーラップ)
 UEは、複数のUL信号/ULチャネルがオーバーラップ(又は、衝突)する場合、優先度に基づいてUL送信を制御してもよい。
(Overlap of UL transmission)
The UE may control UL transmission based on priority when multiple UL signals / UL channels overlap (or collide).
 複数のUL信号/ULチャネルがオーバーラップするとは、複数のUL信号/ULチャネルの時間リソース(又は、時間リソースと周波数リソース)がオーバーラップする場合、又は複数のUL信号/ULチャネルの送信タイミングがオーバーラップする場合であってもよい。時間リソースは、時間領域又は時間ドメインと読み替えられてもよい。時間リソースは、シンボル、スロット、サブスロット、又はサブフレーム単位であってもよい。 When multiple UL signals / UL channels overlap, the time resources (or time resources and frequency resources) of multiple UL signals / UL channels overlap, or the transmission timing of multiple UL signals / UL channels is different. It may be the case of overlapping. A time resource may be read as a time domain or a time domain. Time resources may be in symbol, slot, subslot, or subframe units.
 同一UE(例えば、intra-UE)において複数のUL信号/ULチャネルがオーバーラップすることは、少なくとも同一の時間リソース(例えば、シンボル)において複数のUL信号/ULチャネルがオーバーラップすることを意味してもよい。また、異なるUE(例えば、inter-UE)においてUL信号/ULチャネルが衝突することは、同一の時間リソース(例えば、シンボル)及び周波数リソース(例えば、RB)において複数のUL信号/ULチャネルがオーバーラップすることを意味してもよい。 Overlapping of multiple UL signals / UL channels in the same UE (eg, intra-UE) means that multiple UL signals / UL channels overlap at least in the same time resource (eg, symbol). You may. Also, collision of UL signals / UL channels in different UEs (eg, inter-UE) means that multiple UL signals / UL channels are overloaded in the same time resource (eg, symbol) and frequency resource (eg, RB). It may mean to wrap.
 例えば、優先度が同じ複数のUL信号/ULチャネルがオーバーラップする場合、UEは、当該複数のUL信号/ULチャネルを、1つのULチャネルに多重(multiplex)して送信するように制御する(図1A参照)。 For example, when a plurality of UL signals / UL channels having the same priority overlap, the UE controls to multiplex the plurality of UL signals / UL channels to one UL channel for transmission (multiplex). See FIG. 1A).
 図1Aでは、第1の優先度(high)が設定されるHARQ-ACK(又は、HARQ-ACK送信用のPUCCH)と、第1の優先度(high)が設定されるULデータ/UL-SCH(又は、ULデータ/UL-SCH送信用のPUSCH)がオーバーラップする場合を示している。この場合、UEは、HARQ-ACKをPUSCHに多重(又は、マッピング)してULデータとHARQ-ACKの両方を送信する。 In FIG. 1A, HARQ-ACK (or PUCCH for HARQ-ACK transmission) in which the first priority (high) is set and UL data / UL-SCH in which the first priority (high) is set. (Or PUSCH for UL data / UL-SCH transmission) overlaps. In this case, the UE multiplexes (or maps) the HARQ-ACK to the PUSCH and transmits both the UL data and the HARQ-ACK.
 優先度が異なる複数のUL信号/ULチャネルがオーバーラップする場合、UEは、優先度が高いUL送信を行い(例えば、優先度が高いUL送信を優先し)、優先度が低いUL送信を行わない(例えば、ドロップする)ように制御してもよい(図1B参照)。 When multiple UL signals / UL channels with different priorities overlap, the UE performs a higher priority UL transmission (eg, prioritizes a higher priority UL transmission) and a lower priority UL transmission. It may be controlled so that it does not exist (for example, it drops) (see FIG. 1B).
 図1Bでは、第1の優先度(high)が設定されるULデータ/HARQ-ACK(又は、ULデータ/HARQ-ACK送信用のULチャネル)と、第2の優先度(low)が設定されるULデータ/HARQ-ACK(又は、ULデータ/HARQ-ACK送信用のULチャネル)がオーバーラップする場合を示している。この場合、UEは、優先度が低いULデータ/HARQ-ACKをドロップし、優先度が高いULデータ/HARQ-ACKを優先(prioritize)して送信するように制御する。なお、UEは、優先度が低いUL送信の送信タイミングを変更(例えば、延期又はシフト)してもよい。 In FIG. 1B, the UL data / HARQ-ACK (or the UL channel for UL data / HARQ-ACK transmission) in which the first priority (high) is set and the second priority (low) are set. The case where the UL data / HARQ-ACK (or the UL channel for UL data / HARQ-ACK transmission) overlaps is shown. In this case, the UE controls to drop the UL data / HARQ-ACK having a low priority and prioritize and transmit the UL data / HARQ-ACK having a high priority. The UE may change (for example, postpone or shift) the transmission timing of the UL transmission having a low priority.
 2個より多い(又は、3個以上の)UL信号/ULチャネルが時間領域においてオーバーラップする場合(図2A参照)、2つのステップにより送信が制御されてもよい。第1のステップでは、優先度が同じUL送信間で1つのULチャネルに多重する(図2B参照)。第2のステップでは、優先度が異なるUL送信間で、優先度が高いUL送信を優先して送信し、優先度が低いUL送信をドロップするように制御してもよい(図2C参照)。 When more than two (or three or more) UL signals / UL channels overlap in the time domain (see FIG. 2A), transmission may be controlled by two steps. In the first step, UL channels having the same priority are multiplexed into one UL channel (see FIG. 2B). In the second step, UL transmissions having different priorities may be controlled so as to preferentially transmit UL transmissions having higher priority and drop UL transmissions having lower priority (see FIG. 2C).
(アンライセンスバンド)
 アンライセンスバンド(例えば、2.4GHz帯、5GHz帯、6GHz帯など)では、例えば、Wi-Fiシステム、Licensed-Assisted Access(LAA)をサポートするシステム(LAAシステム)等の複数のシステムが共存することが想定されるため、当該複数のシステム間での送信の衝突回避及び/又は干渉制御が必要となると考えられる。
(Unlicensed band)
In the unlicensed band (for example, 2.4 GHz band, 5 GHz band, 6 GHz band, etc.), 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.
 既存のLTEシステム(例えば、Rel.13)のLAAでは、データの送信装置は、アンライセンスバンドにおけるデータの送信前に、他の装置(例えば、基地局、ユーザ端末、Wi-Fi装置など)の送信の有無を確認するリスニング(Listen Before Talk(LBT)、Clear Channel Assessment(CCA)、キャリアセンス、チャネルのセンシング、センシング、チャネルアクセス動作(channel access procedure))を行う。 In the LAA of an existing LTE system (eg, Rel.13), the data transmission device 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.
 当該送信装置は、例えば、下りリンク(DL)では基地局(例えば、gNB:gNodeB)、上りリンク(UL)ではユーザ端末(例えば、User Equipment(UE))であってもよい。また、送信装置からのデータを受信する受信装置は、例えば、DLではユーザ端末、ULでは基地局であってもよい。 The transmitting device may be, for example, a base station (for example, gNB: gNodeB) for the downlink (DL) and a user terminal (for example, User Equipment (UE)) for the uplink (UL). Further, 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.
 既存のLTEシステムのLAAでは、当該送信装置は、LBTにおいて他の装置の送信がないこと(アイドル状態)が検出されてから所定期間(例えば、直後又はバックオフの期間)後にデータ送信を開始する。 In the LAA of an existing LTE system, the transmitting device starts data transmission after a predetermined period (for example, immediately after or during a backoff period) after the LBT detects that there is no transmission of another device (idle state). ..
 将来の無線通信システム(例えば、5G、5G+、New Radio(NR)、3GPP Rel.15以降などともいう)でもアンライセンスバンドの利用が検討されている。アンライセンスバンドを用いるNRシステムは、NR-Unlicensed(U)システム、NR LAAシステムなどと呼ばれてもよい。 The use of unlicensed bands is also being considered for 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))、アンライセンスバンドのスタンドアローン(Stand-Alone(SA))なども、NR-Uに含まれてもよい。 NR-U may also include dual connectivity (DC) between licensed bands and unlicensed bands, and stand-alone (Stand-Alone (SA)) unlicensed bands.
 NR-Uにおけるノード(例えば、基地局、UE)は、他システム又は他オペレータとの共存のため、LBTによりチャネルが空いていること(idle)を確認してから、送信を開始する。 The node (for example, base station, UE) in NR-U confirms that the channel is free (idle) by LBT for coexistence with other systems or other operators, and then starts transmission.
 NR-Uにおいて、基地局(例えば、gNB)又はUEは、LBT結果がアイドルである場合に送信機会(Transmission Opportunity(TxOP))を獲得し、送信を行う。基地局又はUEは、LBT結果がビジーである場合(LBT-busy)に、送信を行わない。送信機会の時間は、チャネル占有時間(Channel Occupancy Time(COT))と呼ばれてもよい。 In the NR-U, 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. The base station or UE does not transmit when the LBT result is busy (LBT-busy). The time of the transmission opportunity may be referred to as channel occupation time (Channel Occupancy Time (COT)).
 なお、LBT-idleは、LBTの成功(LBT success)で読み替えられてもよい。LBT-busyは、LBTの失敗(LBT failure)で読み替えられてもよい。 LBT-idle may be read as the success of LBT (LBT success). LBT-busy may be read as LBT failure.
(HARQ-ACKコードブック)
 UEは、1以上の送達確認情報(例えば、Hybrid Automatic Repeat reQuest ACKnowledgement(HARQ-ACK))のビットから構成されるHARQ-ACKコードブック単位で、1つのPUCCHリソースを用いてHARQ-ACKフィードバックを送信してもよい。HARQ-ACKビットは、HARQ-ACK情報、HARQ-ACK情報ビットなどと呼ばれてもよい。
(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.
 ここで、HARQ-ACKコードブックは、時間領域(例えば、スロット)、周波数領域(例えば、コンポーネントキャリア(Component Carrier(CC)))、空間領域(例えば、レイヤ)、トランスポートブロック(Transport Block(TB))、及びTBを構成するコードブロックグループ(Code Block Group(CBG))の少なくとも1つの単位でのHARQ-ACK用のビットを含んで構成されてもよい。HARQ-ACKコードブックは、単にコードブックと呼ばれてもよい。 Here, the HARQ-ACK codebook includes a time domain (for example, a slot), a frequency domain (for example, a component carrier (CC)), a spatial domain (for example, a layer), and a transport block (TB). )), And 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 be simply referred to as a codebook.
 なお、HARQ-ACKコードブックに含まれるビット数(サイズ)等は、準静的(semi-static)又は動的に(dynamic)決定されてもよい。準静的にサイズが決定されるHARQ-ACKコードブックは、準静的HARQ-ACKコードブック、タイプ1HARQ-ACKコードブックなどとも呼ばれる。動的にサイズが決定されるHARQ-ACKコードブックは、動的HARQ-ACKコードブック、タイプ2HARQ-ACKコードブックなどとも呼ばれる。 The number of bits (size) and the like included in the HARQ-ACK codebook may be determined quasi-static (semi-static) or dynamically (dynamic). 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.
 タイプ1HARQ-ACKコードブック及びタイプ2HARQ-ACKコードブックのいずれを用いるかは、上位レイヤパラメータ(例えば、pdsch-HARQ-ACK-Codebook)を用いてUEに設定されてもよい。 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).
 タイプ1HARQ-ACKコードブックの場合、UEは、ある範囲(例えば、上位レイヤパラメータに基づいて設定される範囲)において、PDSCHのスケジューリングの有無に関係なく、当該範囲に対応するPDSCH候補(又はPDSCH機会(オケージョン))に対するHARQ-ACKビットをフィードバックしてもよい。 For a Type 1 HARQ-ACK codebook, the UE will have a PDSCH candidate (or PDSCH opportunity) corresponding to that range, with or without PDSCH scheduling, in a range (eg, a range set based on higher layer parameters). The HARQ-ACK bit for (occasion)) may be fed back.
 当該範囲は、ある期間(例えば、候補となるPDSCH受信用の特定の数の機会(occasion)のセット、又は、下りリンク制御チャネル(Physical Downlink Control Channel(PDCCH))の特定の数のモニタリング機会(monitoring occasion))、UEに設定又はアクティブ化されるCCの数、TBの数(レイヤ数又はランク)、1TBあたりのCBG数、空間バンドリングの適用の有無、の少なくとも1つに基づいて定められてもよい。当該特定の範囲は、HARQ-ACKウィンドウ、HARQ-ACKバンドリングウィンドウ、HARQ-ACKフィードバックウィンドウなどとも呼ばれる。 The range is a set of a specific number of opportunities for receiving candidate PDSCHs, or a specific number of monitoring opportunities for a Physical Downlink Control Channel (PDCCH) for a period of time (eg, a specific number of opportunities for receiving a candidate PDSCH (PDCCH). Monitoring occasion)), the number of CCs set or activated in the UE, the number of TBs (number of layers or ranks), the number of CBGs per TB, and the presence or absence of spatial bundling. You may. The specific range is also referred to as a HARQ-ACK window, a HARQ-ACK bundling window, a HARQ-ACK feedback window, and the like.
 タイプ1HARQ-ACKコードブックでは、特定の範囲内であれば、UEに対するPDSCHのスケジューリングが無い場合でも、UEは、当該PDSCHに対するHARQ-ACKビットをコードブック内に確保する。UEは、当該PDSCHが実際にはスケジューリングされてないと判断した場合、当該ビットをNACKビットとしてフィードバックできる。 In the type 1 HARQ-ACK codebook, within a specific range, the UE allocates the HARQ-ACK bit for the PDSCH in the codebook even if there is no PDSCH scheduling for the UE. If the UE determines that the PDSCH is not actually scheduled, the UE can feed back the bit as a NACK bit.
 一方、タイプ2HARQ-ACKコードブックの場合、UEは、上記特定の範囲において、スケジューリングされたPDSCHに対するHARQ-ACKビットをフィードバックしてもよい。 On the other hand, in the case of the type 2 HARQ-ACK codebook, the UE may feed back the HARQ-ACK bit for the scheduled PDSCH within the above specific range.
 具体的には、UEは、タイプ2HARQ-ACKコードブックのビット数を、DCI内の特定のフィールド(例えば、DL割り当てインデックス(Downlink Assignment Indicator(Index)(DAI))フィールド)に基づいて決定してもよい。DAIフィールドは、カウンタDAI(Counter DAI(C-DAI))及びトータルDAI(Total DAI(T-DAI))を含んでもよい。 Specifically, the UE determines the number of bits in the Type 2 HARQ-ACK codebook based on a particular field in the DCI (eg, the Downlink Assignment Indicator (Index) (DAI) field). May be good. The DAI field may include a counter DAI (Counter DAI (C-DAI)) and a total DAI (Total DAI (T-DAI)).
 C-DAIは、特定の期間内でスケジューリングされる下り送信(PDSCH、データ、TB)のカウンタ値を示してもよい。例えば、当該特定の期間内にデータをスケジューリングするDCI内のC-DAIは、当該特定の期間内で最初に周波数領域(例えば、CC)で、その後に時間領域でカウントされた数を示してもよい。例えば、C-DAIは、特定の期間に含まれる1つ以上のDCIについて、サービングセルインデックスの昇順で、次にPDCCHモニタリング機会の昇順でPDSCH受信又はセミパーシステントスケジューリング(Semi-Persistent Scheduling(SPS))リリースをカウントした値に該当してもよい。 C-DAI may indicate a counter value of downlink transmission (PDSCH, data, TB) scheduled within a specific period. For example, a C-DAI in a DCI that schedules data within that particular period may indicate a number that is first counted in the frequency domain (eg, CC) and then in the time domain within that particular period. good. For example, C-DAI may receive PDSCH or semi-persistent scheduling (SPS) for one or more DCIs included in a particular period in ascending order of serving cell index and then in ascending order of PDCCH monitoring opportunities. It may correspond to the value obtained by counting the releases.
 T-DAIは、特定の期間内でスケジューリングされるデータの合計値(総数)を示してもよい。例えば、当該特定の期間内のある時間ユニット(例えば、PDCCHモニタリング機会)においてデータをスケジューリングするDCI内のT-DAIは、当該特定の期間内で当該時間ユニット(ポイント、タイミングなどともいう)までにスケジューリングされたデータの総数を示してもよい。 T-DAI may indicate the total value (total number) of data scheduled within a specific period. For example, a T-DAI in a DCI that schedules data in a time unit (eg, PDCCH monitoring opportunity) within that particular period may be up to that time unit (also referred to as point, timing, etc.) within that particular period. It may indicate the total number of scheduled data.
 また、異なるサービスタイプ(又は、異なる優先度が設定されたPDSCH又はHARQ-ACK)に対して、HARQ-ACKコードブックが別々に設定されることが検討されている。つまり、複数のサービスタイプ(又は、複数の優先度)をサポートするために、複数のHARQ-ACKコードブックが同時に構成されることが考えられる。例えば、URLLC(例えば、第1の優先度)に対応する第1のHARQ-ACKコードブックと、eMBB(例えば、第2の優先度)に対応する第2のHARQ-ACKコードブックが構成されてもよい。 It is also being considered that the HARQ-ACK codebook is set separately for different service types (or PDSCH or HARQ-ACK with different priorities). 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 corresponding to URLLC (eg, first priority) and a second HARQ-ACK codebook corresponding to eMBB (eg, second priority) are configured. May be good.
 この場合、第1のHARQ-ACKコードブックに対応する第1のPUCCH設定パラメータ(例えば、PUCCH configuration、又はPUCH configuration parameters)と、第2のHARQ-ACKコードブックに対応する第2のPUCCH設定パラメータは別々にサポート又は設定されてもよい。PUCCH設定パラメータは、HARQ-ACKの送信に適用するPUCCHリソース(又は、PUCCHリソースセット)、PUCCHの送信タイミング(例えば、K1セット)、最大符号化率(例えば、max-code rate)及びPUCCHの送信電力の少なくとも一つであってもよい。 In this case, the first PUCCH setting parameter corresponding to the first HARQ-ACK codebook (for example, PUCCH configuration or PUCH configuration parameters) and the second PUCCH setting parameter corresponding to the second HARQ-ACK codebook. May be supported or configured separately. The PUCCH setting parameters are the PUCCH resource (or PUCCH resource set) applied to the HARQ-ACK transmission, 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.
 この場合、第1のPUCCH設定情報は、URLLC用のHARQ-ACKフィードバックに適用され、第2のPUCCH設定情報は、eMBB用のHARQ-ACKフィードバックに適用されてもよい。 In this case, the first PUCCH setting information may be applied to the HARQ-ACK feedback for URLLC, and the second PUCCH setting information may be applied to the HARQ-ACK feedback for eMBB.
(HARQプロセス)
 キャリアアグリゲーション(CA)またはデュアルコネクティビティ(DC)が設定されたUEに対し、セル(CC)またはセルグループ(CG)ごとに1つの独立したHARQエンティティ(entity)が存在してもよい。HARQエンティティは、複数のHARQプロセスを並行して管理してもよい。
(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.
 無線通信システムでは、データ送信はスケジューリングに基づき、Downlink(DL)データ送信のスケジューリング情報は下り制御情報(DCI)で搬送される。HARQプロセスに対しHARQプロセス番号(HARQ Process Number(HPN))が与えられる。DCIは、現在のデータ送信に使用されるHARQプロセス番号を示す4ビットのHARQプロセス番号フィールドを含む。HARQエンティティは、複数(最大16個)のHARQプロセスを並行して管理する。すなわち、HARQプロセス番号は、HPN0からHPN15まで存在する。HARQプロセス番号は、HARQプロセスID(HARQ process identifier)とも呼ばれる。 In the wireless communication system, data transmission is based on scheduling, and downlink (DL) data transmission scheduling information is carried by downlink control information (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 multiple (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 identifier (HARQ process identifier).
 Uplink(UL)データをPhysical Uplink Shared Channel(PUSCH)で送信する単位、および、DLデータをPhysical Downlink Shared Channel(PDSCH)で送信する単位は、トランスポートブロック(Transport Block(TB))と呼ばれてもよい。TBは、Media Access Control(MAC)層によって扱われる単位である。HARQ(再送信)の制御は、TBごとに行われてもよいし、TB内の1つ以上のコードブロック(Code Block(CB))を含むコードブロックグループ(Code Block Group(CBG))ごとに行われてもよい。 The unit for transmitting Uplink (UL) data on the Physical Uplink Shared Channel (PUSCH) and the unit for transmitting DL data on the Physical Downlink Shared Channel (PDSCH) are called transport blocks (TB). May be good. TB is a unit handled by the Media Access Control (MAC) layer. 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.
 ユーザ端末は、PDSCHを使用して受信したDLトランスポートブロックの復号に成功したか否かを示すHARQの肯定応答(Positive Acknowledgement(ACK))/否定応答(Negative Acknowledgement(NACK))を示す情報を、PUCCH(Physical Uplink Control Channel)またはPUSCHなどを使用して基地局へ送信する。 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 was successfully decoded. , PUCCH (Physical Uplink Control Channel) or PUSCH is used to transmit to the base station.
 物理層で複数のULデータまたは複数のDLデータが空間多重(spatial multiplexing)されない場合、単一のHARQプロセスは、1つのトランスポートブロック(TB)に対応する。物理層で複数のULデータまたは複数のDLデータが空間多重される場合、単一のHARQプロセスは、1または複数のトランスポートブロック(TB)に対応してもよい。 When multiple UL data or multiple DL data are not spatially multiplexed in the physical layer, a single HARQ process corresponds to one transport block (TB). When multiple UL data or multiple DL data are spatially multiplexed in the physical layer, a single HARQ process may correspond to one or more transport blocks (TB).
(エンハンスドダイナミックHARQフィードバック)
 Rel.16以降では、UEにおけるLBTの失敗又は基地局におけるPUCCHの検出ミスによるHARQ-ACKフィードバック用の送信機会を提供するために、あるリソースにおいて、複数のHARQ-ACKプロセスを含むHARQ-ACKコードブックのフィードバックを行うことを、UEに要求又はトリガすることが検討されている。HARQ-ACKプロセス(例えば、DL HARQ-ACKプロセス)は、PUCCHグループにおいてUEに設定された全てのCCにおけるHARQ-ACKであってもよい。
(Enhanced Dynamic HARQ Feedback)
Rel. From 16 onwards, in a resource, a HARQ-ACK codebook containing multiple HARQ-ACK processes to provide a transmission opportunity for HARQ-ACK feedback due to LBT failure in the UE or PUCCH detection error in the base station. It is being considered to request or trigger the UE to provide feedback. The HARQ-ACK process (eg, DL HARQ-ACK process) may be HARQ-ACK in all CCs configured on the UE in the PUCCH group.
 複数のHARQ-ACKプロセスを含むHARQ-ACK(又は、HARQ-ACKコードブック)のフィードバックは、拡張動的(エンハンスドダイナミック、Enhanced dynamic)HARQ-ACKフィードバック、エンハンスドダイナミックHARQフィードバック、グループベース(group-based)HARQフィードバック、エンハンスドダイナミックHARQ-ACKコードブック、などと呼ばれてもよい。エンハンスドダイナミックHARQフィードバックは、基地局からUEに特定のDCIフォーマットを利用して通知してもよい。特定のDCIフォーマットは、UE固有のDCIフォーマット(例えば、DCIフォーマット1_1)であってもよい。 HARQ-ACK (or HARQ-ACK codebook) feedback that includes multiple HARQ-ACK processes includes enhanced dynamic HARQ-ACK feedback, enhanced dynamic HARQ feedback, and group-based. ) HARQ feedback, enhanced dynamic HARQ-ACK codebook, etc. may be referred to. Enhanced dynamic HARQ feedback may be notified from the base station to the UE using a specific DCI format. The particular DCI format may be a UE-specific DCI format (eg, DCI format 1-11).
 特定のDCIフォーマット(例えば、DCIフォーマット1_1)は、エンハンスドダイナミックHARQフィードバックを通知(要求又はトリガ)するために、特定のフィールドを含んでもよい。当該特定のフィールドは、PDSCHグループインデックス(PDSCH group index)フィールド、および、要求PDSCHグループ数(Number of requested PDSCH group(s))フィールドの少なくとも一つであってもよい。 A particular DCI format (eg, DCI format 1-11) may include a particular field to signal (request or trigger) enhanced dynamic HARQ feedback. The specific field may be at least one of a PDSCH group index (PDSCH group index) field and a number of requested PDSCH group (s) fields.
 特定のDCIフォーマット(例えば、DCIフォーマット1_1)に含まれる特定のフィールド(例えば、PDSCHグループインデックス(PDSCH group index)フィールド、要求PDSCHグループ数(Number of requested PDSCH group(s))フィールド)は、特定の上位レイヤパラメータ(pdsch-HARQ-ACK-Codebook)がエンハンスドダイナミック(例えば、enhancedDynamic-r16、enhancedDynamic)に設定される場合、1ビットのビット長を有してもよく、その他の場合には0ビットであってもよい。 A specific field (eg, PDSCH group index field, Number of requested PDSCH group (s) field) contained in a specific DCI format (for example, DCI format 1-11) is a specific field. If the higher layer parameter (pdsch-HARQ-ACK-Codebook) is set to enhanced dynamics (eg enhancedDynamic-r16, enhancedDynamic), it may have a bit length of 1 bit, otherwise it may be 0 bits. There may be.
 PDSCHグループインデックス(PDSCH group index)は、PDSCHグループインデックスを含むDCIによってスケジュールされるPDSCHのグループを特定するインデックスであってもよい。 The PDSCH group index (PDSCH group index) may be an index that identifies a group of PDSCHs scheduled by DCI including the PDSCH group index.
 DCI内の要求PDSCHグループ数(Number of requested PDSCH group(s))フィールドの値が“0”である場合、UEは、そのDCIによってスケジュールされるPDSCHグループに対する一以上のHARQフィードバックを、あるリソースにおいて行ってもよい。DCI内の要求PDSCHグループ数フィールドの値が“1”である場合、UEは、そのDCIによってスケジュールされるPDSCHグループと、そのDCIによってスケジュールされるPDSCHグループとは別のPDSCHグループと、に対する一以上のHARQフィードバックを、あるリソースにおいて行ってもよい。言い換えれば、DCI内の要求PDSCHグループ数フィールドの値が“1”である場合、UEは、PDSCHグループインデックス“0”及び“1”が設定されるPDSCHに対するHARQフィードバックを、あるリソースにおいて行ってもよい。 If the value of the Number of requested PDSCH group (s) field in the DCI is "0", the UE will provide one or more HARQ feedback to the PDSCH group scheduled by that DCI in a resource. You may go. When the value of the request PDSCH group number field in the DCI is "1", the UE has one or more for the PDSCH group scheduled by the DCI and a PDSCH group different from the PDSCH group scheduled by the DCI. HARQ feedback may be given at a resource. In other words, if the value of the requested PDSCH group number field in the DCI is "1", the UE may provide HARQ feedback to the PDSCH where the PDSCH group indexes "0" and "1" are set in a resource. good.
 また、特定のDCIフォーマット(例えば、DCIフォーマット1_1)は、特定のフィールド(例えば、新規フィードバックインジケータ(New feedback indicator(NFI))フィールド)を含んでもよい。 Further, the specific DCI format (for example, DCI format 1-11) may include a specific field (for example, a new feedback indicator (NFI) field).
 特定のDCIフォーマット(例えば、DCIフォーマット1_1)に含まれる特定のフィールド(例えば、新規フィードバックインジケータ(New feedback indicator)フィールド)は、特定の上位レイヤパラメータ(pdsch-HARQ-ACK-Codebook)がエンハンスドダイナミック(enhancedDynamic-r16)に設定され、かつ、別の上位レイヤパラメータ(NFI-TotalDAI-Included-r16)が設定される(NFI-TotalDAI-Included-r16=enableである)場合、2ビットのビット長を有してもよい。また、特定のフィールド(例えば、新規フィードバックインジケータ(New feedback indicator)フィールド)は、特定の上位レイヤパラメータ(pdsch-HARQ-ACK-Codebook)がエンハンスドダイナミック(enhancedDynamic-r16)に設定され、かつ、別の上位レイヤパラメータ(NFI-TotalDAI-Included-r16)が設定されない場合、1ビットのビット長を有してもよく、その他の場合には0ビットであってもよい。 A specific field (eg, a New feedback indicator field) contained in a specific DCI format (for example, DCI format 1-11) has a specific upper layer parameter (pdsch-HARQ-ACK-Codebook) enhanced dynamic (for example). If it is set to enhancedDynamic-r16) and another upper layer parameter (NFI-TotalDAI-Included-r16) is set (NFI-TotalDAI-Included-r16 = enable), it has a bit length of 2 bits. You may. Further, in a specific field (for example, a new feedback indicator (New feedback indicator) field), a specific upper layer parameter (pdsch-HARQ-ACK-Codebook) is set to the enhanced dynamic (enhancedDynamic-r16), and another field is used. If the upper layer parameter (NFI-TotalDAI-Included-r16) is not set, it may have a bit length of 1 bit, and in other cases, it may be 0 bit.
 なお、当該別の上位レイヤパラメータ(NFI-TotalDAI-Included-r16)は、NFI及びスケジュールされていないPDSCHグループのT-DAIフィールドが、非フォールバックDLグラントDCI(例えば、DCIフォーマット1_1)に含まれるかどうかを示すパラメータであってもよい。 The other upper layer parameter (NFI-TotalDAI-Included-r16) includes the NFI and the T-DAI field of the unscheduled PDSCH group in the non-fallback DL grant DCI (eg DCI format 1-11). It may be a parameter indicating whether or not.
 エンハンスドダイナミックHARQフィードバックを要求又はトリガされたUEは、一以上のHARQ-ACKプロセスを含むコードブックを、PUCCH/PUSCHを利用してフィードバックしてもよい。 A UE requesting or triggering enhanced dynamic HARQ feedback may feed back a codebook containing one or more HARQ-ACK processes using PUCCH / PUSCH.
 図3は、エンハンスドダイナミックHARQフィードバック方法の一例を示す図である。図3の例において、UEは、COT#0におけるPDCCH1及びPDCCH2をモニタし、COT#1におけるPDCCH3をモニタしている。PDCCH1、PDCCH2及びPDCCH3のそれぞれにおいて伝送されるDCIによって、PDSCH1、PDSCH2及びPDSCH3がスケジュールされている。PDSCH1に対して指示されるPDSCHグループインデックスは0であり、PDSCH2及びPDSCH3に対して指示されるPDSCHグループインデックスは1である。 FIG. 3 is a diagram showing an example of an enhanced dynamic HARQ feedback method. In the example of FIG. 3, the UE monitors PDCCH1 and PDCCH2 in COT # 0 and monitors PDCCH3 in COT # 1. PDSCH1, PDSCH2 and PDSCH3 are scheduled by DCI transmitted in each of PDCCH1, PDCCH2 and PDCCH3. The PDSCH group index indicated for PDSCH1 is 0, and the PDSCH group index indicated for PDSCH2 and PDSCH3 is 1.
 図3の例において、UEは、PDCCH1及びPDCCH3の開始シンボルにおいて、LBTを開始する。UEは、PDCCH1によって、グループ0のPDSCH(PDSCH1)に対するHARQ-ACK1を、COT#0におけるHARQ-ACK送信用リソースにおいて送信するよう指示される(HARQフィードバックタイミング(PDSCH-to-HARQ_feedback timing indicator)、K1が2である)。UEは、COT#0におけるLBTに失敗すると、HARQ-ACK1を送信しない。 In the example of FIG. 3, the UE starts LBT at the start symbols of PDCCH1 and PDCCH3. The UE is instructed by PDCCH1 to transmit HARQ-ACK1 for PDSCH (PDSCH1) of group 0 in the HARQ-ACK transmission resource in COT # 0 (HARQ feedback timing (PDSCH-to-HARQ_feedback timing indicator)). K1 is 2). The UE does not transmit HARQ-ACK1 if the LBT at COT # 0 fails.
 また、図3の例において、グループ1のPDSCH(PDSCH2)に対するHARQ-ACK2について、PDCCH2によって受信するDCIに含まれるHARQフィードバックタイミングの値(K1)が適用不可能(inapplicable)である場合、UEは、COT#0におけるHARQ-ACK送信用リソースにおいて、HARQ-ACK2を送信しない(HARQ-ACK2を保持する)。 Further, in the example of FIG. 3, when the HARQ feedback timing value (K1) included in the DCI received by the PDCCH2 is inapplicable for HARQ-ACK2 for the PDSCH (PDSCH2) of the group 1, the UE is determined. , HARQ-ACK2 is not transmitted (HARQ-ACK2 is retained) in the HARQ-ACK transmission resource in COT # 0.
 さらに、図3の例において、UEは、PDCCH3によって、グループ1のPDSCH(PDSCH3)に対するHARQ-ACK3を、COT#1におけるHARQ-ACK送信用リソースにおいて送信するよう指示される(K1が2である)。当該PDCCH3のDCIに含まれる要求PDSCHグループ数フィールドの値が“1”の場合、COT#1におけるHARQ-ACK送信用リソースにおいて、PDCCH3がスケジュールするPDSCHグループ(PDSCHグループ1)と、PDCCH3がスケジュールしないPDSCHグループ(PDSCHグループ0)と、に対応するPDSCHに対するHARQ-ACKを送信する。 Further, in the example of FIG. 3, the UE is instructed by PDCCH3 to transmit HARQ-ACK3 for the PDSCH (PDSCH3) of group 1 in the HARQ-ACK transmission resource in COT # 1 (K1 is 2). ). When the value of the request PDSCH group number field included in the DCI of the PDCCH 3 is "1", the PDCCH group (PDSCH group 1) scheduled by the PDCCH 3 and the PDCCH 3 are not scheduled in the HARQ-ACK transmission resource in COT # 1. The PDSCH group (PDSCH group 0) and the HARQ-ACK for the corresponding PDSCH are transmitted.
 図3の例において、UEは、COT#1におけるLBTに成功すると、HARQ-ACK3の送信を行う。このとき、UEは、COT#0におけるLBTの失敗によって送信しなかったHARQ-ACK1と、保持しているHARQ-ACK2と、をHARK-ACK3の送信用リソースに多重し、送信する。 In the example of FIG. 3, when the UE succeeds in LBT in COT # 1, it transmits HARQ-ACK3. At this time, the UE multiplexes the HARQ-ACK1 that was not transmitted due to the failure of the LBT in COT # 0 and the held HARQ-ACK2 to the transmission resource of the HARK-ACK3, and transmits the HARQ-ACK1.
 このように、UEは、DCIに含まれる要求PDSCHグループ数に基づいて、PDSCHのグループ単位で1以上のHARQ-ACKフィードバックを制御してもよい。 In this way, the UE may control one or more HARQ-ACK feedback in units of PDSCH groups based on the number of requested PDSCH groups included in the DCI.
(1ショットHARQフィードバック)
 Rel.16以降では、UEにおけるLBTの失敗又は基地局におけるPUCCHの検出ミスによるHARQ-ACKフィードバック用の送信機会を提供するために、複数(例えば、全て)のHARQ-ACKプロセスを含むHARQ-ACKコードブックのフィードバックをUEに要求又はトリガすることが検討されている。HARQ-ACKプロセス(例えば、DL HARQ-ACKプロセス)は、PUCCHグループにおいてUEに設定された複数(例えば、全て)のCCにおけるHARQ-ACKであってもよい。
(1 shot HARQ feedback)
Rel. From 16 onwards, a HARQ-ACK codebook containing multiple (eg, all) HARQ-ACK processes to provide a transmission opportunity for HARQ-ACK feedback due to an LBT failure in the UE or a PUCCH detection error in the base station. It is being considered to request or trigger feedback from the UE. The HARQ-ACK process (eg, DL HARQ-ACK process) may be HARQ-ACK in multiple (eg, all) CCs configured on the UE in the PUCCH group.
 複数(例えば、全て)のCCにおける複数(例えば、全て)のHARQ-ACKプロセスを含むHARQ-ACK(又は、HARQ-ACKコードブック)のフィードバックは、1ショット(ワンショット(One-shot))HARQ-ACKフィードバック、1ショット(ワンショット(One-shot))HARQフィードバック、HARQ-ACKワンショットフィードバックと呼ばれてもよい。1ショットHARQフィードバックは、基地局からUEに特定のDCIフォーマットを利用して通知してもよい。特定のDCIフォーマットは、UE固有のDCIフォーマット(例えば、DCIフォーマット1_1)であってもよい。 The feedback of HARQ-ACK (or HARQ-ACK codebook) including multiple (eg, all) HARQ-ACK processes in multiple (eg, all) CCs is one-shot (One-shot) HARQ. -ACK feedback One-shot (One-shot) HARQ feedback may be referred to as HARQ-ACK one-shot feedback. The one-shot HARQ feedback may be notified from the base station to the UE using a specific DCI format. The particular DCI format may be a UE-specific DCI format (eg, DCI format 1-11).
 特定のDCIフォーマット(例えば、DCIフォーマット1_1)は、ワンショットHARQ-ACKフィードバックを通知するために、特定のフィールドを含んでもよい。当該特定のフィールドは、1ショットHARQ-ACK要求(One-shot HARQ-ACK request)フィールドであってもよい。 A particular DCI format (eg, DCI format 1-11) may include a particular field to signal one-shot HARQ-ACK feedback. The specific field may be a one-shot HARQ-ACK request field.
 特定のDCIフォーマット(例えば、DCIフォーマット1_1)に含まれる特定のフィールド(例えば、1ショットHARQ-ACK要求(One-shot HARQ-ACK request)フィールド)は、特定の上位レイヤパラメータ(pdsch-HARQ-ACK-OneShotFeedback-r16)が設定される場合、1ビットのビット長を有してもよく、その他の場合には0ビットであってもよい。 A specific field (eg, a one-shot HARQ-ACK request field) contained in a specific DCI format (eg, DCI format 1-11) is a specific upper layer parameter (pdsch-HARQ-ACK). When -OneShotFeedback-r16) is set, it may have a bit length of 1 bit, and in other cases, it may be 0 bit.
 1ショットHARQ-ACK要求(One-shot HARQ-ACK request)は、複数(例えば、全て)のHARQプロセスを、あるリソースにおいて送信することをUEに要求又はトリガするパラメータであってもよい。 The one-shot HARQ-ACK request may be a parameter that requests or triggers the UE to transmit a plurality of (for example, all) HARQ processes in a certain resource.
 1ショットHARQ-ACK要求(One-shot HARQ-ACK request)の値が“0”である場合、UEは、1ショットHARQ-ACK要求を含むDCIによってスケジュールされるPDSCHに対するHARQフィードバックを、あるリソースにおいて行ってもよい。1ショットHARQ-ACK要求の値が“1”である場合、UEは、PDSCHに対する送信していないHARQフィードバックと、1ショットHARQ-ACK要求を含むDCIによってスケジュールされるPDSCHに対するHARQフィードバックとを、あるリソースにおいて行ってもよい。 If the value of the one-shot HARQ-ACK request is "0", the UE will provide HARQ feedback to the PDSCH scheduled by the DCI containing the one-shot HARQ-ACK request in a resource. You may go. If the value of the one-shot HARQ-ACK request is "1", the UE has untransmitted HARQ feedback for the PDSCH and HARQ feedback for the PDSCH scheduled by the DCI containing the one-shot HARQ-ACK request. It may be done in resources.
 1ショットHARQフィードバックを要求又はトリガされたUEは、設定された各CCにおける複数(例えば、全て)のHARQ-ACKプロセスを含むコードブックを、PUCCH/PUSCHを利用してフィードバックしてもよい。このとき、フィードバックに新規データインジケータ(New Data Indicator(NDI))を含めることによって、UEとgNB間でのHARQ不整合を回避することができる。 A UE requesting or triggering one-shot HARQ feedback may use PUCCH / PUSCH to feed back a codebook containing a plurality of (for example, all) HARQ-ACK processes in each configured CC. At this time, by including a new data indicator (New Data Indicator (NDI)) in the feedback, it is possible to avoid HARQ inconsistency between the UE and gNB.
 図4は、1ショットHARQフィードバック方法の一例を示す図である。図4の例における各チャネルリソースの配置及びLBTのタイミングは、図3と同じである。 FIG. 4 is a diagram showing an example of a one-shot HARQ feedback method. The arrangement of each channel resource and the timing of LBT in the example of FIG. 4 are the same as those of FIG.
 図4の例において、UEは、COT#0におけるLBTに失敗すると、HARQ-ACK1を送信しない。また、UEは、PDSCH2に対するHARQ-ACK2について、PDCCH2によって受信するDCIに含まれるHARQフィードバックタイミングの値(K1)が適用不可能(inapplicable)である場合、COT#0におけるHARQ-ACK送信用リソースにおいて、HARQ-ACK2を送信しない(HARQ-ACK2を保持する)。 In the example of FIG. 4, the UE does not transmit HARQ-ACK1 if the LBT at COT # 0 fails. Further, regarding HARQ-ACK2 for PDSCH2, when the HARQ feedback timing value (K1) included in the DCI received by PDCCH2 is inapplicable, the UE performs the HARQ-ACK transmission resource in COT # 0. , Do not send HARQ-ACK2 (hold HARQ-ACK2).
 また、図4の例において、UEは、PDCCH3によって、グループ1のPDSCH(PDSCH3)に対するHARQ-ACK3を、COT#1におけるHARQ-ACK送信用リソースにおいて送信するよう指示される(K1が2である)。UEは、COT#1におけるLBTに成功すると、HARQ-ACK3の送信を行う。このとき、UEは、PDCCH3によって受信するDCIによって1ショットHARQフィードバックが指示される場合、COT#0において、LBTの失敗によって送信しなかったHARQ-ACK1と、保持しているHARQ-ACK2と、をHARK-ACK3の送信用リソースに多重し、送信する。 Also, in the example of FIG. 4, the UE is instructed by PDCCH3 to transmit HARQ-ACK3 for the PDSCH (PDSCH3) of group 1 in the HARQ-ACK transmission resource in COT # 1 (K1 is 2). ). When the UE succeeds in LBT in COT # 1, it transmits HARQ-ACK3. At this time, when the one-shot HARQ feedback is instructed by the DCI received by the PDCCH 3, the UE receives HARQ-ACK1 which was not transmitted due to the failure of the LBT and HARQ-ACK2 which is held in COT # 0. It is multiplexed with the transmission resource of HARK-ACK3 and transmitted.
 このように、UEは、DCIに含まれる1ショットHARQ-ACKの要求に基づいて、1以上のHARQ-ACKフィードバックを制御してもよい。 In this way, the UE may control one or more HARQ-ACK feedbacks based on the one-shot HARQ-ACK request contained in the DCI.
(マルチプルHARQ-ACKコードブック)
 Rel.16以降では、所定スロット(例えば、1スロット)において、最大N個のHARQ-ACKコードブックを構成することが許容されてもよい。Nは、例えば2であってもよい。例えば、Nが2の場合、UEは、所定スロットにおいて、優先度が異なるHARQ-ACK用のコードブック(又は、異なる優先度/異なるサービスタイプに対応するコードブック)を2個構成し、当該コードブックをフィードバックしてもよい。
(Multiple HARQ-ACK Codebook)
Rel. From 16 onwards, it may be permissible to configure up to N HARQ-ACK codebooks in a predetermined slot (eg, 1 slot). N may be 2, for example. For example, when N is 2, the UE configures two codebooks for HARQ-ACK having different priorities (or codebooks corresponding to different priorities / different service types) in a predetermined slot, and the code concerned. You may feed back the book.
 UEは、各PDSCHにそれぞれ対応するDCIに含まれる優先度通知フィールド(例えば、Priority Indicator field)の値に基づいて、HARQ-ACKコードブックの生成(例えば、HARQ-ACKコードブック内のHARQ-ACKビットの生成)を制御してもよい。図5は、スロット#nにおいて、異なる優先度に対応する2個のHARQ-ACKコードブック(ここでは、CB#0とCB#1)を生成/フィードバックする場合の一例を示している。CB#0は、第2の優先度(low)又はeMBBに対応し、CB#1は、第1の優先度(high)又はURLLCに対応している。 The UE generates a HARQ-ACK codebook (for example, HARQ-ACK in the HARQ-ACK codebook) based on the value of the priority notification field (for example, Priority Indicator field) included in the DCI corresponding to each PDSCH. Bit generation) may be controlled. FIG. 5 shows an example of generating / feeding back two HARQ-ACK codebooks (here, CB # 0 and CB # 1) corresponding to different priorities in slot # n. CB # 0 corresponds to a second priority (low) or eMBB, and CB # 1 corresponds to a first priority (high) or URLLC.
 図5において、スロット#n-5で送信されるPDSCHに対応するDCIにより、HARQ-ACKのフィードバックタイミングがスロット#nであること(K1=5)、第2の優先度(low)であること、が通知される。スロット#n-3で送信されるPDSCHに対応するDCIにより、HARQ-ACKのフィードバックタイミングがスロット#nであること(K1=3)、第2の優先度(low)であること、が通知される。 In FIG. 5, the feedback timing of HARQ-ACK is slot # n (K1 = 5) and the second priority (low) due to the DCI corresponding to the PDSCH transmitted in slot # n-5. , Will be notified. The DCI corresponding to the PDSCH transmitted in slot # n-3 notifies that the feedback timing of HARQ-ACK is slot # n (K1 = 3) and the second priority (low). To.
 図5において、スロット#n-2(サブスロット#n-4、#n-5)で送信されるPDSCHに対応するDCIにより、HARQ-ACKのフィードバックタイミングがスロット#n(サブスロット#n)であること(K1=5サブスロット)、第1の優先度(high)であること、が通知される。 In FIG. 5, the feedback timing of HARQ-ACK is set to slot # n (subslot #n) by the DCI corresponding to the PDSCH transmitted in slot # n-2 (subslots # n-4, # n-5). It is notified that there is (K1 = 5 subslots) and that it is the first priority (high).
 この場合、UEは、スロット#nにおいて、2個のHARQ-ACKコードブック(CB#0とCB#1)を生成してフィードバックしてもよい。 In this case, the UE may generate and feed back two HARQ-ACK codebooks (CB # 0 and CB # 1) in slot # n.
 一方で、CB#0用のULリソース(例えば、PUCCH/PUSCH)と、CB#1用のULリソースがオーバーラップする場合、HARQ-ACK(又は、CB)に対応する優先度に基づいてHARQ-ACKの送信を制御してもよい。 On the other hand, when the UL resource for CB # 0 (for example, PUCCH / PUSCH) and the UL resource for CB # 1 overlap, HARQ- is based on the priority corresponding to HARQ-ACK (or CB). You may control the transmission of ACK.
 しかし、上述したように、複数のHARQ-ACKをまとめてフィードバックする場合(例えば、1ショットHARQ-ACKフィードバック、又はPDSCHグループに基づくHARQ-ACKフィードバックを行う場合)、複数のHARQ-ACKが各コードブックに含まれるケースが考えられる。かかる場合、UL送信の優先度をどのように適用/制御するかが問題となる。 However, as described above, when multiple HARQ-ACKs are fed back together (for example, when performing one-shot HARQ-ACK feedback or HARQ-ACK feedback based on a PDSCH group), multiple HARQ-ACKs are used for each code. It may be included in the book. In such a case, how to apply / control the priority of UL transmission becomes a problem.
 例えば、1ショットHARQ-ACKフィードバックを適用する場合、当該1ショットHARQ-ACKフィードバックに含まれる各HARQ-ACKの優先度、又は1ショットHARQ-ACKフィードバック(又は、1ショットHARQ-ACKフィードバックに利用するコードブック)に対応する優先度をどのように設定/適用するかが問題となる。 For example, when applying 1-shot HARQ-ACK feedback, it is used for the priority of each HARQ-ACK included in the 1-shot HARQ-ACK feedback, or for 1-shot HARQ-ACK feedback (or 1-shot HARQ-ACK feedback). The problem is how to set / apply the priority corresponding to the codebook).
 あるいは、PDSCHグループ単位でHARQ-ACKのフィードバックを行う場合、PDSCHグループに含まれる各HARQ-ACKの優先度、又はPDSCHグループに対応するHARQ-ACK(又は、当該HARQ-ACKのコードブック)に対応する優先度をどのように設定/適用するかが問題となる。 Alternatively, when feedback of HARQ-ACK is given for each PDSCH group, the priority of each HARQ-ACK included in the PDSCH group or the HARQ-ACK corresponding to the PDSCH group (or the codebook of the HARQ-ACK) is supported. The problem is how to set / apply the priority to be applied.
 本発明者らは、本実施の形態の一態様として、1ショットHARQ-ACKフィードバック要求に対してフィードバックするHARQ-ACK(又は、HARQ-ACKコードブック)に対する優先度、又は当該HARQ-ACKコードブックに含めるHARQ-ACKの優先度について検討し、本実施の形態の一態様を着想した。 As one aspect of the present embodiment, the present inventors have a priority over HARQ-ACK (or HARQ-ACK codebook) that feeds back in response to a one-shot HARQ-ACK feedback request, or the HARQ-ACK codebook. The priority of HARQ-ACK to be included in the above was examined, and one aspect of the present embodiment was conceived.
 また、本発明者らは、本実施の形態の他の態様として、所定グループ(例えば、PDSCHグループ)単位に基づいてフィードバックを行うHARQ-ACK(又は、HARQ-ACKコードブック)に対する優先度、又はPDSCHグループに対応する各HARQ-ACKの優先度について検討し、本実施の形態の他の態様を着想した。 Further, as another aspect of the present embodiment, the present inventors have a priority on HARQ-ACK (or HARQ-ACK codebook) that provides feedback based on a predetermined group (for example, PDSCH group) unit, or The priority of each HARQ-ACK corresponding to the PDSCH group was examined, and another aspect of this embodiment was conceived.
 以下、本開示に係る実施形態について、図面を参照して詳細に説明する。各実施の態様で説明する構成は、それぞれ単独で適用されてもよいし、組み合わせて適用されてもよい。 Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. The configurations described in each embodiment may be applied individually or in combination.
 また、本開示において、「A/B」は、A及びBの少なくとも一つ、「A/B/C」は、A、B及びCの少なくとも一つと読み替えられてもよい。 Further, in the present disclosure, "A / B" may be read as at least one of A and B, and "A / B / C" may be read as at least one of A, B and C.
 また、本開示は、NR-Uを適用する無線通信システムだけでなく、NR-Uを適用しない無線通信システムに適用することも可能である。 Further, the present disclosure can be applied not only to a wireless communication system to which NR-U is applied, but also to a wireless communication system to which NR-U is not applied.
 以下の説明では、UL送信の優先度として、第1の優先度(high)と第2の優先度(low)の2レベルを例に挙げて説明するが、優先度は2レベルに限られない。3レベル以上の優先度が設定されてもよい。また、以下の説明において、HARQ-ACKコードブックの優先度(又は、HARQ-ACKの優先度)は、HARQ-ACK送信に利用されるPUCCHの優先度、又はHARQ-ACK送信に利用されるPUSCHの優先度に読み替えられてもよい。 In the following description, two levels of the first priority (high) and the second priority (low) will be described as examples of the priority of UL transmission, but the priority is not limited to the two levels. .. Three or more levels of priority may be set. Further, in the following description, the priority of the HARQ-ACK codebook (or the priority of HARQ-ACK) is the priority of PUCCH used for HARQ-ACK transmission or PUSCH used for HARQ-ACK transmission. It may be read as the priority of.
(第1の態様)
 第1の態様では、1ショットHARQ-ACKの要求に基づいてHARQ-ACKフィードバックを行う場合のUL送信の優先度の設定/制御について説明する。
(First aspect)
In the first aspect, setting / control of the priority of UL transmission when performing HARQ-ACK feedback based on the request of 1-shot HARQ-ACK will be described.
 UEは、DCIに含まれる1ショットHARQ-ACK要求フィールドに基づいて、1又は複数のHARQ-ACKを所定リソースでフィードバックするように制御してもよい(図6参照)。図6は、PDSCH#3をスケジュールするDCI#3に含まれる1ショットHARQ-ACK要求に基づいて、PDSCH#1に対応するHARQ-ACK#1、PDSCH#2に対応するHARQ-ACK#2、PDSCH#3に対応するHARQ-ACK#3を所定のULリソースを利用してフィードバックする場合を示している。 The UE may control one or more HARQ-ACKs to be fed back with a predetermined resource based on the one-shot HARQ-ACK request field included in the DCI (see FIG. 6). FIG. 6 shows HARQ-ACK # 1 corresponding to PDSCH # 1 and HARQ-ACK # 2 corresponding to PDSCH # 2 based on the one-shot HARQ-ACK request included in DCI # 3 that schedules PDSCH # 3. The case where HARQ-ACK # 3 corresponding to PDSCH # 3 is fed back by using a predetermined UL resource is shown.
 以下の説明において、DCIは、PDCCHに読み替えられてもよい。ULリソースは、HARQ-ACKコードブック、PUCCHリソース、又はPUSCHリソースに読み替えられてもよい。 In the following description, DCI may be read as PDCCH. The UL resource may be read as a HARQ-ACK codebook, a PUCCH resource, or a PUSCH resource.
 1ショットHARQ-ACK要求に基づいてフィードバックするHARQ-ACK(又は、HARQ-ACKコードブック)の優先度は、所定条件に基づいて決定されてもよい。 The priority of HARQ-ACK (or HARQ-ACK codebook) to be fed back based on the one-shot HARQ-ACK request may be determined based on predetermined conditions.
 UEは、1ショットHARQ-ACK要求に基づいてフィードバックするHARQ-ACKの優先度を、当該1ショットHARQ-ACK要求フィールドが含まれるDCI(図6のDCI#3)に基づいて判断してもよい。例えば、UEは、当該DCIに含まれる優先度指示フィールド(例えば、Priority Indicator field)に基づいて1ショットHARQ-ACKに対する優先度を決定してもよい(オプション1-1)。あるいは、UEは、当該DCIに適用される構成/パラメータ(例えば、DCIフォーマット)に基づいて1ショットHARQ-ACKに対する優先度を決定してもよい(オプション1-2)。 The UE may determine the priority of HARQ-ACK to be fed back based on the 1-shot HARQ-ACK request based on the DCI (DCI # 3 in FIG. 6) including the 1-shot HARQ-ACK request field. .. For example, the UE may determine the priority for the one-shot HARQ-ACK based on the priority indicator field (for example, Priority Indicator field) included in the DCI (option 1-1). Alternatively, the UE may determine the priority for 1-shot HARQ-ACK based on the configuration / parameters applied to the DCI (eg, DCI format) (option 1-2).
<オプション1-1>
 UEは、1ショットHARQ-ACK要求を指示するDCIに含まれる優先度指示フィールドに基づいて、1ショットHARQ-ACKで送信するHARQ-ACKコードブックの優先度を決定してもよい。当該DCIに含まれる優先度指示フィールドにより第1の優先度(high)又は第2の優先度(low)が設定されてもよい。なお、優先度は2レベルに限られず、3レベル以上のいずれかが通知されてもよい。
<Option 1-1>
The UE may determine the priority of the HARQ-ACK codebook transmitted by the 1-shot HARQ-ACK based on the priority instruction field included in the DCI indicating the 1-shot HARQ-ACK request. A first priority (high) or a second priority (low) may be set by the priority indicating field included in the DCI. The priority is not limited to 2 levels, and any of 3 levels or higher may be notified.
 UEは、1ショットHARQ-ACK要求に基づいて所定リソースを利用して複数のHARQ-ACKをフィードバックする場合、優先度が異なる複数のHARQ-ACKをまとめてフィードバックするように制御してもよい(オプション1-1-1)。あるいは、UEは、1ショットHARQ-ACK要求に基づいて所定リソースを利用して複数のHARQ-ACKをフィードバックする場合、特定の優先度のHARQ-ACKを選択してフィードバックするように制御してもよい(オプション1-1-2)。 When a plurality of HARQ-ACKs are fed back by using a predetermined resource based on a one-shot HARQ-ACK request, the UE may control to feed back a plurality of HARQ-ACKs having different priorities at once ( Option 1-1-1). Alternatively, when the UE feeds back a plurality of HARQ-ACKs using a predetermined resource based on the one-shot HARQ-ACK request, the UE may control to select and feed back the HARQ-ACK of a specific priority. Good (option 1-1-2).
<オプション1-1-1>
 UEは、1ショットHARQ-ACKフィードバックが指示された場合、優先度に関わらず対象となる1以上のHARQ-ACK(例えば、図3におけるHARQ-ACK#1、#2、#3)をフィードバックするように制御してもよい。
<Option 1-1-1>
When the one-shot HARQ-ACK feedback is instructed, the UE feeds back one or more target HARQ-ACKs (for example, HARQ-ACK # 1, # 2, # 3 in FIG. 3) regardless of the priority. It may be controlled as follows.
 1ショットHARQ-ACKフィードバックの対象となるHARQ-ACKとして、第1の優先度(high)の第1のHARQ-ACKと、第2の優先度(low)の第2のHARQ-ACKが含まれる場合を想定する。かかる場合、UEは、第1のHARQ-ACKと第2のHARQ-ACKをまとめて(例えば、同じHARQ-ACKコードブックに含めて)送信するように制御してもよい。 The HARQ-ACK to be fed back includes a first HARQ-ACK with a first priority (high) and a second HARQ-ACK with a second priority (low). Imagine a case. In such a case, the UE may control the first HARQ-ACK and the second HARQ-ACK to be transmitted together (for example, included in the same HARQ-ACK codebook).
 UEは、1ショットHARQ-ACK要求を指示するDCIにより第1の優先度(high)が指示される場合、第1の優先度(high)のHARQ-ACK及び第2の優先度(low)のHARQ-ACKの少なくとも一つをHARQ-ACKコードブックに含めてフィードバックするように制御してもよい。この場合、1ショットHARQ-ACK要求に応じてフィードバックするHARQ-ACKコードブックの優先度として、第1の優先度(high)が設定されてもよい。 When the first priority (high) is indicated by the DCI instructing the one-shot HARQ-ACK request, the UE is of the first priority (high) HARQ-ACK and the second priority (low). At least one of HARQ-ACK may be included in the HARQ-ACK codebook and controlled to be fed back. In this case, the first priority (high) may be set as the priority of the HARQ-ACK codebook to be fed back in response to the one-shot HARQ-ACK request.
 UEは、1ショットHARQ-ACK要求を指示するDCIにより第2の優先度(low)が指示される場合、第1の優先度(high)のHARQ-ACK及び第2の優先度(low)のHARQ-ACKの少なくとも一つをHARQ-ACKコードブックに含めてフィードバックするように制御してもよい。この場合、1ショットHARQ-ACK要求に応じてフィードバックするHARQ-ACKコードブックの優先度として、第2の優先度(low)が設定されてもよい。 The UE is of the first priority (high) HARQ-ACK and the second priority (low) when the second priority (low) is indicated by the DCI instructing the one-shot HARQ-ACK request. At least one of HARQ-ACK may be included in the HARQ-ACK codebook and controlled to be fed back. In this case, a second priority (low) may be set as the priority of the HARQ-ACK codebook to be fed back in response to the one-shot HARQ-ACK request.
 このように、1ショットHARQ-ACKフィードバックの対象となるHARQ-ACKを優先度に関わらず選択することにより、1回の送信でより多くのHARQ-ACKをフィードバックすることができる。なお、1ショットHARQ-ACKフィードバックの対象となる各HARQ-ACKの優先度は、各HARQ-ACKに対応するPDSCHをスケジュールするDCIに基づいて決定してもよい。 In this way, by selecting the HARQ-ACK to be the target of the one-shot HARQ-ACK feedback regardless of the priority, it is possible to feed back more HARQ-ACK in one transmission. The priority of each HARQ-ACK subject to the one-shot HARQ-ACK feedback may be determined based on the DCI that schedules the PDSCH corresponding to each HARQ-ACK.
 あるいは、1ショットHARQ-ACK要求を指示するDCIに含まれる優先度指示フィールドで指示された優先度の値(例えば、i)に基づいて、1ショットHARQ-ACKフィードバックに含めるHARQ-ACKが決定されてもよい。例えば、1ショットHARQ-ACK要求を指示するDCIに含まれる優先度指示フィールドの値(例えば、i)以上の優先度を有するHARQ-ACKを選択して、1ショットHARQ-ACKとしてフィードバックしてもよい。 Alternatively, the HARQ-ACK to be included in the 1-shot HARQ-ACK feedback is determined based on the priority value (eg i) specified in the priority indicator field included in the DCI that directs the 1-shot HARQ-ACK request. You may. For example, even if HARQ-ACK having a priority equal to or higher than the value of the priority indicating field (for example, i) included in the DCI for instructing the one-shot HARQ-ACK request is selected and fed back as one-shot HARQ-ACK. good.
 優先度が高い順に1、2、3、4(4レベル)で設定され、優先度指示フィールドで2が指示される場合を想定する。DCIに含まれる優先度指示フィールドで2が指定される場合、UEは、優先度が2以上(例えば、1、2)の優先度を有するHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを適用してもよい。これにより、特定の優先度のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを適用することができる。 It is assumed that 1, 2, 3, 4 (4 levels) are set in descending order of priority, and 2 is specified in the priority instruction field. If 2 is specified in the priority indicator field contained in the DCI, the UE selects HARQ-ACK with a priority of 2 or higher (eg, 1 or 2) and 1-shot HARQ-ACK feedback. May be applied. This allows one-shot HARQ-ACK feedback to be applied by selecting a particular priority HARQ-ACK.
<オプション1-1-2>
 UEは、1ショットHARQ-ACKフィードバックが指示された場合、特定の優先度のHARQ-ACKを選択してフィードバックするように制御してもよい。
<Option 1-1-2>
When the one-shot HARQ-ACK feedback is instructed, the UE may control to select and feed back the HARQ-ACK of a specific priority.
 例えば、1ショットHARQ-ACKフィードバックの対象となるHARQ-ACKとして、第1の優先度(high)の第1のHARQ-ACKと、第2の優先度(low)の第2のHARQ-ACKが含まれる場合を想定する。かかる場合、UEは、いずれか一方の優先度(第1の優先度又は第2の優先度)を有するHARQ-ACKをまとめて(例えば、同じHARQ-ACKコードブックに含めて)送信するように制御してもよい。この場合、他の優先度を有するHARQ-ACKに対して1ショットHARQ-ACKフィードバックが適用されなくてもよい。 For example, as HARQ-ACK to be the target of 1-shot HARQ-ACK feedback, a first HARQ-ACK having a first priority (high) and a second HARQ-ACK having a second priority (low) are used. It is assumed that it is included. In such a case, the UE should send the HARQ-ACKs having either priority (first priority or second priority) together (for example, included in the same HARQ-ACK codebook). You may control it. In this case, the one-shot HARQ-ACK feedback may not be applied to the HARQ-ACK having another priority.
 例えば、第1の優先度(high)を有するHARQ-ACKに対して1ショットHARQ-ACKフィードバックを適用してもよい。UEは、1ショットHARQ-ACK要求が指示された場合、第1の優先度(high)を有する1以上のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを行ってもよい。なお、1ショットHARQ-ACKフィードバックの対象となる各HARQ-ACKの優先度は、各HARQ-ACKに対応するPDSCHをスケジュールするDCIに基づいて決定してもよい。 For example, 1-shot HARQ-ACK feedback may be applied to HARQ-ACK having the first priority (high). When a one-shot HARQ-ACK request is instructed, the UE may select one or more HARQ-ACKs having a first priority (high) to provide one-shot HARQ-ACK feedback. The priority of each HARQ-ACK subject to the one-shot HARQ-ACK feedback may be determined based on the DCI that schedules the PDSCH corresponding to each HARQ-ACK.
 第1の優先度のHARQ-ACKに対して1ショットHARQ-ACKフィードバックを適用する場合、フィードバックするHARQ-ACKコードブックは、第1の優先度が設定されてもよい。この場合、1ショットHARQ-ACKフィードバックを指示するDCIに優先度指示フィールドが含まれない構成としてよい。UEは、DCIに優先度指示フィールドが含まれる場合、1ショットHARQ-ACKフィードバックが指示されることを想定/期待しなくてもよい。 When applying the one-shot HARQ-ACK feedback to the first priority HARQ-ACK, the first priority may be set for the HARQ-ACK codebook to be fed back. In this case, the DCI for instructing the one-shot HARQ-ACK feedback may not include the priority instruction field. The UE may not expect / expect that one-shot HARQ-ACK feedback is indicated if the DCI includes a priority indicator field.
 あるいは、第2の優先度(low)を有するHARQ-ACKに対して1ショットHARQ-ACKフィードバックを適用してもよい。UEは、1ショットHARQ-ACK要求が指示された場合、第2の優先度(low)を有する1以上のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを行ってもよい。 Alternatively, 1-shot HARQ-ACK feedback may be applied to HARQ-ACK having a second priority (low). When a one-shot HARQ-ACK request is instructed, the UE may select one or more HARQ-ACKs having a second priority (low) to provide one-shot HARQ-ACK feedback.
 第2の優先度のHARQ-ACKに対して1ショットHARQ-ACKフィードバックを適用する場合、フィードバックするHARQ-ACKコードブックは、第2の優先度が設定されてもよい。この場合、1ショットHARQ-ACKフィードバックを指示するDCIに優先度指示フィールドが含まれない構成としてよい。UEは、DCIに優先度指示フィールドが含まれる場合、1ショットHARQ-ACKフィードバックが指示されることを想定/期待しなくてもよい。 When applying the 1-shot HARQ-ACK feedback to the HARQ-ACK of the second priority, the HARQ-ACK codebook to be fed back may be set to the second priority. In this case, the DCI for instructing the one-shot HARQ-ACK feedback may not include the priority instruction field. The UE may not expect / expect that one-shot HARQ-ACK feedback is indicated if the DCI includes a priority indicator field.
 あるいは、1ショットHARQ-ACKフィードバックを適用するHARQ-ACKの優先度を上位レイヤシグナリング/DCIを利用してUEに通知/設定してもよい。 Alternatively, the priority of HARQ-ACK to which the one-shot HARQ-ACK feedback is applied may be notified / set to the UE by using the upper layer signaling / DCI.
 1ショットHARQ-ACKフィードバックを適用するHARQ-ACKの優先度を上位レイヤシグナリングでUEに通知する場合、通知された優先度を1ショットHARQ-ACKフィードバックに利用するHARQ-ACKコードブックに適用すればよい。この場合、1ショットHARQ-ACKフィードバックを指示するDCIに優先度指示フィールドが含まれない構成としてよい。UEは、DCIに優先度指示フィールドが含まれる場合、1ショットHARQ-ACKフィードバックが指示されることを想定/期待しなくてもよい。 Applying 1-shot HARQ-ACK feedback When notifying the UE of the priority of HARQ-ACK by higher layer signaling, if the notified priority is applied to the HARQ-ACK codebook used for 1-shot HARQ-ACK feedback. good. In this case, the DCI for instructing the one-shot HARQ-ACK feedback may not include the priority instruction field. The UE may not expect / expect that one-shot HARQ-ACK feedback is indicated if the DCI includes a priority indicator field.
 UEは、1ショットHARQ-ACK要求を指示するDCIに含まれる所定フィールド(例えば、優先度指示フィールド)に基づいて、1ショットHARQ-ACKフィードバックを適用するHARQ-ACKを判断してもよい。1ショットHARQ-ACK要求を指示するDCIにより第1の優先度(high)が指示される場合、UEは、第1の優先度(high)を有する1以上のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを行ってもよい。また、1ショットHARQ-ACKに利用するHARQ-ACKコードブック(又は、PUCCH/PUSCH)は、第1の優先度が設定されてもよい。 The UE may determine the HARQ-ACK to which the 1-shot HARQ-ACK feedback is applied based on a predetermined field (for example, a priority instruction field) included in the DCI that instructs the 1-shot HARQ-ACK request. If the DCI indicating the one-shot HARQ-ACK request indicates a first priority (high), the UE selects one or more HARQ-ACKs with the first priority (high) and 1 Shot HARQ-ACK feedback may be given. Further, the HARQ-ACK codebook (or PUCCH / PUSCH) used for the one-shot HARQ-ACK may have a first priority set.
 あるいは、1ショットHARQ-ACK要求を指示するDCIにより第2の優先度(low)が指示される場合、UEは、第2の優先度(low)を有する1以上のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを行ってもよい。また、1ショットHARQ-ACKに利用するHARQ-ACKコードブック(又は、PUCCH/PUSCH)は、第2の優先度が設定されてもよい。 Alternatively, if the DCI indicating the one-shot HARQ-ACK request indicates a second priority (low), the UE selects one or more HARQ-ACKs with the second priority (low). One-shot HARQ-ACK feedback may be given. Further, the HARQ-ACK codebook (or PUCCH / PUSCH) used for the one-shot HARQ-ACK may have a second priority set.
 このように、1ショットHARQ-ACKフィードバックの対象となるHARQ-ACKを優先度に基づいて選択することにより、当該優先度に基づいて1ショットHARQ-ACKフィードバックを柔軟に制御することができる。 In this way, by selecting the HARQ-ACK to be the target of the 1-shot HARQ-ACK feedback based on the priority, the 1-shot HARQ-ACK feedback can be flexibly controlled based on the priority.
<オプション1-2>
 UEは、1ショットHARQ-ACK要求を指示するDCIのフォーマットに基づいて、1ショットHARQ-ACKに対する優先度を決定してもよい。DCIフォーマットに基づいて第1の優先度(high)又は第2の優先度(low)が設定されてもよい。なお、優先度は2レベルに限られず、3レベル以上のいずれかが通知されてもよい。以下の説明では、第1のDCIフォーマット(例えば、DCIフォーマット1_2)が第1の優先度(high)に対応し、第2のDCIフォーマット(例えば、DCIフォーマット1_1)が第2の優先度(low)に対応する場合を例に挙げるが、これに限られない。
<Option 1-2>
The UE may determine the priority for the 1-shot HARQ-ACK based on the format of the DCI indicating the 1-shot HARQ-ACK request. A first priority (high) or a second priority (low) may be set based on the DCI format. The priority is not limited to 2 levels, and any of 3 levels or higher may be notified. In the following description, the first DCI format (eg DCI format 1_2) corresponds to the first priority (high) and the second DCI format (eg DCI format 1_1) corresponds to the second priority (low). ) Is taken as an example, but it is not limited to this.
 UEは、1ショットHARQ-ACK要求に基づいて所定リソースを利用して複数のHARQ-ACKをフィードバックする場合、優先度が異なる複数のHARQ-ACKをまとめてフィードバックするように制御してもよい(オプション1-2-1)。あるいは、UEは、1ショットHARQ-ACK要求に基づいて所定リソースを利用して複数のHARQ-ACKをフィードバックする場合、特定の優先度のHARQ-ACKを選択してフィードバックするように制御してもよい(オプション1-2-2)。 When a plurality of HARQ-ACKs are fed back by using a predetermined resource based on a one-shot HARQ-ACK request, the UE may control to feed back a plurality of HARQ-ACKs having different priorities at once ( Option 1-2-1). Alternatively, when the UE feeds back a plurality of HARQ-ACKs using a predetermined resource based on the one-shot HARQ-ACK request, the UE may control to select and feed back the HARQ-ACK of a specific priority. Good (option 1-2-2).
<オプション1-2-1>
 UEは、1ショットHARQ-ACKフィードバックが指示された場合、優先度に関わらず対象となる1以上のHARQ-ACK(例えば、図3におけるHARQ-ACK#1、#2、#3)をフィードバックするように制御してもよい。
<Option 1-2-1>
When the one-shot HARQ-ACK feedback is instructed, the UE feeds back one or more target HARQ-ACKs (for example, HARQ-ACK # 1, # 2, # 3 in FIG. 3) regardless of the priority. It may be controlled as follows.
 例えば、1ショットHARQ-ACKフィードバックの対象となるHARQ-ACKとして、第1の優先度(high)の第1のHARQ-ACKと、第2の優先度(low)の第2のHARQ-ACKが含まれる場合を想定する。かかる場合、UEは、第1のHARQ-ACKと第2のHARQ-ACKをまとめて(例えば、同じHARQ-ACKコードブックに含めて)送信するように制御してもよい。 For example, as HARQ-ACK to be the target of 1-shot HARQ-ACK feedback, a first HARQ-ACK having a first priority (high) and a second HARQ-ACK having a second priority (low) are used. It is assumed that it is included. In such a case, the UE may control the first HARQ-ACK and the second HARQ-ACK to be transmitted together (for example, included in the same HARQ-ACK codebook).
 UEは、1ショットHARQ-ACK要求を指示するDCIフォーマット(例えば、DCIフォーマット1_2)により第1の優先度(high)が指示される場合、第1の優先度(high)のHARQ-ACK及び第2の優先度(low)のHARQ-ACKの少なくとも一つをHARQ-ACKコードブックに含めてフィードバックするように制御してもよい。この場合、1ショットHARQ-ACK要求に応じてフィードバックするHARQ-ACKコードブック)の優先度として、第1の優先度(high)が設定されてもよい。 When the first priority (high) is specified by the DCI format (for example, DCI format 1_2) instructing the one-shot HARQ-ACK request, the UE has the first priority (high) HARQ-ACK and the first. At least one of the 2 low priority HARQ-ACKs may be included in the HARQ-ACK codebook and controlled to be fed back. In this case, the first priority (high) may be set as the priority of the HARQ-ACK codebook) that feeds back in response to the one-shot HARQ-ACK request.
 UEは、1ショットHARQ-ACK要求を指示するDCIフォーマット(例えば、DCIフォーマット1_1)により第2の優先度(low)が指示される場合、第1の優先度(high)のHARQ-ACK及び第2の優先度(low)のHARQ-ACKの少なくとも一つをHARQ-ACKコードブックに含めてフィードバックするように制御してもよい。この場合、1ショットHARQ-ACK要求に応じてフィードバックするHARQ-ACKコードブックの優先度として、第2の優先度(low)が設定されてもよい。 If the second priority (low) is indicated by the DCI format (eg, DCI format 1-11) instructing the one-shot HARQ-ACK request, the UE has a first priority (high) HARQ-ACK and a second. At least one of the 2 low priority HARQ-ACKs may be included in the HARQ-ACK codebook and controlled to be fed back. In this case, a second priority (low) may be set as the priority of the HARQ-ACK codebook to be fed back in response to the one-shot HARQ-ACK request.
 このように、1ショットHARQ-ACKフィードバックの対象となるHARQ-ACKを優先度に関わらず選択することにより、1回の送信でより多くのHARQ-ACKをフィードバックすることができる。なお、1ショットHARQ-ACKフィードバックの対象となる各HARQ-ACKの優先度は、各HARQ-ACKに対応するPDSCHをスケジュールするDCI(例えば、DCIフォーマット)に基づいて決定してもよい。 In this way, by selecting the HARQ-ACK to be the target of the one-shot HARQ-ACK feedback regardless of the priority, it is possible to feed back more HARQ-ACK in one transmission. The priority of each HARQ-ACK subject to the one-shot HARQ-ACK feedback may be determined based on the DCI (for example, DCI format) that schedules the PDSCH corresponding to each HARQ-ACK.
 あるいは、1ショットHARQ-ACK要求を指示するDCIフォーマット基づいて決定される優先度の値(例えば、i)に基づいて、1ショットHARQ-ACKフィードバックに含めるHARQ-ACKが決定されてもよい。例えば、1ショットHARQ-ACK要求を指示するDCIフォーマットに基づいて決定される優先度の値(例えば、i)以上の優先度を有するHARQ-ACKを選択して、1ショットHARQ-ACKとしてフィードバックしてもよい。 Alternatively, the HARQ-ACK to be included in the 1-shot HARQ-ACK feedback may be determined based on the priority value (eg, i) determined based on the DCI format indicating the 1-shot HARQ-ACK request. For example, a HARQ-ACK having a priority value equal to or higher than the priority value (for example, i) determined based on the DCI format indicating the 1-shot HARQ-ACK request is selected and fed back as a 1-shot HARQ-ACK. You may.
 優先度が高い順に1、2、3、4(4レベル)で設定され、DCIフォーマットにより2が指示される場合を想定する。DCIフォーマットにより2が指定される場合、UEは、優先度が2以上(例えば、1、2)の優先度を有するHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを適用してもよい。これにより、特定の優先度のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを適用することができる。 It is assumed that 1, 2, 3, 4 (4 levels) are set in descending order of priority, and 2 is indicated by the DCI format. If 2 is specified by the DCI format, the UE may select HARQ-ACK with a priority of 2 or higher (eg, 1 or 2) and apply 1-shot HARQ-ACK feedback. .. This allows one-shot HARQ-ACK feedback to be applied by selecting a particular priority HARQ-ACK.
<オプション1-1-2>
 UEは、1ショットHARQ-ACKフィードバックが指示された場合、特定の優先度のHARQ-ACKを選択してフィードバックするように制御してもよい。
<Option 1-1-2>
When the one-shot HARQ-ACK feedback is instructed, the UE may control to select and feed back the HARQ-ACK of a specific priority.
 例えば、1ショットHARQ-ACKフィードバックの対象となるHARQ-ACKとして、第1の優先度(high)の第1のHARQ-ACKと、第2の優先度(low)の第2のHARQ-ACKが含まれる場合を想定する。かかる場合、UEは、いずれか一方の優先度(第1の優先度又は第2の優先度)を有するHARQ-ACKをまとめて(例えば、同じHARQ-ACKコードブックに含めて)送信するように制御してもよい。この場合、他の優先度を有するHARQ-ACKに対して1ショットHARQ-ACKフィードバックが適用されなくてもよい。 For example, as HARQ-ACK to be the target of 1-shot HARQ-ACK feedback, a first HARQ-ACK having a first priority (high) and a second HARQ-ACK having a second priority (low) are used. It is assumed that it is included. In such a case, the UE should send the HARQ-ACKs having either priority (first priority or second priority) together (for example, included in the same HARQ-ACK codebook). You may control it. In this case, the one-shot HARQ-ACK feedback may not be applied to the HARQ-ACK having another priority.
 例えば、第1の優先度(high)を有するHARQ-ACKに対して1ショットHARQ-ACKフィードバックを適用してもよい。UEは、1ショットHARQ-ACK要求が指示された場合、第1の優先度(high)を有する1以上のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを行ってもよい。なお、1ショットHARQ-ACKフィードバックの対象となる各HARQ-ACKの優先度は、各HARQ-ACKに対応するPDSCHをスケジュールするDCIフォーマットに基づいて決定してもよい。 For example, 1-shot HARQ-ACK feedback may be applied to HARQ-ACK having the first priority (high). When a one-shot HARQ-ACK request is instructed, the UE may select one or more HARQ-ACKs having a first priority (high) to provide one-shot HARQ-ACK feedback. The priority of each HARQ-ACK subject to the one-shot HARQ-ACK feedback may be determined based on the DCI format that schedules the PDSCH corresponding to each HARQ-ACK.
 第1の優先度のHARQ-ACKに対して1ショットHARQ-ACKフィードバックを適用する場合、フィードバックするHARQ-ACKコードブックは、第1の優先度が設定されてもよい。 When applying the one-shot HARQ-ACK feedback to the first priority HARQ-ACK, the first priority may be set for the HARQ-ACK codebook to be fed back.
 あるいは、第2の優先度(low)を有するHARQ-ACKに対して1ショットHARQ-ACKフィードバックを適用してもよい。UEは、1ショットHARQ-ACK要求が指示された場合、第2の優先度(low)を有する1以上のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを行ってもよい。 Alternatively, 1-shot HARQ-ACK feedback may be applied to HARQ-ACK having a second priority (low). When a one-shot HARQ-ACK request is instructed, the UE may select one or more HARQ-ACKs having a second priority (low) to provide one-shot HARQ-ACK feedback.
 第2の優先度のHARQ-ACKに対して1ショットHARQ-ACKフィードバックを適用する場合、フィードバックするHARQ-ACKコードブックは、第2の優先度が設定されてもよい。 When applying the 1-shot HARQ-ACK feedback to the HARQ-ACK of the second priority, the HARQ-ACK codebook to be fed back may be set to the second priority.
 あるいは、1ショットHARQ-ACKフィードバックを適用するHARQ-ACKの優先度を上位レイヤシグナリング/DCIを利用してUEに通知/設定してもよい。 Alternatively, the priority of HARQ-ACK to which the one-shot HARQ-ACK feedback is applied may be notified / set to the UE by using the upper layer signaling / DCI.
 1ショットHARQ-ACKフィードバックを適用するHARQ-ACKの優先度を上位レイヤシグナリングでUEに通知する場合、通知された優先度を1ショットHARQ-ACKに利用するHARQ-ACKコードブックに適用してもよい。この場合、1ショットHARQ-ACKフィードバックを指示するDCIフォーマットは、第1のDCIフォーマット及び第2のDCIフォーマットの少なくとも一つを利用してもよい。 When notifying the UE of the priority of HARQ-ACK to which 1-shot HARQ-ACK feedback is applied by higher layer signaling, even if the notified priority is applied to the HARQ-ACK codebook used for 1-shot HARQ-ACK. good. In this case, the DCI format for instructing the one-shot HARQ-ACK feedback may utilize at least one of the first DCI format and the second DCI format.
 UEは、1ショットHARQ-ACK要求を指示するDCIのフォーマットに基づいて、1ショットHARQ-ACKフィードバックを適用するHARQ-ACKを判断してもよい。1ショットHARQ-ACK要求を指示するDCIフォーマット(例えば、DCIフォーマット1_2)により第1の優先度(high)が指示される場合、UEは、第1の優先度(high)を有する1以上のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを行ってもよい。また、1ショットHARQ-ACKに利用するHARQ-ACKコードブックは、第1の優先度が設定されてもよい。 The UE may determine the HARQ-ACK to which the 1-shot HARQ-ACK feedback is applied based on the DCI format instructing the 1-shot HARQ-ACK request. If a first priority (high) is indicated by a DCI format (eg, DCI format 1_2) instructing a one-shot HARQ-ACK request, the UE has one or more HARQs with the first priority (high). -ACK may be selected to provide 1-shot HARQ-ACK feedback. Further, the HARQ-ACK codebook used for the one-shot HARQ-ACK may have a first priority set.
 あるいは、1ショットHARQ-ACK要求を指示するDCIフォーマット(例えば、DCIフォーマット1_1)により第2の優先度(low)が指示される場合、UEは、第2の優先度(low)を有する1以上のHARQ-ACKを選択して、1ショットHARQ-ACKフィードバックを行ってもよい。また、1ショットHARQ-ACKに利用するHARQ-ACKコードブックは、第2の優先度が設定されてもよい。 Alternatively, if a second priority (low) is indicated by a DCI format (eg, DCI format 1-11) instructing a one-shot HARQ-ACK request, the UE is one or more with the second priority (low). HARQ-ACK may be selected to provide one-shot HARQ-ACK feedback. Further, the HARQ-ACK codebook used for the one-shot HARQ-ACK may have a second priority set.
 このように、1ショットHARQ-ACKフィードバックの対象となるHARQ-ACKを優先度に基づいて選択することにより、当該優先度に基づいて1ショットHARQ-ACKフィードバックを柔軟に制御することができる。 In this way, by selecting the HARQ-ACK to be the target of the 1-shot HARQ-ACK feedback based on the priority, the 1-shot HARQ-ACK feedback can be flexibly controlled based on the priority.
<バリエーション>
 1ショットHARQ-ACKフィードバックの優先度は、上記オプション1-1又はオプション1-2のいずれかを利用して決定してもよい。この場合、オプション1-1とオプション1-2のいずれを利用するかについて、上位レイヤシグナリングによりUEに通知/設定してもよい。
<Variations>
The priority of the 1-shot HARQ-ACK feedback may be determined by using either the option 1-1 or the option 1-2 described above. In this case, the UE may be notified / set by higher layer signaling as to whether option 1-1 or option 1-2 is to be used.
 所定の上位レイヤパラメータ(例えば、PriorityIndicator-ForDCIFormatX_Y)が設定される場合(例えば、DCIフォーマットX_Yに優先度指定フィールドが存在する場合)、上記オプション1-1を利用して1ショットHARQ-ACKフィードバックの優先度を決定してもよい。それ以外の場合(例えば、所定の上位レイヤパラメータが設定されない場合)、上記オプション1-2を利用して1ショットHARQ-ACKフィードバックの優先度を決定してもよい。 When a predetermined upper layer parameter (for example, PriorityIndicator-ForDCIFormatX_Y) is set (for example, when a priority specification field exists in the DCI format X_Y), the above option 1-1 is used to provide 1-shot HARQ-ACK feedback. You may decide the priority. In other cases (for example, when a predetermined upper layer parameter is not set), the above option 1-2 may be used to determine the priority of the 1-shot HARQ-ACK feedback.
 また、1ショットHARQ-ACKフィードバックでフィードバックされるHARQ-ACKは、オプション1-1又はオプション1-2で示した方法を適用してもよい。 Further, the method shown in option 1-1 or option 1-2 may be applied to the HARQ-ACK fed back by the one-shot HARQ-ACK feedback.
 あるいは、オプション1-1とオプション1-2は、適宜組み合わせて適用されてもよい。例えば、1ショットHARQ-ACKフィードバック自体の優先度は、当該1ショットHARQ-ACKフィードバックを指示するDCIのフォーマットに基づいて決定する。一方で、各HARQ-ACKの優先度は、各HARQ-ACKに対応するPDSCHをスケジュールするDCIに含まれる優先度指定フィールドに基づいて決定してもよい。 Alternatively, option 1-1 and option 1-2 may be applied in combination as appropriate. For example, the priority of the one-shot HARQ-ACK feedback itself is determined based on the format of the DCI that directs the one-shot HARQ-ACK feedback. On the other hand, the priority of each HARQ-ACK may be determined based on the priority specification field included in the DCI that schedules the PDSCH corresponding to each HARQ-ACK.
 あるいは、1ショットHARQ-ACKフィードバック自体の優先度は、当該1ショットHARQ-ACKフィードバックを指示するDCIに含まれる優先度指定フィールドに基づいて決定する。一方で、各HARQ-ACKの優先度は、各HARQ-ACKに対応するPDSCHをスケジュールするDCIのフォーマットに基づいて決定してもよい。 Alternatively, the priority of the 1-shot HARQ-ACK feedback itself is determined based on the priority specification field included in the DCI that indicates the 1-shot HARQ-ACK feedback. On the other hand, the priority of each HARQ-ACK may be determined based on the format of the DCI that schedules the PDSCH corresponding to each HARQ-ACK.
(第2の態様)
 第2の態様では、所定グループ(例えば、PDSCHグループ)を利用してHARQ-ACKフィードバックを行う場合のUL送信の優先度の設定/制御について説明する。
(Second aspect)
In the second aspect, setting / control of the priority of UL transmission when performing HARQ-ACK feedback by using a predetermined group (for example, PDSCH group) will be described.
 UEは、DCIに含まれる要求PDSCHグループ数(Number of requested PDSCH group(s))フィールドに基づいて、フィードバックするHARQ-ACKを判断してもよい。例えば、UEは、要求PDSCHグループ数(Number of requested PDSCH group(s))フィールドの値が“0”である場合、UEは、そのDCIによってスケジュールされるPDSCHグループに対する1以上のHARQフィードバックを、あるリソースにおいて行ってもよい(図7参照)。 The UE may determine the HARQ-ACK to be fed back based on the number of requested PDSCH group (s) field included in the DCI. For example, if the UE has a value of "0" in the Number of requested PDSCH group (s) field, the UE has one or more HARQ feedbacks for the PDSCH groups scheduled by its DCI. This may be done in resources (see Figure 7).
 図7は、PDSCH#3をスケジュールするDCI#3に含まれる要求PDSCHグループ数に基づいて、DCI#3でスケジュールされるPDSCH#3が対応するPDSCHグループ(ここでは、PDSCHグループ#1)に対応する1以上のHARQ-ACK(ここでは、HARQ-ACK#2、#3)を所定のULリソースを利用してフィードバックする場合を示している。 FIG. 7 corresponds to a PDSCH group (here, PDSCH group # 1) corresponding to PDSCH # 3 scheduled by DCI # 3, based on the number of requested PDSCH groups included in DCI # 3 that schedules PDSCH # 3. Shows a case where one or more HARQ-ACKs (here, HARQ-ACK # 2 and # 3) are fed back by using a predetermined UL resource.
 一方で、DCI内の要求PDSCHグループ数フィールドの値が“1”である場合、UEは、そのDCIによってスケジュールされるPDSCHグループと、そのDCIによってスケジュールされるPDSCHグループとは別のPDSCHグループと、に対する一以上のHARQフィードバックを、あるリソースにおいて行ってもよい(図8参照)。 On the other hand, when the value of the request PDSCH group number field in the DCI is "1", the UE has a PDSCH group scheduled by the DCI and a PDSCH group different from the PDSCH group scheduled by the DCI. One or more HARQ feedbacks to a resource may be given at a resource (see Figure 8).
 図8は、PDSCH#3をスケジュールするDCI#3に含まれる要求PDSCHグループ数に基づいて、DCI#3でスケジュールされるPDSCH#3が対応するPDSCHグループ(ここでは、PDSCHグループ#1)と、別のPDSCHグループ(ここでは、PDSCHグループ#0)にそれぞれ対応する1以上のHARQ-ACK(ここでは、HARQ-ACK#1、#2、#3)を所定のULリソースを利用してフィードバックする場合を示している。 FIG. 8 shows a PDSCH group (here, PDSCH group # 1) corresponding to PDSCH # 3 scheduled by DCI # 3, based on the number of requested PDSCH groups included in DCI # 3 that schedules PDSCH # 3. One or more HARQ-ACKs (here, HARQ-ACK # 1, # 2, # 3) corresponding to different PDSCH groups (here, PDSCH group # 0) are fed back using predetermined UL resources. Shows the case.
 PDSCHグループインデックス(PDSCH group index)は、PDSCHをスケジュールするDCIを利用してUEに通知してもよい。また、PDSCHグループインデックスは、所定数(例えば、2個)であってもよい。設定されるPDSCHグループインデックスが2個(例えば、インデックス0、1である)であり、DCI内の要求PDSCHグループ数フィールドの値が“1”である場合、UEは、PDSCHグループインデックス0及び1が設定されるPDSCHに対するHARQフィードバックを、あるリソースにおいて行ってもよい。 The PDSCH group index may notify the UE using the DCI that schedules the PDSCH. Further, the PDSCH group index may be a predetermined number (for example, two). When there are two PDSCH group indexes set (for example, indexes 0 and 1) and the value of the requested PDSCH group number field in the DCI is "1", the UE has PDSCH group indexes 0 and 1. HARQ feedback for the set PDSCH may be performed at a certain resource.
 以下の説明では、DCIに含まれる要求PDSCHグループ数フィールドにより、当該DCIによりスケジュールされるPDSCHグループに対する一以上のHARQ-ACKをフィードバックする場合(ケース1)と、当該DCIによりスケジュールされるPDSCHグループと、当該PDSCHグループとは別のPDSCHグループと、に対する一以上のHARQ-ACKをフィードバックする場合(ケース2)を例に挙げて説明する。 In the following description, the request PDSCH group number field included in the DCI feeds back one or more HARQ-ACKs to the PDSCH group scheduled by the DCI (Case 1), and the PDSCH group scheduled by the DCI. , A case where one or more HARQ-ACKs are fed back to a PDSCH group different from the PDSCH group (Case 2) will be described as an example.
<ケース1>
 ケース1(例えば、図7参照)において、同一グループに対して、優先度が異なるHARQ-ACK(又は、PDSCH)が対応する構成(オプション2-1)としてもよい。この場合、複数の優先度(例えば、2個の優先度)が、同じPDSCHグループ内に分類/対応される。例えば、図7において、PDSCH#2(又は、HARQ-ACK#2)とPDSCH#3(又は、HARQ-ACK#3)の優先度が異なっていてもよい。これにより、各グループに対応するPDSCHを柔軟に設定することができる。
<Case 1>
In case 1 (for example, see FIG. 7), HARQ-ACK (or PDSCH) having different priorities may correspond to the same group (option 2-1). In this case, a plurality of priorities (eg, two priorities) are classified / corresponding within the same PDSCH group. For example, in FIG. 7, PDSCH # 2 (or HARQ-ACK # 2) and PDSCH # 3 (or HARQ-ACK # 3) may have different priorities. This makes it possible to flexibly set the PDSCH corresponding to each group.
 あるいは、同一グループに対して、同一の優先度のHARQ-ACK(又は、PDSCH)のみが対応する構成、又は、同一グループに対して、優先度が異なるHARQ-ACKが対応することを許容しない構成(オプション2-2)としてもよい。この場合、同じ優先度(例えば、1個の優先度)のみが、同じPDSCHグループ内に分類/対応される。例えば、図7において、PDSCH#2(又は、HARQ-ACK#2)とPDSCH#3(又は、HARQ-ACK#3)の優先度が同一となるように設定する。 Alternatively, a configuration in which only HARQ-ACK (or PDSCH) having the same priority corresponds to the same group, or a configuration in which HARQ-ACK having different priorities does not allow the same group to correspond. (Option 2-2) may be used. In this case, only the same priorities (eg, one priority) are classified / matched within the same PDSCH group. For example, in FIG. 7, PDSCH # 2 (or HARQ-ACK # 2) and PDSCH # 3 (or HARQ-ACK # 3) are set to have the same priority.
<オプション2-1A>
 複数の優先度(例えば、2個の優先度)が同じPDSCHグループに対応することがサポートされる場合、UEは、要求PDSCHグループ数フィールドが含まれるDCIに基づいて、複数の優先度のHARQ-ACKをフィードバックするように制御してもよい(オプション2-1-1)。
<Option 2-1A>
If multiple priorities (eg, two priorities) are supported to correspond to the same PDSCH group, the UE will have multiple priorities HARQ-based on the DCI containing the request PDSCH group count field. It may be controlled to feed back ACK (option 2-1-1).
 UEは、各優先度にそれぞれ対応する複数のHARQ-ACKコードブックを利用してHARQ-ACKのフィードバックを行ってもよい。例えば、UEは、第1の優先度に対応する第1のHARQ-ACKコードブックと、第2の優先度に対応する第2のHARQ-ACKコードブックを利用して、要求PDSCHグループ数により指定されたPDSCHグループ(例えば、図7におけるPDSCHグループ#1)に対応するHARQ-ACKをフィードバックしてもよい。 The UE may provide HARQ-ACK feedback using a plurality of HARQ-ACK codebooks corresponding to each priority. For example, the UE is specified by the number of requested PDSCH groups using the first HARQ-ACK codebook corresponding to the first priority and the second HARQ-ACK codebook corresponding to the second priority. The HARQ-ACK corresponding to the PDSCH group (for example, PDSCH group # 1 in FIG. 7) may be fed back.
 各HARQ-ACKコードブックの優先度は、各HARQ-ACKコードブックに含まれるHARQ-ACKの優先度に基づいて決定されてもよい。例えば、第1のHARQ-ACKコードブックは第1の優先度(high)が設定され、第2のHARQ-ACKコードブックは第2の優先度(low)が設定されてもよい。又は、第1のHARQ-ACKコードブックと第2のHARQ-ACKコードブックに共通の優先度が設定されてもよい。 The priority of each HARQ-ACK codebook may be determined based on the priority of HARQ-ACK included in each HARQ-ACK codebook. For example, the first HARQ-ACK codebook may be set to a first priority (high) and the second HARQ-ACK codebook may be set to a second priority (low). Alternatively, a common priority may be set for the first HARQ-ACK codebook and the second HARQ-ACK codebook.
 あるいは、UEは、共通のHARQ-ACKコードブックを利用して、優先度が異なる複数のHARQ-ACKをフィードバックするように制御してもよい。この場合、優先度が異なる複数のHARQ-ACKを含むHARQ-ACKコードブックの優先度は、DCI(例えば、要求PDSCHグループ数フィールドを含むDCI)に含まれる優先度指定フィールド、又は当該DCIのフォーマットに基づいて決定されてもよい。 Alternatively, the UE may control to feed back a plurality of HARQ-ACKs having different priorities by using a common HARQ-ACK codebook. In this case, the priority of the HARQ-ACK codebook containing a plurality of HARQ-ACKs having different priorities is the priority specification field included in the DCI (for example, the DCI including the request PDSCH group number field), or the format of the DCI. It may be determined based on.
 同一のPDSCHグループに含まれる各HARQ-ACK(又は、各PDSCHに対応するHARQ-ACK)の優先度は、各PDSCHに対応するDCIに含まれる優先度指定フィールド、又はDCIフォーマットに基づいて決定されてもよい。PDSCHは、当該PDSCHの優先度に関わらず同じPDSCHグループに蓄積される。 The priority of each HARQ-ACK (or HARQ-ACK corresponding to each PDSCH) contained in the same PDSCH group is determined based on the priority specification field included in the DCI corresponding to each PDSCH or the DCI format. You may. PDSCHs are accumulated in the same PDSCH group regardless of the priority of the PDSCH.
 UEが要求PDSCHグループ数フィールド(例えば、“0”)を含むDCIを検出した場合、UEは、当該DCIでスケジュールされるPDSCHグループに対応するHARQ-ACKについて優先度に関わらずフィードバックするように制御する。 When the UE detects a DCI containing a requested PDSCH group number field (for example, “0”), the UE controls to give feedback on HARQ-ACK corresponding to the PDSCH group scheduled in the DCI regardless of priority. do.
 このように、同じPDSCHグループに異なる優先度が対応することを許容することにより、優先度とPDSCHグループを柔軟に設定することができる。また、PDSCHグループ単位を利用してHARQ-ACKフィードバックを行う場合に、複数の優先度のHARQ-ACKをフィードバックすることにより、優先度に関わらずHARQ-ACKをフィードバックすることが可能となる。 In this way, by allowing different priorities to correspond to the same PDSCH group, the priority and PDSCH group can be flexibly set. Further, when performing HARQ-ACK feedback using the PDSCH group unit, it is possible to feed back HARQ-ACK regardless of the priority by feeding back HARQ-ACK of a plurality of priorities.
 あるいは、UEは、DCIに含まれる要求PDSCHグループ数フィールドに基づいて、特定の優先度のHARQ-ACKを選択してフィードバックするように制御してもよい(オプション2-1-2)。つまり、所定グループに対して複数の優先度の対応づけをサポートしつつ、所定の優先度のHARQ-ACKを選択的にフィードバックしてもよい。 Alternatively, the UE may control to select and feed back HARQ-ACK of a specific priority based on the request PDSCH group number field included in the DCI (option 2-1-2). That is, HARQ-ACK of a predetermined priority may be selectively fed back while supporting the association of a plurality of priorities with respect to the predetermined group.
 フィードバックを行うHARQ-ACKの優先度は、仕様であらかじめ定義(例えば、highがフィードバック)されてもよいし、DCI/上位レイヤシグナリングに基づいて決定されてもよい。例えば、第1の優先度と第2の優先度が同じPDSCHグループに対応する場合、第1の優先度に対応するHARQ-ACKと第2の優先度に対応するHARQ-ACKのいずれをフィードバックするかについて、DCI/上位レイヤシグナリングに基づいて判断してもよい。 The priority of HARQ-ACK to give feedback may be defined in advance in the specification (for example, high is feedback), or may be determined based on DCI / upper layer signaling. For example, when the first priority and the second priority correspond to the same PDSCH group, either the HARQ-ACK corresponding to the first priority or the HARQ-ACK corresponding to the second priority is fed back. It may be determined based on DCI / upper layer signaling.
 PDSCHグループに含まれる各HARQ-ACK(又は、各PDSCHに対応するHARQ-ACK)の優先度は、各PDSCHに対応するDCIに含まれる優先度指定フィールド、又はDCIフォーマットに基づいて決定されてもよい。PDSCHは、当該PDSCHの優先度に関わらず同じPDSCHグループに蓄積される。 Even if the priority of each HARQ-ACK (or HARQ-ACK corresponding to each PDSCH) included in the PDSCH group is determined based on the priority specification field included in the DCI corresponding to each PDSCH or the DCI format. good. PDSCHs are accumulated in the same PDSCH group regardless of the priority of the PDSCH.
 UEが要求PDSCHグループ数フィールド(例えば、“0”)を含むDCIを検出した場合、UEは、当該DCIでスケジュールされるPDSCHグループに対応するHARQ-ACKのうち、特定の優先度のHARQ-ACKのみをフィードバックするように制御してもよい。 If the UE detects a DCI containing a requested PDSCH group number field (eg, “0”), the UE will have a particular priority HARQ-ACK of the HARQ-ACKs corresponding to the PDSCH groups scheduled in the DCI. It may be controlled to feed back only.
 特定の優先度は、要求PDSCHグループ数フィールド(例えば、“0”)を含むDCIに含まれる優先度指定フィールド、又は当該DCIのフォーマットに基づいて決定されてもよい。あるいは、特定の優先度は、当該PDSCHグループに属するPDSCHのスケジューリングに利用されるDCIのうちの少なくとも一つ(例えば、最後に送信されたDCI)に含まれる優先度指定フィールド、又は当該DCIのフォーマットに基づいて決定されてもよい。 The specific priority may be determined based on the priority specification field included in the DCI including the request PDSCH group number field (eg, "0"), or the format of the DCI. Alternatively, the particular priority is a priority specification field contained in at least one of the DCIs used for scheduling PDSCHs belonging to the PDSCH group (eg, the last transmitted DCI), or the format of the DCI. It may be determined based on.
 特定の優先度のHARQ-ACKのみをフィードバックする場合、フィードバックに利用するHARQ-ACKコードブックの優先度は、当該特定の優先度が設定されてもよい。 When only the HARQ-ACK of a specific priority is fed back, the specific priority may be set as the priority of the HARQ-ACK codebook used for the feedback.
 このように、PDSCHグループ単位を利用してHARQ-ACKフィードバックを行う場合に、特定の優先度のHARQ-ACKを選択してフィードバックすることにより、優先度に応じてHARQ-ACKのフィードバックを制御することが可能となる。 In this way, when performing HARQ-ACK feedback using the PDSCH group unit, the HARQ-ACK feedback of a specific priority is selected and fed back to control the HARQ-ACK feedback according to the priority. It becomes possible.
<オプション2-2A>
 複数の優先度が同じPDSCHグループに対応することがサポートされない場合、又は、特定の優先度(例えば、1個の優先度)のみが同じPDSCHグループに対応する場合、UEは、要求PDSCHグループ数フィールドが含まれるDCIに基づいて、各PDSCHグループに対応するHARQ-ACKをフィードバックするように制御してもよい。
<Option 2-2A>
If multiple priorities do not support the same PDSCH group, or if only a particular priority (eg, one priority) corresponds to the same PDSCH group, the UE will request a PDSCH group count field. The HARQ-ACK corresponding to each PDSCH group may be controlled to be fed back based on the DCI including.
 複数(例えば、2個)のPDSCHグループのうち、1つのPDSCHグループに第1の優先度が対応し、他のPDSCHグループに第2の優先度が対応してもよい。あるいは、複数のPDSCHグループに対して同じ優先度が対応してもよい。PDSCHグループと対応する優先度に関する情報は、上位レイヤシグナリング/DCIを利用してUEに通知/設定されてもよい。 Of a plurality of (for example, two) PDSCH groups, one PDSCH group may correspond to the first priority, and the other PDSCH group may correspond to the second priority. Alternatively, the same priority may correspond to a plurality of PDSCH groups. Information about the PDSCH group and the corresponding priority may be notified / set to the UE using higher layer signaling / DCI.
 DCIでスケジュールされるPDSCHの優先度が第2の優先度(low)となる場合、特定のPDSCHグループ(例えば、インデックス“0”)に対応してもよい。この場合、DCI(例えば、PDSCHをスケジュールするDCI/要求PDSCHグループ数フィールドを含むDCI)に含まれる優先度指定フィールドが“0”(又は、DCIのフォーマットが1_1)に設定され、DCIに含まれるPDSCHグループインデックスフィールドが“0”に設定されてもよい。 When the priority of the PDSCH scheduled by DCI becomes the second priority (low), it may correspond to a specific PDSCH group (for example, index “0”). In this case, the priority specification field included in the DCI (for example, the DCI including the DCI / request PDSCH group number field for scheduling PDSCH) is set to "0" (or the DCI format is 1-1-1) and is included in the DCI. The PDSCH group index field may be set to "0".
 DCIでスケジュールされるPDSCHの優先度が第1の優先度(high)となる場合、特定のPDSCHグループ(例えば、インデックス“1”)に対応してもよい。この場合、DCI(例えば、PDSCHをスケジュールするDCI/要求PDSCHグループ数フィールドを含むDCI)に含まれる優先度指定フィールドが“1”(又は、DCIのフォーマットが1_2)に設定され、DCIに含まれるPDSCHグループインデックスフィールドが“1”に設定されてもよい。 When the priority of the PDSCH scheduled by DCI is the first priority (high), it may correspond to a specific PDSCH group (for example, index “1”). In this case, the priority specification field included in the DCI (for example, the DCI including the DCI / request PDSCH group number field for scheduling PDSCH) is set to "1" (or the DCI format is 1_2) and is included in the DCI. The PDSCH group index field may be set to "1".
 UEが要求PDSCHグループ数フィールド(例えば、“0”)を含むDCIを検出した場合、UEは、当該DCIでスケジュールされるPDSCHグループ#1に対応する1以上のHARQ-ACKをフィードバックするように制御する。例えば、当該要求PDSCHグループ数フィールドを含むDCI(例えば、DCI#3)により第2の優先度(low)が指定され、当該DCI#3より先に送信された他のDCI(例えば、DCI#2)によりPDSCHグループ#1(及び第2の優先度)が指定される場合を想定する。かかる場合、UEは、DCI#2でスケジュールされるPDSCH#2に対応するHARQ-ACKと、DCI#3でスケジュールされるPDSCH#3に対応するHARQ-ACK#3を同一のHARQ-ACKコードブックに含めてフィードバックしてもよい。また、当該HARQ-ACKコードブックに第2の優先度が設定されてもよい。 When the UE detects a DCI containing a requested PDSCH group number field (eg, “0”), the UE controls to feed back one or more HARQ-ACKs corresponding to PDSCH group # 1 scheduled in the DCI. do. For example, a DCI containing the request PDSCH group number field (eg DCI # 3) specifies a second priority (low) and another DCI transmitted prior to the DCI # 3 (eg DCI # 2). ) Specifies PDSCH group # 1 (and the second priority). In such a case, the UE uses the same HARQ-ACK codebook for HARQ-ACK corresponding to PDSCH # 2 scheduled in DCI # 2 and HARQ-ACK # 3 corresponding to PDSCH # 3 scheduled in DCI # 3. You may include it in and give feedback. In addition, a second priority may be set in the HARQ-ACK codebook.
 あるいは、UEが要求PDSCHグループ数フィールド(例えば、“0”)を含むDCIを検出した場合、UEは、当該DCIでスケジュールされるPDSCHグループ#1に対応する1以上のHARQ-ACKをフィードバックするように制御する。例えば、当該要求PDSCHグループ数フィールドを含むDCI(例えば、DCI#3)により第1の優先度(high)が指定され、当該DCI#3より先に送信された他のDCI(例えば、DCI#2)によりPDSCHグループ#1(及び第1の優先度)が指定される場合を想定する。かかる場合、UEは、DCI#2でスケジュールされるPDSCH#2に対応するHARQ-ACK#2と、DCI#3でスケジュールされるPDSCH#3に対応するHARQ-ACK#3を同一のHARQ-ACKコードブックに含めてフィードバックしてもよい。また、当該HARQ-ACKコードブックに第1の優先度が設定されてもよい。 Alternatively, if the UE detects a DCI containing a requested PDSCH group number field (eg, “0”), the UE may feed back one or more HARQ-ACKs corresponding to the PDSCH group # 1 scheduled in the DCI. To control. For example, a DCI containing the request PDSCH group number field (eg DCI # 3) specifies a first priority (high) and another DCI transmitted prior to the DCI # 3 (eg DCI # 2). ) Specifies PDSCH group # 1 (and the first priority). In such a case, the UE performs the same HARQ-ACK # 2 corresponding to PDSCH # 2 scheduled by DCI # 2 and HARQ-ACK # 3 corresponding to PDSCH # 3 scheduled by DCI # 3. You may include it in the codebook and give feedback. Further, the first priority may be set in the HARQ-ACK codebook.
<バリエーション>
 UEは、DCI(例えば、要求PDSCHグループ数を指示するDCI、又は所定PDSCHグループに含まれるPDSCHをスケジュールするDCI)から決定される優先度の値(例えば、i)に基づいて、所定PDSCHグループに対してフィードバックするHARQ-ACKを決定してもよい。例えば、当該DCIから得られる優先度の値(例えば、i)以上の優先度を有するHARQ-ACKを選択して、所定PDSCHグループに対するHARQ-ACKフィードバックに含めてもよい。
<Variations>
The UE is assigned to a predetermined PDSCH group based on a priority value (eg, i) determined from a DCI (eg, a DCI indicating the number of requested PDSCH groups, or a DCI scheduling PDSCHs contained in a predetermined PDSCH group). The HARQ-ACK to be fed back may be determined. For example, a HARQ-ACK having a priority value (eg, i) or higher obtained from the DCI may be selected and included in the HARQ-ACK feedback for a predetermined PDSCH group.
 UEが要求PDSCHグループ数フィールド(例えば、“0”)を含むDCIを検出した場合、UEは、当該DCIでスケジュールされるPDSCHグループ#1の優先度以上の優先度を有するHARQ-ACK(又は、PDSCHグループのHARQ-ACK)をフィードバックするように制御する。例えば、当該要求PDSCHグループ数フィールドを含むDCI(DCI#3)により第2の優先度(low)が指定され、当該DCI#3より前に送信されたDCI#2により第2の優先度より高い優先度を有するPDSCH#2(及び第1の優先度)が指定される場合を想定する。かかる場合、UEは、PDSCH#2に対応するHARQ-ACK#2と、PDSCH#3に対応するHARQ-ACK#3を同一のHARQ-ACKコードブックに含めてフィードバックしてもよい。また、当該HARQ-ACKコードブックに第1の優先度又は第2の優先度が設定されてもよい。 If the UE detects a DCI containing a requested PDSCH group number field (eg, “0”), the UE has a HARQ-ACK (or a priority equal to or higher than the priority of PDSCH group # 1 scheduled in the DCI). The PDSCH group's HARQ-ACK) is controlled to be fed back. For example, a DCI (DCI # 3) containing the request PDSCH group number field specifies a second priority (low), which is higher than the second priority by DCI # 2 transmitted prior to DCI # 3. It is assumed that PDSCH # 2 (and the first priority) having a priority is specified. In such a case, the UE may include HARQ-ACK # 2 corresponding to PDSCH # 2 and HARQ-ACK # 3 corresponding to PDSCH # 3 in the same HARQ-ACK codebook for feedback. Further, a first priority or a second priority may be set in the HARQ-ACK codebook.
 上記説明では、優先度指示フィールド“0”と、PDSCHグループインデックス“0”が対応し、優先度指示フィールド“1”と、PDSCHグループインデックス“1”が対応する場合を示したがこれに限られない。優先度指示フィールド“0”と、PDSCHグループインデックス“1”が対応し、優先度指示フィールド“1”と、PDSCHグループインデックス“0”が対応してもよい。 In the above description, the case where the priority instruction field "0" and the PDSCH group index "0" correspond to each other and the priority instruction field "1" and the PDSCH group index "1" correspond to each other is shown, but the present invention is limited to this. No. The priority instruction field "0" may correspond to the PDSCH group index "1", and the priority instruction field "1" may correspond to the PDSCH group index "0".
 また、DCIフォーマット1_1と、PDSCHグループインデックス“0”が対応し、DCIフォーマット1_2と、PDSCHグループインデックス“1”が対応してもよい。あるいは、DCIフォーマット1_1と、PDSCHグループインデックス“1”が対応し、DCIフォーマット1_2と、PDSCHグループインデックス“0”が対応してもよい。DCIフォーマットと、PDSCHグループインデックスの対応づけは、上位レイヤシグナリング等を利用してUEに通知/設定してもよい。 Further, the DCI format 1_1 may correspond to the PDSCH group index “0”, and the DCI format 1_2 may correspond to the PDSCH group index “1”. Alternatively, the DCI format 1_1 may correspond to the PDSCH group index “1”, and the DCI format 1_2 may correspond to the PDSCH group index “0”. The association between the DCI format and the PDSCH group index may be notified / set to the UE by using higher layer signaling or the like.
 DCIに優先度指示フィールド(例えば、Priority Indicator field)が存在する場合、PDSCHグループインデックスフィールド(例えば、PDSCH group index field)は、存在しない又は“0”に設定されない構成としてもよい。 When a priority indicator field (for example, Priority Indicator field) exists in DCI, the PDSCH group index field (for example, PDSCH group index field) may not exist or may not be set to "0".
 この場合、優先度と、PDSCHグループインデックスは関連付けられていてもよい。また、所定の上位レイヤパラメータ(例えば、hpdsch-HARQ-ACK-Codebook=enhancedDynamic-r16)が設定される場合、優先度指示フィールドは、対応するPDSCHグループインデックスを指定してもよい。これにより、DCIのビット数を低減することができる。 In this case, the priority and the PDSCH group index may be related. Further, when a predetermined upper layer parameter (for example, hpdsch-HARQ-ACK-Codebook = enhancedDynamic-r16) is set, the priority indicator field may specify the corresponding PDSCH group index. Thereby, the number of bits of DCI can be reduced.
 PDSCHグループに対して、設定される優先度について制限が設けられる構成としてもよいし、制限されない構成としてもよい。制限が設けられる構成としては、例えば、2個のPDSCHグループの一方に対して第1の優先度(high)が対応し、他方に対してい第2の優先度(low)が対応してもよい。制限されない構成としては、例えば、2個のPDSCHグループの両方に同じ優先度(例えば、high)が対応する構成としてもよい。 The PDSCH group may be configured to have restrictions on the priority to be set, or may be configured not to be restricted. As a configuration in which the restriction is provided, for example, one of the two PDSCH groups may correspond to the first priority (high) and the other may correspond to the second priority (low). .. As an unrestricted configuration, for example, a configuration in which the same priority (for example, high) corresponds to both of two PDSCH groups may be used.
<ケース2>
 ケース2では、DCIに含まれる要求PDSCHグループ数フィールドにより、当該DCIによりスケジュールされるPDSCHグループと、当該PDSCHグループとは別のPDSCHグループと、に対する一以上のHARQ-ACKをフィードバックする場合に相当する(例えば、図8参照)。
<Case 2>
Case 2 corresponds to the case where one or more HARQ-ACKs are fed back to the PDSCH group scheduled by the DCI and the PDSCH group different from the PDSCH group by the request PDSCH group number field included in the DCI. (See, for example, FIG. 8).
 ケース2において、同一グループに対して、優先度が異なるHARQ-ACK(又は、PDSCH)が対応する構成(オプション2-1)としてもよい。この場合、複数の優先度(例えば、2個の優先度)が、同じPDSCHグループ内に分類/対応される。例えば、図8において、グループ#1に含まれるPDSCH#2(又は、HARQ-ACK#2)とPDSCH#3(又は、HARQ-ACK#3)の優先度が異なっていてもよい。 In case 2, HARQ-ACK (or PDSCH) having different priorities may correspond to the same group (option 2-1). In this case, a plurality of priorities (eg, two priorities) are classified / corresponding within the same PDSCH group. For example, in FIG. 8, PDSCH # 2 (or HARQ-ACK # 2) and PDSCH # 3 (or HARQ-ACK # 3) included in group # 1 may have different priorities.
 あるいは、同一グループに対して、同一の優先度のHARQ-ACK(又は、PDSCH)のみが対応する構成、又は、同一グループに対して、優先度が異なるHARQ-ACKが対応することを許容しない構成(オプション2-2)としてもよい。この場合、同じ優先度(例えば、1個の優先度)のみが、同じPDSCHグループ内に分類/対応される。例えば、図8において、PDSCH#2(又は、HARQ-ACK#2)とPDSCH#3(又は、HARQ-ACK#3)の優先度が同一となるように設定する。 Alternatively, a configuration in which only HARQ-ACK (or PDSCH) having the same priority corresponds to the same group, or a configuration in which HARQ-ACK having different priorities does not allow the same group to correspond. (Option 2-2) may be used. In this case, only the same priorities (eg, one priority) are classified / matched within the same PDSCH group. For example, in FIG. 8, PDSCH # 2 (or HARQ-ACK # 2) and PDSCH # 3 (or HARQ-ACK # 3) are set to have the same priority.
<オプション2-1B>
 複数の優先度(例えば、2個の優先度)が同じPDSCHグループに対応することがサポートされる場合、UEは、要求PDSCHグループ数フィールドが含まれるDCIに基づいて、複数の優先度のHARQ-ACKをフィードバックするように制御してもよい(オプション2-1-1)。
<Option 2-1B>
If multiple priorities (eg, two priorities) are supported to correspond to the same PDSCH group, the UE will have multiple priorities HARQ-based on the DCI containing the request PDSCH group count field. It may be controlled to feed back ACK (option 2-1-1).
 UEは、各優先度/各PDSCHグループにそれぞれ対応する複数のHARQ-ACKコードブックを利用してHARQ-ACKのフィードバックを行ってもよい。例えば、UEは、第1の優先度に対応する第1のHARQ-ACKコードブックと、第2の優先度に対応する第2のHARQ-ACKコードブックを利用して、要求PDSCHグループ数により指定されたPDSCHグループ(例えば、図8におけるPDSCHグループ#0と#1)に対応するHARQ-ACKをフィードバックしてもよい。 The UE may provide HARQ-ACK feedback using a plurality of HARQ-ACK codebooks corresponding to each priority / each PDSCH group. For example, the UE is specified by the number of requested PDSCH groups using the first HARQ-ACK codebook corresponding to the first priority and the second HARQ-ACK codebook corresponding to the second priority. The HARQ-ACK corresponding to the PDSCH group (for example, PDSCH groups # 0 and # 1 in FIG. 8) may be fed back.
 各HARQ-ACKコードブックの優先度は、各HARQ-ACKコードブックに含まれるHARQ-ACKの優先度に基づいて決定されてもよい。例えば、第1のHARQ-ACKコードブックは第1の優先度(high)が設定され、第2のHARQ-ACKコードブックは第2の優先度(low)が設定されてもよい。又は、第1のHARQ-ACKコードブックと第2のHARQ-ACKコードブックに共通の優先度が設定されてもよい。 The priority of each HARQ-ACK codebook may be determined based on the priority of HARQ-ACK included in each HARQ-ACK codebook. For example, the first HARQ-ACK codebook may be set to a first priority (high) and the second HARQ-ACK codebook may be set to a second priority (low). Alternatively, a common priority may be set for the first HARQ-ACK codebook and the second HARQ-ACK codebook.
 あるいは、UEは、第1のPDSCHグループに対応する第1のHARQ-ACKコードブックと、第2のPDSCHグループに対応する第2のHARQ-ACKコードブックを利用して、各PDSCHグループに対応するHARQ-ACKをフィードバックしてもよい。この場合、第1のHARQ-ACKコードブックに優先度が異なる複数のHARQ-ACKが含まれてもよい。また、第2のHARQ-ACKコードブックに優先度が異なる複数のHARQ-ACKが含まれてもよい。 Alternatively, the UE uses a first HARQ-ACK codebook corresponding to the first PDSCH group and a second HARQ-ACK codebook corresponding to the second PDSCH group to correspond to each PDSCH group. HARQ-ACK may be fed back. In this case, the first HARQ-ACK codebook may contain a plurality of HARQ-ACKs having different priorities. Further, the second HARQ-ACK codebook may contain a plurality of HARQ-ACKs having different priorities.
 優先度が異なる複数のHARQ-ACKを含むHARQ-ACKコードブックの優先度は、DCI(例えば、要求PDSCHグループ数フィールドを含むDCI)に含まれる優先度指定フィールド、又は当該DCIのフォーマットに基づいて決定されてもよい。あるいは、各PDSCHグループに対応する優先度に基づいて決定されてもよい。 The priority of a HARQ-ACK codebook containing multiple HARQ-ACKs with different priorities is based on the priority specification field contained in the DCI (eg, the DCI containing the requested PDSCH group number field) or the format of the DCI. It may be decided. Alternatively, it may be determined based on the priority corresponding to each PDSCH group.
 PDSCHグループに含まれる各HARQ-ACK(又は、各PDSCHに対応するHARQ-ACK)の優先度は、各PDSCHに対応するDCIに含まれる優先度指定フィールド、又はDCIフォーマットに基づいて決定されてもよい。各PDSCHは、当該PDSCHの優先度に関わらず対応するPDSCHグループに蓄積される。 Even if the priority of each HARQ-ACK (or HARQ-ACK corresponding to each PDSCH) included in the PDSCH group is determined based on the priority specification field included in the DCI corresponding to each PDSCH or the DCI format. good. Each PDSCH is accumulated in the corresponding PDSCH group regardless of the priority of the PDSCH.
 UEが要求PDSCHグループ数フィールド(例えば、値“1”)を含むDCIを検出した場合、UEは、当該DCIでスケジュールされるPDSCHグループ#1に対応するHARQ-ACK#2、#3と、当該PDSCHグループ#1とは別のPDSCHグループ#0に対応するHARQ-ACK#1について優先度に関わらずフィードバックするように制御する。 If the UE detects a DCI containing a requested PDSCH group number field (eg, value "1"), the UE will include HARQ-ACK # 2, # 3, corresponding to PDSCH group # 1 scheduled in the DCI, and the said. It is controlled so that the HARQ-ACK # 1 corresponding to the PDSCH group # 0 different from the PDSCH group # 1 is fed back regardless of the priority.
 このように、同じPDSCHグループに異なる優先度が対応することを許容することにより、優先度とPDSCHグループを柔軟に設定することができる。また、PDSCHグループ単位を利用してHARQ-ACKフィードバックを行う場合に、複数の優先度のHARQ-ACKをフィードバックすることにより、優先度に関わらずHARQ-ACKをフィードバックすることが可能となる。 In this way, by allowing different priorities to correspond to the same PDSCH group, the priority and PDSCH group can be flexibly set. Further, when performing HARQ-ACK feedback using the PDSCH group unit, it is possible to feed back HARQ-ACK regardless of the priority by feeding back HARQ-ACK of a plurality of priorities.
 あるいは、UEは、DCIに含まれる要求PDSCHグループ数フィールドに基づいて、特定の優先度のHARQ-ACKを選択してフィードバックするように制御してもよい(オプション2-1-2)。 Alternatively, the UE may control to select and feed back HARQ-ACK of a specific priority based on the request PDSCH group number field included in the DCI (option 2-1-2).
 フィードバックを行うHARQ-ACKの優先度は、仕様であらかじめ定義(例えば、highがフィードバック)されてもよいし、DCI/上位レイヤシグナリングに基づいて決定されてもよい。例えば、第1の優先度と第2の優先度が同じPDSCHグループに対応する場合、第1の優先度に対応するHARQ-ACKと第2の優先度に対応するHARQ-ACKのいずれをフィードバックするかについて、DCI/上位レイヤシグナリングに基づいて判断してもよい。 The priority of HARQ-ACK to give feedback may be defined in advance in the specification (for example, high is feedback), or may be determined based on DCI / upper layer signaling. For example, when the first priority and the second priority correspond to the same PDSCH group, either the HARQ-ACK corresponding to the first priority or the HARQ-ACK corresponding to the second priority is fed back. It may be determined based on DCI / upper layer signaling.
 PDSCHグループに含まれる各HARQ-ACK(又は、各PDSCHに対応するHARQ-ACK)の優先度は、各PDSCHに対応するDCIに含まれる優先度指定フィールド、又はDCIフォーマットに基づいて決定されてもよい。PDSCHは、当該PDSCHの優先度に関わらず対応するPDSCHグループに蓄積される。 Even if the priority of each HARQ-ACK (or HARQ-ACK corresponding to each PDSCH) included in the PDSCH group is determined based on the priority specification field included in the DCI corresponding to each PDSCH or the DCI format. good. The PDSCH is accumulated in the corresponding PDSCH group regardless of the priority of the PDSCH.
 UEが要求PDSCHグループ数フィールド(例えば、“1”)を含むDCIを検出した場合、UEは、当該DCIでスケジュールされるPDSCHグループ#1に対応するHARQ-ACKのうち特定の優先度のHARQ-ACKと、別のPDSCHグループ#0に対応するHARQ-ACKのうち特定の優先度のHARQ-ACKのみをフィードバックするように制御する。 If the UE detects a DCI containing a requested PDSCH group number field (eg, “1”), the UE will have a particular priority HARQ-ACK of the HARQ-ACK corresponding to the PDSCH group # 1 scheduled in the DCI. It is controlled to feed back only the HARQ-ACK of a specific priority among the ACK and the HARQ-ACK corresponding to another PDSCH group # 0.
 例えば、特定の優先度は、要求PDSCHグループ数フィールド(例えば、“1”)を含むDCIに含まれる優先度指定フィールド、又は当該DCIのフォーマットに基づいて決定されてもよい。あるいは、特定の優先度は、当該PDSCHグループに属するPDSCHのスケジューリングに利用されるDCIのうちの少なくとも一つ(例えば、最後に送信されたDCI)に含まれる優先度指定フィールド、又は当該DCIのフォーマットに基づいて決定されてもよい。 For example, the specific priority may be determined based on the priority specification field included in the DCI including the request PDSCH group number field (eg, "1"), or the format of the DCI. Alternatively, the particular priority is a priority specification field contained in at least one of the DCIs used for scheduling PDSCHs belonging to the PDSCH group (eg, the last transmitted DCI), or the format of the DCI. It may be determined based on.
 あるいは、特定の優先度は、PDSCHグループ(例えば、PDSCHグループインデックス)に基づいて決定されてもよい。優先度とPDSCHグループの対応に関する情報は、上位レイヤシグナリングによりUEに通知/設定されてもよい。 Alternatively, the specific priority may be determined based on the PDSCH group (eg, PDSCH group index). Information regarding the correspondence between the priority and the PDSCH group may be notified / set to the UE by higher layer signaling.
 特定の優先度のHARQ-ACKのみをフィードバックする場合、フィードバックに利用するHARQ-ACKコードブックの優先度は、特定の優先度が設定されてもよい。 When only the HARQ-ACK of a specific priority is fed back, the priority of the HARQ-ACK codebook used for the feedback may be set to a specific priority.
 このように、PDSCHグループ単位を利用してHARQ-ACKフィードバックを行う場合に、特定の優先度のHARQ-ACKを選択してフィードバックすることにより、優先度に応じてHARQ-ACKのフィードバックを制御することが可能となる。 In this way, when performing HARQ-ACK feedback using the PDSCH group unit, the HARQ-ACK feedback of a specific priority is selected and fed back to control the HARQ-ACK feedback according to the priority. It becomes possible.
<オプション2-2B>
 複数の優先度が同じPDSCHグループに対応することがサポートされない場合、又は、特定の優先度(例えば、1個の優先度)のみが同じPDSCHグループに対応する場合、UEは、要求PDSCHグループ数フィールドが含まれるDCIに基づいて、各PDSCHグループに対応するHARQ-ACKをフィードバックするように制御してもよい。
<Option 2-2B>
If multiple priorities do not support the same PDSCH group, or if only a particular priority (eg, one priority) corresponds to the same PDSCH group, the UE will request a PDSCH group count field. The HARQ-ACK corresponding to each PDSCH group may be controlled to be fed back based on the DCI including.
 複数(例えば、2個)のPDSCHグループのうち、1つのPDSCHグループに第1の優先度が対応し、他のPDSCHグループに第2の優先度が対応してもよい。あるいは、複数のPDSCHグループに対して同じ優先度が対応してもよい。PDSCHグループと対応する優先度に関する情報は、上位レイヤシグナリング/DCIを利用してUEに通知/設定されてもよい。 Of a plurality of (for example, two) PDSCH groups, one PDSCH group may correspond to the first priority, and the other PDSCH group may correspond to the second priority. Alternatively, the same priority may correspond to a plurality of PDSCH groups. Information about the PDSCH group and the corresponding priority may be notified / set to the UE using higher layer signaling / DCI.
 DCIでスケジュールされるPDSCHの優先度が第2の優先度(low)となる場合、特定のPDSCHグループ(例えば、インデックス“0”)に対応してもよい。この場合、DCI(例えば、PDSCHをスケジュールするDCI/要求PDSCHグループ数フィールドを含むDCI)に含まれる優先度指定フィールドが“0”(又は、DCIのフォーマットが1_1)に設定され、DCIに含まれるPDSCHグループインデックスフィールドが“0”に設定されてもよい。 When the priority of the PDSCH scheduled by DCI becomes the second priority (low), it may correspond to a specific PDSCH group (for example, index “0”). In this case, the priority specification field included in the DCI (for example, the DCI including the DCI / request PDSCH group number field for scheduling PDSCH) is set to "0" (or the DCI format is 1-1-1) and is included in the DCI. The PDSCH group index field may be set to "0".
 DCIでスケジュールされるPDSCHの優先度が第1の優先度(high)となる場合、特定のPDSCHグループ(例えば、インデックス“1”)に対応してもよい。この場合、DCI(例えば、PDSCHをスケジュールするDCI/要求PDSCHグループ数フィールドを含むDCI)に含まれる優先度指定フィールドが“1”(又は、DCIのフォーマットが1_2)に設定され、DCIに含まれるPDSCHグループインデックスフィールドが“1”に設定されてもよい。 When the priority of the PDSCH scheduled by DCI is the first priority (high), it may correspond to a specific PDSCH group (for example, index “1”). In this case, the priority specification field included in the DCI (for example, the DCI including the DCI / request PDSCH group number field for scheduling PDSCH) is set to "1" (or the DCI format is 1_2) and is included in the DCI. The PDSCH group index field may be set to "1".
 UEが要求PDSCHグループ数フィールド(例えば、“1”)を含むDCI#3を検出した場合、UEは、当該DCI#3でスケジュールされるPDSCHグループ#1に対応する1以上のHARQ-ACK#2、#3と、他のPDSCHグループ#0に対応するHARQ-ACK#1をフィードバックするように制御する。例えば、当該要求PDSCHグループ数フィールドを含むDCI#3により第2の優先度(low)が指定され、当該DCI#3より先に送信されたDCI#1により他のPDSCHグループ#0(及び第2の優先度又は第1の優先度)が指定される場合を想定する。 If the UE detects a DCI # 3 containing a requested PDSCH group number field (eg, “1”), the UE has one or more HARQ-ACK # 2 corresponding to the PDSCH group # 1 scheduled in the DCI # 3. , # 3 and HARQ-ACK # 1 corresponding to another PDSCH group # 0 are controlled to be fed back. For example, a second priority (low) is specified by DCI # 3 including the request PDSCH group number field, and another PDSCH group # 0 (and a second) by DCI # 1 transmitted prior to DCI # 3. Priority or first priority) is specified.
 かかる場合、UEは、DCI#3でスケジュールされるPDSCH#3が含まれるPDSCHグループ#1に対するHARQ-ACK#2、#3と、DCI#1でスケジュールされるPDSCH#1(PDSCHグループ#0)に対するHARQ-ACK#1を同一又は異なるHARQ-ACKコードブックに含めてフィードバックしてもよい。異なるHARQ-ACKコードブックで送信を行う場合、各PDSCHグループに対応する優先度、又は各PDSCHグループのPDSCHをスケジュールするDCIで指定される優先度が対応するHARQ-ACKコードブックに設定されてもよい。 In such a case, the UE has HARQ-ACK # 2 and # 3 for PDSCH group # 1 including PDSCH # 3 scheduled in DCI # 3, and PDSCH # 1 (PDSCH group # 0) scheduled in DCI # 1. HARQ-ACK # 1 may be included in the same or different HARQ-ACK codebooks for feedback. When transmitting with a different HARQ-ACK codebook, even if the priority corresponding to each PDSCH group or the priority specified by the DCI that schedules the PDSCH of each PDSCH group is set to the corresponding HARQ-ACK codebook. good.
 また、要求PDSCHグループ数フィールドを含むDCI#3により第1の優先度(high)が指定され、当該DCI#3より先に送信されたDCI#1により他のPDSCHグループ#0(及び第1の優先度又は第2の優先度)が指定される場合を想定する。 Further, the first priority (high) is specified by DCI # 3 including the request PDSCH group number field, and another PDSCH group # 0 (and the first PDSCH group # 0) is specified by DCI # 1 transmitted before the DCI # 3. It is assumed that a priority or a second priority) is specified.
 かかる場合、UEは、DCI#3でスケジュールされるPDSCH#3が含まれるPDSCHグループ#1に対するHARQ-ACK#2、#3と、DCI#1でスケジュールされるPDSCH#1(PDSCHグループ#0)に対するHARQ-ACK#1を同一又は異なるHARQ-ACKコードブックに含めてフィードバックしてもよい。異なるHARQ-ACKコードブックで送信を行う場合、各PDSCHグループに対応する優先度、又は各PDSCHグループのPDSCHをスケジュールするDCIで指定される優先度が対応するHARQ-ACKコードブックに設定されてもよい。 In such a case, the UE has HARQ-ACK # 2 and # 3 for PDSCH group # 1 including PDSCH # 3 scheduled in DCI # 3, and PDSCH # 1 (PDSCH group # 0) scheduled in DCI # 1. HARQ-ACK # 1 may be included in the same or different HARQ-ACK codebooks for feedback. When transmitting with a different HARQ-ACK codebook, even if the priority corresponding to each PDSCH group or the priority specified by the DCI that schedules the PDSCH of each PDSCH group is set to the corresponding HARQ-ACK codebook. good.
<バリエーション>
 UEは、DCI(例えば、要求PDSCHグループ数を指示するDCI、又は所定PDSCHグループに含まれるPDSCHをスケジュールするDCI)から決定される優先度の値(例えば、i)に基づいて、所定PDSCHグループに対してフィードバックするHARQ-ACKを決定してもよい。例えば、当該DCIから得られる優先度の値(例えば、i)以上の優先度を有するHARQ-ACKを選択して、所定PDSCHグループに対するHARQ-ACKフィードバックに含めてもよい。
<Variations>
The UE is assigned to a predetermined PDSCH group based on a priority value (eg, i) determined from a DCI (eg, a DCI indicating the number of requested PDSCH groups, or a DCI scheduling PDSCHs contained in a predetermined PDSCH group). The HARQ-ACK to be fed back may be determined. For example, a HARQ-ACK having a priority value (eg, i) or higher obtained from the DCI may be selected and included in the HARQ-ACK feedback for a predetermined PDSCH group.
 UEが要求PDSCHグループ数フィールド(例えば、“1”)を含むDCI#3を検出した場合、UEは、当該DCI#3でスケジュールされるPDSCHグループ#1の優先度以上の優先度を有するHARQ-ACKと、他のPDSCHグループ#0に対応するHARQ-ACKをフィードバックするように制御する。他のPDSCHグループ#0に対応するHARQ-ACKは、PDSCHグループ#1の優先度以上の優先度を有するHARQ-ACKであってもよい。 If the UE detects a DCI # 3 containing a requested PDSCH group number field (eg, “1”), the UE has a HARQ-that has a priority equal to or higher than the priority of the PDSCH group # 1 scheduled in the DCI # 3. Control to feed back ACK and HARQ-ACK corresponding to another PDSCH group # 0. The HARQ-ACK corresponding to the other PDSCH group # 0 may be a HARQ-ACK having a priority equal to or higher than the priority of the PDSCH group # 1.
 例えば、当該要求PDSCHグループ数フィールドを含むDCI#3により第2の優先度(low)が指定され、当該DCI#3より先に送信されたDCI#1により第2の優先度より高い優先度を有するPDSCHグループ#0(及び第1の優先度)が指定される場合を想定する。かかる場合、UEは、DCI#3でスケジュールされるPDSCHグループ#1に対応するHARQ-ACK#3(及び#2)と、DCI#1でスケジュールされるHARQ-ACK#1を同一又は異なるHARQ-ACKコードブックに含めてフィードバックしてもよい。また、当該HARQ-ACKコードブックに第1の優先度又は第2の優先度が設定されてもよい。 For example, DCI # 3 including the request PDSCH group number field specifies a second priority (low), and DCI # 1 transmitted prior to DCI # 3 gives a higher priority than the second priority. It is assumed that the PDSCH group # 0 (and the first priority) to have is specified. In such a case, the UE has the same or different HARQ-ACK # 3 (and # 2) corresponding to the PDSCH group # 1 scheduled in DCI # 3 and HARQ-ACK # 1 scheduled in DCI # 1. You may include it in the ACK codebook and give feedback. Further, a first priority or a second priority may be set in the HARQ-ACK codebook.
 上記説明では、優先度指示フィールド“0”と、PDSCHグループインデックス“0”が対応し、優先度指示フィールド“1”と、PDSCHグループインデックス“1”が対応する場合を示したがこれに限られない。優先度指示フィールド“0”と、PDSCHグループインデックス“1”が対応し、優先度指示フィールド“1”と、PDSCHグループインデックス“0”が対応してもよい。 In the above description, the case where the priority instruction field "0" and the PDSCH group index "0" correspond to each other and the priority instruction field "1" and the PDSCH group index "1" correspond to each other is shown, but the present invention is limited to this. No. The priority instruction field "0" may correspond to the PDSCH group index "1", and the priority instruction field "1" may correspond to the PDSCH group index "0".
 また、DCIフォーマット1_1と、PDSCHグループインデックス“0”が対応し、DCIフォーマット1_2と、PDSCHグループインデックス“1”が対応してもよい。あるいは、DCIフォーマット1_1と、PDSCHグループインデックス“1”が対応し、DCIフォーマット1_2と、PDSCHグループインデックス“0”が対応してもよい。DCIフォーマットと、PDSCHグループインデックスの対応づけは、上位レイヤシグナリング等を利用してUEに通知/設定してもよい。 Further, the DCI format 1_1 may correspond to the PDSCH group index “0”, and the DCI format 1_2 may correspond to the PDSCH group index “1”. Alternatively, the DCI format 1_1 may correspond to the PDSCH group index “1”, and the DCI format 1_2 may correspond to the PDSCH group index “0”. The association between the DCI format and the PDSCH group index may be notified / set to the UE by using higher layer signaling or the like.
 DCIに優先度指示フィールド(例えば、Priority Indicator field)が存在する場合、PDSCHグループインデックスフィールド(例えば、PDSCH group index field)は、存在しない又は“0”に設定されない構成としてもよい。 When a priority indicator field (for example, Priority Indicator field) exists in DCI, the PDSCH group index field (for example, PDSCH group index field) may not exist or may not be set to "0".
 この場合、優先度と、PDSCHグループインデックスは関連付けられていてもよい。また、所定の上位レイヤパラメータ(例えば、hpdsch-HARQ-ACK-Codebook=enhancedDynamic-r16)が設定される場合、優先度指示フィールドは、対応するPDSCHグループインデックスを指定してもよい。これにより、DCIのビット数を低減することができる。 In this case, the priority and the PDSCH group index may be related. Further, when a predetermined upper layer parameter (for example, hpdsch-HARQ-ACK-Codebook = enhancedDynamic-r16) is set, the priority indicator field may specify the corresponding PDSCH group index. Thereby, the number of bits of DCI can be reduced.
 PDSCHグループに対して、設定される優先度について制限が設けられる構成としてもよいし、制限されない構成としてもよい。制限が設けられる構成としては、例えば、2個のPDSCHグループの一方に対して第1の優先度(high)が対応し、他方に対してい第2の優先度(low)が対応してもよい。制限されない構成としては、例えば、2個のPDSCHグループの両方に同じ優先度(例えば、high)が対応する構成としてもよい。 The PDSCH group may be configured to have restrictions on the priority to be set, or may be configured not to be restricted. As a configuration in which the restriction is provided, for example, one of the two PDSCH groups may correspond to the first priority (high) and the other may correspond to the second priority (low). .. As an unrestricted configuration, for example, a configuration in which the same priority (for example, high) corresponds to both of two PDSCH groups may be used.
(無線通信システム)
 以下、本開示の一実施形態に係る無線通信システムの構成について説明する。この無線通信システムでは、本開示の上記各実施形態に係る無線通信方法のいずれか又はこれらの組み合わせを用いて通信が行われる。
(Wireless communication system)
Hereinafter, the configuration of the wireless communication system according to the embodiment of the present disclosure will be described. In this 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.
 図9は、一実施形態に係る無線通信システムの概略構成の一例を示す図である。無線通信システム1は、Third Generation Partnership Project(3GPP)によって仕様化されるLong Term Evolution(LTE)、5th generation mobile communication system New Radio(5G NR)などを用いて通信を実現するシステムであってもよい。 FIG. 9 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). ..
 また、無線通信システム1は、複数のRadio Access Technology(RAT)間のデュアルコネクティビティ(マルチRATデュアルコネクティビティ(Multi-RAT Dual Connectivity(MR-DC)))をサポートしてもよい。MR-DCは、LTE(Evolved Universal Terrestrial Radio Access(E-UTRA))とNRとのデュアルコネクティビティ(E-UTRA-NR Dual Connectivity(EN-DC))、NRとLTEとのデュアルコネクティビティ(NR-E-UTRA Dual Connectivity(NE-DC))などを含んでもよい。 Further, the wireless communication system 1 may support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between a plurality of Radio Access Technologies (RATs). MR-DC is a dual connectivity (E-UTRA-NR Dual Connectivity (EN-DC)) between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR, and a dual connectivity (NR-E) between NR and LTE. -UTRA Dual Connectivity (NE-DC)) may be included.
 EN-DCでは、LTE(E-UTRA)の基地局(eNB)がマスタノード(Master Node(MN))であり、NRの基地局(gNB)がセカンダリノード(Secondary Node(SN))である。NE-DCでは、NRの基地局(gNB)がMNであり、LTE(E-UTRA)の基地局(eNB)がSNである。 In EN-DC, 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)). In NE-DC, the base station (gNB) of NR is MN, and the base station (eNB) of LTE (E-UTRA) is SN.
 無線通信システム1は、同一のRAT内の複数の基地局間のデュアルコネクティビティ(例えば、MN及びSNの双方がNRの基地局(gNB)であるデュアルコネクティビティ(NR-NR Dual Connectivity(NN-DC)))をサポートしてもよい。 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.
 無線通信システム1は、比較的カバレッジの広いマクロセルC1を形成する基地局11と、マクロセルC1内に配置され、マクロセルC1よりも狭いスモールセルC2を形成する基地局12(12a-12c)と、を備えてもよい。ユーザ端末20は、少なくとも1つのセル内に位置してもよい。各セル及びユーザ端末20の配置、数などは、図に示す態様に限定されない。以下、基地局11及び12を区別しない場合は、基地局10と総称する。 The wireless communication system 1 includes a base station 11 that forms a macrocell C1 having a relatively wide coverage, and a base station 12 (12a-12c) that is arranged in the macrocell C1 and forms a small cell C2 that is narrower than the macrocell C1. You may prepare. The user terminal 20 may be located in at least one cell. The arrangement, number, and the like of each cell and the user terminal 20 are not limited to the mode shown in the figure. Hereinafter, when the base stations 11 and 12 are not distinguished, they are collectively referred to as the base station 10.
 ユーザ端末20は、複数の基地局10のうち、少なくとも1つに接続してもよい。ユーザ端末20は、複数のコンポーネントキャリア(Component Carrier(CC))を用いたキャリアアグリゲーション(Carrier Aggregation(CA))及びデュアルコネクティビティ(DC)の少なくとも一方を利用してもよい。 The user terminal 20 may be connected to at least one of a plurality of base stations 10. The user terminal 20 may use at least one of carrier aggregation (Carrier Aggregation (CA)) and dual connectivity (DC) using a plurality of component carriers (Component Carrier (CC)).
 各CCは、第1の周波数帯(Frequency Range 1(FR1))及び第2の周波数帯(Frequency Range 2(FR2))の少なくとも1つに含まれてもよい。マクロセルC1はFR1に含まれてもよいし、スモールセルC2はFR2に含まれてもよい。例えば、FR1は、6GHz以下の周波数帯(サブ6GHz(sub-6GHz))であってもよいし、FR2は、24GHzよりも高い周波数帯(above-24GHz)であってもよい。なお、FR1及びFR2の周波数帯、定義などはこれらに限られず、例えばFR1がFR2よりも高い周波数帯に該当してもよい。 Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macrocell C1 may be included in FR1 and the small cell C2 may be included in FR2. For example, FR1 may be in a frequency band of 6 GHz or less (sub 6 GHz (sub-6 GHz)), and FR 2 may be in a frequency band higher than 24 GHz (above-24 GHz). The frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.
 また、ユーザ端末20は、各CCにおいて、時分割複信(Time Division Duplex(TDD))及び周波数分割複信(Frequency Division Duplex(FDD))の少なくとも1つを用いて通信を行ってもよい。 Further, the user terminal 20 may perform communication using at least one of Time Division Duplex (TDD) and Frequency Division Duplex (FDD) in each CC.
 複数の基地局10は、有線(例えば、Common Public Radio Interface(CPRI)に準拠した光ファイバ、X2インターフェースなど)又は無線(例えば、NR通信)によって接続されてもよい。例えば、基地局11及び12間においてNR通信がバックホールとして利用される場合、上位局に該当する基地局11はIntegrated Access Backhaul(IAB)ドナー、中継局(リレー)に該当する基地局12はIABノードと呼ばれてもよい。 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). 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.
 基地局10は、他の基地局10を介して、又は直接コアネットワーク30に接続されてもよい。コアネットワーク30は、例えば、Evolved Packet Core(EPC)、5G Core Network(5GCN)、Next Generation Core(NGC)などの少なくとも1つを含んでもよい。 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).
 ユーザ端末20は、LTE、LTE-A、5Gなどの通信方式の少なくとも1つに対応した端末であってもよい。 The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.
 無線通信システム1においては、直交周波数分割多重(Orthogonal Frequency Division Multiplexing(OFDM))ベースの無線アクセス方式が利用されてもよい。例えば、下りリンク(Downlink(DL))及び上りリンク(Uplink(UL))の少なくとも一方において、Cyclic Prefix OFDM(CP-OFDM)、Discrete Fourier Transform Spread OFDM(DFT-s-OFDM)、Orthogonal Frequency Division Multiple Access(OFDMA)、Single Carrier Frequency Division Multiple Access(SC-FDMA)などが利用されてもよい。 In the wireless communication system 1, a wireless access method based on Orthogonal Frequency Division Multiplexing (OFDM) may be used. For example, at least one of the downlink (Downlink (DL)) and the uplink (Uplink (UL)), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple. Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.
 無線アクセス方式は、波形(waveform)と呼ばれてもよい。なお、無線通信システム1においては、UL及びDLの無線アクセス方式には、他の無線アクセス方式(例えば、他のシングルキャリア伝送方式、他のマルチキャリア伝送方式)が用いられてもよい。 The wireless access method may be called a waveform. In the wireless communication system 1, another wireless access system (for example, another single carrier transmission system, another multi-carrier transmission system) may be used as the UL and DL wireless access systems.
 無線通信システム1では、下りリンクチャネルとして、各ユーザ端末20で共有される下り共有チャネル(Physical Downlink Shared Channel(PDSCH))、ブロードキャストチャネル(Physical Broadcast Channel(PBCH))、下り制御チャネル(Physical Downlink Control Channel(PDCCH))などが用いられてもよい。 In the wireless communication system 1, as downlink channels, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)), a broadcast channel (Physical Broadcast Channel (PBCH)), and a downlink control channel (Physical Downlink Control) shared by each user terminal 20 are used. Channel (PDCCH)) and the like may be used.
 また、無線通信システム1では、上りリンクチャネルとして、各ユーザ端末20で共有される上り共有チャネル(Physical Uplink Shared Channel(PUSCH))、上り制御チャネル(Physical Uplink Control Channel(PUCCH))、ランダムアクセスチャネル(Physical Random Access Channel(PRACH))などが用いられてもよい。 Further, in the wireless communication system 1, as the uplink channel, the uplink shared channel (Physical Uplink Shared Channel (PUSCH)), the uplink control channel (Physical Uplink Control Channel (PUCCH)), and the random access channel shared by each user terminal 20 are used. (Physical Random Access Channel (PRACH)) or the like may be used.
 PDSCHによって、ユーザデータ、上位レイヤ制御情報、System Information Block(SIB)などが伝送される。PUSCHによって、ユーザデータ、上位レイヤ制御情報などが伝送されてもよい。また、PBCHによって、Master Information Block(MIB)が伝送されてもよい。 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. Further, the Master Information Block (MIB) may be transmitted by the PBCH.
 PDCCHによって、下位レイヤ制御情報が伝送されてもよい。下位レイヤ制御情報は、例えば、PDSCH及びPUSCHの少なくとも一方のスケジューリング情報を含む下り制御情報(Downlink Control Information(DCI))を含んでもよい。 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.
 なお、PDSCHをスケジューリングするDCIは、DLアサインメント、DL DCIなどと呼ばれてもよいし、PUSCHをスケジューリングするDCIは、ULグラント、UL DCIなどと呼ばれてもよい。なお、PDSCHはDLデータで読み替えられてもよいし、PUSCHはULデータで読み替えられてもよい。 The DCI that schedules PDSCH may be called DL assignment, DL DCI, or the like, and the DCI that schedules PUSCH may be called UL grant, UL DCI, or the like. The PDSCH may be read as DL data, and the PUSCH may be read as UL data.
 PDCCHの検出には、制御リソースセット(COntrol REsource SET(CORESET))及びサーチスペース(search space)が利用されてもよい。CORESETは、DCIをサーチするリソースに対応する。サーチスペースは、PDCCH候補(PDCCH candidates)のサーチ領域及びサーチ方法に対応する。1つのCORESETは、1つ又は複数のサーチスペースに関連付けられてもよい。UEは、サーチスペース設定に基づいて、あるサーチスペースに関連するCORESETをモニタしてもよい。 A control resource set (COntrol REsource SET (CORESET)) and a search space (search space) may be used for PDCCH detection. CORESET corresponds to a resource for searching DCI. The search space corresponds to the search area and search method of PDCCH candidates (PDCCH candidates). One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a search space based on the search space settings.
 1つのサーチスペースは、1つ又は複数のアグリゲーションレベル(aggregation Level)に該当するPDCCH候補に対応してもよい。1つ又は複数のサーチスペースは、サーチスペースセットと呼ばれてもよい。なお、本開示の「サーチスペース」、「サーチスペースセット」、「サーチスペース設定」、「サーチスペースセット設定」、「CORESET」、「CORESET設定」などは、互いに読み替えられてもよい。 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.
 PUCCHによって、チャネル状態情報(Channel State Information(CSI))、送達確認情報(例えば、Hybrid Automatic Repeat reQuest ACKnowledgement(HARQ-ACK)、ACK/NACKなどと呼ばれてもよい)及びスケジューリングリクエスト(Scheduling Request(SR))の少なくとも1つを含む上り制御情報(Uplink Control Information(UCI))が伝送されてもよい。PRACHによって、セルとの接続確立のためのランダムアクセスプリアンブルが伝送されてもよい。 Depending on the PUCCH, 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.) and scheduling request (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.
 なお、本開示において下りリンク、上りリンクなどは「リンク」を付けずに表現されてもよい。また、各種チャネルの先頭に「物理(Physical)」を付けずに表現されてもよい。 In this disclosure, downlinks, uplinks, etc. may be expressed without "links". Further, it may be expressed without adding "Physical" to the beginning of various channels.
 無線通信システム1では、同期信号(Synchronization Signal(SS))、下りリンク参照信号(Downlink Reference Signal(DL-RS))などが伝送されてもよい。無線通信システム1では、DL-RSとして、セル固有参照信号(Cell-specific Reference Signal(CRS))、チャネル状態情報参照信号(Channel State Information Reference Signal(CSI-RS))、復調用参照信号(DeModulation Reference Signal(DMRS))、位置決定参照信号(Positioning Reference Signal(PRS))、位相トラッキング参照信号(Phase Tracking Reference Signal(PTRS))などが伝送されてもよい。 In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), and the like may be transmitted. In the wireless communication system 1, the DL-RS includes a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), and a reference signal for demodulation (DeModulation). 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.
 同期信号は、例えば、プライマリ同期信号(Primary Synchronization Signal(PSS))及びセカンダリ同期信号(Secondary Synchronization Signal(SSS))の少なくとも1つであってもよい。SS(PSS、SSS)及びPBCH(及びPBCH用のDMRS)を含む信号ブロックは、SS/PBCHブロック、SS Block(SSB)などと呼ばれてもよい。なお、SS、SSBなども、参照信号と呼ばれてもよい。 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)). 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. In addition, SS, SSB and the like may also be called a reference signal.
 また、無線通信システム1では、上りリンク参照信号(Uplink Reference Signal(UL-RS))として、測定用参照信号(Sounding Reference Signal(SRS))、復調用参照信号(DMRS)などが伝送されてもよい。なお、DMRSはユーザ端末固有参照信号(UE-specific Reference Signal)と呼ばれてもよい。 Further, in the wireless communication system 1, even if a measurement reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), or the like is transmitted as an uplink reference signal (Uplink Reference Signal (UL-RS)). good. The DMRS may be called a user terminal specific reference signal (UE-specific Reference Signal).
(基地局)
 図10は、一実施形態に係る基地局の構成の一例を示す図である。基地局10は、制御部110、送受信部120、送受信アンテナ130及び伝送路インターフェース(transmission line interface)140を備えている。なお、制御部110、送受信部120及び送受信アンテナ130及び伝送路インターフェース140は、それぞれ1つ以上が備えられてもよい。
(base station)
FIG. 10 is a diagram showing an example of the configuration of a base station according to an 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.
 なお、本例では、本実施の形態における特徴部分の機能ブロックを主に示しており、基地局10は、無線通信に必要な他の機能ブロックも有すると想定されてもよい。以下で説明する各部の処理の一部は、省略されてもよい。 In this example, the functional block of the characteristic portion in the present embodiment is mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.
 制御部110は、基地局10全体の制御を実施する。制御部110は、本開示に係る技術分野での共通認識に基づいて説明されるコントローラ、制御回路などから構成することができる。 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.
 制御部110は、信号の生成、スケジューリング(例えば、リソース割り当て、マッピング)などを制御してもよい。制御部110は、送受信部120、送受信アンテナ130及び伝送路インターフェース140を用いた送受信、測定などを制御してもよい。制御部110は、信号として送信するデータ、制御情報、系列(sequence)などを生成し、送受信部120に転送してもよい。制御部110は、通信チャネルの呼処理(設定、解放など)、基地局10の状態管理、無線リソースの管理などを行ってもよい。 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, status management of the base station 10, management of radio resources, and the like.
 送受信部120は、ベースバンド(baseband)部121、Radio Frequency(RF)部122、測定部123を含んでもよい。ベースバンド部121は、送信処理部1211及び受信処理部1212を含んでもよい。送受信部120は、本開示に係る技術分野での共通認識に基づいて説明されるトランスミッター/レシーバー、RF回路、ベースバンド回路、フィルタ、位相シフタ(phase shifter)、測定回路、送受信回路などから構成することができる。 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 the common recognition in the technical field according to the present disclosure. be able to.
 送受信部120は、一体の送受信部として構成されてもよいし、送信部及び受信部から構成されてもよい。当該送信部は、送信処理部1211、RF部122から構成されてもよい。当該受信部は、受信処理部1212、RF部122、測定部123から構成されてもよい。 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.
 送受信アンテナ130は、本開示に係る技術分野での共通認識に基づいて説明されるアンテナ、例えばアレイアンテナなどから構成することができる。 The transmitting / receiving antenna 130 can be composed of an antenna described based on the common recognition in the technical field according to the present disclosure, for example, an array antenna.
 送受信部120は、上述の下りリンクチャネル、同期信号、下りリンク参照信号などを送信してもよい。送受信部120は、上述の上りリンクチャネル、上りリンク参照信号などを受信してもよい。 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.
 送受信部120は、デジタルビームフォーミング(例えば、プリコーディング)、アナログビームフォーミング(例えば、位相回転)などを用いて、送信ビーム及び受信ビームの少なくとも一方を形成してもよい。 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.
 送受信部120(送信処理部1211)は、例えば制御部110から取得したデータ、制御情報などに対して、Packet Data Convergence Protocol(PDCP)レイヤの処理、Radio Link Control(RLC)レイヤの処理(例えば、RLC再送制御)、Medium Access Control(MAC)レイヤの処理(例えば、HARQ再送制御)などを行い、送信するビット列を生成してもよい。 The transmission / reception unit 120 (transmission processing unit 1211) 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. RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.
 送受信部120(送信処理部1211)は、送信するビット列に対して、チャネル符号化(誤り訂正符号化を含んでもよい)、変調、マッピング、フィルタ処理、離散フーリエ変換(Discrete Fourier Transform(DFT))処理(必要に応じて)、逆高速フーリエ変換(Inverse Fast Fourier Transform(IFFT))処理、プリコーディング、デジタル-アナログ変換などの送信処理を行い、ベースバンド信号を出力してもよい。 The transmission / reception unit 120 (transmission processing unit 1211) performs channel coding (may include error correction coding), modulation, mapping, filtering, and discrete Fourier transform (Discrete Fourier Transform (DFT)) for the bit string to be transmitted. Processing (if necessary), inverse Fast Fourier Transform (IFFT) processing, precoding, transmission processing such as digital-analog transformation may be performed, and the baseband signal may be output.
 送受信部120(RF部122)は、ベースバンド信号に対して、無線周波数帯への変調、フィルタ処理、増幅などを行い、無線周波数帯の信号を、送受信アンテナ130を介して送信してもよい。 The transmission / reception unit 120 (RF unit 122) 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. ..
 一方、送受信部120(RF部122)は、送受信アンテナ130によって受信された無線周波数帯の信号に対して、増幅、フィルタ処理、ベースバンド信号への復調などを行ってもよい。 On the other hand, the transmission / reception unit 120 (RF unit 122) 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.
 送受信部120(受信処理部1212)は、取得されたベースバンド信号に対して、アナログ-デジタル変換、高速フーリエ変換(Fast Fourier Transform(FFT))処理、逆離散フーリエ変換(Inverse Discrete Fourier Transform(IDFT))処理(必要に応じて)、フィルタ処理、デマッピング、復調、復号(誤り訂正復号を含んでもよい)、MACレイヤ処理、RLCレイヤの処理及びPDCPレイヤの処理などの受信処理を適用し、ユーザデータなどを取得してもよい。 The transmission / reception unit 120 (reception processing unit 1212) performs analog-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) for the acquired baseband signal. )) Processing (if necessary), filtering, decoding, demodulation, decoding (may include error correction decoding), MAC layer processing, RLC layer processing, PDCP layer processing, and other reception processing are applied. User data and the like may be acquired.
 送受信部120(測定部123)は、受信した信号に関する測定を実施してもよい。例えば、測定部123は、受信した信号に基づいて、Radio Resource Management(RRM)測定、Channel State Information(CSI)測定などを行ってもよい。測定部123は、受信電力(例えば、Reference Signal Received Power(RSRP))、受信品質(例えば、Reference Signal Received Quality(RSRQ)、Signal to Interference plus Noise Ratio(SINR)、Signal to Noise Ratio(SNR))、信号強度(例えば、Received Signal Strength Indicator(RSSI))、伝搬路情報(例えば、CSI)などについて測定してもよい。測定結果は、制御部110に出力されてもよい。 The transmission / reception unit 120 (measurement unit 123) may perform measurement on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, or the like based on the received signal. The measuring unit 123 has received power (for example, Reference Signal Received Power (RSRP)) and reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)). , Signal strength (for example, Received Signal Strength Indicator (RSSI)), propagation path information (for example, CSI), and the like may be measured. The measurement result may be output to the control unit 110.
 伝送路インターフェース140は、コアネットワーク30に含まれる装置、他の基地局10などとの間で信号を送受信(バックホールシグナリング)し、ユーザ端末20のためのユーザデータ(ユーザプレーンデータ)、制御プレーンデータなどを取得、伝送などしてもよい。 The transmission line interface 140 transmits / receives signals (backhaul signaling) to / from a device included in the core network 30, another base station 10, etc., and user data (user plane data) for the user terminal 20 and a control plane. Data or the like may be acquired or transmitted.
 なお、本開示における基地局10の送信部及び受信部は、送受信部120、送受信アンテナ130及び伝送路インターフェース140の少なくとも1つによって構成されてもよい。 The transmission unit and the reception unit of the base station 10 in the present disclosure may be composed of at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140.
 送受信部120は、1ショットHARQ-ACKを指示する下り制御情報を送信してもよい。あるいは、送受信部120は、下り共有チャネルのグループ番号を示す情報と、HARQ-ACKフィードバックを行う下り共有チャネルのグループに関する情報と、を含む下り制御情報を送信してもよい。 The transmission / reception unit 120 may transmit downlink control information instructing 1-shot HARQ-ACK. Alternatively, the transmission / reception unit 120 may transmit downlink control information including information indicating the group number of the downlink shared channel and information regarding the group of the downlink shared channel that performs HARQ-ACK feedback.
 制御部110は、下り制御情報で通知するUL送信の優先度に関する情報に基づいて優先度が決定される1ショットHARQ-ACKの受信を制御してもよい。 The control unit 110 may control the reception of the one-shot HARQ-ACK whose priority is determined based on the information regarding the priority of UL transmission notified by the downlink control information.
 あるいは、制御部110は、下り制御情報で通知するUL送信の優先度に関する情報、及びグループに関する情報の少なくとも一つに基づいてフィードバックされるHARQ-ACKの受信を制御してもよい。 Alternatively, the control unit 110 may control the reception of HARQ-ACK that is fed back based on at least one of the information regarding the priority of UL transmission notified by the downlink control information and the information regarding the group.
(ユーザ端末)
 図11は、一実施形態に係るユーザ端末の構成の一例を示す図である。ユーザ端末20は、制御部210、送受信部220及び送受信アンテナ230を備えている。なお、制御部210、送受信部220及び送受信アンテナ230は、それぞれ1つ以上が備えられてもよい。
(User terminal)
FIG. 11 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.
 なお、本例では、本実施の形態における特徴部分の機能ブロックを主に示しており、ユーザ端末20は、無線通信に必要な他の機能ブロックも有すると想定されてもよい。以下で説明する各部の処理の一部は、省略されてもよい。 In this example, the functional block of the feature portion in the present embodiment is mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each part described below may be omitted.
 制御部210は、ユーザ端末20全体の制御を実施する。制御部210は、本開示に係る技術分野での共通認識に基づいて説明されるコントローラ、制御回路などから構成することができる。 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.
 制御部210は、信号の生成、マッピングなどを制御してもよい。制御部210は、送受信部220及び送受信アンテナ230を用いた送受信、測定などを制御してもよい。制御部210は、信号として送信するデータ、制御情報、系列などを生成し、送受信部220に転送してもよい。 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.
 送受信部220は、ベースバンド部221、RF部222、測定部223を含んでもよい。ベースバンド部221は、送信処理部2211、受信処理部2212を含んでもよい。送受信部220は、本開示に係る技術分野での共通認識に基づいて説明されるトランスミッター/レシーバー、RF回路、ベースバンド回路、フィルタ、位相シフタ、測定回路、送受信回路などから構成することができる。 The transmission / reception unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The 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.
 送受信部220は、一体の送受信部として構成されてもよいし、送信部及び受信部から構成されてもよい。当該送信部は、送信処理部2211、RF部222から構成されてもよい。当該受信部は、受信処理部2212、RF部222、測定部223から構成されてもよい。 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.
 送受信アンテナ230は、本開示に係る技術分野での共通認識に基づいて説明されるアンテナ、例えばアレイアンテナなどから構成することができる。 The transmitting / receiving antenna 230 can be composed of an antenna described based on the common recognition in the technical field according to the present disclosure, for example, an array antenna.
 送受信部220は、上述の下りリンクチャネル、同期信号、下りリンク参照信号などを受信してもよい。送受信部220は、上述の上りリンクチャネル、上りリンク参照信号などを送信してもよい。 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.
 送受信部220は、デジタルビームフォーミング(例えば、プリコーディング)、アナログビームフォーミング(例えば、位相回転)などを用いて、送信ビーム及び受信ビームの少なくとも一方を形成してもよい。 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.
 送受信部220(送信処理部2211)は、例えば制御部210から取得したデータ、制御情報などに対して、PDCPレイヤの処理、RLCレイヤの処理(例えば、RLC再送制御)、MACレイヤの処理(例えば、HARQ再送制御)などを行い、送信するビット列を生成してもよい。 The transmission / reception unit 220 (transmission processing unit 2211) processes, for example, PDCP layer processing, RLC layer processing (for example, RLC retransmission control), and MAC layer processing (for example, for data, control information, etc. acquired from the control unit 210). , HARQ retransmission control), etc., to generate a bit string to be transmitted.
 送受信部220(送信処理部2211)は、送信するビット列に対して、チャネル符号化(誤り訂正符号化を含んでもよい)、変調、マッピング、フィルタ処理、DFT処理(必要に応じて)、IFFT処理、プリコーディング、デジタル-アナログ変換などの送信処理を行い、ベースバンド信号を出力してもよい。 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, and the baseband signal may be output.
 なお、DFT処理を適用するか否かは、トランスフォームプリコーディングの設定に基づいてもよい。送受信部220(送信処理部2211)は、あるチャネル(例えば、PUSCH)について、トランスフォームプリコーディングが有効(enabled)である場合、当該チャネルをDFT-s-OFDM波形を用いて送信するために上記送信処理としてDFT処理を行ってもよいし、そうでない場合、上記送信処理としてDFT処理を行わなくてもよい。 Whether or not to apply the DFT process may be based on the transform precoding setting. When the transform precoding is enabled for a channel (for example, PUSCH), the transmission / reception unit 220 (transmission processing unit 2211) 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.
 送受信部220(RF部222)は、ベースバンド信号に対して、無線周波数帯への変調、フィルタ処理、増幅などを行い、無線周波数帯の信号を、送受信アンテナ230を介して送信してもよい。 The transmission / reception unit 220 (RF unit 222) 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. ..
 一方、送受信部220(RF部222)は、送受信アンテナ230によって受信された無線周波数帯の信号に対して、増幅、フィルタ処理、ベースバンド信号への復調などを行ってもよい。 On the other hand, the transmission / reception unit 220 (RF unit 222) 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.
 送受信部220(受信処理部2212)は、取得されたベースバンド信号に対して、アナログ-デジタル変換、FFT処理、IDFT処理(必要に応じて)、フィルタ処理、デマッピング、復調、復号(誤り訂正復号を含んでもよい)、MACレイヤ処理、RLCレイヤの処理及びPDCPレイヤの処理などの受信処理を適用し、ユーザデータなどを取得してもよい。 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.
 送受信部220(測定部223)は、受信した信号に関する測定を実施してもよい。例えば、測定部223は、受信した信号に基づいて、RRM測定、CSI測定などを行ってもよい。測定部223は、受信電力(例えば、RSRP)、受信品質(例えば、RSRQ、SINR、SNR)、信号強度(例えば、RSSI)、伝搬路情報(例えば、CSI)などについて測定してもよい。測定結果は、制御部210に出力されてもよい。 The transmission / reception unit 220 (measurement unit 223) may perform measurement on the received signal. For example, 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.
 なお、本開示におけるユーザ端末20の送信部及び受信部は、送受信部220及び送受信アンテナ230の少なくとも1つによって構成されてもよい。 The transmitting unit and the receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmission / reception unit 220 and the transmission / reception antenna 230.
 送受信部220は、1ショットHARQ-ACKを指示する下り制御情報を受信してもよい。あるいは、送受信部220は、下り共有チャネルのグループ番号を示す情報と、HARQ-ACKのフィードバックを行う下り共有チャネルのグループに関する情報と、を含む下り制御情報を受信してもよい。 The transmission / reception unit 220 may receive downlink control information instructing 1-shot HARQ-ACK. Alternatively, the transmission / reception unit 220 may receive downlink control information including information indicating the group number of the downlink shared channel and information regarding the group of the downlink shared channel that provides feedback of HARQ-ACK.
 制御部210は、下り制御情報から取得できるUL送信の優先度に関する情報に基づいて、1ショットHARQ-ACKの優先度を判断してもよい。例えば、制御部210は、1ショットHARQ-ACKで指定される1以上のHARQ-ACKについて、各HARQ-ACKの優先度に関わらずフィードバックするように制御してもよい。制御部210は、1ショットHARQ-ACKで指定される1以上のHARQ-ACKについて、各HARQ-ACKの優先度に基づいてフィードバックするHARQ-ACKを判断してもよい。制御部210は、下り制御情報に含まれるUL送信の優先度を指定する情報、及び下り制御情報のフォーマットの少なくとも一つに基づいて、1ショットHARQ-ACKの優先度を判断してもよい。 The control unit 210 may determine the priority of the one-shot HARQ-ACK based on the information regarding the priority of UL transmission that can be acquired from the downlink control information. For example, the control unit 210 may control one or more HARQ-ACKs specified by the one-shot HARQ-ACK so as to feed back regardless of the priority of each HARQ-ACK. The control unit 210 may determine the HARQ-ACK to be fed back based on the priority of each HARQ-ACK for one or more HARQ-ACKs specified by the one-shot HARQ-ACK. The control unit 210 may determine the priority of the one-shot HARQ-ACK based on at least one of the information that specifies the priority of UL transmission included in the downlink control information and the format of the downlink control information.
 制御部210は、下り制御情報から取得できるUL送信の優先度に関する情報、及びグループに関する情報の少なくとも一つに基づいてHARQ-ACKのフィードバックを制御してもよい。同一のグループに対して、優先度が異なる下り共有チャネル、及び優先度が異なるHARQ-ACKの少なくとも一つの設定がサポートされてもよい。同一のグループに対して、優先度が同一の下り共有チャネル、及び優先度が同一のHARQ-ACKの少なくとも一つが設定されてもよい。制御部210は、同一のグループに対して、優先度が同一のHARQ-ACKをフィードバックするように制御してもよい。 The control unit 210 may control the feedback of HARQ-ACK based on at least one of the information regarding the priority of UL transmission that can be acquired from the downlink control information and the information regarding the group. At least one configuration of downlink shared channels with different priorities and HARQ-ACK with different priorities may be supported for the same group. At least one of a downlink shared channel having the same priority and HARQ-ACK having the same priority may be set for the same group. The control unit 210 may control to feed back HARQ-ACK having the same priority to the same group.
(ハードウェア構成)
 なお、上記実施形態の説明に用いたブロック図は、機能単位のブロックを示している。これらの機能ブロック(構成部)は、ハードウェア及びソフトウェアの少なくとも一方の任意の組み合わせによって実現される。また、各機能ブロックの実現方法は特に限定されない。すなわち、各機能ブロックは、物理的又は論理的に結合した1つの装置を用いて実現されてもよいし、物理的又は論理的に分離した2つ以上の装置を直接的又は間接的に(例えば、有線、無線などを用いて)接続し、これら複数の装置を用いて実現されてもよい。機能ブロックは、上記1つの装置又は上記複数の装置にソフトウェアを組み合わせて実現されてもよい。
(Hardware configuration)
The block diagram used in the description of the above embodiment shows a block of functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Further, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or two or more physically or logically separated devices can be directly or indirectly (eg, for example). , Wired, wireless, etc.) and may be realized using these plurality of devices. The functional block may be realized by combining the software with the one device or the plurality of devices.
 ここで、機能には、判断、決定、判定、計算、算出、処理、導出、調査、探索、確認、受信、送信、出力、アクセス、解決、選択、選定、確立、比較、想定、期待、みなし、報知(broadcasting)、通知(notifying)、通信(communicating)、転送(forwarding)、構成(configuring)、再構成(reconfiguring)、割り当て(allocating、mapping)、割り振り(assigning)などがあるが、これらに限られない。例えば、送信を機能させる機能ブロック(構成部)は、送信部(transmitting unit)、送信機(transmitter)などと呼称されてもよい。いずれも、上述したとおり、実現方法は特に限定されない。 Here, 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. Not limited. For example, a functional block (configuration unit) for functioning transmission may be referred to as a transmitting unit (transmitting unit), a transmitter (transmitter), or the like. In each case, as described above, the realization method is not particularly limited.
 例えば、本開示の一実施形態における基地局、ユーザ端末などは、本開示の無線通信方法の処理を行うコンピュータとして機能してもよい。図12は、一実施形態に係る基地局及びユーザ端末のハードウェア構成の一例を示す図である。上述の基地局10及びユーザ端末20は、物理的には、プロセッサ1001、メモリ1002、ストレージ1003、通信装置1004、入力装置1005、出力装置1006、バス1007などを含むコンピュータ装置として構成されてもよい。 For example, 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. 12 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. ..
 なお、本開示において、装置、回路、デバイス、部(section)、ユニットなどの文言は、互いに読み替えることができる。基地局10及びユーザ端末20のハードウェア構成は、図に示した各装置を1つ又は複数含むように構成されてもよいし、一部の装置を含まずに構成されてもよい。 In this disclosure, the terms of devices, circuits, devices, sections, units, etc. can be read as each other. 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.
 例えば、プロセッサ1001は1つだけ図示されているが、複数のプロセッサがあってもよい。また、処理は、1のプロセッサによって実行されてもよいし、処理が同時に、逐次に、又はその他の手法を用いて、2以上のプロセッサによって実行されてもよい。なお、プロセッサ1001は、1以上のチップによって実装されてもよい。 For example, although only one processor 1001 is shown, there 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.
 基地局10及びユーザ端末20における各機能は、例えば、プロセッサ1001、メモリ1002などのハードウェア上に所定のソフトウェア(プログラム)を読み込ませることによって、プロセッサ1001が演算を行い、通信装置1004を介する通信を制御したり、メモリ1002及びストレージ1003におけるデータの読み出し及び書き込みの少なくとも一方を制御したりすることによって実現される。 For each function in the base station 10 and the user terminal 20, for example, by loading predetermined software (program) on hardware such as the processor 1001 and the memory 1002, the processor 1001 performs an operation and communicates via the communication device 1004. It is realized by controlling at least one of reading and writing of data in the memory 1002 and the storage 1003.
 プロセッサ1001は、例えば、オペレーティングシステムを動作させてコンピュータ全体を制御する。プロセッサ1001は、周辺装置とのインターフェース、制御装置、演算装置、レジスタなどを含む中央処理装置(Central Processing Unit(CPU))によって構成されてもよい。例えば、上述の制御部110(210)、送受信部120(220)などの少なくとも一部は、プロセッサ1001によって実現されてもよい。 The processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, and the like. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), and the like may be realized by the processor 1001.
 また、プロセッサ1001は、プログラム(プログラムコード)、ソフトウェアモジュール、データなどを、ストレージ1003及び通信装置1004の少なくとも一方からメモリ1002に読み出し、これらに従って各種の処理を実行する。プログラムとしては、上述の実施形態において説明した動作の少なくとも一部をコンピュータに実行させるプログラムが用いられる。例えば、制御部110(210)は、メモリ1002に格納され、プロセッサ1001において動作する制御プログラムによって実現されてもよく、他の機能ブロックについても同様に実現されてもよい。 Further, 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. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiment is used. For example, the control unit 110 (210) 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.
 メモリ1002は、コンピュータ読み取り可能な記録媒体であり、例えば、Read Only Memory(ROM)、Erasable Programmable ROM(EPROM)、Electrically EPROM(EEPROM)、Random Access Memory(RAM)、その他の適切な記憶媒体の少なくとも1つによって構成されてもよい。メモリ1002は、レジスタ、キャッシュ、メインメモリ(主記憶装置)などと呼ばれてもよい。メモリ1002は、本開示の一実施形態に係る無線通信方法を実施するために実行可能なプログラム(プログラムコード)、ソフトウェアモジュールなどを保存することができる。 The memory 1002 is a computer-readable recording medium, for example, at least a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), or any other suitable storage medium. It may be composed of one. The memory 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like. The memory 1002 can store a program (program code), a software module, or the like that can be executed to implement the wireless communication method according to the embodiment of the present disclosure.
 ストレージ1003は、コンピュータ読み取り可能な記録媒体であり、例えば、フレキシブルディスク、フロッピー(登録商標)ディスク、光磁気ディスク(例えば、コンパクトディスク(Compact Disc ROM(CD-ROM)など)、デジタル多用途ディスク、Blu-ray(登録商標)ディスク)、リムーバブルディスク、ハードディスクドライブ、スマートカード、フラッシュメモリデバイス(例えば、カード、スティック、キードライブ)、磁気ストライプ、データベース、サーバ、その他の適切な記憶媒体の少なくとも1つによって構成されてもよい。ストレージ1003は、補助記憶装置と呼ばれてもよい。 The storage 1003 is a computer-readable recording medium, and is, for example, a flexible disk, a floppy disk (registered trademark) disk, an optical magnetic disk (for example, a compact disc (Compact Disc ROM (CD-ROM), etc.), a digital versatile disk, etc.). At least one of Blu-ray® discs), removable discs, optical disc drives, smart cards, flash memory devices (eg cards, sticks, key drives), magnetic stripes, databases, servers and other suitable storage media. May be configured by. The storage 1003 may be referred to as an auxiliary storage device.
 通信装置1004は、有線ネットワーク及び無線ネットワークの少なくとも一方を介してコンピュータ間の通信を行うためのハードウェア(送受信デバイス)であり、例えばネットワークデバイス、ネットワークコントローラ、ネットワークカード、通信モジュールなどともいう。通信装置1004は、例えば周波数分割複信(Frequency Division Duplex(FDD))及び時分割複信(Time Division Duplex(TDD))の少なくとも一方を実現するために、高周波スイッチ、デュプレクサ、フィルタ、周波数シンセサイザなどを含んで構成されてもよい。例えば、上述の送受信部120(220)、送受信アンテナ130(230)などは、通信装置1004によって実現されてもよい。送受信部120(220)は、送信部120a(220a)と受信部120b(220b)とで、物理的に又は論理的に分離された実装がなされてもよい。 The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 has, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (Frequency Division Duplex (FDD)) and time division duplex (Time Division Duplex (TDD)). May be configured to include. For example, the transmission / reception unit 120 (220), the transmission / reception antenna 130 (230), and the like described above may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be physically or logically separated by the transmission unit 120a (220a) and the reception unit 120b (220b).
 入力装置1005は、外部からの入力を受け付ける入力デバイス(例えば、キーボード、マウス、マイクロフォン、スイッチ、ボタン、センサなど)である。出力装置1006は、外部への出力を実施する出力デバイス(例えば、ディスプレイ、スピーカー、Light Emitting Diode(LED)ランプなど)である。なお、入力装置1005及び出力装置1006は、一体となった構成(例えば、タッチパネル)であってもよい。 The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
 また、プロセッサ1001、メモリ1002などの各装置は、情報を通信するためのバス1007によって接続される。バス1007は、単一のバスを用いて構成されてもよいし、装置間ごとに異なるバスを用いて構成されてもよい。 Further, 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.
 また、基地局10及びユーザ端末20は、マイクロプロセッサ、デジタル信号プロセッサ(Digital Signal Processor(DSP))、Application Specific Integrated Circuit(ASIC)、Programmable Logic Device(PLD)、Field Programmable Gate Array(FPGA)などのハードウェアを含んで構成されてもよく、当該ハードウェアを用いて各機能ブロックの一部又は全てが実現されてもよい。例えば、プロセッサ1001は、これらのハードウェアの少なくとも1つを用いて実装されてもよい。 Further, 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.
(変形例)
 なお、本開示において説明した用語及び本開示の理解に必要な用語については、同一の又は類似する意味を有する用語と置き換えてもよい。例えば、チャネル、シンボル及び信号(シグナル又はシグナリング)は、互いに読み替えられてもよい。また、信号はメッセージであってもよい。参照信号(reference signal)は、RSと略称することもでき、適用される標準によってパイロット(Pilot)、パイロット信号などと呼ばれてもよい。また、コンポーネントキャリア(Component Carrier(CC))は、セル、周波数キャリア、キャリア周波数などと呼ばれてもよい。
(Modification example)
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. For example, channels, symbols and signals (signals or signaling) may be read interchangeably. Also, 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. Further, the component carrier (CC) may be referred to as a cell, a frequency carrier, a carrier frequency, or the like.
 無線フレームは、時間領域において1つ又は複数の期間(フレーム)によって構成されてもよい。無線フレームを構成する当該1つ又は複数の各期間(フレーム)は、サブフレームと呼ばれてもよい。さらに、サブフレームは、時間領域において1つ又は複数のスロットによって構成されてもよい。サブフレームは、ニューメロロジー(numerology)に依存しない固定の時間長(例えば、1ms)であってもよい。 The wireless frame may be configured by one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the radio frame may be referred to as a subframe. Further, the subframe may be composed of one or more slots in the time domain. The subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.
 ここで、ニューメロロジーは、ある信号又はチャネルの送信及び受信の少なくとも一方に適用される通信パラメータであってもよい。ニューメロロジーは、例えば、サブキャリア間隔(SubCarrier Spacing(SCS))、帯域幅、シンボル長、サイクリックプレフィックス長、送信時間間隔(Transmission Time Interval(TTI))、TTIあたりのシンボル数、無線フレーム構成、送受信機が周波数領域において行う特定のフィルタリング処理、送受信機が時間領域において行う特定のウィンドウイング処理などの少なくとも1つを示してもよい。 Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel. Numerology is, for example, subcarrier interval (SubCarrier Spacing (SCS)), bandwidth, symbol length, cyclic prefix length, transmission time interval (Transmission Time Interval (TTI)), number of symbols per TTI, wireless frame configuration. , A specific filtering process performed by the transmitter / receiver in the frequency domain, a specific windowing process performed by the transmitter / receiver in the time domain, and the like may be indicated.
 スロットは、時間領域において1つ又は複数のシンボル(Orthogonal Frequency Division Multiplexing(OFDM)シンボル、Single Carrier Frequency Division Multiple Access(SC-FDMA)シンボルなど)によって構成されてもよい。また、スロットは、ニューメロロジーに基づく時間単位であってもよい。 The slot may be composed of one or more symbols in the time domain (Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol, etc.). Further, the slot may be a time unit based on numerology.
 スロットは、複数のミニスロットを含んでもよい。各ミニスロットは、時間領域において1つ又は複数のシンボルによって構成されてもよい。また、ミニスロットは、サブスロットと呼ばれてもよい。ミニスロットは、スロットよりも少ない数のシンボルによって構成されてもよい。ミニスロットより大きい時間単位で送信されるPDSCH(又はPUSCH)は、PDSCH(PUSCH)マッピングタイプAと呼ばれてもよい。ミニスロットを用いて送信されるPDSCH(又はPUSCH)は、PDSCH(PUSCH)マッピングタイプBと呼ばれてもよい。 The slot may include a plurality of mini slots. Each minislot may be composed of one or more symbols in the time domain. Further, the mini slot may be referred to as a sub slot. The 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 use different names corresponding to each. The time units such as frames, subframes, slots, mini slots, and symbols in the present disclosure may be read as each other.
 例えば、1サブフレームはTTIと呼ばれてもよいし、複数の連続したサブフレームがTTIと呼ばれてよいし、1スロット又は1ミニスロットがTTIと呼ばれてもよい。つまり、サブフレーム及びTTIの少なくとも一方は、既存のLTEにおけるサブフレーム(1ms)であってもよいし、1msより短い期間(例えば、1-13シンボル)であってもよいし、1msより長い期間であってもよい。なお、TTIを表す単位は、サブフレームではなくスロット、ミニスロットなどと呼ばれてもよい。 For example, one subframe may be called TTI, a plurality of consecutive subframes may be called TTI, and one slot or one minislot may be called TTI. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms. May be. The unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.
 ここで、TTIは、例えば、無線通信におけるスケジューリングの最小時間単位のことをいう。例えば、LTEシステムでは、基地局が各ユーザ端末に対して、無線リソース(各ユーザ端末において使用することが可能な周波数帯域幅、送信電力など)を、TTI単位で割り当てるスケジューリングを行う。なお、TTIの定義はこれに限られない。 Here, TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in the LTE system, the base station schedules each user terminal to allocate radio resources (frequency bandwidth that can be used in each user terminal, transmission power, etc.) in TTI units. The definition of TTI is not limited to this.
 TTIは、チャネル符号化されたデータパケット(トランスポートブロック)、コードブロック、コードワードなどの送信時間単位であってもよいし、スケジューリング、リンクアダプテーションなどの処理単位となってもよい。なお、TTIが与えられたとき、実際にトランスポートブロック、コードブロック、コードワードなどがマッピングされる時間区間(例えば、シンボル数)は、当該TTIよりも短くてもよい。 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. When a TTI is given, the time interval (for example, the number of symbols) to which the transport block, code block, code word, etc. are actually mapped may be shorter than the TTI.
 なお、1スロット又は1ミニスロットがTTIと呼ばれる場合、1以上のTTI(すなわち、1以上のスロット又は1以上のミニスロット)が、スケジューリングの最小時間単位となってもよい。また、当該スケジューリングの最小時間単位を構成するスロット数(ミニスロット数)は制御されてもよい。 When one slot or one mini slot is called TTI, one or more TTIs (that is, one or more slots or one or more mini slots) 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.
 1msの時間長を有するTTIは、通常TTI(3GPP Rel.8-12におけるTTI)、ノーマルTTI、ロングTTI、通常サブフレーム、ノーマルサブフレーム、ロングサブフレーム、スロットなどと呼ばれてもよい。通常TTIより短いTTIは、短縮TTI、ショートTTI、部分TTI(partial又はfractional TTI)、短縮サブフレーム、ショートサブフレーム、ミニスロット、サブスロット、スロットなどと呼ばれてもよい。 A TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in 3GPP Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like. A TTI shorter than a normal TTI may be referred to as a shortened TTI, a short TTI, a partial TTI (partial or fractional TTI), a shortened subframe, a short subframe, a minislot, a subslot, a slot, and the like.
 なお、ロングTTI(例えば、通常TTI、サブフレームなど)は、1msを超える時間長を有するTTIで読み替えてもよいし、ショートTTI(例えば、短縮TTIなど)は、ロングTTIのTTI長未満かつ1ms以上のTTI長を有するTTIで読み替えてもよい。 The long TTI (eg, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and the short TTI (eg, shortened TTI, etc.) may be read as a TTI less than the TTI length of the long TTI and 1 ms. It may be read as TTI having the above TTI length.
 リソースブロック(Resource Block(RB))は、時間領域及び周波数領域のリソース割当単位であり、周波数領域において、1つ又は複数個の連続した副搬送波(サブキャリア(subcarrier))を含んでもよい。RBに含まれるサブキャリアの数は、ニューメロロジーに関わらず同じであってもよく、例えば12であってもよい。RBに含まれるサブキャリアの数は、ニューメロロジーに基づいて決定されてもよい。 A resource block (Resource Block (RB)) 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.
 また、RBは、時間領域において、1つ又は複数個のシンボルを含んでもよく、1スロット、1ミニスロット、1サブフレーム又は1TTIの長さであってもよい。1TTI、1サブフレームなどは、それぞれ1つ又は複数のリソースブロックによって構成されてもよい。 Further, 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.
 なお、1つ又は複数のRBは、物理リソースブロック(Physical RB(PRB))、サブキャリアグループ(Sub-Carrier Group(SCG))、リソースエレメントグループ(Resource Element Group(REG))、PRBペア、RBペアなどと呼ばれてもよい。 In addition, 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.
 また、リソースブロックは、1つ又は複数のリソースエレメント(Resource Element(RE))によって構成されてもよい。例えば、1REは、1サブキャリア及び1シンボルの無線リソース領域であってもよい。 Further, the resource block may be composed of one or a plurality of resource elements (Resource Element (RE)). For example, 1RE may be a radio resource area of 1 subcarrier and 1 symbol.
 帯域幅部分(Bandwidth Part(BWP))(部分帯域幅などと呼ばれてもよい)は、あるキャリアにおいて、あるニューメロロジー用の連続する共通RB(common resource blocks)のサブセットのことを表してもよい。ここで、共通RBは、当該キャリアの共通参照ポイントを基準としたRBのインデックスによって特定されてもよい。PRBは、あるBWPで定義され、当該BWP内で番号付けされてもよい。 Bandwidth Part (BWP) (which may also be called partial bandwidth) represents a subset of consecutive common resource blocks (RBs) for a neurology in a carrier. May be good. Here, 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.
 BWPには、UL BWP(UL用のBWP)と、DL BWP(DL用のBWP)とが含まれてもよい。UEに対して、1キャリア内に1つ又は複数のBWPが設定されてもよい。 The BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be set in one carrier for the UE.
 設定されたBWPの少なくとも1つがアクティブであってもよく、UEは、アクティブなBWPの外で所定の信号/チャネルを送受信することを想定しなくてもよい。なお、本開示における「セル」、「キャリア」などは、「BWP」で読み替えられてもよい。 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. In addition, "cell", "carrier" and the like in this disclosure may be read as "BWP".
 なお、上述した無線フレーム、サブフレーム、スロット、ミニスロット及びシンボルなどの構造は例示に過ぎない。例えば、無線フレームに含まれるサブフレームの数、サブフレーム又は無線フレームあたりのスロットの数、スロット内に含まれるミニスロットの数、スロット又はミニスロットに含まれるシンボル及びRBの数、RBに含まれるサブキャリアの数、並びにTTI内のシンボル数、シンボル長、サイクリックプレフィックス(Cyclic Prefix(CP))長などの構成は、様々に変更することができる。 Note that the above-mentioned structures such as wireless frames, subframes, slots, mini-slots, and symbols are merely examples. For example, the number of subframes contained in a radio frame, the number of slots per subframe or radioframe, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in the RB. The number of subcarriers, the number of symbols in TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.
 また、本開示において説明した情報、パラメータなどは、絶対値を用いて表されてもよいし、所定の値からの相対値を用いて表されてもよいし、対応する別の情報を用いて表されてもよい。例えば、無線リソースは、所定のインデックスによって指示されてもよい。 Further, 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, the radio resource may be indicated by a given index.
 本開示においてパラメータなどに使用する名称は、いかなる点においても限定的な名称ではない。さらに、これらのパラメータを使用する数式などは、本開示において明示的に開示したものと異なってもよい。様々なチャネル(PUCCH、PDCCHなど)及び情報要素は、あらゆる好適な名称によって識別できるので、これらの様々なチャネル及び情報要素に割り当てている様々な名称は、いかなる点においても限定的な名称ではない。 The names used for parameters, etc. in this disclosure are not limited in any respect. Further, mathematical formulas and the like using these parameters may differ from those expressly disclosed in the present disclosure. Since the various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not limiting in any way. ..
 本開示において説明した情報、信号などは、様々な異なる技術のいずれかを使用して表されてもよい。例えば、上記の説明全体に渡って言及され得るデータ、命令、コマンド、情報、信号、ビット、シンボル、チップなどは、電圧、電流、電磁波、磁界若しくは磁性粒子、光場若しくは光子、又はこれらの任意の組み合わせによって表されてもよい。 The information, signals, etc. described in this disclosure may be represented using any of a variety of different techniques. For example, 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.
 また、情報、信号などは、上位レイヤから下位レイヤ及び下位レイヤから上位レイヤの少なくとも一方へ出力され得る。情報、信号などは、複数のネットワークノードを介して入出力されてもよい。 In addition, 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.
 情報の通知は、本開示において説明した態様/実施形態に限られず、他の方法を用いて行われてもよい。例えば、本開示における情報の通知は、物理レイヤシグナリング(例えば、下り制御情報(Downlink Control Information(DCI))、上り制御情報(Uplink Control Information(UCI)))、上位レイヤシグナリング(例えば、Radio Resource Control(RRC)シグナリング、ブロードキャスト情報(マスタ情報ブロック(Master Information Block(MIB))、システム情報ブロック(System Information Block(SIB))など)、Medium Access Control(MAC)シグナリング)、その他の信号又はこれらの組み合わせによって実施されてもよい。 The notification of information is not limited to the embodiment / embodiment described in the present disclosure, and may be performed by using another method. For example, 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.
 なお、物理レイヤシグナリングは、Layer 1/Layer 2(L1/L2)制御情報(L1/L2制御信号)、L1制御情報(L1制御信号)などと呼ばれてもよい。また、RRCシグナリングは、RRCメッセージと呼ばれてもよく、例えば、RRC接続セットアップ(RRC Connection Setup)メッセージ、RRC接続再構成(RRC Connection Reconfiguration)メッセージなどであってもよい。また、MACシグナリングは、例えば、MAC制御要素(MAC Control Element(CE))を用いて通知されてもよい。 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. Further, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like. Further, MAC signaling may be notified using, for example, a MAC control element (MAC Control Element (CE)).
 また、所定の情報の通知(例えば、「Xであること」の通知)は、明示的な通知に限られず、暗示的に(例えば、当該所定の情報の通知を行わないことによって又は別の情報の通知によって)行われてもよい。 In addition, the notification of predetermined information (for example, the notification of "being X") 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).
 判定は、1ビットで表される値(0か1か)によって行われてもよいし、真(true)又は偽(false)で表される真偽値(boolean)によって行われてもよいし、数値の比較(例えば、所定の値との比較)によって行われてもよい。 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 called software, firmware, middleware, microcode, hardware description language, or other names, 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.
 また、ソフトウェア、命令、情報などは、伝送媒体を介して送受信されてもよい。例えば、ソフトウェアが、有線技術(同軸ケーブル、光ファイバケーブル、ツイストペア、デジタル加入者回線(Digital Subscriber Line(DSL))など)及び無線技術(赤外線、マイクロ波など)の少なくとも一方を使用してウェブサイト、サーバ、又は他のリモートソースから送信される場合、これらの有線技術及び無線技術の少なくとも一方は、伝送媒体の定義内に含まれる。 Further, software, instructions, information, etc. may be transmitted and received via 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.). When transmitted from a server, or other remote source, at least one of these wired and wireless technologies is included within the definition of transmission medium.
 本開示において使用する「システム」及び「ネットワーク」という用語は、互換的に使用され得る。「ネットワーク」は、ネットワークに含まれる装置(例えば、基地局)のことを意味してもよい。 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.
 本開示において、「プリコーディング」、「プリコーダ」、「ウェイト(プリコーディングウェイト)」、「擬似コロケーション(Quasi-Co-Location(QCL))」、「Transmission Configuration Indication state(TCI状態)」、「空間関係(spatial relation)」、「空間ドメインフィルタ(spatial domain filter)」、「送信電力」、「位相回転」、「アンテナポート」、「アンテナポートグル-プ」、「レイヤ」、「レイヤ数」、「ランク」、「リソース」、「リソースセット」、「リソースグループ」、「ビーム」、「ビーム幅」、「ビーム角度」、「アンテナ」、「アンテナ素子」、「パネル」などの用語は、互換的に使用され得る。 In the present disclosure, "precoding", "precoder", "weight (precoding weight)", "pseudo-colocation (Quasi-Co-Location (QCL))", "Transmission Configuration Indication state (TCI 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 for
 本開示においては、「基地局(Base Station(BS))」、「無線基地局」、「固定局(fixed station)」、「NodeB」、「eNB(eNodeB)」、「gNB(gNodeB)」、「アクセスポイント(access point)」、「送信ポイント(Transmission Point(TP))」、「受信ポイント(Reception Point(RP))」、「送受信ポイント(Transmission/Reception Point(TRP))」、「パネル」、「セル」、「セクタ」、「セルグループ」、「キャリア」、「コンポーネントキャリア」などの用語は、互換的に使用され得る。基地局は、マクロセル、スモールセル、フェムトセル、ピコセルなどの用語で呼ばれる場合もある。 In this disclosure, "base station (BS)", "wireless base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission point (Transmission Point (TP))", "Reception point (Reception Point (RP))", "Transmission / reception point (Transmission / Reception Point (TRP))", "Panel" , "Cell", "sector", "cell group", "carrier", "component carrier" and the like may be used interchangeably. Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.
 基地局は、1つ又は複数(例えば、3つ)のセルを収容することができる。基地局が複数のセルを収容する場合、基地局のカバレッジエリア全体は複数のより小さいエリアに区分でき、各々のより小さいエリアは、基地局サブシステム(例えば、屋内用の小型基地局(Remote Radio Head(RRH)))によって通信サービスを提供することもできる。「セル」又は「セクタ」という用語は、このカバレッジにおいて通信サービスを行う基地局及び基地局サブシステムの少なくとも一方のカバレッジエリアの一部又は全体を指す。 The base station can accommodate one or more (eg, 3) cells. When 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))). The term "cell" or "sector" refers to a portion or all of the coverage area of at least one of a base station and a base station subsystem that provides communication services in this coverage.
 本開示においては、「移動局(Mobile Station(MS))」、「ユーザ端末(user terminal)」、「ユーザ装置(User Equipment(UE))」、「端末」などの用語は、互換的に使用され得る。 In this disclosure, terms such as "mobile station (MS)", "user terminal", "user equipment (UE)", and "terminal" are used interchangeably. Can be done.
 移動局は、加入者局、モバイルユニット、加入者ユニット、ワイヤレスユニット、リモートユニット、モバイルデバイス、ワイヤレスデバイス、ワイヤレス通信デバイス、リモートデバイス、モバイル加入者局、アクセス端末、モバイル端末、ワイヤレス端末、リモート端末、ハンドセット、ユーザエージェント、モバイルクライアント、クライアント又はいくつかの他の適切な用語で呼ばれる場合もある。 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.
 基地局及び移動局の少なくとも一方は、送信装置、受信装置、無線通信装置などと呼ばれてもよい。なお、基地局及び移動局の少なくとも一方は、移動体に搭載されたデバイス、移動体自体などであってもよい。当該移動体は、乗り物(例えば、車、飛行機など)であってもよいし、無人で動く移動体(例えば、ドローン、自動運転車など)であってもよいし、ロボット(有人型又は無人型)であってもよい。なお、基地局及び移動局の少なくとも一方は、必ずしも通信動作時に移動しない装置も含む。例えば、基地局及び移動局の少なくとも一方は、センサなどのInternet of Things(IoT)機器であってもよい。 At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, or the like. At least one of the base station and the mobile station may be a device mounted on the mobile body, a mobile body itself, or the like. The moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ) May be. It should be noted that at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
 また、本開示における基地局は、ユーザ端末で読み替えてもよい。例えば、基地局及びユーザ端末間の通信を、複数のユーザ端末間の通信(例えば、Device-to-Device(D2D)、Vehicle-to-Everything(V2X)などと呼ばれてもよい)に置き換えた構成について、本開示の各態様/実施形態を適用してもよい。この場合、上述の基地局10が有する機能をユーザ端末20が有する構成としてもよい。また、「上り」、「下り」などの文言は、端末間通信に対応する文言(例えば、「サイド(side)」)で読み替えられてもよい。例えば、上りチャネル、下りチャネルなどは、サイドチャネルで読み替えられてもよい。 Further, the base station in the present disclosure may be read by the user terminal. For example, 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.). Each aspect / embodiment of the present disclosure may be applied to the configuration. In this case, the user terminal 20 may have the function of the base station 10 described above. Further, the words such as "up" and "down" may be read as words corresponding to the communication between terminals (for example, "side"). For example, the upstream channel, the downstream channel, and the like may be read as a side channel.
 同様に、本開示におけるユーザ端末は、基地局で読み替えてもよい。この場合、上述のユーザ端末20が有する機能を基地局10が有する構成としてもよい。 Similarly, the user terminal in the present disclosure may be read as a base station. In this case, the base station 10 may have the functions of the user terminal 20 described above.
 本開示において、基地局によって行われるとした動作は、場合によってはその上位ノード(upper node)によって行われることもある。基地局を有する1つ又は複数のネットワークノード(network nodes)を含むネットワークにおいて、端末との通信のために行われる様々な動作は、基地局、基地局以外の1つ以上のネットワークノード(例えば、Mobility Management Entity(MME)、Serving-Gateway(S-GW)などが考えられるが、これらに限られない)又はこれらの組み合わせによって行われ得ることは明らかである。 In the present disclosure, the operation performed by the base station may be performed by its upper node (upper node) in some cases. In a network including one or more network nodes having a base station, various operations performed for communication with a terminal are a base station, one or more network nodes other than the base station (for example,). Mobility Management Entity (MME), Serving-Gateway (S-GW), etc. can be considered, but it is not limited to these), or it is clear that it can be performed by a combination thereof.
 本開示において説明した各態様/実施形態は単独で用いてもよいし、組み合わせて用いてもよいし、実行に伴って切り替えて用いてもよい。また、本開示において説明した各態様/実施形態の処理手順、シーケンス、フローチャートなどは、矛盾の無い限り、順序を入れ替えてもよい。例えば、本開示において説明した方法については、例示的な順序を用いて様々なステップの要素を提示しており、提示した特定の順序に限定されない。 Each aspect / embodiment described in the present disclosure may be used alone, in combination, or may be switched and used according to the execution. Further, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be changed as long as there is no contradiction. For example, the methods described in the present disclosure present elements of various steps using exemplary order, and are not limited to the particular order presented.
 本開示において説明した各態様/実施形態は、Long Term Evolution(LTE)、LTE-Advanced(LTE-A)、LTE-Beyond(LTE-B)、SUPER 3G、IMT-Advanced、4th generation mobile communication system(4G)、5th generation mobile communication system(5G)、6th generation mobile communication system(6G)、xth generation mobile communication system(xG)(xG(xは、例えば整数、小数))、Future Radio Access(FRA)、New-Radio Access Technology(RAT)、New Radio(NR)、New radio access(NX)、Future generation radio access(FX)、Global System for Mobile communications(GSM(登録商標))、CDMA2000、Ultra Mobile Broadband(UMB)、IEEE 802.11(Wi-Fi(登録商標))、IEEE 802.16(WiMAX(登録商標))、IEEE 802.20、Ultra-WideBand(UWB)、Bluetooth(登録商標)、その他の適切な無線通信方法を利用するシステム、これらに基づいて拡張された次世代システムなどに適用されてもよい。また、複数のシステムが組み合わされて(例えば、LTE又はLTE-Aと、5Gとの組み合わせなど)適用されてもよい。 Each aspect / embodiment described in the present disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system ( 4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a fraction)), Future Radio Access (FRA), New -Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB) , LTE 802.11 (Wi-Fi®), LTE 802.16 (WiMAX®), LTE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other suitable radios. It may be applied to a system using a communication method, a next-generation system extended based on these, and the like. Further, a plurality of systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).
 本開示において使用する「に基づいて」という記載は、別段に明記されていない限り、「のみに基づいて」を意味しない。言い換えれば、「に基づいて」という記載は、「のみに基づいて」と「に少なくとも基づいて」の両方を意味する。 The statement "based on" used in this disclosure does not mean "based on" unless otherwise stated. In other words, the statement "based on" means both "based only" and "at least based on".
 本開示において使用する「第1の」、「第2の」などの呼称を使用した要素へのいかなる参照も、それらの要素の量又は順序を全般的に限定しない。これらの呼称は、2つ以上の要素間を区別する便利な方法として本開示において使用され得る。したがって、第1及び第2の要素の参照は、2つの要素のみが採用され得ること又は何らかの形で第1の要素が第2の要素に先行しなければならないことを意味しない。 Any reference 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)」という用語は、多種多様な動作を包含する場合がある。例えば、「判断(決定)」は、判定(judging)、計算(calculating)、算出(computing)、処理(processing)、導出(deriving)、調査(investigating)、探索(looking up、search、inquiry)(例えば、テーブル、データベース又は別のデータ構造での探索)、確認(ascertaining)などを「判断(決定)」することであるとみなされてもよい。 The term "determining" used in this disclosure may include a wide variety of actions. For example, "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".
 また、「判断(決定)」は、受信(receiving)(例えば、情報を受信すること)、送信(transmitting)(例えば、情報を送信すること)、入力(input)、出力(output)、アクセス(accessing)(例えば、メモリ中のデータにアクセスすること)などを「判断(決定)」することであるとみなされてもよい。 Further, "judgment (decision)" includes receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access (for example). It may be regarded as "determining" such as accessing) (for example, accessing data in memory).
 また、「判断(決定)」は、解決(resolving)、選択(selecting)、選定(choosing)、確立(establishing)、比較(comparing)などを「判断(決定)」することであるとみなされてもよい。つまり、「判断(決定)」は、何らかの動作を「判断(決定)」することであるとみなされてもよい。 In addition, "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.
 また、「判断(決定)」は、「想定する(assuming)」、「期待する(expecting)」、「みなす(considering)」などで読み替えられてもよい。 Further, "judgment (decision)" may be read as "assuming", "expecting", "considering" and the like.
 本開示に記載の「最大送信電力」は送信電力の最大値を意味してもよいし、公称最大送信電力(the nominal UE maximum transmit power)を意味してもよいし、定格最大送信電力(the rated UE maximum transmit power)を意味してもよい。 The "maximum transmission power" described in the present disclosure may mean the maximum value of the transmission power, may mean the nominal UE maximum transmit power, or may mean the rated maximum transmission power (the). It may mean rated UE maximum transmit power).
 本開示において使用する「接続された(connected)」、「結合された(coupled)」という用語、又はこれらのあらゆる変形は、2又はそれ以上の要素間の直接的又は間接的なあらゆる接続又は結合を意味し、互いに「接続」又は「結合」された2つの要素間に1又はそれ以上の中間要素が存在することを含むことができる。要素間の結合又は接続は、物理的であっても、論理的であっても、あるいはこれらの組み合わせであってもよい。例えば、「接続」は「アクセス」で読み替えられてもよい。 The terms "connected", "coupled", or any variation thereof, as used in the present disclosure, are any direct or indirect connections or connections between two or more elements. Means, and can include the presence of one or more intermediate elements between two elements that are "connected" or "bonded" to each other. The connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access".
 本開示において、2つの要素が接続される場合、1つ以上の電線、ケーブル、プリント電気接続などを用いて、並びにいくつかの非限定的かつ非包括的な例として、無線周波数領域、マイクロ波領域、光(可視及び不可視の両方)領域の波長を有する電磁エネルギーなどを用いて、互いに「接続」又は「結合」されると考えることができる。 In the present disclosure, when two elements are connected, one or more wires, cables, printed electrical connections, etc. are used, and as some non-limiting and non-comprehensive examples, the radio frequency domain, microwaves. It can be considered to be "connected" or "coupled" to each other using frequency, electromagnetic energy having wavelengths in the region, light (both visible and invisible) regions, and the like.
 本開示において、「AとBが異なる」という用語は、「AとBが互いに異なる」ことを意味してもよい。なお、当該用語は、「AとBがそれぞれCと異なる」ことを意味してもよい。「離れる」、「結合される」などの用語も、「異なる」と同様に解釈されてもよい。 In the present disclosure, 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".
 本開示において、「含む(include)」、「含んでいる(including)」及びこれらの変形が使用されている場合、これらの用語は、用語「備える(comprising)」と同様に、包括的であることが意図される。さらに、本開示において使用されている用語「又は(or)」は、排他的論理和ではないことが意図される。 When "include", "including" and variations thereof are used in the present disclosure, these terms are as inclusive as the term "comprising". Is intended. Moreover, the term "or" used in the present disclosure is intended not to be an exclusive OR.
 本開示において、例えば、英語でのa, an及びtheのように、翻訳によって冠詞が追加された場合、本開示は、これらの冠詞の後に続く名詞が複数形であることを含んでもよい。 In the present disclosure, if articles are added by translation, for example, a, an and the in English, the disclosure may include the plural nouns following these articles.
 以上、本開示に係る発明について詳細に説明したが、当業者にとっては、本開示に係る発明が本開示中に説明した実施形態に限定されないということは明らかである。本開示に係る発明は、請求の範囲の記載に基づいて定まる発明の趣旨及び範囲を逸脱することなく修正及び変更態様として実施することができる。したがって、本開示の記載は、例示説明を目的とし、本開示に係る発明に対して何ら制限的な意味をもたらさない。
 
 
 
 
Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as an amended or modified mode without departing from the spirit and scope of the invention determined based on the description of the claims. Therefore, the description of the present disclosure is for purposes of illustration and does not bring any limiting meaning to the invention according to the present disclosure.



Claims (6)

  1.  1ショットHARQ-ACK(Hybrid Automatic Repeat reQuest ACKnowledgement)を指示する下り制御情報を受信する受信部と、
     前記下り制御情報から取得できるUL送信の優先度に関する情報に基づいて、前記1ショットHARQ-ACKの優先度を判断する制御部と、を有することを特徴とする端末。
    A receiver that receives downlink control information that instructs 1-shot HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement),
    A terminal having a control unit for determining the priority of the one-shot HARQ-ACK based on the information regarding the priority of UL transmission that can be acquired from the downlink control information.
  2.  前記制御部は、前記1ショットHARQ-ACKで指定される1以上のHARQ-ACKについて、各HARQ-ACKの優先度に関わらずフィードバックするように制御することを特徴とする請求項1に記載の端末。 The first aspect of claim 1, wherein the control unit controls one or more HARQ-ACKs designated by the one-shot HARQ-ACK so as to feed back regardless of the priority of each HARQ-ACK. Terminal.
  3.  前記制御部は、前記1ショットHARQ-ACKで指定される1以上のHARQ-ACKについて、各HARQ-ACKの優先度に基づいてフィードバックするHARQ-ACKを判断することを特徴とする請求項1に記載の端末。 The first aspect of the present invention is characterized in that the control unit determines HARQ-ACK to be fed back based on the priority of each HARQ-ACK for one or more HARQ-ACKs designated by the one-shot HARQ-ACK. Described terminal.
  4.  前記制御部は、前記下り制御情報に含まれるUL送信の優先度を指定する情報、及び前記下り制御情報のフォーマットの少なくとも一つに基づいて、前記1ショットHARQ-ACKの優先度を判断することを特徴とする請求項1から請求項3のいずれかに記載の端末。 The control unit determines the priority of the one-shot HARQ-ACK based on at least one of the information that specifies the priority of UL transmission included in the downlink control information and the format of the downlink control information. The terminal according to any one of claims 1 to 3.
  5.  1ショットHARQ-ACK(Hybrid Automatic Repeat reQuest ACKnowledgement)を指示する下り制御情報を受信する工程と、
     前記下り制御情報から取得できるUL送信の優先度に関する情報に基づいて、前記1ショットHARQ-ACKの優先度を判断する工程と、を有することを特徴とする無線通信方法。
    The process of receiving downlink control information instructing 1-shot HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement), and
    A wireless communication method comprising: a step of determining the priority of the one-shot HARQ-ACK based on the information regarding the priority of UL transmission that can be acquired from the downlink control information.
  6.  1ショットHARQ-ACK(Hybrid Automatic Repeat reQuest ACKnowledgement)を指示する下り制御情報を送信する送信部と、
     前記下り制御情報で通知するUL送信の優先度に関する情報に基づいて優先度が決定される前記1ショットHARQ-ACKの受信を制御する制御部と、を有することを特徴とする基地局。
     
     
     
    A transmitter that transmits downlink control information that instructs 1-shot HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement),
    A base station including a control unit that controls reception of the one-shot HARQ-ACK whose priority is determined based on information regarding the priority of UL transmission notified by the downlink control information.


PCT/JP2020/026739 2020-07-08 2020-07-08 Terminal, wireless communication method, and base station WO2022009346A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/026739 WO2022009346A1 (en) 2020-07-08 2020-07-08 Terminal, wireless communication method, and base station

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/026739 WO2022009346A1 (en) 2020-07-08 2020-07-08 Terminal, wireless communication method, and base station

Publications (1)

Publication Number Publication Date
WO2022009346A1 true WO2022009346A1 (en) 2022-01-13

Family

ID=79552396

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/026739 WO2022009346A1 (en) 2020-07-08 2020-07-08 Terminal, wireless communication method, and base station

Country Status (1)

Country Link
WO (1) WO2022009346A1 (en)

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

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "Remaining issues on NR-U HARQ scheduling and feedback", 3GPP DRAFT; R1-2000503, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200224 - 20200228, 14 February 2020 (2020-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051852900 *
SAMSUNG: "UE features for URLLC/IIoT", 3GPP DRAFT; R1-2003897, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200525 - 20200605, 15 May 2020 (2020-05-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051885663 *

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

Similar Documents

Publication Publication Date Title
JP7269331B2 (en) Terminal, wireless communication method, base station and system
WO2020144833A1 (en) User terminal and wireless communication method
WO2021152805A1 (en) Terminal, wireless communication method, and base station
WO2022024379A1 (en) Terminal, wireless communication method, and base station
WO2020110244A1 (en) User terminal and wireless communication method
JP7337837B2 (en) Terminal, wireless communication method, base station and system
JPWO2020059148A1 (en) Terminals, wireless communication methods, base stations and systems
WO2021064961A1 (en) Terminal and wireless communication method
WO2022039164A1 (en) Terminal, wirless communication method, and base station
WO2020202478A1 (en) User terminal and wireless communication method
WO2020188821A1 (en) User terminal and wireless communication method
WO2021255936A1 (en) Terminal, radio communication method, and base station
JP7351921B2 (en) Terminals, wireless communication methods, base stations and systems
WO2020188666A1 (en) User terminal and wireless communication method
WO2022009346A1 (en) Terminal, wireless communication method, and base station
WO2022009347A1 (en) Terminal, wireless communication method, and base station
WO2021152804A1 (en) Terminal, wireless communication method, and base station
WO2022059110A1 (en) Terminal, wireless communication method, and base station
WO2022034641A1 (en) Terminal, wireless communication method, and base station
WO2022079805A1 (en) Terminal, wireless communication method, and base station
WO2022079804A1 (en) Terminal, wireless communication method, and base station
WO2022009315A1 (en) Terminal, wireless communication method and base station
JP7335349B2 (en) Terminal, wireless communication method, base station and system
WO2021186701A1 (en) Terminal, wireless communication method and base station
WO2020202477A1 (en) User terminal and wireless communication method

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20944681

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP