Terminal, wireless communication method, base station and system

Abstract

A terminal according to one embodiment of the present invention includes: a reception unit for receiving a first setting for a primary physical uplink control channel (PUCCH) group, a second setting for a secondary PUCCH group, and a first list indicating at least one hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook type for a physical downlink shared channel (PDSCH); and a control unit that determines at least one first HARQ-ACK codebook type for the primary PUCCH group on the basis of the first list and determines at least one second HARQ-ACK codebook type for the secondary PUCCH group on the basis of at least one of the first list, an upper layer parameter, and specifications. This embodiment of the present invention makes it possible to suitably determine a HARQ-ACK codebook.

Description

Terminal, wireless communication method and base station

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

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

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

[0004] 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

[0005] In future wireless communication systems (e.g., NR), multiple physical uplink control channel (PUCCH) groups can be configured.

[0006] However, there are cases where it is unclear how the Hybrid Automatic Repeat reQuest-ACKnowledgement (HARQ-ACK) codebook for each PUCCH group is determined. If the HARQ-ACK codebook is unclear, it may result in a decrease in throughput.

[0007] Therefore, one of the objects of the present disclosure is to provide a terminal, a wireless communication method, and a base station that appropriately determine a HARQ-ACK codebook.

[0008] A terminal according to one aspect of the present disclosure includes: a receiving unit that receives a first configuration of a primary physical uplink control channel (PUCCH) group, a second configuration of a secondary PUCCH group, and a first list indicating one or more hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook types for a physical downlink shared channel (PDSCH); and a control unit that determines one or more first HARQ-ACK codebook types for the primary PUCCH group based on the first list, and determines one or more second HARQ-ACK codebook types for the secondary PUCCH group based on at least one of the first list, higher layer parameters, and specifications.

[0009] According to one aspect of the present disclosure, the HARQ-ACK codebook can be appropriately determined.

[0010] FIG. 1 is a diagram showing an example of a HARQ-ACK codebook corresponding to a priority index. FIG. 2 is a diagram showing an example of aspect 1-1. FIG. 3 is a diagram showing an example of aspect 1-2. FIG. 4 is a diagram showing an example of aspect 1-3-2. FIG. 5 is a diagram showing an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 6 is a diagram showing an example of a configuration of a base station according to an embodiment. FIG. 7 is a diagram showing an example of a configuration of a user terminal according to an embodiment. FIG. 8 is a diagram showing an example of the hardware configuration of a base station and a user terminal according to an embodiment.

[0011] <HARQ-ACK Codebook> In NR, a mechanism is being considered in which a user terminal (UE: User Equipment) feeds back (also referred to as a report or transmission, etc.) delivery confirmation information (also referred to as Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK), ACKnowledge / Non-ACK (ACK / NACK), HARQ-ACK information, A / N, etc.) for a downlink shared channel (also referred to as a Physical Downlink Shared Channel (PDSCH), etc.).

[0012] For example, in NR, the value of a field in the downlink control information (DCI) (for example, DCI format 1_0, 1_1, or 1_2) used for scheduling the PDSCH indicates the feedback timing of the HARQ-ACK for the PDSCH. When the UE transmits a HARQ-ACK for the PDSCH received in slot #n in slot #n+k, the value of this field may be mapped to the value of k. This field is called, for example, a PDSCH-to-HARQ feedback timing indicator (PDSCH-to-HARQ_feedback timing indicator) field.

[0013] Also, in NR, based on the value of a field in the DCI (for example, DCI format 1_0, 1_1, or 1_2) used for scheduling the PDSCH, the resource (for example, a resource for an uplink control channel (for example, a Physical Uplink Control Channel (PUCCH)) (PUCCH resource)) used for feedback of the HARQ-ACK for the PDSCH is determined. This field may be called, for example, a PUCCH resource indicator (PRI) field, an ACK / NACK resource indicator (ARI) field, or the like. The value of this field may be called PRI, ARI, or the like.

[0014] The PUCCH resources mapped to each value of the field may be configured in advance in the UE by a higher layer parameter (e.g., ResourceList in PUCCH-ResourceSet). Alternatively, the PUCCH resources may be configured in the UE for each set (PUCCH resource set) including one or more PUCCH resources.

[0015] In addition, in NR, one or more HARQ-ACKs may be mapped to a HARQ-ACK codebook, and the HARQ-ACK codebook may be transmitted on a PUCCH resource indicated by a specific DCI (e.g., the last DCI).

[0016] Here, the HARQ-ACK codebook includes bits for HARQ-ACK within a certain range. These bits are also called HARQ-ACK bits, HARQ-ACK information, or HARQ-ACK information bits. The HARQ-ACK codebook is also called a PDSCH-HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook), a codebook, a HARQ codebook, a HARQ-ACK size, etc.

[0017] The range may be determined using at least one unit of the time domain (e.g., a slot or a downlink control channel (e.g., a Physical Downlink Control Channel (PDCCH)) monitoring occasion), the frequency domain (e.g., a Component Carrier (CC)), the spatial domain (e.g., a layer), a transport block (TB), and a group of code blocks constituting a TB (a Code Block Group (CBG)).

[0018] This range is also called the HARQ-ACK window, window, HARQ-ACK bundling window, HARQ-ACK feedback window, bundling window, feedback window, etc.

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

[0020] In the present disclosure, "determining a semi-static HARQ-ACK codebook" may mean determining at least one of the number of bits (size), order, and bit values ​​in the semi-static HARQ-ACK codebook. Also, "determining a dynamic HARQ-ACK codebook" may mean determining at least one of the number of bits (size), order, and bit values ​​in the dynamic HARQ-ACK codebook.

[0021] In the case of a semi-static HARQ-ACK codebook, the UE may determine the semi-static HARQ-ACK codebook regardless of whether a PDSCH is scheduled within the HARQ-ACK window. For example, the semi-static HARQ-ACK codebook may be determined based on at least one of the following parameters: a: A value indicating the timing of HARQ-ACK (HARQ-ACK timing value, PDSCH-HARQ feedback timing indication) K １ b: A table used to determine time domain resources allocated to the PDSCH (PDSCH time domain resource allocation table); c: When different subcarrier spacings are set for downlink and uplink, the subcarrier spacing configuration μ of the downlink (or downlink BWP); ＤＬ and the uplink (or uplink BWP) subcarrier spacing configuration μ ＵＬ The ratio of (μ ＤＬ -μ ＵＬ) power d: cell-specific TDD UL / DL configuration (e.g., TDD-UL-DL-ConfigurationCommon) and slot-specific configuration that overrides the cell-specific TDD UL / DL configuration (e.g., TDD-UL-DL-ConfigDedicated)

[0022] On the other hand, in the case of a dynamic HARQ-ACK codebook, the UE may determine the dynamic HARQ-ACK codebook based on the presence or absence of a PDSCH in the HARQ-ACK window. For example, the dynamic HARQ-ACK codebook may be determined based on the value of a field in the DCI (e.g., a Downlink Assignment Index (DAI) field).

[0023] The value of the DAI field in the DCI may indicate a counter DAI, or may indicate a counter DAI and a total DAI. The counter DAI may indicate a count value of PDSCHs allocated before the target time. The total DAI may indicate the total number of PDSCHs transmitted before the target time within the HARQ-ACK window.

[0024] For example, the value of a bit (e.g., a certain number of least significant bits (LSBs)) of a DAI field in a DCI may indicate a counter DAI, and the value of the remaining bits (e.g., a certain number of most significant bits (MSBs)) of the DAI field may indicate a total DAI.

[0025] The UE may receive information (type information, for example, "pdsch-HARQ-ACK-Codebook" of a Radio Resource Control (RRC) parameter) indicating whether to use the above-described semi-static HARQ-ACK codebook or the dynamic HARQ-ACK codebook. The RRC parameter may also be referred to as an RRC information element (IE).

[0026] Specifically, the UE may receive the type information for each group including one or more cells, and one cell in the group may transmit the PUCCH. The group may be called a cell group, a master cell group (MCG), a secondary cell group (SCG), a PUCCH group, a PUCCH cell group, etc.

[0027] Furthermore, the term "cell" may be interchangeably referred to as a serving cell, a carrier, a component carrier (CC), etc. The cell from which the PUCCH is transmitted may be referred to as a special cell (SpCell), a primary cell (PCell), a primary secondary cell (PSCell), a PUCCH cell, etc.

[0028] The UE may include HARQ-ACKs for PDSCHs received within a specific period on one or more CCs within the cell group in a HARQ-ACK codebook of a type configured for the cell group (e.g., a semi-static HARQ-ACK codebook (type 1) or a dynamic HARQ-ACK codebook (type 2)).

[0029] <Priority> In NR Rel. 16 and later, it is being considered to set multiple levels (e.g., two levels) of priority for specific signals or channels. For example, it is expected that different priorities will be set for signals or channels corresponding to different traffic types (also referred to as services, service types, communication types, use cases, etc.) to control communications (e.g., transmission control during collisions). This makes it possible to control communications by setting different priorities for the same signal or channel depending on the service type, etc.

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

[0031] For example, a priority may be set for UCI (e.g., at least one of a scheduling request, CSI, and HARQ-ACK). A priority may be set for a HARQ-ACK codebook corresponding to these HARQ-ACKs. Alternatively, a priority may be set for a PUSCH used to transmit a predetermined MAC CE. Note that when a priority is set for a PUSCH, the priority of information or a signal (e.g., MAC CE, CSI, etc.) transmitted by the PUSCH may be interpreted as the priority of the PUSCH.

[0032] In addition, priorities may be set for dynamic grant-based PUSCH, configuration grant-based PUSCH, etc.

[0033] When different UL signals / channels collide, the UE may control UL transmissions based on priority, for example, by performing high-priority UL transmissions and not performing (e.g., dropping) low-priority UL transmissions, or by changing (e.g., postponing or shifting) the transmission timing of low-priority UL transmissions.

[0034] Different UL signals / UL channels collide when the time resources (or time resources and frequency resources) of different UL signals / UL channels overlap, or when the transmission timings of different UL signals / UL channels overlap.

[0035] The priority indicator field in the DCI that schedules the data (PDSCH / PUSCH) may indicate the priority (priority index) of that data.

[0036] The priority may be associated with a traffic type corresponding to communication requirements (requirements such as delay, error rate, etc., required conditions), data type (voice, data, etc.), etc. Expected traffic types (also referred to as type, service, service type, communication type, use case, etc.) include further advancements in mobile broadband (e.g., enhanced Mobile Broadband (eMBB)), machine-type communications that realize multiple simultaneous connections (e.g., massive Machine Type Communications (mMTC), Internet of Things (IoT)), and highly reliable and low-latency communications (e.g., Ultra-Reliable and Low-Latency Communications (URLLC)).

[0037] The priority of the URLLC may be higher than the priority of the eMBB: the priority may be set to "high" (high priority, 1) for the URLLC and "low" (low priority, 0) for the eMBB.

[0038] Enhanced Ultra Reliable and Low Latency Communications (eURLLC) is being studied as a way to improve the reliability of traffic, mainly for unicast data. Hereinafter, when there is no need to distinguish between URLLC and eURLLC, they will simply be referred to as URLLC.

[0039] In NR Rel. 16 eURLLC, a UE can report low-priority or high-priority HARQ-ACK information to a base station. A UE can multiplex multiple HARQ-ACKs as a HARQ-ACK codebook (CB). Type 1 (semi-static) and Type 2 (dynamic) codebook types are supported.

[0040] In the example of Figure 1, PDSCHs #1 and #2 are scheduled by DCIs #1 and #2 indicating a priority index (priority indicator) of 0, respectively, and PDSCH #3 is scheduled by DCI #3 indicating a priority index of 1. Priority index 0 may correspond to eMBB, and priority index 0 may correspond to URLLC. In one slot, the UE may transmit PUCCH #1 containing a HARQ-ACK codebook for PDSCHs #1 and #2 for eMBB, and PUCCH #2 containing a HARQ-ACK codebook for PDSCH #3 for URLLC.

[0041] Regarding the codebook type for HARQ feedback for DL ​​reception, in NR Rel. 16, up to two codebook types for URLLC may be configured for a UE by the PDSCH-HARQ-ACK codebook type list (PDSCH-HARQ-ACK-CodebookList-r16). Of the two configured codebooks, the first codebook is for low priority (priority index 0) and the second codebook is for high priority (priority index 1).

[0042] If the UE is provided with a PDSCH-HARQ-ACK codebook type list, the UE is instructed by the PDSCH-HARQ-ACK codebook type list to generate one or two HARQ-ACK codebooks. If the UE is instructed to generate one HARQ-ACK codebook, the HARQ-ACK codebook is associated with the PUCCH with priority index 0. If the UE is provided with a PDSCH-HARQ-ACK codebook type list, the UE multiplexes only HARQ-ACK information associated with the same priority index into one and the same HARQ-ACK codebook. If the UE is instructed to generate two HARQ-ACK codebooks, the HARQ-ACK codebooks follow procedures 1 and 2 below. [Step 1] The first HARQ-ACK codebook is associated with the PUCCH with priority index 0, and the second HARQ-ACK codebook is associated with the PUCCH with priority index 1. [Step 2] The UE is provided with first and second parameters for the PUCCH configuration parameters, UCI on PUSCH parameters, and PDSCH code block group transmission parameters (PUCCH-Config, UCI-OnPUSCH, PDSCH-codeBlockGroupTransmission) by the PUCCH configuration parameter list, UCI-OnPUSCH parameter list, and PDSCH code block group transmission parameter list (PUCCHConfigurationList, UCI-OnPUSCH-List, PDSCH-CodeBlockGroupTransmission-List), respectively, for use with the first and second HARQ-ACK codebook.

[0043] If the PDSCH-HARQ-ACK codebook type list is configured, the UE ignores the PDSCH-HARQ-ACK codebook type (pdsch-HARQ-ACK-Codebook) which configures only one codebook.

[0044] Two PUCCH groups may be configured for a cell group: the primary PUCCH group may be the PCell (PSCell) and SCell associated with the PUCCH on the PCell (PSCell) in a cell group, and the secondary PUCCH group may be the SCell associated with the PUCCH on the PUCCH-SCell in that cell group.

[0045] In NR Rel.16, when two PUCCH groups are configured for a cell group, up to two codebook types can be configured using the PDSCH-HARQ-ACK codebook type and the PDSCH-HARQ-ACK codebook type for the secondary PUCCH group (pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup). That is, the codebook type for the primary PUCCH group is configured using the PDSCH-HARQ-ACK codebook type, and the codebook type for the secondary PUCCH group is configured using the PDSCH-HARQ-ACK codebook type for the secondary PUCCH group.

[0046] The primary PUCCH group may be the PCell (PSCell) and SCells associated with the PUCCH on the PCell (PSCell) in a cell group, and the secondary PUCCH group may be the SCells associated with the PUCCH on the PUCCH-SCell in that cell group.

[0047] However, when two PUCCH groups are configured for a certain cell group and two priority indices are used in one of the PUCCH groups, it is not clear which codebook type the UE uses to report HARQ-ACK. If the codebook type is not clear, a misunderstanding may occur between the UE and the base station, which may result in degradation of throughput, etc.

[0048] Therefore, the present inventors have devised a method for determining the HARQ-ACK codebook type.

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

[0050] In the present disclosure, "A / B / C" and "at least one of A, B, and C" may be read as interchangeable. In the present disclosure, cell, CC, carrier, BWP, DL BWP, UL BWP, active DL BWP, active UL BWP, and band may be read as interchangeable. In the present disclosure, index, ID, indicator, and resource ID may be read as interchangeable. In the present disclosure, support, control, controllable, operate, and operable may be read as interchangeable.

[0051] In the present disclosure, the terms configure, activate, update, indicate, enable, specify, and select may be read interchangeably.

[0052] In the present disclosure, the higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof. In the present disclosure, RRC, RRC signaling, RRC parameters, higher layer, higher layer parameters, RRC information elements (IEs), and RRC messages may be read interchangeably.

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

[0054] In the present disclosure, HARQ-ACK information and ACK / NACK may be read interchangeably.

[0055] In the present disclosure, the terms HARQ-ACK codebook type 1 and semi-static codebook may be interchangeable. In the present disclosure, the terms HARQ-ACK codebook type 2 and dynamic codebook may be interchangeable.

[0056] In the present disclosure, the terms "priority index," "priority indicator," "service," and "traffic type" may be interchangeable. In the present disclosure, the terms "priority index of 0" and "eMBB" may be interchangeable. In the present disclosure, the terms "priority index of 1" and "URLLC" may be interchangeable.

[0057] In the present disclosure, the terms PDSCH-HARQ-ACK codebook type, PDSCH-HARQ-ACK codebook parameter, PDSCH-HARQ-ACK codebook, and PDSCH-HARQ-ACK-Codebook may be interchanged. In the present disclosure, the terms PDSCH-HARQ-ACK codebook type list, PDSCH-HARQ-ACK codebook parameter list, PDSCH-HARQ-ACK codebook list, and PDSCH-HARQ-ACK-CodebookList may be interchanged.

[0058] (Wireless communication method) <First embodiment> When a primary PUCCH group and a secondary PUCCH group are configured and a PDSCH-HARQ-ACK codebook type list (PDSCH-HARQ-ACK-CodebookList-r16, first list) is configured, the UE may determine the HARQ-ACK codebook type for the primary PUCCH group and the secondary PUCCH group.

[0059] The determination of the HARQ-ACK codebook type may be in accordance with any of the following aspects 1-1 to 1-3.

[0060] Aspect 1-1: The UE may determine the HARQ-ACK codebook type for the primary PUCCH group based on the PDSCH-HARQ-ACK codebook type list (FIG. 2: S110). The UE may ignore the PDSCH-HARQ-ACK codebook type when determining the HARQ-ACK codebook type for the primary PUCCH group.

[0061] If the PDSCH-HARQ-ACK codebook type list indicates one HARQ-ACK codebook type (indicating that one HARQ-ACK codebook is generated), the one HARQ-ACK codebook type may be associated with the PUCCH with priority index 0. If the PDSCH-HARQ-ACK codebook type list indicates two HARQ-ACK codebook types (indicating that two HARQ-ACK codebooks are generated), the first HARQ-ACK codebook type (value) may be associated with the PUCCH with priority index 0, and the second HARQ-ACK codebook type (value) may be associated with the PUCCH with priority index 1.

[0062] The UE may determine the HARQ-ACK codebook type for the secondary PUCCH group based on the PDSCH-HARQ-ACK codebook type (pdsch-HARQ-ACK-Codebook, first parameter) (FIG. 2: S120). The UE may use the PDSCH-HARQ-ACK codebook type in determining the HARQ-ACK codebook type for the secondary PUCCH group.

[0063] One HARQ-ACK codebook type indicated by the PDSCH-HARQ-ACK codebook type may be associated with a PUCCH with priority index 0, or may be associated with a PUCCH with priority index 0 and a PUCCH with priority index 1.

[0064] According to this aspect, the UE operation is the same regardless of whether the PDSCH-HARQ-ACK codebook type list is configured or not, which simplifies the UE configuration (reduces complexity).

[0065] Aspect 1-2: The UE may determine the HARQ-ACK codebook type for the primary PUCCH group based on the PDSCH-HARQ-ACK codebook type list (FIG. 3: S210). The UE may ignore the PDSCH-HARQ-ACK codebook type when determining the HARQ-ACK codebook type for the primary PUCCH group.

[0066] The UE may determine the HARQ-ACK codebook type for the secondary PUCCH group based on the PDSCH-HARQ-ACK codebook type list (FIG. 3: S220). The UE may ignore the PDSCH-HARQ-ACK codebook type when determining the HARQ-ACK codebook type for the secondary PUCCH group.

[0067] The determination of the HARQ-ACK codebook type may be in accordance with any of aspects 1-2-1 to 1-2-4.

[0068] [Aspect 1-2-1] The UE may use only the first HARQ-ACK codebook type in the PDSCH-HARQ-ACK codebook type list as the HARQ-ACK codebook type for the secondary PUCCH group.

[0069] If the PDSCH-HARQ-ACK codebook type list indicates one HARQ-ACK codebook type (indicating that one HARQ-ACK codebook is generated) as the HARQ-ACK codebook type for the primary PUCCH group, the one HARQ-ACK codebook type may be associated with the PUCCH with priority index 0. If the PDSCH-HARQ-ACK codebook type list indicates two HARQ-ACK codebook types (indicating that two HARQ-ACK codebooks are generated), the first HARQ-ACK codebook type (value) may be associated with the PUCCH with priority index 0, and the second HARQ-ACK codebook type (value) may be associated with the PUCCH with priority index 1.

[0070] The HARQ-ACK codebook type for the secondary PUCCH group (both the HARQ-ACK codebook type for the PUCCH with priority index 0 in the secondary PUCCH group and the HARQ-ACK codebook type for the PUCCH with priority index 1 in the secondary PUCCH group) may be the first HARQ-ACK codebook type (value) in the PDSCH-HARQ-ACK codebook type list.

[0071] [Aspect 1-2-2] The UE may use only the second HARQ-ACK codebook type in the PDSCH-HARQ-ACK codebook type list as the HARQ-ACK codebook type for the secondary PUCCH group.

[0072] If the PDSCH-HARQ-ACK codebook type list indicates one HARQ-ACK codebook type (indicating that one HARQ-ACK codebook is generated) as the HARQ-ACK codebook type for the primary PUCCH group, the one HARQ-ACK codebook type may be associated with the PUCCH with priority index 0. If the PDSCH-HARQ-ACK codebook type list indicates two HARQ-ACK codebook types (indicating that two HARQ-ACK codebooks are generated), the first HARQ-ACK codebook type (value) may be associated with the PUCCH with priority index 0, and the second HARQ-ACK codebook type (value) may be associated with the PUCCH with priority index 1.

[0073] The HARQ-ACK codebook type for the secondary PUCCH group (both the HARQ-ACK codebook type for the PUCCH with priority index 0 in the secondary PUCCH group and the HARQ-ACK codebook type for the PUCCH with priority index 1 in the secondary PUCCH group) may be the second HARQ-ACK codebook type (value) in the PDSCH-HARQ-ACK codebook type list.

[0074] According to aspect 1-2-1 / 1-2-2, the same HARQ-ACK codebook type as that actually used for the primary PUCCH group can be applied to the secondary PUCCH group, which simplifies the configuration of the UE (reduces complexity).

[0075] [Aspect 1-2-3] The UE may apply the first HARQ-ACK codebook type or the second HARQ-ACK codebook type (value) in the PDSCH-HARQ-ACK codebook type list as the HARQ-ACK codebook type for the primary PUCCH group and the secondary PUCCH group based on the priority index.

[0076] The HARQ-ACK codebook type for the PUCCH with priority index 0 (both the HARQ-ACK codebook type for the PUCCH with priority index 0 in the primary PUCCH group and the HARQ-ACK codebook type for the PUCCH with priority index 0 in the secondary PUCCH group) may be the first HARQ-ACK codebook type (value) in the PDSCH-HARQ-ACK codebook type list. The HARQ-ACK codebook type for the PUCCH with priority index 1 (both the HARQ-ACK codebook type for the PUCCH with priority index 1 in the primary PUCCH group and the HARQ-ACK codebook type for the PUCCH with priority index 1 in the secondary PUCCH group) may be the second HARQ-ACK codebook type (value) in the PDSCH-HARQ-ACK codebook type list.

[0077] According to aspect 1-2-3, it is possible to apply an optimal HARQ-ACK codebook type to a priority index.

[0078] [Aspect 1-2-4] The UE may apply the first HARQ-ACK codebook type or the second HARQ-ACK codebook type (value) in the PDSCH-HARQ-ACK codebook type list based on whether the PUCCH belongs to a primary PUCCH group or a secondary PUCCH group.

[0079] The HARQ-ACK codebook type for the primary PUCCH group (both the HARQ-ACK codebook type for the PUCCH with priority index 0 in the primary PUCCH group and the HARQ-ACK codebook type for the PUCCH with priority index 1 in the primary PUCCH group) may be the first HARQ-ACK codebook type (value) in the PDSCH-HARQ-ACK codebook type list. The HARQ-ACK codebook type for the secondary PUCCH group (both the HARQ-ACK codebook type for the PUCCH with priority index 0 in the secondary PUCCH group and the HARQ-ACK codebook type for the PUCCH with priority index 1 in the secondary PUCCH group) may be the second HARQ-ACK codebook type (value) in the PDSCH-HARQ-ACK codebook type list.

[0080] According to example 1-2-4, the optimal HARQ-ACK codebook type can be applied to each PUCCH group.

[0081] Aspect 1-3: The UE may determine the HARQ-ACK codebook type for the primary PUCCH group based on the PDSCH-HARQ-ACK codebook type list (FIG. 4: S310). The UE may ignore the PDSCH-HARQ-ACK codebook type when determining the HARQ-ACK codebook type for the primary PUCCH group.

[0082] If the PDSCH-HARQ-ACK codebook type list indicates one HARQ-ACK codebook type (indicating that one HARQ-ACK codebook is generated), the one HARQ-ACK codebook type may be associated with the PUCCH with priority index 0. If the PDSCH-HARQ-ACK codebook type list indicates two HARQ-ACK codebook types (indicating that two HARQ-ACK codebooks are generated), the first HARQ-ACK codebook type may be associated with the PUCCH with priority index 0, and the second HARQ-ACK codebook type may be associated with the PUCCH with priority index 1.

[0083] The UE may determine the HARQ-ACK codebook type for the secondary PUCCH group independently of the HARQ-ACK codebook type for the primary PUCCH group.

[0084] The determination of the HARQ-ACK codebook type may be in accordance with either of aspects 1-3-1 and 1-3-2.

[0085] [Aspect 1-3-1] The UE may apply a HARQ-ACK codebook type defined in the specifications to a secondary PUCCH group. For the secondary PUCCH group, the HARQ-ACK codebook type associated with the PUCCH with priority index 0 and the HARQ-ACK codebook type associated with the PUCCH with priority index 1 may be defined commonly or individually.

[0086] [Aspect 1-3-2] The UE may apply the HARQ-ACK codebook type set by higher layer parameters to the secondary PUCCH group (FIG. 4: S320). The higher layer parameters may be parameters for the secondary PUCCH group. The parameters for the secondary PUCCH group may be a PDSCH-HARQ-ACK codebook type for the secondary PUCCH group (e.g., pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup, second parameter) or a PDSCH-HARQ-ACK codebook type list for the secondary PUCCH group (e.g., pdsch-HARQ-ACK-CodebookList-secondaryPUCCHgroup, second list).

[0087] If multiple HARQ-ACK codebook types are configured by higher layer parameters (e.g., a PDSCH-HARQ-ACK codebook type list for a secondary PUCCH group), the first HARQ-ACK codebook type may be associated with the PUCCH with priority index 0, and the second HARQ-ACK codebook type may be associated with the PUCCH with priority index 1.

[0088] According to aspect 1-3, the HARQ-ACK codebook type of the secondary PUCCH group can be flexibly determined regardless of the HARQ-ACK codebook type of the primary PUCCH group.

[0089] According to the first embodiment described above, even when a primary PUCCH group and a secondary PUCCH group are configured and a PDSCH-HARQ-ACK codebook type list is configured, the HARQ-ACK codebook type of the primary PUCCH group and the HARQ-ACK codebook type of the secondary PUCCH group can be appropriately determined.

[0090] <Second embodiment> When a primary PUCCH group and a secondary PUCCH group are configured, a PDSCH-HARQ-ACK codebook type list (PDSCH-HARQ-ACK-CodebookList-r16) is configured, and a PDSCH-HARQ-ACK codebook type for the secondary PUCCH group (for example, pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup) is configured, the HARQ-ACK codebook type may be determined in accordance with any of the first embodiment (aspects 1-1 to 1-3).

[0091] When the UE follows aspect 1-1 or 1-2, the UE may ignore the PDSCH-HARQ-ACK codebook type for the secondary PUCCH group. When the UE follows aspect 1-3, the higher layer parameter may be the PDSCH-HARQ-ACK codebook type for the secondary PUCCH group.

[0092] According to the second embodiment described above, even when a primary PUCCH group and a secondary PUCCH group are configured, a PDSCH-HARQ-ACK codebook type list is configured, and a PDSCH-HARQ-ACK codebook type for the secondary PUCCH group is configured, the HARQ-ACK codebook type for the primary PUCCH group and the HARQ-ACK codebook type for the secondary PUCCH group can be appropriately determined.

[0093] <Third embodiment> When a primary PUCCH group and a secondary PUCCH group are configured, a PDSCH-HARQ-ACK codebook type list (PDSCH-HARQ-ACK-CodebookList-r16) is configured, and a PDSCH-HARQ-ACK codebook type list for a secondary PUCCH group (e.g., pdsch-HARQ-ACK-CodebookList-secondaryPUCCHgroup) is configured, the determination of the HARQ-ACK codebook type may follow any of the first embodiment (aspects 1-1 to 1-3).

[0094] When the UE follows aspect 1-1 or 1-2, the UE may ignore the PDSCH-HARQ-ACK codebook type for the secondary PUCCH group. When the UE follows aspect 1-3, the higher layer parameter may be a PDSCH-HARQ-ACK codebook type list for the secondary PUCCH group.

[0095] According to the above third embodiment, even when a primary PUCCH group and a secondary PUCCH group are configured, a PDSCH-HARQ-ACK codebook type list is configured, and a PDSCH-HARQ-ACK codebook type list for the secondary PUCCH group is configured, it is possible to appropriately determine the HARQ-ACK codebook type of the primary PUCCH group and the HARQ-ACK codebook type of the secondary PUCCH group.

[0096] (Wireless Communication System) The 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 thereof.

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

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

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

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

[0101] 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 located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 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 base station 10.

[0102] 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 (CA) using multiple component carriers (CCs) and dual connectivity (DC).

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

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

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

[0106] 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, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), a Next Generation Core (NGC), and the like.

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

[0108] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0109] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

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

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

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

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

[0114] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0115] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching 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 more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

[0116] One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0117] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

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

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

[0120] 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 referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0121] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0122] (Base Station) Fig. 6 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 the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

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

[0124] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from 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.

[0125] 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 transceiver unit 120, the transceiver 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 transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0126] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 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.

[0127] 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, the RF unit 122, and a measurement unit 123.

[0128] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

[0130] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0131] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) 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.

[0132] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

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

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

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

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

[0137] 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), control plane data, etc. for the user terminal 20.

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

[0139] The transceiver 120 may transmit transmission configuration indication (TCI) state information indicating a plurality of TCI states applicable to a plurality of types of channels, and may transmit first downlink control information indicating one TCI state among the plurality of TCI states. The controller 110 may apply the one TCI state to a first signal after a timing when a specific time has elapsed from either the first downlink control information or a first uplink channel based on the first downlink control information.

[0140] The transceiver unit 120 may transmit a first configuration of a primary physical uplink control channel (PUCCH) group, a second configuration of a secondary PUCCH group, and a first list indicating one or more hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook types for a physical downlink shared channel (PDSCH). The controller 110 may control reception of one or more first HARQ-ACK codebook types for the primary PUCCH group and reception of one or more second HARQ-ACK codebook types for the secondary PUCCH group. The first HARQ-ACK codebook type may be determined based on the first list. The second HARQ-ACK codebook type may be determined based on at least one of the first list, higher layer parameters, and specifications.

[0141] (User Terminal) Fig. 7 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0142] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0143] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

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

[0145] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be 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.

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

[0147] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

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

[0149] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

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

[0151] The transmitter / receiver unit 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 string to be transmitted, and output a baseband signal.

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

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

[0154] 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 band signal received by the transceiver antenna 230.

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

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

[0157] The transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting / receiving unit 220 and the transmitting / receiving antenna 230.

[0158] The transceiver unit 220 may receive a first configuration of a primary physical uplink control channel (PUCCH) group, a second configuration of a secondary PUCCH group, and a first list indicating one or more hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook types for a physical downlink shared channel (PDSCH). The control unit 210 may determine one or more first HARQ-ACK codebook types for the primary PUCCH group based on the first list, and may determine one or more second HARQ-ACK codebook types for the secondary PUCCH group based on the first list and at least one of higher layer parameters and specifications.

[0159] The upper layer parameter may be one of a first parameter indicating one HARQ-ACK codebook type for the primary PUCCH group (aspect 1-1), a second parameter indicating one HARQ-ACK codebook type for the secondary PUCCH group (aspect 1-3-2), and a second list indicating one or more HARQ-ACK codebook types for the secondary PUCCH group (aspect 1-3-2).

[0160] The control unit 210 may apply one of the first value in the first list, the second value in the first list, and a value corresponding to a priority index in the first list to the one or more first HARQ-ACK codebook types and the one or more second HARQ-ACK codebook types (aspect 1-2).

[0161] When the upper layer parameter is the second list and the second list indicates two HARQ-ACK codebook types, the control unit 210 may apply the first value in the second list to a PUCCH with priority index 0 for the secondary PUCCH group, and may apply the second value in the second list to a PUCCH with priority index 1 for the secondary PUCCH group (aspect 1-3-2).

[0162] (Hardware Configuration) Note that 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. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0163] 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, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

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

[0165] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used 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.

[0166] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0167] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0168] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as 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), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0169] The processor 1001 also reads 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0170] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0171] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), 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, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0172] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. 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.

[0173] 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, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0174] Furthermore, 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.

[0175] 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), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0176] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

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

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

[0179] 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. A slot may also be a time unit based on numerology.

[0180] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist 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.

[0181] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to 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 interchangeable.

[0182] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in 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.

[0183] Here, TTI refers to, for example, the smallest 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.

[0184] 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) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0185] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

[0187] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 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 greater than or equal to 1 ms.

[0188] 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 numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.

[0189] 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 which may be composed of one or more resource blocks.

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

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

[0192] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

[0194] 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 read as "BWP."

[0195] The above-described 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.

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

[0197] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

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

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

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

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

[0202] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

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

[0204] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

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

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

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

[0208] 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," etc. may be used interchangeably.

[0209] In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNB (eNodeB)," "gNB (gNodeB)," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "cell," "sector," "cell group," "carrier," "component carrier," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0210] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

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

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

[0213] At least one of the base station and the mobile station may be referred to as 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 mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile 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 also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0214] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments 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 multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). 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, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0215] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0216] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0217] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed 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.

[0218] Each aspect / embodiment described in the present disclosure may be a technology other than Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or decimal number)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other appropriate wireless communication methods, or to next-generation systems that are based on these and are extended thereto. In addition, the present invention may be applied to a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G).

[0219] 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."

[0220] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. 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 in some way precede the second element.

[0221] 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, etc.

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

[0223] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0224] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

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

[0226] 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 elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access."

[0227] 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, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0228] 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."

[0229] 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." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0230] In this disclosure, where articles are 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.

[0231] 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 in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A terminal having: a receiver that receives a first configuration of a primary physical uplink control channel (PUCCH) group, a second configuration of a secondary PUCCH group, and a first list indicating one or more hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook types for a physical downlink shared channel (PDSCH); and a controller that determines one or more first HARQ-ACK codebook types for the primary PUCCH group based on the first list, and determines one or more second HARQ-ACK codebook types for the secondary PUCCH group based on at least one of the first list, higher layer parameters, and specifications.

2. The terminal of claim 1, wherein the higher layer parameter is one of a first parameter indicating one HARQ-ACK codebook type for the primary PUCCH group, a second parameter indicating one HARQ-ACK codebook type for the secondary PUCCH group, and a second list indicating one or more HARQ-ACK codebook types for the secondary PUCCH group.

3. The terminal according to claim 1, wherein the control unit applies one of the first value in the first list, the second value in the first list, and a value corresponding to a priority index in the first list to the one or more first HARQ-ACK codebook types and the one or more second HARQ-ACK codebook types.

4. The terminal of claim 2, wherein, when the higher layer parameter is the second list and the second list indicates two HARQ-ACK codebook types, the control unit applies a first value in the second list to a PUCCH with a priority index of 0 for the secondary PUCCH group and applies a second value in the second list to a PUCCH with a priority index of 1 for the secondary PUCCH group.

5. A wireless communication method for a terminal, comprising: receiving a first configuration of a primary physical uplink control channel (PUCCH) group, a second configuration of a secondary PUCCH group, and a first list indicating one or more hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook types for a physical downlink shared channel (PDSCH); and determining one or more first HARQ-ACK codebook types for the primary PUCCH group based on the first list, and determining one or more second HARQ-ACK codebook types for the secondary PUCCH group based on at least one of the first list and higher layer parameters and specifications.

6. A base station comprising: a transmitter unit that transmits a first configuration of a primary physical uplink control channel (PUCCH) group, a second configuration of a secondary PUCCH group, and a first list indicating one or more hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook types for a physical downlink shared channel (PDSCH); and a controller that controls reception of one or more first HARQ-ACK codebook types for the primary PUCCH group and reception of one or more second HARQ-ACK codebook types for the secondary PUCCH group, wherein the first HARQ-ACK codebook type is determined based on the first list, and the second HARQ-ACK codebook type is determined based on at least one of the first list, higher layer parameters, and specifications.

Images