Terminal, wireless communication method and system

By combining HARQ-ACK information bits with varying coding rates and time positioning in multiple HARQ-ACK codebooks, the terminal effectively addresses the challenge of overlapping HARQ-ACK transmissions in future wireless communication systems, ensuring system performance.

JP7592125B2Active Publication Date: 2024-11-29NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2023117956
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-07-20
Publication Date
2024-11-29
Estimated Expiration
2038-09-28

AI Technical Summary

Technical Problem

In future wireless communication systems like LTE Rel.15 or later, 5G, and NR, the generation of Hybrid Automatic Repeat reQuest (HARQ)-ACK codebooks becomes challenging when multiple HARQ-ACKs have the same transmission timings, leading to potential system performance deterioration.

Method used

A terminal is configured to receive multiple HARQ-ACK codebooks with different priorities, where HARQ-ACK information bits are combined into one Physical Uplink Control Channel (PUCCH) with varying coding rates and time positioning, and the HARQ-ACK codebook is generated appropriately even when transmission timings overlap.

Benefits of technology

This approach allows for the proper generation and transmission of HARQ-ACK codebooks, even when multiple HARQ-ACKs have the same timing, thereby maintaining system performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007592125000001
    Figure 0007592125000001
  • Figure 0007592125000002
    Figure 0007592125000002
  • Figure 0007592125000003
    Figure 0007592125000003
Patent Text Reader

Abstract

To appropriately generate a HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement) codebook even when transmission timings of a plurality of HARQ-ACKs are the same.SOLUTION: A terminal has: a control unit that generates a first HARQ-ACK codebook related to a first priority, and a second HARQ-ACK codebook related to a second priority different from the first priority; and a transmission unit that transmits a first HARQ-ACK information bit based on the first HARQ-ACK codebook and a second HARQ-ACK information bit based on the second HARQ-ACK codebook in one PUCCH (Physical Uplink Control Channel). An encoding rate used for the first HARQ-ACK information bit and that used for the second HARQ-ACK information bit can be set to values different from each other.SELECTED DRAWING: Figure 10
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a terminal, a wireless communication method and a system in a next-generation mobile communication system. [Background technology]

[0002] In the Universal Mobile Telecommunications System (UMTS) network, LTE (Long Term Evolution) has been specified for the purpose of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of achieving higher capacity and greater sophistication of LTE (3GPP (Third Generation Partnership Project) Rel. (Release) 8, 9).

[0003] Successor systems to LTE (e.g., 5G (5th generation mobile communication system), 5G+ (plus), NR (New Radio), 3GPP Rel. 15 or later) are also being considered.

[0004] Furthermore, in existing LTE systems (e.g., LTE Rel. 8-13), a user terminal transmits uplink control information (UCI) using an uplink control channel (e.g., PUCCH: Physical Uplink Control Channel) or an uplink shared channel (e.g., PUSCH: Physical Uplink Shared Channel). The configuration (format) of the uplink control channel is called a PUCCH format, etc. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010 Summary of the Invention [Problem to be solved by the invention]

[0006] In future wireless communication systems (e.g., LTE Rel. 15 or later, 5G, 5G+, NR, etc.), when UCI is transmitted using an uplink control channel (e.g., PUCCH), it is being considered to determine resources for the uplink control channel (e.g., PUCCH resources) based on higher layer signaling and a predetermined field value in downlink control information (DCI).

[0007] In addition, in NR, a study is being conducted to specify the transmission timing of a delivery acknowledgement signal (HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement)) for a DL signal (e.g., PDSCH) to a UE by DCI that schedules the PDSCH. Therefore, there may be cases where HARQ-ACK corresponding to PDSCH transmitted in different transmission periods (e.g., slots) is transmitted in the same slot.

[0008] The UE feeds back the HARQ-ACK based on the codebook (per codebook), but when multiple HARQ-ACKs are transmitted in the same slot, how to control the generation of the HARQ-ACK codebook becomes an issue. If the HARQ-ACK codebook cannot be generated appropriately, degradation of system performance may occur.

[0009] Therefore, an object of the present disclosure is to provide a terminal, a wireless communication method, and a system that can appropriately generate a HARQ-ACK codebook even when multiple HARQ-ACKs are transmitted at the same timing. [Means for solving the problem]

[0010] A terminal according to one embodiment of the present disclosure includes: a control unit that generates a first Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) codebook associated with a first priority and a second HARQ-ACK codebook associated with a second priority different from the first priority; and a transmission unit that transmits, in one Physical Uplink Control Channel (PUCCH), first HARQ-ACK information bits based on the first HARQ-ACK codebook and second HARQ-ACK information bits based on the second HARQ-ACK codebook, and when a PUCCH including the first HARQ-ACK information bits and a PUCCH including the second HARQ-ACK information bits overlap, the control unit controls the transmission unit to transmit, in the one PUCCH, one of the first HARQ-ACK information bits and the second HARQ-ACK information bits so that the one HARQ-ACK information bit is located earlier in the time direction than the other HARQ-ACK information bit. Concatenating the first HARQ-ACK information bit and the second HARQ-ACK information bit And the above Concatenated A coding rate used for the first HARQ-ACK information bit, Concatenated The coding rate may be set to a value different from that used for the second HARQ-ACK information bits. Effect of the Invention

[0011] According to one aspect of the present disclosure, even if multiple HARQ-ACKs are transmitted at the same timing, a HARQ-ACK codebook can be appropriately generated. [Brief description of the drawings]

[0012] [Figure 1]FIG. 1 is a diagram illustrating an example of HARQ-ACK feedback for a UE that supports only eMBB services. [Diagram 2] FIG. 2 is a diagram illustrating an example of HARQ-ACK feedback of a UE that supports only URLLC services. [Diagram 3] FIG. 3 illustrates an example of HARQ-ACK feedback for a UE supporting eMBB and URLLC services. [Figure 4] FIG. 4 is a diagram illustrating an example of HARQ-ACK codebook generation according to aspect 1-1. [Diagram 5] 5A and 5B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 1 and CBG configuration methods 1 and 2 of aspect 1-2. [Figure 6] 6A and 6B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 2 and CBG configuration methods 1 and 2 of aspect 1-2. [Figure 7] FIG. 7 is a diagram illustrating an example of HARQ-ACK codebook generation according to aspect 2-1. [Figure 8] 8A and 8B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 1, and CBG setting methods 1 and 2 of aspect 2-2-1. [Figure 9] 9A and 9B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 2, and CBG setting methods 1 and 2 of aspect 2-2-1. [Figure 10] 10A and 10B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 1, and CBG setting methods 1 and 2 of aspect 2-2-1. [Figure 11] 11A and 11B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 2, and CBG setting methods 1 and 2 of aspect 2-2-1. [Figure 12]12A and 12B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 1, and CBG setting methods 1 and 2 of aspect 2-2-2. [Figure 13] 13A and 13B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 2, and CBG setting methods 1 and 2 of aspect 2-2-2. [Figure 14] 14A and 14B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 1, and CBG setting methods 1 and 2 of aspect 2-2-2. [Figure 15] 15A and 15B are diagrams illustrating an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 2, and CBG setting methods 1 and 2 of aspect 2-2-2. [Figure 16] FIG. 16 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of the configuration of a base station according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] (HARQ-ACK codebook) In future wireless communication systems (for example, NR), it is considered that a user terminal will determine a HARQ-ACK codebook (which may also be called a HARQ-ACK size) semi-statically or dynamically. A base station may notify a user terminal of information indicating a method for determining a HARQ-ACK codebook, for example, information indicating whether the HARQ-ACK codebook is semi-static or dynamic, by higher layer signaling for each component carrier, each cell group (CG), each PUCCH group, or each user terminal.

[0014] The HARQ-ACK codebook may be interpreted as a PDSCH HARQ-ACK codebook, a HARQ-ACK codebook size, the number of HARQ-ACK bits, or the like.

[0015] In the present disclosure, higher layer signaling may be, for example, any one of RRC signaling, Medium Access Control (MAC) signaling, and broadcast information, or a combination thereof.

[0016] The MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. The broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0017] The user terminal may determine (generate) a HARQ-ACK information bit based on the determined HARQ-ACK codebook for each component carrier, each cell group, each PUCCH group, or each user terminal, and may transmit the generated HARQ-ACK using at least one of the uplink control channel (PUCCH) or the uplink shared channel (PUSCH).

[0018] When a user terminal is configured to semi-statically determine a HARQ-ACK codebook or is configured with a semi-static HARQ-ACK codebook, the determination of the HARQ-ACK codebook may be referred to as Type 1 HARQ-ACK codebook determination. When a user terminal is configured to dynamically determine a HARQ-ACK codebook or is configured with a dynamic HARQ-ACK codebook, the determination of the HARQ-ACK codebook may be referred to as Type 2 HARQ-ACK codebook determination.

[0019] The type 1 HARQ-ACK codebook and the semi-static HARQ-ACK codebook may be interchangeable, and the type 2 HARQ-ACK codebook and the dynamic HARQ-ACK codebook may be interchangeable.

[0020] In the type 1 HARQ-ACK codebook determination, the user terminal may determine the number of HARQ-ACK bits, etc. based on a configuration set by higher layer signaling. The set configuration may include, for example, a DL (Downlink) transmission, e.g., a maximum or minimum number of PDSCHs, to be scheduled over a range associated with the feedback timing of the HARQ-ACK.

[0021] The range is also called a HARQ-ACK bundling window, a HARQ-ACK feedback window, a bundling window, a feedback window, etc. The bundling window may correspond to at least one range of space, time, and frequency.

[0022] When determining a type 2 HARQ-ACK codebook, the user terminal may determine the number of HARQ-ACK bits, etc., based on downlink control information, for example, a bit string in a Downlink Assignment Index (DAI) field included in a DL assignment.

[0023] The DAI field may indicate at least one of a total DAI and a counter DAI.

[0024] The total DAI is information on the total number of DL data (PDSCH) to be scheduled, and may correspond to the total number of bits of HARQ-ACK fed back by the user terminal or the codebook size.

[0025] The counter DAI is information on the cumulative value of scheduled DL data (PDSCH). For example, the counter DAI numbered in the order of component carrier index may be included in the Downlink Control Information (DCI) of one or more component carriers detected in a certain time unit, for example, a slot or a subframe. When HARQ-ACKs for PDSCHs scheduled over multiple time units are fed back together, for example, when a bundling window is composed of multiple slots, the counter DAI may be applied over the multiple time units.

[0026] Also, if the UE is not configured with code block group (CBG)-based transmission (CBG-based HARQ-ACK codebook determination) by the higher layer parameter (PDSCH code block group transmission information element, PDSCH-CodeBlockGroupTransmission), the UE assumes transport block (TB)-based transmission (TB-based HARQ-ACK codebook determination). That is, the UE generates HARQ-ACK information bits for each TB.

[0027] When the UE is provided with higher layer parameters of the PDSCH code block group transmission information element for the serving cell (Component Carrier: CC), the UE receives a PDSCH including multiple CBGs for one TB. The PDSCH code block group transmission information element includes the maximum number of CBGs in one TB (maxCodeBlockGroupsPerTransportBlock). The UE generates HARQ-ACK information bits for each of the multiple CBGs for the TB reception of the serving cell, and generates a HARQ-ACK codebook including the maximum number of HARQ-ACK information bits for the CBG.

[0028] The DCI used for scheduling the PDSCH may include CBG Transmission Information (CBGTI) and CBG Flushing Out Information (CBGFI). The CBGTI may indicate which CBG in the TB is to be transmitted. The CBGFI may indicate whether a retransmitted CBG can be combined with a previously received same CBG or not. The UE may be indicated whether the CBGFI is valid or not by a higher layer parameter (codeBlockGroupFlushIndicator) in the PDSCH code block group transmission information element.

[0029] (PDSCH-to-ACK timing) In future wireless communication systems (e.g., NR), a user terminal determines the transmission timing of a HARQ-ACK corresponding to a received PDSCH based on a DCI that schedules the PDSCH. The timing may be referred to as PDSCH-to-ACK timing, K1, etc. The DCI may be referred to as DL DCI, DL assignment, DCI format 1_0, DCI format 1_1, etc.

[0030] For example, when a user terminal detects DCI format 1_0, it transmits a HARQ-ACK corresponding to the PDSCH in slot (n+k) (where k is an integer from 1 to 8, for example) based on the HARQ timing indication field (PDSCH-to-HARQ-timing-indicator field) corresponding to the PDSCH contained in the DCI, and with slot n including the final symbol of the PDSCH as a reference.

[0031] When the user terminal detects DCI format 1_1, the user terminal transmits a HARQ-ACK corresponding to the PDSCH in slot (n+k) (where k is an integer from 1 to 8, for example) based on a HARQ timing indication field (PDSCH-to-HARQ-timing-indicator field) corresponding to the PDSCH included in the DCI, with slot n including the last symbol of the PDSCH as a reference. Here, the correspondence between k and the timing indication field may be configured in the user terminal for each PUCCH, PUCCH group, or cell group by higher layer signaling.

[0032] For example, the above correspondence may be set by a parameter included in a PUCCH Config information element of RRC signaling. The parameter may be called dl-DataToUL-ACK, Slot-timing-value-K1, etc. For example, multiple candidate values ​​of the PDSCH-to-ACK timing indication may be set by higher layer signaling using K1, and one of the multiple candidate values ​​may be indicated by DCI for scheduling the PDSCH.

[0033] K1 may be set for each PUCCH group or cell group. K1 may be a time determined based on the numerology (e.g., subcarrier spacing) of the channel, e.g., PUCCH or PUSCH, on which the HARQ-ACK is transmitted.

[0034] (PUCCH Resources) In future wireless communication systems (e.g., LTE Rel. 15 and later, 5G, NR, etc.), configurations (formats, also called PUCCH formats (PFs)) for uplink control channels (e.g., PUCCH) used to transmit UCI are under consideration. For example, in LTE Rel. 15, support for five types of PFs 0 to 4 is under consideration. Note that the names of the PFs shown below are merely examples, and different names may be used.

[0035] For example, PF0 and PF1 are PFs used for transmitting UCI of up to 2 bits (for example, delivery acknowledgement information (HARQ-ACK: Hybrid Automatic Repeat reQuest-Acknowledge, also called ACK or NACK, etc.)). PF0 can be assigned to 1 or 2 symbols, and is therefore also called a short PUCCH or sequence-based short PUCCH, etc. On the other hand, PF1 can be assigned to 4 to 14 symbols, and is therefore also called a long PUCCH, etc. With PF1, multiple user terminals may be code division multiplexed (CDM) within the same PRB by block spreading in the time domain using at least one of CS and OCC.

[0036] PF2-4 are PFs used for transmitting UCI of more than 2 bits (for example, Channel State Information (CSI) (or CSI and HARQ-ACK and / or Scheduling Request (SR))). PF2 can be assigned to 1 or 2 symbols, and is therefore also called a short PUCCH, etc. Meanwhile, PF3 and PF4 can be assigned to 4-14 symbols, and are therefore also called long PUCCH, etc. With PF4, multiple user terminals may be CDM-spread using (frequency domain) block spreading before DFT.

[0037] The allocation of resources (e.g., PUCCH resources) used for transmitting the uplink control channel is performed using higher layer signaling and / or downlink control information (DCI). Here, the higher layer signaling may be at least one of RRC (Radio Resource Control) signaling, system information (e.g., at least one of RMSI: Remaining Minimum System Information, OSI: Other system information, MIB: Master Information Block, and SIB: System Information Block), and broadcast information (PBCH: Physical Broadcast Channel).

[0038] Specifically, one or more sets (PUCCH resource sets), each including one or more PUCCH resources, are notified (configured) to a user terminal by higher layer signaling. For example, K (e.g., 1≦K≦4) PUCCH resource sets may be notified to a user terminal from a radio base station. Each PUCCH resource set may include M (e.g., 8≦M≦32) PUCCH resources.

[0039] The user terminal may determine a single PUCCH resource set from the configured K PUCCH resource sets based on a payload size of the UCI (UCI payload size), which may be the number of bits of the UCI excluding Cyclic Redundancy Code (CRC) bits.

[0040] The user terminal may determine a PUCCH resource to be used for transmitting UCI from the M PUCCH resources included in the determined PUCCH resource set, based on at least one of DCI (PUCCH resource indicator field) and implicit information (also referred to as implicit indication information or implicit index, etc.). The implicit indication may be at least one of the number of CCEs in a CORESET of a PDCCH reception carrying the DCI, an index of the top CCE of the PDCCH reception, and the number of PUCCH resources in a PUCCH resource set.

[0041] When PUCCH resource sets #0 to #3 are configured for a user terminal, the user terminal selects one of the PUCCH resource sets based on the UCI payload size.

[0042] For example, when the UCI payload size is 1 or 2 bits, PUCCH resource set #0 is selected. When the UCI payload size is 3 bits or more and N2-1 bits or less, PUCCH resource set #1 is selected. When the UCI payload size is N2 bits or more and N3-1 bits or less, PUCCH resource set #2 is selected. Similarly, when the UCI payload size is N3 bits or more and N3-1 bits or less, PUCCH resource set #3 is selected.

[0043] In this way, the range of UCI payload sizes for which PUCCH resource set #i (i = 0, ..., K-1) is selected is N i Bits or more N i+1 -1 bit or less (i.e., {N i ,…,N i+1 -1} bits).

[0044] Here, the starting positions (starting bit numbers) N0, N1 of the UCI payload size for PUCCH resource sets #0, #1 may be 1, 3, respectively. Thus, when transmitting UCI of 2 bits or less, PUCCH resource set #0 is selected, and therefore PUCCH resource set #0 may include PUCCH resources #0 to #M-1 for at least one of PF0 and PF1. On the other hand, when transmitting UCI of more than 2 bits, one of PUCCH resource sets #1 to #3 is selected, and therefore PUCCH resource sets #1 to #3 may each include PUCCH resources #0 to #M-1 for at least one of PF2, PF3, and PF4.

[0045] In addition, in NR, the transmission timing (for example, K1) of the HARQ-ACK for the PDSCH is notified to the UE by using DCI that schedules the PDSCH. K1 may be information on a slot in which a PUCCH resource is set.

[0046] The UE controls the transmission of HARQ-ACK based on the PUCCH resource set notified by the base station and the transmission timing of HARQ-ACK notified by the DCI that schedules the PDSCH. The transmission of HARQ-ACK is controlled by using the HARQ-ACK codebook (HARQ-ACK codebook unit).

[0047] Since the HARQ-ACK transmission timing for each PDSCH can be flexibly set by DCI, there may be cases where the transmission timing of HARQ-ACK for PDSCHs transmitted in different slots is set to the same slot.

[0048] 1 shows a case where the transmission timing of the HARQ-ACK for PDSCH#1 transmitted in slot (SL_#1) and the HARQ-ACK for PDSCH#2 transmitted in slot (SL_#3) are set to the same slot (here, slot (SL_#7)). For example, when K1=6 included in DCI#1 scheduling PDSCH#1 and K1=4 included in DCI#2 scheduling PDSCH#2, the transmission timing of HARQ-ACK#1 and HARQ-ACK#2 are set to the same slot (SL_#7).

[0049] If the UE only supports eMBB (enhanced Mobile Broadband) services, the UE may not expect to transmit multiple PUCCHs with HARQ-ACK information in one slot. The UE may multiplex multiple HARQ-ACKs into one HARQ-ACK codebook in one slot when the feedback timing of multiple HARQ-ACKs for multiple PDSCHs is indicated to be the same slot.

[0050] A UE that only supports eMBB services may determine one PUCCH resource for transmission of one HARQ-ACK codebook based on the last detected DCI, as shown in FIG. 1.

[0051] If the UE supports only the Ultra Reliable and Low Latency Communications (URLLC) service, the UE may transmit multiple PUCCHs with HARQ-ACK information in one slot to reduce latency. The UE may divide multiple HARQ-ACKs into multiple HARQ-ACK codebooks in one slot even if the feedback timings of multiple HARQ-ACKs for multiple PDSCHs are instructed to be the same slot.

[0052] In the example of Figure 2, a UE that supports only URLLC services is instructed to feedback the HARQ-ACK of PDSCH#1 and #2 in the same slot (SL#7) as in Figure 1, but may use different PUCCH resources in the same slot based on the PUCCH resource notification fields of DCI#1 and #2.

[0053] When a UE supports multiple services with different requirements (e.g., when the UE supports both eMBB service and URLLC service, or when the UE supports two URLLC services with different requirements), when the UE multiplexes multiple HARQ-ACKs for the PDSCHs of multiple services within the same PUCCH resource, it is not clear what kind of HARQ-ACK codebook the UE should generate.

[0054] The example of Figure 3 shows a case where the transmission timings of the HARQ-ACK for PDSCH #1 of the eMBB service transmitted in slot (SL_#1), the HARQ-ACK for PDSCH #2 of the eMBB service transmitted in slot (SL_#2), the HARQ-ACK for PDSCH #3 of the URLLC service transmitted in slot (SL_#3), and the HARQ-ACK for PDSCH #4 of the URLLC service transmitted in slot (SL_#4) are set to the same slot (here, slot (SL_#7)).

[0055] In such a case, it is not clear what kind of HARQ-ACK codebook a UE that supports multiple services should generate. If the HARQ-ACK codebook cannot be generated appropriately, degradation of system performance may occur.

[0056] Therefore, the present inventors came up with the idea of ​​generating HARQ-ACK information based on a plurality of downlink data having different communication requirements, and transmitting the HARQ-ACK information in one uplink channel resource.

[0057] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0058] In the present disclosure, a service (service type) may be defined by at least one of communication requirements (e.g., reliability, latency, etc.) and parameters used for scheduling (such as a Modulation and Coding Scheme (MCS) table and a Radio Network Temporary Identifier (RNTI)). For example, a UE may use (be configured with) different MCS tables for PDSCHs of different services. For example, the CRCs of DCIs for scheduling the PDSCHs of different services may be scrambled using different RNTIs.

[0059] Alternatively, the service type (or traffic type) corresponding to URLLC and the service type corresponding to eMBB may be identified based on at least one of the following: · Logical channels with different priorities Modulation and Coding Scheme (MCS) table (MCS index table) DCI format Used to scramble (mask) the Cyclic Redundancy Check (CRC) bits included (added) in the DCI (DCI format) (Radio Network Temporary Identifier (RNTI)) RRC (Radio Resource Control) parameters A specific RNTI (e.g., RNTI for URLLC, MCS-C-RNTI, etc.) Search Space - Predefined fields in DCI (e.g., new fields being added or existing fields being reused)

[0060] Below, we will describe an example in which a UE supports a first service and a second service, where the first service is an eMBB service and the second service is a URLLC service, but the first service may be a first URLLC service, and the second service may be a second URLLC service having requirements different from the requirements of the first URLLC service.

[0061] Case 2 describes an example in which the UE is configured with CBG-based transmission only for the eMBB service. In this example, the TB-based transmission is used for the URLLC service because the reliability of the URLLC service is high, the probability of retransmission is low, the delay of the URLLC service is small, and it is preferable to reduce the number of HARQ-ACK information bits. On the other hand, the following embodiment can also be applied to a case in which the UE is configured with TB-based transmission for the eMBB service (first service) and CBG-based transmission for the URLLC service (second service) when sufficient resources for retransmission can be secured for the eMBB service. The following embodiment can also be applied to a case in which the first service is the URLLC service and the second service is the eMBB service.

[0062] Hereinafter, a case where one HARQ-ACK codebook includes multiple HARQ-ACK sub-codebooks and a case where one HARQ-ACK sub-codebook includes multiple HARQ-ACK sub-sub-codebooks will be described, but a HARQ-ACK codebook may be used instead of the HARQ-ACK sub-codebook. In this case, one HARQ-ACK codebook may be read as two concatenated HARQ-ACK codebooks, a HARQ-ACK sub-codebook may be read as a HARQ-ACK codebook, and a HARQ-ACK sub-sub-codebook may be read as a HARQ-ACK sub-codebook.

[0063] In the following, a case will be described where the UE transmits HARQ-ACK codebooks for multiple PDSCHs in one PUCCH resource, but they may also be transmitted (piggybacked) in one PUSCH resource.

[0064] (Wireless communication method) In the HARQ-ACK codebook of a UE supporting multiple services, the following cases 1 and 2 need to be considered.

[0065] [Case 1] The UE is configured with transport block (TB)-based HARQ-ACK, in other words, the UE is not configured with code block group (CBG)-based HARQ-ACK.

[0066] [Case 2] The UE is configured for TB based transmission and CBG based transmission.

[0067] (Aspect 1) The UE may generate multiple HARQ-ACKs for different services together. In other words, the UE may generate multiple HARQ-ACKs for different services without distinguishing them. The UE may generate information in which multiple HARQ-ACKs for different services are mixed.

[0068] The UE may take different actions for cases 1 and 2 above.

[0069] <Aspect 1-1> For case 1, the UE may jointly encode HARQ-ACKs for different services.

[0070] The UE may count the DAIs for different services together.

[0071] In the example diagram below, the first service is an eMBB service and the second service is a URLLC service.

[0072] FIG. 4 is a diagram illustrating an example of HARQ-ACK codebook generation according to aspect 1-1.

[0073] The UE is not configured for CBG based transmission on CC1, 2, and 3. Therefore, the UE generates HARQ-ACK for TB based transmission on CC1, 2, and 3 (performs TB based HARQ-ACK codebook decision).

[0074] The UE receives the PDSCH of the eMBB service on CC1 and CC2, and receives the PDSCH of the URLLC service on CC2 and CC3.

[0075] The UE counts DAI for TB-based transmissions regardless of the PDSCH service.

[0076] The UE counts the counter DAI in the order of the CC index, then counts the counter DAI in the order of the slot index, and counts the total DAI in the order of the slot index.

[0077] The UE generates one HARQ-ACK information bit for every 1 TB.

[0078] The UE arranges the HARQ-ACK information bits in the HARQ-ACK codebook in the order of CC index, and then arranges the HARQ-ACK information bits in the HARQ-ACK codebook in the order of slot index. In other words, the UE arranges the HARQ-ACK codebook regardless of the first service and the second service.

[0079] According to this aspect 1-1, the UE can appropriately transmit HARQ-ACKs for PDSCHs of different services as one HARQ-ACK codebook.

[0080] <Aspect 1-2> For case 2, the UE may generate two HARQ-ACK sub-codebooks (sub-codebooks).

[0081] The two sub-codebooks may be a sub-codebook for TB-based transmission and a sub-codebook for CBG-based transmission. In other words, the UE may determine the position of the HARQ-ACK information bit in the HARQ-ACK codebook based on the service corresponding to the HARQ-ACK information bit. Also, the UE may arrange the HARQ-ACK information bits for TB-based transmission consecutively in the HARQ-ACK codebook, and arrange the HARQ-ACK information bits for base transmission consecutively in the HARQ-ACK codebook.

[0082] If the UE supports the first service and the second service, the UE may be configured with CBG based transmission for at least one of the first service and the second service according to one of the following CBG configuration methods 1 and 2.

[0083] [CBG setting method 1] In a serving cell configured with CBG-based transmission by higher layer signaling, the UE may expect the PDSCH of the first service to be CBG-based transmission and may generate a HARQ-ACK for the CBG-based transmission of the first service (may perform a CBG-based HARQ-ACK codebook decision). The DCI for scheduling the PDSCH of the first service may include information indicating the CBG to be transmitted (CBG transmission information, e.g., CBGTI).

[0084] In a serving cell configured with CBG-based transmission by higher layer signaling, the UE may expect the PDSCH of the second service to be TB-based transmission and may generate a HARQ-ACK for the TB-based transmission of the second service (may perform a TB-based HARQ-ACK codebook decision). The DCI for scheduling the PDSCH of the second service may not include information indicating the CBG to be transmitted (CBG transmission information, e.g., CBGTI).

[0085] That is, even if CBG-based transmission is configured for a serving cell by higher layer signaling, CBG-based transmission does not have to be applied to the PDSCH of the second service on the serving cell.

[0086] [CBG setting method 2] In a serving cell configured with CBG-based transmission by higher layer signaling, the UE may expect the PDSCH to be CBG-based transmission regardless of whether it is the first service or the second service, and may generate a HARQ-ACK for the CBG-based transmission (may perform a CBG-based HARQ-ACK codebook decision). The DCI for scheduling the PDSCH may include information indicating the CBG to be transmitted (CBG transmission information, e.g., CBGTI).

[0087] The UE may generate one HARQ-ACK codebook by concatenating two sub-codebooks. The UE may concatenate the two sub-codebooks according to one of the following concatenation methods 1 and 2.

[0088] [Connection method 1] The UE preconfigures the sub-codebook for TB based transmission.

[0089] [Connection method 2] The UE preconfigures the sub-codebook for CBG based transmission.

[0090] The UE may count the DAI for TB based transmission and the DAI for CBG based transmission separately.

[0091] Fig. 5A is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 1 and CBG configuration method 1 of aspect 1-2. Differences from Fig. 4 will be mainly described.

[0092] The UE is configured with CBG-based transmission for CC2, and the maximum CBG number is set to 4. The UE expects the PDSCH of the eMBB service in CC2 to be CBG-based transmission. Meanwhile, the UE expects the PDSCH of the URLLC service in CC2 to be TB-based transmission. Thus, the UE generates HARQ-ACKs for the eMBB service and CBG-based transmission, and HARQ-ACKs for the URLLC service and TB-based transmission in CC2.

[0093] The UE counts the DAI for TB-based transmission and the DAI for CBG-based transmission separately, regardless of the PDSCH service.

[0094] The UE generates one HARQ-ACK information bit per TB for TB-based transmission, and one HARQ-ACK information bit per CBG for CBG-based transmission.

[0095] The UE places the HARQ-ACK information bits for TB-based transmission in the first sub-codebook in the order of CC index and slot index, and places the HARQ-ACK information bits for CBG-based transmission in the second sub-codebook in the order of CC index and slot index.

[0096] Fig. 5B is a diagram showing an example of HARQ-ACK codebook generation according to the concatenation method 1 and the CBG configuration method 2 of aspect 1-2. Differences from Fig. 5A will be mainly described.

[0097] The UE is configured with CBG-based transmission for CC2, and the maximum CBG number is set to 4. The UE expects the PDSCH of the eMBB service of CC2 to be CBG-based transmission, and expects the PDSCH of the URLLC service of CC2 to be CBG-based transmission. Thus, the UE generates HARQ-ACKs for the eMBB service and CBG-based transmission, and HARQ-ACKs for the URLLC service and CBG-based transmission in CC2.

[0098] Fig. 6A is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 2 and CBG configuration method 1 of aspect 1-2. Differences from Fig. 5A will be mainly described.

[0099] The UE places the HARQ-ACK information bits for CBG-based transmission in the first sub-codebook in the order of CC index and slot index, and places the HARQ-ACK information bits for TB-based transmission in the second sub-codebook in the order of CC index and slot index.

[0100] Fig. 6B is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 2 and CBG configuration method 2 of aspect 1-2. Differences from Fig. 6A will be mainly described.

[0101] The UE is configured with CBG-based transmission for CC2, and the maximum CBG number is set to 4. The UE expects the PDSCH of the eMBB service of CC2 to be CBG-based transmission, and expects the PDSCH of the URLLC service of CC2 to be CBG-based transmission. Thus, the UE generates HARQ-ACKs for the eMBB service and CBG-based transmission, and HARQ-ACKs for the URLLC service and CBG-based transmission in CC2.

[0102] According to this aspect 1-2, even if TB based transmission and CBG based transmission are mixed in PDSCHs of different services, HARQ-ACKs for those PDSCHs can be appropriately transmitted as one HARQ-ACK codebook.

[0103] (Aspect 2) The UE may generate multiple HARQ-ACKs for different services separately, in other words, the UE may generate a HARQ-ACK for each service and concatenate them.

[0104] The UE may take different actions for cases 1 and 2 above.

[0105] <Aspect 2-1> For case 1, the UE may generate two HARQ-ACK sub-codebooks (sub-codebooks).

[0106] The two sub-codebooks may be a sub-codebook for a first service and a sub-codebook for a second service. In other words, the UE may determine a position of the HARQ-ACK information bit in the HARQ-ACK codebook based on a service corresponding to the HARQ-ACK information bit. Also, the UE may arrange the HARQ-ACK information bit for the first service consecutively in the HARQ-ACK codebook, and may arrange the HARQ-ACK information bit for the second service consecutively in the HARQ-ACK codebook.

[0107] The UE may generate one HARQ-ACK codebook by concatenating two sub-codebooks. The UE may concatenate the two sub-codebooks according to one of the following concatenation methods 1 and 2.

[0108] [Connection method 1] The UE preconfigures the sub-codebook for the first service.

[0109] [Connection method 2] The UE pre-configures the sub-codebook for the second service.

[0110] The UE may count the DAI for the first service and the DAI for the second service separately.

[0111] FIG. 7 is a diagram illustrating an example of HARQ-ACK codebook generation according to aspect 2-1.

[0112] The UE is not configured for CBG based transmission on CC1, 2, and 3. Therefore, the UE generates HARQ-ACK for TB based transmission on CC1, 2, and 3.

[0113] The UE receives the PDSCH of the eMBB service on CC1 and CC2, and receives the PDSCH of the URLLC service on CC2 and CC3.

[0114] The UE counts the DAI for the eMBB service and the DAI for the URLLC service separately.

[0115] The UE counts the counter DAI in the order of the CC index, then counts the counter DAI in the order of the slot index, and counts the total DAI in the order of the slot index.

[0116] The UE generates one HARQ-ACK information bit for every 1 TB.

[0117] When using concatenation method 1 (HARQ-ACK codebook 1), the UE places HARQ-ACK information bits for eMBB services in the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for URLLC services in the second sub-codebook in the order of CC index and slot index.

[0118] When using concatenation method 2 (HARQ-ACK codebook 2), the UE places HARQ-ACK information bits for the URLLC service in the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for the eMBB service in the second sub-codebook in the order of CC index and slot index.

[0119] According to this aspect 2-1, the UE can appropriately transmit HARQ-ACKs for PDSCHs of different services as one HARQ-ACK codebook.

[0120] <Aspect 2-2> For case 2, the UE may generate two HARQ-ACK sub-codebooks (sub-codebooks).

[0121] The UE may generate the two sub-codebooks according to one of the following aspects 2-2-1 and 2-2-2.

[0122] "Aspect 2-2-1" The two sub-codebooks may be a sub-codebook for a first service and a sub-codebook for a second service. In other words, the UE may determine a position of the HARQ-ACK information bit in the HARQ-ACK codebook based on a service corresponding to the HARQ-ACK information bit. Also, the UE may arrange the HARQ-ACK information bit for the first service consecutively in the HARQ-ACK codebook, and may arrange the HARQ-ACK information bit for the second service consecutively in the HARQ-ACK codebook.

[0123] The UE may generate two HARQ-ACK sub-sub-codebooks (sub-sub-codebooks) for the sub-codebook for the first service.

[0124] The two sub-sub-codebooks for the first service may be a sub-sub-codebook for TB based transmission and a sub-sub-codebook for CBG based transmission.

[0125] The UE may generate one sub-codebook by concatenating two sub-sub-codebooks. The UE may concatenate the two sub-sub-codebooks according to one of the following sub-sub-codebook concatenation methods 1 and 2:

[0126] [Sub-sub codebook concatenation method 1] The UE prepopulates the sub-sub-codebook for TB based transmission.

[0127] [Sub-sub codebook concatenation method 2] The UE prepopulates the sub-sub-codebook for CBG based transmission.

[0128] The UE may be configured with CBG based transmission for at least one of the first service and the second service according to the following CBG configuration methods 1 and 2.

[0129] [CBG setting method 1] The UE may expect that the PDSCH of the first service is CBG-based transmission in the serving cell configured for CBG-based transmission by higher layer signaling, so that the UE may generate a HARQ-ACK for the CBG-based transmission in the first service.

[0130] The UE may expect that the PDSCH of the second service is TB-based transmission in the serving cell configured for CBG-based transmission by higher layer signaling, so that the UE may generate a HARQ-ACK for the TB-based transmission in the second service.

[0131] The UE may generate one sub-sub-codebook as the sub-codebook for the second service, which may be the sub-sub-codebook for TB based transmission.

[0132] [CBG setting method 2] The UE may expect the PDSCH to be CBG-based transmission regardless of whether it is the first service or the second service in the serving cell configured for CBG-based transmission by higher layer signaling, so that the UE may generate HARQ-ACK for the CBG-based transmission in both the first service and the second service.

[0133] The UE may generate two sub-sub-codebooks for the sub-codebook for the second service.

[0134] The two sub-sub-codebooks may be a sub-sub-codebook for TB based transmission and a sub-sub-codebook for CBG based transmission.

[0135] The UE may generate one sub-codebook by concatenating two sub-sub-codebooks. The UE may concatenate the two sub-sub-codebooks according to one of the following sub-sub-codebook concatenation methods 1 and 2:

[0136] [Sub-sub codebook concatenation method 1] The UE prepopulates the sub-sub-codebook for TB based transmission.

[0137] [Sub-sub codebook concatenation method 2] The UE prepopulates the sub-sub-codebook for CBG based transmission.

[0138] The UE may generate one HARQ-ACK codebook by concatenating two sub-codebooks. The UE may concatenate the two sub-codebooks according to one of the following concatenation methods 1 and 2.

[0139] [Connection method 1] The UE preconfigures the sub-codebook for the first service.

[0140] [Connection method 2] The UE pre-configures the sub-codebook for the second service.

[0141] The UE may encode the sub-codebook for the first service and the sub-codebook for the second service separately.

[0142] The UE may separately count the DAI for the first service and TB based transmission, the DAI for the first service and CBG based transmission, the DAI for the second service and TB based transmission, and the DAI for the second service and CBG based transmission.

[0143] Fig. 8A is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 1, and CBG setting method 1 of aspect 2-2-1. Differences from Fig. 7 will be mainly described.

[0144] The UE is configured with CBG-based transmission for CC2, and the maximum CBG number is set to 4. The UE expects the PDSCH of the eMBB service in CC2 to be CBG-based transmission. Meanwhile, the UE expects the PDSCH of the URLLC service in CC2 to be TB-based transmission. Thus, the UE generates HARQ-ACKs for the eMBB service and CBG-based transmission, and HARQ-ACKs for the URLLC service and TB-based transmission in CC2.

[0145] The UE counts the DAI for TB-based transmission of the eMBB service, the DAI for CBG-based transmission of the eMBB service, and the DAI for TB-based transmission of the URLLC service separately.

[0146] The UE generates one HARQ-ACK information bit per TB for TB-based transmission, and one HARQ-ACK information bit per CBG for CBG-based transmission.

[0147] The UE places HARQ-ACK information bits for eMBB service and TB based transmission in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for eMBB service and CBG based transmission in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for URLLC service and TB based transmission in the second sub-codebook (sub-sub-codebook) in the order of CC index and slot index.

[0148] Fig. 8B is a diagram showing an example of HARQ-ACK codebook generation according to the concatenation method 1, the sub-sub codebook concatenation method 1, and the CBG setting method 2 of aspect 2-2-1. Differences from Fig. 8A will be mainly described.

[0149] The UE is configured with CBG-based transmission for CC2, and the maximum CBG number is set to 4. The UE expects the PDSCH of the eMBB service of CC2 to be CBG-based transmission, and expects the PDSCH of the URLLC service of CC2 to be CBG-based transmission. Thus, the UE generates HARQ-ACKs for the eMBB service and CBG-based transmission, and HARQ-ACKs for the URLLC service and CBG-based transmission in CC2.

[0150] The UE counts the DAI of the TB-based transmission of the eMBB service, the DAI of the CBG-based transmission of the eMBB service, the DAI of the TB-based transmission of the URLLC service, and the DAI of the CBG-based transmission of the URLLC service separately.

[0151] The UE places HARQ-ACK information bits for eMBB service and TB based transmission in the first sub-sub-codebook of the first sub-codebook in order of CC index and slot index, and places HARQ-ACK information bits for eMBB service and CBG based transmission in the second sub-sub-codebook of the first sub-codebook in order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for URLLC service and TB based transmission in the first sub-sub-codebook of the second sub-codebook in order of CC index and slot index, and places HARQ-ACK information bits for URLLC service and CBG based transmission in the second sub-sub-codebook of the second sub-codebook in order of CC index and slot index.

[0152] Fig. 9A is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 2, and CBG setting method 1 of aspect 2-2-1. Differences from Fig. 8A will be mainly described.

[0153] The UE places HARQ-ACK information bits for eMBB service and CBG based transmission in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for eMBB service and TB based transmission in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for URLLC service and TB based transmission in the second sub-codebook (sub-sub-codebook) in the order of CC index and slot index.

[0154] Fig. 9B is a diagram showing an example of HARQ-ACK codebook generation according to the concatenation method 1, the sub-sub codebook concatenation method 2, and the CBG setting method 2 of aspect 2-2-1. Differences from Fig. 8A will be mainly described.

[0155] The UE is configured with CBG-based transmission for CC2, and the maximum CBG number is set to 4. The UE expects the PDSCH of the eMBB service of CC2 to be CBG-based transmission, and expects the PDSCH of the URLLC service of CC2 to be CBG-based transmission. Thus, the UE generates HARQ-ACKs for the eMBB service and CBG-based transmission, and HARQ-ACKs for the URLLC service and CBG-based transmission in CC2.

[0156] The UE places HARQ-ACK information bits for eMBB service and CBG based transmission in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for eMBB service and TB based transmission in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for URLLC service and CBG based transmission in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for URLLC service and TB based transmission in the second sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0157] Fig. 10A is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 1, and CBG setting method 1 of aspect 2-2-1. Differences from Fig. 8A will be mainly described.

[0158] The UE places HARQ-ACK information bits for URLLC service and TB based transmission in the first sub-codebook (sub-sub-codebook) in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for eMBB service and TB based transmission in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for eMBB service and CBG based transmission in the second sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0159] Fig. 10B is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 1, and CBG setting method 2 of aspect 2-2-1. Differences from Fig. 8B will be mainly described.

[0160] The UE places HARQ-ACK information bits for URLLC service and TB based transmission in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for URLLC service and CBG based transmission in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for eMBB service and TB based transmission in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for eMBB service and CBG based transmission in the second sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0161] Fig. 11A is a diagram showing an example of HARQ-ACK codebook generation according to aspect 2-2-1 of concatenation method 2, sub-sub codebook concatenation method 2, and CBG setting method 1. Differences from Fig. 9A will be mainly described.

[0162] The UE places HARQ-ACK information bits for URLLC service and TB based transmission in the first sub-codebook (sub-sub-codebook) in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for eMBB service and CBG based transmission in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for eMBB service and TB based transmission in the second sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0163] Fig. 11B is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 2, and CBG setting method 2 of aspect 2-2-1. Differences from Fig. 9B will be mainly described.

[0164] The UE places HARQ-ACK information bits for URLLC service and CBG based transmission in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for URLLC service and TB based transmission in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for eMBB service and CBG based transmission in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for eMBB service and TB based transmission in the second sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0165] "Aspect 2-2-2" The two sub-codebooks may be a sub-codebook for TB-based transmission and a sub-codebook for CBG-based transmission. In other words, the UE may determine the position of the HARQ-ACK information bit in the HARQ-ACK codebook based on whether the HARQ-ACK information bit corresponds to the CBG-based transmission. Also, the UE may arrange the HARQ-ACK information bits for the TB-based transmission in the HARQ-ACK codebook consecutively, and may arrange the HARQ-ACK information bits for the CBG-based transmission in the HARQ-ACK codebook consecutively.

[0166] The UE may generate two HARQ-ACK sub-sub-codebooks (sub-sub-codebooks) for the sub-codebook for TB based transmission.

[0167] The two sub-sub-codebooks may be a sub-sub-codebook for a first service and a sub-sub-codebook for a second service.

[0168] The UE may generate one sub-codebook by concatenating two sub-sub-codebooks. The UE may concatenate the two sub-sub-codebooks according to one of the following sub-sub-codebook concatenation methods 1 and 2:

[0169] [Sub-sub codebook concatenation method 1] The UE preconfigures the sub-sub codebook for the first service.

[0170] [Sub-sub codebook concatenation method 2] The UE pre-configures the sub-sub codebook for the second service.

[0171] The UE may be configured with CBG based transmission for at least one of the first service and the second service according to one of the following CBG configuration methods 1 and 2.

[0172] [CBG setting method 1] The UE may expect that the PDSCH of the first service is CBG-based transmission in the serving cell configured for CBG-based transmission by higher layer signaling, so that the UE may generate a HARQ-ACK for the CBG-based transmission in the first service.

[0173] The UE may expect that the PDSCH of the second service is TB-based transmission in the serving cell configured for CBG-based transmission by higher layer signaling, so that the UE may generate a HARQ-ACK for the TB-based transmission in the second service.

[0174] The UE may generate one sub-sub-codebook as a sub-codebook for the CBG-based transmission, and the sub-sub-codebook may be a sub-sub-codebook for the first service.

[0175] [CBG setting method 2] The UE may expect the PDSCH to be CBG-based transmission regardless of whether it is the first service or the second service in the serving cell configured for CBG-based transmission by higher layer signaling, so that the UE may generate HARQ-ACK for the CBG-based transmission in both the first service and the second service.

[0176] The UE may generate two sub-sub-codebooks for the sub-codebook for CBG based transmission.

[0177] The two sub-sub-codebooks may be a sub-sub-codebook for a first service and a sub-sub-codebook for a second service.

[0178] The UE may generate one sub-codebook by concatenating two sub-sub-codebooks. The UE may concatenate the two sub-sub-codebooks according to one of the following sub-sub-codebook concatenation methods 1 and 2:

[0179] [Sub-sub codebook concatenation method 1] The UE preconfigures the sub-sub codebook for the first service.

[0180] [Sub-sub codebook concatenation method 2] The UE pre-configures the sub-sub codebook for the second service.

[0181] The UE may generate one HARQ-ACK codebook by concatenating two sub-codebooks. The UE may concatenate the two sub-codebooks according to one of the following concatenation methods 1 and 2.

[0182] [Connection method 1] The UE preconfigures the sub-codebook for TB based transmission.

[0183] [Connection method 2] The UE preconfigures the sub-codebook for CBG based transmission.

[0184] The UE may separately encode the sub-codebook for TB based transmission and the sub-codebook for CBG based transmission.

[0185] The UE may separately count the DAI for the first service and TB based transmission, the DAI for the first service and CBG based transmission, the DAI for the second service and TB based transmission, and the DAI for the second service and CBG based transmission.

[0186] Fig. 12A is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 1, and CBG setting method 1 of aspect 2-2-2. Differences from Fig. 8A will be mainly described.

[0187] The UE places HARQ-ACK information bits for TB based transmission and eMBB service in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for TB based transmission and URLLC service in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for CBG based transmission and eMBB service in the second sub-codebook (sub-sub-codebook) in the order of CC index and slot index.

[0188] Fig. 12B is a diagram showing an example of HARQ-ACK codebook generation according to the concatenation method 1, the sub-sub codebook concatenation method 1, and the CBG setting method 2 of aspect 2-2-2. Differences from Fig. 8B will be mainly described.

[0189] The UE places HARQ-ACK information bits for TB based transmission and eMBB service in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for TB based transmission and URLLC service in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for CBG based transmission and eMBB service in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for CBG based transmission and URLLC service in the second sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0190] Fig. 13A is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 2, and CBG setting method 1 of aspect 2-2-2. Differences from Fig. 9A will be mainly described.

[0191] The UE places HARQ-ACK information bits for TB based transmission and URLLC service in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for TB based transmission and eMBB service in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for CBG based transmission and eMBB service in the second sub-codebook (sub-sub-codebook) in the order of CC index and slot index.

[0192] Fig. 13B is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 1, sub-sub codebook concatenation method 2, and CBG setting method 2 of aspect 2-2-2. Differences from Fig. 9B will be mainly described.

[0193] The UE places HARQ-ACK information bits for TB based transmission and URLLC service in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for TB based transmission and eMBB service in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for CBG based transmission and URLLC service in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for CBG based transmission and eMBB service in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0194] Fig. 14A is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 1, and CBG setting method 1 of aspect 2-2-2. Differences from Fig. 10A will be mainly described.

[0195] The UE places HARQ-ACK information bits for CBG based transmission and eMBB service in the first sub-codebook (sub-sub-codebook) in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for TB based transmission and eMBB service in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for TB based transmission and URLLC service in the second sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0196] Fig. 14B is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 1, and CBG setting method 2 of aspect 2-2-2. Differences from Fig. 10B will be mainly described.

[0197] The UE places HARQ-ACK information bits for CBG based transmission and eMBB service in the first sub-sub-codebook of the first sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for CBG based transmission and URLLC service in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for TB based transmission and eMBB service in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for TB based transmission and URLLC service in the second sub-sub-codebook of the second sub-codebook in the order of CC index and slot index.

[0198] Fig. 15A is a diagram showing an example of HARQ-ACK codebook generation according to the concatenation method 2 and the sub-sub codebook concatenation method 2 of aspect 2-2-2 and the CBG setting method 1. Differences from Fig. 11A will be mainly described.

[0199] The UE places HARQ-ACK information bits for CBG based transmission and eMBB service in the first sub-codebook (sub-sub-codebook) in the order of CC index and slot index. Furthermore, the UE places HARQ-ACK information bits for TB based transmission and URLLC service in the first sub-sub-codebook of the second sub-codebook in the order of CC index and slot index, and places HARQ-ACK information bits for TB based transmission and eMBB service in the second sub-sub-codebook of the first sub-codebook in the order of CC index and slot index.

[0200] Fig. 15B is a diagram showing an example of HARQ-ACK codebook generation according to concatenation method 2, sub-sub codebook concatenation method 2, and CBG setting method 2 of aspect 2-2-2. Differences from Fig. 11B will be mainly described.

[0201] The UE places HARQ-ACK information bits for the CBG-based transmission and URLLC service in the first sub-sub-codebook of the first sub-codebook in the order of the CC index and the slot index, and places HARQ-ACK information bits for the CBG-based transmission and eMBB service in the second sub-sub-codebook of the first sub-codebook in the order of the CC index and the slot index. Furthermore, the UE places HARQ-ACK information bits for the TB-based transmission and URLLC service in the first sub-sub-codebook of the second sub-codebook in the order of the CC index and the slot index, and places HARQ-ACK information bits for the TB-based transmission and eMBB service in the second sub-sub-codebook of the second sub-codebook in the order of the CC index and the slot index.

[0202] According to this aspect 2-2, even when different services are mixed and TB based transmission and CBG based transmission are mixed, HARQ-ACKs for those PDSCHs can be appropriately transmitted as one HARQ-ACK codebook.

[0203] (Aspect 3) If a predetermined condition is met, the UE may apply the HARQ-ACK codebook generation rule as shown in example 1 or example 2.

[0204] The UE may follow at least one of the following actions AC.

[0205] (Action A) If the DCI for the first service and the DCI for the second service indicate the same slot for HARQ-ACK feedback, the UE applies the HARQ-ACK codebook generation rule.

[0206] (Operation B) When the PUCCH resources for HARQ-ACK feedback are determined separately between the first service and the second service, if the PUCCH resource containing the HARQ-ACK for the first service overlaps with the PUCCH resource containing the HARQ-ACK for the second service, or if the PUCCH resource containing the HARQ-ACK for the first service overlaps with the same PUSCH, the UE applies the HARQ-ACK codebook generation rule.

[0207] (Operation C) The UE is instructed by a higher layer parameter or a DCI field which of the multiple HARQ-ACK codebook generation rules as shown in the first and second aspects should be applied.

[0208] According to this aspect 3, the UE can generate an appropriate HARQ-ACK codebook depending on the situation.

[0209] (Aspect 4) The UE may duplicate HARQ-ACK information bits for a specific service in the HARQ-ACK codebook of the first embodiment and insert the duplicated HARQ-ACK information bits into the HARQ-ACK codebook. The specific service may be a URLLC service. This makes it possible to make the reliability of the URLLC service higher than the reliability of other services.

[0210] The UE may code the HARQ-ACK information bits and / or control the amount of coded bits transmitted on the uplink channel to have different coding rates between the first service and the second service in the HARQ-ACK codebook of aspect 2. The coding rate of the HARQ-ACK for the URLLC service may be lower than the coding rate of the HARQ-ACK for the eMBB service. This allows the reliability of the URLLC service to be higher than the reliability of the eMBB service.

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

[0212] 16 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using LTE (Long Term Evolution), 5G NR (5th generation mobile communication system New Radio), or the like, which are specified by 3GPP (Third Generation Partnership Project).

[0213] Furthermore, the wireless communication system 1 may support dual connectivity between a plurality of RATs (Radio Access Technologies) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (E-UTRA: Evolved Universal Terrestrial Radio Access) and NR (EN-DC: E-UTRA-NR Dual Connectivity), dual connectivity between NR and LTE (NE-DC: NR-E-UTRA Dual Connectivity), and the like.

[0214] In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (MN) and the NR base station (gNB) is the secondary node (SN). In NE-DC, the NR base station (gNB) is the MN and the LTE (E-UTRA) base station (eNB) is the SN.

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

[0216] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are arranged in the macrocell C1 and form a small cell C2 that is narrower than the macrocell C1. A user terminal 20 may be located in at least one of the cells. The arrangement and number of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as a base station 10.

[0217] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation using multiple component carriers (CC) and dual connectivity (DC).

[0218] Each CC may be included in at least one of a first frequency band (FR1: Frequency Range 1) and a second frequency band (FR2: Frequency Range 2). 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 above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a frequency band higher than FR2.

[0219] Furthermore, the user terminal 20 may perform communication in each CC using at least one of time division duplex (TDD) and frequency division duplex (FDD).

[0220] The multiple base stations 10 may be connected by wire (e.g., optical fiber conforming to CPRI (Common Public Radio Interface), X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an IAB (Integrated Access Backhaul) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

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

[0222] The user terminal 20 may be a terminal compatible with at least one of communication methods such as LTE, LTE-A, and 5G.

[0223] A radio access scheme based on Orthogonal Frequency Division Multiplexing (OFDM) may be used in the radio communication system 1. For example, in at least one of the downlink (DL) and the uplink (UL), a cyclic prefix OFDM (CP-OFDM), a discrete Fourier transform spread OFDM (DFT-s-OFDM), an orthogonal frequency division multiple access (OFDMA), a single carrier frequency division multiple access (SC-FDMA), or the like may be used.

[0224] The radio access scheme may be called a waveform. In the wireless communication system 1, other radio access schemes (for example, other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

[0226] Furthermore, in the wireless communication system 1, an uplink shared channel (PUSCH: Physical Uplink Shared Channel) shared by each user terminal 20, an uplink control channel (PUCCH: Physical Uplink Control Channel), a random access channel (PRACH: Physical Random Access Channel), or the like may be used as an uplink channel.

[0227] The PDSCH transmits user data, higher layer control information, SIB (System Information Block), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit MIB (Master Information Block).

[0228] 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 of at least one of the PDSCH and the PUSCH.

[0229] In addition, DCI for scheduling PDSCH may be called DL assignment, DL DCI, etc., and DCI for scheduling PUSCH may be called UL grant, UL DCI, etc. In addition, PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

[0230] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources to search for DCI. The search space corresponds to a search region and a search method for PDCCH candidates. One CORESET may be associated with one or multiple search spaces. The UE may monitor a CORESET associated with a certain search space based on the search space configuration.

[0231] One SS 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 terms "search space," "search space set," "search space setting," "search space set setting," "CORESET," "CORESET setting," and the like in the present disclosure may be read as interchangeable terms.

[0232] The PUCCH may transmit channel state information (CSI), delivery acknowledgement information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), a scheduling request (SR), etc. The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0233] In the present disclosure, a downlink, an uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning of the channels.

[0234] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0235] The synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block including an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be called an SS / PBCH block, an SSB (SS Block), or the like. In addition, the SS, SSB, and the like may also be called a reference signal.

[0236] In addition, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), etc. may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may be called a user equipment specific reference signal (UE-specific reference signal).

[0237] (base station) 17 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 each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140 may be provided.

[0238] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the base station 10 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0239] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured with a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0240] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transmission and reception unit 120, the transmission and reception antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transmission and reception unit 120. The control unit 110 may perform call processing (setting, release, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0241] The transceiver unit 120 may include a baseband unit 121, an RF (Radio Frequency) 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 may be configured with 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 common understanding in the technical field related to the present disclosure.

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

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

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

[0245] The transceiver 120 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

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

[0247] The transceiver 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 string to be transmitted, and output a baseband signal.

[0248] The transceiver unit 120 (RF unit 122) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna .

[0249] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency signal received by the transceiver antenna .

[0250] The transceiver 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 to the acquired baseband signal, thereby acquiring user data, etc.

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

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

[0253] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0254] The transmitting / receiving unit 120 may transmit the setting of whether or not to perform CBG-based transmission by higher layer signaling. The transmitting / receiving unit 120 may transmit the downlink signal by using parameters (such as an MCS table and an RNTI) corresponding to communication requirements.

[0255] (User terminal) 18 is a diagram showing an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control unit 210, a transmitting / receiving unit 220, and a transmitting / receiving antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transmitting / receiving unit 220, and the transmitting / receiving antenna 230.

[0256] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and the user terminal 20 may be assumed to have other functional blocks necessary for wireless communication. Some of the processes of each unit described below may be omitted.

[0257] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured with a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0258] 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.

[0259] The transmitting / receiving 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 transmitting / receiving unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitting / receiving circuit, and the like, which are described based on common understanding in the technical field related to the present disclosure.

[0260] The transmitting / receiving unit 220 may be configured as an integrated transmitting / 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 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0261] The transmitting / receiving antenna 230 can be composed of an antenna described based on common understanding in the technical field to which this disclosure pertains, such as an array antenna.

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

[0263] The transceiver 220 may form at least one of a transmission beam and a reception beam using digital beamforming (eg, precoding), analog beamforming (eg, phase rotation), or the like.

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

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

[0266] Whether or not to apply the DFT process may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver 220 (transmission processor 2211) may perform the DFT process as the transmission process to transmit the channel using a DFT-s-OFDM waveform, and may not perform the DFT process as the transmission process if transform precoding is enabled for the channel.

[0267] The transceiver unit 220 (RF unit 222) may perform modulation to a radio frequency band, filtering, amplification, and the like on the baseband signal, and transmit the radio frequency band signal via the transceiver antenna 230.

[0268] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency signal received by the transceiver antenna 230.

[0269] The transceiver 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 to the acquired baseband signal, and acquire user data, etc.

[0270] The transceiver 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.

[0271] In addition, the transmitting section and the receiving section of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving section 220, the transmitting / receiving antenna 230, and the transmission path interface 240.

[0272] Also, the control unit 210 may generate a HARQ-ACK codebook (at least one HARQ-ACK codebook) based on a plurality of downlink data (e.g., PDSCH) having different communication requirements (e.g., eMBB service, URLLC service). The transceiver unit 220 may transmit the HARQ-ACK codebook in one uplink channel resource (e.g., PUCCH, PUSCH).

[0273] Furthermore, the control unit 210 may determine the position of the HARQ-ACK information bit in the HARQ-ACK codebook based on a communication requirement (service, MCS table, RNTI, etc.) corresponding to the HARQ-ACK information bit (embodiments 1 and 2).

[0274] In addition, the control unit 210 may determine the position of the HARQ-ACK information bit in the HARQ-ACK codebook based on whether the HARQ-ACK information bit corresponds to a codebook group-based transmission (e.g., a CBG indicated by a CBGTI) (Case 2 in aspects 1 and 2).

[0275] Furthermore, the control unit 210 may consecutively allocate HARQ-ACK information bits corresponding to the same communication requirement in the HARQ-ACK codebook (mode 2-2-1).

[0276] In addition, the control unit 210 may consecutively place HARQ-ACK information bits that correspond to the same codebook group-based transmission (for example, the CBG indicated by the CBGTI) in the HARQ-ACK codebook (mode 2-2-2).

[0277] (Hardware configuration) The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

[0278] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission may be called a transmitting unit, a transmitter, and the like. In either case, as described above, the method of realization is not particularly limited.

[0279] For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 19 is a diagram showing an example of a hardware configuration of a base station and a user terminal according to an embodiment. The above-mentioned base station 10 and user terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0280] In this disclosure, the terms "apparatus," "circuit," "device," "section," "unit," and the like can be read interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0281] For example, although only one processor 1001 is shown, there may be multiple processors. Also, the processes may be performed by one processor, or the processes may be performed by two or more processors simultaneously, sequentially, or in other manners. Also, the processor 1001 may be implemented by one or more chips.

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

[0283] The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured with a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transmission / reception unit 120 (220), etc. may be realized by the processor 1001.

[0284] Moreover, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to the programs. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated by the processor 1001, and the other functional blocks may be realized in a similar manner.

[0285] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically EPROM (EEPROM), a Random Access Memory (RAM), and other suitable storage media. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), and the like. The memory 1002 can store a program (program code), a software module, and the like that is executable to implement a wireless communication method according to an embodiment of the present disclosure.

[0286] Storage 1003 is a computer-readable recording medium, and may be constituted by at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disk (CD-ROM (Compact Disc 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 (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, and other suitable storage media. Storage 1003 may also be referred to as an auxiliary storage device.

[0287] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0288] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED (Light Emitting Diode) lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one (e.g., a touch panel).

[0289] In addition, 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 between each device.

[0290] Furthermore, 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), a field programmable gate array (FPGA), etc., 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 pieces of hardware.

[0291] (Modification) In addition, the terms explained in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be read as mutually interchangeable. A signal may also be a message. A reference signal may also be abbreviated as RS (Reference Signal), and may also be called a pilot, pilot signal, etc. depending on the applied standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

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

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

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

[0295] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0296] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. A different name may be used for the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be read as interchangeable with each other.

[0297] For example, one subframe may be called a TTI, multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, 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, minislot, etc., instead of a subframe.

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

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

[0300] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

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

[0302] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

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

[0304] In addition, an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0305] Note that one or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0306] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0307] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

[0309] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0310] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. 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 minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

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

[0312] The names used for parameters and the like in this disclosure are not limiting in any way. Furthermore, the formulas and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH (Physical Uplink Control Channel), PDCCH (Physical Downlink Control Channel), etc.) and information elements may be identified by any suitable names, and the various names assigned to these various channels and information elements are not limiting in any way.

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

[0314] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0315] Input and output information, signals, etc. may be stored in a specific location (e.g., memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added to. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

[0316] Notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, notification of information in the present disclosure may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher 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 combinations thereof.

[0317] The physical layer signaling may be called L1 / L2 (Layer 1 / Layer 2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. The RRC signaling may be called an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc. The MAC signaling may be notified by using a MAC Control Element (MAC CE (Control Element)), for example.

[0318] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0319] The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value represented as true or false, or by comparing numerical values ​​(e.g., with a predetermined value).

[0320] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0321] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired and / or wireless technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0322] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0323] 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," "transmit 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," and the like may be used interchangeably.

[0324] In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0325] 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 partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services in this coverage.

[0326] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

[0327] A 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 terminology.

[0328] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. 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.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include 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 IoT (Internet of Things) device such as a sensor.

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

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

[0331] In the present disclosure, an operation performed by a base station may be performed by its upper node in some cases. In a network including one or more network nodes having a base station, it is clear that 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 (such as, but not limited to, an MME (Mobility Management Entity) and an S-GW (Serving-Gateway)), or a combination thereof.

[0332] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to implementation. In addition, the processing procedures, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0333] Each aspect / embodiment described in the present disclosure may be applied to a system using LTE (Long Term Evolution), LTE-A (LTE-Advanced), LTE-B (LTE-Beyond), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), New-RAT (Radio Access Technology), NR (New Radio), NX (New radio access), FX (Future generation radio access), GSM (registered trademark) (Global System for Mobile communications), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable wireless communication method, or a next-generation system extended based on these. In addition, multiple systems may be applied in combination (for example, a combination of LTE or LTE-A and 5G).

[0334] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0335] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

[0336] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, and the like.

[0337] A "determining" may also be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), etc.

[0338] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. That is, "determination" may be considered to be "deciding" to perform some action.

[0339] Additionally, "judgment (decision)" may be interpreted as "assuming," "expecting," "considering," etc.

[0340] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.

[0341] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may 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 the elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0342] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, and the like, as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, and the like, as some non-limiting and non-exhaustive examples.

[0343] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0344] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0345] In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0346] Although the invention according to the present disclosure has been described in detail above, it is clear to those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modified and altered forms without departing from the spirit and scope of the invention defined based on the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the invention according to the present disclosure.

Claims

1. A control unit that generates a first HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement) codebook associated with a first priority and a second HARQ-ACK codebook associated with a second priority different from the first priority; a transmitter configured to transmit a first HARQ-ACK information bit based on the first HARQ-ACK codebook and a second HARQ-ACK information bit based on the second HARQ-ACK codebook in one PUCCH (Physical Uplink Control Channel); When the PUCCH including the first HARQ-ACK information bit and the PUCCH including the second HARQ-ACK information bit overlap, the control unit connects the first HARQ-ACK information bit and the second HARQ-ACK information bit in the one PUCCH so that one of the first HARQ-ACK information bit and the second HARQ-ACK information bit is located forward in the time direction from the other HARQ-ACK information bit, A terminal, wherein a coding rate used for the concatenated first HARQ-ACK information bits and a coding rate used for the concatenated second HARQ-ACK information bits can be set to different values.

2. generating a first Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) codebook associated with a first priority and a second Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK) codebook associated with a second priority different from the first priority; Transmitting a first HARQ-ACK information bit based on the first HARQ-ACK codebook and a second HARQ-ACK information bit based on the second HARQ-ACK codebook in one PUCCH (Physical Uplink Control Channel); A wireless communication method in a terminal, comprising: when a PUCCH including the first HARQ-ACK information bit and a PUCCH including the second HARQ-ACK information bit overlap, connecting the first HARQ-ACK information bit and the second HARQ-ACK information bit in the one PUCCH such that one of the first HARQ-ACK information bit and the second HARQ-ACK information bit is located earlier in a time direction than the other, A wireless communication method, wherein a coding rate used for the concatenated first HARQ-ACK information bits and a coding rate used for the concatenated second HARQ-ACK information bits can be set to different values.

3. A system including a terminal and a base station, The terminal includes: A control unit that generates a first HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgement) codebook associated with a first priority and a second HARQ-ACK codebook associated with a second priority different from the first priority; a transmitter configured to transmit a first HARQ-ACK information bit based on the first HARQ-ACK codebook and a second HARQ-ACK information bit based on the second HARQ-ACK codebook in one PUCCH (Physical Uplink Control Channel); When the PUCCH including the first HARQ-ACK information bit and the PUCCH including the second HARQ-ACK information bit overlap, the control unit connects the first HARQ-ACK information bit and the second HARQ-ACK information bit in the one PUCCH so that one of the first HARQ-ACK information bit and the second HARQ-ACK information bit is located forward in the time direction from the other HARQ-ACK information bit, The coding rate used for the concatenated first HARQ-ACK information bits and the coding rate used for the concatenated second HARQ-ACK information bits may be set to different values, The base station, A system comprising a receiving unit for receiving the one PUCCH.