Method and apparatus for transmitting and receiving signals in a wireless communication system

Abstract

According to an embodiment of the present invention, a user equipment: receives DCI via PDCCH; and sends a HARQ-ACK report, wherein, based on the DCI indicating a HARQ-ACK report based on a specific type of codebook for sending ACK / NACK for all HARQ processes of the serving cell at one time and the user equipment is configured to report each NDI bit via the HARQ-ACK report based on the specific type of codebook, even if spatial bundling has been configured on the user equipment, the user equipment can send the HARQ-ACK report based on the specific type of codebook without spatial bundling.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting or receiving uplink / downlink wireless signals in the wireless communication system. Background Art

[0002] Wireless communication systems have been widely deployed to provide various types of communication services, such as voice and data. Typically, wireless communication systems are multiple-access systems that can support communication with multiple users by sharing available system resources (bandwidth, transmit power, etc.). Examples of multiple-access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single-carrier frequency division multiple access (SC-FDMA). Summary of the Invention

[0003] Technical issues

[0004] An object of the present disclosure is to provide a method and apparatus for efficiently performing a wireless signal transmission / reception process.

[0005] The technical objectives to be achieved by the present disclosure are not limited to the above-mentioned technical objectives, and other technical objectives not described herein will be clearly understood by those skilled in the art from the following description.

[0006] Technical Solution

[0007] In one aspect of the present disclosure, a method for transmitting a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) report by a user equipment (UE) in a wireless communication system may include: receiving downlink control information (DCI) through a physical downlink control channel (PDCCH); and transmitting a HARQ-ACK report based on the DCI. When transmitting the HARQ-ACK report, even if spatial bundling of ACK / negative ACK (NACK) bits based on transport blocks (TBs) is configured, based on the DCI indicating a HARQ-ACK report based on a specific type of codebook for transmitting ACK / NACK for all HARQ processes of one or more serving cells configured for the UE at one time and the UE is configured to report each new data indicator (NDI) bit through the HARQ-ACK report based on the specific type of codebook, the UE may report each NDI bit and each TB-based ACK / NACK bit without performing spatial bundling.

[0008] In another aspect of the present disclosure, a user equipment (UE) may include: a transceiver; and a processor configured to receive downlink control information (DCI) through a physical downlink control channel (PDCCH) by controlling the transceiver and send a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) report based on the DCI. When sending the HARQ-ACK report, even if spatial bundling of ACK / negative ACK (NACK) bits based on transport blocks (TBs) is configured, based on the DCI indicating a HARQ-ACK report based on a specific type of codebook for one-time transmission of ACK / NACK for all HARQ processes of one or more serving cells configured for the UE and the UE being configured to report each new data indicator (NDI) bit through the HARQ-ACK report based on the specific type of codebook, the processor may report each NDI bit and each TB-based ACK / NACK bit without performing spatial bundling.

[0009] The specific type codebook is a type 3 codebook, and for HARQ-ACK reports based on the type 3 codebook configured to include individual NDI bits, spatial bundling may not be performed as an exception to spatial bundling. Depending on whether the HARQ-ACK report based on the type 3 codebook is configured to include individual NDI bits, an exception to spatial bundling may apply. For HARQ-ACK reports based on type 1 or type 2 codebooks other than the type 3 codebook, spatial bundling may be performed on the corresponding TB-based ACK / NACK bits.

[0010] The UE may receive, through higher layer signaling, a configuration for spatial bundling of corresponding TB-based ACK / NACK bits using a logical AND operation and a configuration for reporting each NDI bit through a HARQ-ACK report based on a specific type of codebook.

[0011] One or more serving cells may include a specific serving cell that performs CBG (code block group)-based transmission. The UE may determine, based on higher layer signaling, whether to perform CBG-based ACK / NACK reporting or TB-based ACK / NACK reporting for a specific serving cell through HARQ-ACK reporting based on a specific type of codebook. The specific type of codebook may be a type 3 codebook. Even if the UE determines, based on higher layer signaling, to perform TB-based ACK / NACK reporting for a specific serving cell through HARQ-ACK reporting based on a type 3 codebook, the UE may perform CBG-based ACK / NACK reporting for the specific serving cell through HARQ-ACK reporting based on a type 1 or type 2 codebook, which is different from the type 3 codebook.

[0012] The ACK / NACK bits of the lower index serving cell may be mapped to the lower index bits in the HARQ-ACK report based on a specific type of codebook. Among the ACK / NACK bits of the same index serving cell, the ACK / NACK bits of the lower index HARQ process may be mapped to the lower index bits in the HARQ-ACK report based on a specific type of codebook. Among the ACK / NACK bits of the same index HARQ process, the ACK / NACK bits of the lower index TB may be mapped to the lower index bits in the HARQ-ACK report based on a specific type of codebook. Among the ACK / NACK bits of the multiple code block groups (CBGs) included in the corresponding TB, the ACK / NACK bits of the lower index CBG may be mapped to the lower index bits in the HARQ-ACK report based on the specific type of codebook.

[0013] Each NDI bit included in the HARQ-ACK report based on the specific type of codebook may be configured with an NDI field value included in the corresponding DCI for scheduling the corresponding TB.

[0014] The UE may receive the first TB through a physical downlink shared channel (PDSCH) of the first serving cell according to TB-based scheduling. The UE may receive the code block group (CBG) of the second TB through the PDSCH of the second serving cell according to CBG-based scheduling. The HARQ-ACK report based on the specific type of codebook may include a TB-based ACK / NACK bit of the first TB, an NDI bit of the first TB, and an NDI bit of the second TB. The HARQ-ACK report based on the specific type of codebook may include a TB-based ACK / NACK bit of the second TB or a CBG-based ACK / NACK bit of the CBG of the second TB.

[0015] In another aspect of the present disclosure, a processor-readable recording medium recording instructions for executing the above method may be provided.

[0016] In another aspect of the present disclosure, an apparatus for performing signal processing for wireless communication may include: a memory storing instructions; and a processor executing the instructions to perform operations, the operations including receiving downlink control information (DCI) through a physical downlink control channel (PDCCH); and sending a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) report based on the DCI. When sending the HARQ-ACK report, even if spatial bundling of ACK / negative ACK (NACK) bits based on transport blocks (TBs) is configured, based on the DCI indicating a HARQ-ACK report based on a specific type of codebook for transmitting ACK / NACK for all HARQ processes of one or more serving cells configured for the apparatus at one time and the apparatus being configured to report each new data indicator (NDI) bit through the HARQ-ACK report based on the specific type of codebook, the processor may report each NDI bit and each TB-based ACK / NACK bit without performing spatial bundling.

[0017] In another aspect of the present disclosure, a method for receiving a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) report by a base station in a wireless communication system may include: transmitting downlink control information (DCI) to a user equipment (UE) through a physical downlink control channel (PDCCH); and receiving a HARQ-ACK report from the UE based on the DCI. When receiving the HARQ-ACK report, even if the UE is configured to perform spatial bundling for ACK / negative ACK (NACK) bits based on transport blocks (TBs), based on indicating, through the DCI, a HARQ-ACK report based on a specific type of codebook for receiving ACK / NACK for all HARQ processes of one or more serving cells configured for the UE at one time and configuring the UE to report each new data indicator (NDI) bit through the HARQ-ACK report based on the specific type of codebook, the base station may obtain each NDI bit and each TB-based ACK / NACK bit through the HARQ-ACK report based on the specific type of codebook without applying spatial bundling.

[0018] In another aspect of the present disclosure, a base station for wireless communication may include: a transceiver; and a processor, configured to control the transceiver to transmit downlink control information (DCI) to a user equipment (UE) via a physical downlink control channel (PDCCH), and receive a hybrid automatic repeat request (HARQ)-acknowledgement (ACK) report from the UE based on the DCI. When receiving the HARQ-ACK report, even if the UE is configured to perform spatial bundling for ACK / negative ACK (NACK) bits based on transport blocks (TBs), based on indicating, through the DCI, a HARQ-ACK report based on a specific type of codebook for receiving ACK / NACK for all HARQ processes of one or more serving cells configured for the UE at one time and configuring the UE to report each new data indicator (NDI) bit through the HARQ-ACK report based on the specific type of codebook, the processor can obtain each NDI bit and each TB-based ACK / NACK bit through the HARQ-ACK report based on the specific type of codebook without applying spatial bundling.

[0019] Technical Effects

[0020] According to the present disclosure, wireless signals can be efficiently transmitted and received in a wireless communication system.

[0021] Effects achievable by the present disclosure are not limited to the above-described effects, and those skilled in the art may clearly understand other effects not described herein from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings are included as a part of the detailed description for understanding the present disclosure. The accompanying drawings provide embodiments of the present disclosure and describe technical features of the present disclosure together with the detailed description.

[0023] Figure 1 Physical channels used in a 3GPP system as an example of a wireless communication system and a general signal transmission method using them are illustrated.

[0024] Figure 2 The frame structure is illustrated.

[0025] Figure 3 A resource grid of time slots is illustrated.

[0026] Figure 4 The structure of a self-contained time slot is illustrated.

[0027] Figure 5 An example is illustrated in which physical channels are mapped into self-contained time slots.

[0028] Figure 6 The ACK / NACK transmission process is illustrated.

[0029] Figure 7 The PUSCH (Physical Uplink Shared Channel) transmission process is illustrated.

[0030] Figure 8 This illustrates an example of multiplexing control information into the PUSCH.

[0031] Figure 9 A wireless communication system supporting a license-free frequency band is exemplified.

[0032] Figure 10 A method for occupying resources in a license-exempt band is illustrated.

[0033] Figure 11 A flow chart illustrating Type 1 CAP operation of a user equipment for uplink signal transmission is shown.

[0034] Figures 12 to 14 A / N transmission according to an embodiment of the present disclosure is illustrated.

[0035] Figure 15 The existing transport block (TB) processing procedure is illustrated.

[0036] Figure 16 Existing CBG-based transmission is illustrated.

[0037] Figure 17 A / N transmission based on a type 3 codebook is illustrated.

[0038] Figure 18 A / N transmission based on a type 3 codebook according to an embodiment of the present disclosure is illustrated.

[0039] Figure 19 A / N transmission according to an embodiment of the present disclosure is illustrated.

[0040] Figures 20 to 23 An A / N based on a type 3 codebook according to an embodiment of the present disclosure is illustrated.

[0041] Figure 24 A / N transmission based on a type 3 codebook according to an embodiment of the present disclosure is illustrated.

[0042] Figures 25 to 28 The communication system 1 and wireless device applied to the present disclosure are exemplified.

[0043] Figure 29 A discontinuous reception (DRX) operation applicable to the present invention is illustrated. DETAILED DESCRIPTION

[0044] The following description may be applied to various radio access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA may be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented by radio technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-A (Advanced) is an advanced version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A.

[0045] As more communication devices have higher capacity, there has been a need for improved mobile broadband communications compared to existing radio access technologies (RATs). In addition, large-scale MTC (machine type communication) that provides various services anytime and anywhere by connecting multiple devices and things is also one of the main issues to be considered in the next generation of communications. In addition, the design of communication systems considering services / terminals that are sensitive to reliability and latency is also discussed. In this way, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable and low-latency communication), etc. is discussed, and for convenience, the corresponding technology is referred to as NR in this disclosure.

[0046] For clarification, description is made based on 3GPP NR, but the technical concept of the present disclosure is not limited thereto.

[0047] In the present disclosure, the expression "setting" can be replaced by the expression "configuration", and the two can be used interchangeably. In addition, conditional expressions (for example, "if", "in the case of..." or "when...", etc.) can be replaced by expressions "based on..." or "under the state of...". In addition, the operation or SW / HW configuration of the terminal / base station based on the corresponding conditions can be inferred / understood. In addition, if the processing of the receiving (or transmitting) side can be derived / understood from the processing of the transmitting (or receiving) side in the signal transmission / reception between wireless communication devices (for example, base stations, terminals), its description can be omitted. For example, signal determination / generation / encoding / transmission on the transmitting side can be understood as signal monitoring, reception / decoding / determination on the receiving side. In addition, the expression that the terminal performs (or does not perform) a specific operation can also be interpreted as the base station expecting / assuming (or expecting / assuming that the terminal does not perform) the terminal to perform the specific operation. The expression that the base station performs (or does not perform) a specific operation can also be interpreted as the terminal expecting / assuming (or expecting / assuming that the base station does not perform) the base station to perform the specific operation. In addition, in the description to be described later, the division and indexing of each section, embodiment, example, option, method, scheme, etc. are for convenience of description and should not be interpreted as implying that each necessarily constitutes a separate scope or that each should only be implemented separately. In addition, when describing each section, embodiment, example, option, method, scheme, etc., if there is no clear conflicting / contrary technology, it can be inferred / interpreted that at least some combinations thereof can be implemented together, or at least some of them can be omitted.

[0048] In wireless communication systems, user equipment receives information from a base station via a downlink (DL) and transmits information to the base station via an uplink (UL). The information transmitted and received between the base station and the user equipment includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0049] Figure 1 This section illustrates physical channels used in the 3GPP NR system and a general signal transmission method using them.

[0050] When the terminal is turned on or newly enters a cell in a state where the terminal is turned off, the terminal performs an initial cell search in step S101 by including synchronization with the base station. For the initial cell search, the terminal receives a synchronization signal block (SSB) from the base station. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The terminal synchronizes with the base station based on the PSS / SSS and obtains information such as a cell identifier (ID). In addition, the terminal can obtain broadcast information in the cell based on the PBCH. In addition, the terminal can check the downlink channel status by receiving a downlink reference signal (DLRS) during the initial cell search phase.

[0051] In step S102 , the terminal that has completed the initial cell search may obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to the physical downlink control channel.

[0052] Afterwards, the terminal may perform a random access procedure such as steps S103 to S106 to complete access to the base station. For the random access procedure, the terminal may transmit a preamble code through a physical random access channel (PRACH) (S103) and may receive a response message to the preamble code through a physical downlink control channel and a corresponding physical downlink shared channel (S104). In the case of contention-based random access, a contention resolution procedure may be performed, such as transmitting an additional physical random access channel (S105) and receiving a physical downlink control channel and a corresponding physical downlink shared channel (S106).

[0053] The terminal that performs the above process can then perform physical downlink control channel / physical downlink shared channel reception (S107) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S108) as a general uplink / downlink signal transmission process. The control information sent by the terminal to the base station is called uplink control information (UCI). UCI includes hybrid automatic repeat request confirmation / negative ACK (HARQ ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix indicator (PMI), rank indication (RI), etc. UCI is usually sent through PUCCH, but when control information and service data are to be sent at the same time, UCI can be sent through PUSCH. In addition, UCI can be sent through PUSCH aperiodically according to the request / instruction of the network.

[0054] Figure 2 The frame structure is illustrated. In NR, uplink and downlink transmissions are configured as frames. Each radio frame has a length of 10ms and is divided into two 5ms half frames (HF). Each half frame is divided into 5 1ms subframes (SF). The subframe is divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols. When using normal CP, each time slot includes 14 OFDM symbols. When using extended CP, each time slot includes 12 OFDM symbols.

[0055] Table 1 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS when a normal CP is used.

[0056] [Table 1]

[0057] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame，u slot ]]> <![CDATA[N subframe，u slot ]]> 15KHz (u=0) 14 10 1 30KHz (u=1) 14 20 2 60KHz (u=2) 14 40 4 120KHz (u=3) 14 80 8 240KHz (u=4) 14 160 16

[0058] *N slot symb : The number of symbols in a time slot

[0059] *N frame,u slot : The number of time slots in a frame

[0060] *N subframe,u slot : The number of time slots in a subframe

[0061] Table 2 illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS when extended CP is used.

[0062] [Table 2]

[0063] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame，u slot ]]> <![CDATA[N subframe，u slot ]]> 60KHz (u=2) 12 40 4

[0064] The structure of the frame is merely an example, and the number of subframes, the number of slots, and the number of symbols in a frame may be changed in various ways.

[0065] In the NR system, OFDM parameter sets (e.g., SCS) can be configured differently between multiple cells aggregated into one UE. Therefore, the (absolute time) duration of a time resource (e.g., SF, time slot, or TTI) (e.g., for convenience, referred to as a TU (time unit)) consisting of the same number of symbols can be configured differently between the aggregated cells. Here, the symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or discrete Fourier transform spread OFDM, DFT-s-OFDM symbols).

[0066] Figure 3A resource grid of a time slot is illustrated. A time slot includes multiple symbols in the time domain. For example, in the case of normal CP, one time slot includes 14 symbols, but in the case of extended CP, one time slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as a plurality of consecutive physical RBs (PRBs) in the frequency domain and can correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for one UE. Each element in the resource grid is called a resource element (RE) and one complex symbol can be mapped.

[0067] Figure 4 The structure of a self-contained time slot is illustrated. In the NR system, the frame is characterized by a self-contained structure in which a DL control channel, DL or UL data, and a UL control channel can all be included in one time slot. For example, the first N symbols in the time slot can be used to send a DL control channel (hereinafter, a DL control region), and the last M symbols in the time slot can be used to send a UL control channel (hereinafter, a UL control region). N and M are each integers greater than or equal to 0. The resource region (hereinafter, a data region) between the DL control region and the UL control region can be used for DL ​​data transmission or for UL data transmission. A time gap for DL ​​to UL or UL to DL switching may exist between the control region and the data region. As an example, the following configuration can be considered. Each duration is listed in chronological order.

[0068] 1. DL configuration only

[0069] 2. UL configuration only

[0070] 3. Hybrid UL-DL configuration

[0071] -DL region + guard period (GP) + UL control region

[0072] -DL control area + GP + UL area

[0073] *DL area: (i) DL data area, (ii) DL control area + DL data area

[0074] *UL area: (i) UL data area, (ii) UL data area + UL control area

[0075] Figure 5This section illustrates an example where physical channels are mapped into self-contained time slots. The PDCCH can be transmitted in the DL control region, and the PDSCH can be transmitted in the DL data region. The PUCCH can be transmitted in the UL control region, and the PUSCH can be transmitted in the UL data region. The GP provides a time gap when the base station and UE switch from transmit mode to receive mode, or when switching from receive mode to transmit mode. Some symbols in a subframe during the time of switching from DL to UL can be configured as GPs.

[0076] In the following, each physical channel will be described in more detail.

[0077] PDCCH carries downlink control information (DCI). For example, PCCCH (i.e., DCI) carries the transmission format and resource allocation of the downlink shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information of the paging channel (PCH), system information on DL-SCH, resource allocation information of higher-layer control messages such as random access responses sent on PDSCH, transmission power control commands, activation / deactivation of configuration scheduling (CS), etc. DCI includes a cyclic redundancy check (CRC) and is masked / scrambled with various identifiers (IDs) (e.g., radio network temporary identifier, RNTI) depending on the owner or purpose of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked by the UE identifier (e.g., cell RNTI, C-RNTI). If the PDCCH is related to paging, the CRC is masked with the paging RNTI (P-RNTI). If the PDCCH is related to system information (eg, system information block, SIB), the CRC is masked with the system information RNTI (SI-RNTI). When the PDCCH is related to a random access response, the CRC is masked with the random access RNTI (RA-RNTI).

[0078] Depending on the aggregation level (AL), the PDCCH is configured as 1, 2, 4, 8, or 16 CCEs (Control Channel Elements). A CCE is a logical allocation unit for providing a PDCCH with a predetermined code rate according to the radio channel state. A CCE includes 6 REGs (Resource Element Groups). A REG is defined by one OFDM symbol and one (P)RB. The PDCCH is transmitted through a control resource set (CORESET). A CORESET is defined as a set of REGs with a given parameter set (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE can overlap in the time / frequency domain. The CORESET can be configured by system information (e.g., Master Information Block, MIB) or UE-specific higher-layer (e.g., Radio Resource Control, RRC, layer) signaling. Specifically, the number of RBs and the number of OFDM symbols (maximum 3) included in the CORESET can be configured by higher-layer signaling.

[0079] For PDCCH reception / detection, the UE monitors PDCCH candidates. PDCCH candidates represent the CCEs that the UE needs to monitor for PDCCH detection. Depending on the AL, each PDCCH candidate is defined as 1, 2, 4, 8 or 16 CCEs. Monitoring includes (blind) decoding of PDCCH candidates. The set of PDCCH candidates monitored by the UE is defined as the PDCCH search space (SS). The search space includes a common search space (CSS) or a UE-specific search space (USS). The UE can obtain DCI by monitoring PDCCH candidates in one or more search spaces configured by MIB or higher-layer signaling. Each CORESET is associated with one or more search spaces, and each search space is associated with one CORESET. The search space can be defined based on the following parameters.

[0080] -controlResourceSetId: Indicates the CORESET associated with the search space

[0081] -monitoringSlotPeriodicityAndOffset: indicates the PDCCH monitoring period (time slot unit) and PDCCH monitoring duration offset (time slot unit)

[0082] -monitoringSymbolsWithinSlot: indicates the PDCCH monitoring symbols in the slot (e.g., indicating the first symbol of CORESET)

[0083] -nrofCandidate: indicates the number of PDCCH candidates (one of 0, 1, 2, 3, 4, 5, 6, 8) for each AL = {1, 2, 4, 8, 16}.

[0084] * A timing (eg, time / frequency resources) for monitoring a PDCCH candidate is defined as a PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings may be configured within a slot.

[0085] Table 3 illustrates the characteristics of each search space type.

[0086] [Table 3]

[0087]

[0088] Table 4 illustrates a DCI format transmitted on the PDCCH.

[0089] [Table 4]

[0090]

[0091] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or CBG (code block group) (or CBG-level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0 / 0_1 can be called UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be called DL grant DCI or UL scheduling information. DCI format 2_0 is used to send dynamic slot format information (e.g., dynamic SFI) to the UE, and DCI format 2_1 is used to send downlink preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 may be transmitted to user equipments in a corresponding group through a group-common PDCCH, which is a PDCCH transmitted to UEs defined as one group.

[0092] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, and DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. Regardless of the UE configuration, the fallback DCI formats have the same DCI size / field configuration. On the other hand, the non-fallback DCI formats have different DCI sizes / field configurations depending on the UE configuration.

[0093] The PDSCH carries downlink data (e.g., DL-SCH transport block, DL-SCH TB) and modulation methods such as QPSK (quadrature phase shift keying), 16QAM (quadrature amplitude modulation), 64QAM, 256QAM, etc. are applied to the PDSCH. A codeword is generated by encoding the TB. The PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to a resource together with a demodulation reference signal (DMRS), generated as an OFDM symbol signal, and sent through the corresponding antenna port.

[0094] PUCCH carries uplink control information (UCI). UCI includes:

[0095] -SR (Scheduling Request): It is information for requesting UL-SCH resources.

[0096] - Hybrid Automatic Repeat Request (HARQ)-ACK (Acknowledgement): It is a response to a downlink data packet (e.g., codeword) on the PDSCH. It indicates whether the downlink data packet has been successfully received. A 1-bit HARQ-ACK can be sent in response to a single codeword. A 2-bit HARQ-ACK can be sent in response to two codewords. The HARQ-ACK response includes positive ACK (abbreviated as ACK), negative ACK (NACK), DTX, or NACK / DTX. Here, HARQ-ACK includes HARQ ACK / NACK and ACK / NACK.

[0097] -CSI (Channel State Information): It is feedback information of the downlink channel. Multiple Input Multiple Output (MIMO) related feedback information includes Rank Indicator (RI) and Precoding Matrix Indicator (PMI).

[0098] Table 5 illustrates the PUCCH format. According to the PUCCH transmission length, it can be divided into short PUCCH (format 0, 2) and long PUCCH (format 1, 3, 4).

[0099] [Table 5]

[0100]

[0101] PUCCH format 0 carries UCI with a maximum size of 2 bits and is mapped and transmitted based on a sequence. Specifically, the UE transmits specific UCI to the base station by transmitting one of multiple sequences via a PUCCH with PUCCH format 0. Only when a positive SR is transmitted, the UE transmits a PUCCH with PUCCH format 0 in the PUCCH resource used to configure the corresponding SR.

[0102] PUCCH format 1 carries UCI with a maximum size of 2 bits, and the modulation symbol is spread in the time domain by an orthogonal cover code (OCC) (which is configured differently depending on whether frequency hopping is performed). DMRS is transmitted in symbols where no modulation symbol is transmitted (i.e., time division multiplexing (TDM) is performed and transmitted).

[0103] PUCCH format 2 carries UCI with a bit size greater than 2 bits and transmits modulation symbols using frequency division multiplexing (FDM) with DMRS. DM-RS are located at symbol indices #1, #4, #7, and #10 in a given resource block with a density of 1 / 3. A pseudo-noise (PN) sequence is used for the DM-RS sequence. Frequency hopping can be activated for 2-symbol PUCCH format 2.

[0104] In PUCCH format 3, UE multiplexing is not performed in the same physical resource block, and PUCCH format 3 carries UCI with a bit size greater than 2 bits. In other words, the PUCCH resources of PUCCH format 3 do not include orthogonal cover codes. Modulation symbols are transmitted by time division multiplexing (TDM) with DMRS.

[0105] PUCCH format 4 supports multiplexing up to 4 UEs in the same physical resource block and carries UCI with a bit size greater than 2 bits. In other words, the PUCCH resources of PUCCH format 3 include orthogonal cover codes. The modulation symbols are transmitted by time division multiplexing (TDM) with DMRS.

[0106] The PUSCH carries uplink data (e.g., UL-SCH transport blocks, UL-SCH TBs) and / or uplink control information (UCI) and is transmitted based on a CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) waveform or a DFT-s-OFDM (Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing) waveform. When the PUSCH is transmitted based on a DFT-s-OFDM waveform, the UE transmits the PUSCH by applying transform precoding. For example, when transform precoding is not possible (e.g., transform precoding is disabled), the UE transmits the PUSCH based on a CP-OFDM waveform, and when transform precoding is possible (e.g., transform precoding is enabled), the UE transmits the PUSCH based on a CP-OFDM waveform or a DFT-s-OFDM waveform. PUSCH transmission can be dynamically scheduled by a UL grant in the DCI, or semi-statically (configured grant) based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). PUSCH transmission may be performed on codebook-based transmission or non-codebook-based transmission.

[0107] Figure 6The ACK / NACK transmission process is illustrated. Figure 6 , the UE can detect the PDCCH in time slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI formats 1_0 and 1_1), and the PDCCH indicates the DL assignment to the PDSCH offset (k0) and the PDSCH-HARQ-ACK report offset (k1). For example, DCI formats 1_0 and 1_1 can include the following information.

[0108] - Frequency domain resource assignment: indicates the set of RBs allocated to PDSCH

[0109] - Time domain resource assignment: Indicates K0 (e.g., slot offset), the starting position of the PDSCH in slot #n+K0 (e.g., OFDM symbol index), and the length of the PDSCH (e.g., the number of OFDM symbols)

[0110] -PDSCH-to-HARQ_feedback timing indicator: indicates K1

[0111] -HARQ process number (4 bits): Indicates the HARQ process ID (identification) of the data (e.g., PDSCH, TB)

[0112] Thereafter, after the UE receives the PDSCH from slot #(n+K0) according to the scheduling information of slot #n, and if the reception of the PDSCH in slot #n1 (where n+K0≤n1) ends, the UE may transmit UCI through the PUCCH in slot #(n1+K1). Here, the UCI may include a HARQ-ACK response to the PDSCH. Figure 6 In the example, for convenience, it is assumed that the SCS of the PDSCH and the SCS of the PUCCH are the same, and it is assumed that slot #n1=slot #n+K0, but the present disclosure is not limited thereto. If the SCSs are different, K1 may be indicated / interpreted based on the SCS of the PUCCH.

[0113] If the PDSCH is configured to transmit up to 1 TB, the HARQ-ACK response may be configured with 1 bit. When the PDSCH is configured to transmit up to 2 TB, the HARQ-ACK response may be configured with 2 bits when spatial bundling is not configured, and the HARQ-ACK response may be configured with 1 bit when spatial bundling is configured. When the HARQ-ACK transmission time of multiple PDSCHs is specified as time slot #(n+K1), the UCI transmitted in time slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0114] Whether the UE should perform spatial bundling for the HARQ-ACK response can be configured for each cell group (e.g., RRC / higher layer signaling). As an example, spatial bundling can be configured separately in each of the HARQ-ACK responses sent via the PUCCH and / or the HARQ-ACK responses sent via the PUSCH.

[0115] When the maximum number of TBs (or codewords) that can be received at one time (or can be scheduled by one DCI) in the corresponding serving cell is two (or two or more) (for example, when the high-level parameter maxNrofCodeWordsScheduledByDCI is 2-TB), spatial bundling can be supported. In addition, a number of layers greater than four can be used for 2-TB transmission, and a maximum of four layers can be used for 1-TB transmission. As a result, when spatial bundling is configured in the corresponding cell group, spatial bundling can be performed on the serving cells in the corresponding cell group that can schedule more than four layers. On the corresponding serving cell, a UE that expects to send a HARQ-ACK response through spatial bundling can generate a HARQ-ACK response by performing a (bit-by-bit) logical AND operation on the A / N bits of multiple TBs.

[0116] For example, assuming that a UE receives DCI for scheduling 2-TB and receives 2-TB via PDSCH based on the DCI, the UE performing spatial bundling can generate a single A / N bit by performing a logical AND operation on the first A / N bit of the first TB and the second A / N bit of the second TB. As a result, when both the first TB and the second TB are ACK, the UE reports the ACK bit value to the base station, and when either TB is NACK, the UE reports the NACK bit value to the base station.

[0117] For example, if only 1-TB is actually scheduled on a serving cell configured to allow reception of 2-TB, the UE may generate a single A / N bit by performing a logical AND operation on the A / N bits corresponding to 1-TB and a bit value of 1.

[0118] Multiple parallel DL HARQ processes exist for DL ​​transmissions in the base station / UE. Multiple parallel HARQ processes allow DL transmissions to continue while waiting for HARQ feedback regarding the successful or unsuccessful reception of previous DL transmissions. Each HARQ process is associated with a HARQ buffer at the MAC (Medium Access Control) layer. Each DL HARQ process manages state variables related to the number of MAC (physical data blocks) transmitted in the buffer, HARQ feedback for the MAC in the buffer, and the current redundancy version. Each HARQ process is identified by a HARQ process ID.

[0119] Figure 7 The PUSCH (Physical Uplink Shared Channel) transmission process is illustrated. Figure 7 , the UE can detect the PDCCH in time slot #n. Here, the PDCCH includes uplink scheduling information (e.g., DCI formats 0_0, 0_1). DCI formats 0_0 and 0_1 can include the following information.

[0120] - Frequency domain resource assignment: indicates the set of RBs allocated to PUSCH

[0121] -Time domain resource assignment: Indicates the slot offset K2, the starting position (e.g., symbol index) and length (e.g., number of OFDM symbols) of the PUSCH in the slot. The starting symbol and length can be indicated by the start and length indicator value (SLIV), or can be indicated separately.

[0122] Thereafter, the UE may send the PUSCH in time slot #(n+K2) according to the scheduling information of time slot #n.

[0123] Figure 8 This figure illustrates an example of multiplexing UCI onto PUSCH. When multiple PUCCH and PUSCH resources overlap within a slot and simultaneous PUCCH-PUSCH transmission is not configured, UCI can be transmitted via PUSCH as shown (UCI piggyback or PUSCH piggyback). Figure 8 This example illustrates the case where HARQ-ACK and CSI are carried on PUSCH resources.

[0124] Figure 9 This document illustrates a wireless communication system that supports an unlicensed frequency band. For convenience, a cell operating in a licensed frequency band (hereinafter referred to as the L-band) is defined as an Lcell, and the carrier of the Lcell is defined as a (DL / UL) licensed component carrier (LCC). Furthermore, a cell operating in an unlicensed frequency band (hereinafter referred to as the U-band) is defined as a UCell, and the carrier of the UCell is defined as a (DL / UL) unlicensed component carrier (UCC). The carrier of a cell may represent the operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., component carrier CC) may be referred to as a cell.

[0125] When carrier aggregation (CA) is supported, a UE can send and receive signals to and from a base station through multiple aggregated cells and carriers. When multiple CCs are configured for a UE, one CC can be configured as a PCC (primary CC) and the remaining CCs can be configured as SCCs (secondary CCs). Specific control information and channels (e.g., CSS PDCCH, PUCCH) can be configured to be sent and received only through the PCC. Data can be sent and received through the PCC and SCCs. Figure 9(a) illustrates a case where a UE and a base station transmit and receive signals using an LCC and a UCC (non-standalone (NSA) mode). In this case, the LCC can be configured as a PCC, and the UCC can be configured as an SCC. When multiple LCCs are configured in a UE, one specific LCC can be configured as a PCC, and the remaining LCCs can be configured as SCCs. Figure 9 (a) corresponds to LAA of the 3GPP LTE system. Figure 9 (b) illustrates a case where the UE and the base station transmit and receive signals (standalone mode (SA)) through one or more UCCs without any LCC. In this case, one of the UCCs can be configured as a PCC, and the other UCCs can be configured as SCCs. Therefore, PUCCH, PUSCH, PRACH transmission, etc. can be supported in the NRUCell. In the unlicensed band of the 3GPP NR system, both NSA mode and SA mode can be supported.

[0126] Figure 10 A method for occupying resources in an unlicensed band is illustrated. According to regional regulations regarding unlicensed bands, communication nodes in an unlicensed band should determine whether other communication nodes are using the channel before transmitting a signal. Specifically, a communication node can perform CS (carrier sense) before sending a signal to check whether other communication nodes are sending signals. The situation where it is determined that other communication nodes are not sending signals is defined as CCA (clear channel assessment) being confirmed. If there is a predefined CCA threshold or CCA threshold configured by higher-layer (e.g., RRC) signaling, if energy above the CCA threshold is detected in the channel, the communication node determines the channel state as busy, otherwise the channel state can be considered idle. For example, in the Wi-Fi standard (802.11ac), the CCA threshold is defined as -62dBm for non-Wi-Fi signals and -82dBm for Wi-Fi signals. If the channel state is determined to be idle, the communication node can start sending signals in the UCell. The above series of processes can be referred to as listen-before-talk (LBT) or channel access procedure (CAP). LBT and CAP may be equivalent.

[0127] In Europe, two LBT operations are exemplified as FBE (Frame-Based Equipment) and LBE (Load-Based Equipment). In FBE, a fixed frame includes a channel occupancy time (e.g., 1 to 10 ms) indicating the time during which a communication node can continue to transmit when the communication node successfully accesses the channel, and an idle period corresponding to at least 5% of the channel occupancy time, and CCA is defined as an operation of observing the channel during a CCA time slot (at least 20 μs) at the end of the idle period. The communication node periodically performs CCA in fixed frame units, and when the channel is not occupied, it transmits data during the channel occupancy time, and when the channel is occupied, it waits until the CCA time slot of the next period.

[0128] On the other hand, in the case of LBE, the communication node first configures the value of q∈{4, 5, ···, 32} and then performs CCA for one CCA slot. When the channel is not occupied in the first CCA slot, data can be transmitted by ensuring a maximum time of (13 / 32)qms. If the channel is occupied in the first CCA slot, the communication node randomly selects the value of N∈{1, 2, ···, q} and stores it as the initial value of the counter. Then, while detecting the channel state in units of CCA slots, when the channel is not occupied in the unit of CCA slots, the value stored in the counter is decremented by 1. When the counter value becomes 0, the communication node can transmit data by ensuring a maximum time of (13 / 32)qms.

[0129] Specifically, multiple CAP types (i.e., LBT types) may be defined for uplink transmission in an unlicensed band. For example, a Type 1 or Type 2 CAP may be defined for uplink transmission. The UE may execute the CAP (e.g., Type 1 or Type 2) configured / indicated by the base station for uplink transmission.

[0130] (1) Type 1 Uplink CAP Method

[0131] Figure 11 A flow chart illustrating Type 1 CAP operations of a UE for uplink signal transmission is shown.

[0132] The UE may initiate a CAP for signal transmission via an unlicensed band (S1510). The UE may arbitrarily select a backoff counter N within a contention window (CW) according to step 1. Here, the value of N is configured as an initial value N init (S1520). N init Selected as 0 and CW pany value between . Then, according to step 4, if the backoff counter value (N) is 0 (S1530; Yes), the UE ends the CAP process (S1532). Thereafter, the UE may perform Tx burst transmission (S1534). On the other hand, if the backoff counter value is not 0 (S1530; No), the UE reduces the backoff counter value by 1 according to step 2 (S1540). Thereafter, the UE checks whether the channel of the Ucell is in an idle state (S1550), and if the channel is in an idle state (S1550; Yes), it checks whether the backoff counter value is 0 (S1530). On the other hand, if the channel is not in an idle state in step S1550, that is, if the channel is in a busy state (S1550; No), the UE checks whether the corresponding channel is in an idle state for a delay period (delay duration Td; 25 milliseconds or more) longer than the slot time (e.g., 9 us) according to step 5 (S1560). If the channel is in an idle state during the delay period (S1570; Yes), the UE may resume the CAP process again. Here, the delay period may include a 16 millisecond period and the m p On the other hand, if the channel is in a busy state during the delay period (S1570; No), the UE re-executes step S1560 to check again whether the channel is in an idle state during the new delay period.

[0133] Table 6 shows the m applied to CAP according to the channel access priority category. p 、Minimum CW(CW min,p )、Maximum CW(CW max,p ), Maximum Channel Occupancy Time (MCOT, T ulmcot,p )).

[0134] [Table 6]

[0135]

[0136] The CW size (CWS) applied to the Type 1 CAP may be determined based on various methods. As an example, the CWS may be adjusted based on whether a new data indicator (NDI) value of at least one HARQ processor associated with HARQ_ID_ref is switched, where HARQ_ID_ref is a HARQ process ID of a UL-SCH within a predetermined duration (e.g., a reference TU). When a UE performs signal transmission using a Type 1 CAP associated with a channel access priority category P on a carrier, if the NDI value of at least one HARQ process associated with HARQ_ID_ref is switched, the UE sets the CWS in all priority categories p∈{1,2,3,4}. p =CW min,p, and if not, the UE will CW p Increase to the next higher allowed value among all priority classes p∈{1,2,3,4}.

[0137] Reference subframe n ref (or reference time slot n ref ) is determined as follows.

[0138] When the UE is in subframe (or time slot) n g Receive UL grant in subframe (or time slot) n0, n1, ..., n and perform transmission including UL-SCH without w When the gap starts from subframe (or time slot) n0 in the ref It is subframe (or time slot) n0.

[0139] (2) Type 2 Uplink CAP Method

[0140] If the channel is sensed to be at least within the sensing period T short_ul = 25 us, the UE can perform uplink transmission (eg, PUSCH) in the unlicensed band immediately after sensing is terminated. short_ul Can include T sl (=9us)+T f (=16us).

[0141] Implementation: HARQ-ACK feedback in U-band

[0142] In order to support independent operation in the U-band, for DL ​​data (e.g., PDSCH) reception, a HARQ-ACK feedback operation based on the U-band PUCCH / PUSCH transmission of the UE may be necessary (hereinafter, for convenience, HARQ-ACK is referred to as A / N). PUCCH / PUSCH indicates PUCCH or PUSCH. For example, a process in which a base station schedules DL data transmission to a UE by ensuring a channel occupancy time (CoT) duration by performing an LBT (CCA) operation and the base station indicates that HARQ-ACK feedback for corresponding DL data reception is sent from the corresponding UE through the same COT duration may be considered (hereinafter, for convenience, LBT or CCA is referred to as LBT). As another example, due to the UE processing time involved in decoding the DL data and encoding the corresponding HARQ-ACK signal for the reception of DL data scheduled / sent through a specific COT duration, it may be considered to indicate a process for sending HARQ-ACK feedback through another COT duration after the corresponding COT duration.

[0143] Hereinafter, in the present disclosure, a HARQ-ACK feedback (hereinafter, A / N) configuration / transmission method in the U-band is proposed. Here, the A / N configuration / transmission method can be performed considering LBT operation, COT configuration, etc. The method proposed in the present disclosure is not limited to the HARQ-ACK feedback transmission method through PUCCH / PUSCH, and can be similarly applied to other UCI (e.g., CSI, SR) transmission methods through PUCCH / PUSCH. In addition, the method proposed in the present disclosure is not limited to U-band operation based on LBT, and can be similarly applied to L-band (or U-band) operation not accompanied by LBT. In addition, in the following description, multiple CC (indexes) are replaced with multiple BWPs (indexes) configured in one (or more) CC / (service) cell or multiple CC / (service) cells including multiple BWPs (i.e., a combination of CC (index) and BWP (index)).

[0144] First, the following terms are defined.

[0145] -UCI: Indicates control information sent by the UE in the UL. UCI includes several types of control information (i.e., UCI types). For example, UCI includes HARQ-ACK, SR, and CSI.

[0146] -HARQ-ACK: Indicates whether the DL data (e.g., transport block (TB), codeword (CW)) on the PDSCH has been successfully received. A 1-bit HARQ-ACK can be sent in response to a single DL data. A 2-bit HARQ-ACK can be sent in response to two DL data. The HARQ-ACK response / result includes positive ACK (ACK), negative ACK (NACK), DTX, or NACK / DTX. Here, HARQ-ACK is equivalent to AMACK / NACK, A / N, and AN.

[0147] -HARQ process number / ID: indicates the number or identifier of the HARQ process. The HARQ process manages state variables related to the number of MAC PDU transmissions in the buffer, HARQ feedback of MAC PDUs in the buffer, and the current redundancy version.

[0148] -PUCCH: represents the physical layer UL channel used for UCI transmission. For convenience, for A / N, SR and CSI transmission, the PUCCH resources configured and / or indicated by the base station for transmission are respectively referred to as A / N PUCCH resources, SR PUCCH resources and CSI PUCCH resources.

[0149] -PUSCH: indicates a physical layer UL channel used for UL data transmission.

[0150] -Slot: represents the basic time unit (TU) (or time interval) used for data scheduling. A slot includes multiple symbols. Here, a symbol includes an OFDM-based symbol (e.g., CP-OFDM symbol, DFT-s-OFDM symbol). In the present disclosure, the terms symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol, and DFT-s-OFDM symbol may be used interchangeably.

[0151] Each of the proposed methods described below can be combined and applied together as long as they do not contradict each other.

[0152] (1) Basic operation method

[0153] The basic operation method for the A / N feedback configuration / transmission method proposed in the present disclosure is described as follows. In the present disclosure, the A / N triggering DCI includes at least DL grant DCI and (in addition to the DL grant DCI) may also include UL grant DCI and / or special DCI that does not schedule PDSCH / PUSCH transmission.

[0154] 1) Timing-based A / N feedback method (hereinafter, tA / N method) Figure 12 )

[0155] A. After configuring multiple candidate HARQ timings in advance via RRC signaling, the base station can indicate one of the multiple candidate HARQ timings to the UE via (DL grant) DCI. In this case, the UE can operate to send A / N feedback for (multiple) PDSCH receptions using HARQ timings in multiple time slots (or time slot sets; for convenience, bundling windows) corresponding to all candidate HARQ timing sets. Here, HARQ timing refers to PDSCH to A / N timing / interval. HARQ timing can be expressed in units of time slots.

[0156] For example, when A / N transmission is indicated in slot #m, the A / N information may include response information for PDSCH reception in slot #(mi).Here, slot #(mi) corresponds to the slot corresponding to the candidate HARQ timing. Figure 12 (a) illustrates a case where the candidate HARQ timing is configured as i = {2, 3, 4, 5}. In this case, when the A / N transmission time is indicated as #(n+5) (=m), the UE can generate and transmit A / N information for PDSCH reception of slots #n to #(n+3) (=mi) (i.e., A / N feedback for all four slots). Here, the A / N response to PDSCH reception of slots #n+1 / #n+3 can be regarded as a NACK.

[0157] For convenience, this A / N feedback configuration / transmission method is referred to as a "Type 1 A / N codebook".

[0158] B. In addition to the HARQ timing indication, a counter downlink assignment index (c-DAI) and / or a total DAI (t-DAI) may be signaled together via the (DL grant) DCI. The c-DAI may notify in which order the PDSCH corresponding to the (DL grant) DCI is scheduled. The t-DAI may notify the total number of PDSCHs scheduled up to the current (time slot) (or the total number of time slots in which PDSCHs are present). Thus, the UE may operate to send the A / N of the PDSCH corresponding to the c-DAI values ​​from the initial c-DAI value to the (received) last t-DAI value via the indicated HARQ timing. When the number of serving cells configured for the UE is 1, c-DAI and t-DAI may have the same meaning. Therefore, t-DAI may be included in the (DL grant) DCI only when the number of serving cells is plural. When multiple service cells are configured in the UE, c-DAI is first counted in a small area, and then c-DAI can notify the scheduling order of PDSCH counted in the time domain (or the order of (service cells, time slots) in which PDSCH exists). Similarly, t-DAI can notify the total number of PDSCHs scheduled until the current (time slot) (or the total number of time slots in which PDSCH exists, the total number of service cells). Here, c-DAI / t-DAI can be defined based on PDCCH. In this case, in the above description, PDSCH can be replaced with PDCCH, and the time slot in which PDCCH exists can be replaced by a PDCCH monitoring opportunity in which PDCCH (or DCI) related to PDCCH exists.

[0159] Each c-DAI / t-DAI may be indicated using a 2-bit value. Modular arithmetic may be used to indicate numbers greater than 4 as follows.

[0160] - When the DAI bits are 00 (eg, DAI value = 1): indicates 4n+1 (ie, 1, 5, 9, ...).

[0161] - When the DAI bits are 01 (eg, DAI value = 2): indicates 4n+2 (ie, 2, 6, 10, ...).

[0162] - When the DAI bit is 10 (eg, DAI value = 3): indicates 4n+3 (ie, 3, 7, 11, ...).

[0163] - When the DAI bit is 11 (eg, DAI value = 4): indicates 4n+4 (ie, 4, 8, 12, ...).

[0164] *n represents an integer greater than or equal to 0.

[0165] Figure 12 (b) illustrates the Figure 12 (a) The same case as (DL authorization) DCI signaling DAI. Figure 12 (b) of the present invention, a PDSCH scheduled by a DCI with DAI=00 in slot #n may be received, and a PDSCH scheduled by a DCI with DAI=10 in slot #(n+2) may be received. In this case, the UE may generate / transmit only A / N information for receiving three PDSCHs corresponding to consecutive DAI values ​​(i.e., DAI=00 / 01 / 11) (hereinafter, a DAI sequence). Here, an A / N response for receiving a PDSCH corresponding to DAI=01 may be processed as a NACK.

[0166] 2) A / N feedback method based on pooling (hereinafter, pA / N method) Figure 13 )

[0167] A. The operation of delaying (pending / postponing) the transmission of A / N feedback for the corresponding PDSCH may be indicated by a DL grant DCI. Subsequently, the transmission (pooling) of A / N feedback for PDSCHs corresponding to (i) all DL HARQ process IDs or (ii) a specific portion of DL HARQ process IDs may be indicated by DCI. A / N feedback may be sent at a timing configured / indicated based on a specific signal (e.g., RRC or DCI signaling). A / N pooling may be indicated by a DL grant (e.g., DCI format 1_0 / 1_1), an UL grant (e.g., DCI format 0_0 / 0_1), or other DCI (e.g., UE (group) common DCI). For convenience, DCI indicating A / N pooling is referred to as pooling DCI. The HARQ process IDs to be pooled may be preconfigured / predefined or may be indicated by pooling DCI. A / N pooling may be indicated per all / group / individual HARQ process ID.

[0168] For example, refer to Figure 13 , the UE can receive three PDSCHs from the base station, and the HARQ process ID (HpID) assigned to each PDSCH can be 0, 3, and 2. In addition, the A / N of the three PDSCHs can be indicated by each DL grant DCI (AN=pe). In this case, the UE delays the transmission of the A / N corresponding to the PDSCH reception of HpID=0 / 3 / 2. Thereafter, upon receiving the pooled DCI (AN=pooled) from the base station, the UE can transmit the A / N corresponding to the PDSCH reception of all or some HpIDs at once.

[0169] B. When c / t-DAI signaling is configured with the tA / N method (e.g., when DAI is signaled via DL grant DCI), A / N pooling corresponds to the HARQ process ID (indicated by pooling DCI), which can be defined as pooled A / N transmission of the PDSCH corresponding to the HARQ process ID, or pooled A / N transmission of the PDSCH corresponding to the t-DAI value (indicated by pooling DCI). In the latter case, the UE can transmit A / N information received on the PDSCH corresponding to the c-DAI initial value to the t-DAI value at one time.

[0170] (2) Proposed method 1

[0171] In the case of the proposed method 1, through A / N triggering DCI, 1) timing A indicating actual A / N transmission timing, and 2) timing D indicating reference A / N timing corresponding to the (DL PDSCH) slot group as the A / N feedback target may be signaled.

[0172] Based on this, the UE may operate to transmit A / N feedback for a slot group (received through the PDSCH of the slot group) corresponding to timing D to the time indicated by timing A. In this case, the A / N payload may be mapped (e.g., sorted) in the slot index order belonging to the corresponding slot group.

[0173] For example, an A / N trigger DCI may be sent / detected via slot #n (or, if the A / N trigger DCI is a DL grant DCI, the corresponding PDSCH), and timing A=K and timing D=L may be indicated via the corresponding DCI. In this case, the UE may operate to send A / N feedback for a slot group corresponding to slot #(n+KL) to slot #(n+K) (i.e., received via the PDSCH for the slot group). Here, a slot group may be defined as a timing set including multiple (e.g., M) candidate timing values ​​D_m (m=0, 1, . . . , M-1). For example, a slot group corresponding to slot #n may be configured / defined as M slots corresponding to slot #(n-D_m) or slot #(n+D_m) (m=0, 1, . . . , M-1). In this case, the time slot group corresponding to time slot #(n+KL) can be configured / defined as time slot #(n+KL-Dm) or time slot #(n+K-L+D_m) (m=0, 1,..., M-1).

[0174] On the other hand, the timing set defining the time slot group can be configured to be the same as the set of candidate timing A values ​​that can be indicated by timing A (e.g., K_m; m=0, 1, ···, M-1), or can be configured independently (differently). For example, the bundling window corresponding to time slot #n can be configured as time slot #(n-K_m), and the time slot group corresponding to time slot #n can also be defined by a timing set configured with K_m (m=0, 1, ···, M-1). For example, A / N triggering DCI (or, when the A / N triggering DCI is a DL authorization DCI, the corresponding PDSCH) can be sent / detected through time slot #n, and timing A=K and timing D=L can be indicated by the corresponding DCI. In this case, the UE can operate to send A / N feedback for the time slot group corresponding to time slot #(n+K) to time slot #(n+KL) (received through the PDSCH of the time slot group). Here, a slot group corresponding to slot #(n+KL) may be configured with slot #(n+K-(K_m+L)) (m=0, 1,..., M-1).

[0175] On the other hand, when the A / N triggering DCI is the same as the DL grant DCI (i.e., both timing A and timing D are signaled by the DL grant DCI), the UE can operate to send (simultaneously, for example, via one PUCCH / PUSCH) by combining 1) A / N feedback for the bundling window corresponding to timing A (received via PDSCH of the bundling window) and 2) A / N feedback for the time slot group corresponding to timing D to the time indicated by timing A (received via PDSCH of the time slot group).

[0176] For example, when a DL grant DCI or a corresponding PDSCH is transmitted / detected through time slot #n and timing A=K and timing D=L are indicated through the corresponding DCI, the UE may operate to transmit by combining 1) A / N feedback of a bundling window corresponding to time slot #(n+K) (received through the PDSCH of the bundling window) and 2) A / N feedback of a time slot group corresponding to time slot #(n+KL) to time slot #(n+K) (received through the PDSCH of the time slot group). Here, the time slot group corresponding to time slot #(n+KL) may be configured / defined as (i) time slot #(n+KL-Dm) or time slot #(n+K-L+D_m) (m=0, 1, ···, M-1), or (ii) time slot #(n+K-(K_m+L)) (m=0, 1, ···, M-1).

[0177] In addition, (for example, when the A / N trigger DCI is the same as the DL grant DCI), the DCI may indicate the absence of the timing D and / or the corresponding time slot group (for which the A / N feedback request is requested). For example, when the timing D = a specific value (for example, 0) is configured, it may indicate the absence of the corresponding time slot group (for which the A / N feedback request is requested).

[0178] In addition, (for example, when the A / N triggering DCI is the same as the DL authorization DCI), it can be indicated by DCI (for example, by the timing D indication field): A / N feedback is sent only for a specific part of the time slots (for example, the first time slot or the last time slot) belonging to the bundling window corresponding to timing A (or the time slot group corresponding to timing D).

[0179] As another method, a method of signaling the trigger timing A / timing D and the A / N feedback transmission trigger corresponding to the corresponding time slot group (eg, bundling window) through UE (group) common DCI may also be considered.

[0180] In addition, due to the limited DCI field size / bit number, the reference A / N timing (corresponding A / N feedback target time slot group) that can be indicated by the timing D can be limited. Taking this into account, it can be indicated that A / N feedback for PDSCH reception corresponding to all (not a specific time slot group) or some (pre-specified) specific HARQ process IDs is sent through a specific state of the timing D indication field.

[0181] In addition, for each timing D value, the A / N transmission PUCCH / PUSCH resource (set) can be configured differently. For example, for each time slot group corresponding to each timing D value, the A / N transmission PUCCH / PUSCH resource (set) can be configured differently. In addition, the corresponding timing D value for each A / N transmission PUCCH / PUSCH resource (set) can be configured differently (for example, corresponding to the A / N feedback target time slot group to the corresponding PUCCH / PUSCH resource (set)). For example, the time slot group corresponding to each PUCCH / PUSCH resource (set) can be configured differently, and therefore, the timing D value can be configured differently.

[0182] (3) Proposed method 2

[0183] In the case of the proposed method 2, when a time slot group size (e.g., the number N of time slots in a single time slot group or the maximum number N of schedulable PDSCHs in a single time slot group) is pre-configured, 1) a current ID (c-ID) indicating the time slot group ID to which the time slot in which the corresponding DCI or the corresponding PDSCH is transmitted belongs may be signaled through DL grant DCI, and 2) a feedback ID (f-ID) indicating the time slot group ID to be the A / N feedback target (DL PDSCH) may be signaled through A / N trigger DCI.

[0184] Based on this, the UE can transmit A / N feedback for a slot group corresponding to the feedback ID (received via the PDSCH of the slot group) at a time (e.g., slot) indicated as the A / N transmission timing. Here, the slot group corresponding to the feedback ID includes slots in which the current ID having the same value as the previous feedback ID is signaled / received, that is, slots in which the current ID having the same value as the previous feedback ID is signaled / received via the DL grant DCI.

[0185] Here, for the A / N payload of the time slot group corresponding to the feedback ID (in the case where the counter DAI is configured to be signaled through the DL grant DCI), it can be mapped (sorted) in the order of the counter DAI values ​​received through the DL grant DCI (e.g., from 1 to N).

[0186] For example, refer to Figure 14 , the A / N triggering DCI (or, when the A / N triggering DCI is a DL grant DCI, the corresponding PDSCH) may be transmitted / detected through slot #n, and the timing A(TA)=K and the feedback ID (f-ID)=X may be indicated through the corresponding DCI. In this case, the UE may transmit, in slot #(n+K), A / N feedback received for the PDSCH in the slot group corresponding to the slot group ID=X (i.e., received as the current ID (c-ID)=X through the DL grant DCI) .

[0187] Furthermore, the counter DAI may be determined / signaled to have consecutive values ​​(starting from an initial value (eg, 1)) in one slot group (ID), as shown in FIG. Figure 12 As shown in (b). That is, the counter DAI value can be determined / signaled independently between different time slot groups. In addition, the time slot group can be defined in the form of a DAI sequence including counter DAI values ​​from 1 to N corresponding to the same time slot group ID value (indicated by DCI). In this case, the time slot group can be configured as discontinuous time slots based on the received / detected counter DAI. In the present disclosure, the time slot group ID and the DAI sequence ID can be replaced / compatible with each other.

[0188] On the other hand, when the A / N triggering DCI is the same as the DL grant DCI (i.e., both the current ID and the feedback ID are signaled through the DL grant DCI), the UE can operate to send (simultaneously, for example, through one PUCCH / PUSCH) by combining (e.g., cascading) 1) the A / N feedback of the bundling window corresponding to timing A or the time slot group corresponding to the current ID (received through the PDSCH of the time slot group) and 2) the A / N feedback of the time slot group corresponding to the feedback ID (received through the PDSCH of the time slot group) at the time indicated by timing A.

[0189] In addition, in the present disclosure, signaling / indicating a feedback ID through an A / N trigger DCI (e.g., DL grant DCI, UL grant DCI) may mean that the total number of (PDSCH) slot groups (IDs) targeted for A / N feedback transmission / request is signaled through the corresponding DCI, and a specific slot group ID determined based on the total ID and the current ID is applied as the feedback ID. For example, in the case where up to two (PDSCH) slot group IDs are set / configured (e.g., ID=0 or ID=1), when the current ID is indicated as X and the total ID is indicated as 1, the feedback ID may be determined / applied as X (which is the same value as the current ID). As another example, in the case where up to two (PDSCH) slot group IDs are set / configured (e.g., ID=0 or ID=1), the current ID is indicated as X and the total ID is indicated as 2, and the feedback ID may be determined / applied as Y (which is a different value from the current ID). In this case, X and Y may be determined as different values ​​(eg, if X=0, then Y=1, or if X=1, then Y=0). For convenience, this method of determining the feedback ID is referred to as "Method 1".

[0190] For example, a DL grant DCI or corresponding PDSCH may be sent / detected via slot #n and may indicate timing A=K, current ID=X, and feedback ID=Y (or total ID=2). In this case, the UE may transmit by combining 1) the A / N feedback of the bundling window corresponding to slot #(n+K) or the slot group corresponding to ID=x (received via the PDSCH of the slot group) and 2) the A / N feedback of the slot group corresponding to ID=Y (received via the PDSCH of the slot group) via slot #(n+K).

[0191] On the other hand, in the present disclosure, the total DAI and / or NFI (new feedback indicator) of the feedback ID (and its corresponding (PDSCH) time slot group) signaled / indicated by the A / N trigger DCI (e.g., DL grant DCI, UL grant DCI) can represent the total DAI and / or NFI for the feedback ID determined according to method 1, or the total DAI and / or NFI for other IDs (corresponding to their time slot groups) having values ​​different from the current ID (regardless of the value indicated as the total ID). As an example of the latter, in the case of setting / configuring up to two (PDSCH) time slot group IDs (e.g., ID=0 or ID=1), when the current ID=X is indicated, the "total DAI and / or NFI for the feedback ID" can represent the total DAI and / or NFI for the time slot group corresponding to the other ID=Y. In this case, X and Y can be determined as different values ​​(e.g., if X=0, then Y=1, or if X=1, then Y=0). For convenience, this method of determining other IDs and applying the total DAI / NFI is referred to as "method 2".

[0192] Here, NFI is 1-bit information for A / N feedback transmitted at a previous (e.g., most recently) time (hereinafter, previous A / N feedback), and indicates (a) whether the base station has correctly detected / received it, or (b) whether the base station has failed to detect / receive it. In case (a), the UE can process the remaining portion, except for the A / N corresponding to the PDSCH scheduled after the previous A / N transmission, as NACK or DTX (Feedback Configuration / Transmission Omission) to configure / transmit updated A / N feedback. In case (b), the UE can configure / transmit A / N feedback by maintaining the remaining portion, except for the A / N corresponding to the PDSCH scheduled after the previous A / N transmission. In case (a), the NFI value switched from the NFI value received via the previous DCI is indicated by the current DCI. In case (b), the NFI value that has not been switched from the NFI value received via the previous DCI can be indicated by the current DCI.

[0193] For example, by sending / detecting DL authorization DCI or the corresponding PDSCH through time slot #n, and indicating timing A=K, current ID=X and feedback ID=Y (or total ID value=2) respectively through the corresponding DCI, the UE can send by combining 1) the bundling window corresponding to time slot #(n+K) or the A / N feedback corresponding to the time slot group with ID=X (received through the PDSCH of the time slot group) and 2) the A / N feedback corresponding to the time slot group with ID=Y (received through the PDSCH of the time slot group) through time slot #(n+K).

[0194] In addition, (for example, when the A / N trigger DCI is the same as the DL grant DCI), the DCI may indicate (via the feedback ID (or total ID) indication field) that there is no corresponding feedback ID (or other ID) and / or time slot group (A / N feedback request on the time slot group). For example, when the feedback ID is indicated with the same value as the current ID (or the total ID value is 1), the UE may be operable to configure / send A / N feedback only for the (one) time slot group corresponding to the current ID.

[0195] In addition, (for example, when the A / N triggering DCI is the same as the DL authorization DCI), it can be indicated by DCI (for example, by the feedback ID (or total ID) indication field): A / N feedback is sent only for a specific part (for example, the first time slot or the last time slot) of the time slots belonging to the bundling window corresponding to timing A or the time slot group corresponding to the current ID (or the time slot group corresponding to the feedback ID (or other ID)).

[0196] As another method, a method of signaling the current ID through UE (group)-common DCI #1 and / or signaling the A / N feedback transmission trigger for the feedback ID and the corresponding time slot group through UE (group)-common DCI #2 can be considered. In this case, UE (group)-common DCI #1 and #2 can be separate DCIs or can be configured as the same DCI.

[0197] In another method, the total DAI is signaled by A / N triggering DCI, and the UE can operate to configure / send A / N feedback only for the counter DAI value from (1 to) the total DAI value for the time slot group corresponding to the feedback ID (or the bundling window corresponding to timing A or the time slot group corresponding to the current ID). That is, it can be configured / sent only for the time slot corresponding to the counter DAI value from 1 to the total DAI value (PDSCH scheduled by this). Alternatively, the total DAI of the time slot group corresponding to the feedback ID (or other ID) and the time slot group corresponding to the current ID (or the bundling window corresponding to timing A) can be signaled separately by DCI. In this case, the UE can operate to configure / send A / N feedback based on the total DAI of each time slot group.

[0198] As an example, the A / N feedback configuration-related information indicated by the DL grant DCI may include (i) the current ID, (ii) the counter / total DAI of the time slot group corresponding to the current ID (PDSCH scheduled by this), and (iii) the feedback ID (or total ID). In addition, the total DAI of the time slot group corresponding to the feedback ID (or other ID) (PDSCH scheduled by this) may be further included in the DL grant DCI (i.e., the A / N feedback configuration-related information).

[0199] On the other hand, (i) the current ID, (ii) the total DAI for the time slot group corresponding to the current ID (through the PDSCH scheduled by this), (iii) the feedback ID (or total ID), and (iv) the total DAI for the time slot group corresponding to the feedback ID (or other ID) can be indicated by the UL grant DCI. Here, the current ID and the feedback ID can be defined / generalized as two feedback IDs #1 and #2. Therefore, the UE can operate to send A / N feedback for the time slot group corresponding to feedback IDs #1 and #2 via (PUCCH or) PUSCH (e.g., in the form of UCI piggybacking).

[0200] Alternatively, the current ID (and / or feedback ID (or total ID)) may not be included in the UL grant DCI. That is, signaling via the UL grant DCI may be omitted for the current ID (and / or feedback ID (or total ID)). In this case, the UE may operate to configure / send A / N feedback (on the PUSCH) based on the current ID (and / or feedback ID (or total ID)) information received via the DL grant DCI. In addition, a specific field may be used to indicate that there is no A / N feedback transmission request (e.g., for a timeslot group targeted for A / N feedback) via the UL grant DCI. Here, the specific field may include, for example, a feedback ID (or total ID) and / or current ID (and / or feedback ID (or other ID) and / or total DAI corresponding to the current ID) indication field.

[0201] As another method, the current ID and the starting ID can be indicated by an A / N triggering DCI (e.g., DL grant DCI, UL grant DCI). In this case, the UE can be operated to configure / transmit A / N feedback for the time slot group set A corresponding to (multiple) consecutive time slot group IDs from the starting ID to the current ID (received via its PDSCH). When the starting ID is indicated with the same value as the current ID, the UE can be operated to configure / transmit A / N feedback only for the (one) time slot group corresponding to the current ID. Here, the current ID can be defined / generalized as the ending ID.

[0202] As an example, the A / N feedback configuration-related information indicated by the DL grant DCI may include (i) the current ID, (ii) the time slot group corresponding to the current ID (PDSCH scheduled by this), and (iii) the starting ID. In addition, the (single) total DAI commonly applied to each (multiple) time slot group belonging to the time slot group set A (excluding the time slot group corresponding to the current ID) may also be included in the DL grant DCI (i.e., the A / N feedback configuration-related information).

[0203] As another example, the UL grant DCI may indicate (i) the current ID, (ii) the total DAI for the slot group corresponding to the current ID (via the PDSCH scheduled for this), (iii) the starting ID, and (iv) the (single) total DAI commonly applied to each (multiple) slot group belonging to the slot group set A (excluding the slot group corresponding to the current ID). Thus, the UE may be operable to transmit A / N feedback for the slot group set corresponding to the starting ID to the current ID via (PUCCH or) PUSCH (e.g., in the form of UCI piggybacking).

[0204] As another example, the current ID (and / or starting ID) may not be included in the UL grant DCI. That is, the signaling for the current ID (and / or starting ID) via the UL grant DCI may be omitted. In this case, the UE may operate to configure / send A / N feedback (on the PUSCH) based on the current ID (and / or starting ID) information received via the DL grant DCI. In addition, a specific field may be used to indicate that there is no A / N feedback transmission request via the UL grant DCI (e.g., for a timeslot group targeted for A / N feedback). Here, the specific field may include, for example, a starting ID and / or current ID (and / or corresponding total DAI) indication field.

[0205] On the other hand, when applying the above method or other methods, the number of (single) A / N feedback configuration target time slot groups transmitted simultaneously can be dynamically changed (for example, 2 including the current ID, or 3 or more including the current ID). In this case, the (single) total DAI commonly applied to each of the multiple time slot groups targeted for the A / N feedback configuration (excluding the time slot group corresponding to the current ID) can be indicated through the A / N trigger DCI (for example, DL grant DCI) and / or UL grant DCI.

[0206] On the other hand, due to the limited DCI field size / bit count, there may be restrictions on the time slot group IDs (corresponding to the A / N feedback target time slot group) that can be indicated by the current ID / feedback ID (or total ID). With this in mind, the current ID / feedback ID (or total ID) indicates a specific state of the field, indicating that A / N feedback for PDSCH reception corresponding to all (not a specific time slot group) or some (pre-specified) specific HARQ process IDs should be sent.

[0207] On the other hand, for each slot group ID value (for the slot group corresponding to the corresponding ID), the A / N transmission PUCCH / PUSCH resource (set) may be configured differently, or the slot group ID value corresponding to each A / N transmission PUCCH / PUSCH resource (set) may be configured differently (e.g., A / N feedback targeting the corresponding PUCCH / PUSCH resource (set)). For example, regarding A / N feedback for slot group ID = X, the UE may transmit by selecting / using the PUCCH / PUSCH resource (set) configured in slot group ID = X.

[0208] In addition, when multiple carriers are aggregated / configured to one UE (i.e., in the case of CA), for the time slot group ID, option 1-1) can commonly indicate / specify the same time slot group ID for all multiple carriers at the same time (e.g., time slot timing) or duration, or option 1-2) can individually indicate / specify the time slot group ID for each carrier in the order of frequency (carrier) first - time (time slot group) - second (secondary).

[0209] In addition, when the time slot group ID is indicated / specified in the CA scenario, for the counter DAI, 1) (when option 1-1 is applied), the PDSCH scheduling counter value can be determined / indicated in the order of frequency (carrier) first-time (time slot group)-second (second) in one time slot group (ID), or 2) (when option 1-2 is applied), the PDSCH scheduling counter value can be determined / indicated independently for each carrier in one time slot group (ID).

[0210] (4) Proposed method 3

[0211] Before describing the proposed method, the A / N feedback configuration / transmission and related basic operation methods will be described. Figures 12 to 13 The described methods are basically the same and are described again below to classify A / N feedback configuration / transmission methods (or A / N codebook methods).

[0212] 1) Timing-based A / N feedback method (tA / N method)

[0213] A. After configuring multiple candidate HARQ timings in advance through RRC signaling, the base station can indicate one of the multiple candidate HARQ timings to the UE through (DL authorization) DCI. In this case, the UE can operate to send A / N feedback for (multiple) PDSCH reception through the indicated HARQ timing in multiple time slots (or time slot sets; bundling windows) corresponding to all candidate HARQ timing sets. Here, HARQ timing represents PDSCH to A / N timing / interval. HARQ timing can be expressed in units of time slots. In the following, the above method is referred to as a type 1 A / N codebook. The type 1 A / N codebook can be called a semi-static A / N codebook.

[0214] B. In addition to the HARQ timing indication, a counter downlink assignment index (c-DAI) and / or a total DAI (t-DAI) may be signaled together via the (DL grant) DCI. The c-DAI may notify in which order the PDSCH corresponding to the (DL grant) DCI is scheduled. The t-DAI may notify the total number of PDSCHs scheduled up to the current (time slot) (or the total number of time slots in which PDSCHs exist). Thus, the UE may operate to send the A / N of the PDSCH corresponding to the c-DAI values ​​from the initial c-DAI value to the (received) last t-DAI value via the indicated HARQ timing. In the following, the above method is referred to as a type 2 A / N codebook. The type 2 A / N codebook may be referred to as a dynamic A / N codebook.

[0215] C. A / N Feedback Method Based on PDSCH (Time Slot) Group ID (Hereinafter, Type 2a A / N Codebook)

[0216] i. The current ID can be signaled via DL grant DCI, and the feedback ID can be signaled via A / N trigger DCI. Here, the current ID indicates the slot group ID to which the slot in which the DL grant DCI or corresponding PDSCH is transmitted belongs. Furthermore, the feedback ID indicates the (DL PDSCH) slot group ID that is the target of A / N feedback. Here, the overall ID is signaled via DCI, and the feedback ID can be inferred from the overall ID based on method 1.

[0217] ii. The UE may transmit the A / N feedback of the slot group corresponding to the feedback ID (received through the PDSCH of the slot group) at the time indicated by the A / N transmission timing.

[0218] iii. When the A / N triggering DCI is the same as the DL grant DCI (i.e., both the current ID and the feedback ID (or total ID) are signaled by the DL grant DCI), the UE may operate to send by combining (simultaneously, for example, through one PUCCH / PUSCH) 1) the A / N feedback of the bundling window corresponding to timing A or the time slot group corresponding to the current ID (received through the PDSCH of the time slot group); and 2) the A / N feedback of the time slot group corresponding to the feedback ID (received through the PDSCH of the time slot group) at the time indicated by timing A.

[0219] 2) Pooling-based A / N feedback method (pA / N method)

[0220] A. The operation of delaying (pending / postponing) the transmission of A / N feedback for the corresponding PDSCH can be indicated by a DL grant DCI. Thereafter, the transmission of A / N feedback for PDSCH corresponding to (i) all DL HARQ process IDs or (ii) a specific portion of DL HARQ process IDs can be indicated (pooled) by DCI. A / N feedback can be sent at a timing configured / indicated based on a specific signal (e.g., RRC or DCI signaling). Hereinafter, the above method is referred to as a Type 3 A / N codebook. The Type 3 A / N codebook can be referred to as a one-time A / N codebook.

[0221] B. When c- / t-DAI signaling is configured with the tA / N method (e.g., when DAI is signaled via DL grant DCI), A / N pooling can be defined as pooled A / N transmission of PDSCH corresponding to the HARQ process ID (indicated by pooled DCI), or pooled A / N transmission of PDSCH corresponding to the t-DAI value (indicated by pooled DCI). In the latter case, the UE can transmit A / N information received on the PDSCH corresponding to the c-DAI initial value to the t-DAI value at one time.

[0222] 3) Dynamic switching between tA / N method and pA / N method

[0223] A. As an example, switching between the tA / N method and the pA / N method can be indicated by a DL grant DCI. That is, whether A / N feedback is configured / sent can be indicated by applying the tA / N method or the pA / N method via a DL grant DCI. Furthermore, both A / N pending and A / N pooling for the pA / N method can be indicated by the same DL grant DCI. For example, when the DL grant DCI indicates the pA / N method, the DL grant DCI can further indicate whether pending A / N feedback transmission or pooling is indicated.

[0224] B. As another example, switching between the A / N pending operation for applying the tA / N method and the pA / N method may be indicated by a DL grant DCI. That is, whether the tA / N method is applied or whether A / N feedback transmission is pending for the pA / N method may be indicated by a DL grant DCI. Here, the A / N pooling operation for the pA / N method may be indicated by a UL grant DCI or a (UE (group)) common DCI.

[0225] C. As another example, switching between the tA / N method and the A / N pending for pA / N can be indicated by a DL grant DCI including PDSCH scheduling. That is, the DL grant DCI can indicate whether to apply tA / N or the pending A / N transmission for the pA / N method. In this case, the A / N pooling for the pA / N method can be indicated by a DL grant DCI that does not include PDSCH scheduling.

[0226] 4) NFI (New Feedback Indicator) information signaling

[0227] A. Due to the UE's A / N feedback transmission drop due to LBT failure and / or the A / N feedback detection failure light in the base station, in order to prevent inconsistencies in the A / N codebook (payload) configuration between the UE and the base station (as well as CW (contention window size) update for LBT operation accompanying A / N PUCCH (including UL transmissions such as PUSCH, etc.), A 1-bit NFI can be signaled through DCI (e.g., DL grant or UL grant) to trigger A / N feedback transmission. NFI can indicate the following information in a toggle form.

[0228] i. For A / N feedback transmitted at the previous (most recent) time (hereinafter, previous A / N feedback), (a) whether the base station correctly detected / received it, and (b) whether the base station failed to detect / receive it can be signaled. In the case of (a), the UE can process the remaining portion except for the A / N corresponding to the PDSCH scheduled after the previous A / N transmission as NACK or DTX (feedback configuration / transmission omission) to configure / transmit updated A / N feedback. In the case of (b), the UE can configure / transmit A / N feedback by maintaining the remaining portion except for the A / N corresponding to the PDSCH scheduled after the previous A / N transmission.

[0229] ii. In case (a), the current DCI indicates an NFI value that has been switched from the NFI value received via the previous DCI. In case (b), the current DCI may indicate an NFI value that has not been switched from the NFI value received via the previous DCI. When the UE receives the switched NFI, the UE may operate to reset the CW used for A / N PUCCH (and / or PUSCH) transmission to the minimum value, but on the other hand, when the UE receives the non-switched NFI, the UE may operate to increase the CW value (by a certain unit).

[0230] Hereinafter, a DL / UL grant DCI configuration method and signaling information when configuring type 2a and type 1 / 2A / N codebooks are proposed. In addition, in the present disclosure, a DCI format in which the field configuration and each field size in the DCI (format) are configurable (i.e., variable) is referred to as non-fallback DCI, and a DCI (format) in which the DCI field configuration and corresponding size are not configurable (i.e., fixed) is referred to as fallback DCI. In the present disclosure, DCI that is not separately designated as fallback DCI in the present disclosure may represent non-fallback DCI.

[0231] (a) DCI configuration and signaling information when configuring type 2a A / N codebook

[0232] 1) Information signaled via DL authorization DCI

[0233] A. Basically, it can include the following information (basic information for convenience).

[0234] i. Current ID information

[0235] ii. Counter DAI and total DAI information associated with the (PDSCH) slot group corresponding to the current ID

[0236] iii. Feedback ID information

[0237] 1. Alternatively, the total ID may be signaled through DCI, and the feedback ID information may be determined based on method 1.

[0238] iv. NFI information for A / N feedback corresponding to the current ID (ie, NFI for the current ID)

[0239] v. NFI information for the A / N feedback corresponding to the feedback ID (i.e., NFI for the feedback ID)

[0240] 1. Based on method 2 (regardless of the value indicated by the total ID), it may be replaced by NFI information for A / N feedback corresponding to other IDs having values ​​different from the current ID (ie, NFI for other IDs).

[0241] B. In addition, it may also include the following information.

[0242] i. Total DAI information associated with the (PDSCH) slot group corresponding to the feedback ID

[0243] 1. Based on method 2 (regardless of the value indicated by the total ID), it may be replaced with A / N feedback corresponding to other IDs having values ​​different from the current ID (ie, total DAI for other IDs).

[0244] C. In addition, it may also include the following information.

[0245] i. Whether to configure / send A / N feedback based on the Type 3 codebook (e.g., CTI (Codebook Type Indicator) signaling, which indicates which A / N codebook to configure / send among Type 2a and Type 3)

[0246] ii. Notes

[0247] 1. If Type 3 is indicated through DCI (at a specific time), NFI information for Type 3 codebook-based A / N feedback (ie, NFI for Type 3) may be additionally signaled through DCI.

[0248] 2. CTI information can be explicitly signaled using a dedicated 1 bit, or implicitly signaled in the following manner.

[0249] 3. In the first method, when the DCI indicates A / N feedback transmission for only one (PDSCH) slot group corresponding to the current ID, CTI information can be signaled through the NFI bit / field for the feedback ID (or NFI for other IDs). When Type 3 is indicated by the CTI, the HARQ process ID group used for A / N feedback and / or (in the case of Carrier Amplification) CC / cell group can be indicated through the counter DAI, the total DAI bit / field, and / or the NFI for the current ID bit / field, and / or the NFI for Type 3 information can be signaled.

[0250] 4. In the second method, when A / N feedback transmission for only one (PDSCH) slot group corresponding to the current ID is indicated by DCI, CTI information can be signaled through the total DAI for the feedback ID (or the total DAI for other IDs) bit / field. When type 3 is indicated by CTI, the HARQ process ID group and / or (in the case of carrier aggregation) the CC / cell group that is the target of A / N feedback can be indicated through the counter DAI, the total DAI (for the current ID) bit / field, the NFI for the current ID, and / or the NFI for the feedback ID (or the NFI for other IDs) bit / field, and / or the NFI information for type 3 can be signaled.

[0251] 5. In addition, in order to prevent mismatch between the UE and the base station in terms of whether to switch NFI related to A / N based on the type 2a codebook (for each of multiple (PDSCH) time slot groups) (thereby causing A / N errors) and to ensure A / N feedback reliability, when A / N feedback is sent based on the type 3 codebook, it can be operated to send the most recently received NFI bit for each of the multiple time slot groups together through the same single PUCCH / PUSCH resource (for example, through DCI indicating A / N feedback based on the type 2a codebook).

[0252] D. About DL Scheduling Based on Fallback DCI

[0253] i. Basically, the fallback DCI format may include only the current ID information and / or counter DAI information (related to the (PDSCH) slot group corresponding to the corresponding ID) among the basic information described above (for convenience, case 1).

[0254] ii. As another approach, all basic information except the total DAI for the current ID may be included / signaled in a fallback DCI format.

[0255] iii. As another approach, the corresponding DCI format may include / not signal all slot group IDs / indexes, total DAI, and NFI (however, the PDSCH scheduled from the corresponding DCI is configured / defined as a slot group with a specific (e.g., lowest) ID / index) (for convenience, this is referred to as "Case 2").

[0256] iv. In this case, for information not included / signaled in the fallback DCI, the UE may perform A / N codebook (payload) based on the most recently detected / received information through non-fallback DL DCI (e.g., feedback ID (or total ID), current ID, NFI, total DAI, and / or CTI). Here, the non-fallback DL DCI related to the most recently detected / received information may be limited to the DCI indicating the HARQ-ACK (PUCCH) transmission time (time slot) indicated by the fallback DL DCI for the HARQ-ACK (PUCCH) transmission time.

[0257] 1. If there is no non-fallback DCI indicating the same HARQ-ACK (PUCCH) transmission time as the fallback DCI, then according to case 1, the UE may configure / send A / N feedback only for the time slot group corresponding to the current ID or the time slot group corresponding to the lowest ID (in the case of case 2), and for the NFI for the current ID or the lowest ID, the UE may operate to assume / apply a switching form (or non-switching form) (compared to the previous A / N feedback or compared to the previously (ie, most recently) received NFI bit). In addition, the UE may operate by assuming / applying that the CTI is indicated by the Type 2a codebook.

[0258] 2. In addition, considering that NFI information is not included / signaled in the DL fallback DCI as in (Case 2) (therefore, A / N errors may occur due to inconsistency between the UE and the base station as to whether to switch NFI), for the time slot group (PDSCH scheduled from it) with a specific (e.g., lowest) ID / index corresponding to the corresponding DCI, it is possible to operate to send the most recently received NFI bit (e.g., through DL non-fallback DCI) together with A / N feedback through the same single PUCCH / PUSCH resource.

[0259] 3. In addition, (for A / N feedback reliability) in addition for other time slot groups other than the time slot group with a specific (e.g., lowest) ID / index, i.e., for each time slot group indicating A / N feedback transmission, it is operable to send the most recently received NFI bit (e.g., via DL non-fallback DCI) and A / N feedback via the same single PUCCH / PUSCH resource.

[0260] v. In addition, in order to prevent A / N feedback mismatch between the UE and the base station due to DL DCI detection failure of the UE (in the case of case 1), multiple fallback DL DCIs indicating the same HARQ-ACK (PUCCH) transmission time (e.g., time slot) can be configured to indicate the same current ID. Therefore, the UE can operate by assuming that all fallback DL DCIs in the multiple fallback DL DCIs indicating the same HARQ-ACK (PUCCH) transmission time indicate the same current ID, and if other DCI is detected, the UE can ignore the DCI (discard it). For example, the UE may not perform the operation indicated by the corresponding DCI.

[0261] E. Regarding DL transmission operations based on CB Group (CBG)

[0262] i. For CCs / cells in which CBG-based DL transmission is configured, the total DAI for feedback ID (or total DAI for other IDs) information may be signaled separately for the A / N subcodebook corresponding to TB-based transmission and the A / N subcodebook corresponding to CBG-based transmission.

[0263] 2) Information signaled by UL authorization DCI

[0264] A. Basically, it can include the following information (basic information for convenience).

[0265] i. Total DAI information for the first (PDSCH) slot group ID (hereinafter, first ID)

[0266] ii. Total DAI information for the second (PDSCH) slot group ID (hereinafter, second ID)

[0267] iii. Notes

[0268] 1. For example, when up to two (PDSCH) slot groups (index=0, 1) are defined / configured, the first ID and the second ID may correspond to slot group indices 0 and 1, respectively.

[0269] 2. As another example, the first ID and the second ID may be configured / replaced as the current ID and the feedback ID (or other IDs), respectively. In this case, the current ID information and the feedback ID (or total ID) information may be further signaled via DCI.

[0270] A). In case of feedback ID, the total ID is signaled through DCI, and the feedback ID information can be determined based on method 1.

[0271] B) Other IDs may be determined as slot group IDs having values ​​different from the current ID based on method 2.

[0272] 3. As another example, bitmap information for all slot group ID / index sets (e.g., ID / index = 0, 1) may be signaled via DCI. The corresponding group ID bitmap may indicate whether the slot group corresponding to the corresponding ID is the target of an A / N feedback request / transmission for each slot group ID.

[0273] 4. In addition, the UL grant DCI may not include time slot group ID / index related information / signaling. In this case, the UE may be operated to configure / send the A / N codebook (payload) based on the most recently detected / received time slot group ID / index information through the DL grant DCI. Here, the DL grant DCI related to the time slot group ID / index may be limited to the DCI indicating the PUSCH transmission time (time slot) scheduled by the UL grant DCI for the HARQ-ACK transmission time.

[0274] iv. As another method, the UL grant DCI may be configured to include only a single overall DAI information for one specific (PDSCH) slot group (ID / index).

[0275] 1. In this case, the PUSCH transmission time (e.g., PUSCH timing) corresponding to the UL grant DCI corresponding to a specific time slot group (ID / index) among the DL grant DCI (or the PDSCH corresponding to the corresponding DCI) indicated as the A / N feedback transmission time of the PDSCH (e.g., the corresponding A / N timing in the form of a valid or digital value) can be determined as the time slot group (ID / index) to which the PDSCH scheduled by the DL grant DCI received at the latest time from the corresponding UL grant DCI reception time (or the corresponding PUSCH timing) belongs (this is referred to as "Method 1").

[0276] 2. Alternatively, the corresponding specific time slot group may be (pre-)configured / defined as a time slot group with a specific (eg, lowest) ID / index (this is referred to as "method 2").

[0277] 3. Alternatively, the ID / index corresponding to a specific time slot group (a field indicating this) may be signaled / included through the UL authorization DCI, and further, whether A / N feedback transmission corresponding to other time slot groups other than the specific time slot group is to be signaled / included through the UL authorization DCI (a field indicating this).

[0278] 4. In addition, for other time slot groups, it is operable to configure / send corresponding A / N codebooks (payload) based on the most recently detected / received information (e.g., total DAI, NFI) through DL DCI.

[0279] 5. As another method, a single overall DAI information signaled through the UL grant DCI may be commonly applied to multiple (eg, two) time slot groups (this is referred to as "method 3").

[0280] A). As an example, total DAI (eg, UL DAI) information indicated by UL grant DCI for each of a plurality of slot groups may be indicated as the maximum value among the last counter DAI or total DAI (eg, DL DAI) values ​​indicated by DL grant DCI.

[0281] B). Therefore, the UE may be operable to individually interpret the indicated UL DAI value based on the DL DAI value received for each slot group and configure / send the corresponding A / N codebook (payload).

[0282] C). For example, when the DL DAI of slot groups 0 and 1 are 2 and 7 respectively, the UL DAI (applying modulo 4 operation) can be indicated as 3 (corresponding to a maximum value of 7), and the UE receiving this can operate to interpret the total DAI values ​​of slot groups 0 and 1 as 3 and 7 respectively, and configure / send the A / N codebook (payload).

[0283] D). As another example, when the DL DAI of slot groups 0 and 1 are 3 and 5 respectively, the UL DAI (applying modulo 4 operation) may be indicated as 1 (corresponding to a maximum value of 5), and upon receiving this, the UE may operate to interpret the total DAI values ​​of slot groups 0 and 1 as 5 and 5, respectively, and configure / send the A / N codebook (payload).

[0284] 6. In addition, from the perspective of the UE, this method can be applied in case 1) when PDSCH scheduling and / or A / N feedback is indicated from the base station for all multiple (e.g., two) time slot groups, or case 2) when PDSCH scheduling and / or A / N feedback is indicated from the base station only for a specific single time slot group, or case 3) when PDSCH scheduling and / or A / N feedback is not indicated from the base station for all multiple (e.g., two) time slot groups.

[0285] A. For example, in case 1 / 3, method 2 (or method 3) can be applied, and in case 2, method 1 (or method 2) can be applied.

[0286] 7. In addition, the DL (non-fallback) DCI can also be configured to include only a single total DAI (and / or NFI) information for a specific one (e.g., corresponding to the current ID) time slot group. Therefore, when configuring the information / signaling included in the DL / UL DCI, 1) both DL / UL DCI can be configured to include separate total DAI (and / or NFI) information for each of multiple (e.g., two) time slot groups, or 2) both DL / UL DCI can be configured to include only total DAI (and / or NFI) information for one specific time slot group.

[0287] B. In addition, it may also include the following information.

[0288] i. NFI information corresponding to the A / N feedback of the first ID

[0289] ii. NFI information corresponding to the A / N feedback of the second ID

[0290] iii. Notes

[0291] 1. In this case, A / N feedback transmission can be indicated to the UE (via PUSCH) without the need for additional DL (PDSCH) scheduling / transmission from the base station.

[0292] 2. Otherwise, the UL grant DCI may not include NFI information for A / N feedback. In this case, the UE may be operable to configure / send the A / N codebook (payload) based on the most recently detected / received NFI information via the DL grant DCI (for each (PDSCH) slot group). Here, the DL grant DCI associated with the NFI information may be limited to the DCI indicating the PUSCH transmission time (time slot) scheduled by the UL grant DCI for the HARQ-ACK transmission time of the PDSCH.

[0293] 3. As another method, whether to include / configure NFI information / signaling (a field therefor) in the UL grant DCI (for each slot group) may be configured to the UE (eg, through a higher layer signal (eg, RRC signaling)).

[0294] iv. As another method, the UL grant DCI may be configured to include only a single NFI information for one specific (PDSCH) slot group (ID / index).

[0295] 1. In this case, the PUSCH transmission time (e.g., PUSCH timing) corresponding to the UL grant DCI for the corresponding specific time slot group (ID / index) among the DL grant DCI (or the PDSCH corresponding to the DCI) indicated as the A / N feedback transmission time of the PDSCH (e.g., in the form of a valid or digital value for the corresponding A / N timing) can be determined as the time slot group (ID / index) to which the PDSCH scheduled by the DL grant DCI received at the latest time from the corresponding UL grant DCI reception time (or the corresponding PUSCH timing) belongs (this is referred to as "Method 1").

[0296] 2. Alternatively, the corresponding specific (PDSCH) slot group may be (pre-)configured / defined as the slot group with a specific (eg, lowest) ID / index (this is referred to as "method 2").

[0297] 3. Alternatively, the ID / index of the corresponding specific time slot group (a field indicating this) can be signaled / included through the UL authorization DCI, and in addition, whether A / N feedback transmission of other (PDSCH) time slot groups other than the specific (PDSCH) time slot group is performed can be signaled / included through the UL authorization DCI (a field indicating this).

[0298] 4. In addition, for other time slot groups, it is operable to configure / send corresponding A / N codebooks (payload) based on the most recently detected / received information (e.g., total DAI, NFI) through DL DCI.

[0299] 5. As another method, single NFI information signaled through UL grant DCI may be commonly applied to multiple (eg, two) time slot groups (this is referred to as "method 3").

[0300] 6. In addition, from the perspective of the UE, the above method can be applied in case 1) when PDSCH scheduling and / or A / N feedback are indicated from the base station for all multiple (e.g., two) time slot groups, or case 2) when PDSCH scheduling and / or A / N feedback are indicated from the base station only for a specific single time slot group, or case 3) when PDSCH scheduling and / or A / N feedback are not indicated from the base station for all multiple (e.g., two) time slot groups.

[0301] A). For example, in case 1 / 3, method 2 (or method 3) can be applied, and in case 2, method 1 (or method 2) can be applied.

[0302] 7. In addition, whether to include / configure (single) NFI information / signaling (a field used therefor) in the UL grant DCI may be configured to the UE (eg, through a higher layer signal (eg, RRC signaling)).

[0303] C. It may also include the following information.

[0304] i. Whether to configure / send A / N feedback based on the type 3 codebook (e.g., indicating which A / N codebook to configure / send, type 2a or type 3)

[0305] ii. Notes

[0306] 1. If Type 3 is indicated by DCI (at a specific time), NFI information for A / N feedback based on the Type 3 codebook may be additionally signaled through the corresponding DCI.

[0307] D. About UL Scheduling Based on Fallback DCI

[0308] i. Basically, the fallback DCI format may be a form in which all essential information is not included / signaled (omitted).

[0309] ii. Alternatively, the fallback DCI format may be in a form in which all basic information (eg, total DAI and / or ID bitmap information for each of the first ID and the second ID) is included / signaled.

[0310] iii. Alternatively, the fallback DCI format may be in a form including / signaling {total DAI for the first ID, total DAI for the second ID, NFI for the first ID, NFI for the second ID}.

[0311] iv. Alternatively, the fallback DCI format may be in a form including / signaling {NFI for the first ID, NFI for the second ID} (and / or group ID bitmap information).

[0312] v. In this case, regarding information not included / signaled in the UL grant DCI, the UE may be operable to configure / transmit an A / N codebook (payload) based on the most recently detected / received information (e.g., slot group ID / index, total DAI, NFI, CTI) via the DL grant DCI. Here, the DL grant DCI associated with the most recently detected / received information may be limited to the DCI indicating the PUSCH transmission time (time slot) scheduled by the UL grant DCI for the HARQ-ACK transmission time of the PDSCH.

[0313] vi. In addition, when A / N is piggybacked and transmitted via CG-PUSCH transmitted without DCI in the configured (configured grant, CG) form instead of scheduling the accompanying dynamic grant DCI transmission, the UE may be operated to configure / transmit the A / N codebook (payload) based on the most recently detected / received information (e.g., slot group ID / index, total DAI, NFI, CTI) via DL grant DCI. Here, the DL grant DCI related to the most recently detected / received information may be limited to DCI indicating the CG-PUSCH transmission time (time slot) of the HARQ-ACK transmission time for the PDSCH.

[0314] E. Regarding DL transmission operations based on CB Group (CBG)

[0315] i. For CCs / cells configured with CBG-based DL transmission, the total DAI (e.g., the total AI for the first ID and the total DAI for the second ID) may be signaled separately for the A / N subcodebook corresponding to TB-based transmission and the A / N subcodebook corresponding to CBG-based transmission.

[0316] In addition, when the UE configures / sends A / N feedback on PUCCH / PUSCH based on the type 2a codebook, a method may be required for the base station to indicate / recognize that "there is no A / N feedback to be piggybacked and sent on PUSCH". To this end, the following DCI signaling and operations may be considered.

[0317] 1) Method 1

[0318] A. When the total DAI bits in the UL grant DCI are indicated as '11' (or the total DAI value is 4), and when no DL grant DCI is detected during the bundling window duration corresponding to the PUSCH transmission time (or the interval from the previous (e.g., most recent) A / N feedback transmission time (or the time indicated by the corresponding transmission time) to the PUSCH transmission timing), and when the NFI bit indicated by the UL grant DCI is toggled (compared to the previous A / N feedback or compared to the previously (e.g., most recent) received NFI bit), the UE may operate so as not to piggyback any A / N on the PUSCH. This method may be applied to a method for signaling NFI information through UL grant DCI. Here, the check for DCI information check and the corresponding UE operation may be performed independently / individually for each (PDSCH) slot group (ID).

[0319] B. In another method, for detected / received UL grant DCI (in the absence of separate NFI information signaling via UL grant DCI), a check on the operation of the DCI / UE is applied / performed and it may be assumed that the NFI bit is non-switched (or toggled) (compared to the previous A / N feedback or compared to the previously (most recently) received NFI bit). This method may be applied to the case of UL grant DCI (format) without separate NFI information signaling (e.g., fallback).

[0320] 2) Method 2

[0321] A. One of the states signaled by the total DAI field in the UL grant DCI may be defined as indicating "no A / N feedback" (to be piggybacked on the PUSCH). When the corresponding state is indicated by the DCI, the UE may operate so as not to piggyback any A / N on the PUSCH. This method may be applied to a method in which NFI information is not signaled by the UL grant DCI. Here, the check for the DCI information and the corresponding UE operation may be performed independently / separately for each (PDSCH) slot group (ID).

[0322] 3) Method 3

[0323] A. Only one (PDSCH) slot group (e.g., first ID) may be indicated by the first ID and second ID (or current ID and feedback ID (or total ID)) bits / fields in the UL grant. In this case, through a specific total DAI field (e.g., the total DAI field for the second ID), 1) A / N feedback (piggybacked on the PUSCH) for only the indicated slot group (e.g., first ID) may be indicated as configured / transmitted, or 2) A / N feedback to be piggybacked on the PUSCH may be indicated even for the indicated slot group (e.g., first ID) (i.e., for all slot groups (first ID and second ID)).

[0324] i. This method can be applied to a method in which the time slot group ID information is signaled (PDSCH) through UL grant DCI (there is no NFI information signaling through UL grant DCI). For example, the time slot group ID information includes the first ID and the second ID (or the current ID and the feedback ID (or total ID)) information).

[0325] In addition, in a state where A / N feedback is configured / transmitted on PUCCH / PUSCH based on the type 2a codebook (there is no separate NFI information signaling through UL grant DCI), during a bundling window period corresponding to a PUSCH transmission time (or a period from a previous (most recent) A / N feedback transmission time (or a time indicated by a corresponding transmission timing) to a corresponding PUSCH transmission time), when no (DL grant) DCI scheduling a PDSCH belonging to a specific (PDSCH) timeslot group (ID) or indicating A / N feedback of a corresponding timeslot group is detected / received, it is assumed / considered that (compared to the previous A / N feedback or compared to the previous (most recent) A / N feedback) ) compared to the received NFI bit) in a state where the NFI bit corresponding to the corresponding (PDSCH) time slot group (ID) is switched (or not switched), the UE may or may not configure the A / N payload corresponding to the corresponding (PDSCH) time slot group (ID) on the PUSCH based on the total DAI value indicated by the UL grant DCI (for example, if the corresponding total DAI value is 4, the UE does not configure the A / N payload (i.e., 0-bit A / N) and does not piggyback on the PUSCH, otherwise if the corresponding total DAI value is not 4, the UE configures the A / N payload (i.e., 1 or more bits A / N) to piggyback the A / N on the PUSCH.

[0326] For another additional method, in the case where operation is to configure / send A / N feedback on PUCCH / PUSCH based on the type 2a codebook (and there is no separate NFI information signaling through UL grant DCI), during the bundling window period corresponding to the PUSCH transmission time, for convenience, the case where no (DL grant) DCI scheduling belonging to a specific (PDSCH) time slot group (ID) is detected / received, the case where no (DL grant) DCI indicating A / N feedback of the corresponding (PDSCH) time slot group is detected / received, or the case where no (DL grant) DCI indicating NFI information of the corresponding (PDSCH) time slot group is detected / received is referred to as a "no PDSCH case".

[0327] Here, in the case of a "no PDSCH situation", the UE may operate to configure or not configure an A / N payload corresponding to the corresponding (PDSCH) time slot group (ID) on the PUSCH based on the corresponding NFI value and the total DAI value indicated by the UL grant DCI, under the assumption / belief that the NFI bit value corresponding to the corresponding (PDSCH) time slot group (ID) has not been switched (or switched) (compared to the previously (most recently) received NFI value).

[0328] Specifically, if the corresponding total DAI value N is 4 (for example, N=4), it can be operated to not configure the A / N payload (i.e., 0-bit A / N) and not piggyback on the PUSCH. Otherwise, if the corresponding total DAI value N is not 4 (for example, N<4), it can be operated to configure the A / N payload (i.e., 1 or more bits of A / N) and piggyback the A / N on the PUSCH. Specifically, it can be operated to configure the A / N payload for {N+4M} (M is a positive integer (including 0)) PDSCHs (or N PDSCHs) based on the non-switching NFI assumption (or switching NFI assumption) and piggyback on the PUSCH.

[0329] As an example, in a case where T-DAI is configured to be indicated for each PDSCH group through UL grant DCI, if the "no PDSCH case" is for a specific (PDSCH) time slot group, the operation can be applied to the corresponding (PDSCH) time slot group. As another example, in a case where it is configured to indicate only one T-DAI through UL grant DCI, if the "no PDSCH case" is for all PDSCH groups, the proposed operation can be applied to a specific (e.g., with the lowest group ID / index) PDSCH group.

[0330] In another way, if there is a "no PDSCH case", the UE can assume that the NFI bit value corresponding to the corresponding (PDSCH) time slot group (ID) remains the same as the previously (most recently) received NFI value (e.g., not switched from the previously (most recently) received NFI value), and regardless of the corresponding NFI value, the UE can operate to configure or not configure the A / N payload corresponding to the corresponding (PDSCH) time slot group (ID) on the PUSCH based only on the total DAI value indicated by the UL grant DCI.

[0331] Specifically, if the corresponding total DAI value N is 4 (for example, N=4), it can be operated to not configure the A / N payload (i.e., 0-bit A / N) and not piggyback on the PUSCH. Otherwise, if the corresponding total DAI value N is not 4 (for example, N<4), it can be operated to configure the A / N payload (i.e., 1 or more bits of A / N) and piggyback the A / N on the PUSCH. Specifically, it can be operated to configure the A / N payload for N PDSCHs (corresponding to the counter DAI values ​​of 1 to N) and piggyback on the PUSCH.

[0332] As an example, in the case where the T-DAI is indicated for each PDSCH group through UL authorization DCI, if the "no PDSCH case" is for a specific (PDSCH) time slot group, the proposed operation can be applied to the corresponding (PDSCH) time slot group. As another example, in the case where the T-DAI is indicated only through UL authorization DCI, if the "no PDSCH case" is for all PDSCH groups, the proposed operation can be applied to a specific (e.g., with the lowest group ID / index) PDSCH group.

[0333] In another method, if there is a "no PDSCH situation", the UE can assume that the NFI bit value corresponding to the corresponding (PDSCH) time slot group (ID) remains the same as the previously (most recently) received NFI value (for example, not switched from the previously (most recently) received NFI value), and in a state where the UE believes that the PDSCH corresponding to the total DAI value indicated by the UL grant DCI does not belong to any (PDSCH) time slot group (ID), the UE can operate to configure or not configure an A / N payload only for the corresponding PDSCH.

[0334] Specifically, if the corresponding total DAI value N is 4 (for example, N=4), it can be operated to not configure the A / N payload (i.e., 0-bit A / N) and not piggyback on the PUSCH. Otherwise, if the corresponding total DAI value N is not 4 (for example, N<4), it can be operated to configure the A / N payload (i.e., 1 or more bits of A / N) and piggyback the A / N on the PUSCH. Specifically, it can be operated to configure the A / N payload for N PDSCHs (corresponding to the counter DAI values ​​of 1 to N) and piggyback on the PUSCH.

[0335] As an example, in a case where it is configured to indicate T-DAI for each PDSCH group through UL authorization DCI, if it is a "no PDSCH case" for a specific PDSCH group, the operation can be applied in a state where the PDSCH corresponding to the T-DAI configured in the corresponding PDSCH group does not belong to any PDSCH group. As another example, in a case where only one T-DAI is indicated through UL authorization DCI, if it is a "no PDSCH case" for all PDSCH groups, the operation can be applied in a state where the PDSCH corresponding to the corresponding T-DAI is considered to not belong to any PDSCH group.

[0336] In addition, in the case of scheduling / indicating (multi-slot scheduling) multiple PUSCH resources sent on multiple time slots via a single UL grant DCI, it may be necessary to apply the operation of the total DAI, NFI and / or CTI information. The corresponding information may be applied only to: (a) PUSCH resources in the first time slot (i.e., first time slot PUSCH), (b) the first PUSCH resource (i.e., first PUSCH), (c) initial PUSCH resources consisting of more than a specific number of symbols (or the number of non-DMRS symbols) and / or a specific number of RBs (or the number of REs or the number of non-DMRS), (d) PUSCH resources allocated in the time slot immediately following the first time slot in which the PUSCH transmission is indicated. , or (e) a first PUSCH resource having the same symbol duration as the slot duration (i.e., a first full PUSCH) (e.g., a specific one of a plurality of resources or a specific combination of resources), alternatively, it may be applied only to 2) (a) the first successful first slot PUSCH in LBT (through its CCA), or (b) the first full PUSCH, alternatively, it may be applied only to 3) (a) the first slot PUSCH in which A / N feedback is transmitted in a piggybacked form, (b) the first PUSCH, or (c) the first full PUSCH. For the remaining slots or PUSCH resources other than the above, a) the A / N codebook (payload) may be configured / transmitted via DL grant DCI based on the most recently detected / received information (e.g., slot group ID / index, total DAI, NFI, CTI, and / or information indicating whether A / N is backed off, information indicating the presence or absence of pending A / N to be described later), and / or b) a specific (e.g., default) value may be assumed / applied for the information.

[0337] In case a), the DL grant DCI related to the most recently detected / received information may be limited to the DCI indicating the PUSCH transmission time (time slot) for the HARQ-ACK transmission time of the PDSCH. In addition, in case b), at least one of the following may be assumed / applied.

[0338] 1) For the total DAI, the total DAI bits may be assumed / applied as '11' (or the total DAI value is 4),

[0339] 2) it may be assumed / applied to a switch (or non-switch) (compared to the previous A / N feedback or compared to the previously (e.g., most recently) received NFI bit),

[0340] 3) It may be assumed / applied that: Type 2a (or Type 1 / 2 in the following case) codebook is indicated as CTI,

[0341] 4) In the following, it may be assumed / applied that there is no corresponding field / signaling for “information indicating whether A / N feedback is based on type 1 codebook”.

[0342] 5) Hereinafter, it may be assumed / applied that there is no corresponding pending A / N feedback for “information indicating the presence or absence of a pending A / N”.

[0343] (b) DCI configuration and signaling information when configuring type 1 / 2A / N codebook

[0344] 1) Information signaled via DL authorization DCI

[0345] A. Basically, it can include the following information (basic information for convenience).

[0346] i. Information indicating whether to fall back on A / N (e.g., for type 1 codebook)

[0347] ii. Notes

[0348] 1. This information may indicate whether only one fallback DCI scheduling PCell (PDSCH transmission via PCell) is transmitted during one bundling window period. The information may be configured / signaled using only 1 bit.

[0349] iii. Counter DAI and total DAI indication information (for type 2 codebook)

[0350] B. It may additionally include the following information.

[0351] i. Whether A / N feedback is configured / sent based on the Type 3 codebook (e.g., CTI signaling indicating which A / N codebook is configured / sent between Type 1 or 2 and Type 3)

[0352] ii. Notes

[0353] 1. If Type 3 is indicated by DCI (at a specific time), NFI information for A / N feedback based on the Type 3 codebook may be additionally signaled through the corresponding DCI.

[0354] C. It may additionally include the following information.

[0355] i. Information indicating the presence or absence of a pending A / N

[0356] ii. Notes

[0357] 1. This information may indicate whether the final A / N feedback is configured by further including an A / N with a pending indication (at a previous time) in the A / N payload based on a Type 1 or Type 2 codebook configuration (ie, pending A / N).

[0358] D. About DL Scheduling Based on Fallback DCI

[0359] i. For Type 1 codebook

[0360] 1. Basically, the corresponding DCI format (at least corresponding to PCell / PSCell) may have a form in which basic information is included / signaled.

[0361] 2. In addition, the fallback DCI format corresponding to the SCell (except PCell / PSCell) may have a form in which basic information is not included / signaled.

[0362] ii. For Type 2 codebook

[0363] 1. Basically, the corresponding DCI format may have a form including / signaling only a counter DAI from basic information.

[0364] E. Regarding DL transmission operations based on CB Group (CBG)

[0365] i. When a CC / cell is configured for CBG-based DL transmission, or when CA includes a CC / cell in which CBG-based DL transmission is configured, the pending A / N payload may be determined based on the maximum number of CBGs configured (transmittable) for all cells / CCs (i.e., the maximum value among the number of CBGs configured (transmittable) for each cell / CC). When a CC / cell is configured for TB-based transmission, or when aggregation includes a CC / cell in which only TB-based transmission is configured, the pending A / N payload may be determined based on the maximum number of TBs configured (transmittable) for all cells / CCs (i.e., the maximum value among the number of TBs configured (transmittable) for each cell / CC).

[0366] 2) Information signaled by UL authorization DCI

[0367] A. Basically, it can include the following information (for convenience, basic information)

[0368] i. Information indicating A / N feedback based on type 1 codebook (e.g., for type 1 codebook)

[0369] ii. Notes

[0370] 1. This information may indicate whether to transmit an A / N payload based on the type 1 codebook configuration piggybacked to the PUSCH (or whether to piggyback 0 bits (ie, omit piggybacking) or only back off A / N) and transmit it.

[0371] iii. Total DAI indication information (for type 2 codebook)

[0372] B. It may also include the following information

[0373] i. Whether to configure / send A / N feedback based on type 3 codebook (e.g., indicating which A / N codebook is configured / sent among type 1 or 2 and type 3)

[0374] ii. Notes

[0375] 1. If Type 3 is indicated through DCI (at a specific time), NFI information for A / N feedback based on the Type 3 codebook may be further signaled through DCI.

[0376] C. It may further include the following information

[0377] i. Information indicating the presence or absence of a pending A / N

[0378] ii. Notes

[0379] 1. This information may indicate whether the final A / N feedback is configured by further including an A / N with a pending indication (at a previous time) in the A / N payload based on a Type 1 or Type 2 codebook configuration (ie, pending A / N).

[0380] D. About UL Scheduling Based on Fallback DCI

[0381] i. Basically, the fallback DCI format may have a form in which basic information is not included / signaled.

[0382] ii. For information not included / signaled in the UL grant DCI, the UE may be operable to configure / transmit the A / N codebook (payload) based on the most recently detected / received information (e.g., information indicating whether A / N is backed off (for type 1 codebook), counter DAI / total DAI information (for type 2 codebook), CTI, information indicating whether a pending A / N is present or absent) through the DL grant DCI. Here, the DL grant DCI related to the most recently detected / received information may be limited to DCI indicating the PUSCH transmission time (time slot) scheduled by the UL grant DCI for the HARQ-ACK transmission time of the PDSCH.

[0383] iii. In addition, A / N can be piggybacked and transmitted in the form of CG (configured grant) instead of CG-PUSCH transmission that schedules the accompanying dynamic grant DCI transmission. In this case, the UE can configure / send the A / N codebook (payload) based on the most recently detected / received information (e.g., information indicating whether to fall back on A / N (for type 1 codebook), counter DAI / total DAI information (for type 2 codebook), CTI, information indicating whether there is a pending A / N). Here, the DL grant DCI related to the most recently detected / received information can be limited to DCI indicating the CG-PUSCH transmission time (time slot) of the HARQ-ACK transmission time for the PDSCH.

[0384] E. Regarding DL transmission operations based on CB Group (CBG)

[0385] i. Similar to the case of DL grant DCI above, the pending A / N payload may be determined based on the maximum number of (transmittable) CBGs or TBs configured in all cells / CCs.

[0386] In addition, (Type 2a or Type 1 or Type 2 A / N codebook configuration, and according to this) DL / UL grant DCI information configuration and signaling operations can be limited to the case where the PUCCH cell / CC (e.g., PCell or PSCell) configured to perform PUCCH transmission in the case of CA is a cell / CC operating in the U band. In this case, the DL / UL grant DCI corresponding to all cells / CCs in CA can be configured according to the method proposed in this disclosure. In addition, when the PUCCH cell / CC is a cell / CC operating in the L band (in a state where the existing Type 1 or Type 2a A / N codebook is configured), the same DL / UL grant DCI information configuration and signaling operations as the existing ones can be applied. In this case, the DL / UL grant DCI corresponding to all aggregated cells / CCs can be configured to be the same as the existing ones.

[0387] As another method, the Type 2a or Type 1 or Type 2 A / N codebook configuration and the configuration / signaling of DL / UL grant DCI information based thereon can be limited to the case where cells / CCs operating in the U-band are included in the multicarrier, that is, a set of multiple cells / CCs are configured for CA to the UE. In this case, the DL / UL grant DCI corresponding to all aggregated cells / CCs can be configured as in the method proposed above. In addition, when the multicarrier includes only cells / CCs operating in the L-band, the existing Type 1 or Type 2a A / N codebook configuration and the configuration / signaling of the existing DL / UL grant DCI information based thereon can be applied. In this case, the DL / UL grant DCI corresponding to all aggregated cells / CCs can be configured the same as the existing one.

[0388] (5) Proposed method 4

[0389] (a) A / N feedback update for a specific PDSCH

[0390] For a specific PDSCH or HARQ process ID, the processing time (required for PDSCH decoding and A / N preparation operations) may be insufficiently scheduled / indicated by the base station (compared to the minimum processing time that the UE can support). In this case, the UE may operate to feedback a NACK (or DTX) for the corresponding PDSCH (or HARQ process ID) through the (first) A / N (PUCCH) transmission time indicated by the DCI (corresponding to the corresponding PDSCH).

[0391] Thereafter, (in the absence of separate retransmission scheduling for the PDSCH (or HARQ process ID) from the base station), the base station may (again) indicate A / N feedback transmission (based on the Type 2a codebook) for the slot group ID including the PDSCH, or A / N feedback transmission (based on the Type 3 codebook) for the HARQ process group including the HARQ process ID. In this case, the UE can update the A / N feedback for the corresponding PDSCH (or HARQ process ID) by reflecting the actual / final decoding result of the corresponding PDSCH (or HARQ process ID). For example, when the decoding result is ACK, an ACK for the corresponding PDSCH (or HARQ process ID) can be fed back using the A / N (PUCCH) transmission time (again) indicated by the base station.

[0392] Furthermore, the above operation may be applied regardless of whether the NFI corresponding to the PDSCH (or HARQ process ID) is switched, or only in one of the cases where the corresponding NFI is not switched and the case where the corresponding NFI is switched. Thus, in the other case, the feedback update described above may be omitted (e.g., maintaining the previous feedback).

[0393] In addition, when the processing time of the HARQ process ID is not fully scheduled / indicated from the base station, the update of the HARQ-ACK feedback sent by the UE through the corresponding HARQ-ACK transmission time (hereinafter, updated feedback) can vary according to the NDI value indicated for the corresponding HARQ process ID. For example, in the case where the NDI value is not switched (compared to the previous value), when the UE previously fed back an ACK for the corresponding HARQ process ID and / or the actual / final PDSCH decoding result is ACK, the UE can update / report HARQ-ACK feedback with ACK (e.g., updated feedback). As another example, in the case where the NDI value is not switched (relative to the previous value), when the UE previously fed back a NACK for the corresponding HARQ process ID and / or the actual / final PDSCH decoding result is NACK, the UE can report HARQ-ACK feedback with NACK (e.g., updated feedback). As another example, when the NDI indication is in a switching state (compared to the previous value) and a new TB or PDSCH is scheduled / transmitted, the UE may report HARQ-ACK feedback (e.g., updated feedback) with an invalid value (e.g., NACK) due to lack of processing time for the corresponding TB or PDSCH.

[0394] (b) CBG retransmission set CC related to A / N feedback

[0395] When the base station indicates the transmission of A / N feedback based on the type 3 codebook, a method for configuring the A / N payload on the PUCCH (or PUSCH) may be required. A consensus needs to be reached between the UE and the base station on the payload configuration of the A / N feedback based on the type 3 codebook.

[0396] As a specific example, based on the CC index set configured for the UE, the HARQ process ID / index set configured for each CC, the (maximum) TB index set or CBG index set configured for each CC, the UE may need to determine the order of mapping the A / N bits corresponding to each {CC, HARQ ID, TB or CBG} combination.

[0397] Taking this into consideration, for example, a method of mapping the A / N bits according to the "first TB / CBG index - second HARQ process index - third CC index" method can be considered. For example, the A / N bits of the TB / CBG are mapped based on the TB / CBG index (first level) -> when the mapping of the A / N bits of the corresponding HARQ process is completed, the A / N bits of the next HARQ process are mapped based on the HARQ process index (second level) -> when the mapping of the A / N bits of the corresponding CC is completed, the A / N bits of the next CC are mapped based on the CC index (third level). In this way, each A / N bit can be mapped in the HARQ-ACK payload. To give a more specific example, 1) for the lowest HARQ process index of the lowest CC index, the A / N corresponding to the lowest TB / CBG index (up to the highest TB / CBG index) is mapped in sequence, 2) for the second lowest HARQ process index of the lowest CC index, the A / N corresponding to the lowest TB / CBG index is mapped in sequence, ... 3) for the highest HARQ process index of the lowest CC index, the A / N corresponding to the lowest TB / CBG index is mapped in sequence, 4) for the lowest HARQ process index of the second lowest CC index, the A / N corresponding to the lowest TB / CBG index is mapped in sequence, ..., the UE can operate to map A / N in the above order. As an example of using such A / N mapping, reference can be made to the later described Figures 17 to 23 .

[0398] The UE may be configured to report A / N for multiple (or all) CCs, multiple (or all) HARQ processes, and multiple (or all) TBs / CBGs (for type 3 codebook-based A / N feedback transmission) at once (e.g., receive the pdsch-HARQ-ACK-OneShotFeedback-r16 parameter via higher layer signaling). The UE may report HARQ-ACK responses based on the configuration related to the type 3 codebook. The order in which the respective A / N bits are mapped in the payload of the HARQ-ACK response may follow the order described above. For example, a UE reporting A / N based on the type 3 codebook may first map the A / N bits in sequence from the A / N bits of the lowest-index TB / CBG of the lowest-index HARQ process in the lowest-index cell to the A / N bits of the highest-index TB / CBG (i.e., the first-level mapping), then perform the first-level mapping separately from the second-lowest-index HARQ process in the lowest-index cell to the highest-index HARQ process (i.e., the second-level mapping), and then perform the first and second-level mappings separately from the second-lowest-index cell to the highest-index cell (i.e., the third-level mapping). According to this example, rules can be clearly defined between the UE / base station regarding the order in which the A / N bits to be sent at once via the same single HARQ-ACK message (e.g., a single PUCCH signal or a single PUSCH signal) should be arranged. In addition, the meaning that the A / N bits are first placed in the payload means that among each A / N bit (O ACK j ), where 0 < j < the maximum number of A / N bits, the corresponding A / N value is mapped to the A / N bit with a lower index j.

[0399] Summarized as:

[0400] -(When multiple serving cells are configured for a UE) The A / N bits of the serving cell with a lower cell index (i.e., the A / N bits of the DL signal received via the serving cell with a lower cell index) are placed first.

[0401] -For the A / N bits with the same cell index, the A / N bits associated with the HARQ process with a lower HARQ index are placed first.

[0402] -For the A / N bits with the same HARQ process index, the A / N bits of the TB with a lower TB index are placed first.

[0403] -(For serving cells configured with CBG-based HARQ-ACK) For the A / N bits with the same TB index, the A / N bits of the CBG with a lower CBG index are placed first.

[0404] Figure 15 Illustrates the existing transport block (TB) processing procedure. Figure 15The process can be applied to the data of the DL-SCH transport channel. The uplink TB (or the data of the uplink transport channel) can be processed similarly.

[0405] Reference Figure 15 , the transmitter applies a CRC (e.g., 24 bits) (TB CRC) to the TB for error detection. Thereafter, the transmitter may divide the TB+CRC into multiple code blocks (CBs) taking into account the size of the channel encoder. The maximum size of a CB in NR is 8424 bits (LDPC basis Figure 1 ) or 3840 bits (LDPC basis Figure 2 ). Therefore, if the TB size is smaller than the CB maximum size, the CB is not configured, and if the TB size is larger than the CB maximum size, the TB is divided into CB maximum size units to generate multiple CBs. CRC (e.g., 24 bits) (CB CRC) is added separately to each CB for error detection. After each CB undergoes channel coding and rate matching, they are combined into one to generate a codeword (CW). In the case of a cell (e.g., CC) where CBG-based transmission (retransmission) is not configured, data scheduling and the resulting HARQ process are performed in TB units, and the CB CRC is used to determine early termination of TB decoding.

[0406] Figure 16 Existing CBG-based transmission is illustrated.

[0407] Reference Figure 16 For a cell (e.g., CC) configured with CBG-based transmission (retransmission), the UE may receive information regarding the maximum number M (>1) of code block groups per transport block from the base station via a higher-layer signal (e.g., an RRC signal) (S1602). CBG-based transmission may be configured for each cell (e.g., CC). Thereafter, the UE may receive initial data transmission from the base station (via the PDSCH) (S1604). Here, the data includes a TB, the transport block includes multiple CBs, and the multiple CBs may be divided into one or more CBGs. For convenience, the TB-CRC and CB-CRC are not shown. Here, some CBGs may include ceiling (K / M) CBs, and the remaining CBs may include flooring (K / M) CBs. K represents the number of CBs in the TB. Thereafter, the UE may feedback CBG-based A / N information for the data to the base station (S1606), and the base station may perform data retransmission based on the CBG (S1608). The A / N information may be sent via the PUCCH or the PUSCH. Here, the A / N information may include multiple A / N bits for data, each A / N bit may indicate a respective A / N response generated in units of CBGs for the data. Regardless of the CBGs (e.g., TBs) constituting the data, the payload size of the A / N information may remain the same based on M.

[0408] In addition, when the base station indicates A / N feedback transmission based on the type 3 codebook, the size of the A / N payload transmitted through the PUCCH (or PUSCH) may increase in proportion to the number of CCs configured for the UE, the number of HARQ processes configured for each CC, the maximum number of TBs, or the maximum number of CBGs configured for each CC. In particular, the number of CBGs may be a factor that rapidly increases the size of the A / N payload compared to other parameters, which may result in a large amount of PUCCH resource overhead.

[0409] Figure 17 A / N transmission based on a type 3 codebook is illustrated.

[0410] The base station may indicate the transmission of A / N feedback based on the Type 3 codebook via DCI on the PDCCH. When the transmission of A / N feedback based on the Type 3 codebook is indicated, the UE may perform the transmission of A / N feedback based on the Type 3 codebook based on the configuration of the Type 3 codebook obtained through higher layer signaling.

[0411] This type 3 codebook-based A / N feedback may be understood as a one-time A / N feedback that reports HARQ-ACK for multiple CCs, multiple HARQ processes per CC, and / or at least one or more TB / CBGs per HARQ process.

[0412] The base station may configure parameters related to the A / N feedback based on the type 3 codebook through higher layer signaling before indicating the A / N feedback based on the type 3 codebook through DCI. For example, higher layer signaling may be provided for each cell group. The base station may configure the A / N feedback based on the type 3 codebook to the UE1 through higher layer signaling (e.g., RRC signaling), and configure whether the A / N feedback based on the type 3 codebook should be performed on a CBG basis and / or whether to report the NDI value related to the corresponding A / N value (e.g., the NDI field value included in the DL grant DCI).

[0413] When the A / N feedback based on the type 3 codebook is configured to be performed in CBG units, the UE can perform A / N feedback based on the type 3 codebook in CBG units for all CCs performing CBG unit transmission. However, for CCs performing transmission in TB units, the UE still performs A / N feedback based on the type 3 codebook in TB units. On the other hand, when the A / N feedback based on the type 3 codebook is not configured to be performed in CBG units, the UE can perform A / N feedback based on the type 3 codebook in TB units for all CCs (e.g., all CCs including the CC performing CBG unit transmission).

[0414] A UE configured (e.g., by higher layer signaling) to report an NDI value (e.g., an NDI field value included in a DL grant DCI) together with an A / N transmission based on a type 3 codebook reports one NDI per TB. For example, for a CC that generates A / N feedback based on a type 3 codebook per TB, the UE reports the A / N bits and the corresponding NDI value of the corresponding TB together (e.g., the corresponding NDI field value of the DCI that schedules the corresponding TB). Additionally, for example, for a CC that generates A / N feedback based on a type 3 codebook per CBG, the UE may report the A / N bits of the CBG included in the corresponding TB together with the corresponding NDI value common to the CBGs belonging to the corresponding TB (e.g., the corresponding NDI field value of the DCI that schedules the CBG of the corresponding TB).

[0415] When receiving an A / N feedback request based on a type 3 codebook through DCI, the UE may generate and send A / N feedback based on the type 3 codebook based on the above-mentioned higher layer signaling.

[0416] exist Figure 17 In the embodiment, it is assumed that the higher layer signaling process related to the A / N feedback based on the type 3 codebook has been completed.

[0417] Reference Figure 17 , the UE may receive one or more PDSCHs on at least one CC (S1702). Each PDSCH may include one or more TBs. Each TB may include one or more CBs. When CBG unit transmission (retransmission) is configured for the corresponding CC, the CBs of the TBs may be bundled into multiple CBGs. Each received PDSCH corresponds to each (DL) HARQ process ID, and the (DL) HARQ process ID corresponding to the corresponding PDSCH may be indicated by the DCI that schedules the PDSCH. The total number of (DL) HARQ process IDs may be configured for each CC.

[0418] Thereafter, the UE may transmit A / N information (based on the type 1 / 2 codebook) according to the corresponding HARQ-ACK process timing of one or more received PDSCHs (not shown). To avoid blurring the focus of the description, the process of transmitting A / N information based on the type 1 / 2 codebook is not shown, and its detailed description will be omitted.

[0419] In addition, the UE may receive control information instructing transmission of A / N feedback based on a Type 3 codebook from the base station (S1704). Transmission of A / N feedback based on a Type 3 codebook may include a process for configuring A / N feedback based on an HARQ process ID (for all HARQ process IDs of the corresponding serving CC / cell). Configuration of A / N feedback based on an HARQ process ID may refer to configuring the generation / arrangement of A / N information included in the A / N feedback based on an HARQ process ID. A / N information may be configured / arranged for each HARQ process ID (for all HARQ process IDs of the corresponding serving CC / cell).

[0420] As a more specific example, based on the indication of DCI (e.g., DL grant) (e.g., refer to CTI of the proposed method 3), A / N feedback transmission based on the type 3 codebook may include (for all serving CCs) configuring A / N feedback for the PDSCH corresponding to all DL HARQ process IDs of each CC based on the HARQ process ID (refer to pA / N of the proposed method 3).

[0421] The UE may send A / N feedback based on the type 3 codebook ( S1706 ).

[0422] The A / N feedback may be transmitted at a timing configured / indicated based on a specific signal (eg, RRC or DCI signaling).

[0423] In case of A / N feedback based on type 3 codebook, the A / N payload may include A / N information configured based on HARQ process ID for all (DL) HARQ process IDs of each CC (for all serving CCs).

[0424] Figure 20 and Figure 21 Various examples of A / N feedback based on type 3 codebook are illustrated. More specifically, Figure 20 An example is given in which spatial bundling is not applied and NDI reporting is not configured for A / N feedback based on the type 3 codebook. Figure 21 An example is given in which spatial bundling is applied for A / N feedback based on the type 3 codebook and NDI reporting is not configured.

[0425] As an example, in the A / N feedback based on the type 3 codebook, when there is no A / N feedback for a specific CC (e.g., Figure 20 (b) CC or Figure 20When CC#n in (c) configures CBG-based transmission, the A / N payload size for a specific CC may be determined based on the maximum number of TBs configured for that CC. For example, the A / N payload for a specific CC may include TB-level A / N information corresponding to each HARQ process ID. TB-level A / N information may be configured with 1 bit for each TB.

[0426] On the other hand, as a case where CBG-based transmission is configured for a specific CC, when a one-time feedback CBG parameter is configured for type 3 A / N feedback (e.g., Figure 20 (a) CC or Figure 20 The A / N payload size of a specific CC may be determined based on the maximum number of CBGs configured for the specific CC. That is, the A / N payload of a specific CC includes CBG-level A / N information corresponding to each HARQ process ID. The CBG-level A / N information may be configured with 1 bit for each CBG. Since the CBG-level A / N information is configured with multiple bits for one TB (e.g., Figure 16 M) A / N information in, so when the A / N information is configured as CBG level, the A / N payload size can increase rapidly.

[0427] Considering the problem of increasing UL (PUCCH) resource overhead as described above, when A / N feedback transmission based on type 3 codebook is indicated, for a CC configured for CBG-based transmission (retransmission), a method that can be operated to generate / map / send TB-level A / N for each HARQ process ID may be required. To this end, high-layer signaling can be used. For example, when the UE does not receive high-layer signaling that explicitly indicates the application of CBG-based A / N for type 3 codebook (for example, when Oneshot-feedback-CBG is not included), even for a CC configured for CBG unit transmission (retransmission) (for example, Figure 20 CC#m in (c) or Figure 20 CC in (d) of , the UE may also operate to generate / map / send TB level A / N for each HARQ process ID.

[0428] Although not limited thereto, as an additional method of reducing the transmission / reception overhead of the payload of the A / N feedback based on the type 3 codebook, the above-mentioned spatial bundling (e.g., Figure 21). A UE configured to feed back TB-level A / N for a CC configured for CBG unit transmission (retransmission) (e.g., without Oneshot-feedback-CBG) may be configured to additionally perform spatial bundling. Spatial bundling A / N may be generated by bundling A / N between CBs or between CBGs corresponding to the same single HARQ process ID. For example, TB-level A / N may be generated by applying a logical AND operation between the CB-level A / Ns of each of a plurality of CBs or between the CBG-level A / Ns of each of a plurality of CBGs. Therefore, bundling A / N between CBs or CBGs corresponding to the same HARQ process ID may be understood as the same meaning of performing a logical AND operation between TB-level A / Ns corresponding to the same single HARQ process ID (e.g., Figure 21 (f) CC or Figure 21 CC#m in (h).

[0429] As a result, the A / N payload size and PUCCH resource overhead based on the type-3 codebook can be reduced.

[0430] In addition, if the A / N feedback transmission is not based on the type 3 codebook (for example, the type 1 / 2 codebook), for the CC configured with CBG unit transmission (retransmission), it can be operated to generate / map / send CBG level A / N for the corresponding PDSCH (or HARQ process ID).

[0431] Figure 18 The A / N transmission based on the type 3 codebook according to the embodiment of the present disclosure is illustrated. Figure 18 It is assumed that Oneshot-feedback-CBG is not configured for the UE.

[0432] Reference Figure 18, the UE may receive at least one PDSCH from the base station on a carrier (e.g., CC) configured for CBG-level transmission (S1802). Thereafter, the UE may send control information (e.g., UCI via PUCCH or PUSCH) including A / N information of the at least one PDSCH to the base station (S1804). Here, the at least one PDSCH includes a CBG corresponding to each TB and may be associated with one of all HARQ process IDs of the carrier. Here, based on the control information configured according to the HARQ process ID of all HARQ process IDs of the carrier (e.g., when indicating A / N feedback transmission based on a type 3 codebook), even if CBG-level transmission is configured for the carrier (based on the fact that Oneshot-feedback-CBG is not configured for the UE), the A / N information of each HARQ process ID of the carrier may be configured as TB-level A / N information. In addition, based on the time slot index of at least one PDSCH of the carrier or the control information configured by the DAI (for example, when A / N feedback transmission based on the type 3 codebook is not indicated, or when A / N feedback transmission based on the type 1 / 2 codebook is indicated), the A / N information of at least one PDSCH can be configured as CBG-level A / N information (regardless of whether Oneshot-Feedback-CBG is configured for the UE). For example, the Oneshot-feedback-CBG parameter can be understood as a parameter that is restrictively applied to the type 3 codebook rather than the type 1 / 2 / 2a codebook.

[0433] Here, the size of the CBG level A / N information is based on the maximum number of CBGs configured for the carrier and may be larger than the size of the TB level A / N information.

[0434] Here, the UE may further receive DCI before step S1804, and based on the codebook type information (eg, CTI) in the DCI, may configure control information for the entire HARQ process ID of the carrier.

[0435] Therefore, when A / N feedback transmission based on type 3 codebook is indicated, for a CC configured for CBG-based transmission (retransmission), whether to generate / send TB-level A / N or generate / send CBG-level A / N can be configured by a higher-layer signal (e.g., the Oneshot-feedback-CBG parameter sent via RRC signaling).

[0436] Figure 19 A / N transmission according to an embodiment of the present disclosure is illustrated.

[0437] Reference Figure 19, the A / N payload (1902) including the A / N of the PDSCH through the CC (or cell) can have different A / N codebook configuration methods according to the situation. First, when the A / N feedback transmission based on the type 3 codebook is not indicated for the CC (for example, when the A / N feedback transmission based on the type 1 or 2 codebook is indicated (for example, the A / N feedback transmission based on the time slot index or the DAI is indicated)) (1904), depending on whether the CBG-based transmission is configured for the CC, the UE can configure the TB-level A / N or CBG-level A / N (not based on the HARQ process ID; for example, based on the time slot index or based on the DAI) for the PDSCH received in the CC (Case 1).

[0438] In addition, if the A / N feedback transmission based on the type 3 codebook is indicated for the CC (via DCI) (1906a), the UE can perform different A / N codebook configuration methods related to the type 3 codebook based on higher layer (e.g., RRC) signaling (1906b). Figure 19 In order to facilitate the description of the UE processing of generating an A / N payload based on the type 3 codebook, 1906a is shown before 1906b. Those skilled in the art can understand that in the real-time domain, the UE first receives the RRC signaling corresponding to 1906b, and then receives the indication of 1906a (the indication of performing A / N feedback transmission based on the type 3 codebook through DCI).

[0439] Specifically, for a CC configured with CBG unit transmission (retransmission), the higher-layer (e.g., RRC) signaling (1906b) related to the type 3 codebook may include information indicating whether to generate / send TB-level A / N or CBG-level A / N (e.g., Oneshot-feedback-CBG parameter). When the generation of CBG-level A / N is indicated (e.g., when the Oneshot-feedback-CBG parameter is included in the higher-layer signaling 1906b), as in Case 1, depending on whether CBG-based transmission is configured for the CC, the UE may configure TB-level A / N or CBG-level A / N (based on the HARQ process ID) for all HARQ process IDs of the CC (Case 2) (e.g., in Figure 20 (a) or (c) of the preceding text).

[0440] On the other hand, when the TB level A / N is generated (for example, when the Oneshot-feedback-CBG parameter is not included in the high-layer signaling 1906b), as shown in FIG. Figure 18 As described, even if CBG-based transmission is configured for a CC, the UE may configure TB-level A / N (based on HARQ process ID) for all HARQ process IDs of the CC (case 3) (e.g., Figure 20 (d)).

[0441] Furthermore, when CBG-based transmission is not configured for a CC (i.e., when TB-based transmission is configured), the UE can always configure the CC's A / N information as TB-level A / N, regardless of the codebook type of the A / N payload. The generated A / N payload (1902) is transmitted from the UE to the base station. The base station can interpret the A / N information in the A / N payload according to the A / N configuration method and perform PDSCH transmission (retransmission) based on the A / N information.

[0442] (c) Handling of A / N Feedback Misalignment

[0443] When A / N feedback transmission based on a type 1 (or type 2 or type 2a) codebook is configured, the UE may feedback / send an ACK for HARQ process ID = X at a specific time (e.g., time slot #n). Thereafter, A / N feedback transmission based on a type 3 codebook at another specific time (e.g., time slot #(n+K)) may be indicated from the base station to the UE. In addition, when a specific DCI schedules a PDSCH corresponding to HARQ process ID = X, the specific DCI may indicate the same time as the time (e.g., time slot #(n+K)) at which the A / N transmission timing for the PDSCH indicates A / N transmission based on the type 3 codebook. If the UE fails to detect the corresponding DCI, A / N feedback misalignment (e.g., DTX to ACK error) may occur between the UE and the base station for HARQ process ID = X in the type 3 codebook. This may unnecessarily result in inefficient (RLC-level) retransmissions.

[0444] To address the above issue, if a specific time (e.g., time slot Y) is indicated as the A / N transmission time based on the type 3 codebook, the UE does not expect (receive) DCI indicating time slot Y as the A / N transmission timing while scheduling PDSCH transmission (and / or scheduling the initial transmission of a new TB (or an NDI value indicating switching), and can operate under the assumption that such DCI does not exist. Therefore, when receiving / receiving DCI as described above, the UE can ignore the DCI. For example, the UE may not perform the operation indicated by the corresponding DCI.

[0445] For example, when a first DCI indicates that a UE is to perform A / N transmission based on a type 3 codebook in a specific time slot, the UE may assume that a second DCI that schedules a PDSCH and indicates the timing of A / N transmission in the same specific time slot will not be received. Despite this assumption, upon receiving the second DCI, the UE may ignore the second DCI and not perform an operation based on the second DCI.

[0446] For example, for a PDSCH corresponding to a specific HARQ process ID = X based on any codebook type (e.g., type 1 / 2 / 2a / 3 codebook), it is assumed that the time when the UE reports (transmits) an ACK may be time slot Y, and thereafter, the time indicated as the HARQ-ACK feedback transmission timing (the initial HARQ-ACK feedback time corresponding to HARQ process ID = X) based on the specific codebook type (e.g., type 3 codebook) is time slot Z. In this case, for the interval from time slot Y (or a specific (next time slot) time after the corresponding time slot Y) to time slot Z (or the time before the UE's minimum PDSCH processing time from the PUCCH start symbol indicated in the corresponding time slot Z), the UE may operate under the assumption that DCI scheduling a PDSCH corresponding to HARQ process ID = X (and / or scheduling the initial transmission of a new TB (or an NDI value indicating switching)) is not expected and that no such DCI exists. When the UE receives DCI as described above, the UE may operate to discard the DCI.

[0447] In addition, when the type 3 codebook is configured, based on any codebook type (e.g., type 1 / 2 / 2a / 3 codebook), the UE can operate to report (transmit) the ACK for PDSCH #1 corresponding to a specific HARQ process ID = X only once in the first A / N feedback time (and then reset the A / N state of the corresponding HARQ process ID = X to DTX or NACK). Therefore, if there is no additional PDSCH scheduling for the corresponding HARQ process ID = X from the initial A / N feedback time of PDSCH #1 to the next A / N feedback time, the UE can operate to report the A / N corresponding to the corresponding HARQ process ID = X as DTX / NACK. On the other hand, if there is scheduling of an additional PDSCH #2 corresponding to HARQ process ID = X from the initial A / N feedback time of PDSCH #1 to the next A / N feedback time, the UE may operate to 1) report an ACK or NACK corresponding to the decoding result of PDSCH #2 if the corresponding PDSCH #2 is a transmission of new data (TB) (scheduled by DCI with a switched NDI), or 2) report an ACK (corresponding to the previous A / N state) if the corresponding PDSCH #2 is a retransmission of a previous data transmission (e.g., a TB sent via PDSCH #1) (scheduled by DCI with an unswitched NDI). That is, in case 2, the UE may exceptionally operate to maintain the previous A / N state without resetting it. In addition, the standard / whether to reset the A / N state (to DTX / NACK) may be determined based on whether the UE actually sends A / N feedback (e.g., ACK). As an example, when the UE fails LBT and drops A / N (PUCCH / PUSCH) transmission, the UE may maintain the corresponding A / N state without resetting (eg, with ACK).

[0448] As another method, when the UE feeds back / transmits an A / N for a specific HARQ process ID = X based on a type 3 codebook, the UE may be operated to reset (to DTX or NACK) the A / N state (e.g., ACK) reported (transmitted) for the corresponding HARQ process ID = X at the previous A / N feedback time (based on a random (e.g., type 1 / 2 / 2a / 3) codebook). Therefore, if there is no additional PDSCH scheduling for HARQ process ID = X from the previous A / N feedback time to the feedback time based on the type 3 codebook, the corresponding A / N may be reported as DTX / NACK. If there is an additional PDSCH scheduling for HARQ process ID = X from the previous A / N feedback time to the feedback time based on the type 3 codebook, the UE may operate to 1) report ACK or NACK corresponding to the decoding result of the PDSCH if the additionally scheduled PDSCH is a transmission of new data (scheduled by DCI with a switched NDI), or 2) report ACK (corresponding to the previous A / N state) if the PDSCH is a retransmission of the previous data transmission (scheduled by DCI with an unswitched NDI). That is, in this case, it is possible to exceptionally operate to maintain the previous A / N state without resetting. In addition, even in this case, the standard / whether to reset the A / N state (to DTX / NACK) can be determined according to whether the UE actually sends A / N feedback (e.g., ACK). As an example, when the UE fails to LBT and discards the A / N (PUCCH / PUSCH) transmission, the UE may operate to maintain the corresponding A / N state without resetting (e.g., with ACK).

[0449] Furthermore, for DCI that the UE does not expect and ignores, DCI that schedules PDSCH transmission and simultaneously indicates A / N transmission based on the Type 3 codebook may be excluded. That is, the UE may perform corresponding operations without ignoring the corresponding DCI. For example, the UE may configure / send A / N feedback based on the Type 3 codebook, which includes A / N for the PDSCH scheduled by the corresponding DCI.

[0450] In addition, the UE may be configured (or instructed) to report the A / N feedback and the NDI bit related to the corresponding A / N feedback together. For example, the UE may receive the TB / CBG received via the PDSCH based on the specific DCI used to schedule the PDSCH, and feedback the A / N corresponding to the TB / CBG and transmit the value of the NDI field included in the specific DCI together. For example, a method may be considered in which the NDI bit (most recently) received via the DL grant DCI and the A / N bit of the corresponding PDSCH are fed back together for each HARQ process ID.

[0451] As another method, a method of performing an XOR (exclusive OR) operation on the (most recently) received NDI bit via the DL grant DCI and the A / N bit of the corresponding PDSCH (e.g., NACK for bit "0", ACK for bit "1") for each HARQ process ID can be considered to feed back the calculated bit. For example, the UE can report the result of the XOR operation on the corresponding NDI bit and the corresponding A / N bit.

[0452] In addition, considering the application of the above method, for CCs that configure transmission (retransmission) / feedback in units of CBG and / or CC, where spatial bundling between the A / Ns of each TB is configured (according to a logical AND operation), the following A / N feedback method (for example, including feedback of NDI) can be considered.

[0453] 1) In the case of CC configured for CBG unit transmission

[0454] A. Basics

[0455] i. Assume that the maximum number of CBGs (per TB) configured for the corresponding CC is N.

[0456] B. Option 1

[0457] i. For each HARQ process ID, the UE may operate to feedback N bits calculated by performing an XOR operation on the NDI bit (for each TB) and each of the N A / N bits corresponding to the N CBGs. For example, N XOR operation results may be reported.

[0458] C. Option 2

[0459] i. For each HARQ process ID, the UE may operate to generate a single A / N bit by first applying bundling (according to a logical AND operation) between the A / Ns corresponding to N CBGs (for each TB), and feeding back a single bit calculated by performing an XOR operation on the corresponding A / N bit and the NDI bit.

[0460] D. Option 3

[0461] i. For each HARQ process ID, a single A / N bit is generated by bundling (according to a logical AND operation) the A / Ns corresponding to N CBGs (for each TB), and the corresponding A / N bit and NDI bit (for the corresponding TB) are fed back together. (For example, each HARQ process ID (each TB corresponding to the HARQ process ID) feeds back 1 bit of A / N and 1 bit of NDI.)

[0462] E. Option 4

[0463] i. When CBG unit transmission is not configured (in any CC), the UE may feedback (1 bit) A / N information and (1 bit) NDI information together for each TB of each HARQ ID (for all CCs). Conversely, when CBG unit transmission is configured (in at least one CC), the UE may operate to feedback only the A / N bit of each TB / CBG for each HARQ process ID (for all CCs) (according to the maximum number of TB / CBGs configured in the corresponding CC).

[0464] F. Notes

[0465] i. If the overall decoding result of a TB is ACK in options 1 / 2 / 3 (even if the number of CBGs included in the corresponding TB is less than N), the UE may map ACK bits to all N CBGs.

[0466] 2) In the case of configuration space bundled CC

[0467] A. Basics

[0468] i. Assume that the maximum number of TBs configured for the corresponding CC is at least 2.

[0469] B. Option 1

[0470] i. The UE may operate to generate a single A / N bit by applying spatial bundling between the A / Ns corresponding to multiple TBs for each HARQ process ID, and feed back a single bit calculated by performing an XOR operation on the corresponding A / N bit and the NDI bit corresponding to a specific one TB (among the multiple TBs).

[0471] C. Option 2

[0472] i. The UE may be operated to feed back together a single A / N bit generated by applying spatial bundling between the A / Ns corresponding to multiple TBs for each HARQ process ID and an NDI bit corresponding to a specific TB (among the multiple TBs) (e.g., 1-bit A / N and 1-bit NDI feedback per HARQ process ID).

[0473] D. Option 3

[0474] i. The UE may be operated to feed back together a single A / N bit generated by applying spatial bundling between the A / Ns corresponding to multiple TBs for each HARQ process ID and multiple NDI bits corresponding to each of multiple (e.g., L) TBs (e.g., 1-bit A / N and L-bit NDI feedback per HARQ process ID).

[0475] E. Option 4

[0476] i. In the case of A / N feedback based on the type 3 codebook, as an exception, the UE may operate to not apply the configured spatial bundling and feedback a single bit calculated by performing an XOR operation on the A / N bit and the NDI bit for each TB of each HARQ process ID.

[0477] F. Option 5

[0478] i. In the case of A / N feedback based on the type 3 codebook, as an exception, the UE may operate so as not to apply the configured spatial bundling and to feedback the A / N bit and the NDI bit together for each TB of each HARQ ID (e.g., feeding back 1-bit A / N and 1-bit NDI for each TB of each HARQ ID). For example, in a state where the UE is configured (e.g., by higher layer signaling) to (a) perform A / N feedback through spatial bundling of the corresponding CC (e.g., by higher layer signaling) and (b) report the A / N feedback based on the type 3 codebook and the NDI of the corresponding TB together (e.g., the bit value of the NDI field included in the DL grant DCI for scheduling the corresponding TB), (b) when the DCI of the PDCCH indicates that the A / N feedback based on the type 3 codebook is to be performed, the UE may not perform spatial bundling despite the (a) spatial bundling configuration and report the A / N feedback based on the type 3 codebook and the NDI of the corresponding TB based on the (b) configuration and (c) indication.

[0479] ii. For example, when the UE receives the Oneshot-feedback-NDI parameter through higher-layer signaling, when performing A / N feedback based on a type 3 codebook, the UE may transmit NDI together (e.g., PUCCH or PUSCH). When the UE is configured to report A / N feedback based on a type 3 codebook together with NDI (e.g., receives the Oneshot-feedback-NDI parameter), the UE may not perform spatial bundling for A / N feedback based on a type 3 codebook as an exception. When the base station transmits the Oneshot-feedback-NDI parameter to the UE through higher-layer signaling, the base station may receive A / N feedback based on a type 3 codebook and NDI together. When the base station configures the UE to report A / N feedback based on a type 3 codebook together with NDI (e.g., transmits the Oneshot-feedback-NDI parameter), the base station may assume that spatial bundling is not performed for A / N feedback based on a type 3 codebook as an exception and decode the A / N feedback.

[0480] ....iii. Figure 22 The payload of various A / N feedback based on type 3 codebook according to option 5 is illustrated. Figure 22(i), (j), (k), and (l) of , when spatial bundling and Oneshot-feedback-NDI are configured together for the UE, it is reported that spatial bundling and NDI are not performed exceptionally for A / N feedback based on the type 3 codebook. However, since this exception is applied to A / N feedback based on the type 3 codebook, spatial bundling is still applied to A / N feedback based on the type 1 / 2 / 2a codebook. In addition, as Figure 22 As shown in FIG, NDI may be located at the end of the A / N bits of each TB / CBG. The NDI value of an unscheduled TB may be reported as 0. In addition, assuming that Figure 22 Space bundling is configured in (i), (j), (k) and (l) of FIG. 1 , but even if space bundling is not configured, those skilled in the art will understand that the payload of the A / N feedback based on the type 3 codebook will be the same as Figure 22 (i), (j), (k) and (l) are generated / sent in the same way.

[0481] ....iv. In addition, in this embodiment, when the UE reports NDI together with the A / N feedback process based on the Type 3 codebook, it can be understood that the UE transmits UCI including NDI (e.g., PUCCH transmission or UCI piggybacked on PUSCH). As described above, this embodiment in which the UE transmits NDI via UCI needs to be distinguished from the existing technology in which the UE receives NDI via DCI, and there are significant differences between the two. For convenience, the NDI included in the DL grant DCI used to schedule DL data (e.g., PDSCH) is referred to as DL data NDI, and the NDI included in the UL grant DCI used to schedule UL data (e.g., PUSCH) is referred to as UL data NDI. The number of DL / UL data NDI fields may vary depending on the number of DL / UL TBs (including CBGs) scheduled by the DCI, but each TB (1-TB including CBGs) is associated with one DL / UL data NDI field (e.g., 1 bit). The base station can use the DL data NDI field to inform the UE whether the corresponding DL data transmission (e.g., TB / CBG) is an initial transmission or a retransmission. The base station can use the UL Data NDI field to schedule new UL data transmission or UL data retransmission to the UE. If the corresponding UL data was not correctly received in the previous UL transmission, the base station can use the UL Data NDI field to schedule UL data retransmission. If the corresponding UL data is correctly received, the base station can toggle the UL Data NDI field to schedule new UL data transmission. Therefore, the UL Data NDI can be used similarly to an A / N indicating the base station's UL data reception status and can be related to the base station's HARQ process. Furthermore, according to this embodiment, the NDI in the UCI transmitted by the UE to the base station is sent. When the UE transmits a first A / N for first DL data, the first NDI in the UCI is configured with the same value as the DL Data NDI associated with the first DL data. When the UE transmits a second A / N for second DL data, the second NDI in the UCI is configured with the same value as the DL Data NDI associated with the second DL data. For example, the NDI in the UCI can be understood as being used to report the DL Data NDI associated with the corresponding A / N included in the UCI to the base station. Since the DL data NDI is a value already known by the base station, there has been no process in the past for the UE to send the received DL data NDI via UCI (e.g., UL control NDI). However, as the number of A / N bits sent and received between the UE and the base station increases due to an increase in the number of CCs configured in a UE, an increase in the number of HARQ processes, and CBG-based transmission, a method is needed to more efficiently identify and handle the portion and cause of A / N misalignment errors. To this end, the UE can report the DL data NDI together with the A / N feedback based on the Type 3 codebook.Therefore, if DL data NDI is reported via UCI (e.g., reporting the first NDI and the second NDI separately), accurately reporting the A / N bits of each TB (each CBG) may be more important than reducing the overhead of UCI. Therefore, it may be desirable that despite the spatial bundling configuration, a UE configured to report NDI via UCI does not perform a logical AND operation on the A / N of the first TB and the A / N of the second TB, but instead reports the A / N of each of the first TB and the second TB separately.

[0482] ....v. Figure 23 The A / N transmission based on the type 3 codebook according to the embodiment of the present disclosure is illustrated. Specifically, Figure 23 is based on Figures 17 to 22 One of the examples of UE / base station operation of the embodiment, and for convenience, the above may be omitted. Figures 17 to 22 The scope of this disclosure is not limited to the content described Figure 23 .

[0483] Reference Figure 23 The UE may receive a configuration related to the HARQ-ACK response from the network (from at least one base station) through higher layer signaling (2305). For example, a configuration related to the HARQ-ACK response per cell group may be provided through an RRC reconfiguration message or an RRC setup message (e.g., spatial bundling, HARQ-ACK-OneShotFeedback, HARQ-ACK-OneShotFeedback NDI and / or HARQ-ACK-OneShotFeedback CBG), but is not limited thereto.

[0484] The UE may receive one or more PDCCHs (2310) from the network (from at least one base station) through at least one DL CC. The PDCCH may include a DL grant DCI for scheduling a PDSCH. The DL grant DCI may include a field indicating the HARQ process index of the corresponding PDSCH (HARQ process number), a field indicating whether the TB (including CBG) of the corresponding PDSCH is newly transmitted or retransmitted (new data indicator, NDI), and a field indicating when the UE should send a HARQ-ACK response to the corresponding PDSCH to the base station (PDSCH-to-HARQ_feedback timing indicator). When the DCI grant DCI has a specific DCI format, the DCI grant DCI may also include a field indicating whether A / N feedback based on a type 3 codebook is requested (one-time HARQ-ACK request).

[0485] The UE may receive one or more PDSCHs (2315) from the network (from at least one base station) through at least one DL CC. The PDCCH and PDSCH may be received on the same DL CC, or may be received on different DL CCs based on a cross-carrier scheduling scheme. The PDSCH may include one (2310) scheduled by the received PDCCH, but is not limited thereto and may include, for example, an SPS PDSCH.

[0486] The terminal may send a HARQ-ACK response (2320, 2330) to the network (to at least one base station) for the received PDSCH. The HARQ-ACK response may include A / N feedback (2325 Yes, 2330) based on the Type 1 / 2 / 2a (2320) and / or Type 3 codebook. The HARQ-ACK response may be sent via UCI of the PUCCH or PUSCH.

[0487] For example, at the HARQ-ACK transmission timing indicated by the DCI of the received PDCCH (2310), the A / N (2320, for example) of the DL data scheduled by the corresponding DCI may be transmitted based on the type 1, 2, or 2a codebook. Figure 19 Case 1). The UE may determine the type of codebook on which the HARQ-ACK response is based from type 1, 2, or 2a codebooks according to higher layer signaling (2305) (e.g., semi-static / dynamic).

[0488] In addition, when the higher layer signaling (2305) includes a HARQ-ACK feedback configuration based on a type 3 codebook and indicates a HARQ-ACK based on a type 3 codebook (e.g., a one-time HARQ-ACK request) to the UE via DCI, the UE may generate a HARQ-ACK based on the type 3 codebook and send it to the network (2330). The DCI indicating the HARQ-ACK based on the type 3 codebook may be one of the PDCCHs (2310) or may be received by the UE via a separate PDCCH (not shown).

[0489] As described above, for mapping of each A / N bit in the HARQ-ACK payload based on the type 3 codebook, the “first TB / CBG index - second HARQ process index - third CC index” method can be used (e.g., Figures 20 to 23 ), but are not limited to.

[0490] When the CC is a CC that performs CBG-based transmission / scheduling (2335 CBG), and CBG-based A / N reporting is configured for the corresponding CC through higher layer signaling even in HARQ-ACK based on type 3 codebook (2340 is, one-time feedback CBG) (2305), the UE may use the CBG-based A / N bits (e.g., Figure 19 In addition, when it is configured to include NDI in HARQ-ACK based on type 3 codebook (2345 is) (for example, one-time feedback NDI configuration), the UE can report NDI together (2355) (for example, Figure 22 Otherwise (No at 2345), the A / N bits of the corresponding CC may be mapped to a HARQ-ACK response based on a type 3 codebook based on the CBG without NDI (2350) (e.g., Figure 20 (a), (c)).

[0491] Even if the CC is a CC that performs CBG-based transmission / scheduling (2335 CBG), when CBG-based A / N reporting is not configured for the corresponding CC through higher layer signaling even in HARQ-ACK based on type 3 codebook (2305) (2340 No) (e.g., Figure 18 or Figure 19 Case 3), the TB-based A / N bits of the corresponding CC can be mapped to the HARQ-ACK response based on the type 3 codebook. If the CC is a CC that performs TB-based transmission / scheduling (2335TB), the A / N bits based on the type 3 codebook of the corresponding CC can be determined regardless of whether there is a one-time feedback CBG parameter configuration.

[0492] When spatial bundling is configured by higher layer signaling (2305) (2360 Yes) and configured not to include NDI in the HARQ-ACK based on the type 3 codebook (2365 No), the UE performs spatial bundling (e.g., a logical AND operation on the A / N based on the TB) per HARQ process to map the A / N bits of the corresponding CC to the HARQ-ACK response based on the type 3 codebook (2370) (e.g., Figure 21 ).

[0493] If spatial bundling is not configured through higher layer signaling (2305) (2360 No) and NDI is not included in the HARQ-ACK based on the type 3 codebook (2380 No), the UE may map the TB-based A / N bits of the corresponding CC to the HARQ-ACK response based on the type 3 codebook (2385) (e.g., Figure 20 (b), (d)).

[0494] When spatial bundling is configured by higher layer signaling (2305) (2360 Yes), and configured to include NDI in type 3 codebook-based HARQ-ACK (2365 Yes), the UE may generate / report TB-based A / N bits and NDI for type 3 codebook-based HARQ-ACK without spatial bundling (2375) despite the spatial bundling configuration (e.g., Figure 22 (j), (l)).

[0495] When spatial bundling is not configured through higher layer signaling (2305) (2360 No) and NDI is included in HARQ-ACK based on type 3 codebook (2380 Yes), the UE can generate / report TB-based A / N bits and NDI (2375) for the corresponding CC.

[0496] G. Option 6

[0497] i. If spatial bundling is not configured (e.g. Figure 23 2360 No), (for all CCs) whether the UE feeds back (1 bit) A / N information and (1 bit) NDI information for each TB of each HARQ process ID together, or whether the base station configures only A / N information for each TB (1 bit) of each HARQ process ID (for example, feeding back NDI information once, Figure 23 2380) (UE provides feedback according to the corresponding configuration, for example, Figure 23 2385 / 2375). When the configuration space is bundled (for example, Figure 23 2360 is), (for all CCs) (according to the maximum number of TBs configured for the corresponding CC) only a single (bundled) A / N bit for a single TB or multiple TBs is fed back for each HARQ ID (e.g., Figure 23 2370).

[0498] H. Notes

[0499] i. In option 1 / 2, a specific TB (corresponding to the NDI bit of the feedback) can be applied as the TB with the lowest / highest index.

[0500] In addition, in the above, when the method of feeding back the NDI bit and the A / N bit together for each HARQ process ID (for each TB) is applied, when the PUCCH resource is determined based on the corresponding UCI payload size and the PRI indication through the DCI, even if all the frequency / time resources configured for the corresponding PUCCH are used, due to the larger UCI payload size, a situation may occur where the maximum UCI coding rate (configured in the corresponding PUCCH) is exceeded. In this case, it is possible to operate to omit (discard) the transmission of the NDI bit (all or a specific part) in the proposed feedback.

[0501] In addition, when the A / N feedback operation based on the type 1 / 2 / 2a codebook is configured, when the A / N feedback based on the type 3 codebook can be dynamically indicated through the DCI, the counter DAI field and / or the total DAI field and / or the current ID (and feedback ID or total ID) field and / or the NFI field in the corresponding DCI (configured for the type 1 / 2 / 2a codebook) can be used to indicate which CC / HARQ group (among multiple predefined / configured CC groups and / or multiple HARQ (process ID) groups) the UE is sending A / N feedback for. A method can be considered.

[0502] And / or, in the case where an A / N feedback operation based on a type 1 / 2 / 2a codebook is configured, when the transmission of A / N feedback based on a type 3 codebook is dynamically indicated through DCI, the corresponding DCI (e.g., a separate field (configured for the type 1 / 2 / 2a codebook) or a counter DAI field, a total DAI field, a current ID (and feedback-ID or total ID) field, and / or an NFI field) can indicate whether only A / N feedback for each HARQ process ID is to be transmitted for the entire (or a specific as indicated above) CC / HARQ group, or whether the A / N feedback and the corresponding NDI are to be transmitted together.

[0503] In addition, in the case where a candidate A / N timing set can be indicated by DCI indicating A / N feedback based on a type 3 codebook (for the same CC or BWP), a candidate A / N timing set can be configured by DCI indicating A / N feedback based on a type 1 / 2 / 2a codebook, or they can be configured independently of each other (for example, the sets are configured with different A / N timing values).

[0504] (d) PDSCH processing indicating A / N pending

[0505] First, in a state where the type 1 A / N codebook method is configured for the UE, when a PDSCH for which A / N is pending is indicated by a specific DL grant DCI (for example, in the form of an invalid or non-digital value indicated in the A / N timing of the PDSCH), for the A / N feedback of the corresponding PDSCH (for convenience, referred to as "pending A / N"), 1) (by the UE) an operation of sending the corresponding pending A / N in the form of a type 3 A / N codebook by indicating separate A / N pooling via DCI, or 2) an operation of appending the corresponding pending A / N to the type 1 A / N codebook sent by A / N timing indicated by another DL grant DCI (for example, in the form of a valid or digital value indicated in the A / N timing of the PDSCH) without separate A / N pooling can be considered. In addition, when considering the operation of configuring and transmitting the A / N payload in the form of appending the pending A / N to the type 1 A / N codebook as described above, it is necessary to configure / perform mapping so that 1) the total number of pending A / N information / bits to be appended and 2) the mapping order of the corresponding pending A / N information / bits on the A / N payload match between the UE and the base station. If there is a mismatch between the UE and the base station regarding the number / mapping of the pending A / N on the A / N payload, unnecessary PDSCH retransmission overhead and large delay may occur due to deterioration of UCI decoding performance and generation of severe ACK / NACK errors (e.g., NACK to ACK).

[0506] Considering the above problem, the (maximum) pending A / N information / number of bits (e.g., P bits) that can be appended to the Type 1 A / N codebook can be configured to the UE (by the base station) via RRC signaling, and the UE can be operated to always append the corresponding P bits to the Type 1 A / N codebook regardless of whether there is an actual pending A / N. As another method, the presence of a pending A / N (or whether to append P bits) can be indicated to the UE (by the base station) via a specific (e.g., 1-bit) field in the DCI (e.g., DL grant). Based on the information indicated by the corresponding field, the UE can be operated to configure the final A / N payload in the form of appending or not appending the pending A / N bits (or corresponding P bits) to the Type 1 A / N codebook. As another method, multiple candidates (having different values ​​including 0) for the additional pending A / N bit number P can be configured to the UE (via RRC), and the value of one of the candidates can be indicated by a specific field in the DCI (e.g., DL grant), and the terminal can operate to configure the final A / N payload by appending the number of bits corresponding to the indicated value to the type 1 A / N codebook.

[0507] In addition, the final A / N payload may be configured in such a manner that the type 1 A / N codebook is preferentially mapped to the lower bit index portion starting from the most significant bit (MSB) (e.g., configured as the first A / N subcodebook), and then the pending A / N information is mapped thereafter (to the higher bit index portion) (e.g., configured as the second A / N subcodebook). In addition, in order to match the mapping order between the pending A / N information / bits on the A / N payload, a sequence value (e.g., a counter DAI) of the number of times the PDCCH / PDSCH corresponding to the A / N pending indication to the UE is scheduled / transmitted (among all PDCCHs / PDSCHs indicating A / N pending) may be indicated (by the base station) through a specific field in the DCI (e.g., DL grant) indicating the A / N pending operation. The UE may be operated to configure the final A / N payload in the form of the additionally configured / mapped pending A / N bits (payload) according to the order of the corresponding sequence values ​​(in the type 1 A / N codebook). In this case, the field indicating the sequence value in the DCI (e.g., DL grant) can be applied as a field for counter DAI signaling, or can be determined / considered as a field for allocating PUCCH resources (to be used for A / N feedback transmission) (e.g., PUCCH resource indicator, PRI).

[0508] In addition, when an A / N pending operation is indicated for a corresponding PDSCH via DCI (e.g., DL grant) at a specific time, (pending) A / N feedback for the corresponding PDSCH may be transmitted at a later specific time using A / N timing indicated by another DCI (as an A / N feedback timing based on the type 1 codebook). In this case, it may be necessary to determine the corresponding A / N timing (at which the pending A / N is to be transmitted). To this end, whether to (additionally) transmit a pending A / N (for a PDSCH for which A / N pending was indicated at a previous time) may be directly indicated at the A / N timing indicated by the corresponding DCI via each DCI (e.g., triggering A / N feedback based on the type 1 codebook). As another method, the corresponding pending A / N may be transmitted by (by adding) the earliest A / N timing among the A / N timings indicated by DCI (e.g., indicating the A / N timing as a valid or digital value and triggering A / N feedback based on the type 1 codebook) transmitted after the (DCI or PDSCH transmission) time indicating that the A / N is pending (or the earliest A / N timing after the minimum PDSCH processing time of the UE from the PDSCH transmission time indicating that the A / N is pending, or the time indicated as the first A / N timing after the minimum PDSCH processing of the UE from the PDSCH transmission time indicating that the A / N is pending). As another method, the corresponding pending A / N may be transmitted by (by adding) the A / N timing indicated by the initial DCI (e.g., triggering A / N feedback based on the type 1 codebook and indicating the A / N timing as a valid or digital value) transmitted in (the same time slot) or after the PDSCH transmission time indicating that the A / N is pending. As another method, the corresponding pending A / N may be transmitted by (by adding) the A / N timing indicated by the DCI for scheduling the first PDSCH to be transmitted (in the same time slot) or after the PDSCH transmission time indicating the pending A / N (e.g., triggering A / N feedback based on the type 1 codebook and indicating the A / N timing as a valid or digital value).

[0509] In addition, to prevent mismatches in the A / N payload between the UE and the base station, a method of configuring / designating the time when pending A / N transmission is allowed (by appending to the Type 1 A / N codebook and transmitting at the same UL time) as described above may be considered. Specifically, when an A / N pending operation is indicated for a PDSCH transmitted in slot #n or via a DCI (e.g., a DL grant) transmitted in slot #n, it may be configured / designated so that the corresponding pending A / N transmission is allowed only via a PUCCH (PUSCH) (carrying the Type 1 A / N codebook) transmitted via a time period including slot #(n+T) / and / or including slot #(n+T+F) / and before a time period including slot #(n+T+F) / . In addition, when the PDSCH reception time slot corresponding to the pending A / N coincides with slot X included in the bundling window corresponding to the A / N transmission timing indicated by the random DCI (e.g., a DL grant), the UE may configure the Type 1 A / N codebook for the bundling window in a manner that maps the corresponding pending A / N information / bit to the A / N bit corresponding to the corresponding slot X.

[0510] In addition, when the Pcell is scheduled and includes a DL fallback DCI with a counter DAI=1 (for convenience, the corresponding A / N is defined as "fallback A / N") indicating a specific A / N timing and there is no other DL authorization DCI indicating the corresponding A / N timing, according to the above scheme (or other schemes), the corresponding A / N timing can be determined as the timing of (additionally) sending a pending A / N (for the PDSCH indicating that A / N is pending at a previous time). In this case, the UE may: Option 1) operate to feed back / transmit the fallback A / N and the corresponding pending A / N together through A / N timing; or Option 2) operate to feed back / transmit only the fallback A / N (the same as before) through A / N timing (therefore, in this case, as an exception, operate not to add / feed back the pending A / N through the A / N timing indicated for fallback A / N transmission); or Option 3) operate to feed back / transmit through A / N timing by adding the corresponding pending A / N to the entire type 1 codebook (therefore, in this case, fallback A / N transmission is performed only through A / N timing that is not determined as the pending A / N feedback / transmission time).

[0511] In addition, when the type 2 A / N codebook method is configured for the UE, in a case where the A / N of the PDSCH to be determined is indicated by a specific DL grant DCI (for example, in the form of the A / N timing of the PDSCH being indicated as invalid or non-digital value), for the (pending) A / N feedback of the corresponding PDSCH, 1) (by the UE) transmitting the corresponding pending A / N in the form of a type 3 A / N codebook by indicating separate A / N pooling via a specific DCI, or 2) without separate A / N pooling, the corresponding pending A / N is appended to the type 2 A / N codebook transmitted by the A / N timing indicated by another DL grant DCI (for example, in the form of the A / N timing of the PDSCH being indicated as valid or a digital value) can be considered. Similarly, when considering the operation of configuring and transmitting the A / N payload in the form of appending the pending A / N to the type 2 A / N codebook as described above, it is necessary to configure / perform mapping so that 1) the total number of pending A / N information / bits to be appended and 2) the mapping order of the corresponding pending A / N information / bits on the A / N payload match between the UE and the base station (in terms of UCI decoding performance and PDSCH retransmission overhead / delay).

[0512] In view of this, in order to match the total number of corresponding pending A / N information / bits on the A / N payload (between the UE and the base station) and the mapping order between the pending A / N information / bits, a specific field in the DCI (e.g., DL grant) indicating the A / N pending operation can be used to inform (by the base station) the number of times (a sequence value, e.g., a counter DAI) that the PDCCH / PDSCH corresponding to the A / N pending indicated by the DCI is scheduled / transmitted (among all PDCCHs / PDSCHs indicating A / N pending) and / or the total number (a total value, e.g., a total DAI) of PDCCHs / PDSCHs for which A / N pending has been indicated to the UE up to the current time. Therefore, the UE can configure the final A / N payload in the form of appending pending A / N bits (payload) configured / mapped in the order of the corresponding total value and / or the corresponding sequence value (to the type 2 A / N codebook). In addition, the final A / N payload may be configured in such a manner that the type 2 A / N codebook is preferentially mapped to the lower bit index portion starting with the MSB (for example, configured in the form of the first A / N sub-codebook), and then the pending A / N information is mapped thereafter (to the higher bit index portion) (for example, configured in the form of the second A / N sub-codebook).

[0513] In addition, when an A / N pending operation is indicated for a corresponding PDSCH via DCI (e.g., DL grant) at a specific time, (pending) A / N feedback for the corresponding PDSCH may be transmitted at a later specific time using A / N timing indicated by another DCI (as an A / N feedback timing based on a type 2 codebook). In this case, it may be necessary to determine the corresponding A / N timing (at which the pending A / N is to be transmitted). To this end, whether to (additionally) transmit a pending A / N (for a PDSCH for which A / N pending was indicated at a previous time) may be directly indicated at the A / N timing indicated by the corresponding DCI via each DCI (e.g., triggering A / N feedback based on a type 2 codebook). As another method, the corresponding pending A / N may be transmitted by (by adding) the earliest A / N timing among the A / N timings indicated by DCI (e.g., indicating the A / N timing as a valid or digital value and triggering A / N feedback based on the type 2 codebook) transmitted after the (DCI or PDSCH transmission) time indicating that the A / N is pending (or the earliest A / N timing after the minimum PDSCH processing time of the UE from the PDSCH transmission time indicating that the A / N is pending, or the time indicated as the first A / N timing after the minimum PDSCH processing of the UE from the PDSCH transmission time indicating that the A / N is pending). As another method, the corresponding pending A / N may be transmitted by (by adding) the A / N timing indicated by the initial DCI (e.g., triggering A / N feedback based on the type 2 codebook and indicating the A / N timing as a valid or digital value) transmitted in (the same time slot) or after the PDSCH transmission time indicating that the A / N is pending. As another method, the corresponding pending A / N may be transmitted by (by adding) the A / N timing indicated by the DCI for scheduling the first PDSCH to be transmitted (in the same time slot) or after the PDSCH transmission time indicating the pending A / N (for example, triggering A / N feedback based on the type 2 codebook and indicating the A / N timing as a valid or digital value).

[0514] In order to support an operation of adding A / N feedback for a PDSCH indicating that A / N is pending to a type 1 / 2 A / N codebook and transmitting it, the following method may be considered by combining the above methods (or in addition to the above methods).

[0515] 1) A / N payload size of the PDSCH used to indicate the A / N to be determined

[0516] A. Option 1

[0517] i. For each CC or BWP (which may be a single A / N feedback configuration), the maximum number Np of PDSCHs for which the A / N is to be determined may be indicated through RRC configuration.

[0518] B. Option 2

[0519] i. For each CC or BWP (which may be a single A / N feedback configuration), the maximum number Np of PDSCHs that may indicate that the A / N is pending is predefined.

[0520] 1. As an example, when the minimum value among the valid or digital value A / N timing configured in CC / BWP is defined as Tm, it can be determined that Np=Tm-a (a=1 (or 0, 2)).

[0521] A) Alternatively, Np=b×(Tm−a) may be determined. Depending on the UE capability as to whether multiple PDSCH receptions are possible in a single time slot, b may be an integer greater than 1.

[0522] 2) A / N sorting method for PDSCH with pending A / N

[0523] A. Option 1

[0524] i. Signaling / applying a counter DAI used only to indicate the A / N pending PDSCH individually / independently for each CC (within the corresponding CC).

[0525] 1. In this case, the pending A / N payload may be configured by mapping A / N corresponding to the counter DAI value from 1 to Np for each CC.

[0526] 2. In this case, the number of A / N bits corresponding to one counter DAI value of each CC may be determined to be the same as the maximum number of TBs or CBGs configured for the corresponding CC.

[0527] B. Option 2

[0528] i. Signal / apply the counter DAI (and total DAI) only for PDSCH indicating A / N pending on the entire CC (in a CC-first then time approach).

[0529] 1. In this case, the counter DAI value may be signaled / applied to have continuous values ​​starting from the PDSCH indicating that the A / N is pending to the DCI (sent later) requesting A / N feedback for the corresponding PDSCH.

[0530] A). For example, if the last counter DAI value corresponding to the PDSCH indicating A / N pending is X, then thereafter, the counter DAI value corresponding to the (first) DCI requesting A / N feedback for the corresponding PDSCH may be signaled / applied as (X+1).

[0531] 2. In this case, the entire A / N payload is configured by sequentially mapping A / N starting from the counter DAI value corresponding to the PDSCH indicating that A / N is pending to the last received counter DAI (or total DAI) value.

[0532] 3) Indicates the A / N feedback time of the PDSCH with pending A / N

[0533] A. Option 1

[0534] i. Whether to add and transmit (e.g., request) or not to add and transmit (e.g., not request) the (pending) A / N feedback of the PDSCH indicating that the A / N is pending (at the previous time) is indicated (to the type 1 / 2 A / N codebook) through the A / N timing indicated by the DCI (e.g., DL grant).

[0535] 1. In the above, when the indication is "request", the (pending) A / N feedback is added to the type 1 / 2 A / N codebook and sent, and when the indication is "not requested", only the type 1 / 2 A / N codebook is sent without adding the (pending) A / N feedback.

[0536] 2. In this case, the A / N status at each (pending) A / N feedback time may always be reset after feedback transmission. For example, the A / N status at a specific A / N feedback time resets the A / N status fed back at the previous (most recent) time, and is then determined to be updated based on whether there is a PDSCH indicating that the A / N is pending.

[0537] B. Option 2

[0538] i. Indicate the NFI information of the (pending) A / N feedback corresponding to the PDSCH indicating A / N pending through DCI (e.g., DL grant) (as an example, whether the A / N status of the previous (most recent) feedback is reset and updated (depending on whether there is another PDSCH indicating A / N pending) or the A / N status of the previous (most recent) feedback is maintained), and transmit the (pending) A / N feedback reflecting the corresponding NFI information through the A / N timing indicated by the DCI (in addition to the type 1 / 2 codebook).

[0539] 1. In this case, pending A / N feedback is always added to the type 1 / 2 codebook and transmitted, or when NFI is not switched (or indicates that the previous A / N state is maintained), pending A / N feedback may always be added to the type 1 / 2 codebook and transmitted, and when NFI is switched (or indicates resetting the previous A / N state), if there is a PDSCH (after the previous feedback time) that further indicates that A / N is pending, pending A / N feedback is added / transmitted, but if not, pending A / N feedback is not added / transmitted.

[0540] 2. In the above, NFI is signaled through a separate bit / field in DCI, or in a state where the entire PUCCH resource set is divided into a resource group corresponding to non-switched NFI (or maintaining the previous A / N state) and a resource group corresponding to switched NFI (or resetting the previous A / N state), the corresponding NFI value can be determined according to the PUCCH resource indicated by DCI.

[0541] In addition, in a state where the type 2a A / N codebook method is indicated to the UE, when the PDSCH in which the A / N is pending is indicated by a specific DL grant DCI (and a specified (PDSCH) time slot group ID = X is specified), for the (pending) A / N feedback of the corresponding PDSCH, it can be considered that 1) the corresponding pending A / N is sent in the form of a type 3 A / N codebook by indicating separate A / N pooling via a specific DCI (by the UE), or 2) the corresponding pending A / N is included in the type 2a A / N codebook transmitted at the A / N timing indicated by another DL grant DCI (e.g., requesting A / N feedback of time slot group ID = X) without separate A / N pooling. In addition, in the latter case, it may be necessary to determine the corresponding A / N timing for transmitting pending A / N feedback. As a method of this, the pending A / N is transmitted by the earliest A / N timing (by addition) among the A / N timings indicated by a specific DCI (e.g., requesting A / N feedback for slot group ID = X (simultaneously triggering A / N feedback based on the type 2a codebook)) transmitted after the time indicating that A / N is pending (for DCI or PDSCH transmission).

[0542] In addition, therefore, the A / N feedback transmission time of the PDSCH indicating that the A / N is pending can be determined as the A / N timing indicated by the DCI detected / received after the corresponding PDSCH reception time. In this case, PUCCH or PUSCH transmission carrying specific A / N information (e.g., A / N information corresponding to SPS PDSCH reception) at a specific time before the A / N timing time or the DCI reception time can be configured / instructed / performed. In this case, there is a possibility that out-of-order (OOO) may occur during HARQ operation, which may cause signal processing complexity in the UE implementation. For example, the A / N feedback of PDSCH #2 of another (or the same) HARQ process ID received after the PDSCH #1 reception time of a specific HARQ process ID is sent before the A / N feedback time of PDSCH #1.

[0543] Therefore, in order to avoid the OOO operation situation, the A / N feedback transmission time of the PDSCH indicating that the A / N is pending can be determined as the earliest A / N PUCCH (or PUSCH) transmission (configuration / instruction / performance of the corresponding transmission) from the corresponding PDSCH reception time (after the minimum PDSCH processing time of the UE). In this case, if the A / N PUCCH is an A / N feedback dedicated PUCCH resource corresponding to the SPS PDSCH, then by using the PUCCH resource indicated by the PRI included in the DCI indicating that the A / N is pending, the A / N of the PDSCH indicating that the A / N is pending and the A / N of the SPS PDSCH can be fed back / transmitted together.

[0544] In addition, in this case, in a state where the type 1 A / N codebook method is configured for the UE, when the A / N PUCCH is an A / N dedicated PUCCH resource corresponding to the SPS PDSCH, 1) the A / N of the PDSCH indicating that A / N is pending and the A / N of the SPS PDSCH can be configured / transmitted together on the same single PUCCH (or PUSCH), or 2) only the A / N of the SPS PDSCH can be transmitted (in this case, the A / N transmission of the PDSCH indicating that A / N is pending can be omitted (for all subsequent A / N timings including the A / N timing corresponding to the SPS PDSCH)). In addition, in this case, when the A / N PUCCH is an A / N dedicated PUCCH resource corresponding to the SPS PDSCH in a state in which the type 2 A / N codebook method is configured for the UE, 1) the A / N corresponding to the PDSCH (including the PDSCH not indicating A / N pending) from the initial counter DAI value to the total DAI (or counter DAI) value included in the DCI indicating A / N pending and the A / N of the SPS PDSCH can be configured / transmitted on the same single PUCCH (or PUSCH), or 2) (except for the PDSCH not indicating A / N pending) the A / N of the PDSCH indicating A / N pending and the A / N of the SPS PDSCH can be configured / transmitted together on the same single PUCCH (or PUSCH). In addition, in this case, in a state where the type 2a A / N codebook method is configured for the UE, when the A / N PUCCH is an A / N dedicated PUCCH resource or the A / N PUCCH (or PUSCH) is a PUCCH (or PUSCH) for A / N feedback indicating group ID = Y, different from the (PDSCH) time slot group ID = X corresponding to the PDSCH indicating A / N pending, 1) the A / N and SPS corresponding to the PDSCH (including the PDSCH not indicating A / N pending) from the initial counter DAI value to the total DAI (or counter DAI) value included in the DCI indicating A / N pending for group ID = X can be configured / transmitted on the same single PUCCH (or PUSCH), or 2) the A / N and SPS of the PDSCH indicating A / N pending for group ID = X (except for the PDSCH not indicating A / N pending) The A / N of PDSCH or the A / N of group ID=Y can be configured / transmitted together on the same single PUCCH (or PUSCH), or 3) through the DCI indicating the A / N feedback of group ID=Y, it can be specified that the A / N feedback of group ID=X is always indicated together.

[0545] In addition, when the Type 1 or Type 2 A / N codebook method is configured, the operation of dynamically triggering A / N feedback transmission based on the Type 3 A / N codebook method through specific DCI can be applied / allowed, while when the Type 2a A / N codebook method is configured, it can be specified / defined so that dynamic Type 3 A / N codebook triggering based on DCI is not applied / allowed. In addition, when the Type 1 or Type 2 A / N codebook method is configured, the A / N pending indication operation (in the form of indicating an invalid or non-numeric A / N timing value for PDSCH) through DCI (e.g., DL grant) as described above can be not applied / allowed, while when the Type 2a method is configured, it can be specified / defined so that the A / N pending indication operation (in the form of indicating an invalid or non-numeric A / N timing value) through DCI is applied / allowed.

[0546] (e) A / N feedback transmission operation for SPS PDSCH

[0547] In addition, when the SPS PDSCH and the A / N feedback of the SPS PDSCH sent without corresponding DCI (e.g., DL grant) can be considered when the type 2a (or type 1 or type 2) A / N codebook method is configured / indicated, since there is no separate time slot group ID designation for the SPS PDSCH, a retransmission request for the A / N feedback corresponding to the corresponding SPS PDSCH (e.g., according to the UE's LBT failure and / or the base station's A / N detection failure) is not possible, and therefore it may be necessary to 1) determine the A / N feedback transmission time of the corresponding SPS PDSCH and 2) the corresponding A / N feedback configuration / mapping rules on the type 2a A / N codebook.

[0548] First, in the case of the A / N feedback transmission time of the SPS PDSCH, for example, assuming that the SPS PDSCH period is configured with L time slots and the A / N timing (delay) corresponding to the SPS PDSCH is indicated with K time slots, the A / N feedback for the SPS PDSCH transmitted in time slot #n can be (repeatedly) transmitted through all A / N timings indicated in the interval from time slot #(n+K) to time slot #(n+K+L-1). Alternatively, the A / N feedback based on the type 2a (or type 1 or type 2) codebook for the SPS PDSCH transmitted in a specific time slot #n is transmitted only through time slot #(n+K) and can (additionally) be transmitted through the time indicated by the A / N timing based on the type 3 codebook in the interval from time slot #(n+K) to time slot #(n+K+L-1). As another method, when operating with the Type 2a A / N codebook method, the specific (time slot) group ID to which the SPS PDSCH to be transmitted later belongs can be specified by enabling DCI of SPS. Therefore, when A / N feedback is configured / sent for the corresponding time slot group ID (upon request of the base station), the A / N of the corresponding SPS PDSCH can be included in the configuration / sent.

[0549] In addition, the A / N configuration / mapping of the SPS PDSCH on the type 2a A / N codebook can be configured / mapped by separating it from the A / N of the PDSCH to which the time slot group ID is assigned through DCI (e.g., DL grant). As an example, on the A / N payload of the type 2a codebook, it can be configured that the A / N of the PDSCH of the specified time slot group ID can be mapped to the lower bit index part starting with the most significant bit (MSB) (e.g., configured in the form of the first A / N subcodebook), and then the A / N of the corresponding SPS PDSCH is mapped thereafter (to the higher bit index part) (e.g., configured in the form of the second A / N subcodebook). In addition, the A / N configuration / mapping of the SPS PDSCH on the type 3 A / N codebook can be configured / mapped separately from the A / N of the PDSCH whose HARQ process ID is specified by DCI (e.g., DL grant). As an example, on the A / N payload of the type 3 codebook, it can be configured that: the A / N of the PDSCH whose HARQ process ID can be specified by DCI is mapped to the lower bit index part starting with the most significant bit (MSB) (e.g., configured in the form of the first A / N subcodebook), and then the A / N of the SPS PDSCH is mapped thereafter (to the higher bit index part) (e.g., configured in the form of the second A / N subcodebook).

[0550] In addition, in the case of type 3 A / N codebook, the A / N payload can be configured in the form of mapping A / N corresponding to each HARQ process ID, and the PDCCH indicating the release of SPS PDSCH can be used to configure PDCCH for releasing SPS by using the HARQ process ID field in DCI. Taking this into consideration, first, the entire type 3 A / N codebook can be configured in the form of adding the (1-bit) A / N information of the SPS release PDCCH to a specific position of the A / N payload in a state where the A / N payload is configured by mapping A / N according to each HARQ process ID, and the specific position can be determined as 1) the next position / the position after the last A / N bit of the entire A / N payload, 2) the next position / the position after the last A / N bit in the A / N payload corresponding to the CC that sends the SPS release PDCCH, 3) the next position / the position after the last A / N bit in the A / N payload corresponding to the CC that sends the SPSPDSCH corresponding to the SPS release PDCCH, or 4) the A / N bit corresponding to a specific HARQ process ID reserved for sending the SPS PDSCH corresponding to the SPS release PDCCH.

[0551] In addition, when the A / N timing corresponding to the SPS PDSCH reception is indicated as an inapplicable (or invalid or non-digital) value by the DCI indicating SPS activation, a method of applying a specific applicable (or valid or digital) value as the A / N timing of the initial PDSCH reception corresponding to the corresponding DCI, followed by the pending A / N feedback corresponding to the SPS PDSCH, may be considered to transmit the corresponding A / N feedback. In this case, the PUCCH resource used for the A / N feedback transmission corresponding to the initial PDSCH reception may be 1) directly indicated by the same SPS activation DCI, 2) determined as a specific resource (e.g., corresponding to the lowest or highest index) among a plurality of candidate PUCCH resource indices (PRIs) configured by RRC, or 3) predefined as a specific resource or configured by RRC. In addition, in this case, the specific applicable value of the A / N transmission timing applied to the initial PDSCH reception can be 1) predefined as a specific value or configured through RRC, 2) determined as a specific (e.g., lowest or highest) value among multiple candidate (applicable) K1 values ​​configured through RRC, or 3) directly enabled by the DCI indication through the same SPS.

[0552] Furthermore, the operation of indicating a non-applicable value as A / N timing (e.g., an A / N pending indication) via DCI indicating SPS activation is permitted only when a Type 2a (and / or Type 3) A / N codebook or a Type 2 (and / or Type 3) A / N codebook is configured for the UE. The corresponding operation may not be permitted when a Type 1 (and / or Type 3) A / N codebook is configured for the UE. This is because, when a Type 2a A / N codebook is configured for the UE, a batch (from the base station) A / N feedback request for multiple SPS PDSCHs with an A / N pending indication as described above can be requested via any DCI indicating A / N transmission based on the corresponding Type 2a and / or Type 3 codebook. When a Type 2 A / N codebook is configured for the UE, the request can be requested via any DCI indicating A / N transmission based on the corresponding Type 2 and / or Type 3 codebook. When a Type 1 A / N codebook is configured for the UE, the request can be requested only via DCI indicating A / N transmission based on the Type 3 codebook (the opportunity for the request is small and limited).

[0553] In addition, for DCI indicating A / N feedback transmission based on a type 3 codebook and / or DCI indicating SPS activation and / or DCI indicating SPS release and / or DCI for a specific cell (e.g., Scell), and for DCI indicating switching to a specific (e.g., dormant) BWP configured to disable PDCCH monitoring or decoding operations of the UE (for convenience, such DCI is referred to as "special DCI"), the A / N timing corresponding to the corresponding DCI reception may be defined such that it is not indicated as an inapplicable value (or such that it is indicated only as an applicable value). Therefore, when an inapplicable value is indicated as A / N timing by the special DCI as described above, the UE may operate to ignore the special DCI. This is because, for the special DCI as described above, when A / N feedback is pending for the corresponding DCI reception, ambiguity or misalignment may arise between the UE and the base station as to whether and when to apply / perform the operation indicated by the corresponding DCI (e.g., SPS release for SPS PDSCH transmission / reception operations or BWP switching for switching transmission / reception operations to a dormant BWP).

[0554] In another method, it is also possible that the method of mapping the state of an inapplicable value among the states indicated by the A / N timing field in the analysis / application DCI is replaced / changed to a specific applicable value of a special DCI, in which case the specific applicable value can be 1) predefined as a specific value or configured through RRC, or 2) determined based on a specific (e.g., minimum or maximum) value among multiple candidate (applicable) K1 values ​​configured through RRC (e.g., a value plus a specific offset) (e.g., determined as the minimum K1-a (e.g., a=1) or the maximum K1+b (e.g., b=1)).

[0555] (f) Determination of the minimum processing time for DCI indicating type 3A / N codebook

[0556] As described above, the A / N feedback transmission based on the type 3 codebook can be indicated by the DL grant DCI. More specifically, the following two methods can be considered (supported):

[0557] Case A) (DL grant) DCI indicates A / N feedback based on type 3 codebook and includes PDSCH scheduling;

[0558] Case B) (DL Grant) DCI indicates A / N feedback based on the type 3 codebook without including PDSCH scheduling. For example, in the latter case B, if the PDSCH frequency resource allocated by the corresponding DCI is invalid (e.g., empty), the UE can recognize and operate it as in the case where the type 3 A / N codebook is indicated without PDSCH scheduling. For example, in case B, even when receiving DCI corresponding to the DL grant DCI format, the UE can generate / transmit HARQ-ACK based on the type 3 codebook without receiving the PDSCH.

[0559] In case B, it is necessary to define a reference time for applying the HARQ-ACK timing (eg, K1) value indicated by the corresponding DCI. Figure 6 As described above, the corresponding DCI includes a PDSCH-to-HARQ feedback timing indicator field and indicates a K1 value. In case B, since there is no PDSCH scheduling as a reference for applying the K1 value, how the UE / base station should determine the HARQ-ACK response time is a problem. As a specific example of solving this problem, the UE / base station may consider the following methods: Option 1) determining the time K1 slots later from the time slot in which the corresponding DCI is received as the A / N transmission time, or Option 2) determining the time K1 slots later from the time slot indicated as the PDSCH reception time (although not actually transmitted) by the corresponding DCI as the A / N transmission time, but is not limited thereto.

[0560] In addition, in the current NR system, a minimum processing time (e.g., N1) is defined for the PDSCH reception of the UE. Specifically, when the interval from the PDSCH reception time (last symbol) to the transmission time (first symbol) of the PUCCH including the corresponding A / N is ensured by the PDSCH minimum processing time = N1 or more symbols, the UE operates to feedback the valid A / N information received by the corresponding PDSCH (reflecting the final decoding result), but if the corresponding interval is less than N1 symbols, the valid A / N information may not be fed back. In this case of N1, different values ​​may be used depending on the SCS applied to the PDSCH and A / N PUCCH transmissions and the DMRS symbol pattern configured in the PDSCH. Table 7 below shows the minimum PDSCH processing time (number of symbols N1) values ​​according to the SCS value and DMRS pattern.

[0561] [Table 7]

[0562] SCS(kHz) No additional DMRS symbol (group) With additional DMRS symbol(s) 15 8 13 or 14 30 10 13 60 17 20 120 20 24

[0563] In addition, in the current NR system, a minimum processing time (e.g., N2) is defined for the PUSCH transmission of the UE. Specifically, if the interval from the reception time (last symbol) of the PDCCH including the UL grant DCI to the transmission time (first symbol) of the PUSCH scheduled by the corresponding UL grant DCI is ensured by more than N2 symbols, the UE operates to send a PUSCH carrying UL data (e.g., TB or CBG) scheduled by the corresponding PDCCH, but if the corresponding interval is less than N2 symbols, the corresponding PDCCH can be discarded and the corresponding PUSCH transmission can be abandoned. In this case of N2, different values ​​may be used depending on the SCS applied to the UL grant PDCCH and PUSCH transmission. Table 8 below shows the minimum PUSCH processing time (number of symbols N2) values ​​according to the SCS value.

[0564] [Table 8]

[0565] SCS(kHz) N2 15 10 30 12 60 23 120 36

[0566] In addition, in the NR system, a minimum processing time (e.g., number of symbols N) is defined for the reception of the PDCCH indicating the SPS PDSCH release. Specifically, if the interval from the reception time (last symbol) of the PDCCH indicating the SPS PDSCH release to the transmission time (first symbol) of the PUCCH including the A / N of the PDCCH is ensured by N or more symbols, the UE operates to feedback valid A / N (e.g., ACK) information received by the corresponding PDCCH, but if the corresponding interval is less than N symbols, valid A / N information may not be fed back. The number of symbols N may have different values ​​depending on the SCS applied to the PDCCH and A / N PUCCH transmission. Table 9 below shows the (minimum) processing time (number of symbols N) value of the PDCCH indicating the SPS PDSCH release according to the SCS value.

[0567] [Table 9]

[0568] SCS(kHz) N 15 10 30 12 60 22 120 25

[0569] Specifically, in Table 9, SCS may refer to the smaller value between the SCS corresponding to the PDCCH and the SCS corresponding to the A / N PUCCH. In addition, when advanced processing time is used for the PDSCH (e.g., processingType2Enabled), the number of symbols N in Table 9 may be reduced (e.g., for 15kHz SCS, N=5, for 30kHz SCS, N=5.5, for 60kHz SCS, N=11).

[0570] In addition, as in case B, when the DL grant PDCCH only indicates A / N feedback transmission (based on the type 3 codebook) without PDSCH scheduling, it may be necessary to define the minimum processing time and the corresponding number of symbols (e.g., Nx) to be applied to the interval from the corresponding PDCCH (last symbol) reception time to the corresponding A / NPUCCH (first symbol) transmission time. Specifically, when the interval from the (last symbol) reception time of the PDCCH indicating A / N feedback transmission (based on the type 3 codebook) to the A / N feedback (e.g., A / N PUCCH) transmission time (first symbol) based on the type 3 codebook is ensured by Nx or more symbols, the UE can feedback valid (based on the type 3 codebook) A / N information corresponding to the corresponding PDCCH. However, if the corresponding interval is less than Nx symbols, the UE may 1) not feedback valid A / N information, or 2) ignore the corresponding PDCCH itself.

[0571] As an example of the Nx value, the N1 value (or the (N1+a) value obtained by adding a specific symbol number a to N1, where a can be configured as a positive or negative number) applied when no additional DMRS symbol (group) is configured among the values ​​shown in Table 7 can be applied as the Nx value. This is because there is no actually scheduled PDSCH and the processing required for this can be omitted, so the minimum N1 value can be applied to each SCS.

[0572] Alternatively, as another example of the Nx value, the N1 value (or the (N1+a) value obtained by adding a specific symbol number a to N1, where a can be configured as a positive or negative number) applied when configuring an additional DMRS symbol (group) among the values ​​shown in Table 7 can be applied as the Nx value. In the case of the PDCCH, since each of all symbols constituting it includes a DMRS, it may not be reasonable to apply the maximum N1 value to each SCS in consideration of the corresponding channel estimation time.

[0573] As another example of the Nx value, the N2 value shown in Table 8 (or the (N2+a) value obtained by adding a specific symbol number a to N2, where a can be configured as a positive or negative number) can be applied as the Nx value. This is because, similar to the PUSCH scheduling / transmission case, Case B is a form of receiving DL control and transmitting the corresponding UL channel, so it may not be difficult to apply the N2 value defined for each SCS.

[0574] As another example of the Nx value, the N value related to the PDCCH indicating SPS release shown in Table 9 (or the (N+a) value obtained by adding a specific number of symbols to N, where a can be configured as a positive number or a negative number) can be used as the Nx value (for example, the symbol offset from the last symbol of the PDCCH indicating A / N feedback transmission based on the type 3 codebook without PDSCH scheduling to the A / N feedback (for example, A / N PUCCH) transmission (first symbol) based on the type 3 codebook). The reason is that in case B (the information indicated by the PDCCH is different from the SPS PDSCH release), the UE receives the PDCCH and sends the HARQ-ACK (for example, A / NPUCCH) corresponding to the PDCCH, so as shown in Table 9, for the PDCCH indicating the SPS PDSCH release, the N value defined for each SCS can be applied to the PDCCH indicating A / N feedback transmission based on the type 3 codebook. For example, when the UE receives a first PDCCH carrying a request for HARQ-ACK based on the type 3 codebook without DCI scheduled by the PDSCH (e.g., DL grant format DCI), just like receiving a second PDCCH carrying DCI indicating SPS release, the UE can send (or start sending) the HARQ-ACK based on the type 3 codebook indicated by the first PDCCH at the timing when the A / N feedback should be sent for the second PDCCH (even if the first PDCCH is actually received and the second PDCCH is not received). When the base station sends a first PDCCH carrying a request for HARQ-ACK based on the type 3 codebook without DCI scheduled by the PDSCH (e.g., DL grant format DCI), just like receiving a second PDCCH carrying DCI indicating SPS release, the base station can receive (or start receiving) the HARQ-ACK based on the type 3 codebook indicated by the first PDCCH at the timing when the base station should receive A / N feedback for the second PDCCH (even if the first PDCCH is actually sent and the second PDCCH is not sent). Therefore, the A / N feedback timing of the PDCCH indicating the SPS PDSCH release can be reused for case B (for example, the UE receiving the PDCCH carrying the DCI requesting HARQ-ACK based on the type 3 codebook without PDSCH scheduling (for example, DL grant format DCI) sends HARQ-ACK based on the type 3 codebook).

[0575] Figure 24 The HARQ-ACK transmission timing based on the type 3 codebook according to the embodiment of the present disclosure is illustrated. Figure 24 , can be omitted with the above content (for example, Figures 17 to 23 etc.) repeated descriptions.

[0576] Reference Figure 24 The UE attempts to detect a PDCCH carrying DCI corresponding to the DL grant DCI format (2405). The PDCCH detection attempt may include performing blind decoding on candidates for the corresponding PDCCH in the search space.

[0577] The UE obtains DCI having a DL grant DCI format from the PDCCH (2410).

[0578] When the DCI requests HARQ-ACK feedback based on the type 3 codebook (2412 Yes) and schedules PDSCH (2415 Yes) (e.g., case A), the UE receives the PDSCH scheduled by the DCI (2425) and generates a HARQ-ACK payload (2430) based on the type 3 codebook indicated by the DCI (e.g., Figures 21 to 23 wait).

[0579] When the DCI requests HARQ-ACK feedback based on the type 3 codebook (2412 Yes) without PDSCH scheduling (2415 No) (e.g., case B), the UE generates a HARQ-ACK payload based on the type 3 codebook indicated by the DCI without PDSCH reception (e.g., Figures 21 to 23 wait).

[0580] The UE transmits a HARQ-ACK based on the type 3 codebook (2435). The HARQ-ACK transmission timing may be determined based on whether the DCI requesting the HARQ-ACK feedback based on the type 3 codebook (2412 Yes) schedules the PDSCH (2415 Yes / No).

[0581] For example, when DCI (2412 is) schedules PDSCH (2415 is), HARQ-ACK transmission (2435) can be determined based on the PDSCH reception (2425) time. As a specific example, HARQ-ACK transmission (2435) can be performed in a second time slot determined by applying a first time slot offset value to the first time slot where PDSCH reception (2425) ends. When DCI (2412 is and 2415 is) includes a PDSCH-to-HARQ timing indicator, the first time slot offset value may mean K1 indicated by the PDSCH-to-HARQ timing indicator. When DCI (2412 is and 2415 is) does not include a PDSCH-to-HARQ timing indicator, a value preconfigured by higher layer signaling may be determined as the first time slot offset value.

[0582] For example, when the DCI (2412 Yes) does not schedule the PDSCH (2415 No), the HARQ-ACK transmission (2435) can be determined based on the reception time of the detected PDCCH (2405). As a specific example, the HARQ-ACK transmission (2435) timing can be determined based on the A / N timing (e.g., Table 9) used when the PDCCH indicates the SPS PDSCH release. The UE / base station can apply / reuse the A / N timing (e.g., Table 9) used when the PDCCH indicates the SPS PDSCH release for the PDCCH (2405) carrying the DCI (2412 Yes and 2415 No) to determine the HARQ-ACK transmission (2435) timing. As a more specific example, when the reception of the PDCCH (2405) carrying DCI (2412 Yes and 2415 No) ends at symbol #X, HARQ-ACK transmission (2435) based on the type 3 codebook can be performed (or transmission starts) at symbol #(X+N), and the value of N can refer to Table 9.

[0583] In addition, HARQ-ACK transmission (2435) may be performed in a fourth time slot determined by applying a second time slot offset value to a third time slot at which reception of the PDCCH (2405) ends. When the DCI (2412 Yes and 2415 No) includes a PDSCH-to-HARQ timing indicator, the second time slot offset value may refer to K1 indicated by the PDSCH-to-HARQ timing indicator. When the DCI (2412 Yes and 2415 No) does not include a PDSCH-to-HARQ timing indicator, a value preconfigured by higher layer signaling may be used as the second time slot offset value, but the present disclosure is not limited thereto.

[0584] (g) Considering Type 2a A / N codebook-related DL / UL DCI signaling based on CBG transmission configuration

[0585] First, when configuring CBG-based PDSCH transmission in a specific serving cell configured for a UE, the following DL grant DCI signaling method may be considered for configuring the type 2A / N codebook.

[0586] 1) When the total DAI (T-DAI) and NFI information of the time slot group (i.e., PDSCH) corresponding to other IDs are configured as indicated by a DL authorization DCI (e.g., DCI indicates the T-DAI and NFI information of each of the PDSCH group corresponding to the current ID (i.e., current group) and the PDSCH group corresponding to other IDs (i.e., other groups)).

[0587] A. Method 0: (through DL grant DCI) indicating both the T-DAI information of the TB-based PDSCH (corresponding to the TB-based A / N subcodebook configuration) of other groups and the T-DAI information of the CBG-based PDSCH (corresponding to the CBG-based A / N subcodebook configuration).

[0588] B. Method 1: (through DL grant DCI) only indicate one T-DAI information of other groups (in this case, the corresponding T-DAI may indicate only T-DAI information of one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0589] i. In this method, the PDSCH type may be fixed to TB-based PDSCH (or fixed to CBG-based PDSCH). For example, when T-DAI indicates T-DAI information of only a specific one of TB-based PDSCH and CBG-based PDSCH, the PDSCH type may be fixed so that PDSCH transmission is performed using the specific PDSCH type.

[0590] ii. In addition, for PDSCH type 1 other than this PDSCH type (for example, when the PDSCH type is TB-based PDSCH, the corresponding PDSCH type 1 becomes CBG-based PDSCH, and when the PDSCH type is CBG-based PDSCH, the corresponding PDSCH type 1 becomes TB-based PDSCH) (common in methods 1 / 2 / 3 / 4), the corresponding A / N feedback (sub-codebook) is configured by applying the most recently received T-DAI information (through another DCI scheduling PDSCH type 1 of other groups).

[0591] C. Method 2: Indicate only one T-DAI information of other groups (through DL grant DCI) (in this case, the corresponding T-DAI indicates only T-DAI information of one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0592] i. When there is another DCI-1 that schedules other groups and indicates the same A / N transmission time slot as the DCI, the PDSCH type is determined from the corresponding DCI-1 as the last scheduled PDSCH type (or when CBG-based PDSCH transmission is configured in the last scheduled cell from the corresponding DCI-1, the PDSCH type is determined as CBG-based PDSCH, otherwise, the PDSCH type is determined as TB-based PDSCH).

[0593] ii. When there is no other DCI-1 that schedules other groups and indicates the same A / N transmission time slot as the DCI, the PDSCH type is determined to be TB-based PDSCH (or is determined to be CBG-based PDSCH, or the PDSCH type is configured through RRC signaling whether it is TB-based PDSCH or CBG-based PDSCH).

[0594] D. Method 3: Indicate only one T-DAI information of other groups (through DL grant DCI) (in this case, the corresponding T-DAI indicates only T-DAI information of one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0595] i. When there is other DCI-1 that schedules other groups and indicates the same A / N transmission time slot as the DCI, and the corresponding DCI-1 schedules both TB-based PDSCH and CBG-based PDSCH, the PDSCH type is determined to be TB-based PDSCH (or is determined to be CBG-based PDSCH, or the PDSCH type is configured by RRC signaling whether it is TB-based PDSCH or CBG-based PDSCH).

[0596] ii. When there is another DCI-1 that schedules other groups and indicates the same A / N transmission time slot as the DCI, and the corresponding DCI-1 schedules only one PDSCH type 1 among the TB-based PDSCH and the CBG-based PDSCH, the PDSCH type is determined to be PDSCH type 1.

[0597] iii. If there is no other DCI-1 that schedules other groups and indicates the same A / N transmission time slot as the DCI, the PDSCH type is determined to be TB-based PDSCH (or is determined to be CBG-based PDSCH, or whether the PDSCH type is TB-based PDSCH or CBG-based PDSCH is configured through RRC signaling).

[0598] E. Method 4: Indicate only one T-DAI information of other groups (through DL grant DCI) (in this case, the corresponding T-DAI indicates only T-DAI information of one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0599] i. Whether the PDSCH type is TB-based PDSCH or CBG-based PDSCH is indicated by the same DCI (ie, DCI-X) (eg, by a separate 1 bit) or can be configured by RRC signaling.

[0600] ii. In addition, for PDSCH type 1 other than PDSCH types, the corresponding A / N feedback (subcodebook) is configured by applying the most recently received T-DAI information (by scheduling the DCI corresponding to PDSCH type 1 of other groups), or in the case of method 4, the A / N feedback (subcodebook) may not be configured / sent for the corresponding PDSCH type 1.

[0601] 2) When it is configured such that the T-DAI and NFI information of other groups is not indicated through the DL grant DCI (ie, only the T-DAI and NFI information of the current group is indicated).

[0602] A. Method 5: For other groups, for each PDSCH type (TB-based or CBG-based), an operation is performed to configure the A / N feedback (sub-codebook) corresponding to each corresponding PDSCH type by applying the most recently received T-DAI information (through the DCI of the corresponding PDSCH type of the other group).

[0603] In addition, regarding signaling T-DAI information through DL grant DCI, one of the following two methods can be configured for the UE through RRC signaling.

[0604] 1) Method X: Indicate both T-DAI information of TB-based PDSCH of other groups and T-DAI information of CBG-based PDSCH (through DL grant DCI) (same as method 0).

[0605] 2) Method Y: (through DL grant DCI) indicate only one T-DAI information of other groups (the corresponding T-DAI only indicates T-DAI information of one of TB-based PDSCH and CBG-based PDSCH).

[0606] Next, when configuring CBG-based PDSCH transmission in a specific cell configured for a UE, the following UL grant DCI signaling method may be considered for configuring the Type 2A / N codebook.

[0607] 1) When the T-DAI information of each of the two PDSCH groups is configured to be indicated by UL authorization DCI (for example, through DCI, indicating both the T-DAI information of the PDSCH group corresponding to the first ID (for example, the first group (index 0)) and the T-DAI information of the PDSCH group corresponding to the second ID (for example, the second group (index 1)).

[0608] A. Method 0: (Through UL grant DCI) indicate the T-DAI information of the TB-based PDSCH (corresponding to the TB-based A / N sub-codebook configuration) and the T-DAI information of the CBG-based PDSCH (corresponding to the CBG-based A / N sub-codebook configuration) of each PDSCH group as follows.

[0609] i. T-DAI information of TB-based PDSCH belonging to the first group

[0610] ii. T-DAI information of CBG-based PDSCH belonging to the first group

[0611] iii. T-DAI information of TB-based PDSCH belonging to the second group

[0612] iv. T-DAI information of CBG-based PDSCH belonging to the second group

[0613] B. Method 1: Indicate only one T-DAI information of each PDSCH group (through UL grant DCI) (in this case, the corresponding T-DAI indicates T-DAI information of only one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0614] i. In this method, the PDSCH type (corresponding to the T-DAI indicated for each PDSCH group) is fixed to TB-based PDSCH (or CBG-based PDSCH).

[0615] ii. In addition, for PDSCH type 1 other than the PDSCH type of each PDSCH group (for example, when the PDSCH type is TB-based PDSCH, the corresponding PDSCH type 1 becomes CBG-based PDSCH, and when the PDSCH type is CBG-based PDSCH, the corresponding PDSCH type 1 becomes TB-based PDSCH) (common in methods 1 / 2 / 3 / 4), the corresponding A / N feedback (sub-codebook) is configured by applying the most recently received T-DAI information (through the DL grant DCI indicating the T-DAI information corresponding to the PDSCH type 1 of the corresponding PDSCH group).

[0616] C. Method 2: Indicate only one T-DAI information of each PDSCH group (through UL grant DCI) (in this case, the corresponding T-DAI indicates only T-DAI information of one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0617] i. When there is a DL grant DCI that schedules the corresponding PDSCH group and indicates the PUSCH transmission time slot indicated by the UL grant DCI of each PDSCH group as the A / N PUCCH transmission time slot, the PDSCH type (corresponding to the T-DAI indicated for the corresponding PDSCH group) is determined from the DL grant DCI as the last scheduled PDSCH type (or when CBG-based PDSCH transmission is configured in the last scheduled cell from the DL DCI, the PDSCH type is determined as CBG-based PDSCH, otherwise, the PDSCH type is determined as TB-based PDSCH).

[0618] ii. When there is no DL authorization DCI that schedules the corresponding PDSCH group and indicates the PUSCH transmission time slot indicated by the UL authorization DCI of each PDSCH group as an A / N PUCCH transmission time slot, the PDSCH type (corresponding to the T-DAI indicated for the corresponding PDSCH group) is determined to be TB-based PDSCH (or is determined to be CBG-based PDSCH, or whether the PDSCH type is TB-based PDSCH or CBG-based PDSCH is configured through RRC signaling).

[0619] D. Method 3: Indicate only one T-DAI information of each PDSCH group (through UL grant DCI) (in this case, the corresponding T-DAI indicates only T-DAI information of one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0620] i. When, for each PDSCH group, there is a DL DCI that schedules the corresponding PDSCH group and indicates the PUSCH transmission time slot indicated by the UL authorization DCI as the A / N PUCCH transmission time slot and the corresponding DL authorization DCI schedules both TB-based PDSCH and CBG-based PDSCH, the PDSCH type (corresponding to the T-DAI indicated for the corresponding PDSCH group) is determined to be TB-based PDSCH (or is determined to be CBG-based PDSCH, or whether the PDSCH type is TB-based PDSCH or CBG-based PDSCH is configured through RRC signaling).

[0621] ii. When, for each PDSCH group, there is a DL authorization DCI that schedules the corresponding PDSCH group and indicates the PUSCH transmission time slot indicated by the UL authorization DCI as the A / N PUCCH transmission time slot, and the corresponding DL authorization DCI schedules only one of the TB-based PDSCH and the CBG-based PDSCH, the PDSCH type (corresponding to the T-DAI indicated for the corresponding PDSCH group) is determined to be the corresponding PDSCH type 1.

[0622] iii. When, for each PDSCH group, there is no DL authorization DCI that schedules the PDSCH group while indicating the PUSCH transmission time slot indicated by the UL authorization DCI as the A / N PUCCH transmission time slot, the PDSCH type (corresponding to the T-DAI indicated for the corresponding PDSCH group) is determined to be TB-based PDSCH (or is determined to be CBG-based PDSCH, or whether the PDSCH type X is TB-based PDSCH or CBG-based PDSCH is configured through RRC signaling).

[0623] E. Method 4: Indicate only one T-DAI information of each PDSCH group (through UL grant DCI) (in this case, the corresponding T-DAI indicates only T-DAI information of one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0624] i. Whether the PDSCH type (corresponding to the T-DAI indicated for each PDSCH group) is TB-based PDSCH or CBG-based PDSCH is indicated by the same UL grant DCI (i.e., DCI-Y) (e.g., by a separate 1 bit) or configured by RRC signaling.

[0625] ii. In addition, for PDSCH type 1 other than the PDSCH type of each PDSCH group, the corresponding A / N feedback (subcodebook) may be configured by applying the most recently received T-DAI information (through DL DCI indicating T-DAI information of the corresponding PDSCH type 1 of the corresponding PDSCH group), or in the case of method 4, A / N feedback (subcodebook) may not be configured / transmitted for the corresponding PDSCH type 1.

[0626] 2) When T-DAI information is configured to be indicated by UL DCI for only one PDSCH group X of two PDSCH groups (eg, a first group (index 0), a second group (index 1)).

[0627] A. Method 5: (through UL grant DCI) indicating both the T-DAI information of the TB-based PDSCH (corresponding to the TB-based A / N subcodebook configuration) and the T-DAI information of the CBG-based PDSCH (corresponding to the CBG-based A / N subcodebook configuration) of a PDSCH group X.

[0628] i.PDSCH group X can be determined as: 1) the first group, when the DL authorization DCI indicating the PUSCH transmission time slot indicated by the UL authorization DCI as the A / N PUCCH transmission time slot schedules two PDSCH groups; 2) corresponding to a specific PDSCH group, when the DL authorization DCI indicating the PUSCH transmission time slot indicated by the UL authorization DCI as the A / N PUCCH transmission time slot schedules only one specific PDSCH group; or 3) the first group, when there is no DL authorization DCI indicating the PUSCH transmission time slot indicated by the UL authorization DCI as the A / NPUCCH transmission time slot.

[0629] ii. For PDSCH group Y other than PDSCH group X, the A / N feedback corresponding to each corresponding PDSCH type (subcodebook) is configured by applying the most recently received T-DAI information (through DL DCI indicating the T-DAI information of the corresponding PDSCH type of the corresponding PDSCH group Y) for each PDSCH type (TB-based or CBG-based).

[0630] B. Method 6: Indicate only one T-DAI information of one PDSCH group (through UL DCI) (in this case, the corresponding T-DAI indicates only T-DAI information of one PDSCH type among TB-based PDSCH and CBG-based PDSCH).

[0631] i. First, PDSCH group X may be determined according to the same method as method 5. The PDSCH type (TB-based or CBG-based) corresponding to the T-DAI indicated for PDSCH group X may be determined by applying at least one of methods 1 / 2 / 3 / 4.

[0632] ii. For PDSCH group Y other than PDSCH group X, the corresponding A / N feedback (sub-codebook) can be configured by applying T-DAI information of each PDSCH type according to the same method as method 5.

[0633] In addition, regarding signaling T-DAI information through UL DCI, one of the following two methods may be configured for the UE through RRC signaling.

[0634] 1) Method X: Indicates both T-DAI information of TB-based PDSCH and T-DAI information of CBG-based PDSCH for each PDSCH group (through UL grant DCI) (same as method 0).

[0635] 2) Method Y: (through UL grant DCI) indicating only one T-DAI information of each PDSCH group (the corresponding T-DAI only indicates the T-DAI information of one of the TB-based PDSCH and the CBG-based PDSCH).

[0636] Figure 25 A communication system 1 to which the present disclosure is applied is exemplified.

[0637] Reference Figure 25 , the communication system 1 applied to the present disclosure includes a wireless device, a base station and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and can be referred to as a communication / wireless / 5G device. Although not limited to this, the wireless device may include a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100b, a handheld device 100d and a home appliance 100e. An Internet of Things (IoT) device (100f) and an AI device / server 400. For example, a vehicle may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device includes an AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) device, and it can be implemented in the form of an HMD (Head Mounted Device), a HUD (Head Up Display) in a vehicle, a TV, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smart watches, smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, washing machines, and the like. IoT devices may include sensors, smart meters, and the like. For example, base stations and networks may be implemented as wireless devices, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0638] Wireless devices 100a to 100f can be connected to a network 300 via a base station 200. AI (artificial intelligence) technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can be connected to an AI server 400 via the network 300. The network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., V2V (vehicle-to-vehicle) / V2X (vehicle-to-everything) communication). Additionally, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0639] Wireless communications / connections 150a, 150b, and 150c may be established between wireless devices 100a to 100f / base station 200 and base station 200 / base station 200. Wireless communications / connections may be implemented using various radio access technologies (e.g., 5G NR), such as uplink / downlink communications 150a, sidelink communications 150b (or D2D communications), and base station communications 150c (e.g., relays, integrated access backhaul (IAB)). Wireless devices and base stations / wireless devices, as well as base stations and base stations, may transmit and receive radio signals to and from each other via wireless communications / connections 150a, 150b, and 150c. For example, wireless communications / connections 150a, 150b, and 150c may transmit and receive signals via various physical channels. To this end, based on various proposals of the present disclosure, at least some of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes may be performed to transmit and receive radio signals.

[0640] Figure 26 A wireless device applied to the present disclosure is exemplified.

[0641] Reference Figure 26 , the first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals through various radio access technologies (e.g., LTE, NR). Here, {first wireless device 100, second wireless device 200} may correspond to Figure 25 {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x}.

[0642] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in the present disclosure. For example, the processor 102 may generate first information / signals by processing information in the memory 104, and then transmit a wireless signal including the first information / signals through the transceiver 106. In addition, the processor 102 may receive a wireless signal including second information / signals through the transceiver 106, and then store information obtained by signal processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including commands for executing all or part of a process controlled by the processor 102 or for executing the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in conjunction with an RF (radio frequency) unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0643] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in the present disclosure. For example, the processor 202 may generate third information / signals by processing information in the memory 204, and then transmit a wireless signal including the third information / signals through the transceiver 206. In addition, the processor 202 may receive a wireless signal including fourth information / signals through the transceiver 206, and then store information obtained by signal processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including commands for executing all or part of the processes controlled by the processor 202 or for executing the descriptions, functions, processes, proposals, methods, and / or operational flowcharts included in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in conjunction with an RF unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0644] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. Without limitation, one or more protocol layers may be implemented by one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). According to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts included in the present disclosure, one or more processors 102 and 202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units). According to the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts included in the present disclosure, one or more processors 102 and 202 may generate messages, control information, data, or information. One or more processors 102, 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure to provide it to one or more transceivers 106, 206. One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 and obtain the PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flow charts included in the present disclosure.

[0645] The one or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. In an example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in the one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in this disclosure may be implemented using firmware or software, or the firmware or software may be implemented to include modules, processes, functions, etc. The firmware or software configured to execute the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in this disclosure may be included in the one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by the one or more processors 102, 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts included in this disclosure may be implemented by firmware or software in the form of codes, commands and / or command sets.

[0646] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, a hard drive, registers, cache memory, a computer-readable storage medium, and / or a combination thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. In addition, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies, such as wired or wireless connections.

[0647] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc. mentioned in the methods and / or operational flowcharts of the present disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc. mentioned in the description, functions, processes, proposals, methods, and / or operational flowcharts of the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 can be connected to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. In addition, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 can be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 can be configured to transmit and receive user data, control information, wireless signals / channels, etc. mentioned in the descriptions, functions, processes, proposals, methods and / or operational flowcharts, etc. included in the present disclosure through one or more antennas 108, 208. In the present disclosure, one or more antennas can be multiple physical antennas or more logical antennas (e.g., antenna ports). One or more transceivers 106, 206 can convert received wireless signals / channels, etc. from RF band signals to baseband signals to process the received user data, control information, wireless signals / channels, etc. by using one or more processors 102, 202. One or more transceivers 106, 206 can convert user data, control information, wireless signals / channels, etc. processed by using one or more processors 102, 202 from baseband signals to RF band signals. Thus, one or more transceivers 106 , 206 may include (analog) oscillators and / or filters.

[0648] According to the above embodiment, the first wireless device 100 can receive downlink control information (DCI) through a physical downlink control channel (PDCCH) and transmit a HARQ-ACK report based on the DCI. In the HARQ-ACK report, even if the wireless device 100 is configured to perform spatial bundling for ACK / NACK (NACK) bits based on transport blocks (TBs), based on the DCI indicating a one-time transmission of ACK / NACK for all HARQ processes of one or more serving cells configured in the first wireless device 100, the wireless device 100 can report each new data indicator (NDI) bit and each TB-based ACK / NACK bit without performing spatial bundling, and the first wireless device 100 is configured to report the ACK / NACK bits based on the HARQ-ACK report based on the specific type of codebook. The first wireless device 100 may report each new data indicator (NDI) bit and each TB-based ACK / NACK bit without performing spatial bundling, even if the wireless device 100 is configured to perform spatial bundling for transport block (TB)-based ACK / negative ACK (NACK) bits, based on the DCI indicating one-time transmission of ACK / NACK for all HARQ processes of one or more serving cells configured in the UE through HARQ-ACK reporting based on a specific type of codebook, and the wireless device 100 may be configured to report each NDI bit through HARQ-ACK reporting based on a specific type of codebook).

[0649] According to the above embodiment, the second wireless device 200 can transmit downlink control information (DCI) to the first wireless device 100 via a physical downlink control channel (PDCCH), and receive a HARQ-ACK report from the first wireless device 100 based on the DCI. When receiving the HARQ-ACK report, even if the second wireless device 200 configures the first wireless device 100 to perform spatial bundling of TB (transport block)-based ACK / NACK (negative ACK) bits, the second wireless device 200 can obtain the respective NDI bits and the respective TB-based ACK / NACK bits without applying spatial bundling, based on the indication of a HARQ-ACK report based on a specific type of codebook by a one-time transmission of ACK / NACK for all HARQ processes of one or more serving cells configured in the first wireless device 100 via DCI and the configuration of the first wireless device 100 to report the respective new data indicator (NDI) bits through the HARQ-ACK report based on the specific type of codebook.

[0650] The specific type codebook is a type 3 codebook, and for HARQ-ACK reports based on the type 3 codebook configured to include individual NDI bits, spatial bundling may not be performed as an exception to spatial bundling. For HARQ-ACK reports based on the type 3 codebook configured to include individual NDI bits, the exception to spatial bundling may apply. For HARQ-ACK reports based on a type 1 or type 2 codebook other than the type 3 codebook, spatial bundling may be performed on the corresponding TB-based ACK / NACK bits.

[0651] The first wireless device 100 may receive, through higher layer signaling, a configuration for spatial bundling corresponding to a logical AND operation of TB-based ACK / NACK bits and a configuration for reporting each NDI bit through a HARQ-ACK report based on a specific type of codebook.

[0652] The one or more serving cells may include a specific serving cell that performs CBG (Code Block Group)-based transmission. The first wireless device 100 may determine, based on higher layer signaling, whether to perform CBG-based ACK / NACK reporting or TB-based ACK / NACK reporting for the specific serving cell using HARQ-ACK reporting based on a specific type of codebook. The specific type of codebook may be a type-3 codebook. Even if the first wireless device 100 determines, based on higher layer signaling, to perform TB-based ACK / NACK reporting for the specific serving cell using HARQ-ACK reporting based on a type-3 codebook, the first wireless device 100 may perform CBG-based ACK / NACK reporting for the specific serving cell using HARQ-ACK reporting based on a type-1 or type-2 codebook, which is different from the type-3 codebook.

[0653] The ACK / NACK bits of the lower index serving cell may be mapped to the lower index bits in the HARQ-ACK report based on a specific type of codebook. Among the ACK / NACK bits of the same index serving cell, the ACK / NACK bits of the lower index HARQ process may be mapped to the lower index bits in the HARQ-ACK report based on a specific type of codebook. Among the ACK / NACK bits of the same index HARQ process, the ACK / NACK bits of the lower index TB may be mapped to the lower index bits in the HARQ-ACK report based on a specific type of codebook. Among the ACK / NACK bits of the multiple code block groups (CBGs) included in the corresponding TB, the ACK / NACK bits of the lower index CBG may be mapped to the lower index bits in the HARQ-ACK report based on the specific type of codebook.

[0654] Each NDI bit included in the HARQ-ACK report based on the specific type of codebook may be configured with an NDI field value included in the corresponding DCI for scheduling the corresponding TB.

[0655] The first wireless device 100 may receive the first TB through a physical downlink shared channel (PDSCH) of the first serving cell according to TB-based scheduling. The first wireless device 100 may receive the code block group (CBG) of the second TB through the PDSCH of the second serving cell according to CBG-based scheduling. The HARQ-ACK report based on the specific type of codebook may include a TB-based ACK / NACK bit of the first TB, an NDI bit of the first TB, and an NDI bit of the second TB. The HARQ-ACK report based on the specific type of codebook may include a TB-based ACK / NACK bit of the second TB or a CBG-based ACK / NACK bit of the CBG of the second TB.

[0656] Figure 27 Another example of a wireless device to which the present disclosure is applied is illustrated. The wireless device may be implemented in various forms depending on the use case / service (see Figure 25 ).

[0657] Reference Figure 27 , the wireless devices 100 and 200 correspond to Figure 26 The wireless devices 100 and 200 may be composed of various elements, components, units and / or modules. For example, the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Figure 26 The one or more processors 102 and 202 and / or the one or more memories 104 and 204 of the present invention may include: Figure 26 The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls all operations of the wireless device. For example, the control unit 120 can control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. In addition, the control unit 120 can transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) through the communication unit 110 via a wireless / wired interface, or store information received from an external device (e.g., another communication device) via the wireless / wired interface in the memory unit 130.

[0658] The additional component 140 may be configured differently depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an I / O unit, a drive unit, and a computing unit. Although not limited thereto, the wireless device may be a robot ( Figure 25 , 100a), vehicle ( Figure 25 , 100b-1, 100b-2), XR device ( Figure 25 , 100c), mobile device ( Figure 25 , 100d), electrical appliances ( Figure 25 , 100e), IoT devices ( Figure 25 , 100f), digital broadcast terminal, hologram device, public safety device, MTC device, medical device, FinTech device (or financial device), security device, climate / environmental device, AI server / device ( Figure 25 , 400), base station ( Figure 25 , 200) and network nodes, etc. Depending on the use case / service, the wireless device can be used in a mobile or fixed location.

[0659] exist Figure 27 In the wireless devices 100 and 200, the various elements, components, units, and / or modules can be interconnected entirely via wired interfaces, or at least some can be wirelessly connected via the communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 can be connected via a wired interface, and the control unit 120 and the first unit (e.g., 130, 140) can be wirelessly connected via the communication unit 110. In addition, each element, component, unit, and / or module in the wireless devices 100 and 200 can also include one or more elements. For example, the control unit 120 can be composed of one or more processors. For example, the control unit 120 can be composed of a group of communication control processors, application processors, electronic control units (ECUs), graphics processing processors, and memory control processors. As another example, the memory unit 130 can be composed of random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), flash memory, volatile memory, non-volatile memory, and / or combinations thereof.

[0660] Figure 28 The vehicle or autonomous driving vehicle applied to the present disclosure is illustrated. The vehicle or autonomous driving vehicle can be implemented as a mobile robot, a vehicle, a train, an aircraft (AV), a ship, etc.

[0661] Reference Figure 28, the vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140d-140d correspond to Figure 27 Blocks 110 / 130 / 140.

[0662] The communication unit 110 can send and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. The control unit 120 can perform various operations by controlling components of the vehicle or autonomous vehicle 100. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a enables the vehicle or autonomous vehicle 100 to operate on the ground. The drive unit 140a may include an engine, a motor, a transmission system, wheels, brakes, a steering system, etc. The power supply unit 140b provides power to the vehicle or autonomous vehicle 100 and may include wired / wireless charging circuits, a battery, etc. The sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a tilt sensor, a weight sensor, a heading sensor, a location module, a vehicle forward / reverse direction sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140d can implement technology for maintaining a driving lane, technology for automatically adjusting speed (such as adaptive cruise control), technology for automatically driving along a predetermined route, technology for automatically setting a route when a destination is set, etc.

[0663] For example, the communication unit 110 can receive map data, traffic information data, and the like from an external server. The autonomous driving unit 140d can generate an autonomous driving route and driving plan based on the acquired data. The control unit 120 can control the drive unit 140a to move the vehicle or autonomous driving vehicle 100 along the autonomous driving path (e.g., adjusting speed and direction) according to the driving plan. During autonomous driving, the communication unit 110 can periodically obtain the latest traffic information data from the external server and can obtain surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit 140c can obtain vehicle status and surrounding environment information. The autonomous driving unit 140d can update the autonomous driving route and driving plan based on the newly acquired data and information. The communication unit 110 can send information about the vehicle's location, autonomous driving route, driving plan, and the like to the external server. The external server can use AI technology, etc., based on information collected from the vehicle or autonomous driving vehicle to predict traffic information data in advance and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0664] Figure 29 is a diagram for explaining a discontinuous reception (DRX) operation of a UE according to an embodiment of the present disclosure.

[0665] The UE may perform DRX operations while executing the procedures and / or methods described / proposed above. A UE configured with DRX can reduce power consumption by discontinuously receiving DL signals. DRX may be performed in the RRC (Radio Resource Control)_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. In the RRC_IDLE state and the RRC_INACTIVE state, DRX is used to discontinuously receive paging signals. Hereinafter, DRX performed in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described.

[0666] Reference Figure 29, the DRX cycle includes an on-duration and a DRX opportunity. The DRX cycle defines a time interval at which the on-duration is periodically repeated. The on-duration indicates the duration that the UE monitors to receive the PDCCH. When DRX is configured, the UE performs PDCCH monitoring during the on-duration. If the PDCCH is successfully detected during the PDCCH monitoring, the UE operates the inactivity timer and maintains the awake state. On the other hand, if the PDCCH is not successfully detected during the PDCCH monitoring, the UE enters the sleep state after the on-duration ends. Therefore, when DRX is configured, PDCCH monitoring / reception can be performed continuously in the time domain when performing the processes and / or methods described / proposed above. For example, when DRX is configured, in the present disclosure, the PDCCH reception timing (e.g., a time slot with a PDCCH search space) can be configured discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, PDCCH monitoring / reception can be performed continuously in the time domain when performing the processes and / or methods described / proposed above. For example, if DRX is not configured, the PDCCH reception opportunities (eg, time slots with PDCCH search spaces) in the present disclosure may be configured continuously. In addition, regardless of whether DRX is configured, PDCCH monitoring may be limited to time intervals configured as measurement gaps.

[0667] Table 10 shows the UE's procedures related to DRX (RRC_CONNECTED state). Referring to Table 10, DRX configuration information is received through higher layer (e.g., RRC) signaling, and DRX on / off is controlled by a DRX command of the MAC layer. When DRX is configured, the UE may discontinuously perform PDCCH monitoring while executing the procedures and / or methods described / proposed in this disclosure.

[0668] [Table 10]

[0669]

[0670] Here, MAC-CellGroupConfig includes configuration information required to configure MAC (Media Access Control) parameters for the cell group. MAC-CellGroupConfig may also include configuration information related to DRX. For example, MAC-CellGroupConfig may include the following information to define DRX.

[0671] -drx-OnDurationTimer value: defines the length of the start duration of the DRX cycle.

[0672] -drx-InactivityTimer value: defines the length of time that the UE remains awake after detecting a PDCCH opportunity indicating a PDCCH for initial UL or DL ​​data.

[0673] -drx-HARQ-RTT-TimerDL value: defines the maximum time interval from the reception of a DL initial transmission until the reception of a DL retransmission.

[0674] -drx-HARQ-RTT-TimerDL value: defines the length of the maximum time interval after receiving the grant for UL initial transmission until receiving the grant for UL retransmission.

[0675] -drx-LongCycleStartOffset: defines the length and start time of the DRX cycle.

[0676] -drx-ShortCycle (optional): defines the length of the short DRX cycle.

[0677] Here, if any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is operating, the UE performs PDCCH monitoring at every PDCCH opportunity while maintaining an awake state.

[0678] The above-mentioned embodiments are elements and features of the present disclosure combined in a predetermined form. Unless otherwise clearly stated, each element or feature should be considered to be optional. Each element or feature can be implemented in a form not combined with other elements or features. In addition, the embodiments of the present disclosure may include a part of the combined elements and / or features. The order of the operations described in the embodiments of the present disclosure can be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced with corresponding elements or features of other embodiments. It is clear that an embodiment may include a combined claim without a clear dependency relationship in the claim, or may be included as a new claim by modification after application.

[0679] It will be clear to those skilled in the art that the present disclosure may be implemented in other specific forms without exceeding the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted restrictively in every aspect and should be considered as illustrative. The scope of the present disclosure should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent range of the present disclosure are included within the scope of the present disclosure.

[0680] Industrial Applicability

[0681] The present disclosure can be used in a terminal, a base station or other devices of a wireless mobile communication system.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising the following steps: receiving downlink control information DCI via a physical downlink control channel PDCCH; as well as Sending HARQ-ACK information in a specific type of hybrid automatic repeat request HARQ-ACK codebook based on the DCI, Even if spatial bundling is configured to generate a single ACK / NACK bit for each HARQ process based on ACK / NACK bits for a plurality of transport blocks TB corresponding to each HARQ process, Based on both i) the DCI requesting the UE to report a HARQ-ACK report of a one-time transmission of ACK / NACK for all HARQ processes of one or more serving cells configured for the UE and ii) the UE being configured to include a new data indicator NDI bit for the HARQ-ACK report, the UE includes an ACK / NACK bit for each TB and an NDI value corresponding to the ACK / NACK bit without performing the spatial bundling.

2. The method according to claim 1, in, The specific type HARQ-ACK codebook is a type 3 HARQ-ACK codebook, and for the type 3 HARQ-ACK codebook configured to include each NDI bit, as an exception to the spatial bundling, the spatial bundling is not performed.

3. The method according to claim 1, in, An exception to the spatial bundling is applied based on the specific type of HARQ-ACK codebook being configured to include each NDI bit.

4. The method according to claim 2, in, For a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook different from the type 3 HARQ-ACK codebook, the spatial bundling is performed on the multiple TBs corresponding to each HARQ process.

5. The method according to claim 1, further comprising the steps of: The configuration of the spatial bundling for the logical AND operation of the ACK / NACK bits of the plurality of TBs corresponding to each HARQ process and the configuration for including each NDI bit in the specific type HARQ-ACK codebook are received through high-layer signaling.

6. The method according to claim 1, in, The one or more serving cells include a specific serving cell that performs code block group (CBG)-based transmission, The UE determines, based on higher layer signaling, whether to perform CBG-based HARQ-ACK reporting or TB-based HARQ-ACK reporting for the specific serving cell in the specific type HARQ-ACK codebook.

7. The method according to claim 6, in, Even if the UE determines, based on the higher layer signaling, to perform TB-based HARQ-ACK reporting for the specific serving cell in the type 3 HARQ-ACK codebook, The UE performs CBG-based HARQ-ACK reporting for the specific serving cell using a type 1 HARQ-ACK codebook or a type 2 HARQ-ACK codebook different from the type 3 HARQ-ACK codebook.

8. The method according to claim 1, in, The ACK / NACK bits of the lower index serving cell are mapped to the lower index bits in the specific type HARQ-ACK codebook, Among the ACK / NACK bits of the same index serving cell, the ACK / NACK bits of the lower index HARQ process are mapped to the lower index bits in the specific type HARQ-ACK codebook, Among the ACK / NACK bits of the HARQ process with the same index, the ACK / NACK bits of the TB with a lower index are mapped to the lower index bits in the specific type of HARQ-ACK codebook.

9. The method according to claim 8, in, Among the ACK / NACK bits of a plurality of code block groups CBGs included in the corresponding TB, the ACK / NACK bits of lower-index CBGs are mapped to lower-index bits in the specific type HARQ-ACK codebook.

10. The method according to claim 1, in, Each NDI bit included in the specific type HARQ-ACK codebook is configured with an NDI field value included in a corresponding DCI for scheduling a corresponding TB.

11. The method according to claim 1, further comprising the steps of: receiving a first TB through a physical downlink shared channel (PDSCH) of a first serving cell according to TB-based scheduling; as well as receiving the CBG of the second TB through the PDSCH of the second serving cell according to the scheduling based on the code block group CBG, The specific type HARQ-ACK codebook includes a TB-based ACK / NACK bit of the first TB, an NDI bit of the first TB, and an NDI bit of the second TB. The specific type HARQ-ACK codebook includes the TB-based ACK / NACK bits of the second TB or the CBG-based ACK / NACK bits of the CBG of the second TB.

12. A user equipment (UE) operating in wireless communication, the UE comprising: transceiver; as well as a processor configured to receive downlink control information (DCI) through a physical downlink control channel (PDCCH) by controlling the transceiver and send HARQ-ACK information in a specific type of hybrid automatic repeat request (HARQ)-acknowledgement (ACK) codebook based on the DCI, Even if spatial bundling is configured to generate a single ACK / NACK bit for each HARQ process based on ACK / NACK bits for a plurality of transport blocks TB corresponding to each HARQ process, based on both i) the DCI requesting the UE to report a HARQ-ACK report of a one-time transmission of ACK / NACK for all HARQ processes of one or more serving cells configured for the UE and ii) the UE being configured to include a new data indicator (NDI) bit for the HARQ-ACK report, The processor includes an ACK / NACK bit for each TB and an NDI value corresponding to the ACK / NACK bit without performing the spatial bundling.

13. A method performed by a base station in a wireless communication system, the method comprising the following steps: Sending downlink control information DCI to user equipment UE via a physical downlink control channel PDCCH; as well as receiving HARQ-ACK information in a specific type of hybrid automatic repeat request HARQ-acknowledgement ACK codebook from the UE based on the DCI, wherein, even if the UE is configured to perform spatial bundling, the spatial bundling is configured to generate a single ACK / NACK bit for each HARQ process based on ACK / NACK bits for a plurality of transport blocks TB corresponding to each HARQ process, Based on both i) a HARQ-ACK report requesting the UE to report ACK / NACK for all HARQ processes of one or more serving cells configured for the UE at one time through the DCI and ii) the UE being configured to include a new data indicator (NDI) bit for the HARQ-ACK report, The base station obtains an ACK / NACK bit for each TB and an NDI value corresponding to the ACK / NACK bit in the specific type HARQ-ACK codebook without applying the spatial bundling.

Images