Terminal, wireless communication method, base station, and system

Abstract

A terminal according to one aspect of the present disclosure includes a receiving unit for receiving downlink control information (DCI) including a priority level indicator field for scheduling of a physical downlink shared channel (PDSCH), and a control unit for controlling, on the basis of the DCI, transmission of Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) information for the PDSCH, characterized in that the DCI includes a field for at least one of HARQ-ACK one-shot feedback for the PDSCH, and an extended dynamic HARQ-ACK codebook for the PDSCH. According to this aspect of the present disclosure, radio communication in an NR-U system can be appropriately controlled.

Description

Technical Field

[0001] The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system. 、 base station and system in the next-generation mobile communication system.

Background Art

[0002] In a Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) was standardized for the purpose of further high-speed data rates, low latency, etc. (Non-Patent Document 1). Also, for the purpose of further large capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9), LTE-Advanced (3GPP Rel. 10-14) was standardized.

[0003] Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), New Radio (NR), 3GPP Rel. 15 and later, etc.) are also being considered.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In future wireless communication systems (also referred to as, for example, 5G, 5G+, New Radio (NR), 3GPP Rel. 16 and later), the use of unlicensed bands (which may also be referred to as NR-Unlicensed (U) systems), similar to existing wireless communication systems (e.g., before 3GPP Rel. 15), is being considered.

[0006] Also, in future wireless communication systems (also referred to as, for example, 5G, 5G+, New Radio (NR), 3GPP Rel. 16 and later), downlink control information (DCI) formats (e.g., DCI format 0_2, 1_2) for traffic types such as ultra-reliable and low-latency communications (URLLC) are being considered for introduction.

[0007] However, there has not been sufficient consideration as to whether to support NR-U system-specific indications using DCI formats for traffic types such as URLLC.

[0008] Therefore, one object of the present disclosure is to provide a terminal and a wireless communication method that can appropriately control wireless communication in an NR-U system 、 base station and system for this purpose. Means for Solving the Problem

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) including a one-shot Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) request field, and a control unit that controls transmission of HARQ-ACK information for the PDSCH based on the one-shot HARQ-ACK request field, wherein the DCI is DCI format 1_2 Further, in the DCI, a PDSCH group index field, a required PDSCH group number field, and a new feedback indicator field are not supported It is characterized by this.

Advantages of the Invention

[0010] According to one aspect of the present disclosure, wireless communication in an NR-U system can be appropriately controlled.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Embodiments for Carrying Out the Invention

[0012] (Service (Traffic Type)) In future wireless communication systems (e.g., NR), traffic types (also referred to as types, services, service types, communication types, use cases, etc.) such as further advancement of mobile broadband (e.g., enhanced Mobile Broadband (eMBB)), machine type communication for realizing a large number of simultaneous connections (e.g., massive Machine Type Communications (mMTC), Internet of Things (IoT)), and ultra-reliable and low-latency communication (e.g., Ultra-Reliable and Low-Latency Communications (URLLC)) are assumed. For example, in URLLC, a lower latency and higher reliability than eMBB are required.

[0013] The traffic type may be identified in the physical layer based on at least one of the following. · Logical channels having different priorities · Modulation and Coding Scheme (MCS) table (MCS index table) · Channel Quality Indication (CQI) table · DCI format · (Radio Network Temporary Identifier (RNTI: System Information-Radio Network Temporary Identifier)) used for scrambling (masking) the cyclic redundancy check (CRC) bits included (added) in the DCI (DCI format) · RRC (Radio Resource Control) parameters · Specific RNTI (e.g., RNTI for URLLC, MCS-C-RNTI, etc.) · Search space · Predetermined field in DCI (e.g., newly added field or reuse of existing field)

[0014] Specifically, the traffic type of HARQ-ACK (or PUCCH) for PDSCH may be determined based on at least one of the following. · MCS index table used for determining at least one of the modulation order, target code rate, and transport block size (TBS) of the PDSCH (e.g., whether to use MCS index table 3) · RNTI used for CRC scrambling of the DCI used for scheduling the PDSCH (e.g., whether CRC scrambling is performed with C-RNTI or MCS-C-RNTI) · Priority set by upper layer signaling

[0015] The traffic type may be associated with communication requirements (requirements such as latency and error rate, required conditions), data types (such as voice and data), etc.

[0016] The difference between the requirements of URLLC and eMBB may be that the latency of URLLC is smaller than that of eMBB, or the requirements of URLLC may include reliability requirements.

[0017] For example, the requirements for the user (U) plane latency of eMBB may include that the downlink U plane latency is 4 ms and the uplink U plane latency is 4 ms. On the other hand, the requirements for the U plane latency of URLLC may include that the downlink U plane latency is 0.5 ms and the uplink U plane latency is 0.5 ms. Also, the requirements for the reliability of URLLC may include that the error rate of 32 bytes is 10-5 at a U plane latency of 1 ms.

[0018] Also, as enhanced Ultra Reliable and Low Latency Communications (eURLLC), mainly the improvement of the reliability of traffic for unicast data is being considered. Hereinafter, when not distinguishing between URLLC and eURLLC, it is simply called URLLC.

[0019] In NR after Rel. 16, setting priorities at multiple levels (e.g., two levels) for a predetermined signal or channel is being considered. For example, it is assumed that separate priorities are set for each signal or channel corresponding to different traffic types (also referred to as services, service types, communication types, use cases, etc.) and communication control (e.g., transmission control at the time of collision, etc.) is performed. Thereby, it becomes possible to control communication by setting different priorities according to the service type or the like for the same signal or channel.

[0020] The priority may be set for a signal (e.g., UCI such as HARQ-ACK, reference signal, etc.), a channel (PDSCH, PUSCH, etc.), or a HARQ-ACK codebook, etc. The priority may be defined by a first priority (e.g., High) and a second priority (e.g., Low) with a lower priority than the first priority. Alternatively, three or more types of priorities may be set. Information regarding the priority may be notified from the base station to the UE using at least one of higher layer signaling and DCI.

[0021] For example, priorities may be set for HARQ-ACK for dynamically scheduled PDSCH, HARQ-ACK for semi-persistent PDSCH (SPS PDSCH), and HARQ-ACK for SPS PDSCH release. Alternatively, priorities may be set for the HARQ-ACK codebook corresponding to these HARQ-ACKs. Note that when setting a priority for PDSCH, the priority of the PDSCH may be read as the priority of the HARQ-ACK for the PDSCH.

[0022] When different UL signals / UL channels collide, the UE may control UL transmission based on priorities. For example, it may be controlled to perform UL transmission with a high priority and not perform (e.g., drop) UL transmission with a low priority. Alternatively, the transmission timing of UL transmission with a low priority may be changed (e.g., postponed or shifted).

[0023] The collision of different UL signals / UL channels may refer to the case where the time resources (or time resources and frequency resources) of different UL signals / UL channels overlap, or the case where the transmission timings of different UL signals / UL channels overlap.

[0024] When using DCI to notify priorities, upper layer signaling may be used to notify or set in the UE from the base station whether a bit field (e.g., Priority indicator) for notifying priorities is set in the DCI. Also, when the DCI does not include a bit field for notifying priorities, the UE may determine that the priority of the PDSCH (or HARQ-ACK corresponding to the PDSCH) scheduled by the DCI is a specific priority (e.g., low).

[0025] (Setting of Priorities) Furthermore, in NR after Rel.16, it is being considered to set priorities at multiple levels (e.g., two levels) for a given signal or channel. For example, it is assumed that separate priorities are set for signals or channels corresponding to different traffic types (also referred to as services, service types, communication types, use cases, etc.), and communication control (e.g., transmission control during collisions, etc.) is performed. This enables communication control by setting different priorities according to the service type, etc., for the same signal or channel.

[0026] The priority may be set for a signal (e.g., UCI such as HARQ-ACK, reference signal, etc.), a channel (PDSCH, PUSCH, etc.), or a HARQ-ACK codebook, etc. The priority may be defined by a first priority (e.g., High) and a second priority (e.g., Low) with a lower priority than the first priority. Alternatively, three or more types of priorities may be set. Information regarding the priority may be notified from the base station to the UE using at least one of higher layer signaling and DCI.

[0027] For example, priorities may be set for HARQ-ACK for dynamically scheduled PDSCH, HARQ-ACK for semi-persistent PDSCH (SPS PDSCH), and HARQ-ACK for SPS PDSCH release. Alternatively, priorities may be set for the HARQ-ACK codebook corresponding to these HARQ-ACKs. When setting a priority for PDSCH, the priority of the PDSCH may be read as the priority of the HARQ-ACK for the PDSCH.

[0028] Also, priorities may be set for dynamically granted PUSCH, configured grant-based PUSCH, etc.

[0029] When different UL signals / UL channels collide, the UE may control UL transmissions based on priority. For example, it may control to perform UL transmissions with high priority and not perform (e.g., drop) UL transmissions with low priority. Alternatively, it may change (e.g., delay or shift) the transmission timing of UL transmissions with low priority.

[0030] The collision of different UL signals / UL channels may refer to the case where the time resources (or time resources and frequency resources) of different UL signals / UL channels overlap, or the transmission timings of different UL signals / UL channels overlap.

[0031] When using DCI to schedule shared channels with different priorities, the problem is how to control the multiple DCI formats used for the scheduling of the shared channels and the priorities of the shared channels scheduled by the DCI. The shared channels with different priorities may be PDSCHs with different HARQ-ACK priorities or PUSCHs with different priorities.

[0032] For example, it is conceivable to control the scheduling of shared channels with different priorities by using either an existing DCI format (e.g., DCI format 0_1 / 1_1) supported in Rel. 15 or a new DCI format (e.g., DCI format 0_2 / 1_2). When the UE is configured to monitor either the existing DCI format or the new DCI format, the existing DCI format or the new DCI format may support the scheduling of both the first priority (or URLLC) and the second priority (or eMBB).

[0033] (Unlicensed band) In an unlicensed band (e.g., 2.4 GHz band, 5 GHz band, 6 GHz band, etc.), it is assumed that a plurality of systems such as, for example, a Wi-Fi system and a system supporting Licensed-Assisted Access (LAA) (LAA system) coexist. Therefore, it is considered necessary to avoid transmission collisions and / or control interference among the plurality of systems.

[0034] In the LAA of an existing LTE system (e.g., Rel. 13), before transmitting data in an unlicensed band, a data transmission device performs listening (Listen Before Talk (LBT), Clear Channel Assessment (CCA), carrier sensing, channel sensing, sensing, channel access procedure) to check for the presence of transmissions from other devices (e.g., base stations, user terminals, Wi-Fi devices, etc.).

[0035] The transmission device may be, for example, a base station (e.g., gNB: gNodeB) in the downlink (DL) and a user terminal (e.g., User Equipment (UE)) in the uplink (UL). Also, the receiving device that receives data from the transmission device may be, for example, a user terminal in the DL and a base station in the UL.

[0036] In the LAA of an existing LTE system, after detecting that there is no transmission from other devices (idle state) in LBT, the transmission device starts data transmission after a predetermined period (e.g., immediately or during a backoff period).

[0037] The use of unlicensed bands is also being considered in future wireless communication systems (e.g., also referred to as 5G, 5G+, New Radio (NR), 3GPP Rel. 15 and later, etc.). An NR system using an unlicensed band may be called an NR-Unlicensed (U) system, an NR LAA system, etc.

[0038] Dual Connectivity (DC) between a licensed band and an unlicensed band, Stand-Alone (SA) of the unlicensed band, etc. may also be included in NR-U.

[0039] In NR-U, a node (e.g., a base station, UE) starts transmission after confirming that the channel is idle by LBT for coexistence with other systems or other operators.

[0040] In NR-U, a base station (e.g., gNB) or UE obtains a Transmission Opportunity (TxOP) and performs transmission when the LBT result is idle. The base station or UE does not perform transmission when the LBT result is busy (LBT-busy). The time of the transmission opportunity may be called the Channel Occupancy Time (COT).

[0041] Note that LBT-idle may be replaced with LBT success. LBT-busy may be replaced with LBT failure.

[0042] (HARQ-ACK Codebook) The UE may transmit HARQ-ACK feedback using one PUCCH resource in units of a HARQ-ACK codebook composed of bits of one or more delivery confirmation information (e.g., Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK)). The HARQ-ACK bits may be called HARQ-ACK information, HARQ-ACK information bits, etc.

[0043] Here, the HARQ-ACK codebook may be configured to include bits for HARQ-ACK in at least one unit of a time domain (e.g., a slot), a frequency domain (e.g., a Component Carrier (CC)), a spatial domain (e.g., a layer), a Transport Block (TB), and a Code Block Group (CBG) that constitutes the TB. The HARQ-ACK codebook may simply be called a codebook.

[0044] Note that the number of bits (size), etc. included in the HARQ-ACK codebook may be determined semi-statically or dynamically. A HARQ-ACK codebook whose size is determined semi-statically is also called a semi-static HARQ-ACK codebook, a Type 1 HARQ-ACK codebook, etc. A HARQ-ACK codebook whose size is determined dynamically is also called a dynamic HARQ-ACK codebook, a Type 2 HARQ-ACK codebook, etc.

[0045] Whether to use a Type 1 HARQ-ACK codebook or a Type 2 HARQ-ACK codebook may be set for the UE using a higher layer parameter (e.g., pdsch-HARQ-ACK-Codebook).

[0046] In the case of a Type 1 HARQ-ACK codebook, the UE may feedback HARQ-ACK bits for PDSCH candidates (or PDSCH opportunities) corresponding to a certain range (e.g., a range set based on a higher layer parameter) regardless of whether the PDSCH is scheduled within the range.

[0047] This range may be determined based on at least one of the following: a certain period (e.g., a specific set of opportunities for a candidate PDSCH reception, or a specific number of monitoring occasions for the Physical Downlink Control Channel (PDCCH)), the number of CCs configured or activated for the UE, the number of transport blocks (number of layers or ranks), the number of codeblock groups (CBGs) per transport block, and whether spatial bundling is applied. This specific range is also referred to as a HARQ-ACK window, a HARQ-ACK bundling window, a HARQ-ACK feedback window, etc.

[0048] In the type 1 HARQ-ACK codebook, within a specific range, even if there is no scheduling of the PDSCH for the UE, the UE reserves the HARQ-ACK bits for the PDSCH within the codebook. If the UE determines that the PDSCH is not actually scheduled, it can feedback these bits as NACK bits.

[0049] On the other hand, in the case of the type 2 HARQ-ACK codebook, the UE may feedback the HARQ-ACK bits for the scheduled PDSCH within the above specific range.

[0050] Specifically, the UE may determine the number of bits in the type 2 HARQ-ACK codebook based on a specific field in the DCI (e.g., the Downlink Assignment Indicator (Index) (DAI) field). The DAI field may include a Counter DAI (C-DAI) and a Total DAI (T-DAI).

[0051] C-DAI may indicate the counter value of the downlink transmission (PDSCH, data, TB) scheduled within a specific period. For example, C-DAI in the DCI that schedules data within the specific period may indicate the number counted first in the frequency domain (e.g., CC) and then in the time domain within the specific period. For example, C-DAI may correspond to the value obtained by counting PDSCH reception or semi-persistent scheduling (SPS) release in ascending order of the serving cell index and then in ascending order of the PDCCH monitoring opportunity for one or more DCIs included in a specific period.

[0052] T-DAI may indicate the total value (total number) of the data scheduled within a specific period. For example, T-DAI in the DCI that schedules data in a certain time unit (e.g., PDCCH monitoring opportunity) within the specific period may indicate the total number of the data scheduled up to that time unit (also referred to as a point, timing, etc.) within the specific period.

[0053] Also, it is being considered to separately configure the HARQ-ACK codebook for different service types (or PDSCH or HARQ-ACK with different priorities set). That is, in order to support multiple service types (or multiple priorities), it is conceivable to simultaneously configure multiple HARQ-ACK codebooks. For example, a first HARQ-ACK codebook corresponding to URLLC (e.g., the first priority) and a second HARQ-ACK codebook corresponding to eMBB (e.g., the second priority) may be configured.

[0054] In this case, the first PUCCH configuration parameter corresponding to the first HARQ-ACK codebook (e.g., PUCCH configuration, or PUCCH configuration parameters) and the second PUCCH configuration parameter corresponding to the second HARQ-ACK codebook may be supported or configured separately. The PUCCH configuration parameter may be at least one of a PUCCH resource (or a PUCCH resource set) applied to the transmission of HARQ-ACK, the transmission timing of PUCCH (e.g., K1 set), the maximum coding rate (e.g., max-code rate), and the transmission power of PUCCH.

[0055] In this case, the first PUCCH configuration information may be applied to the HARQ-ACK feedback for URLLC, and the second PUCCH configuration information may be applied to the HARQ-ACK feedback for eMBB.

[0056] (HARQ process) For a UE with carrier aggregation (CA) or dual connectivity (DC) configured, 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.

[0057] In a wireless communication system, data transmission is based on scheduling, and the scheduling information for downlink (DL) data transmission is carried by downlink control information (DCI). A HARQ process number (HARQ Process Number (HPN)) is assigned to each HARQ process. The DCI includes a 4-bit HARQ process number field indicating the HARQ process number used for the current data transmission. The HARQ entity manages multiple (up to 16) HARQ processes in parallel. That is, the HARQ process numbers range from HPN0 to HPN15. The HARQ process number is also referred to as the HARQ process identifier.

[0058] The unit for transmitting uplink (UL) data via the Physical Uplink Shared Channel (PUSCH) and the unit for transmitting downlink (DL) data via the Physical Downlink Shared Channel (PDSCH) may be referred to as a transport block (TB). A TB is a unit handled by the Media Access Control (MAC) layer. The control of hybrid automatic repeat request (HARQ) (retransmission) may be performed for each TB or for each code block group (CBG) including one or more code blocks (CBs) within a TB.

[0059] The user equipment transmits information indicating a positive acknowledgement (ACK) / negative acknowledgement (NACK) of HARQ indicating whether or not the decoding of the DL transport block received using the PDSCH was successful to the base station using, for example, the Physical Uplink Control Channel (PUCCH) or the PUSCH.

[0060] 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).

[0061] (Enhanced Dynamic HARQ Feedback) Since Release 16, in order to provide a transmission opportunity for HARQ-ACK feedback due to LBT failure in the UE or PUCCH detection error in the base station, it has been considered to request or trigger the UE to perform feedback of a HARQ-ACK codebook including a plurality of HARQ-ACK processes in a certain resource. The HARQ-ACK process (e.g., DL HARQ-ACK process) may be HARQ-ACK for all CCs set in the UE in the PUCCH group.

[0062] Feedback of HARQ-ACK (or HARQ-ACK codebook) including a plurality of HARQ-ACK processes may be called enhanced dynamic HARQ-ACK feedback, enhanced dynamic HARQ feedback, group-based HARQ feedback, enhanced dynamic HARQ-ACK codebook, etc. The enhanced dynamic HARQ feedback may be notified from the base station to the UE using a specific DCI format. The specific DCI format may be a UE-specific DCI format (e.g., DCI format 1_1).

[0063] The specific DCI format (e.g., DCI format 1_1) may include a specific field to notify (request or trigger) enhanced dynamic HARQ feedback. The specific field may be at least one of a PDSCH group index field and a Number of requested PDSCH group(s) field.

[0064] Specific fields (e.g., PDSCH group index field, Number of requested PDSCH group(s) field) included in a specific DCI format (e.g., DCI format 1_1) may have a bit length of 1 bit when a specific higher layer parameter (pdsch-HARQ-ACK-Codebook) is set to enhanced dynamic (e.g., enhancedDynamic-r16, enhancedDynamic), and may be 0 bits in other cases.

[0065] The PDSCH group index may be an index that identifies a group of PDSCHs scheduled by a DCI that includes the PDSCH group index.

[0066] When the value of the Number of requested PDSCH group(s) field in the DCI is 0, the UE may perform one or more HARQ feedbacks for the PDSCH group scheduled by that DCI in a certain resource. When the value of the Number of requested PDSCH group(s) field in the DCI is 1, the UE may perform one or more HARQ feedbacks for the PDSCH group scheduled by that DCI and a PDSCH group different from the PDSCH group scheduled by that DCI in a certain resource. In other words, when the value of the Number of requested PDSCH group(s) field in the DCI is 1, the UE may perform HARQ feedback for the PDSCHs with PDSCH group indices 0 and 1 set in a certain resource.

[0067] Also, a specific DCI format (e.g., DCI format 1_1) may include a specific field (e.g., New feedback indicator (NFI) field).

[0068] A specific field (e.g., New feedback indicator field) included in a specific DCI format (e.g., DCI format 1_1) may have a bit length of 2 bits when a specific upper layer parameter (pdsch-HARQ-ACK-Codebook) is set to enhancedDynamic-r16 and another upper layer parameter (NFI-TotalDAI-Included-r16) is set (NFI-TotalDAI-Included-r16 = enable). Also, a specific field (e.g., New feedback indicator field) may have a bit length of 1 bit when a specific upper layer parameter (pdsch-HARQ-ACK-Codebook) is set to enhancedDynamic-r16 and another upper layer parameter (NFI-TotalDAI-Included-r16) is not set, and may be 0 bits in other cases.

[0069] Note that the other upper layer parameter (NFI-TotalDAI-Included-r16) may be a parameter indicating whether the NFI and the T-DAI field of the unscheduled PDSCH group are included in the non-fallback DL grant DCI (e.g., DCI format 1_1).

[0070] Note that the UE operation for the above New feedback indicator will be described in detail below.

[0071] A UE requested or triggered to perform enhancedDynamic HARQ feedback may feedback a codebook including one or more HARQ-ACK processes using PUCCH / PUSCH.

[0072] FIG. 1 is a diagram showing an example of an enhanced dynamic HARQ feedback method. In the example of FIG. 1, the UE monitors PDCCH1 and PDCCH2 in COT#0 and monitors PDCCH3 in COT#1. PDSCH1, PDSCH2, and PDSCH3 are scheduled by the 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.

[0073] In the example of FIG. 1, the UE starts LBT at the start symbol of PDCCH1 and PDCCH3. The UE is instructed by PDCCH1 to transmit HARQ-ACK1 for the PDSCH (PDSCH1) of group 0 in the HARQ-ACK transmission resource in COT#0 (the HARQ feedback timing (PDSCH-to-HARQ_feedback timing indicator), K1 is 2). If the UE fails in LBT in COT#0, it does not transmit HARQ-ACK1.

[0074] Also, in the example of FIG. 1, for HARQ-ACK2 for the PDSCH (PDSCH2) of group 1, if the value (K1) of the HARQ feedback timing included in the DCI received by PDCCH2 is inapplicable, the UE does not transmit HARQ-ACK2 (holds HARQ-ACK2) in the HARQ-ACK transmission resource in COT#0.

[0075] Furthermore, in the example of FIG. 1, the UE is instructed by PDCCH3 to transmit HARQ-ACK3 for PDSCH in group 1 (PDSCH3) in the HARQ-ACK transmission resource in COT#1 (where K1 is 2). Since the value of the requested PDSCH group number field included in the DCI of the PDCCH3 is 1, in the HARQ-ACK transmission resource in COT#1, the UE transmits HARQ-ACK for the PDSCH corresponding to the PDSCH group (PDSCH group 1) scheduled by PDCCH3 and the PDSCH group (PDSCH group 0) not scheduled by PDCCH3.

[0076] In the example of FIG. 1, when the UE succeeds in LBT in COT#1, the UE transmits HARQ-ACK3. At this time, the UE multiplexes and transmits HARQ-ACK1 that was not transmitted due to the failure of LBT in COT#0 and the held HARQ-ACK2 in the transmission resource for HARK-ACK3.

[0077] (1-shot HARQ feedback) After Rel. 16, in order to provide a transmission opportunity for HARQ-ACK feedback due to the failure of LBT in the UE or the detection error of PUCCH in the base station, it is being considered to request or trigger the UE to feedback a HARQ-ACK codebook including a plurality (for example, all) of HARQ-ACK processes. The HARQ-ACK process (for example, the DL HARQ-ACK process) may be HARQ-ACK for a plurality (for example, all) of CCs set in the UE in the PUCCH group.

[0078] Feedback of HARQ-ACK (or HARQ-ACK codebook) including a plurality (e.g., all) of HARQ-ACK processes in a plurality (e.g., all) of CCs may be called one-shot HARQ-ACK feedback, one-shot HARQ feedback, or HARQ-ACK one-shot feedback. The one-shot HARQ feedback may be notified from a base station to a UE using a specific DCI format. The specific DCI format may be a UE-specific DCI format (e.g., DCI format 1_1).

[0079] The specific DCI format (e.g., DCI format 1_1) may include a specific field for notifying one-shot HARQ feedback. The specific field may be a one-shot HARQ-ACK request field.

[0080] The specific field (e.g., one-shot HARQ-ACK request field) included in the specific DCI format (e.g., DCI format 1_1) may have a bit length of 1 bit when a specific upper layer parameter (pdsch-HARQ-ACK-OneShotFeedback-r16) is set, and may be 0 bits in other cases.

[0081] The one-shot HARQ-ACK request may be a parameter that requests or triggers a UE to transmit a plurality (e.g., all) of HARQ processes in a certain resource.

[0082] If the value of the one-shot HARQ-ACK request is 0, the UE may perform HARQ feedback for the PDSCH scheduled by the DCI including the one-shot HARQ-ACK request in a certain resource. If the value of the one-shot HARQ-ACK request is 1, the UE may perform, in a certain resource, the HARQ feedback not sent for the PDSCH and the HARQ feedback for the PDSCH scheduled by the DCI including the one-shot HARQ-ACK request.

[0083] A UE for which one-shot HARQ feedback is requested or triggered may feedback, using the PUCCH / PUSCH, a codebook including a plurality (e.g., all) of HARQ-ACK processes in each configured CC. At this time, by including a New Data Indicator (NDI) in the feedback, HARQ inconsistency between the UE and the gNB can be avoided.

[0084] FIG. 2 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. 2 are the same as those in FIG. 1.

[0085] In the example of FIG. 2, if the UE fails in the LBT in COT#0, it does not transmit HARQ-ACK1. Also, for HARQ-ACK2 for PDSCH2, if the value (K1) of the HARQ feedback timing included in the DCI received by PDCCH2 is inapplicable, the UE does not transmit HARQ-ACK2 (holds HARQ-ACK2) in the resource for HARQ-ACK transmission in COT#0.

[0086] Also, in the example of FIG. 2, the UE is instructed by PDCCH3 to transmit the HARQ-ACK3 for the PDSCH of group 1 (PDSCH3) 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, if the UE is instructed by the DCI received by PDCCH3 for one-shot HARQ feedback, in COT#0, it multiplexes and transmits HARQ-ACK1 that was not transmitted due to LBT failure and the held HARQ-ACK2 in the transmission resource for HARK-ACK3.

[0087] (New feedback indicator) The new feedback indicator (New feedback indicator (NFI)) included in the DCI is a field (signaling) that indicates whether to reset the generation / holding (status) (e.g., ACK or NACK) of the previous HARQ-ACK information for a specific HARQ process ID.

[0088] Within the PDSCH group regardless of the PUCCH transmission opportunity, C-DAI and T-DAI are accumulated. In other words, C-DAI and T-DAI are not reset by the PUCCH transmission opportunity. Also, when the UE transmits the HARQ-ACK codebook, it does not hold (resets) the HARQ-ACK information.

[0089] The DCI for scheduling the PDSCH (e.g., DCI format 1_1) may include at least one field of C-DAI, T-DAI, PDSCH group index (GI), NFI, required PDSCH group number (RG).

[0090] The NFI bits indicate that C-DAI and T-DAI are flushed and generate (hold) another HARQ-ACK information for new feedback. If the NFI bits are not toggled, C-DAI and T-DAI are maintained (not reset). On the other hand, if the NFI bits are toggled, C-DAI and T-DAI are reset.

[0091] When the NFI in the DCI has a bit length of 1 bit, the NFI is a field that indicates whether the C-DAI, T-DAI, and HARQ-ACK information corresponding to the PDSCH group (GI) indicated by that DCI is reset.

[0092] When the NFI in the DCI has a bit length of 2 bits, each bit of the NFI corresponds to one PDSCH group. Each bit is a field that indicates whether the C-DAI, T-DAI, and HARQ-ACK information of the corresponding PDSCH group is reset.

[0093] The first (upper) bit of the 2-bit NFI corresponds to the PDSCH group indicated by that DCI among the two PDSCH groups. The second (lower) bit of the 2-bit NFI corresponds to a PDSCH group different from the PDSCH group indicated by that DCI among the two PDSCH groups.

[0094] Note that the first bit and the second bit may be the first New_Feedback indicator field and the second New_Feedback indicator field, respectively. The first bit and the second bit may correspond to the lower bit and the upper bit, respectively.

[0095] FIG. 3 is a diagram showing an example of holding and resetting HARQ-ACK information by NFI. FIG. 3 shows an example where the number of bits of NFI is 1. In the example of FIG. 3, PDSCH1-6 are respectively scheduled by DCI received by each of PDCCH1-6. In the example of FIG. 3, the PDSCH group index (GI) indicated by DCI in PDSCH1-6 is all 0. HARQ-ACK1 and 2 for each of PDSCH1 and 2 are transmitted in the resources for transmitting HARQ-ACK3 and 4 for each of PDSCH3 and 4 due to the LBT failure in COT#0.

[0096] In the example of FIG. 3, the UE receives DCI including the value 0 of NFI until transmitting HARQ-ACK. During that time, C-DAI and T-DAI are accumulated. After the UE transmits HARQ-ACK1-4, the UE receives DCI with the value of NFI being 1 by PDCCH5. In this case, the generation / holding (status) of C-DAI, T-DAI, and HARQ-ACK information is reset.

[0097] FIG. 4 is a diagram showing another example of holding and resetting HARQ-ACK information by NFI. FIG. 4 shows an example where the number of bits of NFI is 1. In the example of FIG. 4, the PDSCH group index (GI) indicated for PDSCH1, 3, and 5 is 0, and the PDSCH group index indicated for PDSCH2 and 4 is 1.

[0098] The UE is notified that HARQ-ACK1 and 2 for each of PDSCH1 and 2 are to be transmitted in the HARQ-ACK transmission resources in COT#0, but due to the LBT failure in COT#0, HARQ-ACK1 and 2 are not transmitted in the HARQ-ACK transmission resources in COT#0.

[0099] The HARQ-ACK3 for PDSCH3 is notified to the UE to be transmitted in the HARQ-ACK transmission resource in COT#1. When the LBT in COT#1 is successful, since the value of the required PDSCH group number (RG) included in the DCI received by PDCCH3 is 0, only the HARQ-ACK for the PDSCH group (GI = 0) scheduled by PDCCH3 is transmitted in the HARQ-ACK transmission resource in COT#1. Here, the transmitted HARQ-ACK corresponds to GI = 0 and includes the HARQ-ACKs that the UE holds, that is, HARQ-ACK1 and HARQ-ACK3.

[0100] The HARQ-ACK4 for PDSCH4 is held because the value (K1) of the HARQ feedback timing included in the DCI received by PDCCH4 is an inapplicable value.

[0101] The HARQ-ACK5 and 6 for PDSCH5 and 6 respectively are notified to the UE to be transmitted in the HARQ-ACK transmission resource in COT#2. When the LBT in COT#2 is successful, since the value of the required PDSCH group number (RG) field included in the DCI received by PDCCH6 is 1, the HARQ-ACKs for both PDSCH groups 0 and 1 (GI = 0 and 1) are transmitted in the HARQ-ACK transmission resource in COT#2. Here, the transmitted HARQ-ACKs are for both PDSCH groups 0 and 1 and include the HARQ-ACKs that the UE holds, that is, HARQ-ACK2, 4, and 6, and the HARQ-ACK5 for PDSCH5 scheduled by PDCCH5.

[0102] For each GI (PDSCH group), C-DAI and T-DAI are accumulated until the HARQ-ACK corresponding to the GI is transmitted. In the example of FIG. 4, for GI = 0, the C-DAI and T-DAI included in the DCI of PDCCH1 that schedules PDSCH1 are 1, and the C-DAI and T-DAI included in the DCI of PDCCH3 that schedules PDSCH3 are 2. When the NFI included in the DCI that schedules the PDSCH is toggled, the C-DAI and T-DAI corresponding to the GI (PDSCH group) indicated by that DCI are reset.

[0103] In the example of FIG. 4, in the HARQ-ACK transmission resource in COT#1, since the transmissions of HARQ-ACK1 and 3 are successful, the value of the NFI included in the DCI of PDCCH5 that schedules PDSCH5 corresponding to GI = 0 in COT#2 is toggled (becomes 1), and the C-DAI and T-DAI are reset. On the other hand, the C-DAI and T-DAI included in the DCI of PDCCH2 that schedules PDSCH2 corresponding to GI = 1 are 1, the C-DAI and T-DAI included in the DCI of PDCCH4 that schedules PDSCH4 are 2, and the C-DAI and T-DAI included in the DCI of PDCCH6 that schedules PDSCH6 are 3 (since the value of the NFI included in any of the DCIs is not toggled (remains 0), the C-DAI and T-DAI are accumulated).

[0104] FIG. 5 is a diagram showing another example of holding and resetting HARQ-ACK information by NFI. FIG. 5 shows an example in which the number of bits of the NFI is 2. In the example of FIG. 5, PDSCH1-6 are each scheduled by PDCCH1-6. The PDSCH group indexes (GIs) of PDSCH1, 3, and 5 are 0. The PDSCH group indexes of PDSCH2 and 4 are 1.

[0105] In the example of FIG. 5, PDSCH1-6 are scheduled by DCI received by each of PDCCH1-6, respectively. HARQ-ACK1 and 2 for each of PDSCH1 and 2 are transmitted in the resource for transmitting HARQ-ACK3 and 4 for each of PDSCH3 and 4 due to the LBT failure in COT#0.

[0106] In the example of FIG. 5, the UE receives DCI containing the same value (00) of NFI until it transmits HARQ-ACK (from PDCCH1 to PDCCH4). Thereby, C-DAI and T-DAI are accumulated. After the UE transmits HARQ-ACK1-4, it receives DCI containing the toggled value (11) of NFI by PDCCH5. In this way, when both the values of the upper bit and the lower bit of the 2-bit NFI are toggled (to 1), C-DAI and T-DAI corresponding to both GI = 0 and 1 are reset.

[0107] Note that in the example of FIG. 5, the value of NFI corresponding to PDCCH6 is 11, but it may be any value (for example, 00, 01, 10).

[0108] (DCI Format for URLLC) After Rel.16, it is considered to introduce DCI formats for traffic types such as high-reliability and low-latency communications (for example, Ultra-Reliable and Low-Latency Communications (URLLC)). The DCI formats may be called DCI format 0_2 and DCI format 1_2. DCI format 0_2 may be DCI (UL grant) for scheduling PUSCH. DCI format 1_2 may be DCI (DL assignment) for scheduling PDSCH.

[0109] The name of the new DCI format is not limited to this. For example, the name of the new DCI format for scheduling PDSCH and PUSCH may be obtained by replacing the "2" in the above DCI format 1_2 and DCI format 0_2 with any character string other than "0" and "1", or may have other names.

[0110] DCI format 0_2 and DCI format 1_2 may be DCI formats in which a part of the payload is restricted as compared with existing DCI formats (for example, DCI format 0_1, 1_1).

[0111] Specifically, DCI format 0_2 and DCI format 1_2 may not allow code block group-based transmission and reception. Further, the redundancy version (RV) field included in DCI format 0_2 and DCI format 1_2 may be settable from 0 to 2 bits. Further, the HARQ process number field included in DCI format 0_2 and DCI format 1_2 may be settable from 0 to 4 bits. Further, the sounding reference signal (SRS) request field included in DCI format 0_2 and DCI format 1_2 may be settable from 0 to 3 bits.

[0112] Further, the PUCCH resource indicator field and the transmission configuration indication state (TCI) field included in DCI format 1_2 may be settable from 0 to 3 bits. Further, the carrier indicator field included in DCI format 0_2 and DCI format 1_2 may be settable from 0 to 3 bits.

[0113] In this way, by making it possible to set the number of bits of each field included in DCI format 0_2 and DCI format 1_2 to be smaller as compared with existing DCI formats (for example, DCI format 0_0, 0_1, 1_0, 1_1), it becomes possible to reduce the payload (size) of the DCI format and improve the reliability of communication.

[0114] By the way, there is not enough consideration as to whether the DCI format used in the NR-U system is supported by the DCI format for URLLC.

[0115] Specifically, in the case of using the DCI format for URLLC for the DCI format used in the NR-U system, there is not enough consideration as to which fields included in the DCI are supported or what the number of bits of the bits included in the DCI should be.

[0116] If such consideration is not sufficient, there is a risk that the throughput will decrease or the communication quality will deteriorate when operating traffic types such as URLLC in the NR-U system.

[0117] Therefore, the inventors conceived an appropriate method for configuring DCI when operating traffic types such as URLLC in the NR-U system.

[0118] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. The wireless communication methods according to the respective embodiments may be applied individually or in combination.

[0119] 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, and may be read interchangeably.

[0120] In the present disclosure, an index, an ID, an indicator, a resource ID, etc. may be read interchangeably.

[0121] In the present disclosure, the first DCI format, DCI format 1_1, the DCI format for eMBB, the DCI format for scheduling the PDSCH for eMBB, the DCI format not including a priority indicator field, the DCI format not including a priority indicator field for scheduling the PDSCH, the existing DCI format, the DCI format of Rel. 15, may be read interchangeably with each other.

[0122] In the present disclosure, the second DCI format, DCI format 1_2, the DCI format for URLLC, the DCI format for scheduling the PDSCH for URLLC, the DCI format including a priority indicator field, the DCI format including a priority indicator field for scheduling the PDSCH, the new DCI format, may be read interchangeably with each other.

[0123] In the present disclosure, at least one of an NR-U field, a specific field, a PDSCH group index field, a Number of requested PDSCH group(s) field, a New feedback indicator (NFI) field, and a One-shot HARQ-ACK request field, and a field for at least one of HARQ-ACK one-shot feedback and an extended dynamic HARQ-ACK codebook, and a field having a size depending on the setting of at least one of upper layer parameters for at least one of HARQ-ACK one-shot feedback and an extended dynamic HARQ-ACK codebook (for example, at least one of pdsch-HARQ-ACK-OneShotFeedback-r16 and pdsch-HARQ-ACK-Codebook=enhancedDynamic-r16), may be read interchangeably with each other.

[0124] (Wireless communication method) <First Embodiment> In the first embodiment, the fields for NR-U included in the second DCI format (for example, DCI format 1_2) will be described. The second DCI format may follow either of the following supports 1 and 2.

[0125] [Support 1] Regarding the second DCI format, all the fields for NR-U included in the first DCI format may be included. In other words, regarding the second DCI format, the UE may perform reception / monitoring of the PDCCH assuming that all the fields for the NR-U system included in the first DCI format are included.

[0126] According to the above support 1, even when URLLC is used in the NR-U system, a common field can be used between the DCI format for URLLC (for example, DCI format 1_2) and the DCI format for eMBB (for example, DCI format 1_1), so the implementation of the UE can be simplified.

[0127] [Support 2] Regarding the second DCI format, only a part (one or more fields) of the fields for NR-U included in the first DCI format may be included. In other words, regarding the second DCI format, the UE may perform reception / monitoring of the PDCCH assuming that one or more fields for NR-U included in the first DCI format are included.

[0128] For example, regarding the second DCI format, a one-shot HARQ-ACK request field may be included. In this case, the UE may perform reception / monitoring of the PDCCH assuming that the one-shot HARQ-ACK request field is included in the second DCI format.

[0129] Also, for example, for the second DCI format, a PDSCH group index field, a Number of requested PDSCH group(s) field, and a New feedback indicator (NFI) field may be included. In this case, the UE may receive / monitor the PDCCH assuming that the PDSCH group index field, the Number of requested PDSCH group(s) field, and the New feedback indicator (NFI) field are included in the second DCI format.

[0130] When the second DCI format does not include at least one NR-U field, the UE may be implicitly notified of the value of this field. In this case, for the NR-U field not included in the second DCI format, the UE may read and use part or all of the bit sequence of other fields included in the second DCI format. Also, for the NR-U field not included in the second DCI format, the UE may read and use, as the bit sequence of the unsupported field, the bit sequence obtained by applying a certain mathematical formula to part or all of the bit sequence of other fields included in the second DCI format.

[0131] According to the above support 2, the payload of the DCI can be set small, enabling more reliable communication.

[0132] <Second Embodiment> In the second embodiment, when the second DCI format is used in the NR-U system, the number of bits of the NR-U field included in the second DCI format will be described.

[0133] When the one-shot HARQ-ACK request field is included in the second DCI format, the number of bits of the one-shot HARQ-ACK request field may be 0 or 1 bit.

[0134] Also, when the PDSCH group index field is included in the second DCI format, the number of bits of the PDSCH group index field may be 0 or 1 bit.

[0135] Also, when the new feedback indicator (NFI) field is included in the second DCI format, the number of bits of the NFI field may be 0, 1 or 2 bits.

[0136] Also, when the number of requested PDSCH group(s) field is included in the second DCI format, the number of bits of the number of requested PDSCH group(s) field may be 0 or 1 bit.

[0137] In this way, even when URLLC is used in the NR-U system, by making the number of bits of the field for NR-U (field for at least one of HARQ-ACK one-shot feedback and extended dynamic HARQ-ACK codebook) in the second DCI format (e.g., DCI format 1_2) the same as the number of bits of the field for NR-U in the first DCI format (e.g., DCI format 1_1), the implementation of the UE can be simplified.

[0138] Alternatively, the number of bits of the NFI field in the second DCI format (e.g., DCI format 1_2) may be different from that in the first DCI format. The number of bits of the NFI field in the second DCI format may be 0 or 1 bit. The NFI field in the second DCI format may have a bit length of 1 bit when a specific upper layer parameter (e.g., pdsch-HARQ-ACK-Codebook) is set to enhanced dynamic (e.g., enhancedDynamic, enhancedDynamic-r16), and may be 0 bits in other cases. The number of bits of the NFI field in the second DCI format may be independent of whether another upper layer parameter is set (enabled) (NFI-TotalDAI-Included-r16 = enable).

[0139] At this time, the UE may determine (recognize) whether the generation / holding (status) of C-DAI, T-DAI, and HARQ-ACK information is reset by the 1-bit NFI included in the second DCI format. In other words, the UE may receive / monitor the PDCCH assuming a DCI including a maximum of 1-bit NFI.

[0140] Also, at this time, after the UE transmits the HARQ-ACK corresponding to the PDSCH of a certain PDSCH group (e.g., PDSCH group i), the UE may receive another PDCCH (DCI) indicating the toggled NFI value of the PDSCH group so that the generation of the HARQ-ACK information of the PDSCH group can be reset, or may always assume (assume, expect) receiving the another PDCCH.

[0141] FIG. 6 is a diagram showing another example of holding and resetting HARQ-ACK information by NFI. The arrangement of each channel, the GI value corresponding to each channel, and LBT in FIG. 6 are the same as those in FIG. 5.

[0142] In the example of FIG. 6, the UE transmits HARQ-ACK1-4 in the resources for HARQ-ACK transmission in COT#1. Next, the UE receives PDCCH5 indicating NFI = 1 (toggled NFI) for resetting the generation of HARQ-ACK information for PDSCH group 0 (GI = 0). Thereafter, the UE receives PDCCH6 indicating NFI = 1 (toggled NFI) for resetting the generation of HARQ-ACK information for PDSCH group 1 (GI = 1). In a case like that of FIG. 6, since the UE transmits HARQ-ACK information for both PDSCH groups 0 and 1 in COT#1, after COT#1 (COT#2), the UE receives a PDCCH (DCI) including the toggled value of NFI for PDSCH groups 0 and 1.

[0143] In this way, when a DCI format for URLLC is used in the NR-U system, by making the number of bits of the field for the NR-U system smaller than that of the DCI format of Rel. 15 (for example, DCI format 1_1), the payload of the DCI can be set smaller, enabling more reliable communication.

[0144] (Wireless communication system) Hereinafter, the configuration of a wireless communication system according to an embodiment of the present disclosure will be described. In this wireless communication system, communication is performed using any one or a combination of the wireless communication methods according to the above embodiments of the present disclosure.

[0145] FIG. 7 is a diagram showing an example of the 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) standardized by the Third Generation Partnership Project (3GPP), the 5th generation mobile communication system New Radio (5G NR), or the like.

[0146] In addition, the wireless communication system 1 may support dual connectivity (Multi-RAT Dual Connectivity (MR-DC)) between multiple Radio Access Technologies (RATs). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), and the like.

[0147] In EN-DC, the base station (eNB) of LTE (E-UTRA) is the Master Node (MN), and the base station (gNB) of NR is the Secondary Node (SN). In NE-DC, the base station (gNB) of NR is the MN, and the base station (eNB) of LTE (E-UTRA) is the SN.

[0148] The wireless communication system 1 may also support dual connectivity between multiple base stations within the same RAT (for example, NR-NR Dual Connectivity (NN-DC) where both the MN and the SN are base stations (gNBs) of NR).

[0149] The wireless communication system 1 may include a base station 11 that forms a relatively wide-coverage macro cell C1, and a base station 12 (12a - 12c) that is disposed within the macro cell C1 and forms a small cell C2 that is narrower than the macro cell C1. The user terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and the user terminal 20 are not limited to the modes 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.

[0150] The user terminal 20 may be connected to at least one of the plurality of base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) and dual connectivity (DC) using a plurality of component carriers (CCs).

[0151] Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). Note that the frequency bands, definitions, etc. of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

[0152] Also, the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0153] The plurality of base stations (for example, RRH) 10 may be connected by wire (for example, an optical fiber compliant with Common Public Radio Interface (CPRI), an 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 upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

[0154] The base station 10 may be connected to the core network 30 via other base stations 10 or directly. The core network 30 may include at least one of, for example, Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), etc.

[0155] The user terminal 20 may be a terminal corresponding to at least one of communication systems such as LTE, LTE-A, 5G, etc.

[0156] In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access method may be used. For example, in at least one of the downlink (DL) and 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.

[0157] The wireless access method may be referred to as a waveform. Note that in the wireless communication system 1, other wireless access methods (for example, other single-carrier transmission methods, other multi-carrier transmission methods) may be used for the UL and DL wireless access methods.

[0158] In the wireless communication system 1, as downlink channels, a Physical Downlink Shared Channel (PDSCH) shared by each user terminal 20, a Physical Broadcast Channel (PBCH), a Physical Downlink Control Channel (PDCCH), etc. may be used.

[0159] Also, in the wireless communication system 1, as uplink channels, a Physical Uplink Shared Channel (PUSCH) shared by each user terminal 20, a Physical Uplink Control Channel (PUCCH), a Physical Random Access Channel (PRACH), etc. may be used.

[0160] User data, upper layer control information, a System Information Block (SIB), etc. are transmitted by the PDSCH. User data, upper layer control information, etc. may be transmitted by the PUSCH. Also, a Master Information Block (MIB) may be transmitted by the PBCH.

[0161] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, downlink control information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0162] Note that the DCI for scheduling the PDSCH may be called a DL assignment, DL DCI, etc., and the DCI for scheduling the PUSCH may be called a UL grant, UL DCI, etc. Note that the PDSCH may be read as DL data, and the PUSCH may be read as UL data.

[0163] For PDCCH detection, a control resource set (CORESET) and a search space may be used. The CORESET corresponds to the resources for searching DCI. The search space corresponds to the search area and search method of PDCCH candidates. One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0164] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be called a search space set. Note that the "search space", "search space set", "search space configuration", "search space set configuration", "CORESET", "CORESET configuration", etc. in the present disclosure may be mutually interchangeable.

[0165] Uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (e.g., may be called Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR) may be transmitted by PUCCH. A random access preamble for connection establishment with the cell may be transmitted by PRACH.

[0166] Note that in the present disclosure, downlink, uplink, etc. may be expressed without "link". Also, "Physical" may not be attached to the beginning of various channels.

[0167] In the wireless communication system 1, a synchronization signal (Synchronization Signal (SS)), a downlink reference signal (Downlink Reference Signal (DL-RS)), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (Cell-specific Reference Signal (CRS)), a channel state information reference signal (Channel State Information Reference Signal (CSI-RS)), a demodulation reference signal (DeModulation Reference Signal (DMRS)), a positioning reference signal (Positioning Reference Signal (PRS)), a phase tracking reference signal (Phase Tracking Reference Signal (PTRS)), etc. may be transmitted.

[0168] 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)). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS / PBCH block, an SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

[0169] Also, in the wireless communication system 1, as the uplink reference signal (Uplink Reference Signal (UL-RS)), a sounding reference signal (Sounding Reference Signal (SRS)), a demodulation reference signal (DMRS), etc. may be transmitted. Note that DMRS may also be called a UE-specific reference signal.

[0170] (Base station) FIG. 8 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 transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that one or more of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

[0171] In this example, the functional blocks of the characteristic parts in the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processes of each part described below may be omitted.

[0172] The control unit 110 controls the entire base station 10. The control unit 110 can be composed of a controller, a control circuit, etc. described based on the common knowledge in the technical field related to the present disclosure.

[0173] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission, reception, measurement, etc. using the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140. The control unit 110 may generate data, control information, a sequence, etc. to be transmitted as a signal and transfer it to the transceiver unit 120. The control unit 110 may perform call processing (setting, releasing, etc.) of a communication channel, state management of the base station 10, management of radio resources, etc.

[0174] The transceiver 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 transceiver unit 120 can be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc. described based on the common knowledge in the technical field related to the present disclosure.

[0175] The transmitting and receiving unit 120 may be configured as an integrated transmitting and receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 1211 and an RF unit 122. The receiving unit may be composed of a reception processing unit 1212, an RF unit 122, and a measurement unit 123.

[0176] The transmitting and receiving antenna 130 can be composed of an antenna described based on the common understanding in the technical field related to the present disclosure, such as an array antenna.

[0177] The transmitting and receiving unit 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitting and receiving unit 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0178] The transmitting and receiving unit 120 may form at least one of a transmission beam and a reception beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

[0179] The transmitting and receiving unit 120 (transmission processing unit 1211) may perform processing of the Packet Data Convergence Protocol (PDCP) layer, processing of the Radio Link Control (RLC) layer (e.g., RLC retransmission control), processing of the Medium Access Control (MAC) layer (e.g., HARQ retransmission control), etc. on, for example, data and control information obtained from the control unit 110, and generate a bit sequence to be transmitted.

[0180] The transmission / reception unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, discrete Fourier transform (DFT) processing (if necessary), inverse fast Fourier transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit sequence to be transmitted, and output a baseband signal.

[0181] The transmission / reception unit 120 (RF unit 122) may perform modulation to the radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the signal in the radio frequency band via the transmission / reception antenna 130.

[0182] On the other hand, the transmission / reception unit 120 (RF unit 122) may perform amplification, filtering, demodulation to the baseband signal, etc. on the signal in the radio frequency band received by the transmission / reception antenna 130.

[0183] The transmission / reception unit 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, fast Fourier transform (FFT) processing, inverse discrete Fourier transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing on the acquired baseband signal, and acquire user data, etc.

[0184] The transmission / reception unit 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0185] The transmission path interface 140 may transmit and receive signals (backhaul signaling) with devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0186] Note that the transmission unit and reception unit of the base station 10 in the present disclosure may be configured by at least one of the transmission / reception unit 120, the transmission / reception antenna 130, and the transmission path interface 140.

[0187] The transmission / reception unit 120 may transmit downlink control information (DCI) including a priority indicator field for scheduling the physical downlink shared channel (PDSCH). The control unit 110 may control the reception of Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) information for the PDSCH based on the DCI. The DCI may include a field for at least one of HARQ-ACK one-shot feedback for the PDSCH and an extended dynamic HARQ-ACK codebook for the PDSCH (First Embodiment).

[0188] (User Equipment) FIG. 9 is a diagram showing an example of the configuration of a user equipment according to an embodiment. The user equipment 20 includes a control unit 210, a transmission / reception unit 220, and a transmission / reception antenna 230. Note that one or more of the control unit 210, the transmission / reception unit 220, and the transmission / reception antenna 230 may be provided respectively.

[0189] Note that in this example, the functional blocks of the characteristic portions in the present embodiment are mainly shown, and the user equipment 20 may be assumed to have other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

[0190] The control unit 210 controls the entire user equipment 20. The control unit 210 may be composed of a controller, a control circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

[0191] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission / reception, measurement, etc. using the transmission / reception unit 220 and the transmission / reception antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transmission / reception unit 220.

[0192] The transceiver 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 transceiver unit 220 may be composed of a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on the common knowledge in the technical field related to the present disclosure.

[0193] The transceiver unit 220 may be configured as an integrated transceiver unit, or may be composed of a transmitter unit and a receiver unit. The transmitter unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiver unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0194] The transceiver antenna 230 may be composed of an antenna described based on the common knowledge in the technical field related to the present disclosure, such as an array antenna.

[0195] The transceiver unit 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver unit 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0196] The transceiver unit 220 may form at least one of a transmission beam and a reception beam by using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), etc.

[0197] The transceiver unit 220 (transmission processing unit 2211) may perform processing of the PDCP layer, processing of the RLC layer (e.g., RLC retransmission control), processing of the MAC layer (e.g., HARQ retransmission control), etc. on, for example, data and control information obtained from the control unit 210, and generate a bit sequence to be transmitted.

[0198] The transmission / reception unit 220 (transmission processing unit 2211) may perform transmission processing such as channel encoding (which may include error correction encoding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, digital-to-analog conversion, etc. on the bit sequence to be transmitted, and output a baseband signal.

[0199] Note that whether to apply DFT processing may be based on the setting of transform precoding. For a certain channel (e.g., PUSCH), when transform precoding is enabled, the transmission / reception unit 220 (transmission processing unit 2211) may perform DFT processing as the above-mentioned transmission processing to transmit the channel using the DFT-s-OFDM waveform, or if not, it may not perform DFT processing as the above-mentioned transmission processing.

[0200] The transmission / reception unit 220 (RF unit 222) may perform modulation to the radio frequency band, filtering, amplification, etc. on the baseband signal, and transmit the radio frequency band signal via the transmission / reception antenna 230.

[0201] On the other hand, the transmission / reception unit 220 (RF unit 222) may perform amplification, filtering, demodulation to the baseband signal, etc. on the radio frequency band signal received by the transmission / reception antenna 230.

[0202] The transmission / reception unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing, etc. to the acquired baseband signal, and acquire user data, etc.

[0203] The transmission / reception unit 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0204] Note that the transmission unit and reception 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.

[0205] The transmission / reception unit 220 may receive downlink control information (DCI) including a priority indicator field for scheduling the physical downlink shared channel (PDSCH). The control unit 210 may control the transmission of Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) information for the PDSCH based on the DCI. The DCI may include fields for at least one of HARQ-ACK one-shot feedback for the PDSCH and an extended dynamic HARQ-ACK codebook for the PDSCH (First Embodiment).

[0206] The DCI may include at least one of a PDSCH group index field, a requested PDSCH group number field, a new feedback indicator field, and a one-shot HARQ-ACK request field (First Embodiment).

[0207] The new feedback indicator field may be 1 bit or less (Second Embodiment).

[0208] When the extended dynamic HARQ-ACK codebook is configured, the DCI may include a 1-bit PDSCH group index field and a 1-bit new feedback indicator field. The new feedback indicator field may correspond to the PDSCH group indicated by the PDSCH group index field (Second Embodiment).

[0209] (Hardware Configuration) Note that the block diagrams used in the description of the above embodiments show functional unit blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly (e.g., using wired, wireless, etc.) connected and realized using these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices.

[0210] Here, functions include, but are not limited to, judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, notification (broadcasting), notification (notifying), communication, forwarding, configuration, reconfiguration, allocation (allocating, mapping), assignment, etc. For example, a functional block (component) that functions to transmit may be referred to as a transmitting unit, a transmitter, etc. In any case, as described above, the realization method is not particularly limited.

[0211] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs the processing of the wireless communication method of the present disclosure. FIG. 10 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment. The above-described base station 10 and user terminal 20 may physically be 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.

[0212] In the present disclosure, words such as device, circuit, device, section, unit, etc. can be read interchangeably with each other. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured without including some devices.

[0213] For example, although only one processor 1001 is shown, there may be a plurality of processors. Also, the processing may be executed by one processor, or the processing may be executed by two or more processors simultaneously, sequentially, or using other methods. Note that the processor 1001 may be implemented by one or more chips.

[0214] Each function in the base station 10 and the user terminal 20 is realized, for example, by causing the processor 1001 to load a predetermined software (program) onto hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations and controls communication via the communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage 1003.

[0215] Processor 1001 controls the entire computer by operating, for example, an operating system. Processor 1001 may be constituted by a Central Processing Unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, etc. For example, at least a part of the above-described control unit 110(210), transmission / reception unit 120(220), etc. may be realized by processor 1001.

[0216] Also, processor 1001 reads a program (program code), software module, data, etc. from at least one of storage 1003 and communication device 1004 into memory 1002, and executes various processes according to these. As the program, a program for causing a computer to execute at least a part of the operations described in the above embodiments is used. For example, control unit 110(210) may be realized by a control program stored in memory 1002 and operating in processor 1001, and the same may be true for other functional blocks.

[0217] Memory 1002 is a computer-readable recording medium, and may be constituted by, for example, at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other appropriate storage media. Memory 1002 may be referred to as a register, cache, main memory (main storage device), etc. Memory 1002 can store a program (program code), software module, etc. executable for implementing the wireless communication method according to an embodiment of the present disclosure.

[0218] Storage 1003 is a computer-readable recording medium, and may be constituted by, for example, at least one of a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (such as Compact Disc ROM (CD-ROM)), a digital versatile disk, a Blu-ray (registered trademark) disk), a removable disk, a hard disk drive, a smart card, a flash memory device (for example, a card, a stick, a key drive), a magnetic stripe, a database, a server, and other appropriate storage media. Storage 1003 may be referred to as an auxiliary storage device.

[0219] Communication device 1004 is hardware (a transmission / reception device) for performing communication 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. Communication device 1004 may include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, or the like in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-described transmission / reception unit 120 (220), transmission / reception antenna 130 (230), or the like may be implemented by communication device 1004. Transmission / reception unit 120 (220) may be physically or logically separated into a transmission unit 120a (220a) and a reception unit 120b (220b).

[0220] Input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or the like) that receives an external input. Output device 1006 is an output device (for example, a display, a speaker, a Light Emitting Diode (LED) lamp, or the like) that performs an output to the outside. Note that input device 1005 and output device 1006 may have an integrated configuration (for example, a touch panel).

[0221] Also, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or may be configured using different buses for each device.

[0222] Also, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), and a Field Programmable Gate Array (FPGA), and some or all of the functional blocks may be realized using the hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0223] (Modification example) In addition, terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol, and signal (signal or signaling) may be read interchangeably with each other. Also, a signal may be a message. A reference signal may also be abbreviated as RS and may be called a pilot, a pilot signal, etc. depending on the applicable standard. Also, a Component Carrier (CC) may be called a cell, a frequency carrier, a carrier frequency, etc.

[0224] A wireless frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting the wireless frame may be called a subframe. Further, a subframe may be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) independent of numerology.

[0225] Here, numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.

[0226] A slot may be composed of one or more symbols (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Also, a slot may be a time unit based on numerology.

[0227] The slot may include a plurality of mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Also, the mini-slot may be called a sub-slot. The mini-slot may be composed of a smaller number of symbols than the slot. The PDSCH (or PUSCH) transmitted in a time unit larger than the mini-slot may be called PDSCH (PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the mini-slot may be called PDSCH (PUSCH) mapping type B.

[0228] The radio frame, sub-frame, slot, mini-slot, and symbol all represent time units for transmitting signals. Different names corresponding to each of them may be used. Note that the time units such as frames, sub-frames, slots, mini-slots, and symbols in the present disclosure may be read interchangeably with each other.

[0229] For example, one sub-frame may be called a TTI, or a plurality of consecutive sub-frames may be called a TTI, or one slot or one mini-slot may be called a TTI. That is, at least one of the sub-frame and the TTI may be the sub-frame (1 ms) in the existing LTE, or a period shorter than 1 ms (for example, 1 - 13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, a mini-slot, etc. instead of a sub-frame.

[0230] Here, the TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) to each user terminal in TTI units. Note that the definition of the TTI is not limited to this.

[0231] The TTI may be a transmission time unit such as a channel-coded data packet (transport block), code block, codeword, etc., or may be a processing unit such as scheduling, link adaptation, etc. When the TTI is given, the time interval (e.g., number of symbols) in which a transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.

[0232] Note that when one slot or one mini-slot is called a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may be the minimum time unit for scheduling. Also, the number of slots (number of mini-slots) constituting the minimum time unit for the scheduling may be controlled.

[0233] A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel.8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than the normal TTI may be called a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, mini-slot, sub-slot, slot, etc.

[0234] Note that the long TTI (e.g., normal TTI, subframe, etc.) may be read as a TTI having a time length exceeding 1 ms, or the short TTI (e.g., shortened TTI, etc.) may be read as a TTI having a TTI length less than that of the long TTI and not less than 1 ms.

[0235] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and in the frequency domain, it may include one or more consecutive subcarriers. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, it may be 12. The number of subcarriers included in an RB may also be determined based on the numerology.

[0236] In addition, an 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. 1 TTI, 1 subframe, etc. may each be composed of one or more resource blocks.

[0237] Note that one or more RBs may also be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0238] Also, a resource block may be composed of one or more resource elements (REs). For example, 1 RE may be a radio resource area of 1 subcarrier and 1 symbol.

[0239] A bandwidth part (BWP) (which may also be called a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (RBs) for a certain numerology in a certain carrier. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. A PRB is defined in a certain BWP and may be numbered within that BWP.

[0240] The BWP may include a UL BWP (BWP for UL) and a DL BWP (BWP for DL). One or more BWPs may be configured within one carrier for a UE.

[0241] At least one of the configured BWPs may be active, and the UE may not be assumed to transmit and receive a predetermined signal / channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

[0242] Note that the structures such as the radio frame, subframe, slot, mini-slot, and symbol described above are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of sub-carriers included in an RB, and the number of symbols within a TTI, symbol length, Cyclic Prefix (CP) length, etc. can be changed in various ways.

[0243] Also, the information, parameters, etc. described in the present disclosure may be represented using absolute values, relative values from a predetermined value, or corresponding other information. For example, a radio resource may be indicated by a predetermined index.

[0244] The names used for parameters, etc. in the present disclosure are not limiting names in any way. Furthermore, the mathematical formulas using these parameters, etc. may be different from those explicitly disclosed in the present disclosure. Since various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, the various names assigned to these various channels and information elements are not limiting names in any way.

[0245] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0246] Also, information, signals, etc. may be output from at least one of the upper layer to the lower layer and from the lower layer to the upper layer. Information, signals, etc. may be input and output via a plurality of network nodes.

[0247] The input and output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information, signals, etc. may be overwritten, updated or appended. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.

[0248] The notification of information is not limited to the aspects / embodiments described in this disclosure and may be performed using other methods. For example, the notification of information in this disclosure may be implemented by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals or a combination thereof.

[0249] Note that physical layer signaling may also be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Also, RRC signaling may also be referred to as an RRC message, and for example, it may be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. Further, MAC signaling may be notified, for example, using a MAC control element (MAC CE).

[0250] Also, the notification of predetermined information (for example, the notification of "being X") is not limited to an explicit notification and may be performed implicitly (for example, by not performing the notification of the predetermined information or by the notification of another piece of information).

[0251] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value represented by true or false, or by a numerical comparison (for example, comparison with a predetermined value).

[0252] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether it is called software, firmware, middleware, microcode, a hardware description language, or by another name.

[0253] Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, optical fiber cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technologies (such as infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of the transmission medium.

[0254] The terms "system" and "network" used in the present disclosure may be used interchangeably. "Network" may mean a device (such as a base station) included in the network.

[0255] In the present disclosure, terms such as "precoding", "precoder", "weight (precoding weight)", "Quasi-Co-Location (QCL)", "Transmission Configuration Indication state (TCI state)", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", "panel", etc. may be used interchangeably.

[0256] In the present disclosure, terms such as "Base Station (BS)", "radio base station", "fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier" may be used interchangeably. The base station may also be referred to by terms such as macro cell, small cell, femto cell, pico cell, etc.

[0257] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each of the smaller areas can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of the base station and the base station subsystem that provides communication services in this coverage.

[0258] In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal" may be used interchangeably.

[0259] The mobile station may also be referred to as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client or some other suitable terms.

[0260] At least one of the base station and the mobile station may be referred to as a transmission device, a reception device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), a moving body that moves unmanned (e.g., a drone, a self-driving car, etc.), or a robot (humanoid or unmanned). Note that at least one of the base station and the mobile station also 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.

[0261] Also, the base station in the present disclosure may be read as a user terminal. For example, for a configuration in which communication between the base station and the user terminal is replaced with communication between a plurality of user terminals (which may be referred to as, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.), each aspect / embodiment of the present disclosure may be applied. In this case, the functions of the above-described base station 10 may be configured to be those of the user terminal 20. Also, terms such as "uplink" and "downlink" may be read as terms corresponding to inter-terminal communication (e.g., "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0262] Similarly, the user terminal in the present disclosure may be read as a base station. In this case, the functions of the above-described user terminal 20 may be configured to be those of the base station 10.

[0263] In the present disclosure, operations assumed to be performed by a base station may, in some cases, be performed by its upper node. In a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (for example, Mobility Management Entity (MME), Serving-Gateway (S-GW), etc., which are conceivable but not limited thereto), or a combination thereof.

[0264] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched and used during execution. Also, the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be reordered as long as there is no contradiction. For example, regarding the method described in the present disclosure, elements of various steps are presented using an exemplary order and are not limited to the presented specific order.

[0265] Each aspect / embodiment described in the present disclosure may be applicable to systems using 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), 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), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable wireless communication methods, next-generation systems extended based on these, etc. Further, it may be applied in combination with a plurality of systems (for example, a combination of LTE or LTE-A and 5G, etc.).

[0266] The description "based on" used in the present disclosure does not mean "only based on" unless otherwise specified. In other words, the description "based on" means both "only based on" and "at least based on".

[0267] Any reference to an element using designations such as "first", "second", etc. used in the present disclosure does not generally limit the quantity or order of those elements. These designations may be used in the present disclosure as a convenient way to distinguish between two or more elements. Therefore, a reference to a first and a second element does not mean that only two elements can be employed or that the first element must precede the second element in some form.

[0268] As used herein, the term "determining" may encompass a wide variety of operations. For example, "determining" may be considered to be "judging", "calculating", "computing", "processing", "deriving", "investigating", "looking up, searching, inquiring" (e.g., searching in a table, database or another data structure), "ascertaining", etc.

[0269] Also, "determining" may be considered to be "receiving" (e.g., receiving information), "transmitting" (e.g., transmitting information), "input", "output", "accessing" (e.g., accessing data in memory), etc.

[0270] Also, "determining" may be considered to be "resolving", "selecting", "choosing", "establishing", "comparing", etc. That is, "determining" may be considered to be making some kind of operation.

[0271] Also, "determining" may be read as "assuming", "expecting", "considering", etc.

[0272] As used in this disclosure, the terms "connected" and "coupled," or any variations thereof, mean any direct or indirect connection or coupling between two or more elements, and can include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements can be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed."

[0273] In this disclosure, when two elements are connected, they can be considered to be "connected" or "coupled" to each other using one or more electric wires, cables, printed electrical connections, etc., and also, as some non-limiting and non-exhaustive examples, using electromagnetic energy having wavelengths in the radio frequency region, microwave region, optical (both visible and invisible) region, etc.

[0274] In this disclosure, the term "A and B are different" may mean that "A and B are different from each other." Note that the term may also mean that "A and B are each different from C." Terms such as "separate," "coupled," etc. may also be interpreted in the same way as "different."

[0275] In this disclosure, when the terms "include," "including," and their variations are used, these terms are intended to be inclusive in the same way as the term "comprising." Further, the term "or" used in this disclosure is not intended to be an exclusive disjunction.

[0276] In this disclosure, for example, when articles are added by translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are in the plural form.

[0277] Although the invention according to the present disclosure has been described in detail above, it is obvious 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 modifications and variations 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 illustrative purposes and does not bring any restrictive meaning to the invention according to the present disclosure.

Claims

1. A receiving unit that receives downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), the DCI including a one-shot Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) request field; A control unit that controls transmission of HARQ-ACK information for the PDSCH based on the one-shot HARQ-ACK request field; and The DCI is DCI format 1_2; A terminal in which a PDSCH group index field, a requested PDSCH group number field, and a new feedback indicator field are not supported in the DCI.

2. The terminal according to claim 1, wherein the DCI format 1_2 is a DCI format for Ultra-Reliable and Low-Latency Communications (URLLC).

3. The terminal according to claim 1, wherein the one-shot HARQ-ACK request field is 1 bit when a specific upper layer parameter is set, and the one-shot HARQ-ACK request field is 0 bit when the specific upper layer parameter is not set.

4. Receiving downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), the DCI including a one-shot Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) request field; Controlling transmission of HARQ-ACK information for the PDSCH based on the one-shot HARQ-ACK request field; and The DCI is DCI format 1_2; A wireless communication method for a terminal in which a PDSCH group index field, a requested PDSCH group number field, and a new feedback indicator field are not supported in the DCI.

5. A transmitting unit that transmits downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH), the DCI including a one-shot Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) request field; A control unit that uses the one-shot HARQ-ACK request field to indicate transmission of HARQ-ACK information for the PDSCH. The DCI is DCI format 1_2. A base station that does not support a PDSCH group index field, a requested PDSCH group number field, and a new feedback indicator field in the DCI. **Claim 6** A system having a base station and a terminal, wherein the base station has a transmission unit that transmits downlink control information (DCI) for scheduling a physical downlink shared channel (PDSCH) including a one-shot Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) request field; wherein the terminal has a reception unit that receives the DCI, and a control unit that controls transmission of HARQ-ACK information for the PDSCH based on the one-shot HARQ-ACK request field; the DCI is DCI format 1_2, and in the DCI, a PDSCH group index field, a requested PDSCH group number field, and a new feedback indicator field are not supported.

Images