Method and apparatus for transmitting and receiving control information in a wireless communication system

Abstract

A method and apparatus for transmitting and receiving control information in a wireless communication system are disclosed. The method of transmitting control information according to an embodiment of the disclosure can include receiving, from a base station, first configuration information for configuring hybrid automatic repeat and request (HARQ)-acknowledgement (ACK) bundling for at least one serving cell among a plurality of serving cells configured in a terminal, receiving, from the base station, downlink control information (DCI) for scheduling at least one physical downlink shared channel (PDSCH) in each of the plurality of serving cells, receiving, from the base station, a plurality of PDSCHs on the plurality of serving cells, and transmitting, to the base station, control information including a HARQ-ACK codebook generated based on HARQ-ACK information for the plurality of PDSCHs.

Description

Technical Field

[0001] This disclosure relates to wireless communication systems, and more specifically, to a method and apparatus for transmitting and receiving uplink control information in a wireless communication system. Background Technology

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded to include data and voice services, and the current explosive growth in services has led to resource shortages. Users are demanding faster services and therefore require more advanced mobile communication systems.

[0003] The overall requirements for next-generation mobile communication systems should be able to support the capacity for explosive data traffic, significantly increased per-user transmission rates, a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies have been investigated, including dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking. Summary of the Invention

[0004] [Technical Issues]

[0005] The technical objective of this disclosure is to provide a method and apparatus for scheduling one or more downlink transmissions and / or one or more uplink transmissions using a single downlink control information.

[0006] An additional technical objective of this disclosure is to provide a method and apparatus for transmitting and receiving hybrid automatic repeat and request (HARQ)-acknowledgement (ACK) messages for one or more downlink transmissions scheduled via a single downlink control message.

[0007] In addition, an additional technical objective of this disclosure is to provide a method and apparatus for sending and receiving HARQ-ACK codebooks when generating HARQ-ACK information for multiple PDSCHs in each predetermined group.

[0008] The technical objectives achieved through this disclosure are not limited to those described above, and those skilled in the art will clearly understand from the following description other technical objectives not described herein.

[0009] [Technical Solution]

[0010] A method for transmitting control information in a wireless communication system according to one aspect of this disclosure may include: receiving from a base station first configuration information for configuring HARQ (Hybrid Automatic Repeat and Request)-ACK (Acknowledgement) bindings for one or more of a plurality of serving cells configured for a terminal; receiving from the base station downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCHs) on each of the plurality of serving cells; receiving from the base station a plurality of PDSCHs on the plurality of serving cells; and transmitting to the base station control information including a HARQ-ACK codebook generated based on HARQ-ACK information for the plurality of PDSCHs. The HARQ-ACK codebook may include a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook may be generated for PDSCHs on one or more first serving cells where the number of HARQ binding groups is set to 1, and the second HARQ-ACK sub-codebook may be generated for PDSCHs on one or more second serving cells where the number of HARQ binding groups is set to greater than 1.

[0011] A method for receiving control information in a wireless communication system according to an additional aspect of this disclosure may include: sending to a terminal first configuration information for configuring HARQ (Hybrid Automatic Repeat and Request)-ACK (Acknowledgement) bindings for one or more of a plurality of serving cells configured for the terminal; sending to the terminal downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCHs) on each of the plurality of serving cells; sending to the terminal a plurality of PDSCHs on the plurality of serving cells; and receiving from the terminal control information including a HARQ-ACK codebook generated based on HARQ-ACK information for the plurality of PDSCHs. The HARQ-ACK codebook may include a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. The first HARQ-ACK sub-codebook may be generated for PDSCHs on one or more first serving cells where the number of HARQ binding groups is set to 1, and the second HARQ-ACK sub-codebook may be generated for PDSCHs on one or more second serving cells where the number of HARQ binding groups is set to greater than 1.

[0012] [Beneficial Effects]

[0013] According to embodiments of this disclosure, by supporting the scheduling of one or more downlink transmissions and / or one or more uplink transmissions through a downlink control information, the transmission efficiency of the downlink control information scheduled for downlink transmissions and / or uplink transmissions can be increased.

[0014] Furthermore, according to embodiments of this disclosure, by generating HARQ-ACK information for multiple PDSCHs for each predetermined group, the overhead on HARQ-ACK information bits can be reduced.

[0015] The effects achievable by this disclosure are not limited to those described above, and those skilled in the art can clearly understand other effects not described herein through the following description. Attached Figure Description

[0016] The accompanying drawings, included as part of the detailed description for understanding this disclosure, provide embodiments of the disclosure and describe the technical features of the disclosure through detailed description.

[0017] Figure 1 The diagram illustrates the structure of a wireless communication system to which this disclosure can be applied.

[0018] Figure 2 The diagram illustrates the frame structure applicable to wireless communication systems disclosed herein.

[0019] Figure 3 The diagram illustrates a resource grid that can be applied to a wireless communication system according to this disclosure.

[0020] Figure 4 The diagram illustrates physical resource blocks in a wireless communication system that can be applied according to this disclosure.

[0021] Figure 5 The diagram illustrates a time slot structure applicable to wireless communication systems according to this disclosure.

[0022] Figure 6 The diagram illustrates a physical channel used in a wireless communication system to which this disclosure can be applied, as well as general signal transmission and reception methods using that physical channel.

[0023] Figure 7 The diagram illustrates the HARQ-ACK process for downlink data in a wireless communication system that can utilize the present disclosure.

[0024] Figure 8 The diagram illustrates the processing procedure and structure of TB in a wireless communication system to which this disclosure can be applied.

[0025] Figure 9 The illustration shows a CBG-based HARQ process that can be applied to a wireless communication system according to this disclosure.

[0026] Figure 10 This is a diagram illustrating PDCCH monitoring based on time slot groups according to an embodiment of the present disclosure.

[0027] Figure 11 This is a diagram illustrating the set of opportunities for determining candidate PDSCH reception according to an embodiment of the present disclosure.

[0028] Figure 12 This is a diagram illustrating the signaling process between a base station and a terminal in a method for transmitting and receiving control information according to an embodiment of the present disclosure.

[0029] Figure 13 This is a diagram illustrating the operation of a terminal for sending and receiving control information according to an embodiment of the present disclosure.

[0030] Figure 14 This is a diagram illustrating the operation of a base station for transmitting and receiving control information according to an embodiment of the present disclosure.

[0031] Figure 15 This is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. Detailed Implementation

[0032] In the following, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed with reference to the drawings is intended to describe exemplary embodiments of the present disclosure and not to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the art will recognize that the present disclosure may be practiced without these specific details.

[0033] In some cases, known structures and devices may be omitted, or they may be shown in block diagram form based on the core functions of each structure and device in order to prevent ambiguity of the concepts in this disclosure.

[0034] In this disclosure, when an element is referred to as “connected,” “combined,” or “linked” to another element, it can include both indirect and direct connections between the two elements. Furthermore, in this disclosure, the terms “comprising” or “having” specify the presence of the mentioned features, steps, operations, components, and / or elements, but do not exclude the presence or addition of one or more other features, stages, operations, components, elements, and / or groups thereof.

[0035] In this invention, terms such as "first" and "second" are used only to distinguish one element from another and are not used to limit the elements. Unless otherwise stated, they do not limit the order or importance of the elements. Therefore, within the scope of this disclosure, a first element in one embodiment may be referred to as a second element in another embodiment, and similarly, a second element in one embodiment may be referred to as a first element in another embodiment.

[0036] The terminology used in this disclosure is for the purpose of describing particular embodiments and not for limiting the claims. As used in the description of the embodiments and the appended claims, the singular forms are intended to include the plural forms unless the context clearly indicates otherwise. The term “and / or” as used in this disclosure may refer to one of the associated enumerations, or is intended to refer to and include any and all possible combinations of two or more of them. Furthermore, unless otherwise stated, the “ / ” between words in this invention has the same meaning as “and / or”.

[0037] This disclosure describes a wireless communication network or wireless communication system, and operations performed in the wireless communication network can be performed during the process of a device (e.g., a base station) controlling the network and transmitting or receiving signals, or during the process of a terminal associated with the corresponding wireless network transmitting or receiving signals between the network or between the terminal.

[0038] In this disclosure, the term "transmit or receive channel" includes the meaning of transmitting or receiving information or signals through a corresponding channel. For example, transmitting a control channel means transmitting control information or control signals through a control channel. Similarly, transmitting a data channel means transmitting data information or data signals through a data channel.

[0039] In the following text, downlink (DL) refers to communication from a base station to a terminal, while uplink (UL) refers to communication from a terminal to a base station. In the downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In the uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. A base station (BS) can be replaced by terms such as fixed station, Node B, eNB (evolved Node B), gNB (next-generation Node B), BTS (Base Transceiver System), Access Point (AP), Network (5G network), AI (Artificial Intelligence) system / module, RSU (Roadside Unit), robot, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, terminals can be fixed or mobile, and can be replaced by terms such as UE (User Equipment), MS (Mobile Station), UT (User Terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless Terminal), MTC (Machine-Type Communication) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicles, RSU (Roadside Unit), robots, AI (Artificial Intelligence) modules, drones (UAVs), AR (Augmented Reality) equipment, and VR (Virtual Reality) equipment.

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

[0041] To make the description clearer, it is based on 3GPP communication systems (e.g., LTE-A, NR), but the technical ideas of this disclosure are not limited thereto. LTE refers to technology from 3GPP TS (Technical Specification) version 8 onwards. Specifically, LTE technology in or after 3GPP TS 36.xxx version 10 is referred to as LTE-A, and LTE technology in or after 3GPP TS 36.xxx version 13 is referred to as LTE-A pro. 3GPP NR refers to technology in or after TS 38.xxx version 15. LTE / NR can be referred to as a 3GPP system. "xxx" refers to the detailed number of the standard document. LTE / NR is generally referred to as a 3GPP system. For background technology, terminology, abbreviations, etc., used to describe this disclosure, reference can be made to the matters described in the standard documents previously published. For example, the following documents can be consulted.

[0042] For 3GPP LTE, please refer to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Compilation), TS 36.213 (Physical Layer Procedures), TS 36.300 (General Description), and TS 36.331 (Radio Resource Control).

[0043] For 3GPP NR, you can refer to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Compilation), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (Next Generation Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0044] The abbreviations of terms that may be used in this disclosure are defined as follows.

[0045] -BM: Beam Management

[0046] -CQI: Channel Quality Indicator

[0047] -CRI: Channel State Information - Reference Signal Resource Indicator

[0048] -CSI: Channel State Information

[0049] -CSI-IM: Channel State Information - Interference Measurement

[0050] -CSI-RS: Channel State Information - Reference Signal

[0051] -DMRS: Demodulation Reference Signal

[0052] -FDM: Frequency Division Multiplexing

[0053] -FFT: Fast Fourier Transform

[0054] -IFDMA: Interleaved Frequency Division Multiple Access

[0055] -IFFT: Inverse Fast Fourier Transform

[0056] -L1-RSRP: Layer 1 Reference Signal Received Power

[0057] -L1-RSRQ: Layer 1 Reference Signal Receive Quality

[0058] -MAC: Media Access Control

[0059] -NZP: Non-zero power

[0060] -OFDM: Orthogonal Frequency Division Multiplexing

[0061] -PDCCH: Physical Downlink Control Channel

[0062] -PDSCH: Physical Downlink Shared Channel

[0063] -PMI: Precoding Matrix Indicator

[0064] -RE: Resource Elements

[0065] -RI: Rank indicator

[0066] -RRC: Radio Resource Control

[0067] -RSSI: Received Signal Strength Indicator

[0068] -Rx: Receive

[0069] -QCL: Quasi-co-addressable

[0070] -SINR: Signal-to-Noise Ratio

[0071] -SSB (or SS / PBCH block): Synchronization signal block (including PSS (primary synchronization signal), SSS (secondary synchronization signal), and PBCH (physical broadcast channel)).

[0072] -TDM: Time Division Multiplexing

[0073] -TRP: Transmitter / Receiver Point

[0074] -TRS: Tracking Reference Signal

[0075] -Tx: Send

[0076] -UE: User Equipment

[0077] -ZP: Zero Power

[0078] Overall System

[0079] With more communication devices requiring higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). Furthermore, massive MTC (machine-type communication) that provides various services anytime, anywhere by connecting multiple devices and things is also one of the main issues to be considered in next-generation communications. In addition, communication system designs considering services / terminals sensitive to reliability and latency are discussed. Therefore, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable low-latency communication), etc., is discussed, and for convenience, the corresponding technologies are referred to as NR in this disclosure. NR is an example expression representing 5G RAT.

[0080] New RAT systems, including those for NR, use OFDM or similar transmission methods. These new RAT systems may follow OFDM parameters different from those used in LTE. Alternatively, the new RAT system may follow existing LTE / LTE-A parameters as is, but may support a wider system bandwidth (e.g., 100MHz). Alternatively, a single cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets can coexist in a single cell.

[0081] The parameter set corresponds to a subcarrier spacing in the frequency domain. Different parameter sets can be defined as the reference subcarrier spacing is scaled by an integer N.

[0082] Figure 1 The diagram illustrates the structure of a wireless communication system to which this disclosure can be applied.

[0083] refer to Figure 1 The NG-RAN is configured with gNBs that provide control plane (RRC) protocol support for the NG-RA (NG Radio Access) user plane (i.e., the new AS (Access Layer) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and UE. The gNBs interconnect via the Xn interface. Furthermore, the gNBs are connected to the NGC (Next Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Power) via the N2 interface and to the UPF (User Plane Functions) via the N3 interface.

[0084] Figure 2 The diagram illustrates a frame structure in a wireless communication system to which this disclosure can be applied.

[0085] NR systems can support multiple parameter sets. These parameter sets can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the basic (reference) subcarrier spacing by an integer N (or μ). Furthermore, while it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the parameter set used can be selected independently of the frequency band. Moreover, various frame structures based on multiple parameter sets can be supported in NR systems.

[0086] The OFDM parameter sets and frame structures that can be considered in an NR system are described below. Several OFDM parameter sets supported in an NR system can be defined as shown in Table 1 below.

[0087] [Table 1]

[0088] μ <![CDATA[Δf=2 μ ·15[kHz]]]> CP 0 15 normal 1 30 normal 2 60 Normal, expansion 3 120 normal 4 240 normal

[0089] NR supports multiple sets of parameters (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15kHz SCS supports wide-area coverage of traditional cellular bands; a 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth; and a 60kHz or higher SCS supports bandwidths exceeding 24.25GHz to overcome phase noise.

[0090] The NR band is defined as frequency ranges of two types (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. Additionally, FR2 can refer to millimeter wave (mmW).

[0091] [Table 2]

[0092] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz–7125MHz 15, 30, 60kHz FR2 24250MHz–52600MHz 60, 120, 240kHz

[0093] Regarding the frame structure in the NR system, the size of various fields in the time domain is expressed as T. c =1 / (Δf) max ·N f A multiple of the time unit. Here, Δf max i is 480·10 3 Hz, and N f The value is 4096. Downlink and uplink transmissions are configured (organized) to have a duration T. f =1 / (Δf) max N f / 100)·T c A radio frame of 10ms. Here, the radio frame is configured with 10 subframes, each with a T... sf =(Δf max N f / 1000)·T c The duration. In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should begin T earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c Begin. For the subcarrier spacing configuration μ, the time slots are arranged in n-order within the subframe. s μ ∈{0,...,N slot subframe,μ The numbers are numbered in ascending order from -1, and in the radio frames, they are numbered in n... s,f μ ∈{0,...,N slot frame,μ The time slot is configured with N in ascending order of -1.symb slot N consecutive OFDM symbols, and N symb slot Determined based on CP. Slot n in the subframe s μ The beginning of the OFDM symbol n in the same subframe s μ N symb slot The start dates are arranged in time. Not all terminals may perform transmission and reception simultaneously, meaning that all OFDM symbols in either the downlink or uplink time slots may not be available.

[0094] Table 3 shows the number of OFDM symbols (N) in each time slot during normal CP. symb slot ), Number of time slots per radio frame (N) slot frame,μ ) and the number of time slots per subframe (N) slot subframe,μ Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0095] [Table 3]

[0096] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0097] [Table 4]

[0098] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 2 12 40 4

[0099] Figure 2 This is an example of μ=2 (SCS is 60kHz), see Table 3. One subframe can include 4 time slots. Figure 2 The subframe shown as {1,2,4} is an example, and the number of time slots that can be included in a subframe is defined in Table 3 or Table 4. Additionally, micro-time slots can include 2, 4, or 7 symbols, or more or fewer symbols.

[0100] Regarding physical resources in an NR system, factors such as antenna ports, resource grids, resource elements, resource blocks, and carrier components can be considered. The following sections will describe these physical resources in detail.

[0101] First, regarding antenna ports, an antenna port is defined such that the channel carrying symbols in that antenna port can be inferred from the channels carrying other symbols in the same antenna port. Two antenna ports can be said to be in a QC / QCL (quasi-co-location or quasi-co-addressable) relationship when the large-scale properties of the channel carrying symbols in one antenna port can be inferred from the channels carrying symbols in another antenna port. In this case, the large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and receive timing.

[0102] Figure 3 The illustration shows a resource grid in a wireless communication system to which this disclosure can be applied.

[0103] refer to Figure 3 The diagram illustrates the resource grid configuration with N in the frequency domain. RB μ N sc RB There are 14.2 subcarriers, and one subframe is configured with 14.2 μ The number of OFDM symbols is not limited to this. In an NR system, the transmitted signal consists of 2 OFDM symbols. μ N symb (μ) Each OFDM symbol and configuration has N RB μ N sc RB It is described by one or more resource grids of N subcarriers. Here, N RB μ ≤N RB max,μ N RB max,μ This represents the maximum transmission bandwidth, which may differ between uplink and downlink, and between parameter sets. In this case, each μ and antenna port p can be configured with a resource grid. Each element of the resource grid used for μ and antenna port p is called a resource element and is uniquely identified by an index pair (k, l'). Here, k = 0, ..., N RB μ N sc RB -1 is the index in the frequency domain, and l' = 0, ..., 2 μ N symb (μ) -1 indicates the symbol position within the subframe. When referencing resource elements in a time slot, the index pair (k, l) is used. Here, l = 0,...,N symb μ -1. The resource element (k,l') used for μ and antenna port p corresponds to the complex value a. k,l' (p,μ)When there is no risk of confusion or when a specific antenna port or parameter set is not specified, the indices p and μ may be discarded, and the complex value may be a. k,l' (p) or a k,l' Furthermore, a resource block (RB) is defined as N in the frequency domain. sc RB = 12 consecutive subcarriers.

[0104] Point A serves as a common reference point for the resource block grid and is obtained as follows.

[0105] - The offsetToPointA of the downlink in the primary cell (PCell) represents the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block, which is used by the terminal for initial cell selection. It is assumed that a 15kHz subcarrier spacing is used for FR1 and a 60kHz subcarrier spacing is used for FR2, expressed in units of resource blocks.

[0106] -absoluteFrequencyPointA represents the frequency location of point A, expressed in ARFCN (Absolute Radio Frequency Channel Number).

[0107] For subcarrier spacing configuration μ, common resource blocks are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of common resource block 0 used for subcarrier spacing configuration μ is the same as "point A". The relationship between the common resource block number nCRBμ of subcarrier spacing configuration μ in the frequency domain and the resource element (k,l) is given by Equation 1 below.

[0108] [Formula 1]

[0109]

[0110] In Equation 1, k is defined relative to point A, such that k = 0 corresponds to a subcarrier centered at point A. Physical resource blocks range from 0 to N in the bandwidth portion (BWP). BWP,i size,μ -1 is the number, and i is the number of the BWP. The physical resource block n in BWP i. PRB and public resource block n CRB The relationship between them is given by Equation 2.

[0111] [Equation 2]

[0112]

[0113] N BWP,i start,μ It is a public resource block relative to public resource block 0 in BWP.

[0114] Figure 4The diagram illustrates physical resource blocks in a wireless communication system to which this disclosure can be applied. Furthermore, Figure 5 The diagram illustrates a time slot structure in a wireless communication system to which this disclosure can be applied.

[0115] refer to Figure 4 and Figure 5 A time slot includes multiple symbols in the time domain. For example, for a normal CP, one time slot includes 7 symbols, but for an extended CP, one time slot includes 6 symbols.

[0116] A carrier comprises multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Component) is defined as multiple consecutive (physical) resource blocks in the frequency domain and can correspond to a set of parameters (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through active BWPs, and only one BWP can be active for a single terminal. In the resource grid, each element is called a resource element (RE) and can be mapped to a complex number of symbols.

[0117] In NR systems, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates with the radio frequency (FR) chip turned on for the entire CC, terminal battery consumption may increase. Alternatively, when considering multiple application scenarios operating in a wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different sets of parameters (e.g., subcarrier spacing, etc.) can be supported in each frequency band of the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. With this in mind, the base station can instruct the terminal to operate only in a portion of the bandwidth, rather than in the full bandwidth of the wideband CC, and for convenience, the corresponding portion of the bandwidth is defined as the bandwidth portion (BWP). The BWP can be configured with consecutive RBs on the frequency axis and can correspond to a set of parameters (e.g., subcarrier spacing, CP length, slot / microslot duration).

[0118] Simultaneously, even within a single CC configured for a terminal, the base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in the PDCCH monitoring slot, and PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when a UE is congested in a particular BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering inter-cell interference cancellation in the frequency domain between neighboring cells, some intermediate spectrum of the full bandwidth can be excluded, and two edge BWPs can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP for a terminal associated with a broadband CC. The base station can activate at least one DL / UL BWP among the configured DL / UL BWPs at a specific time (via L1 signaling, MAC CE (control element), or RRC signaling, etc.). Furthermore, the base station can instruct a handover to other configured DL / UL BWPs (via L1 signaling, MAC CE, or RRC signaling, etc.). Alternatively, based on a timer, a handover to a specific DL / UL BWP can be performed when the timer value expires. Here, the active DL / UL BWP is defined as the active DL / UL BWP. However, the terminal may not receive the configuration on the DL / UL BWP before performing the initial access procedure or establishing an RRC connection. Therefore, in these cases, the DL / UL BWP assumed by the terminal is defined as the initially active DL / UL BWP.

[0119] Figure 6 The illustration shows a physical channel used in a wireless communication system to which this disclosure can be applied, as well as general signal transmission and reception methods using the physical channel.

[0120] In wireless communication systems, terminals receive information from base stations via downlink and transmit information to base stations via uplink. The information sent and received by base stations and terminals includes data and various control information, and various physical channels exist depending on the type / use of the information they send and receive.

[0121] When a terminal is powered on or enters a new cell, it performs an initial cell search (S601), including synchronization with the base station. For the initial cell search, the terminal synchronizes with the base station by receiving the primary synchronization signal (PSS) and secondary synchronization signal (SSS) from the base station, and obtains information such as the cell identifier (ID). Then, the terminal obtains broadcast information within the cell by receiving the physical broadcast channel (PBCH) from the base station. Simultaneously, the terminal checks the downlink channel state by receiving the downlink reference signal (DL RS) during the initial cell search phase.

[0122] The terminal that has completed the initial cell search can obtain more detailed system information by receiving the Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) based on the information carried in the PDCCH (S602).

[0123] Simultaneously, when a terminal first accesses a base station or when there are no radio resources available for signal transmission, it can perform a random access (RACH) procedure (S603 to S606). For the random access procedure, the terminal can send a specific sequence as a preamble via the Physical Random Access Channel (PRACH) (S603 and S605), and can receive response messages to the preamble via the PDCCH and the corresponding PDSCH (S604 and S606). Contention-based RACH can further execute a contention resolution procedure.

[0124] The terminal that subsequently performs the above process can execute PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) via PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its intended use.

[0125] Meanwhile, control information sent by the terminal to the base station via the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgment / non-acknowledgment) signals, CQI (Channel Command Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. For 3GPP LTE systems, the terminal can send the aforementioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0126] Table 5 shows examples of DCI format in NR systems.

[0127] [Table 5]

[0128]

[0129] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information (e.g., UL / SUL (Supplemental UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), information related to transport blocks (TBs) (e.g., MCS (Modulation Compilation and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), information related to HARQ (Hybrid Automatic Repeat and Request) (e.g., process number, DAI (Downlink Assignment Index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), power control information related to PUSCH scheduling (e.g., PUSCH power control, etc.), and control information included in each DCI format can be predefined.

[0130] DCI format 0_0 is used to schedule PUSCH in a cell. The information included in DCI format 0_0 is scrambled with CRC (Cyclic Redundancy Check) by C-RNTI (Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Compilation Scheme Cell RNTI) and then transmitted.

[0131] DCI format 0_1 ​​is used to indicate the scheduling of one or more PUSCHs or to provide downlink feedback information to the Terminal Configuration Grant (CG) in a cell. The information included in DCI format 0_1 ​​is scrambled and transmitted by C-RNTI, CS-RNTI, SP-CSI-RNTI (semi-persistent CSI RNTI), or MCS-C-RNTI.

[0132] DCI format 0_2 is used to schedule PUSCH within a cell. The information included in DCI format 0_2 is scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0133] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB (Virtual Resource Block) - PRB (Physical Resource Block) mapping, etc.), information related to transport blocks (TB) (e.g., MCS, NDI, RV, etc.), information related to HARQ (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., antenna port, TCI (Transmission Configuration Indicator), SRS (Sound Reference Signal) request, etc.), information related to PUCCH scheduling regarding PDSCH (e.g., PUCCH power control, PUCCH resource indicator, etc.), and control information included in each DCI format can be predefined.

[0134] DCI format 1_0 is used to schedule PDSCH in a DL cell. The information included in DCI format 1_0 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0135] DCI format 1_1 is used to schedule PDSCH in a cell. The information included in DCI format 1_1 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0136] DCI format 1_2 is used to schedule PDSCH in a cell. The information contained in DCI format 1_2 is a CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0137] Data transmission and HARQ (Hybrid Automatic Repeat and Request) - ACK (Acknowledgement) process

[0138] Figure 7 The diagram illustrates the HARQ-ACK process for downlink data in a wireless communication system that can utilize the present disclosure.

[0139] refer to Figure 7 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 reporting offset (K1). For example, DCI formats 1_0 and 1_1 may include the following information.

[0140] - Frequency domain resource allocation: Indicates the RB resources (e.g., one or more (non-)contiguous RBs) allocated to the PDSCH.

[0141] - Time-domain resource assignment: K0, indicating the start position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH in the time slot.

[0142] -PDSCH to HARQ_ Feedback Timing Indicator: Indicates K1.

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

[0144] -PUCCH Resource Indicator (PRI: PUCCH Resource Indicator): Indicates the PUCCH resource to be used for UCI transmission among multiple PUCCH resources in the PUCCH resource set.

[0145] Subsequently, the UE can receive PDSCH in time slot #(n+K0) according to the scheduling information of time slot #n, and then send UCI via PUCCH in time slot #(n+K1). Here, UCI includes a HARQ-ACK response for the PDSCH. If the PDSCH is configured to be sent up to 1 TB, the HARQ-ACK response can be configured with 1 bit. When the PDSCH is configured to be sent up to 2 TB, the HARQ-ACK response can be configured with 2 bits when no spatial binding is configured, and with 1 bit when spatial binding is configured. When the HARQ-ACK transmission time for multiple PDSCHs is specified as time slot #(n+K1), the UCI sent in time slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0146] HARQ process based on CBG (block group)

[0147] In LTE, a transport block (TB) based HARQ procedure is supported. In NR, a block-based (CBG) based HARQ procedure is supported in conjunction with the TB-based HARQ procedure.

[0148] Figure 8 The diagram illustrates the processing procedure and structure of TB in a wireless communication system to which this disclosure can be applied.

[0149] Figure 8 The process can be applied to data in DL Shared Channel (DL-SCH), Paging Channel (PCH), and Multicast Channel (MCH) transmission channels. UL TB (or UL transmission channel data) can be processed similarly.

[0150] refer to Figure 8 The transmitter appends a CRC (e.g., 24 bits) (TB CRC) to the TB for error checking. The transmitter may then divide the TB+CRC into multiple code blocks, taking into account the size of the channel encoder. For example, the maximum size of a code block (CB) in LTE is 6144 bits. Therefore, if the TB size is less than 6144 bits, no CB is configured, and if the TB size is greater than 6144 bits, the TB is divided into 6144-bit units to generate multiple CBs. A CRC (e.g., 24 bits) (CB CRC) is appended separately to each CB for error checking. After each CB undergoes channel compilation and rate matching, they are combined into a codeword (CW). Data scheduling and HARQ procedures are performed on a TB-by-TB basis, and the CBC RC is used to determine the early termination of TB decoding.

[0151] Figure 9 The illustration shows a CBG-based HARQ process that can be applied to a wireless communication system according to this disclosure.

[0152] In CBG-based HARQ processes, data scheduling and corresponding HARQ processes can be executed on a CBG basis.

[0153] refer to Figure 9 The UE can receive information about the maximum number M of code block groups (CBGs) per transport block from the base station via a higher-layer signal (e.g., an RRC signal) (S1602). Afterward, the UE can receive initial data transmission from the base station (via PDSCH) (S1604). Here, the data includes TBs, the transport block includes multiple CBs, and the multiple CBs can be classified into one or more CBGs. Here, some CBGs may include ceiling (K / M) number of CBs, and the remaining CBGs may include flooring (K / M) number of CBs. K represents the number of CBs in the data. Afterward, the UE can feed back CBG-based A / N information for the data to the base station (S1606), and the base station can perform data retransmission based on the CBGs (S1608). The A / N information can be sent via PUCCH or PUSCH. Here, the A / N information may include multiple A / N bits for the data, and each A / N bit may indicate each A / N response generated for the data in units of CBGs. Regardless of the CBGs included in the data, the payload size of the A / N information can remain the same based on M.

[0154] Dynamic / Semi-static HARQ-ACK Codebook Scheme

[0155] NR supports both dynamic and semi-static HARQ-ACK codebook schemes. The HARQ-ACK (or A / N) codebook can be replaced by a HARQ-ACK payload.

[0156] When configuring a dynamic HARQ-ACK codebook scheme, the size of the A / N payload varies depending on the actual amount of DL data scheduled. Therefore, the PDCCH associated with DL scheduling includes a counter-downlink assignment index (counter DAI) and a total DAI. The counter DAI indicates the {CC, slot} scheduling order value calculated using a CC (component carrier) (or cell) priority method and is used to specify the position of the A / N bits in the A / N codebook. The total DAI indicates the accumulated slot unit scheduling value up to the current slot and is used to determine the size of the A / N codebook.

[0157] When configuring a semi-static A / N codebook scheme, the size of the A / N codebook is fixed (at its maximum value), regardless of the actual amount of scheduled DL data. Specifically, the (maximum) A / N payload (size) transmitted via a PUCCH in a time slot can be determined by the number of corresponding A / N bits (hereinafter referred to as the binding window) corresponding to all CCs configured for the UE and all DL scheduling time slots (or PDSCH transmission time slots or PDCCH monitoring time slots) that can indicate the timing of A / N transmissions to it. For example, the DL-granted DCI (PDCCH) includes PDSCH-to-A / N timing information, and the PDSCH-to-A / N timing information can have one of several values ​​(e.g., k). For example, when a PDSCH is received in time slot #m and the PDSCH-to-A / N timing information in the DL-granted DCI (PDCCH) scheduling that PDSCH indicates k, A / N information for the PDSCH can be transmitted in time slot #(m+k). As an example, k∈{1,2,3,4,5,6,7,8} can be given. Simultaneously, when A / N information is transmitted in time slot #n, the A / N information can include the maximum possible A / N based on the binding window. That is, the A / N information for time slot #n can include the A / N corresponding to time slot #(nk). For example, if k∈{1,2,3,4,5,6,7,8}, then the A / N information for time slot #n includes the A / N corresponding to time slots #(n-8) to #(n-1) (i.e., the maximum number of A / Ns), regardless of the actual DL data reception. Here, the A / N information can be replaced by an A / N codebook and an A / N payload. Furthermore, a time slot can be understood as / substituted as a candidate timing for DL ​​data reception. As an example, the binding window can be determined based on the PDSCH to A / N timing based on the A / N time slot, and the PDSCH to A / N timing set can have predefined values ​​(e.g., {1,2,3,4,5,6,7,8}) or can be configured via higher-layer (RRC) signaling.

[0158] The dynamic / semi-static HARQ-ACK codebook configurations defined in the NR standard are as follows. When the UE is configured with a semi-static PDSCH HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook) parameter, the UE determines a Type 1 HARQ-ACK codebook report (i.e., a semi-static HARQ-ACK codebook). On the other hand, when the UE is configured with a dynamic PDSCH HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook) (or pdsch-HARQ-ACK-Codebook-r16) parameter, the UE determines a Type 2 HARQ-ACK codebook report (i.e., a dynamic HARQ-ACK codebook).

[0159] HARQ-ACK codebook configuration method for multi-PDSCH scheduling

[0160] -PUSCH: Physical Uplink Shared Channel

[0161] -RRM: Radio Resource Management

[0162] -SCS: Subcarrier Spacing

[0163] -RLM: Radio Link Monitoring

[0164] -DCI: Downlink Control Information

[0165] -CAP: Channel Access Procedure

[0166] -Ucell: Unauthorized cell

[0167] -TBS: Transport Block Size

[0168] -TDRA: Time Domain Resource Allocation

[0169] -SLIV: Start and Length Indicator Value. (It is an indicator of the start symbol index and the number of symbols in the time slot of the PDSCH and / or PUSCH. It can be configured as part of an entry in the TDRA field of the PDCCH for scheduling the corresponding PDSCH / or PUSCH.)

[0170] -BWP: Bandwidth portion (which can be configured with contiguous resource blocks (RBs) on the frequency axis. A set of parameters (e.g., SCS, CP length, slot / micro-slot duration, etc.). Multiple BWPs can be configured on a single carrier (the number of BWPs per carrier can also be limited), however, the number of active BWPs can be limited to a portion of each carrier (e.g., one).

[0171] -CORESET: Control resource set (which means the time-frequency resource area in which PDCCH can be sent; the number of CORESETs per BWP can be limited).

[0172] -REG: Resource Element Group

[0173] -SFI: Slot Format Indicator (It is an indicator that indicates the symbol-level DL / UL direction in a specific slot, and it is transmitted via the group common PDCCH.)

[0174] -COT: Channel Occupancy Time

[0175] -SPS: Semi-persistent scheduling

[0176] -QCL: Quasi-co-located (The QCL relationship between two reference signals (RS) means that QCL parameters obtained from one RS (e.g., Doppler shift, Doppler spread, average delay, average spread, and spatial reception parameters) can be applied to other RSs (or the antenna ports of the corresponding RSs). In NR systems, four QCL types are defined as follows: 'typeA': {Doppler shift, Doppler spread, average delay, delay spread}, 'typeB': {Doppler shift, Doppler spread}, 'typeC': {Doppler shift, average delay}, 'typeD': {Spatial Rx parameters}. For a given DL RS antenna port, the first DL RS is configured as a reference for QCL type X (X = A, B, C, or D), and the second DL RS can be configured as a reference for QCL type Y (Y = A, B, C, or D, but X ≠ Y).

[0177] -TCI: Transmission Configuration Indicator (A TCI state includes the QCL relationship between one or more DL RSs and the DM-RS ports of PDSCH, DM-RS ports of PDCCH, or CSI-RS resources. For the "Transmission Configuration Indicator" field in the DCI used for scheduling PDSCH, the TCI state index corresponding to each code point in this field is activated by the MAC control element (CE), and the TCI state configuration for each TCI state index is configured via RRC signaling. In version 16NR, corresponding TCI states are configured between DL RSs, but future versions may allow configuration between DL RSs and UL RSs or between UL RSs. Examples of UL RSs include SRS, PUSCH DM-RS, PUCCH DM-RS, etc.)

[0178] -SRI: SRS Resource Indicator (It indicates one of the SRS resource index values ​​configured in the "SRS Resource Indicator" field of the DCI used for scheduling PUSCH. When the UE transmits PUSCH, the UE can transmit the PUSCH by using the same spatial domain transmission filter used for transmitting and receiving reference signals associated with the corresponding SRS resource. Here, the reference RS is configured by RRC signaling of the SRS spatial relation information (SRS-SpatialRelationInfo) parameter for each SRS resource, and SS / PBCH blocks, CSI-RS, or SRS can be configured as reference RS.)

[0179] -TRP: Sending and Receiving Point

[0180] To improve the transmission efficiency of DCIs scheduled for PDSCH and / or PUSCH, multiple PDSCH (or PUSCH) transmissions can be supported by a single DCI. For convenience, in this disclosure, the corresponding DCI is referred to as M-DCI, and the DCI that schedules a single PDSCH (or PUSCH) is referred to as S-DCI.

[0181] For example, a higher-layer signaling (e.g., RRC signaling) can be used to configure a terminal to schedule the transmission of multiple PDSCHs (or PUSCHs) via a single DCI. Whether to schedule the transmission of multiple PDSCHs (or PUSCHs) via a single DCI can be configured for each of one or more serving cells configured for the terminal. For example, if information for configuring the scheduling of multiple PDSCHs (or PUSCHs) via a single DCI is provided for the corresponding serving cell, then the scheduling for transmitting multiple PDSCHs (or PUSCHs) via a single DCI on that cell can be configured / supported. On the other hand, if no information for configuring the scheduling of multiple PDSCHs (or PUSCHs) via a single DCI is provided for the corresponding serving cell, then the scheduling for transmitting multiple PDSCHs (or PUSCHs) via a single DCI on that corresponding cell may not be configured / supported.

[0182] Here, even for M-DCI, a single PDSCH can be scheduled, or multiple PDSCHs can be scheduled, depending on the situation. For example, when configuring the TDRA entry for M-DCI, only one SLIV can be linked (associated) with row index #A, and multiple SLIVs can be linked (associated) with row index #B. Here, when row index #A is indicated in M-DCI, this can mean that the corresponding DCI schedules only a single PDSCH; on the other hand, when row index #B is indicated in M-DCI, this can mean that the corresponding DCI schedules multiple PDSCHs. For convenience, the case of scheduling via S-DCI and scheduling only one PDSCH via M-DCI (or when the DCI indicates that the SPS PDSCH is released or the SCell is in a sleep state) is referred to as the single PDSCH case, and the case of scheduling multiple PDSCHs via M-DCI is referred to as the multi-PDSCH case.

[0183] Therefore, in this disclosure, it is recommended to consider the multiple PDSCH case when configuring the type 1 (i.e., semi-static) or type 2 (i.e., dynamic) HARQ-ACK codebook (HCB).

[0184] In NR systems, the millimeter wave (mmWave) band (e.g., above 125 or 24 GHz to 52.6 GHz) is defined as Frequency Range 2 (FR2). The subcarrier spacing (SCS) of the SS / PBCH block in the corresponding band can be 120 kHz or 240 kHz, and the SCS of other signals / channels (e.g., PDCCH, PDSCH, PUSCH, etc.) can be 60 kHz or 120 kHz.

[0185] In high-frequency NR systems (e.g., above 52.6 GHz to 71 GHz, referred to as FR3 (or FR2-2) for ease of description), larger SCSs can be introduced. If the scalability of the OFDM symbol duration and CP length defined in the current NR system is maintained, the OFDM symbol duration and CP length for each SCS can be defined using the lengths shown in Table 6 below.

[0186] [Table 6]

[0187] SCS[kHz] 120 240 480 960 Symbol duration 8.33μs 4.17μs 2.08μs 1.04μs CP length 586ns 293ns 146ns 73ns

[0188] In the FR3 (or FR2-2) band, considering the terminal's monitoring capabilities, PDCCH monitoring can be performed in one time slot out of every multiple time slots. Considering the reduced PDCCH monitoring opportunity area, the operation of scheduling multiple PDSCHs and / or multiple PUSCHs via a single DCI can be introduced. However, the PDSCHs and / or PUSCHs indicated by the DCI can be instructed to be transmitted not only in FR3 (or FR2-2) but also in another frequency range. That is, the M-DCI proposed in this disclosure is not limited to NR systems operating in FR3 (or FR2-2) and can be applied to other frequency ranges.

[0189] Example 1: Time Binding Configuration Method

[0190] Specifically, considering the introduction of 480 / 960kHz SCS in the FR3 band, even if multiple PDSCHs are scheduled across multiple time slots via M-DCI, the absolute duration of these multiple PDSCHs may be quite short. Therefore, since the channel may not change significantly during the corresponding duration (or multiple PDSCHs), the decoding success / failure results of multiple PDSCHs can be identical. When configuring time-binding periods with this in mind, the HARQ-ACK payload can be reduced by binding (i.e., logical AND operation) the ARQ-ACK results within the corresponding duration. Based on this, a specific time-binding method is proposed.

[0191] In other words, when HARQ time binding is configured for a specific serving cell, multiple PDSCHs scheduled on the specific serving cell can be grouped into one or more groups (or they can be called binding groups, HARQ groups, or HARQ binding groups, etc.), and HARQ-ACK information is generated for each of the one or more groups.

[0192] For example, time binding can be configured for a terminal via higher-layer signaling (e.g., RRC signaling). Whether or not time binding is configured can be set for each of one or more serving cells configured for the terminal. For instance, if information for configuring time binding is provided for the corresponding serving cell, time binding can be configured / supported for multiple PDSCHs scheduled on that cell. Conversely, if no information for configuring time binding is provided for the corresponding serving cell, time binding can be left unconfigured / unsupported for multiple PDSCHs scheduled on that cell.

[0193] In this disclosure, for ease of description, the binding of HARQ-ACK information for multiple PDSCHs is referred to as time binding, but this disclosure is not limited to this, and it may also be referred to as HARQ binding, HARQ-ACK binding, etc.

[0194] Method 1: A time-binding method based on the number of PDSCHs in the schedule is proposed. That is, multiple PDSCHs can be bound (grouped) into one or more groups based on a predetermined number of PDSCHs.

[0195] Specifically, in the case of multiple PDSCHs with M (M is a natural number) or fewer, the PDSCHs can be bound into one group, and in the case of multiple PDSCHs with more than M PDSCHs, the PDSCHs can be divided into two groups and bound. Here, the value of M can be half of the maximum number of PDSCHs that can be scheduled by the M-DCI configured in the corresponding cell (or in all cells configured for the terminal) (if the half value is not an integer, it can be converted to an integer by rounding down, rounding up, or rounding). Alternatively, the value of M can be configured by higher-layer signaling. Specifically, when the actual number of scheduled PDSCHs is N (> M), the first M PDSCHs (e.g., the earliest M PDSCHs in the time domain) can be bound to group 1, and the remaining NM PDSCHs can be bound to group 2. Alternatively, the first part (N / 2) of the PDSCHs can be bound to group 1, and the remaining part (N / 2) of the PDSCHs can be bound to group 2.

[0196] -Method 2: A time-binding method based on the number of time slots occupied by PDSCH is proposed. That is, multiple PDSCHs can be bound into one or more groups based on a predetermined number of PDSCH time slots.

[0197] Specifically, in the case of multiple PDSCHs with L (L is a natural number) or fewer slots, the PDSCHs can be bound into one group. In the case of multiple PDSCHs with more than L slots, the PDSCHs can be divided into two groups and bound. Here, the value of L can be half of the maximum number of PDSCH slots that the M-DCI configured in the corresponding cell (or in all cells configured for the terminal) can schedule (i.e., the maximum value among the slot durations from the first PDSCH slot to the last PDSCH slot). (If the half value is not an integer, it can be converted to an integer using rounding, floor operations, or other methods). Alternatively, the value of L can be configured via higher-layer signaling. Specifically, when the actual scheduled slot duration from the first PDSCH slot to the last PDSCH slot is K slots (>L), the PDSCHs for the first L slot durations are bound to group 1, and the remaining PDSCHs for the remaining KL slot durations can be bound to group 2. Alternatively, the PDSCH for the duration of the first portion (K / 2) of the time slots can be bound to group 1, and the PDSCH for the duration of the remaining portion (K / 2) of the time slots can be bound to group 2.

[0198] - Method 3: Regardless of the number of PDSCHs and time slots, multiple PDSCHs can always be time-bound into two groups. When the actual number of scheduled PDSCHs is N, the first part (N / 2) of the PDSCHs can be bound to group 1, and the remaining part (N / 2) of the PDSCHs can be bound to group 2.

[0199] Alternatively, through further extension, G groups (G is a natural number) can be configured, and multiple PDSCHs can be time-bound (or grouped) into G groups. Here, multiple PDSCHs can be mapped to each group in the order of scheduled (or valid) PDSCHs (in ascending order of group index) (in other words, multiple PDSCHs are mapped to each group in chronological order, and this process can be repeated cyclically until all PDSCHs are mapped to groups). For example, if 5 PDSCHs are scheduled (or valid) through 1 DCI and G=4, then PDSCH#0 / 4 can correspond to (map to) group #0, PDSCH#1 can correspond to (map to) group #1, PDSCH#2 can correspond to (map to) group #2, and PDSCH#3 can correspond to (map to) group #3. Here, a valid PDSCH can refer to a PDSCH that does not overlap with symbols (or time slots including the corresponding symbols) configured for uplink (or flexible) via parameters for TDD UL-DL common configuration (e.g., tdd-UL-DL-ConfigurationCommon) or TDD UL-DL dedicated configuration (e.g., tdd-UL-DL-ConfigurationDedicated). Here, the terminal can perform a logical AND operation for each binding group (i.e., HARQ-ACK information can be generated for each binding group).

[0200] If multiple PDSCHs are mapped to binding groups in the order of their scheduling (i.e., regardless of PDSCH validity), valid and invalid PDSCHs can coexist (both belong to the same binding group) or only the invalid PDSCH may exist in a specific binding group. Here, if valid and invalid PDSCHs coexist in a specific binding group (if both belong to the same binding group), the terminal can treat the invalid PDSCH as an ACK and perform a logical AND operation on the corresponding binding group. However, when only invalid PDSCHs exist in a specific binding group, the terminal can treat the invalid PDSCH as a NACK, or treat the HARQ-ACK information corresponding to that binding group as a NACK. For example, in the example above, if we assume that PDSCH#0 mapped to group #0 is a valid PDSCH, and PDSCH#4 mapped to group #0 is an invalid PDSCH (i.e., both valid and invalid PDSCHs belong to the same binding group), then the HARQ-ACK information corresponding to PDSCH#4 can be treated as an ACK. As another example, in the example above, if we assume that PDSCH#1 mapped to group #1 is an invalid PDSCH (i.e., only invalid PDSCHs exist in a particular binding group), then the HARQ-ACK message corresponding to PDSCH#1 can be regarded as NACK. Alternatively, the HARQ-ACK message corresponding to the corresponding group #1 can be regarded as NACK.

[0201] For ease of description, methods 1 to 3 are mainly described for the case where the number of groups is 2. However, the same methods can be extended and applied even when the number of groups is configured to be greater than 2 or 1.

[0202] As mentioned in Method 3 above, the number of binding groups can be configured, as follows.

[0203] If the UE is configured with a number of HARQ-BundlingGroups for serving cell c (i.e., if the number of HARQ-BundlingGroups is configured via RRC parameters), the UE generates HARQ-ACK information via the Transport Block Group (TBG) used for PDSCH reception. Here, N represents the maximum number of PDSCH receptions scheduled in DCI format on the serving cell. max PDSCH The maximum number of TBGs, N TBG,max HARQ-ACK,c Provided by numberOfHARQ-BundlingGroups. If the UE detects that N is scheduled on serving cell c. PDSCH,c If the DCI format received by each PDSCH is given, the UE generates N for the first TB. TBG,max HARQ-ACK,c1 HARQ-ACK information bit, and by setting N CBG / TB,max HARQ-ACK =N TBG,max HARQ-ACK,c and C=N PDSCH,c And generate for N PDSCH,c The second TB of N received by a PDSCH TBG,max HARQ-ACK,c One HARQ-ACK information bit. That is, the binding group can be generated in the same way as the following code block group (CBG).

[0204] If the UE is configured with CBG transmissions for the serving cell's PDSCH (PDSCH - Code Block Group Transmission), the UE receives PDSCHs scheduled in DCI format 1_1, which include CBGs of transport blocks. The UE is also configured with a maximum number of CBGs (i.e., an indication N is provided). CBG / TB,max HARQ-ACK The maximum number of CBGs per TB (maxCodeBlockGroupsPerTransportBlock) is used to generate the corresponding HARQ-ACK information bits for the transport block reception of the serving cell.

[0205] For the number of C code blocks (CBs) in a transport block, the UE determines the number M of CBGs and the number of HARQ-ACK bits in the transport block as N. CBG / TB HARQ-ACK =M.

[0206] If the UE correctly receives all code blocks of the CBG, the UE generates an ACK for the HARQ-ACK information bits of the CBG. If the UE incorrectly receives at least one code block of the CBG, the UE generates a NACK for the HARQ-ACK information bits of the CBG. If the UE receives two TBs, the UE concatenates the HARQ-ACK information bits for the CBG of the second TB after the HARQ-ACK information bits for the CBG of the first TB.

[0207] The HARQ-ACK codebook includes N CBG / TB,max HARQ-ACK N HARQ-ACK information bits, and if for TB N CBG / TB HARQ-ACK <N CBG / TB,max HARQ-ACK Then the UE generates the last N for TB in the HARQ-ACK codebook. CBG / TB,max HARQ-ACK -N CBG / TB HARQ-ACKThe NACK value of each HARQ-ACK information bit.

[0208] If the UE generates a HARQ-ACK codebook in response to a TB retransmission, corresponding to the same HARQ procedure as the previous TB transmission, the UE generates an ACK for each CBG that the UE correctly decoded in the previous TB transmission.

[0209] If the UE correctly detects N CBG / TB HARQ-ACK Each of the CBGs and no correct detection was made for N. CBG / TB HARQ-ACK For each CBG TB, the UE generates a TB for N. CBG / TB HARQ-ACK The NACK value for each of the CBGs.

[0210] Simultaneously, when generating binding groups, as described above, binding groups can be generated based on a pre-configured SLIV linked (associated) with TDRA information indicated by DCI. Here, when valid PDSCHs and invalid PDSCHs coexist (or both belong to each other) or when only invalid PDSCHs may exist in a particular binding group, a HARQ-ACK generation method needs to be defined for the corresponding binding group. Here, a valid PDSCH may refer to a PDSCH that does not overlap with a symbol (or time slot including the corresponding symbol) configured as uplink (or flexible) by parameters for TDD UL-DL common configuration (e.g., tdd-UL-DL-ConfigurationCommon) or parameters for TDD UL-DL dedicated configuration (e.g., tdd-UL-DL-ConfigurationDedicated). On the other hand, an invalid PDSCH can refer to a PDSCH that overlaps with a symbol (or time slot including the corresponding symbol) configured for uplink (or flexible) via parameters for TDD UL-DL common configuration (e.g., tdd-UL-DL-ConfigurationCommon) or parameters for TDD UL-DL dedicated configuration (e.g., tdd-UL-DL-ConfigurationDedicated). If valid and invalid PDSCHs coexist (both belong to) a specific binding group, then when all valid PDSCHs belonging to that binding group are correctly received, a HARQ-ACK message corresponding to that binding group is generated as an ACK message; otherwise (i.e., when even one of the valid PDSCHs belonging to the corresponding binding group is not correctly received), it can be expected to be generated as a NACK. In other words, when generating HARQ-ACK messages corresponding to a binding group (to which both valid and invalid PDSCHs belong),

[0211] Alternative (Alt) 1: An invalid PDSCH can be considered (or assumed) to have been received correctly, or

[0212] Alt 2: Invalid PDSCH can preferably be ignored.

[0213] As an example, the above content can be reflected in the standard as follows.

[0214] Alt 1: If the UE is configured with a number of HARQ-BundlingGroups in serving cell c (i.e., if the number of HARQ-BundlingGroups is configured via RRC parameters), then the UE generates HARQ-ACK information on the Transport Block Group (TBG) for PDSCH reception. Here, N represents the maximum number of PDSCH receptions scheduled in DCI format on the serving cell. max PDSCH The maximum number of TBGs, N TBG,max HARQ-ACK,c Provided by numberOfHARQ-BundlingGroups. If the UE detects that N is scheduled on serving cell c. PDSCH,c If the DCI format received by each PDSCH is given, the UE generates N for the first TB. TBG,max HARQ-ACK,c N HARQ-ACK information bits, and in the following manner PDSCH,c N is generated in each PDSCH receiver for the second TB. TBG,max HARQ-ACK,c One HARQ-ACK information bit: Set N CBG / TB,max HARQ-ACK =N TBG,max HARQ-ACK,c and C=N PDSCH,c Furthermore, for TBGs with at least one actual PDSCH reception, it is assumed that the PDSCH overlapping with the UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is correctly received (if any).

[0215] Alt 2: Alt 1: If the UE is configured with a number of HARQ-BundlingGroups in serving cell c (i.e., if the number of HARQ-BundlingGroups is configured via RRC parameters), then the UE generates HARQ-ACK information for PDSCH reception via Transport Block Group (TBG). Here, N is the maximum number of PDSCH receptions scheduled in DCI format on the serving cell. max PDSCHThe maximum number of TBGs, N TBG,max HARQ-ACK,c Provided by numberOfHARQ-BundlingGroups. If the UE detects that N is scheduled on serving cell c. PDSCH,c If the DCI format received by each PDSCH is given, the UE generates N for the first TB. TBG,max HARQ-ACK,c N HARQ-ACK information bits, and in the following manner at N PDSCH,c N is generated in each PDSCH receiver for the second TB. TBG,max HARQ-ACK,c One HARQ-ACK information bit: Set N CBG / TB,max HARQ-ACK =N TBG,max HARQ-ACK,c and C=N PDSCH,c Furthermore, for TBGs with at least one actual PDSCH reception, PDSCHs that overlap with UL symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are ignored (if any).

[0216] Example 2: Configuration method for Type 1 HARQ-ACK codebook (HCB) when configuring time binding.

[0217] HARQ-ACK timing (slots) can be determined as follows: based on the last PDSCH transmission slot (in time) among multiple PDSCHs scheduled from the M-DCI, apply the Kl value (indicated by the corresponding DCI) (in this disclosure, Kl represents the slot interval between the PDSCH transmission slot and the HARQ-ACK transmission slot used for the corresponding PDSCH reception). Based on this, HARQ-ACK feedback for all multiple PDSCHs scheduled from the DCI can be sent together using the same (corresponding) HARQ-ACK timing.

[0218] Therefore, HARQ-ACK feedback (for all PDSCHs scheduled from the corresponding DCI) can be multiplexed only among M-DCIs (and S-DCIs) indicating the same time slot as the last PDSCH transmission time slot as the HARQ-ACK timing, and can be sent through the same HARQ-ACK timing.

[0219] Simultaneously, with a set of multiple (e.g., K_N) candidate K1 values ​​configured, in the case of existing type 1HCB, the terminal calculates a combination of all PDSCH opportunities (SLIVs) that can be transmitted in K1 previous DL slots based on the HARQ-ACK transmission slots for each K1 value (configured in the corresponding cell of each serving cell). Then, the terminal configures the timing for candidate PDSCH reception corresponding to each DL slot (including determining the position / order of the HARQ-ACK bits corresponding to each SLIV) (this is defined as "SLIV pruning"). HARQ-ACK information bits are constructed for each opportunity included in the set of candidate PDSCH reception opportunities obtained through this process, and the entire HARQ-ACK codebook can be constructed by concatenating each HARQ-ACK information bit.

[0220] In other words, 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 terminal via (DL-licensed) DCI. In this case, the terminal can operate to send A / N feedback for (multiple) PDSCH receptions in multiple time slots (or sets of time slots) corresponding to the entire set of candidate HARQ timings, using the indicated HARQ timing. Here, HARQ timing means PDSCH to A / N timing / interval. HARQ timing can be expressed in units of time slots. For example, when an A / N transmission is indicated in time slot #m, the A / N information may include response information for PDSCH receptions in time slot #(mi). Here, time slot #(mi) corresponds to the time slot corresponding to the candidate HARQ timing. Here, when the candidate HARQ timing is configured as i = {2,3,4,5}, and when the A / N transmission time is indicated by #(n+5)(=m), the terminal can generate / transmit A / N information for PDSCH reception in time slots #n to #(n+3)(=mi) (i.e., A / N feedback for all four time slots). Here, the A / N response to PDSCH reception in time slots #n+1 / #n+3 can be processed as NACK.

[0221] The following are some relevant standards for reference.

[0222] For serving cell c, active DLB WP, and active UL BWP, the UE determines the M for candidate PDSCH reception. A,C For the timing set, the UE can receive candidate PDSCH in time slot n. U The corresponding HARQ-ACK information is sent in the PUCCH. If the serving cell c is disabled, the UE uses the DL BWP provided by firstActiveDownlinkBWP-Id as the active DL BWP to determine the M for candidate PDSCH reception. A,CA set of timings. This determination is based on:

[0223] a) This determination is based on a set of time slot timing values ​​K associated with the active UL BWP. l .

[0224] - If the UE is configured to monitor the PDCCH of DCI format 1_0 on the serving cell c and is not configured to monitor the PDCCH of DCI format 1_1 or DCI format 1_2 on the serving cell c, then K1 is provided by the time slot timing value {1,2,3,4,5,6,7,8}.

[0225] - If the UE is configured to monitor the PDCCH of DCI format 1_1 for serving cell c and is not configured to monitor the PDCCH of DCI format 1_2 for serving cell c, then K l Provided by dl-DataToUL-ACK.

[0226] - If the UE is configured to monitor the PDCCH of DCI format 1_2 for serving cell c and is not configured to monitor the PDCCH of DCI format 1_1 for serving cell c, then K l Provided by dl-DataToUL-ACK-ForDCIFormat1_2.

[0227] - If the UE is configured to monitor the PDCCH of DCI format 1_1 and DCI format 1_2 of serving cell c, then K1 is provided by the union of dl-DataToUL-ACK and dl-DataToUL-ACK-ForDCIFormat1_2.

[0228] b) This determination is based on a set of row indexes R of a table associated with the active DL BWP and defining a corresponding set of slot offset K0, start and length indicators SLIV, and PDSCH mapping types for PDSCH reception. Here, the row index R of the table is provided by the union of the row indexes of the time-domain resource allocation table in DCI format used by the UE to monitor the PDCCH of serving cell c.

[0229] - If referenceOfSLIVDCI-1-2 is provided to the UE, then for each row index with slot offset K0 = 0 and PDSCH mapping type B in the set of row indexes of the table for DCI format 1_2, for each PDCCH monitoring opportunity in a set of PDCCH monitoring opportunities with different start symbols in a slot where the UE monitors the PDCCH of DCI format 1_2 and has start symbol S0 > 0, if for normal cyclic prefix S+S0+L≤14 and for extended cyclic prefix S+S0+L≤12, then a new row index is added to the set of row indexes of the table by replacing the start symbol S of the row index with S+S0.

[0230] In this embodiment, a Type 1HCB configuration method is proposed when time binding is configured as in Embodiment 1 above.

[0231] First, SLIV pruning can be performed solely based on the last SLIV (in each row of the TDRA table). That is, the set of opportunities for candidate PDSCH reception that can send the corresponding HARQ-ACK information in the PUCCH within a specific time slot can be determined based solely on the last SLIV of each row in the TDRA table. For example, one or more rows in the TDRA table can indicate multiple SLIV values ​​for scheduling multiple PDSCHs. For instance, row index 2: {SLIV1, SLIV2, SLIV3}, row index 3: {SLIV4, SLIV5} can be configured / defined. In this case, the set of opportunities for candidate PDSCH reception can be determined solely based on the last SLIV of each row in the TDRA table. That is, by considering only row index 2: {SLIV3} and row index 3: {SLIV5}, the set of opportunities for candidate PDSCH reception can be determined.

[0232] After performing SLIV pruning on each DL slot (i.e., slot n-K1 when HARQ-ACK is sent in slot n) corresponding to each K1 in the set of multiple candidate Kl values, if HARQ-ACK transmission is required for group G at any of the TDRA row indices corresponding to the corresponding K1, then the number of (G-1) opportunities can be added to the SLIV pruning result. For example, if G=1, no opportunities need to be added to the SLIV pruning result.

[0233] For example, the TDRA entry for M-DCI in a specific cell can be as follows.

[0234] - Row index #0: Links (associates) 5 SLIV values, and the final SLIV = {S = 0, L = 5}

[0235] - Row index #1: Links (associates) 3 SLIV values, and the final SLIV = {S = 2, L = 5}

[0236] Additionally, the TDRA entries used for the corresponding S-DCI in the cell can be as follows.

[0237] - Row index #0: SLIV = {S = 9, L = 5}

[0238] For a given cell, for a given DL time slot corresponding to a given Kl, when SLIV pruning is performed only based on the last SLIV (i.e., determining the set of opportunities for candidate PDSCH reception), two opportunities for candidate PDSCH reception can be allocated to the corresponding DL time slot (e.g., one opportunity for receiving candidate PDSCH via M-DCI and one opportunity for receiving candidate PDSCH via S-DCI).

[0239] Similar to Method 1 in Example 1, it is assumed that two groups for time binding are configured and M = 4. In this case, when row index #0 is indicated by M-DCI, since a total of 5 PDSCHs are scheduled, the PDSCHs can be bound into two groups. On the other hand, when row index #1 is indicated by M-DCI, since a total of 3 PDSCHs are scheduled, the PDSCHs can be bound into one group.

[0240] In this scenario, at least two groups are required for row index #0, so the number of times candidate PDSCHs can be three in the final corresponding DL slot (e.g., two times for candidate PDSCH reception via M-DCI (for each group), and one time for PDSCH reception via S-DCI). If row index #0 or 1 of M-DCI is scheduled, the HARQ-ACK information can correspond to the first two times within that time slot, where, in the case of row index #1, a NACK can be filled in the second time slot (because there is no PDSCH corresponding to the second group). And when row index #0 of S-DCI is scheduled, the HARQ-ACK information can correspond to the third time slot. That is, the HARQ-ACK information can first correspond to the time slot for receiving candidate PDSCHs via M-DCI, and then the HARQ-ACK information can correspond to the time slot for receiving candidate PDSCHs via S-DCI.

[0241] As another example, the TDRA entry for M-DCI in a specific cell can be as follows.

[0242] - Row index #0: Links (associates) 5 SLIV values, and the final SLIV = {S = 9, L = 5}

[0243] - Row index #1: Links (associates) 3 SLIV values, and the final SLIV = {S = 10, L = 4}

[0244] Additionally, the TDRA entries for the corresponding S-DCI in the cell can be as follows.

[0245] - Row index #0: SLIV = {S = 0, L = 5}

[0246] For a given cell, for a given DL time slot corresponding to a given Kl, when SLIV pruning is performed only based on the last SLIV (i.e., determining the set of opportunities for candidate PDSCH reception), two opportunities for candidate PDSCH reception can be allocated to the corresponding DL time slot (e.g., one opportunity for receiving candidate PDSCH via M-DCI and one opportunity for receiving candidate PDSCH via S-DCI).

[0247] Similar to Method 1 in Example 1, it is assumed that two groups for time binding are configured and M = 4. In this case, when row index #0 is indicated by M-DCI, since a total of 5 PDSCHs are scheduled, the PDSCHs can be bound into two groups. On the other hand, when row index #1 is indicated by M-DCI, since a total of 3 PDSCHs are scheduled, the PDSCHs can be bound into one group.

[0248] In this scenario, at least two groups are required for row index #0, so the number of opportunities for candidate PDSCH reception in the final corresponding DL time slot can be 3 (e.g., two opportunities for candidate PDSCH reception via M-DCI (due to each group), and one opportunity for PDSCH reception via S-DCI). If row index #0 or 1 is scheduled for M-DCI, the HARQ-ACK information can correspond to the first and third opportunities within the corresponding opportunity, where, in the case of row index #1, a NACK can be filled in the third opportunity (because there is no PDSCH corresponding to the second group). And when row index #0 of S-DCI is scheduled, the HARQ-ACK information can correspond to the second opportunity. That is, based on SLIV pruning only based on the last SLIV, one opportunity is first allocated for row index #0 of S-DCI, and row index #0 / 1 for M-DCI is allocated as the next opportunity, so a total of 2 opportunities can be configured. Here, additional opportunities due to time binding are configured before the corresponding two opportunities, so that a total of three opportunities can be allocated to the corresponding DL time slots. In other words, the HARQ-ACK message corresponds to the timing of receiving the candidate PDSCH via S-DCI, and then the HARQ-ACK message corresponds to the timing of receiving the candidate PDSCH via M-DCI. If there is a timing due to time binding in the timing of receiving the candidate PDSCH via M-DCI, the HARQ-ACK message can first correspond to it.

[0249] Example 3: Type 1HCB configuration method when configuring PDCCH monitoring based on time slot groups

[0250] Due to the introduction of higher SCS such as 480 / 960kHz, performing PDCCH monitoring per time slot can be a burden on UE implementations. With this in mind, time slot group-based PDCCH monitoring can be introduced.

[0251] Figure 10 This is a diagram illustrating PDCCH monitoring based on time slot groups according to an embodiment of the present disclosure.

[0252] refer to Figure 10 Four time slots (i.e., Gr = 4) are defined as a time slot group, and PDCCH monitoring can be restricted to certain regions within the corresponding time slot group (e.g., the first time slot). This time slot group can be predefined (for each SCS), configured via higher-level signaling, or it can be a value derived by the terminal from the search space set configuration. Furthermore, the time slot group can be used as a criterion for calculating the maximum number of PDCCH candidates and / or the maximum number of non-overlapping control channel elements (CCEs), and can be used as a criterion for discarding search space sets based on their corresponding numbers.

[0253] According to this embodiment, for the corresponding cell, SLIV pruning can be performed on the entire time slot group, instead of on a specific DL time slot corresponding to a specific Kl. Here, for the case of multiple PDSCHs with a specific time slot in the corresponding time slot group as the first PDSCH time slot, scheduling restrictions that only schedule within the same time slot group can be configured / defined. That is, for the case of multiple PDSCHs with a specific time slot in the nth time slot group as the first PDSCH time slot, the following restrictions are required: all PDSCHs scheduled by the corresponding M-DCI should belong to the corresponding nth time slot group, and no single PDSCH should be scheduled to belong to the (n+1)th time slot group. In other words, when scheduling multiple PDSCHs through M-DCI, all multiple PDSCHs need to be scheduled within a single time slot group.

[0254] Specifically, for each Kl, SLIV trimming can be performed on all time slots belonging to the time slot group where the time slot indicated by each Kl becomes the last time slot.

[0255] Figure 11 This is a diagram illustrating the determination of a set of timings for candidate PDSCH reception according to an embodiment of the present disclosure.

[0256] refer to Figure 11When slot #9 is the UL slot to which HARQ-ACK is sent, K1 set = {2,3,4,5,6,7}, and the TDRA entries for M-DCI are configured as row indices #0, #1, #2, SLIV pruning corresponding to slot-group #1 is exemplified. When K1 = 2, since the corresponding slot #7 belongs to slot group #1, SLIV pruning can be performed on the entire K1 = 2 / 3 / 4 / 5 corresponding to slot group #1. That is, the row indices corresponding to each of K1 = 2 / 3 / 4 / 5 can be arranged as follows: Figure 11 As shown (under scheduling constraints), a SLIV pruning process (replacing existing time slots with all 56 symbols of the time slot group and the corresponding time slot group) can be performed on all 9 SLIV sequences corresponding to time slot group #1. As a result, 4 time slots can be allocated to the corresponding time slot group #1. If the actual scheduling via M-DCI is to schedule 3 PDSCHs from time slot #5 with row index #0, then the 2nd / 3rd / 4th time slots can correspond to each PDSCH.

[0257] Example 4: Type 2HCB Configuration Method Considering M-DCI

[0258] In the case of traditional S-DCI, the counter DAI (C-DAI) and the total DAI (T-DAI) are counted as 1 for each DCI or each PDSCH. On the other hand, in the case of M-DCI, since there may be multiple PDSCHs corresponding to one DCI, the method used to count the DAI value can vary, and the following methods can be considered.

[0259] –Alt 1: Count DAI (C-DAI and T-DAI) for each DCI

[0260] –Alt 2: Count DAI (C-DAI and T-DAI) per PDSCH

[0261] Here, if at least one symbol of a particular PDSCH among multiple scheduled PDSCHs overlaps with a UL symbol configured for higher-layer (e.g., RRC) signaling, the corresponding PDSCH may not be sent. In this case, the DAI of the corresponding PDSCH can be omitted without counting.

[0262] -Alt3: For each of the W PDSCH counts, the DAI value (W is a natural number), where the W value can be configured by higher-level (e.g., RRC) signaling (or can be a pre-defined fixed value).

[0263] Here, when configuring M-DCI for multiple cells in the same cell group, the corresponding W value can preferably be configured as a value common to the corresponding cells. This is because by matching the HARQ-ACK structural units between cells, ambiguity can be eliminated even if a specific DCI is lost.

[0264] In the following sections, for each alternative in this embodiment, a method for configuring C-DAI / T-DAI signaling, HARQ-ACK payload size, and HCB (HARQ-ACK codebook) in DL / UL DCI when CBG is configured in addition will be proposed.

[0265] In addition, for each alternative, methods for configuring a single CB (codebook) for single PDSCH and multiple PDSCH cases, as well as methods for configuring an individual sub-codebook (sub-CB) (i.e., HARQ-ACK sub-codebook) for each, are divided and suggested.

[0266] In this disclosure, configuring individual sub-CBs means independently determining and signaling the C / T-DAI value for each sub-CB (i.e., independently determining / signaling the order / total number of DCI / PDSCHs scheduled for each sub-CB). In other words, the C-DAI and T-DAI values ​​can be applied individually to each HARQ-ACK subcodebook.

[0267] For example, configuring an individual sub-CB for both single-PDSCH and multi-PDSCH scenarios means independently determining and signaling the C / T-DAI value for each scenario (i.e., it can mean independently determining / signaling the order / total number of DCIs / PDSCHs scheduled for each scenario). In other words, the DCI corresponding to the single-PDSCH scenario determines and signales the DAI value only for the single-PDSCH scenario, and the DCI corresponding to the multi-PDSCH scenario determines and signales the DAI value only for the multi-PDSCH scenario. Furthermore, the final HARQ-ACK codebook (HCB) can be constructed by concatenating HARQ-ACK payloads corresponding to different sub-CBs.

[0268] Simultaneously, configuring a single CB can mean determining and signaling a common C / T-DAI value as before (i.e., jointly determining / signaling the order / total number of DCI / PDSCHs scheduled for a single CB). For example, configuring a single CB for both single-PDSCH and multi-PDSCH cases can mean counting and signaling the C / T-DAI value by grouping (combining) the single-PDSCH and multi-PDSCH cases (i.e., determining / signaling the order / total number of DCI / PDSCHs scheduled regardless of each case).

[0269] Example 4-1: DAI count per DCI (i.e., Alt 1 in Example 4 above) + single HARQ-ACK CB (codebook) configuration

[0270] The terminal can configure / generate a CB for single PDSCH and multiple PDSCH scenarios.

[0271] -M-DCI: Can maintain the existing DL DAI size (i.e., 2 bits per C / T-DAI).

[0272] -S-DCI: Can maintain the existing DL DAI size.

[0273] -UL license: The existing UL DAI size can be maintained (i.e., 2 bits for T-DAI).

[0274] -HARQ-ACK payload: This can be determined by the maximum number (Y) of PDSCHs that M-DCI can schedule (Y is a natural number). For example, if 2TB is configured (i.e., PDSCH reception is configured to carry two transport blocks to the corresponding serving cell, or the maximum number of transport blocks (or codewords) that a DCI can schedule is set to 2) and spatial binding for HARQ is not configured, then 2 bits can be calculated for each PDSCH. For cells configured with 2TB but spatial binding, or cells configured with 1TB, 1 bit can be calculated for each PDSCH.

[0275] As another example, with X bits per PDSCH (as mentioned above, X = 2 for a cell configured with 2TB and no spatial binding for HARQ-ACK information; X = 1 for a cell configured with 2TB and spatial binding, or for a cell configured with 1TB), the number of HARQ-ACK bits corresponding to one DAI can be X*Y for both single-PDSCH and multi-PDSCH scenarios. If M-DCI is configured for multiple cells (in a cell group), the number of HARQ-ACK bits for each DAI can be determined by the maximum X*Y value in any cell. That is, it can be determined as the maximum X*Y value among the X*Y values ​​calculated for each cell in the cell group.

[0276] Example 4-1a: DAI count per DCI (i.e., Alt 1 in Example 4 above) + single HARQ-ACK CB (codebook) configuration + when configuring CBG

[0277] 1) Option 1: The terminal can configure / generate individual sub-CBs. That is, a sub-CB can be configured for TB-based PDSCH scheduling in both single-PDSCH and multi-PDSCH scenarios. Additionally, another sub-CB can be configured for CBG-based PDSCH scheduling in the single-PDSCH scenario.

[0278] - When a CBG is configured in a cell where an M-DCI is configured, the DAI in the M-DCI can indicate the C / T-DAI value used for CBG-based PDSCH in the case of a single PDSCH. When no CBG is configured in a cell where an M-DCI is configured, the DAI in the M-DCI can indicate the C / T-DAI value used for TB-based PDSCH in the case of a single PDSCH.

[0279] -S-DCI or M-DCI: can maintain the existing DL DAI size.

[0280] -UL License: In addition to the existing UL DAI size, 2 bits are required for T-DAI (sub-CB for CBG).

[0281] -HARQ-ACK payload: The payload of a sub-CB configured for TB-based PDSCH scheduling in both single-PDSCH and multi-PDSCH scenarios can be configured / determined using the same method as in Example 4-1. Additionally, in the case of a single PDSCH, the payload of another sub-CB configured for CBG-based PDSCH scheduling can be the same as the payload of an existing CBG-based sub-CB configuration.

[0282] 2) Option 2: A single sub-CB can be configured. That is, in both single PDSCH and multi-PDSCH scenarios, a sub-CB can be configured for PDSCH scheduling based on TB or CBG.

[0283] - Regardless of whether a CBG is configured in a cell in which M-DCI is configured, even in the case of a single PDSCH, the DAI in M-DCI can indicate the C / T-DAI value for a single CB.

[0284] -S-DCI or M-DCI or UL license: The DAI size can be maintained in the same manner as in Example 4-1.

[0285] - HARQ-ACK Payload: When the maximum number of CBGs configured is C (C is a natural number), the payload size can be configured / determined by the maximum value between the maximum C value (max_C) in any cell (within a cell group) and the maximum X*Y value (max_XY) in any cell (within a cell group) (derived in Example 4-1 above). That is, for both single PDSCH and multi-PDSCH cases, the number of HARQ-ACK bits corresponding to one DAI can be max{max_C, max_XY}.

[0286] Example 4-1b: DAI count per DCI (i.e., Alt 1 in Example 4 above) + single HARQ-ACK CB (codebook) configuration + when configuration time binding

[0287] When time binding is configured for one or more serving cells (all or some) in the terminal as in Example 1, a type 2HCB configuration is proposed.

[0288] -M-DCI or S-DCI or UL license: As in Example 4-1 above, the DAI size can be maintained.

[0289] -HARQ-ACK Payload: The size of the HARQ-ACK payload can be determined by the (maximum) number of groups (G) configured for time binding (G is a natural number).

[0290] For example, in both single-PDSCH and multi-PDSCH scenarios, the number of HARQ-ACK bits corresponding to one DAI can be G (or X*G) (for example, the value of X can be 2 or 1, depending on whether 2TB is configured in the corresponding serving cell (i.e., whether the maximum number of PDSCH reception carrying two transport blocks or one DCI schedulable transport block (or codeword) is configured). As another example, for a cell where 2TB is configured but spatial binding for HARQ-ACK information is not configured, X = 2. For a cell where 2TB is configured but spatial binding is configured, or for a cell where 1TB is configured, X = 1.

[0291] If M-DCI is configured for multiple cells (within a cell group), the number of HARQ-ACK bits for each DAI can be determined by the maximum G (or X*G) value in any cell. That is, G (or X*G) is compared for each cell in the cell group, and the number of HARQ-ACK bits for each DAI can be determined based on the maximum G (or X*G) value.

[0292] If no PDSCH corresponds to a specific time-binding group (especially when the value of G is 2 or greater), NACK can be mapped. For example, if G=1, the number of HARQ-ACK bits corresponding to a DAI can be 1 (or X) for both single-PDSCH and multi-PDSCH cases (e.g., the value of X can be 2 or 1 depending on whether 2TB is configured in the corresponding serving cell (i.e., whether PDSCH reception carrying two transport blocks is configured, or the maximum number of transport blocks (or codewords) that a DCI can schedule). As another example, X=2 for a cell where 2TB is configured and spatial binding for HARQ-ACK information is not configured. For a cell where 2TB is configured but spatial binding is configured, or a cell where 1TB is configured, X=1. Alternatively, if G=1 is configured for all cells where M-DCI is configured (within the same PUCCH cell group), a single CB can be configured for both single-PDSCH and multi-PDSCH cases.

[0293] When time binding is configured as in the corresponding method, the terminal can construct / generate a single CB for both single-PDSCH and multi-PDSCH scenarios. In this case, if a CBG is configured in a specific serving cell within the same PUCCH group, an individual sub-CB can be configured. In other words, as in Option 1 of Embodiment 4-1a, a sub-CB (configured time binding) can be configured for TB-based PDSCH scheduling in both single-PDSCH and multi-PDSCH scenarios. Additionally, another sub-CB can be configured for CBG-based PDSCH scheduling in the single-PDSCH scenario. In this case, the detailed DCI and HARQ-ACK payload configuration method can be as follows.

[0294] - When a CBG is configured in a cell where an M-DCI is configured, the DAI in the M-DCI can indicate the C / T-DAI value used for CBG-based PDSCH in the case of a single PDSCH. When no CBG is configured in a cell where an M-DCI is configured, the DAI in the M-DCI can indicate the C / T-DAI value used for TB-based PDSCH in the case of a single PDSCH.

[0295] -S-DCI or M-DCI: can maintain the existing DL DAI size.

[0296] - UL Licensing: In addition to the existing UL DAI size, a 2-bit T-DAI (for sub-CBs of CBG) may be required.

[0297] - HARQ-ACK Payload: The payload of a sub-CB configured for TB-based PDSCH scheduling in both single-PDSCH and multi-PDSCH scenarios can be the same as the case without CBG configuration in Example 4-1b above (i.e., for both single-PDSCH and multi-PDSCH scenarios, the number of HARQ-ACK bits corresponding to one DAI can be G or X*G (e.g., the value of X can be 2 or 1, depending on whether 2TB is configured in the corresponding serving cell (i.e., whether PDSCH reception carrying two transport blocks is configured, or the maximum number of transport blocks (or codewords) that a DCI can schedule)). As another example, for a cell where 2TB is configured and spatial binding for HARQ-ACK information is not configured, X = 2. For a cell where 2TB is configured but spatial binding is configured, or a cell where 1TB is configured, X = 1. The payload of another sub-CB configured for CBG-based PDSCH scheduling in the single-PDSCH scenario can be the same as the payload of an existing CBG-based sub-CB configuration.

[0298] Alternatively, when both M-DCI and CBG are configured in the same PUCCH group, the rule can be configured to automatically apply time binding to the multi-PDSCH case (here, the G value can be predefined (e.g., G=1) or configured by the base station). Here, it is possible to define / configure a single CB for both single-PDSCH and multi-PDSCH cases.

[0299] Example 4-2: DAI count per DCI (i.e., Alt 1 in Example 4 above) + individual HARQ-ACK sub-CB (codebook) configuration

[0300] The terminal can configure / generate one sub-CB corresponding to the single PDSCH case and another sub-CB corresponding to the multiple PDSCH case.

[0301] -M-DCI: Can maintain the existing DL DAI size (i.e., 2 bits per C / T-DAI).

[0302] -S-DCI: Can maintain the existing DL DAI size.

[0303] -UL Licensing: In addition to the existing UL DAI size, 2 bits may be required for T-DAI (for the appended sub-CB).

[0304] - HARQ-ACK Payload: The number of HARQ-ACK bits for each sub-CB DAI corresponding to the single PDSCH case is X (e.g., the value of X can be 2 or 1, depending on whether 2TB is configured in the corresponding serving cell (i.e., whether the maximum number of PDSCH reception carrying two transport blocks or a DCI-schedulable transport block (or codeword) is configured). As another example, for a cell where 2TB is configured and spatial binding for HARQ-ACK information is not configured, X = 2. For a cell where 2TB is configured but spatial binding is configured, or for a cell where 1TB is configured, X = 1, and the number of HARQ-ACK bits for each sub-CB DAI corresponding to the multi-PDSCH case is the maximum X*Y value among any cell (in a cell group). That is, it can be determined as the maximum X*Y value among the X*Y values ​​calculated for each cell in the cell group.

[0305] Example 4-2a: DAI count per DCI (i.e., Alt 1 in Example 4 above) + individual HARQ-ACK sub-CB (codebook) configuration + when configuring CBG

[0306] 1) Option 1: The terminal can configure / generate individual sub-CBs. (That is, the first sub-CB can be configured for TB-based PDSCH scheduling in the case of a single PDSCH, the second sub-CB can be configured for the case of multiple PDSCHs, and the third sub-CB can be configured for CBG-based PDSCH scheduling in the case of a single PDSCH.)

[0307] - When a CBG is configured in a cell where an M-DCI is configured, the DAI in the M-DCI can indicate the C / T-DAI value used for CBG-based PDSCH in the case of a single PDSCH. When no CBG is configured in a cell where an M-DCI is configured, the DAI in the M-DCI can indicate the C / T-DAI value used for TB-based PDSCH in the case of a single PDSCH.

[0308] -S-DCI or M-DCI: can maintain the existing DL DAI size.

[0309] - UL Licensing: In addition to the existing UL DAI size, 4 bits are required for the T-DAI (for the two additional sub-CBs). (That is, the T-DAI for each sub-CB increases by 2 bits.)

[0310] -HARQ-ACK Payload: When performing TB-based PDSCH scheduling in a single PDSCH scenario, the payload of the first sub-CB can be the same as the sub-CB in the single PDSCH scenario of Example 4-2. The payload of the second sub-CB configured for the multi-PDSCH scenario can be the same as the sub-CB corresponding to the multi-PDSCH scenario in Example 4-2. The payload of the third sub-CB configured for CBG-based PDSCH scheduling in the single PDSCH scenario can be the same as the payload of the existing CBG-based sub-CB configuration.

[0311] 2) Option 2: The terminal can configure / generate the first sub-CB for TB-based PDSCH scheduling in the single PDSCH case, and can configure / generate the second sub-CB for integrated CBG-based PDSCH scheduling through the single PDSCH case and the multi-PDSCH case.

[0312] - When a CBG is configured in a cell where an M-DCI is configured, the DAI in the M-DCI can indicate the C / T-DAI value used for the second sub-CB in the case of a single PDSCH. When a CBG is not configured in a cell where an M-DCI is configured, the DAI in the M-DCI can indicate the C / T-DAI value of the first sub-CB in the case of a single PDSCH.

[0313] -S-DCI or M-DCI or UL license: can be the same as in Example 4-2.

[0314] - HARQ-ACK Payload: When the maximum number of CBGs configured is C (C is a natural number), the payload size can be configured / determined by the maximum value between the maximum C value (max_C) of any cell (within a cell group) and the maximum X*Y value (max_XY) of any cell (within a cell group) (derived in Example 4-2 above). That is, for both single PDSCH and multi-PDSCH cases, the number of HARQ-ACK bits corresponding to the second sub-CB DAI can be max{max_C, max_XY}. In addition, the number of HARQ-ACK bits for each first sub-CB DAI can be X (X = 1 or 2 depending on the number of TBs and spatial binding configuration as described above).

[0315] 3) Option 3: Simultaneous (together) configuration of M-DCI and CBG in the same PUCCH group may not be permitted. Alternatively, when a Type 1 HARQ-ACK CB is configured for a cell in which M-DCI is configured (or when a Type 2 HARQ-ACK CB is not configured for that cell), CBG configuration may be permitted for other cells in the same PUCCH group (excluding the cell in question).

[0316] Option 1 and / or Option 2 are supported as optional UE features, and Option 3 can be defined / configured as the default operation for terminals that do not support Option 1 and / or Option 2. For terminals that do not support Option 1 and / or Option 2, it is expected that M-DCI and CBG in the same PUCCH group will not be configured simultaneously (together).

[0317] Which method of option 1 and option 2 to apply (for terminals that support both options 1 and 2) can be configured via higher-level signaling (e.g., RRC signaling, MAC CE, etc.). Alternatively, the application of option 1 or option 2 can be determined based on the size between the maximum number of CBGs (i.e., max_C) and the maximum number of PDSCHs or TBs (i.e., max_XY), thereby preventing a significant increase in the overall codebook size. For example, if the max_C and max_XY values ​​are the same, the increase in codebook size is not significant even with the same CB configuration, so option 2 can be applied; otherwise, option 1 can be applied. As another example, if the difference between the max_C and max_XY values ​​is less than or equal to K (where K is predefined (e.g., K=4) or can be configured by higher-level signaling), option 2 can be applied; otherwise, option 1 can be applied.

[0318] Example 4-2b: DAI count per DCI (i.e., Alt 1 in Example 4 above) + individual HARQ-ACK sub-CB (codebook) + when configured for time binding

[0319] When time binding is configured for one or more serving cells (all or some) in the terminal as in Example 1, a type 2HCB configuration is proposed.

[0320] -M-DCI or S-DCI or UL license: As in Example 4-1 above, the DAI size can be maintained.

[0321] - The HARQ-ACK payload of the sub-CB corresponding to the multi-PDSCH case: it can be determined by the (maximum) number (G) of groups configured for time binding (G is a natural number).

[0322] For example, the number of HARQ-ACK bits corresponding to one DAI can be G (or X*G) (for example, the value of X can be 2 or 1, depending on whether 2TB is configured in the corresponding serving cell (i.e., whether the maximum number of PDSCH reception carrying two transport blocks or one DCI schedulable transport block (or codeword) is configured). As another example, for a cell where 2TB is configured and spatial binding for HARQ-ACK information is not configured, X = 2. For a cell where 2TB is configured but spatial binding is configured, or a cell where 1TB is configured, X = 1.

[0323] If M-DCI is configured for multiple cells (within a cell group), the number of HARQ-ACK bits for each DAI can be determined by the maximum G (or X*G) value in any cell. That is, G (or X*G) is compared for each cell in the cell group, and the number of HARQ-ACK bits for each DAI can be determined based on the maximum G (or X*G) value.

[0324] If there is no PDSCH corresponding to a specific time-binding group, NACK can be mapped. Here, for cells that have M-DCI configured but not time-binding configured, the maximum number of PDSCHs that can be scheduled by the corresponding M-DCI (Y) can be used instead of the G value (Y is a natural number).

[0325] In other words, among multiple cells configured with M-DCI (within the same single PUCCH cell group), for cells without time binding or for cells with time binding configured and a G greater than 1 (= the number of PDSCH groups performing time binding), the number of HARQ-ACK bits for each DAI can be determined by the maximum value among the Q values ​​calculated for each cell (e.g., the number of HARQ-ACK bits corresponding to a DCI or a DAI value when configuring the HARQ-ACK codebook).

[0326] Here, in the case of a cell configured with M-DCI but without time binding, the Q value can be calculated as the product of the maximum number of PDSCHs that can be scheduled by M-DCI and X (e.g., the X value can be 2 or 1 depending on whether 2TB is configured in the corresponding serving cell (i.e., whether PDSCH reception carrying two transport blocks is configured or the maximum number of transport blocks (or codewords) that can be scheduled by a DCI). For example, for a cell configured with 2TB but without spatial binding for HARQ-ACK information, X = 2. For a cell configured with 2TB but with spatial binding, or for a cell with 1TB configured, X = 1.

[0327] Alternatively, in the case of a cell configured with M-DCI and a time binding configuration with a G value greater than 1, the Q value can be calculated as the product of G and X (e.g., the X value can be 2 or 1, depending on whether 2TB is configured in the corresponding serving cell (i.e., whether a maximum number of PDSCH receptions carrying two transport blocks or a DCI schedulable transport block (or codeword) is configured). As another example, for a cell configured with 2TB and without spatial binding for HARQ-ACK information, X = 2. For a cell configured with 2TB but with spatial binding, or a cell configured with 1TB, X = 1.

[0328] - HARQ-ACK payload for sub-CBs corresponding to the single PDSCH case: The number of HARQ-ACK bits for each sub-CB DAI corresponding to the single PDSCH case is X (e.g., the value of X can be 2 or 1, depending on whether 2TB is configured in the corresponding serving cell (i.e., whether the maximum number of PDSCH reception carrying two transport blocks or a DCI schedulable transport block (or codeword) is configured). As another example, for a cell configured with 2TB and without spatial binding for HARQ-ACK information, X = 2. For a cell configured with 2TB but with spatial binding or a cell configured with 1TB, X = 1.

[0329] If G=1 is configured for any cell in a cell with M-DCI, then the HARQ-ACK bits corresponding to the M-DCI of the corresponding cell can be carried in the sub-CB corresponding to the single PDSCH case (e.g., the X value can be 2 or 1, depending on whether 2TB is configured in the corresponding serving cell (i.e., whether the maximum number of PDSCH reception carrying two transport blocks or a DCI-schedulable transport block (or codeword) is configured). As another example, for a cell with 2TB configured and no spatial binding for HARQ-ACK information configured, X=2. For a cell with 2TB configured but spatial binding configured, or for a cell with 1TB configured, X=1. That is, a CB can be configured for the multi-PDSCH case of a cell where both single PDSCH and M-DCI are configured and G=1 is configured.

[0330] Meanwhile, when configuring HARQ-ACK codebooks and DAI signaling via DCI, independent DAI signaling can be executed (i.e., C-DAI and T-DAI are applied separately to each HARQ-ACK subcodebook) and individual HARQ-ACK subcodebooks can be configured between the following two PDSCH types.

[0331] - PDSCH Type 1: M-DCI-based PDSCH transmission without time binding (i.e., PDSCH scheduled on one or more cells with M-DCI-based scheduling but no time binding), M-DCI-based PDSCH transmission with a G value greater than 1 (= the number of PDSCH groups with time binding) (i.e., PDSCH scheduled on one or more cells with M-DCI-based scheduling and a G value greater than 1 for time binding).

[0332] -PDSCH Type 2: PDSCH transmissions based on M-DCI with G=1 configured (i.e., PDSCHs scheduled on one or more cells with M-DCI-based scheduling configured and time-bound with G=1) and existing PDSCH transmissions based on S-DCI (i.e., PDSCHs scheduled on one or more cells without M-DCI-based scheduling configured).

[0333] In other words, relative to PDSCH type 1, for a PDSCH that i) is configured with M-DCI-based scheduling but not with time binding, or ii) is configured with M-DCI-based scheduling and has a time binding configured with a G value greater than 1, a first HARQ-ACK subcodebook can be generated. Furthermore, relative to PDSCH type 2, for a PDSCH that i) is configured with M-DCI-based scheduling and has a time binding configured with G=1, or ii) is not configured with M-DCI-based scheduling, a second HARQ-ACK subcodebook can be generated. Here, the multiple serving cells configured in the terminal can correspond to the sum of one or more first serving cells and one or more second serving cells.

[0334] In this case, the individual (UL) DAI field / information for each of PDSCH types 1 and 2 can be configured / indicated in the UL DCI. If PDSCH type 1 as described above does not exist, DAI signaling can be performed only for PDSCH type 2, the HARQ-ACK codebook can be configured only for PDSCH type 2, and the UL DAI field / information for PDSCH type 2 can be configured / indicated only in the UL DCI.

[0335] Alternatively, independent DAI signaling can be performed between the following two PDSCH types, and individual HARQ-ACK subcodebooks can be configured. The Y value below can be configured / defined as 2.

[0336] -PDSCH Type 1: PDSCH transmission based on M-DCI, where the Q value exceeds the Y value.

[0337] PDSCH Type 2: PDSCH transmission based on M-DCI with Q value of Y or less, PDSCH transmission based on M-DCI configured with G=1, and existing PDSCH transmission based on S-DCI.

[0338] In this case, the individual ULDAI fields / information for each of PDSCH types 1 and 2 can be configured / indicated in the UL DCI. If PDSCH type 1 as described above does not exist, DAI signaling can be performed only for PDSCH type 2, the HARQ-ACK codebook can be configured only for PDSCH type 2, and the UL DAI fields / information for PDSCH type 2 can be configured / indicated only in the UL DCI.

[0339] Example 4-3: DAI count per PDSCH (i.e., Alt2 in Example 4 above) + single HARQ-ACK CB (codebook) configuration

[0340] The terminal can configure / generate a CB for single PDSCH and multiple PDSCH scenarios.

[0341] -M-DCI: The existing DL DAI size (i.e., 2 bits per C / T-DAI) can be increased (for each C / T-DAI) by ceiling{log2(the maximum of the N_max values ​​configured for each CC (or BWP) in the same cell group)}. Here, N_max is the maximum number of PDSCHs that can be scheduled for a specific cell via M-DCI.

[0342] -S-DCI: The size of the existing DL DAI can be increased (for each C / T-DAI) by ceiling{log2(the maximum of the N_max values ​​configured for each CC (or BWP) in the same cell group)}. Here, N_max is the maximum number of PDSCHs that can be scheduled for a specific cell via M-DCI.

[0343] Here, we assume the DAI increment ceiling{log2(the maximum value of N_max among the configured CCs (or BWPs) in the same cell group)} is A. Once the DL DAI of the fallback DL DCI (i.e., DCI format 1_0) is maintained at 2 bits as before, we can consider increasing the interval between the indicated DAI values ​​to 2^A. This is because, considering the reliability of the fallback DL DCI, we do not want to increase the DCI size. For example, if the DAI increment is 2 bits, 2^A = 4, then the 2-bit DAI value indicated by the fallback DCI can be scaled to 2^A using {4, 8, 12, 16} (instead of {1, 2, 3, 4,}). For this purpose, if the previous C-DAI value was 5 and the C-DAI value indicated by the corresponding fallback DL DCI is 8, then the terminal can map the HARQ-ACK information corresponding to C-DAI = 6, 7 to NACK.

[0344] Alternatively, assume that the DAI increment ceiling{log2(the maximum of the N_max values ​​for each CC (or BWP) configured in the same cell group)} is A. Once the DL DAI of the back-off DL DCI (i.e., DCI format 1_0) remains 2 bits, the corresponding DAI counting step can also be incremented by 1 as before. Here, multi-PDSCH scheduling DCIs (or DCIs where the DL DAI size increases by A) and back-off DCIs (or DCIs where the DL DAI size remains the same as before) can be restricted so as not to indicate the same PUCCH slots. For example, multi-PDSCH scheduling DCIs (or DCIs where the DL DAI size increases by A) may be allowed to indicate only the same PUCCH slots (or DCIs where the DL DAI size increases by A) as the non-back-off DCI of the same / different cell. In other words, multi-PDSCH scheduling DCIs (or DCIs where the DL DAI size increases by A) may not be allowed to indicate the same PUCCH slots as the back-off DCI of the same / different cell (or DCIs where the DL DAI size remains the same as before). Here, only the back-off DCI (or the DCI where the DL DAI size remains the same as before) and the non-back-off DCI of the same / different cell (or the DCI where the DL DAI size is increased by A, or the DCI among the DCIs where the DL DAI size is increased by A, excluding the multi-PDSCH scheduling DCI) can indicate the same PUCCH slot. However, in this case, the DAI field of the non-back-off DCI (or the DCI where the DL DAI size is increased by A, or the DCI among the DCIs where the DL DAI size is increased by A, excluding the multi-PDSCH scheduling DCI) (although the size is the same as A) can be specified / configured to indicate only values ​​from 1 to 4 (e.g., in 2+A bits, only the most significant bit (MSB) or least significant bit (LSB) 2 bits are valid and the remaining bits are ignored).

[0345] Alternatively, assume that the DAI increment ceiling{log2(the maximum of the N_max values ​​configured for each CC (or BWP) in the same cell group)} is A. Once the DL DAI of the back-down DL DCI (i.e., DCI format 1_0) remains 2 bits, the corresponding DAI counting step can also be incremented by 1 as before. Here, individual PUCCHs can be restricted to PDSCH indications only for those scheduled using the back-down DCI (or the DCI where the DL DAI size remains the same as before). In other words, the terminal can expect that the PUCCH resources (especially time resources) indicated in the multi-PDSCH scheduled DCI (or the DCI where the DL DAI size increases by A) and the PUCCH resources (especially time resources) indicated by the back-down DCI (or the DCI where the DL DAI size remains the same as before) do not overlap. For example, it can be allowed that the multi-PDSCH scheduled DCI only indicates the same PUCCH slots as the non-back-down DCI of the same / different cells. In other words, it may not be allowed to allow backoff DCI to indicate the same PUCCH slot as multi-PDSCH scheduled DCI or non-backoff DCI.

[0346] - UL Permission: The existing UL DAI size (i.e., 2 bits for T-DAR) can be increased by ceiling{log2(the maximum of the N_max values ​​of each CC (or BWP) configured in the same cell group)}. Here, N_max is the maximum number of PDSCHs that a particular cell can schedule via M-DCI, and the corresponding increase should apply to all cells with or without M-DCI configured. That is, if M-DCI is configured even for at least one serving cell in the same cell group, the corresponding increase is applied to the UL permission of all serving cells in the same cell group.

[0347] - HARQ-ACK Payload: The number of HARQ-ACK bits per DAI can be X bits (e.g., based on whether 2TB is configured in the corresponding serving cell (i.e., whether the maximum number of PDSCH reception carrying two transport blocks or a DCI-schedulable transport block (or codeword) is configured), X can be 2 or 1). As another example, for a cell configured with 2TB but not with spatial binding for HARQ-ACK information, X = 2. For a cell configured with 2TB but with spatial binding, or for a cell configured with 1TB, X = 1.

[0348] Example 4-3a: DAI count per PDSCH (i.e., Alt 2 in Example 4 above) + single HARQ-ACK CB (codebook) configuration + when configuring CBG

[0349] The UE can configure / generate individual sub-CBs. (That is, one sub-CB can be configured for TB-based PDSCH scheduling in both single-PDSCH and multi-PDSCH scenarios, and another sub-CB can be configured for CBG-based PDSCH scheduling in the single-PDSCH scenario.)

[0350] -S-DCI: In the case of a cell with CBG configured but no M-DCI configured, the DL DAI size in option 1-1) of the non-backoff DCI format (i.e., DCI format 1_1 or 1_2) can be increased as in Example 4-3, or option 1-2) can remain at 2 bits as before. In the case of a cell where CBG is configured but no M-DCI configured, the DL DAI size in the backoff DCI format (i.e., DCI format 1_0) can be increased or remained at 2 bits as in Example 4-3. In the case of a cell with both M-DCI and CBG configured, the DL DAI size can be increased as in Example 4-3.

[0351] -M-DCI (Case 1): In the case of a cell where M-DCI is configured but CBG is not configured, the DL DAI size can be increased as in Examples 4-3. Here, in the case of a single PDSCH, the DAI in multiple TTIDCI (e.g., multiple PDSCH DCI) can indicate the C / T-DAI value used for TB-based PDSCH.

[0352] -M-DCI (Case 2): In the case of a cell configured with both M-DCI and CBG, when the DLDAI size in the DCI is increased to M_1 bits (>2) (as in Example 4-3), Option 2-1) M_1 bits can indicate the C / T-DAI value (especially in the case of Option 1-1), or Option 2-2) 2 bits can indicate the C / T-DAI value (especially in the case of Option 1-2). Typically, in the case of Option 2-2, the DL DAI field size itself can be reduced to 2 bits per C / T-DAI based on the TDRA field check (if in the case of a single PDSCH). (Conversely, in the case of a multi-PDSCH based on the TDRA field check, the DL DAI field size can be M_1 bits.) Here, in the case of a single PDSCH, the DAI in multiple TTIDCIs (e.g., multiple PDSCH DCIs) can indicate the C / T-DAI value used for CBG-based PDSCHs.

[0353] - UL Licensing: In addition to the DAI size for UL licensing as described in Examples #4-3, an additional 2 bits may be required for T-DAI (the sub-CB for CBG). That is, if CBG is configured even for at least one serving cell in the same cell group, the corresponding increase can be applied to UL licensing for all serving cells in the same cell group.

[0354] -HARQ-ACK payload: The payload of a sub-CB configured for TB-based PDSCH scheduling in both single-PDSCH and multi-PDSCH scenarios can be the same as in Examples 4-3. The payload of another sub-CB configured for CBG-based PDSCH scheduling in the single-PDSCH scenario can be the same as the payload of an existing CBG-based sub-CB configuration.

[0355] Example 4-3b: DAI count per PDSCH (i.e., Alt 2 in Example 4 above) + single HARQ-ACK CB (codebook) configuration + when configuration time binding

[0356] When time binding is configured for one or more serving cells (all or some) in the terminal as in Example 1, a type 2HCB configuration is proposed.

[0357] -M-DCI: It can be the same as in Examples 4-3, or it can be increased (for each C / T-DAI) by ceiling{log2(the maximum value of G_max among the C / T-DAI configured in the same cell group)}. In this case, G_max is the number of (maximum) time-bound groups configured in a particular cell.

[0358] -S-DCI: This can be the same as in Examples 4-3, or the existing DL DAI size can be increased (for each C / T-DAI by) ceiling{log2(the maximum value of G_max among the values ​​configured for each CC (or BWP) in the same cell group)}. Here, G_max is the (maximum) number of time-bound groups configured in a particular cell.

[0359] Here, we assume the DAI increment ceiling{log2(the maximum of the N_max or G_max values ​​configured for each CC (or BWP) in the same cell group)} is A. Once the DL DAI of the fallback DL DCI (i.e., DCI format 1_0) is maintained at 2 bits as before, it is advisable to consider increasing the interval between the indicated DAI values ​​to 2^A. This is because, considering the reliability of the fallback DL DCI, it is undesirable to increase the DCI size. For example, if the DAI increment is 1 bit, 2^A = 2, then the 2-bit DAI value indicated by the fallback DCI can be scaled to 2^A using {2,4,6,8} (instead of {1,2,3,4,}). For this purpose, if the previous C-DAI value was 2 and the C-DAI value indicated by the corresponding fallback DL DCI is 4, then the terminal can map the HARQ-ACK information corresponding to C-DAI = 3 to NACK.

[0360] – UL Licensing: This can be the same as in Examples 4-3, or it can be increased by ceiling{log2(the maximum value of G_max among each CC (or BWP) configured in the same cell group)} for the existing UL DAI size (i.e., 2 bits for T-DAI). Here, G_max is the number of (maximum) time-bound groups configured in a particular cell, and the corresponding increase should apply to all cells with or without M-DCI configured. That is, if M-DCI is configured even for at least one serving cell in the same cell group, the corresponding increase can be applied to UL licensing for all serving cells in the same cell group.

[0361] - HARQ-ACK Payload: If the DAI size used for M-DCI, S-DCI, and UL licensing follows Embodiments 4-3, the HARQ-ACK payload can be configured by binding the PDSCH corresponding to the G_max (or G allocated to each cell) DAI. Alternatively, if the DAI size used for M-DCI, S-DCI, and UL licensing is determined based on G_max, 1 bit of HARQ-ACK can be configured for each DAI.

[0362] Example 4-4: DAI count per PDSCH (i.e., Alt2 in Example 4 above) + individual HARQ-ACK sub-CB (codebook)

[0363] The terminal can configure / generate one sub-CB corresponding to the single PDSCH case and another sub-CB corresponding to the multiple PDSCH case.

[0364] -M-DCI: The existing DL DAI size (i.e., 2 bits per C / T-DAI) can be increased (by ceiling{log2(the maximum of the N_max values ​​configured for each CC (or BWP) in the same cell group)}. Here, N_max is the maximum number of PDSCHs that can be scheduled for a specific cell via M-DCI.

[0365] -S-DCI: Can maintain the existing DL DAI size. This should work for two cells with or without M-DCI configured.

[0366] - UL License: In addition to the existing UL DAI size, Z bits (Z is a natural number) may be required for the T-DAI (for the additional sub-CB). Here, Z = ceiling{log2(the maximum of the N_max values ​​for each CC (or BWP) configured in the same cell group)}. Here, N_max is the maximum number of PDSCHs that a particular cell can schedule via M-DCI, and the corresponding increase should apply to all cells with or without M-DCI configured. That is, if M-DCI is configured even for at least one serving cell in the same cell group, the corresponding increase can be applied to the UL license for all serving cells in the same cell group.

[0367] - HARQ-ACK Payload: The number of HARQ-ACK bits for each sub-CB DAI corresponding to the single PDSCH case can be X (e.g., based on whether 2TB is configured in the corresponding serving cell (i.e., whether the maximum number of PDSCH reception carrying two transport blocks or a DCI-schedulable transport block (or codeword) is configured), X can be 2 or 1). As another example, for a cell configured with 2TB and without spatial binding for HARQ-ACK information, X = 2. For a cell configured with 2TB but with spatial binding, or for a cell configured with 1TB, X = 1. The number of HARQ-ACK bits for each sub-CB DAI corresponding to the multi-PDSCH case can also be X (e.g., based on whether 2TB is configured in the corresponding serving cell (i.e., whether the maximum number of PDSCH reception carrying two transport blocks or a DCI-schedulable transport block (or codeword) is configured), X can be 2 or 1). As another example, for a cell configured with 2TB and without spatial binding for HARQ-ACK information, X = 2. For cells with a 2TB configuration but bound to the configuration space, or cells with a 1TB configuration, X = 1.

[0368] Example 4-4a: DAI count per PDSCH (i.e., Alt 2 in Example 4 above) + individual HARQ-ACK sub-CB (codebook) + when CBG is configured

[0369] The terminal can configure / generate individual sub-CBs. (That is, the first sub-CB can be configured for TB-based PDSCH scheduling in the single PDSCH case, the second sub-CB can be configured for multi-PDSCH cases, and the third sub-CB can be configured for CBG-based PDSCH scheduling in the single PDSCH case.)

[0370] -S-DCI: In the case of a cell where CBG is configured but M-DCI is not configured, the DL DAI size in the non-backoff DCI format (i.e., DCI format 1_1 or 1_2) can be maintained as 2 bits as before. In the case of a cell where CBG is configured but M-DCI is not configured, the DL DAI size in the backoff DCI format (i.e., DCI format 1_0) can be maintained as 2 bits. In the case of a cell where both M-DCI and CBG are configured, the DL DAI size can be maintained as in Examples 4-4.

[0371] -M-DCI (Case 1): In the case of a cell where M-DCI is configured but CBG is not configured, the DL DAI size can be increased as in Examples 4-4. Here, in the case of a single PDSCH, the DAI in multiple TTIDCI (e.g., multiple PDSCH DCI) can indicate the C / T-DAI value used for TB-based PDSCH.

[0372] -M-DCI (Case 2): In the case of a cell configured with both M-DCI and CBG, when the DLDAI size in the DCI is increased to M_2 bits (>2) (as in Examples 4-4), 2 bits can indicate the C / T-DAI value. Typically, based on the TDRA field check (in the case of a single PDSCH), the DL DAI field size itself can be reduced to 2 bits in each C / T-DAI. (Conversely, in the case of multiple PDSCH based on the TDRA field check, the DL DAI field size can be M_2 bits.) Here, in the case of a single PDSCH, the DAI in multiple TTIDCIs (e.g., multiple PDSCH DCIs) can indicate the C / T-DAI value used for CBG-based PDSCH.

[0373] - UL Licensing: In addition to the UL DAI size of Implementation #4-4, 4 bits may be required for the T-DAI (for the additional 2 sub-CBs) (i.e., 2 bits of the T-DAI for each sub-CB).

[0374] -HARQ-ACK Payload: In the case of TB-based PDSCH scheduling in the single PDSCH scenario, the payload of the first sub-CB can be the same as the sub-CB corresponding to the single PDSCH scenario in Example 4-4. The payload of the second sub-CB configured for the multi-PDSCH scenario can be the same as the sub-CB corresponding to the multi-PDSCH scenario in Example 4-4. The payload of the third sub-CB configured for CBG-based PDSCH scheduling in the single PDSCH scenario can be the same as the payload of the existing CBG-based sub-CB configuration.

[0375] Example 4-4b: DAI count per PDSCH (i.e., Alt 2 in Example 4 above) + individual HARQ-ACK sub-CB (codebook) + when configured for time binding

[0376] When time binding is configured for one or more serving cells (all or some) in the terminal as in Example 1, a type 2HCB configuration is proposed.

[0377] -M-DCI: It can be the same as in Examples 4-4, or it can be increased (for each C / T-DAI) by ceiling{log2(the maximum value of G_max among the values ​​of each CC (or BWP) configured in the same cell group)}. Here, G_max is the number of (maximum) time-bound groups configured in a particular cell.

[0378] -S-DCI or UL license: It can be the same as in Examples 4-4 above.

[0379] - HARQ-ACK payload for sub-CBs corresponding to the multi-PDSCH case: If the DAI size for M-DCI follows Example 4-4, the HARQ-ACK payload can be configured by binding the PDSCH corresponding to the G_max (or the G allocated to each cell) DAI. Alternatively, if the DAI size for M-DCI is determined based on G_max, one HARQ-ACK bit can be configured for each DAI.

[0380] - HARQ-ACK payload for sub-CBs corresponding to the single PDSCH case: The number of HARQ-ACK bits for each sub-CB DAI corresponding to the single PDSCH case can be X (e.g., based on whether 2TB is configured in the corresponding serving cell (i.e., whether PDSCH reception carrying two transport blocks or the maximum number of transport blocks (or codewords) schedulable by one DCI is configured), the value of X can be 2 or 1). As another example, for a cell where 2TB is configured and spatial bundling for HARQ-ACK information is not configured, X = 2. For a cell where 2TB is configured but spatial bundling is configured or a cell where 1TB is configured, X = 1.

[0381] Example 4-5: DAI counting for every W (W is a natural number) PDSCHs (i.e., Alt 3 of Example 4)

[0382] When the value of W is equal to N_max_all (here, N_max_all represents the maximum value of the N_max values for each CC (or BWP) configured in the same cell group, and N_max represents the maximum number of PDSCHs schedulable by the M-DCI of a specific cell), since it has the same meaning as counting DAI for each DCI (i.e., Alt 1 of Example 4), Example 4-1, Example 4-1a, Example 4-2, and Example 4-2a can be applied.

[0383] On the other hand, when the value of W is less than N_max_all, Example 4-3, Example 4-3a, Example 4-4, and Example 4-4a can be applied. However, here, the equation for calculating the DAI increment can be changed to ceiling{log2(maximum value of N_max / W values for each CC (or BWP) configured in the same cell group)}. Additionally, in the HARQ-ACK payload, the number of HARQ-ACK bits for each DAI can be replaced by X*W bits instead of X bits. (When X = 1) When the number of PDSCHs corresponding to a specific DAI is less than W, e.g., K (K < W), the last W - K bits of the HARQ-ACK M bits corresponding to this DAI can be mapped to NACK.

[0384] Example 5: DAI signaling method when indicating multiple PUCCHs corresponding to multiple PDSCHs scheduled by one DCI

[0385] Because DAI counting should be performed separately for each PDSCH corresponding to a different PUCCH, there is a drawback that an equal number of individual DAI fields are needed as many as the number of PUCCHs. For example, when a DCI schedules N PDSCHs, the PUCCHs corresponding to N1 PDSCHs can be designated as slot n1, and the PUCCHs corresponding to the remaining N2 PDSCHs can be designated as slot n2 (i.e., N = N1 + N2, where the value of N1 can be predefined or configured by higher-layer signaling, or it can be determined as N1 = ceiling{N / 2}, N2 = floor{N / 2}, or it can be determined as N1 = floor{N / 2}, N2 = ceiling{N / 2}). Here, C-DAI / T-DAI may be needed for N1 PDSCHs and C-DAI / T-DAI may be needed for N2 PDSCHs. To mitigate this DCI overhead issue, in the case of multiple PDSCHs, rules can be configured (defined) to configure only the same number of individual C-DAI fields as the number of PUCCHs (without T-DAI). That is, only the C-DAI1 field for N1 PDSCHs and the C-DAI2 field for N2 PDSCHs are signaled in the DL DCI, and the T-DAI fields for N1 and N2 PDSCHs can be omitted in the DL DCI signaling. If the terminal misses the last DCI (with T-DAI information) (e.g., decoding failure), a HARQ-ACK payload mismatch may occur between the base station and the terminal because there is no T-DAI in the corresponding multiple PDSCH case. However, this problem can be solved by having the base station separately schedule DCIs that include reliable T-DAI. Alternatively, this problem can be solved by indicating different PUCCHs and having the base station perform blind detection on multiple PUCCHs. Typically, in the case of M-DCI, in case 1) when more than N PDSCHs are scheduled (e.g., this can be predefined as a value such as N=1, or the value of N can be configured by higher-layer signaling), multiple PUCCHs can be indicated; or in case 2) when N or fewer PDSCHs are scheduled, only one PUCCH can be indicated. In case 2, the C-DAI and T-DAI fields are configured in the DCI, and C-DAI and T-DAI information can be indicated. On the other hand, in case 1, the C-DAI1 field / information for N1 PDSCHs and the C-DAI2 field / information for N2 PDSCHs can be configured / indicated respectively. Here, the bits interpreted as C-DAI and T-DAI fields in case 2 can be interpreted as C-DAI1 for N1 PDSCHs and C-DAI2 for N2 PDSCHs in case 1 (or vice versa).

[0386] Alternatively, the N / N1 / N2 values ​​can be DL slot units instead of PDSCH units. For example, when N' PDSCHs spanning N slots are scheduled by a DCI, the PUCCH corresponding to the N1' PDSCHs spanning N1 slots can be indicated as slot n1, and the PUCCH corresponding to the PDSCHs spanning the remaining N2 slots can be indicated as slot n2 (i.e., N = N1 + N2, where the value of N1 can be predefined or configured by higher-layer signaling, or it can be determined as N1 = ceiling{N / 2}, N2 = floor{N / 2}, or it can be determined as N1 = floor{N / 2}, N2 = ceiling{N / 2}). Here, C-DAI / T-DAI may be needed for the PDSCHs spanning N1 slots and C-DAI / T-DAI may be needed for the PDSCHs spanning N2 slots. To mitigate this DCI overhead issue, in the case of multiple PDSCHs, rules can be configured (defined) to configure only the same number of individual C-DAI fields as the number of PUCCHs (without T-DAI). That is, in DL DCI, only the C-DAI1 field for PDSCHs spanning N1 time slots and the C-DAI2 field for PDSCHs spanning N2 time slots are signaled, and the T-DAI fields for PDSCHs spanning N1 and N2 time slots can be omitted in the DL DCI signaling. If the terminal misses the last DCI (with T-DAI information) (e.g., decoding failure), a HARQ-ACK payload mismatch will occur between the base station and the terminal due to the absence of T-DAI in the case of multiple PDSCHs. However, this problem can be solved by having the base station separately schedule DCIs that include reliable T-DAI. Alternatively, this problem can be solved by having different PUCCHs indicated and the base station performing blind detection on multiple PUCCHs. Typically, in the case of M-DCI, in case 1) when scheduling PDSCHs spanning more than N time slots (e.g., it can be predefined as a value such as N=1, or the value of N can be configured by higher-layer signaling), multiple PUCCHs can be indicated, or in case 2) when scheduling PDSCHs spanning N or fewer time slots, only one PUCCH can be indicated. In this case, in case 2, the C-DAI and T-DAI fields are configured in the DCI, and C-DAI and T-DAI information can be indicated. On the other hand, in case 1, the C-DAI1 field / information for PDSCHs spanning N1 time slots and the C-DAI2 field / information for PDSCHs spanning N2 time slots can be configured / indicated respectively.Here, the bits that are interpreted as C-DAI and T-DAI fields in Case 2 can be interpreted as C-DAI1 for PDSCH spanning N1 time slots and C-DAI2 for PDSCH spanning N2 time slots (or vice versa) in Case 1.

[0387] Example 6: When configuring the DAI count (i.e., Alt 1 in Example 4) + individual sub-CB for each DCI as in Example 4-2, a method for configuring individual sub-CB is proposed.

[0388] A sub-CB that can include HARQ-ACK information corresponding to a single PDSCH case can be defined as sub-CB#1, and a sub-CB that can include all or part of HARQ-ACK information corresponding to multiple PDSCH cases can be defined as sub-CB#2. When the number of bits of HARQ-ACK corresponding to a DAI is defined as K, the K value corresponding to sub-CB#2 can generally be greater than the K value corresponding to sub-CB#1. In the following text, S-DCI configured cell may refer to a cell that is not configured with M-DCI.

[0389] Scenario 1) When there is no spatial binding configuration and 2-TB is configured in the S-DCI configured cell (and / or M-DCI configured cell)

[0390] Since at least 2-TB of PDSCH is configured in the S-DCI-configured cell and no spatial binding is configured, the number of HARQ-ACK bits for each DAI in sub-CB#1 can be determined to be 2 bits. Here, when only one or two 1-TB PDSCHs or a single 2-TB PDSCH are scheduled via M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#2. When, as described above, the HARQ-ACK information corresponding to the PDSCH scheduled via M-DCI is included in sub-CB#1 and only 1-TB PDSCHs are scheduled via M-DCI, the first bit of the 2 bits of HARQ-ACK corresponding to the corresponding DAI carries the ACK or NACK information of the scheduled PDSCH, and the second bit can always be filled with NACK, or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) can be repeated in the second bit. Additionally, when only two 2-TB PDSCHs are scheduled via M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be converted to 2 bits through spatial binding and included in subCB#1.

[0391] Meanwhile, when time binding is configured in M-DCI as in Example 4-2b, if the number of HARQ-ACK bits for time binding of the PDSCH used for scheduling is 1 or 2, the corresponding HARQ-ACK bits can be included in subCB#1; otherwise, they can be included in subCB#2.

[0392] Scenario 2) When there is no space binding configuration and 2-TB is configured only in the M-DCI configuration cell

[0393] Since no 2-TB PDSCH is configured in all S-DCI configuration cells, the number of HARQ-ACK bits per DAI for sub-CB#1 can be determined to be 1 bit. Here, only when a single 1-TB PDSCH is scheduled via M-DCI can the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#2. Additionally, when only one 2-TB PDSCH is scheduled via M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled via M-DCI can be converted to 1 bit through spatial binding and included in sub-CB#1.

[0394] Meanwhile, when time binding is configured in M-DCI as in Example 4-2b, if the number of HARQ-ACK bits for time binding of the PDSCH used for scheduling is 1, the corresponding HARQ-ACK bit can be included in subCB#1; otherwise, it can be included in subCB#2.

[0395] As another approach, a method similar to that in Case 1 can be applied in this case. For example, the number of HARQ-ACK bits for each DAI in sub-CB#1 can be determined to be 2 bits. Here, when only one or two 1-TB PDSCHs or a single 2-TB PDSCH are scheduled via M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#2. When the HARQ-ACK information corresponding to the PDSCH scheduled via M-DCI is included in sub-CB#1 as described above and only 1-TB PDSCHs are scheduled via M-DCI, the first bit of the 2 bits of HARQ-ACK corresponding to the corresponding DAI carries the ACK or NACK information of the scheduled PDSCH, and the second bit can always be filled with NACK, or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) can be repeated in the second bit. Similarly, in the case of a 1-TB PDSCH scheduled via S-DCI, the first bit of the 2-bit HARQ-ACK corresponding to the corresponding DAI carries the ACK or NACK information of the scheduled PDSCH, and the second bit can always be filled with NACK, or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) can be repeated in the second bit. Additionally, when only two 2-TB PDSCHs are scheduled via M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be converted to 2 bits through spatial binding and included in subCB#1.

[0396] Meanwhile, when time binding is configured in M-DCI as in Example 4-2b, if the number of HARQ-ACK bits for time binding of the PDSCH used for scheduling is 1 or 2, the corresponding HARQ-ACK bits can be included in subCB#1; otherwise, they can be included in subCB#2.

[0397] Scenario 3) When spatial binding configuration exists, or when 2-TB is not configured in all cells (within a PUCCH cell group)

[0398] Since 2-TB is not configured in all S-DCI-configured cells, the number of HARQ-ACK bits for each DAI used in sub-CB#1 can be determined to be 1 bit. Here, only when M-DCI schedules a single PDSCH (2-TB or 1-TB), the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#2. Alternatively, when two 1-TB PDSCHs are scheduled via M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be converted to 1 bit through time binding and included in sub-CB#1. Alternatively, when two 1-TB PDSCHs are scheduled via M-DCI, 2 bits of HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#1.

[0399] Meanwhile, when time binding is configured in M-DCI as in Example 4-2b, if the number of HARQ-ACK bits for time binding of the PDSCH used for scheduling is 1, the corresponding HARQ-ACK bit can be included in subCB#1; otherwise, it can be included in subCB#2.

[0400] As an alternative to Case 3, the number of HARQ-ACK bits for each DAI in sub-CB#1 can be determined to be 2 bits. Here, similar to Case 1, when only one or two 1-TB PDSCHs are scheduled via M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled via the corresponding M-DCI can be included in sub-CB#2. Furthermore, in the case of 1-TB PDSCHs scheduled via S-DCI, the first bit of the 2 HARQ-ACK bits corresponding to the corresponding DAI carries the ACK or NACK information of the scheduled PDSCH, and the second bit can always be filled with NACK, or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) can be repeated in the second bit.

[0401] Meanwhile, when time binding is configured in M-DCI as in Example 4-2b, if the number of HARQ-ACK bits for time binding of the PDSCH used for scheduling is 1 or 2, the corresponding HARQ-ACK bits can be included in subCB#1; otherwise, they can be included in subCB#2.

[0402] Example 7: When the transmission / reception of some PDSCHs scheduled by M-DCI can be omitted, a method for DAI counting and HARQ-ACK CB (codebook) configuration is proposed.

[0403] In this embodiment, the omission of some PDSCH transmission / reception may mean at least some or all of the following.

[0404] - PDSCH that overlaps with symbols (or time slots including the corresponding symbols) configured for uplink (or flexible) via higher-level signaling for public TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon) and higher-level signaling for dedicated TDD configuration (e.g., tdd-UL-DL-ConfigurationDedicated).

[0405] - PDSCH included in (or overlapping) resources, which are configured / indicated by higher-level signaling (e.g., RateMatchPattern) used to configure rate matching patterns.

[0406] Here, as in Examples 4-3 (or Examples 4-3a / b) and 4-4 (or Examples 4-4a / b), a method for counting DAI is proposed as the DAI value increases for each PDSCH.

[0407] 1) Option 1: When the transmission / reception of some PDSCHs among multiple PDSCHs scheduled by the M-DCI can be omitted, consecutive values ​​starting from the (C-)DAI value indicated by the DCI can be assigned to PDSCHs that are actually transmitted / received only in chronological order (not based on scheduling). For example, in the case where the terminal receives an M-DCI in which four PDSCHs are scheduled, some (or all) OFDM symbols of the third PDSCH can be configured as uplink (or flexibly) via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. Additionally, when the C-DAI value indicated by the corresponding M-DCI corresponds to 3, the terminal can identify that the C-DAIs used for scheduling the 1st / 2nd / 4th PDSCHs are 3 / 4 / 5 respectively (skipping the mapping of C-DAI values ​​to the third PDSCH).

[0408] 2) Option 2: When the transmission / reception of some PDSCHs among multiple PDSCHs scheduled by the M-DCI can be omitted, in this case, for the DAI value, consecutive values ​​starting from the (C-)DAI value indicated by the DCI can be assigned chronologically to all PDSCHs scheduled by the DCI, regardless of the actual transmission / reception. For example, in the case where the terminal receives an M-DCI in which four PDSCHs are scheduled, some (or all) OFDM symbols of the third PDSCH can be configured as uplink (or flexibly) via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. Additionally, when the C-DAI value indicated by the corresponding M-DCI corresponds to 3, the terminal can identify the C-DAIs used for scheduling 1 / 2 / 3 / 4 as 3 / 4 / 5 / 6, respectively.

[0409] In Option 2, the HARQ-ACK information corresponding to the (C-)DAI value that corresponds to the omitted PDSCH for transmission / reception can be mapped to NACK. Furthermore, even when the DAI value increases for each DCI, as in Embodiments 4-1 (or 4-1a / b) and 4-2 (or 4-2a / b) described above, the HARQ-ACK information corresponding to the omitted PDSCH for transmission / reception can be mapped to NACK.

[0410] Example 8: When the transmission / reception of some PUSCHs scheduled by M-DCI can be omitted, a method for aperiodic CSI reporting and frequency hopping is proposed.

[0411] In this embodiment, the omission of some PUSCH send / receive may mean at least some or all of the following.

[0412] - PUSCH that overlaps with symbols (or time slots including corresponding symbols) configured for downlink (or flexible) via higher-level signaling for public TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon) and higher-level signaling for dedicated TDD configuration (e.g., tdd-UL-DL-ConfigurationDedicated).

[0413] - Includes PUSCH in resources configured / indicated by higher-level signaling (e.g., invalidSymbolPattern) for configuring invalid symbol patterns.

[0414] In this context, a non-periodic CSI reporting and frequency hopping methods were proposed.

[0415] Meanwhile, the following regulations can be followed when submitting non-periodic CSI reports through M-DCI.

[0416] When DCI format 0_1 ​​schedules two PUSCH allocations, aperiodic CSI reports are carried on the second scheduled PUSCH. When DCI format 0_1 ​​schedules more than two PUSCH allocations, aperiodic CSI reports are carried on the penultimate scheduled PUSCH.

[0417] However, when the transmission / reception of some PUSCHs among multiple PUSCHs scheduled by M-DCI can be omitted, the PUSCH to which aperiodic CSI reports are sent can be determined solely by targeting the actually transmitted / received PUSCHs (not based on scheduling). That is, when the actual number of transmitted / received PUSCHs is 2, CSI can be reported via the second PUSCH (out of the two actually transmitted / received PUSCHs), and when the actual number of transmitted / received PUSCHs is 3 or more, CSI can be reported via the penultimate PUSCH (out of the multiple actually transmitted / received PUSCHs). Specifically, it can be as follows.

[0418] For example, in the case where a terminal receives an M-DCI that schedules four PUSCHs, some (or all) of the OFDM symbols of the third PUSCH can be configured as downlink (or flexibly) via tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. Here, when an aperiodic CSI report is triggered in the corresponding M-DCI, the aperiodic CSI can be reported on the second-scheduled PUSCH, which is the penultimate scheduled PUSCH based on the actually transmitted PUSCH.

[0419] Meanwhile, when DCI format 0_1 ​​schedules allocate no fewer than two PUSCHs but only sends two PUSCHs, an aperiodic CSI report is carried on the second sent PUSCH. When DCI format 0_1 ​​schedules allocate more than two PUSCHs and sends more than two PUSCHs, an aperiodic CSI report is carried on the penultimate sent PUSCH.

[0420] Meanwhile, in the case of frequency hopping (for multiple PUSCHs scheduled via M-DCI), when applying inter-slot hopping, n in Equation 3 below... μ s The value can be increased based on the actual PUSCH sent (not based on the pre-defined PUSCH). That is, for a scheduled but not actually sent PUSCH, the corresponding parameter n... μ sThe value does not need to be increased.

[0421] In the case of frequency hopping between time slots, time slot n μ s The initial RB during the period is given by Equation 3 below.

[0422] [Equation 3]

[0423]

[0424] In equation 3, n μ s This is the current timeslot number within the radio frame. Multi-slot PUSCH transmission is possible here, RB start It is the starting RB in UL BWP, calculated based on the resource block assignment information of resource allocation type 1, and the RB offset It is the frequency offset in the RB between the two frequency hopping frequencies.

[0425] Figure 12 This is a diagram illustrating the signaling process between a base station and a terminal in a method for sending and receiving control information according to an embodiment of the present disclosure.

[0426] Figure 12 The signaling process between a user equipment (UE) and a base station (BS) is illustrated based on previously proposed methods (e.g., any one of Embodiments 1 to 8 and its detailed embodiments or a combination of one or more (detailed) embodiments). Figure 12 This is for ease of description only and is not intended to limit the scope of this disclosure. Additionally, omissions may be made depending on the situation and / or configuration, etc. Figure 12 Some of the steps are shown below. Additionally... Figure 12 The base station and terminal in the example are just one example and can be implemented as follows: Figure 15 The apparatus shown. For example, Figure 15 The processor (102 / 202) can control the use of transceivers (106 / 206) to send / receive channels / signals / data / information, etc., and control the storage of channels / signals / data / information to be sent or received in memory (104 / 204).

[0427] In addition, Figure 12 Even without a separate description, the above content can be referenced / used in the operation between the base station and the terminal.

[0428] A base station can be a general term referring to an object that transmits and receives data relative to a terminal. For example, a base station may include one or more TPs (Transmission Points), one or more TRPs (Transmission and Receive Points), etc. Furthermore, TPs and / or TRPs may include panels of base stations, transmitting and receiving units, etc. Additionally, "TRP" can be used interchangeably with panels, antenna arrays, cells (e.g., macro cells / small cells / pecimen cells, etc.), TPs (Transmission Points), base stations (base stations, gNBs, etc.). As mentioned above, TRPs can be classified based on information about CORESET groups (or CORESET pools) (e.g., indexes, identifiers (IDs)). As an example, when a terminal is configured to perform transmission / reception relative to multiple TRPs (or cells), this can mean configuring multiple CORESET groups (or CORESET pools) for a single terminal. Such CORESET group (or CORESET pool) configuration can be performed via higher-level signaling (e.g., RRC signaling, etc.).

[0429] refer to Figure 12 For ease of description, this section considers signaling between a base station and a terminal; however, this signaling method can be extended and applied to signaling between multiple TRPs and multiple terminals. In the following description, a base station can be interpreted as a TRP. Alternatively, a base station may include multiple TRPs, or it may be a cell comprising multiple TRPs.

[0430] refer to Figure 12 The terminal receives first configuration information related to M-DCI and / or second configuration information related to HARQ-ACK from the base station (S1201).

[0431] Here, the first and second configuration information can be sent via higher-level signaling (e.g., RRC signaling, MAC CE, etc.).

[0432] The first configuration information may refer to configuration information used to configure whether multiple PDSCHs can be scheduled by a single DCI (e.g., PDSCH-TimeDomainResourceAllocationListForMultiPDSCH). For example, if information is provided for the corresponding serving cell to configure scheduling for transmitting multiple PDSCHs (or PUSCHs) through a single DCI, then scheduling for transmitting multiple PDSCHs (or PUSCHs) through a single DCI can be configured / supported on the corresponding cell (this is called multi-PDSCH scheduling). On the other hand, if no information is provided for the corresponding serving cell to configure scheduling for transmitting multiple PDSCHs (or PUSCHs) through a single DCI, then multi-PDSCH scheduling may not be configured / supported on the corresponding cell.

[0433] The second configuration information may include information for configuring the type of HARQ-ACK codebook (e.g., the RRC parameter pdsch-HARQ-ACK-Codebook indicating whether it is a type 1 (i.e., semi-static) HARQ-ACK codebook or a type 2 (i.e., dynamic) HARQ-ACK codebook), information for configuring HARQ-ACK binding (i.e., time binding), and information about the number of HARQ-ACK binding groups (e.g., numberOfHARQBundlingGroups). Here, for example, if information for configuring the number of HARQ binding groups for a specific serving cell is provided, it can be assumed that time binding is configured for that specific serving cell. Conversely, if no information for configuring the number of HARQ binding groups for a specific serving cell is provided, it can be assumed that time binding is configured for that specific serving cell.

[0434] In other words, multi-PDSCH scheduling can be configured for one or more serving cells among multiple serving cells configured for a terminal. In serving cells where multi-PDSCH scheduling is not configured, a single PDSCH can be scheduled via a single DCI, as in existing technologies. Additionally, HARQ-ACK bindings (i.e., time bindings) can be configured for one or more serving cells among those configured with multi-PDSCH scheduling. For example, as described above, HARQ-ACK bindings can be configured in the corresponding cells by configuring the number of HARQ-ACK binding groups. Thus, for multiple PDSCHs scheduled on serving cells with configured HARQ-ACK bindings, HARQ-ACK information can be generated for each group or group. Here, HARQ-HARQ information for each group can be generated by performing a logical AND operation on the HARQ-ACK information of the multiple PDSCHs included in each of the one or more groups.

[0435] Here, when the number of HARQ-ACK binding groups is set to 1, a single HARQ-ACK message can be generated; and when the number of HARQ-ACK binding groups is set to more than 1, the number of HARQ-ACK messages for that group can be generated. On the other hand, for cells that do not have HARQ-ACK binding (i.e., time binding) configured in one or more serving cells with multi-PDSCH scheduling, HARQ-ACK messages can be generated for each of the multiple PDSCHs scheduled in the corresponding cell.

[0436] Here, based on the above embodiment 1, time binding can be configured for one or more of the multiple cells configured for the terminal.

[0437] The terminal receives M-DCI and / or S-DCI from the base station for scheduling one or more PDSCHs, and receives one or more scheduled PDSCHs (S1202).

[0438] Here, the terminal can receive DCI via PDCCH.

[0439] As described above, one or more PDSCHs can be scheduled via M-DCI on cells configured with M-DCI among multiple serving cells configured for the terminal. On the other hand, a single PDSCH can be scheduled via S-DCI on cells not configured with M-DCI among multiple serving cells configured for the terminal.

[0440] In other words, the terminal can receive DCIs (e.g., each DCI format for each serving cell) used to schedule one or more PDSCHs in each of the multiple configured serving cells. Additionally, the terminal can receive one or more PDSCHs in each of the multiple configured serving cells (i.e., receive multiple PDSCHs in multiple configured serving cells).

[0441] Here, in DAI signaling, DAI signaling can be executed based on any one or a combination of one or more specific embodiments of embodiment 4 above, or based on embodiment 5 above, or based on embodiment 7 above.

[0442] The terminal constructs / generates a HARQ-ACK codebook based on the configuration information and the decoding result of the scheduled PDSCH (i.e., ACK or NACK) (S1203).

[0443] Here, when configuring time binding, the terminal can configure / generate a type 1 HARQ-ACK codebook based on embodiment 2 above. Alternatively, when configuring PDCCH monitoring based on time slot groups, the terminal can configure / generate a type 1 HARQ-ACK codebook based on embodiment 3 above. Alternatively, the terminal can configure / generate a type 2 HARQ-ACK codebook based on any one or more specific embodiments of embodiment 4 above, or based on embodiment 6 above. Alternatively, when omitting the transmission / reception of some PDSCHs scheduled by M-DCI, the HARQ-ACK codebook can be configured / generated based on embodiment 7 above.

[0444] Furthermore, based on Embodiment 1 above, when only PDSCHs overlapping with uplink symbols in the HARQ binding of a specific group are included, the HARQ-ACK information for that specific group can be generated as NACK (negative ACK). Alternatively, when one or more PDSCHs overlapping with uplink symbols in the HARQ binding of a specific group are included, the HARQ-ACK information for that specific group can be generated by considering the HARQ-ACK information for the one or more PDSCHs overlapping with uplink symbols as ACK or NACK (negative ACK).

[0445] The terminal sends HARQ-ACK information to the base station at the time indicated by DCI, which is used to schedule PDSCH (S1204) based on the HARQ-ACK codebook type configured by the configuration information.

[0446] The terminal sends control information, including the generated HARQ-ACK codebook, to the base station via PUCCH or PUSCH. In addition to the HARQ-ACK codebook, the control information may also include scheduling requests, channel state information, uplink data (in the case of PUSCH), etc.

[0447] Figure 13 This is a diagram illustrating the operation of a terminal for sending and receiving control information according to an embodiment of the present disclosure.

[0448] Figure 13 The operation of a terminal based on the methods described above (e.g., any one of Embodiments 1 to 8 and their detailed embodiments or combinations of one or more (detailed) embodiments) is illustrated. Figure 13 This is for ease of description only and is not intended to limit the scope of this disclosure. Omissions may be made depending on the circumstances and / or configuration, etc. Figure 13 Some of the steps are shown below. Additionally... Figure 13 The terminal in the example is just one example and can be implemented as Figure 15 The device shown. For example. Figure 15 The processor (102 / 202) can control the transmission and reception of channels / signals / data / information (e.g., RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, PHICH, etc.) by using transceivers (106 / 206), and control the storage of transmitted or received channels / signals / data / information in memory (104 / 204).

[0449] The terminal receives from the base station configuration information (hereinafter referred to as first configuration information) for configuring HARQ-ACK bindings for one or more of the multiple serving cells configured for the terminal (S1301).

[0450] Here, the first configuration information may also include information for configuring the type of HARQ-ACK codebook (e.g., the RRC parameter pdsch-HARQ-ACK-Codebook indicating type 1 (i.e., semi-static) HARQ-ACK codebook or type 2 (i.e., dynamic) HARQ-ACK codebook) and / or information about the number of HARQ-ACK binding groups (e.g., numberOfHARQBundlingGroups).

[0451] Furthermore, as mentioned above, the first configuration information can correspond to information about the number of HARQ-ACK binding groups. That is, if information about the number of HARQ binding groups for configuring a specific serving cell is provided, it can be assumed that time binding is configured for that specific serving cell. For example, if information about the number of HARQ binding groups for configuring a specific serving cell is provided, it can be assumed that time binding is configured for that specific serving cell. On the other hand, if information about the number of HARQ binding groups for configuring a specific serving cell is not provided, it can be assumed that time binding is not configured for that specific serving cell.

[0452] Additionally, together with the first configuration information (i.e., via a message or information element (IE)) or separately from the first configuration information (i.e., via a different message or IE), the terminal can receive from the base station second configuration information (e.g., PDSCH-TimeDomainResourceAllocationListForMultiPDSCH) for configuring scheduling of multiple PDSCHs (referred to as multiPDSCH scheduling) via a single DCI for one or more of the multiple serving cells configured for the terminal. For example, if information for configuring scheduling for transmitting multiple PDSCHs (or PUSCHs) via a single DCI is provided for the corresponding serving cell, scheduling for transmitting multiple PDSCHs (or PUSCHs) via a single DCI on the corresponding cell can be configured / supported (this is referred to as multiPDSCH scheduling). On the other hand, if no information for configuring scheduling for transmitting multiple PDSCHs (or PUSCHs) via a single DCI is provided for the corresponding serving cell, multiPDSCH scheduling can not be configured / supported on the corresponding cell.

[0453] Multiple PDSCH scheduling can be configured for one or more serving cells among multiple serving cells configured for a terminal. In serving cells where multiple PDSCH scheduling is not configured, a PDSCH can be scheduled using a single DCI as in the prior art. Additionally, HARQ-ACK binding (i.e., time binding) can be configured for one or more serving cells among those configured with multiple PDSCH scheduling. For example, as described above, HARQ-ACK binding can be configured in the corresponding cell by configuring the number of HARQ-ACK binding groups. Thus, for multiple PDSCHs scheduled on serving cells with configured HARQ-ACK binding, HARQ-ACK information can be generated for each group. Here, HARQ-HARQ information for each group can be generated by performing a logical AND operation on the HARQ-ACK information of multiple PDSCHs included in each of the one or more groups.

[0454] Here, when the number of HARQ-ACK binding groups is set to 1, a single HARQ-ACK message can be generated; and when the number of HARQ-ACK binding groups is set to greater than 1, a number of HARQ-ACK messages for all groups can be generated. On the other hand, for cells that do not have HARQ-ACK binding (i.e., time binding) configured in one or more serving cells with multi-PDSCH scheduling, HARQ-ACK messages can be generated for each of the multiple PDSCHs scheduled in the corresponding cell.

[0455] Here, the first and second configuration information can be sent via higher-level signaling (e.g., RRC signaling, MAC CE, etc.).

[0456] Here, based on the above embodiment 1, time binding can be configured for one or more of the multiple cells configured for the terminal.

[0457] The terminal receives from the base station a DCI for scheduling one or more PDSCHs in each of a plurality of serving cells configured for the terminal (S1302), and the terminal receives from the base station a plurality of PDSCHs on the plurality of serving cells configured for the terminal (S1303).

[0458] Here, DCI can be sent via PDCCH.

[0459] As described above, one or more PDSCHs can be scheduled via M-DCI on cells configured with M-DCI among multiple serving cells configured for the terminal. On the other hand, a single PDSCH can be scheduled via S-DCI on cells not configured with M-DCI among multiple serving cells configured for the terminal.

[0460] In other words, the terminal can receive DCIs (e.g., each DCI format for each serving cell) used to schedule one or more PDSCHs in each of the multiple configured serving cells. Additionally, the terminal can receive one or more PDSCHs in each of the multiple configured serving cells (i.e., receive multiple PDSCHs in multiple configured serving cells).

[0461] Here, in DAI signaling, DAI signaling can be executed based on any one or a combination of one or more specific embodiments of embodiment 4 above, or based on embodiment 5 above, or based on embodiment 7 above.

[0462] The terminal generates a HARQ-ACK codebook based on the HARQ-ACK information used for multiple PDSCHs, and sends control information including the generated HARQ-ACK codebook to the base station (S1304).

[0463] Here, when configuring time binding, the terminal can configure / generate a type 1 HARQ-ACK codebook based on embodiment 2 above. Alternatively, when configuring PDCCH monitoring based on time slot groups, the terminal can configure / generate a type 1 HARQ-ACK codebook based on embodiment 3 above.

[0464] Alternatively, the terminal may configure / generate a type 2 HARQ-ACK codebook based on any one or a combination of one or more detailed embodiments of Embodiment 4 described above.

[0465] More specifically, the HARQ-ACK codebook may include a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. For example, the HARQ-ACK codebook can be generated by appending the second HARQ-ACK sub-codebook to the first HARQ-ACK sub-codebook.

[0466] In this case, the C-DAI and T-DAI values ​​of DCI can be applied individually to each of the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook.

[0467] Here, a first HARQ-ACK subcodebook can be generated for the PDSCH on one or more first serving cells, wherein the number of HARQ binding groups is set to 1. Furthermore, a second HARQ-ACK subcodebook can be generated for the PDSCH on one or more second serving cells, wherein the number of HARQ binding groups is set to greater than 1.

[0468] Simultaneously, upon receiving the second configuration information, among the multiple serving cells configured for the terminal, a first HARQ-ACK subcodebook can be generated for the PDSCH of one or more first serving cells where PDSCH scheduling is not configured or the number of HARQ binding groups is set to 1. Additionally, among the one or more serving cells configured with multiple PDSCH scheduling, a second HARQ-ACK subcodebook can be generated for the PDSCH of one or more second serving cells where the number of HARQ binding groups is set to greater than 1 or HARQ binding is not configured.

[0469] Here, when configuring HARQ bindings for one or more second serving cells, a second HARQ-ACK subcodebook can be generated based on the first HARQ-ACK information bits. The number of the first HARQ-ACK information bits can correspond to the maximum value between the product of the number of HARQ binding groups across all one or more second serving cells and the value of X. For PDSCH reception configured to carry two transport blocks (i.e., the maximum number of TBs (or codewords) through a DCI is set to 2) and no spatial bindings configured for HARQ-ACK information (i.e., HARQ-ACK information bits are generated by performing a logical AND operation on the HARQ-ACK information bits corresponding to the first TB and the second TB), the value of X can be 2; otherwise, the value of X can be 1.

[0470] Alternatively, when no HARQ binding is configured for one or more second serving cells, a second HARQ-ACK subcodebook can be generated based on the second HARQ-ACK information bits. The number of second HARQ-ACK information bits can correspond to the maximum value between the product of the number of PDSCHs that can be scheduled across all one or more second serving cells in a single DCI and the value of X. For cells configured to receive PDSCHs carrying two transport blocks (i.e., the maximum number of TBs (or codewords) through a DCI is set to 2) and not configured with spatial binding for HARQ-ACK information (i.e., generating HARQ-ACK information bits by performing a logical AND operation on the HARQ-ACK information bits corresponding to the first TB and the second TB), the value of X can be 2; otherwise, the value of X can be 1.

[0471] Alternatively, the type 2 HARQ-ACK codebook can be configured / generated based on embodiment 6 above. Alternatively, when some PDSCH transmissions / receptions scheduled by M-DCI are omitted, the HARQ-ACK codebook can be configured / generated based on embodiment 7 above.

[0472] Furthermore, based on Embodiment 1 above, when only PDSCHs overlapping with uplink symbols in the HARQ binding of a specific group are included, the HARQ-ACK information for that specific group can be generated as NACK (negative ACK). Alternatively, when one or more PDSCHs overlapping with uplink symbols in the HARQ binding of a specific group are included, the HARQ-ACK information for that specific group can be generated by considering the HARQ-ACK information of one or more PDSCHs overlapping with uplink symbols as ACK or NACK (negative ACK).

[0473] As described above, the terminal can generate a HARQ-ACK codebook based on the HARQ-ACK codebook type configured by the configuration information. Additionally, the terminal can send control information, including the generated HARQ-ACK codebook, to the base station via PUCCH or PUSCH. Here, the HARQ-ACK information can be sent to the base station at the time indicated by the DCI of the scheduling PDSCH. Furthermore, in addition to the HARQ-ACK codebook, the control information may also include scheduling requests, channel state information, uplink data (in the case of PUSCH), etc.

[0474] Figure 14 This is a diagram illustrating the operation of a base station for transmitting and receiving control information according to an embodiment of the present disclosure.

[0475] Figure 14 The operation of a base station based on the methods described above (e.g., any one of Embodiments 1 to 8 and its detailed embodiments or a combination of one or more (detailed) embodiments) is illustrated. Figure 14 This is for ease of description only and is not intended to limit the scope of this disclosure. Omissions may be made depending on the situation and / or configuration, etc. Figure 14 Some of the steps are shown below. Additionally... Figure 14 The base station in the example is just one example and can be implemented as Figure 15 The device shown. For example. Figure 15 The processor (102 / 202) can control the transmission and reception of channels / signals / data / information (e.g., RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, PHICH, etc.) and control the storage of transmitted or received channels / signals / data / information in memory (104 / 204) by using transceivers (106 / 206).

[0476] The base station sends configuration information (hereinafter referred to as the first configuration information) to the terminal for configuring HARQ-ACK binding for one or more of the multiple serving cells configured for the terminal (S1401).

[0477] Here, the first configuration information may also include information for configuring the type of HARQ-ACK codebook (e.g., the RRC parameter pdsch-HARQ-ACK-Codebook indicating type 1 (i.e., semi-static) HARQ-ACK codebook or type 2 (i.e., dynamic) HARQ-ACK codebook) and / or information about the number of HARQ-ACK binding groups (e.g., numberOfHARQBundlingGroups).

[0478] Furthermore, as mentioned above, the first configuration information can correspond to information about the number of HARQ-ACK binding groups. That is, if information about the number of HARQ binding groups for configuring a specific serving cell is provided, it can be assumed that time binding is configured for that specific serving cell. For example, if information about the number of HARQ binding groups for configuring a specific serving cell is provided, it can be assumed that time binding is configured for that specific serving cell. On the other hand, if information about the number of HARQ binding groups for configuring a specific serving cell is not provided, it can be assumed that time binding is not configured for that specific serving cell.

[0479] Additionally, along with the first configuration information (i.e., via a message or information element (IE)) or separately from the first configuration information (i.e., via a different message or IE), the base station may send to the terminal second configuration information (e.g., PDSCH-TimeDomainResourceAllocationListForMultiPDSCH) for configuring scheduling of multiple PDSCHs (referred to as multiPDSCH scheduling) via a single DCI for one or more of the multiple serving cells configured for the terminal. For example, if information for configuring scheduling for transmitting multiple PDSCHs (or PUSCHs) via a single DCI is provided for the corresponding serving cell, scheduling for transmitting multiple PDSCHs (or PUSCHs) via a single DCI on the corresponding cell can be configured / supported (this is referred to as multiPDSCH scheduling). On the other hand, if information for configuring scheduling for transmitting multiple PDSCHs (or PUSCHs) via a single DCI is not provided for the corresponding serving cell, multiPDSCH scheduling may not be configured / supported on the corresponding cell.

[0480] Multiple PDSCH scheduling can be configured for one or more serving cells among multiple serving cells configured for a terminal. In serving cells where multiple PDSCH scheduling is not configured, a PDSCH can be scheduled using a single DCI as in the prior art. Additionally, HARQ-ACK binding (i.e., time binding) can be configured for one or more serving cells among those configured with multiple PDSCH scheduling. For example, as described above, HARQ-ACK binding can be configured in the corresponding cell by configuring the number of HARQ-ACK binding groups. Thus, for multiple PDSCHs scheduled on serving cells with configured HARQ-ACK binding, HARQ-ACK information can be generated for each group. Here, HARQ-HARQ information for each group can be generated by performing a logical AND operation on the HARQ-ACK information of multiple PDSCHs included in each of the one or more groups.

[0481] Here, when the number of HARQ-ACK binding groups is set to 1, a single HARQ-ACK message can be generated; and when the number of HARQ-ACK binding groups is set to greater than 1, HARQ-ACK messages for the number of groups can be generated. On the other hand, for cells that do not have HARQ-ACK binding (i.e., time binding) configured in one or more serving cells with multi-PDSCH scheduling, HARQ-ACK messages can be generated for each of the multiple PDSCHs scheduled in the corresponding cell.

[0482] Here, the first and second configuration information can be sent via higher-level signaling (e.g., RRC signaling, MAC CE, etc.).

[0483] Here, based on the above embodiment 1, time binding can be configured for one or more of the multiple cells configured for the terminal.

[0484] The base station sends a DCI (S1402) to the terminal for scheduling one or more PDSCHs in each of the multiple serving cells configured for the terminal, and the base station sends multiple PDSCHs on the multiple serving cells configured for the terminal to the terminal (S1403).

[0485] Here, DCI can be sent via PDCCH.

[0486] As described above, one or more PDSCHs can be scheduled via M-DCI on cells configured with M-DCI among multiple serving cells configured for the terminal. On the other hand, a single PDSCH can be scheduled via S-DCI on cells not configured with M-DCI among multiple serving cells configured for the terminal.

[0487] In other words, the base station can send DCIs (e.g., each DCI format for each serving cell) for scheduling one or more PDSCHs in each of the multiple serving cells configured for the terminal. Additionally, the base station can send one or more PDSCHs in each of the multiple serving cells configured for the terminal (i.e., send multiple PDSCHs in multiple configured serving cells).

[0488] Here, in DAI signaling, DAI signaling can be executed based on any one or a combination of one or more specific embodiments of embodiment 4 above, or based on embodiment 5 above, or based on embodiment 7 above.

[0489] The base station receives control information from the terminal, including a HARQ-ACK codebook generated based on HARQ-ACK information for multiple PDSCHs (S1404).

[0490] Here, when configuring time binding, the type 1 HARQ-ACK codebook can be configured / generated based on embodiment 2 above. Alternatively, when configuring PDCCH monitoring based on time slot groups, the type 1 HARQ-ACK codebook can be configured / generated based on embodiment 3 above.

[0491] Alternatively, a type 2 HARQ-ACK codebook can be configured / generated based on any one or a combination of the detailed embodiments of embodiment 4 described above.

[0492] More specifically, the HARQ-ACK codebook may include a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. For example, the HARQ-ACK codebook can be generated by appending the second HARQ-ACK sub-codebook to the first HARQ-ACK sub-codebook.

[0493] In this case, the C-DAI and T-DAI values ​​of DCI can be applied individually to each of the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook.

[0494] Here, a first HARQ-ACK subcodebook can be generated for the PDSCH on one or more first serving cells, wherein the number of HARQ-bound groups is set to 1. Furthermore, a second HARQ-ACK subcodebook can be generated for the PDSCH on one or more second serving cells, wherein the number of HARQ-bound groups is set to greater than 1.

[0495] Simultaneously, upon receiving the second configuration information, among the multiple serving cells configured for the terminal, a first HARQ-ACK subcodebook can be generated for the PDSCH on multiple first serving cells where PDSCH scheduling is not configured or the number of HARQ binding groups is set to 1. Additionally, among one or more serving cells configured with multiple PDSCH scheduling, a second HARQ-ACK subcodebook can be generated for the PDSCH on one or more second serving cells where the number of HARQ binding groups is set to greater than 1 or HARQ binding is not configured.

[0496] Here, when configuring HARQ bindings for one or more second serving cells, a second HARQ-ACK subcodebook can be generated based on the first HARQ-ACK information bits. The number of the first HARQ-ACK information bits can correspond to the maximum value between the product of the number of HARQ binding groups across all one or more second serving cells and the value of X. For cells configured to receive PDSCH carrying two transport blocks (i.e., the maximum number of TBs (or codewords) through a DCI is set to 2) and not configured with spatial bindings for HARQ-ACK information (i.e., generating HARQ-ACK information bits by performing a logical AND operation on the HARQ-ACK information bits corresponding to the first TB and the second TB), the value of X can be 2; otherwise, the value of X can be 1.

[0497] Alternatively, when no HARQ binding is configured for one or more second serving cells, a second HARQ-ACK subcodebook can be generated based on the second HARQ-ACK information bits. The number of second HARQ-ACK information bits can correspond to the maximum value between the product of the number of PDSCHs that can be scheduled across all one or more second serving cells in a single DCI and the value of X. For cells configured to receive PDSCHs carrying two transport blocks (i.e., the maximum number of TBs (or codewords) through a DCI is set to 2) and not configured with spatial binding for HARQ-ACK information (i.e., generating HARQ-ACK information bits by performing a logical AND operation on the HARQ-ACK information bits corresponding to the first TB and the second TB), the value of X can be 2; otherwise, the value of X can be 1.

[0498] Alternatively, the type 2 HARQ-ACK codebook can be configured / generated based on embodiment 6 above. Alternatively, when some PDSCH transmissions / receptions scheduled by M-DCI are omitted, the HARQ-ACK codebook can be configured / generated based on embodiment 7 above.

[0499] Furthermore, based on Embodiment 1 above, when only PDSCHs overlapping with uplink symbols in the HARQ binding of a specific group are included, the HARQ-ACK information for that specific group can be generated as NACK (negative ACK). Alternatively, when one or more PDSCHs overlapping with uplink symbols in the HARQ binding of a specific group are included, the HARQ-ACK information for that specific group can be generated by considering the HARQ-ACK information for the one or more PDSCHs overlapping with uplink symbols as ACK or NACK (negative ACK).

[0500] The base station can receive control information, including the generated HARQ-ACK codebook, from the terminal via PUCCH or PUSCH. Here, HARQ-ACK information can be sent from the terminal at the time indicated by the DCI of the scheduling PDSCH. In addition to the HARQ-ACK codebook, the control information may also include scheduling requests, channel state information, uplink data (in the case of PUSCH), etc.

[0501] The general-purpose devices disclosed herein can be used.

[0502] Figure 15 This is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0503] refer to Figure 15 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).

[0504] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and may additionally 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 operation flowcharts disclosed herein. For example, the processor 102 may transmit a wireless signal including the first information / signal via the transceiver 106 after generating first information / signal by processing information in the memory 104. Furthermore, the processor 102 may receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained through signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and may store various information relating to the operation of the processor 102. For example, the memory 104 may store software code including commands for performing all or part of the processes controlled by the processor 102 or for performing the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 106 may be connected to processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used with an RF (radio frequency) unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0505] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and may additionally 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 operation flowcharts disclosed in this 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 via the transceiver 206. Additionally, the processor 202 may receive wireless signals including fourth information / signals via the transceiver 206, and then store information obtained through signal processing of 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 operation flowcharts disclosed in this disclosure. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). Transceiver 206 may be connected to processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used with an RF unit. In this disclosure, wireless device may refer to a communication modem / circuit / chip.

[0506] The hardware components of wireless devices 100 and 200 will be described in more detail below. However, they are not limited to this; 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). 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, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed in this disclosure to provide them to one or more transceivers 106 and 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information in accordance with the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure.

[0507] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 202 may be implemented by hardware, firmware, software, or a combination thereof. In examples, 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 one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this disclosure may be included in one or more processors 102, 202 or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this invention may be implemented by firmware or software in the form of code, commands, and / or command sets.

[0508] One or more memories 104, 204 may be connected to one or more processors 102, 202 and are capable of storing data, signals, messages, information, programs, code, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard disk drive, registers, digital memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located internally and / or externally to one or more processors 102, 202. Furthermore, 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.

[0509] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., mentioned in the methods and / or operation flowcharts, etc., disclosed herein 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 descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein 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. Furthermore, 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. Furthermore, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., mentioned in the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein through one or more antennas 108, 208. In this invention, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may process the received wireless signals / channels, etc., by converting them from RF band signals to baseband signals using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed by using one or more processors 102, 202 from baseband signals to RF band signals. Therefore, the one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0510] The above embodiments combine the elements and features of this disclosure in a predetermined form. Unless otherwise expressly stated, each element or feature should be considered optional. Each element or feature can be implemented without combination with other elements or features. Furthermore, embodiments of this disclosure may include combinations of certain elements and / or features. The order of operations described in the embodiments of this disclosure may be changed. Some elements or features of one embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. It is clear that embodiments may include combinations of claims where there is no explicit dependency in the claims, or may be included as new claims by amendment after the application.

[0511] It will be apparent to those skilled in the art that this disclosure may be practiced in other specific forms without departing from the essential characteristics of this disclosure. Therefore, the foregoing detailed description should not be construed as restrictive in every respect, but rather as illustrative. The scope of the invention should be determined by a reasonable interpretation of the appended claims, and all variations within the equivalent scope of this disclosure are included within the scope of the invention.

[0512] The scope of this disclosure includes software or machine-executable commands (e.g., operating systems, applications, firmware, programs, etc.) that operate in a device or computer according to methods of various embodiments, and non-transitory computer-readable media that store such software or commands and are executable in the device or computer. Commands that can be used to program a processing system to perform the features described in this disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in this disclosure can be implemented using a computer program product including such a storage medium. The storage medium may include, but is not limited to, high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state storage devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory may optionally include one or more storage devices located remote from the processor. Alternatively, the non-volatile memory devices in the memory may include non-transitory computer-readable storage media. The features described in this disclosure can be stored in any machine-readable medium to control the hardware of a processing system and can be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using results from embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0513] Here, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may include narrowband Internet of Things (IoT) for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names. Alternatively, the wireless communication technologies implemented in the wireless devices 100 and 200 of this disclosure may perform communication based on LTE-M technology. Here, in examples, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (Enhanced Machine-Type Communication). For example, LTE-M technology may be implemented in at least any of the following standards: 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and is not limited to the aforementioned names. Alternatively, the wireless communication technology implemented in the wireless devices 100 and 200 of this disclosure may include at least any one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and it is not limited to the aforementioned names. In the example, ZigBee technology can generate a PAN (Personal Area Network) associated with small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be referred to by various names.

[0514] [Industrial Availability]

[0515] The method proposed in this invention is mainly described using 3GPP LTE / LTE-A and 5G systems as examples, but it can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method for transmitting HARQ (Hybrid Automatic Repeat Request)-ACK (Acknowledgement) information in a wireless communication system, wherein the method is performed by a terminal and comprises: Receive first configuration information for configuring HARQ binding for one or more of a plurality of serving cells configured for the terminal; Receive downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCH) in each of the plurality of serving cells; Receive multiple PDSCHs on the multiple serving cells; and Send HARQ-ACK information for the multiple PDSCHs. The HARQ-ACK codebook corresponding to the HARQ-ACK information includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. Specifically, the first HARQ-ACK subcodebook is determined for one or more first serving cells where the number of HARQ-bound groups is set to 1. Specifically, the number of HARQ-bound groups is set to one or more second serving cells greater than 1 to determine the second HARQ-ACK subcodebook.

2. The method according to claim 1, further comprising: Receive second configuration information for configuring multiple PDSCH scheduling, wherein the multiple PDSCH scheduling is used to schedule multiple PDSCHs for one or more serving cells among the plurality of serving cells through a single DCI.

3. The method according to claim 2, in, The first HARQ-ACK subcodebook is determined for one or more first serving cells among the plurality of serving cells where the multi-PDSCH scheduling is not configured or the number of HARQ-bound groups is set to 1. Specifically, the second HARQ-ACK subcodebook is determined for one or more second serving cells in which the number of HARQ binding groups is set to be greater than 1 or the HARQ binding is not configured.

4. The method according to claim 1, in, Based on configuring the HARQ binding for the one or more second serving cells, the second HARQ-ACK subcodebook is determined based on the first HARQ-ACK information bits. Wherein, the number of the first HARQ-ACK information bits corresponds to the maximum value between the product of the number of HARQ-bound groups across all one or more of the second serving cells and the value of X. Specifically, for cells where PDSCH reception carrying two transport blocks is configured but spatial binding for HARQ-ACK information is not configured, the value of X is 2; otherwise, the value of X is 1.

5. The method according to claim 1, in, Since the HARQ binding is not configured for the one or more second serving cells, the second HARQ-ACK subcodebook is determined based on the second HARQ-ACK information bits. Wherein, the number of the second HARQ-ACK information bits corresponds to the maximum value between the product of the number of PDSCHs schedulable via a single DCI and the value of X across all one or more of the second serving cells. Specifically, for cells where PDSCH reception carrying two transport blocks is configured but spatial binding for HARQ-ACK information is not configured, the value of X is 2; otherwise, the value of X is 1.

6. The method according to claim 1, in, The counter downlink assignment index (C-DAI) value and the total downlink assignment index (T-DAI) value of the DCI are respectively applied to each of the first HARQ-ACK subcodebook and the second HARQ-ACK subcodebook.

7. The method according to claim 1, wherein, The HARQ-ACK codebook is determined by appending the second HARQ-ACK subcodebook to the first HARQ-ACK subcodebook.

8. The method according to claim 1, in, Based on configuring the HARQ binding for a specific serving cell, HARQ-ACK information is generated for each of one or more groups of multiple PDSCHs used for scheduling on the specific serving cell.

9. The method according to claim 8, wherein, HARQ information for each group is generated by performing a logical AND operation on the HARQ-ACK information bits for the multiple PDSCHs included in each of the one or more groups.

10. The method according to claim 8, wherein, The HARQ-ACK information for the specific group is generated as a negative ACK (NACK) based only on the PDSCH that overlaps with the uplink symbols included in the specific group bound to the HARQ.

11. The method according to claim 8, wherein, Based on one or more PDSCHs that overlap with the uplink symbols included in the specific group bound to the HARQ, the HARQ-ACK information for the one or more PDSCHs is regarded as ACK or negative ACK (NACK) to generate HARQ-ACK information for the specific group.

12. A terminal for transmitting HARQ (Hybrid Automatic Repeat Request)-ACK (Acknowledgement) information in a wireless communication system, the terminal comprising: At least one transceiver, the at least one transceiver being used to transmit and receive wireless signals; as well as At least one processor, the at least one processor being used to control the at least one transceiver, Wherein, the at least one processor is configured to: Receive first configuration information for configuring HARQ-ACK binding for one or more of a plurality of serving cells configured for the terminal; Receive downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCH) in each of the plurality of serving cells; Receive multiple PDSCHs on the multiple serving cells; and Send HARQ-ACK information for the multiple PDSCHs. The HARQ-ACK codebook corresponding to the HARQ-ACK information includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. Specifically, the first HARQ-ACK subcodebook is determined for one or more first serving cells where the number of HARQ-bound groups is set to 1. Specifically, the number of HARQ-bound groups is set to one or more second serving cells greater than 1 to determine the second HARQ-ACK subcodebook.

13. A base station for receiving HARQ (Hybrid Automatic Repeat Request)-ACK (Acknowledgement) information in a wireless communication system, the base station comprising: At least one transceiver, the at least one transceiver being used to transmit and receive wireless signals; as well as At least one processor, the at least one processor being used to control the at least one transceiver, Wherein, the at least one processor is configured to: Send first configuration information for configuring HARQ-ACK binding for one or more of the multiple serving cells configured for the terminal; Send downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCH) in each of the plurality of serving cells; Send multiple PDSCHs on the multiple serving cells; and Receive HARQ-ACK information for the plurality of PDSCHs. The HARQ-ACK codebook corresponding to the HARQ-ACK information includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook. Specifically, the first HARQ-ACK subcodebook is determined for one or more first serving cells where the number of HARQ-bound groups is set to 1. Specifically, the number of HARQ-bound groups is set to one or more second serving cells greater than 1 to determine the second HARQ-ACK subcodebook.

Images