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

Abstract

To provide a method and an apparatus for transmitting and receiving control information in a wireless communication system.SOLUTION: A method of transmitting control information may include receiving, from a base station, first configuration information for configuring HARQ-ACK bundling for one or more serving cells among a plurality of serving cells configured for the terminal; receiving, from the base station, DCI for scheduling one or more 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 on the basis of HARQ-ACK information for the plurality of PDSCHs.SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting and receiving uplink control information in a wireless communication system.

Background Art

[0002] A mobile communication system was developed to provide a voice service while ensuring the user's mobility. However, the mobile communication system has expanded its scope to include not only voice but also data services, and currently, due to the explosive increase in traffic, there is a shortage of resources, and users are also demanding faster services. Therefore, a more developed mobile communication system is desired.

[0003] The requirements for a next-generation mobile communication system are, broadly speaking, the acceptance of explosive data traffic, an epoch-making increase in the transmission rate per user, the acceptance of a significantly increased number of connected devices, a very low end-to-end latency, and support for high energy efficiency. For this purpose, various technologies such as dual connectivity, massive multiple input multiple output (Massive MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being studied.

Summary of the Invention

Problems to be Solved by the Invention

[0004] A technical problem of the present 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.

[0005] The technical problem of the present disclosure is to provide a method and apparatus for transmitting and receiving HARQ (Hybrid Automatic Repeat and request)-ACK (acknowledgement) information for one or more downlink transmissions scheduled using a single downlink control information.

[0006] Furthermore, a further technical problem of the present disclosure is to provide a method and apparatus for transmitting and receiving a HARQ-ACK codebook when HARQ-ACK information is generated for a plurality of PDSCHs in a predetermined group.

[0007] The technical problem to be achieved in the present disclosure is not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those having ordinary knowledge in the technical field to which the present disclosure pertains from the following description.

Means for Solving the Problems

[0008] A method for transmitting control information in a wireless communication system according to an aspect of the present disclosure, wherein the method performed by a terminal includes receiving, from a base station, first configuration information for configuring HARQ (Hybrid Automatic Repeat and Request)-ACK (acknowledgement) bundling for one or more serving cells among a plurality of serving cells configured for the terminal; receiving, from the base station, downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCHs) 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. The HARQ-ACK codebook may include a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook, and the first HARQ-ACK sub-codebook may be generated for PDSCHs on one or more first serving cells for which the number of HARQ bundling groups is set to 1, and the second HARQ-ACK sub-codebook may be generated for PDSCHs on one or more second serving cells for which the number of HARQ bundling groups is set to be greater than 1.

[0009] A method for receiving control information in a wireless communication system according to another aspect of the present disclosure, the method performed by a base station, the method comprising: transmitting, to a terminal, first setting information for setting HARQ (Hybrid Automatic Repeat and request)-ACK (acknowledgement) bundling for one or more serving cells among a plurality of serving cells set for the terminal; transmitting, to the terminal, downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCHs) in each of the plurality of serving cells; transmitting, 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 the second HARQ-ACK sub-codebook, the first HARQ-ACK sub-codebook being generated for PDSCHs on one or more first serving cells for which the number of HARQ bundling groups is set to 1, and the second HARQ-ACK sub-codebook being generated for PDSCHs on one or more second serving cells for which the number of HARQ bundling groups is set to be greater than 1. [Advantage of the Invention]

[0010] According to an embodiment of the present disclosure, by assisting scheduling for one or more downlink transmissions and / or one or more uplink transmissions using one downlink control information, it is possible to increase the transmission efficiency of the downlink control information for scheduling the downlink transmission and / or the uplink transmission.

[0011] According to an embodiment of the present disclosure, by generating HARQ-ACK information for a plurality of PDSCHs for each predetermined group, the overhead of HARQ-ACK information bits can be reduced.

[0012] The effects obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those of ordinary skill in the technical field to which the present disclosure pertains from the following description.

Brief Description of the Drawings

[0013] The accompanying drawings, included as part of the detailed description to assist in understanding the present disclosure, provide embodiments related to the present disclosure and explain the technical features of the present disclosure together with the detailed description.

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

[0015] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is for explaining exemplary embodiments of the present disclosure, and is not for showing the only embodiment in which the present disclosure can be implemented. The following detailed description includes specific details for providing a complete understanding of the present disclosure. However, it is understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0016] In some cases, to avoid obscuring the concepts of the present disclosure, well-known structures and devices may be omitted, or may be shown in the form of a block diagram centered on the core functions of each structure and device.

[0017] In the present disclosure, when a component is "connected", "coupled", or "joined" to another component, this can include not only a direct connection relationship but also an indirect connection relationship in which there are additional components between them. Further, in the present disclosure, the terms "comprising" or "having" identify the presence of the recited features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0018] In the present disclosure, terms such as "first", "second", etc. are used only for the purpose of distinguishing one component from another and are not used to limit the components, and unless otherwise specified, do not limit the order or importance, etc. between the components. Thus, within the scope of the present disclosure, the first component in one embodiment can also be referred to as the second component in another embodiment, and similarly, the second component in one embodiment can be referred to as the first component in another embodiment.

[0019] The terms used in the present disclosure are for the purpose of describing particular embodiments and are not for limiting the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms are also intended to include the plural forms unless the context clearly dictates otherwise. The term "and / or" as used in the present disclosure means that it may refer to one of the related listed items or include any and all possible combinations of two or more of them. Further, in the present disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0020] The present disclosure is described with respect to a wireless communication network or a wireless communication system, and the operations performed in the wireless communication network may be performed in the process of a device (e.g., a base station) that governs the wireless communication network controlling the network and transmitting or receiving signals, or in the process of a terminal coupled to the wireless network transmitting or receiving signals to or from the network or between terminals.

[0021] In the present disclosure, transmitting or receiving a channel means transmitting or receiving information or a signal on the channel. For example, transmitting a control channel means transmitting control information or a signal on the control channel. Similarly, transmitting a data channel means transmitting data information or a signal on the data channel.

[0022] In the following, the downlink (DL) means communication from the base station to the terminal, and the uplink (UL) means communication from the terminal to the base station. In the downlink, the transmitter may be part of the base station and the receiver may be part of the terminal. In the uplink, the transmitter may be part of the terminal and the receiver may be part of the base station. The base station may be represented as the first communication device, and the terminal may be represented as the second communication device. The base station (BS: Base Station) may be replaced by terms such as fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. Also, the terminal (Terminal) may be fixed or mobile, and may 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) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0023] The following techniques may be used in various wireless connection systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by wireless technologies such as UTRA (Universal Terrestrial Radio Access) and CDMA2000. TDMA may be implemented by wireless technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA may be implemented by wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (Registered Trademark) (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0024] For clarity of description, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of the present disclosure is not limited thereto. LTE means the technology after 3GPP TS (Technical Specification) 36.xxx Release 8. Specifically, the LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-A, and the LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-A pro. 3GPP NR means the technology after TS 38.xxx Release 15. LTE / NR may be called the 3GPP system. "xxx" means the detailed number of the standard document. LTE / NR may be called the 3GPP system. Regarding the background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference can be made to the matters described in the standard documents published before the present disclosure. For example, the following documents can be referred to.

[0025] In 3GPP LTE, reference can be made to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (General Description), TS 36.331 (Radio Resource Control).

[0026] In 3GPP NR, reference can be made to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), 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 (New Generation-Radio Access Network)), TS 38.331 (Radio Resource Control Protocol Specification).

[0027] The abbreviations of the terms that can be used in the present disclosure are defined as follows.

[0028] - BM: Beam Management

[0029] - CQI: Channel Quality Indicator

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

[0031] - CSI: Channel State Information

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

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

[0034] - DMRS: Demodulation Reference Signal

[0035] - FDM: Frequency Division Multiplexing

[0036] - FFT: Fast Fourier Transform

[0037] - IFDMA: Interleaved Frequency Division Multiple Access

[0038] - IFFT: Inverse Fast Fourier Transform

[0039] - L1-RSRP: Layer 1 reference signal received power

[0040] - L1-RSRQ: Layer 1 reference signal received quality

[0041] - MAC: medium access control

[0042] - NZP: non-zero power

[0043] - OFDM: orthogonal frequency division multiplexing

[0044] - PDCCH: physical downlink control channel

[0045] - PDSCH: physical downlink shared channel

[0046] - PMI: precoding matrix indicator

[0047] - RE: resource element

[0048] - RI: Rank indicator

[0049] - RRC: radio resource control

[0050] - RSSI: received signal strength indicator

[0051] - Rx: Reception

[0052] - QCL: Quasi co-location

[0053] - SINR: Signal to interference and noise ratio

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

[0055] - TDM: Time division multiplexing

[0056] - TRP: Transmission and reception point

[0057] - TRS: Tracking reference signal

[0058] - Tx: Transmission

[0059] - UE: User equipment

[0060] - ZP: Zero power

[0061] System general

[0062] As more communication devices demand greater communication capacity, there is a growing need for mobile broadband communication that is improved compared to existing radio access technologies (RATs). In addition, massive Machine Type Communications (MTC), which connects a large number of devices and things to provide various services anytime and anywhere, is also one of the major issues considered in next-generation communications. In addition to this, the design of communication systems considering services / terminals sensitive to reliability and latency is also being discussed. Thus, the introduction of next-generation RATs considering enhanced mobile broadband communication (eMBB), massive MTC (mMTC), Ultra-Reliable and Low Latency Communication (URLLC), etc. is being discussed, and in this disclosure, for convenience, this technology is referred to as NR. NR is an expression representing an example of a 5G RAT.

[0063] The new RAT system including NR uses an OFDM transmission method or a transmission method similar thereto. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the existing numerology of LTE / LTE-A as it is, but can support a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell can also support multiple numerologies. That is, terminals operating with different numerologies may coexist within one cell.

[0064] Numerology corresponds to one subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0065] FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure is applicable.

[0066] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide NG-RA (NG-Radio Access) user plane (i.e., new AS (access stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and control plane (RRC) protocol termination for the UE. The gNBs are interconnected via the Xn interface. The gNBs are also connected to the NGC (New Generation Core) via the NG interface. More specifically, the gNBs are connected to the AMF (Access and Mobility Management Function) via the N2 interface and to the UPF (User Plane Function) via the N3 interface.

[0067] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure is applicable.

[0068] The NR system can support a number of numerologies. Here, the numerology may be defined by the subcarrier spacing and the cyclic prefix (CP) overhead. At this time, a number of subcarrier spacings may be derived by scaling the basic (reference) subcarrier spacing by an integer N (or μ). Also, even assuming that a very low subcarrier spacing is not used at a very high carrier frequency, the numerology used may be selected independently of the frequency band. Also, in the NR system, various frame structures with a number of numerologies may be supported.

[0069] The OFDM numerologies and frame structures that can be considered in the NR system are described below. A number of OFDM numerologies supported in the NR system may be defined as shown in Table 1 below.

[0070] [Table 1]

[0071] NR supports a number of numerologies (or subcarrier spacings (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands. When the SCS is 30 kHz / 60 kHz, it supports dense-urban areas, lower latency, and wider carrier bandwidths. When the SCS is 60 kHz or higher, it supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0072] The NR frequency band is defined as two types (FR1, FR2) of frequency ranges. FR1 and FR2 may be configured as shown in Table 2 below. Also, FR2 can mean millimeter wave (mmW).

[0073] [Table 2]

[0074] In relation to the frame structure in the NR system, the sizes of various fields in the time domain are T c = 1 / (Δf max · N f ) expressed as multiples of time units. Here, Δf max = 480 · 10 3 Hz, and Nf is 4096. Downlink and uplink transmissions are in T f = 1 / (Δf max N f / 100)·T c = 10 ms intervals and are organized into radio frames. Here, each radio frame has T sf =(Δf max N f / 1000)·T c = 1 ms intervals and is composed of 10 subframes. In this case, there may be one set of frames for the uplink and one set of frames for the downlink. Also, the transmission at the uplink frame number i from the terminal must start T TA =(N TA +N TA,offset )T c before the start of the corresponding downlink frame at the terminal. For the subcarrier spacing configuration μ, the slot is numbered in increasing order of n s μ ∈ {0,...,N slot subframe,μ -1} within the subframe and in increasing order of n s,f μ ∈ {0,...,N slot frame,μ -1} within the radio frame. One slot is composed of N symb slot consecutive OFDM symbols, and N symb slot is determined by the CP. The start of slot n s μ in the subframe is the OFDM symbol n s μ N symb slotis aligned in time with the start. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or an uplink slot can be used.

[0075] Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per radio frame (N slot frame,μ ), and the number of slots per subframe (N slot subframe,μ ) in the normal CP. 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.

[0076]

Table 3

[0077]

Table 4

[0078] Figure 2 shows an example when μ = 2 (SCS is 60 kHz). Referring to Table 3, one subframe can include 4 slots. The one subframe = {1, 2, 4} slots shown in Figure 2 is an example, and the number of slots that can be included in one subframe is defined as in Table 3 or Table 4. Also, a mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols.

[0079] In relation to physical resources in the NR system, an antenna port, a resource grid, a resource element, a resource block, a carrier part, etc. may be considered. Hereinafter, the physical resources that can be considered in the NR system will be specifically described.

[0080] First, in relation to the antenna port, the antenna port is defined such that the channel carried by the symbols on the antenna port can be inferred from the channels carried by other symbols on the same antenna port. When the large-scale properties of the channels carried by the symbols on one antenna port can be inferred from the channels carried by the symbols on other antenna ports, it can be said that the two antenna ports are in a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale properties include any one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0081] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure is applicable.

[0082] Referring to FIG. 3, the resource grid is composed of N RB μ N sc RB sub-carriers, and it is exemplarily described that one sub-frame is composed of 14·2 μ OFDM symbols, but it is not limited thereto. In the NR system, the transmitted signal is N RBμ N sc RB One or more resource grids composed of sub - carriers and 2 μ N symb (μ) is described by the OFDM symbols of. Here, N RB μ ≤ N RB max,μ is. The said N RB max,μ represents the maximum transmission bandwidth, which may vary not only with the numerology but also between the uplink and the downlink. In this case, one resource grid may be set separately for each of μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element and is uniquely identified by the index pair JPEG2025106493000006.jpg10144. Here, k = 0,..., N RB μ N sc RB −1 is the index in the frequency domain, and JPEG2025106493000007.jpg12133 represents the position of the symbol within the sub - frame. When indicating a resource element in a slot, the index pair (k, l) is used. Here, l = 0,..., N symb μ −1. The resource element for μ and antenna port p JPEG2025106493000008.jpg11147 corresponds to a complex value JPEG2025106493000009.jpg811. When there is no risk of confusion or when a specific antenna port or numerology is not specified, the indices p and μ may be dropped, and as a result, the complex value is JPEG2025106493000010.jpg912 or It can be 912 for JPEG2025106493000011.jpg. Also, a resource block (RB) is defined as N sc RB = 12 consecutive subcarriers in the frequency domain.

[0083] Point A serves as the common reference point of the resource block grid and is obtained as follows.

[0084] - offsetToPointA for the primary cell (PCell) downlink indicates the frequency offset between the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block used by the terminal for initial cell selection and point A. It is expressed in units of resource blocks assuming a 15 kHz subcarrier spacing for FR1 and a 60 kHz subcarrier spacing for FR2.

[0085] - absoluteFrequencyPointA indicates the frequency - position of point A expressed as in the absolute radio - frequency channel number (ARFCN).

[0086] Common resource blocks are numbered upward from 0 in the frequency domain for the subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for the subcarrier spacing setting μ coincides with 'point A'. The relationship between the common resource block number n CRB μ in the frequency domain and the resource element (k, l) for the subcarrier spacing setting μ is given as in Equation 1 below.

[0087]

Equation

[0088] In Equation 1, k is defined relative to Point A such that k = 0 corresponds to the sub-carrier centered at Point A. The physical resource block is numbered from 0 to N BWP,i size,μ -1 within the bandwidth part (BWP), and i is the number of the BWP. In BWP i, the relationship between the physical resource block n PRB and the common resource block n CRB is given by Equation 2 below.

[0089]

Equation

[0090] N BWP,i start,μ is the common resource block where the BWP starts relative to the common resource block 0.

[0091] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure is applicable. And FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure is applicable.

[0092] Referring to FIGS. 4 and 5, a slot includes a plurality of symbols in the time domain. For example, in the case of normal CP, one slot includes 7 symbols, while in the case of extended CP, one slot includes 6 symbols.

[0093] The carrier wave includes a plurality of sub-carrier waves in the frequency domain. An RB (Resource Block) is defined as a plurality (e.g., 12) of consecutive sub-carrier waves in the frequency domain. A BWP (Bandwidth Part) is defined as a plurality of consecutive (physical) resource blocks in the frequency domain and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier wave can include up to N (e.g., 5) BWPs. Data communication is performed on the activated BWP, and only one BWP may be activated for one terminal. Each element in the resource grid is called a resource element (RE: Resource Element), and one complex symbol may be mapped to it.

[0094] The NR system may support up to 400 MHz per component carrier (CC: Component Carrier). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Or, considering various use cases (e.g., eMBB, URLLC, Mmtc, V2X, etc.) operating within one wideband CC, different numerologies (e.g., sub-carrier spacing, etc.) may be supported for different frequency bands within the CC. Or, the capabilities of terminals may vary for the maximum bandwidth. Considering this, the base station may instruct the terminal to operate only on a part of the bandwidth instead of the entire bandwidth of the wideband CC, and this part of the bandwidth is defined as the bandwidth part (BWP) for convenience. A BWP may be composed of consecutive RBs on the frequency axis and can correspond to one numerology (e.g., sub-carrier spacing, CP length, slot / minislot interval).

[0095] On one hand, the base station can configure multiple BWPs even within one CC configured for the terminal. For example, in the PDCCH monitoring slot, a BWP that occupies a relatively small frequency region can be configured, and the PDSCH indicated by the PDCCH may be scheduled on a larger BWP than that. Alternatively, when UEs concentrate on a specific BWP, other BWPs may be configured for some terminals for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between adjacent cells, etc., a part of the spectrum of the entire bandwidth can be excluded, and both BWPs can be configured even within the same slot. That is, the base station can configure at least one DL / UL BWP for the terminal associated with the wideband CC. The base station can activate at least one of the DL / UL BWPs configured at a specific time (by means of L1 signaling or MAC CE (Control Element) or RRC signaling, etc.). Also, the base station can instruct switching to other configured DL / UL BWPs (by means of L1 signaling or MAC CE or RRC signaling, etc.). Or, when the timer value expires based on the timer, it may switch to the defined DL / UL BWP. At this time, the activated DL / UL BWP is defined as the active DL / UL BWP. However, during the initial access process of the terminal or in situations such as before the RRC connection is set up, the terminal may not be able to receive the configuration for the DL / UL BWP. Therefore, the DL / UL BWP assumed by the terminal in such a situation is defined as the initial active DL / UL BWP.

[0096] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure is applicable and a general signal transmission / reception method using them.

[0097] In a wireless communication system, a terminal receives information from a base station on the downlink, and the terminal transmits information to the base station on the uplink. The information transmitted and received between the base station and the terminal includes data and various control information, and there are various physical channels according to the types / uses of the information they transmit and receive.

[0098] When the terminal is powered on or newly enters a cell, it performs initial cell search operations such as synchronizing with the base station (S601). For this purpose, the terminal receives the primary synchronization signal (PSS) and the secondary synchronization signal (SSS) from the base station to synchronize with the base station and can obtain information such as the cell identifier (ID). After that, the terminal can receive the physical broadcast channel (PBCH) from the base station to obtain in-cell broadcast information. On the other hand, the terminal can receive the downlink reference signal (DL RS) in the initial cell search stage to check the downlink channel state.

[0099] After completing the initial cell search, the terminal receives the physical downlink shared channel (PDSCH) based on the physical downlink control channel (PDCCH) and the information carried on the PDCCH, and can obtain more specific system information (S602).

[0100] On one hand, when a terminal first connects to a base station or there is no radio resource for signal transmission, the terminal can perform a random access procedure (RACH) with the base station (steps S603 to S606). To this end, the terminal transmits a specific sequence as a preamble on a physical random access channel (PRACH) (S603 and S605), and can receive a response message for the preamble on a PDCCH and the corresponding PDSCH (S604 and S606). In the case of contention-based RACH, furthermore, a contention resolution procedure can be performed.

[0101] After performing the procedure as described above, the terminal can then perform PDCCH / PDSCH reception (S607) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S608) as general uplink / downlink signal transmission procedures. In particular, the terminal receives downlink control information (DCI) on the PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and the formats differ from each other depending on the purpose of use.

[0102] On the other hand, the control information transmitted by the terminal to the base station on the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In the 3GPP LTE system, the terminal can transmit control information such as the above-mentioned CQI / PMI / RI on the PUSCH and / or PUCCH.

[0103] Table 5 shows an example of DCI format in the NR system.

[0104] [Table 5]

[0105] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 can include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transmission block (TB: Transport Block) related information (e.g., MCS (Modulation Coding and Scheme), NDI (New Data Indicator), RV (Redundancy Version), etc.), HARQ (Hybrid - Automatic Repeat and request) related information (e.g., process number, DAI (Downlink Assignment Index), PDSCH - HARQ feedback timing, etc.), multi - antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.). The control information included in each DCI format may be defined in advance.

[0106] DCI format 0_0 is used for PUSCH scheduling in one cell. The information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled and transmitted by C - RNTI (Cell RNTI: Cell Radio Network Temporary Identifier) or CS - RNTI (Configured Scheduling RNTI) or MCS - C - RNTI (Modulation Coding Scheme Cell RNTI).

[0107] DCI format 0_1 is used to schedule one or more PUSCHs in one cell or to indicate downlink feedback information of a configured grant (CG) to a terminal. The information included in DCI format 0_1 is transmitted after being CRC scrambled by a C-RNTI or a CS-RNTI or an SP-CSI-RNTI (Semi-Persistent CSI RNTI) or an MCS-C-RNTI.

[0108] DCI format 0_2 is used to schedule PUSCHs in one cell. The information included in DCI format 0_2 is transmitted after being CRC scrambled by a C-RNTI or a CS-RNTI or an SP-CSI-RNTI or an MCS-C-RNTI.

[0109] Next, DCI formats 1_0, 1_1, and 1_2 can include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multi-antenna related information (e.g., antenna port, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), and PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.). The control information included in each DCI format may be defined in advance.

[0110] DCI format 1_0 is used for scheduling the PDSCH in one DL cell. The information included in DCI format 1_0 is transmitted after being CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0111] DCI format 1_1 is used for scheduling the PDSCH in one cell. The information included in DCI format 1_1 is transmitted after being CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0112] DCI format 1_2 is used for scheduling the PDSCH in one cell. The information included in DCI format 1_2 is transmitted after being CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0113] Data transmission and HARQ (Hybrid Automatic Repeat and reQuest)-ACK (Acknowledgement) process

[0114] FIG. 7 illustrates the HARQ-ACK procedure for downlink data in a wireless communication system to which the present disclosure is applicable.

[0115] Referring to FIG. 7, the terminal can detect the PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI formats 1_0, 1_1), and the PDCCH indicates the DL assignment-to-PDSCH offset (K0) and the PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0, 1_1 may include the following information.

[0116] - Frequency domain resource assignment: Indicates the RB resources assigned to the PDSCH (e.g., one or more (dis)continuous RBs).

[0117] - Time domain resource assignment: Indicates K0, the start position (e.g., OFDM symbol index) and length (e.g., number of OFDM symbols) of the PDSCH within a slot.

[0118] - PDSCH-to-HARQ_feedback timing indicator: Indicates K1.

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

[0120] - PUCCH resource indicator (PRI): Among multiple PUCCH resources within a PUCCH resource set, indicates the PUCCH resource used for UCI transmission.

[0121] After that, the terminal can receive the PDSCH in slot #(n + K0) according to the scheduling information of slot #n, and then transmit UCI using the PUCCH in slot #(n + K1). Here, the UCI includes the HARQ-ACK response for the PDSCH. When the PDSCH is configured to transmit a maximum of 1 TB, the HARQ-ACK response may be composed of 1 bit. When the PDSCH is configured to transmit a maximum of 2 TBs, the HARQ-ACK response may be composed of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. When the HARQ-ACK transmission time for multiple PDSCHs is specified as slot #(n + K1), the UCI transmitted in slot #(n + K1) includes the HARQ-ACK responses for multiple PDSCHs.

[0122] CBG (Code Block Group)-based HARQ process

[0123] In LTE, TB (Transport Block)-based HARQ processes are supported. In NR, both TB-based HARQ processes and CBG-based HARQ processes are supported.

[0124] FIG. 8 illustrates the processing procedure and structure of a TB in a wireless communication system to which the present disclosure is applicable.

[0125] The procedure of FIG. 8 may be applied to data on transmission channels of DL-SCH (Shared Channel), PCH (Paging Channel), and MCH (Multicast Channel). UL TB (or data on the UL transmission channel) may also be processed similarly.

[0126] Referring to FIG. 8, the transmitter adds a CRC (e.g., 24 bits) (TB CRC) for error checking to the TB. Thereafter, considering the size of the channel encoder, the TB+CRC can be divided into a plurality of code blocks. As an example, in LTE, the maximum size of a code block is 6144 bits. Thus, if the TB size is 6144 bits or less, no code block is configured, and when the TB size is larger than 6144 bits, the TB is divided in units of 6144 bits, and a plurality of code blocks are configured. A CRC (e.g., 24 bits) (CB CRC) for error checking is individually added to each code block. Each code block forms a codeword by being combined into one after channel coding and rate matching. In the TB-based HARQ process, data scheduling and the resulting HARQ process are performed in TB units, and the CB CRC is used to determine early termination of TB decoding.

[0127] FIG. 9 illustrates a CBG-based HARQ process in a wireless communication system to which the present disclosure is applicable.

[0128] In the CBG-based HARQ process, data scheduling and the resulting HARQ process may be performed in units of CBGs.

[0129] Referring to FIG. 9, the terminal can receive from the base station information regarding the number M of code block groups per transmission block by means of a higher layer signal (e.g., an RRC signal) (S1602). Thereafter, the terminal can receive an initial data transmission from the base station (by means of PDSCH) (S1604). Here, the data includes a transmission block, the transmission block includes a plurality of code blocks, and the plurality of code blocks may be divided into one or more code block groups. Here, some of the code block groups may include ceiling(K / M) code blocks, and the remaining code blocks may include flooring(K / M) code blocks. K indicates the number of code blocks in the data. Thereafter, the terminal can feedback to the base station code block group-based A / N information for the data (S1606), and the base station can perform data retransmission based on the code block groups (S1608). The A / N information may be transmitted by means of PUCCH or PUSCH. Here, the A / N information includes a plurality of A / N bits for the data, and each A / N bit can indicate each A / N response generated in units of code block groups for the data. The payload size of the A / N information may be maintained the same based on M regardless of the number of code block groups constituting the data.

[0130] Dynamic / semi-static HARQ-ACK codebook method

[0131] In NR, a dynamic HARQ-ACK codebook scheme and a semi-static HARQ-ACK codebook scheme are supported. The HARQ-ACK (or, A / N) codebook may be replaced by the HARQ-ACK payload.

[0132] When the dynamic HARQ-ACK codebook method is configured, the size of the A / N payload changes according to the number of actually scheduled DL data. Therefore, the PDCCH associated with DL scheduling includes a counter DAI (Downlink Assignment Index) and a total DAI. The counter DAI indicates the {CC, slot} scheduling order value calculated by the CC (Component Carrier) (or cell) priority method and is used to specify the position of the A / N bit in the A / N codebook. The total DAI indicates the cumulative slot-by-slot scheduling value up to the current slot and is used to determine the size of the A / N codebook.

[0133] When the quasi-static A / N codebook scheme is configured, the size of the A / N codebook is fixed (to the maximum value) regardless of the number of actually scheduled DL data. Specifically, the (maximum) A / N payload (size) transmitted by one PUCCH within one slot may be determined as the number of A / N bits corresponding to the combination of all the CCs configured for the terminal and all the DL scheduling slots (or, PDSCH transmission slots or PDCCH monitoring slots) for which the A / N transmission timing can be indicated (hereinafter, the bundling window). For example, the DL grant DCI (PDCCH) includes PDSCH-to-A / N timing information, and the PDSCH-to-A / N timing information can have one of a plurality of values (e.g., k). For example, when the PDSCH is received in slot #m and the PDSCH-to-A / N timing information in the DL grant DCI (PDCCH) scheduling the PDSCH indicates k, the A / N information for the PDSCH may be transmitted in slot #(m + k). As an example, k ∈ {1, 2, 3, 4, 5, 6, 7, 8} may be given. On the other hand, when the A / N information is transmitted in slot #n, the A / N information may include the maximum possible A / N based on the bundling window. That is, the A / N information in slot #n may include the A / N corresponding to slot #(n - k). For example, when k ∈ {1, 2, 3, 4, 5, 6, 7, 8}, the A / N information in slot #n includes the A / N corresponding to slots #(n - 8) to #(n - 1) regardless of the actual DL data reception (i.e., the maximum number of A / N). Here, the A / N information may be replaced with an A / N codebook, an A / N payload. Also, a slot may be understood / replaced as an opportunity for DL data reception. As illustrated, the bundling window is determined based on the PDSCH-to-A / N timing with respect to the A / N slot, and the PDSCH-to-A / N timing set may have predefined values (e.g., {1, 2, 3, 4, 5, 6, 7, 8}) or may be set by upper layer (RRC) signaling.

[0134] The dynamic / semi-static HARQ-ACK codebook configuration defined in the NR standard is as follows. When the UE is set with the semi-static PDSCH HARQ-ACK codebook (pdsch-HARQ-ACK-Codebook) parameter, the UE determines the reporting of the Type-1 HARQ-ACK codebook (i.e., semi-static HARQ-ACK codebook). On the other hand, when the UE is set with the dynamic PDSCH HARQ-ACK codebook (or pdsch-HARQ-ACK-Codebook-r16) parameter, the UE determines the reporting of the Type-2 HARQ-ACK codebook (i.e., dynamic HARQ-ACK codebook).

[0135] Method for configuring HARQ-ACK codebook for multi-PDSCH scheduling

[0136] - PUSCH: Physical Uplink Shared Channel

[0137] - RRM: Radio resource management

[0138] - SCS: Sub-carrier spacing

[0139] - RLM: Radio link monitoring

[0140] - DCI: Downlink Control Information

[0141] - CAP: Channel Access Procedure

[0142] - Ucell: Unlicensed cell

[0143] - TBS: Transport Block Size

[0144] - TDRA: Time Domain Resource Allocation

[0145] - SLIV: Starting and Length Indicator Value (It is an indication value for the start symbol index and the number of symbols within a slot of PDSCH and / or PUSCH. It may be set as a component of an entry that constitutes a TDRA field in a PDCCH that schedules the PDSCH and / or PUSCH.)

[0146] - BWP: BandWidth Part (It may be composed of consecutive resource blocks (RBs) on the frequency axis. It may correspond to one numerology (e.g., SCS, CP length, slot / mini-slot duration, etc.). Also, multiple BWPs may be set in one carrier (the number of BWPs per carrier may also be limited.), but the number of activated BWPs may be limited to a part (e.g., 1) per carrier.)

[0147] - CORESET: COntrol REsourse SET (It means the time-frequency resource area where a PDCCH can be transmitted, and the number of CORESETs per BWP may be limited.)

[0148] - REG: Resource element group

[0149] - SFI: Slot Format Indicator (An indicator that indicates the symbol-level DL / UL direction within a specific slot and is transmitted by the group common PDCCH.)

[0150] - COT: Channel occupancy time

[0151] - SPS: Semi-persistent scheduling

[0152] - QCL: Quasi-Co-Location. The QCL relationship between two reference signals (RS) means that QCL parameters such as Doppler shift, Doppler spread, average delay, delay spread, and Spatial Rx parameter obtained from one RS may also be applicable to other RSs (or the antenna ports of the said RS). In the NR system, 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 parameter}. For a certain DL RS antenna port, the first DL RS may be set as a reference for QCL type X (X = A, B, C, or D), and furthermore, the second DL RS may be set as a reference for QCL type Y (Y = A, B, C, or D, provided that X ≠ Y).

[0153] - TCI: Transmission Configuration Indication (One TCI state includes the QCL relationship between one or more DL RSs such as the DM-RS port of PDSCH, the DM-RS port of PDCCH, or the CSI-RS port of CSI-RS resource. For the "Transmission Configuration Indication" in the fields within the DCI that schedules PDSCH, the TCI state index corresponding to each code point that constitutes the field is activated by the MAC control element (CE), and the TCI state setting for each TCI state index is set by RRC signaling. In the Rel-16 NR system, the TCI state is set between DL RSs, but in subsequent releases, setting between DL RS and UL RS or between UL RS and UL RS may be allowed. Examples of UL RS include SRS, PUSCH DM-RS, PUCCH DM-RS, etc.)

[0154] - SRI: SRS Resource Indicator (Indicates one of the SRS resource index values set by "SRS resource indicator" in the fields within the DCI that schedules PUSCH. When transmitting PUSCH, the terminal can transmit PUSCH using the same spatial domain transmission filter as that used for reference signal transmission and reception associated with the SRS resource. Here, for each SRS resource, the reference RS (reference RS) is set by RRC signaling using the SRS-SpatialRelationInfo parameter, and the SS / PBCH block, CSI-RS, or SRS, etc. may be set as the reference RS.)

[0155] - TRP: Transmission and Reception Point

[0156] To increase the transmission efficiency of scheduling DCI for PDSCH and / or PUSCH, multiple PDSCH (or PUSCH) transmissions may be supported by one DCI. For convenience, in the present disclosure, the DCI is referred to as M-DCI, and the DCI that schedules a single PDSCH (or PUSCH) is referred to as S-DCI.

[0157] For example, the scheduling for multiple PDSCH (or PUSCH) transmissions by one DCI may be set for the terminal by upper layer signaling (e.g., RRC signaling). For each of one or more serving cells set for the terminal, it may be set whether the scheduling for multiple PDSCH (or PUSCH) transmissions is performed by one DCI. For example, when information for setting the scheduling for multiple PDSCH (or PUSCH) transmissions by one DCI is provided for the serving cell, the scheduling for multiple PDSCH (or PUSCH) transmissions by one DCI may be set / supported on the cell. On the other hand, when information for setting the scheduling for multiple PDSCH (or PUSCH) transmissions by one DCI is not provided for the serving cell, the scheduling for multiple PDSCH (or PUSCH) transmissions by one DCI may not be set / supported on the cell.

[0158] Here, even for M-DCI, depending on the case, it may schedule only a single PDSCH, or it may schedule multiple PDSCHs. For example, when configuring the TDRA entry of M-DCI, only one SLIV may be associated with a certain row index #A, and multiple SLIVs may be associated with row index #B. Here, when the row index #A is indicated by M-DCI, it means that only a single PDSCH is scheduled by the DCI. On the other hand, when the row index #B is indicated by M-DCI, the DCI can mean scheduling multiple PDSCHs. For convenience, the case where it is scheduled by S-DCI and the case where only one PDSCH is scheduled by M-DCI (or when SPS PDSCH release or SCell dormancy is indicated by DCI) are called the single-PDSCH case, and the case where multiple PDSCHs are scheduled by M-DCI is called the multi-PDSCH case.

[0159] Therefore, in the present disclosure, a method for configuring a type-1 (i.e., semi-static) or type-2 (i.e., dynamic) HARQ-ACK codebook (HARQ-ACK codebook, HCB) considering the multi-PDSCH case is proposed.

[0160] In the NR system, the millimeter wave (mmWave) band (e.g., exceeding 7.125 or 24 GHz up to 52.6 GHz) is defined as frequency range 2 (FR2). In this band, the sub-carrier spacing (SCS) of the SS / PBCH block may be one of 120 or 240 kHz, and for other signals / channels (e.g., PDCCH, PDSCH, PUSCH, etc.), it may be one of 60 or 120 kHz.

[0161] In a high frequency (HF) NR system (e.g., named FR3 (or FR2-2) for convenience of explanation, from above 52.6 GHz up to 71 GHz), a larger SCS may be introduced. If the scalability of the OFDM symbol duration and CP length defined in the current NR system is maintained, lengths as shown in Table 6 below may be defined as the OFDM symbol duration and CP length for each SCS.

[0162] [Table 6]

[0163] Considering the monitoring capability of the terminal in the FR3 (or FR2-2) frequency band, PDCCH monitoring may be performed in one slot per multiple slots. Considering the reduced PDCCH monitoring occasion area, an operation of scheduling multiple PDSCHs and / or multiple PUSCHs by one DCI may be introduced. However, the PDSCH and / or PUSCH indicated by such a DCI may be indicated to be transmitted in another frequency range in addition to FR3 (or FR2-2). That is, the M-DCI proposed in this disclosure is not limited to the NR system operating in FR3 (or FR2-2), and may be applied in other frequency regions.

[0164] Example 1: Time bundling setting method

[0165] Considering the 480 / 960 kHz SCS introduced in the FR3 band, in particular, even if multiple PDSCHs are scheduled in multiple slot regions by M-DCI, the absolute time of multiple PDSCHs may be very short. For this reason, the channel may not change significantly in the time interval (or multiple PDSCHs), and the results of successful / failed decoding of multiple PDSCHs may be the same. Considering this, when a time bundling interval is set, the HARQ-ACK payload can be reduced by bundling (i.e., logical AND operation) the HARQ-ACK results within the interval. Therefore, a specific time bundling method is proposed.

[0166] In other words, when HARQ time bundling is set for a specific serving cell, multiple PDSCHs scheduled on the specific serving cell are grouped into one or more groups (which may be referred to as a bundling group, or HARQ group, or HARQ bundling group, etc.), and HARQ-ACK information may be generated for each of the one or more groups.

[0167] For example, time bundling may be set for the terminal by upper layer signaling (e.g., RRC signaling). The presence or absence of time bundling may be set for each of one or more serving cells set for the terminal. For example, when information for setting time bundling is provided for the serving cell, time bundling may be set / supported for multiple PDSCHs scheduled on the cell. On the other hand, when information for setting time bundling is not provided for the serving cell, time bundling may not be set / supported for multiple PDSCHs scheduled on the cell.

[0168] In the present disclosure, for the sake of convenience of description, the bundling of HARQ-ACK information for multiple PDSCHs is referred to as time bundling, but the present disclosure is not limited thereto, and it may be given other names such as HARQ bundling and HARQ-ACK bundling.

[0169] - Method 1: Propose a time bundling method based on the number of scheduled PDSCHs. That is, multiple PDSCHs may be bundled (grouped) into one or more groups based on a predetermined number of PDSCHs.

[0170] Specifically, for a multi-PDSCH case with M or less PDSCHs (where M is a natural number), the PDSCHs may be bundled into one group, and for a multi-PDSCH case with more than M PDSCHs, the PDSCHs may be bundled into two groups. Here, the value of M may be half of the maximum number of PDSCHs that can be scheduled by the M-DCI set in the cell (or among all cells set in the terminal) (if the value obtained by taking half is not an integer, it may be converted to an integer by floor operation, ceiling operation, rounding, etc.). Alternatively, the value of M may be set 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) may be bundled into group 1, and the remaining N-M PDSCHs may be bundled into group 2. As another method, the first ceil(N / 2) PDSCHs may be bundled into group 1, and the remaining floor(N / 2) PDSCHs may be bundled into group 2.

[0171] - Method 2: Propose a time bundling method based on the number of slots occupied by PDSCHs. That is, multiple PDSCHs are bundled (grouped) into one or more groups based on a predetermined number of PDSCH slots.

[0172] Specifically, for the multiplexed PDSCH case for L or fewer (L is a natural number) slots, the PDSCH may be bundled into one group, and for the multiplexed PDSCH case for more than L slots, the PDSCH may be bundled separately into two groups. Here, the L value may be half of the maximum number of PDSCH slots schedulable by the M-DCI configured for the cell (or among all cells configured for the terminal) (i.e., the maximum value within the slot interval from the first PDSCH slot to the last PDSCH slot). If the value obtained by taking half is not an integer, it may be converted to an integer using floor operation, ceiling operation, rounding operation, etc.). Alternatively, the L value may be set by higher layer signaling. Specifically, when the slot interval from the first actually scheduled PDSCH slot to the last PDSCH slot is K slots (>L), the PDSCH within the first L slot intervals may be bundled into group 1, and the PDSCH within the remaining K - L slot intervals may be bundled into group 2. As another method, the PDSCH within the first ceil(K / 2) slot intervals may be bundled into group 1, and the PDSCH within the remaining floor(K / 2) slot intervals may be bundled into group 2.

[0173] - Method 3: Regardless of the number of PDSCH and the number of slots, multiple PDSCHs may always be time bundled into two groups. When the number of actually scheduled PDSCHs is N, the first ceil(N / 2) PDSCHs may be bundled into group 1, and the remaining floor(N / 2) PDSCHs may be bundled into group 2.

[0174] Alternatively, this can be further extended such that G groups (where G is a natural number) may be configured, and multiple PDSCHs may be time-bundled (or grouped) into G groups. Here, the scheduled (or valid) PDSCHs may be mapped to each group in order (in ascending group index order). In other words, multiple PDSCHs are mapped to each group according to the time order, and such a process may loop and repeat until all PDSCHs are mapped to groups. For example, if 5 PDSCHs are scheduled (or are valid) by one DCI and G = 4, PDSCH #0 / 4 may correspond (map) to group #0, PDSCH #1 to group #1, PDSCH #2 to group #2, and PDSCH #3 to group #3. Here, a valid PDSCH can mean a PDSCH that does not overlap with an uplink (or flexible) symbol (or a slot containing such a symbol) configured by parameters for TDD UL-DL common settings (e.g., tdd-UL-DL-ConfigurationCommon) or parameters for TDD UL-DL dedicated settings (e.g., tdd-UL-DL-ConfigurationDedicated). Here, the terminal can perform a logical AND operation for each bundling group (i.e., HARQ-ACK information may be generated for each bundling group).

[0175] If the PDSCH is mapped to a bundling group in the scheduled PDSCH order (i.e., regardless of the validity of the PDSCH), there may be a mixture of valid and invalid PDSCHs in a specific bundling group (both belonging to it), or only invalid PDSCHs may exist. Here, if there is a mixture of valid and invalid PDSCHs in a specific bundling group (both belonging to it), the terminal can consider the invalid PDSCH as ACK and perform a logical AND operation on the bundling group. However, when only invalid PDSCHs exist in a specific bundling group, the terminal may consider the invalid PDSCH as NACK, or the HARQ-ACK information corresponding to the bundling group may be considered as NACK. For example, in the above illustration, assuming that PDSCH #0 mapped to group #0 is a valid PDSCH and PDSCH #4 is an invalid PDSCH (i.e., both valid and invalid PDSCHs belong to a specific bundling group), the HARQ-ACK information corresponding to PDSCH #4 may be considered as ACK. As another example, in the above illustration, assuming that PDSCH #1 mapped to group #1 is an invalid PDSCH (i.e., only invalid PDSCHs exist in a specific bundling group), the HARQ-ACK information corresponding to PDSCH #1 may be considered as NACK, or the HARQ-ACK information corresponding to group #1 may be considered as NACK.

[0176] For the sake of convenience in explanation, the above Methods 1 to 3 mainly described the case where the number of groups is 2. However, the same methods may be extended and applied when the number of groups is set to be more than 2 or 1.

[0177] The number of bundling groups may be set as proposed in Method 3 above, and specifically, it may be as follows.

[0178] When the number of HARQ - bundling groups (numberOfHARQ - BundlingGroups) is set for the serving cell c by the UE (i.e., when the number of HARQ - bundling groups is set by the RRC parameter), the UE generates HARQ - ACK information for the transport block group (TBG) for PDSCH reception. Here, for the maximum number N of PDSCH receptions scheduled by the DCI format on the serving cell max PDSCH the maximum number N of TBGs TBG,max HARQ-ACK,c is provided by numberOfHARQ - BundlingGroups. When the UE detects a DCI format that schedules N PDSCH,c PDSCH receptions on the serving cell c, the UE sets N CBG / TB,max HARQ-ACK =N TBG,max HARQ-ACK,c and C = N PDSCH,c and generates N PDSCH,c HARQ - ACK information bits for the first TB within the N TBG,max HARQ-ACK,c PDSCH receptions, and generates N TBG,max HARQ-ACK,c HARQ - ACK information bits for the second TB. That is, the bundling group may be generated in the same way as the CBG (code block group) construction as follows.

[0179] When PDSCH - CodeBlockGroupTransmission is set for the serving cell by the UE, the UE receives the PDSCH scheduled by DCI format 1_1 including the CBG of the TB. The UE sets the maximum number of CBGs for generating each HARQ - ACK information bit for the TB reception for the serving cell (i.e., N CBG / TB,max HARQ-ACK ​​​​​​​​​The number of maximum CBGs per transport block (maxCodeBlockGroupsPerTransportBlock) indicating

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

[0181] When the UE correctly receives all the code blocks of a CBG, it generates an ACK for the HARQ-ACK information bits of the CBG. And when the UE incorrectly receives at least one code block of the CBG, it 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 CBGs of the second TB after the HARQ-ACK information bits for the CBGs of the first TB.

[0182] The HARQ-ACK codebook contains N CBG / TB,max HARQ-ACK HARQ-ACK information bits and for a TB, N CBG / TB HARQ-ACK <N CBG / TB,max HARQ-ACK if so, the UE generates NACK values for the last N CBG / TB,max HARQ-ACK -N CBG / TB HARQ-ACK HARQ-ACK information bits for the TB in the HARQ-ACK codebook.

[0183] When the UE generates a HARQ-ACK codebook in response to a retransmission of a TB corresponding to the same HARQ process as a previous transmission of the TB, the UE generates an ACK for each CBG that was correctly decoded in the previous transmission of the TB.

[0184] If the UE correctly detects each of N CBG / TB HARQ-ACK CBGs but N CBG / TBHARQ-ACK If the UE cannot accurately detect the TB for each CBG, it will CBG / TB HARQ-ACK generate a NACK value for each of the CBGs.

[0185] On the other hand, in the generation of a bundling group, as described above, the bundling group may be generated based on a pre-set SLIV associated (linked) with the TDRA information indicated by DCI. Here, when the PDSCHs that are valid and not valid for a specific bundling group are mixed (both belong), or when only non-valid PDSCHs exist, it is necessary to define the HARQ-ACK generation method for the bundling group. Here, a valid PDSCH can mean a PDSCH that does not overlap with the symbol (or the slot including the symbol) configured as uplink (or flexible) by a parameter for TDD UL-DL common configuration (for example, tdd-UL-DL-ConfigurationCommon) or a parameter for TDD UL-DL dedicated configuration (for example, tdd-UL-DL-ConfigurationDedicated). On the other hand, a non-valid PDSCH can mean a PDSCH that overlaps with the symbol (or the slot including the symbol) configured as uplink (or flexible) by a parameter for TDD UL-DL common configuration (for example, tdd-UL-DL-ConfigurationCommon) or a parameter for TDD UL-DL dedicated configuration (for example, tdd-UL-DL-ConfigurationDedicated). If valid and non-valid PDSCHs are mixed in a specific bundling group (both belong), it is preferable that the HARQ-ACK information corresponding to the bundling group generates ACK information when all valid PDSCHs belonging to the bundling group are accurately received, and generates NACK in other cases (that is, when even one of the valid PDSCHs belonging to the bundling group cannot be accurately received). In other words, in the generation of HARQ-ACK information corresponding to the bundling group (to which both valid and non-valid PDSCHs belong),

[0186] Alternative (Alt) 1: Consider (or assume) that non - valid PDSCH is received accurately.

[0187] Alt 2: It is preferred that non - valid PDSCH is ignored.

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

[0189] Alt 1: When the number of HARQ - BundlingGroups (numberOfHARQ - BundlingGroups) is set for the serving cell c to the UE (i.e., when the number of HARQ - BundlingGroups is set by the RRC parameter), the UE generates HARQ - ACK information for the transport block group (TBG) for PDSCH reception. Here, for the maximum number N of PDSCH receptions scheduled by the DCI format on the serving cell max PDSCH the maximum number N of TBGs TBG,max HARQ-ACK,c is provided by numberOfHARQ - BundlingGroups. When the UE detects a DCI format that schedules N PDSCH,c PDSCH receptions on the serving cell c, the UE sets N CBG / TB,max HARQ-ACK = N TBG,max HARQ-ACK,c and C = N PDSCH,c and by assuming that the PDSCH overlapping with the UL symbols indicated by tdd - UL - DL - ConfigurationCommon or tdd - UL - DL - ConfigurationDedicated for the TBG in at least one actual PDSCH reception is received accurately, N PDSCH,c generates N TBG,max HARQ-ACK,c HARQ - ACK information bits for the first TB within N TBG,max HARQ-ACK,c PDSCH receptions and generates N

[0190] Alternative 2: When the number of HARQ - bundling groups (numberOfHARQ - BundlingGroups) is set for the serving cell c in the UE (i.e., when the number of HARQ - bundling groups is set by the RRC parameter), the UE generates HARQ - ACK information for the transport block group (TBG) for PDSCH reception. Here, the maximum number N of PDSCH receptions scheduled by the DCI format on the serving cell max PDSCH For, the maximum number N of TBGs TBG,max HARQ-ACK,c is provided by numberOfHARQ - BundlingGroups. When the UE detects a DCI format that schedules N PDSCH,c PDSCH receptions on the serving cell c, the UE sets N CBG / TB,max HARQ-ACK =N TBG,max HARQ-ACK,c and C = N PDSCH,c By setting as such, and by ignoring the PDSCH that overlaps with the UL symbol indicated by tdd - UL - DL - ConfigurationCommon or tdd - UL - DL - ConfigurationDedicated for the TBG in at least one actual PDSCH reception, within N PDSCH,c PDSCH receptions, N TBG,max HARQ-ACK,c HARQ - ACK information bits for the first TB are generated, and N TBG,max HARQ-ACK,c HARQ - ACK information bits for the second TB are generated.

[0191] Example 2: Type - 1 HARQ - ACK codebook (HCB) configuration method when time bundling is set

[0192] Based on the last PDSCH transmission slot (in terms of time) among the multiple PDSCHs scheduled by the M-DCI, the value of K1 (in this disclosure, K1 means the slot interval between the PDSCH transmission slot and the HARQ-ACK transmission slot for the PDSCH reception) indicated by the DCI may be applied to determine the HARQ-ACK timing (slot). Based on this, the HARQ-ACK feedback for all of the multiple PDSCHs scheduled by the DCI may be transmitted in a batch at the same (identical one) HARQ-ACK timing.

[0193] Thus, HARQ-ACK feedback (for all of the multiple PDSCHs scheduled by the DCI) is multiplexed (that is, HARQ-ACK information bits within one codebook are included) only between the M-DCI indicating the same slot as the HARQ-ACK time (slot) corresponding to the last PDSCH transmission slot and the S-DCI indicating the same slot as the HARQ-ACK time (slot) corresponding to the last PDSCH transmission slot, and may be transmitted at the same one HARQ-ACK time.

[0194] On the one hand, when it is an existing Type-1 HCB with a set of K1 values for a plurality (e.g., K_N) of candidates, the terminal calculates, for each K1 value (for each serving cell, for the K1 values set for that cell), the combination of all PDSCH opportunities (SLIV) that can be transmitted within the DL slots K1 slots before the HARQ-ACK transmission slot. Then, the terminal constructs an opportunity for receiving a candidate PDSCH (including determining the HARQ-ACK bit position / order corresponding to each SLIV) corresponding to each DL slot (this is defined as "SLIV pruning"). For each opportunity included in the set of opportunities for receiving a candidate PDSCH obtained from such a process, HARQ-ACK information bits are constructed, and the overall HARQ-ACK codebook can be constructed by concatenating each HARQ-ACK information bit.

[0195] In other words, after setting a plurality of candidate HARQ timings by RRC signaling in advance, the base station can indicate one of the plurality of candidate HARQ timings to the terminal by (DL grant) DCI. In this case, the terminal can operate to transmit A / N feedback for (multiple) PDSCH receptions in a plurality of slots (or a set of slots) corresponding to the entire candidate HARQ timing set at the indicated HARQ timing. Here, the HARQ timing means the PDSCH-to-A / N timing / interval. The HARQ timing may be expressed in slot units. For example, when the A / N transmission is indicated to be in slot #m, the A / N information may include response information for PDSCH reception in slot #(m-i). Here, slot #(m-i) corresponds to the slot corresponding to the candidate HARQ timing. Here, when the candidate HARQ timing is set to i = {2, 3, 4, 5} and the A / N transmission time point is indicated to be #(n + 5) (= m), the terminal can generate / transmit A / N information for PDSCH reception in slots #n to #(n + 3) (= m - i) (that is, A / N feedback for all of the 4 slots). Here, the A / N response for PDSCH reception in slot #n + 1 / #n + 3 may be processed as NACK.

[0196] Referring to a part of the standard related to this, it is as follows.

[0197] In the serving cell c, the activated DL BWP, and the activated UL BWP, the UE determines a set of M U opportunities for candidate PDSCH receptions for which the HARQ-ACK information can be transmitted in the PUCCH in slot n. When the serving cell c is deactivated, the DL BWP provided by firstActiveDownlinkBWP-Id is used as the activated DL BWP for determining the set of M A,C opportunities for candidate PDSCH receptions. The determination is based on the following: A,C

[0198] a) The determination is based on a set of slot timing values K1 associated with the activated UL BWP.

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

[0200] - If the UE is configured to monitor the PDCCH for DCI format 1_1 on serving cell c and is not configured to monitor the PDCCH for DCI format 1_2, K1 is provided by dl-DataToUL-ACK.

[0201] - If the UE is configured to monitor the PDCCH for DCI format 1_2 on serving cell c and is not configured to monitor the PDCCH for DCI format 1_1, K1 is provided by dl-DataToUL-ACK-ForDCIFormat1_2.

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

[0203] b) The determination is associated with the activated DL BWP and is based on a set of row indices R of a table that defines each set of the slot offset K0 and the SLIV (start and length indicator), and the PDSCH mapping type for PDSCH reception. Here, the row index R of the table is provided as the union of the row indices of the time domain resource allocation table for the DCI format configured for the UE to monitor the PDCCH for the serving cell c.

[0204] - When the referenceOfSLIVDCI-1-2 is provided to the UE, at each row index having the slot offset K0 = 0 and the PDSCH mapping type B within the set of row indices of the table for the DCI format 1_2, where the start symbol S0 > 0 and the PDCCH monitoring occasions within the set of PDCCH monitoring occasions having different start symbols from each other within the slot for monitoring the PDCCH for the DCI format 1_2, if S + S0 + L ≤ 14 for the normal cyclic prefix and S + S0 + L ≤ 12 for the extended cyclic prefix, the UE replaces the start symbol S of the row index with S + S0 within the set of row indices of the table and adds a new row index.

[0205] In this embodiment, a type-1 HCB configuration method is proposed when time bundling is set as in Embodiment 1 above.

[0206] First, SLIV pruning may be performed based only on the last SLIV in each row of the TDRA table. That is, the set of occasions for candidate PDSCH receptions capable of transmitting the HARQ-ACK information within PUCCH in a specific slot may be determined based only on the last SLIV in each row in the TDRA table. For example, in the TDRA table, one or more rows may have multiple SLIV values indicated for scheduling multiple PDSCHs. For example, it may be set / defined as row index 2: {SLIV1, SLIV2, SLIV3}, row index 3: {SLIV4, SLIV5}. In this case, the set of occasions for candidate PDSCH receptions may be determined based only on the last SLIV in each row in the TDRA table. That is, considering only row index 2: {SLIV3} and row index 3: {SLIV5}, the set of occasions for candidate PDSCH receptions may be determined.

[0207] For each DL slot corresponding to each K1 within a set of multiple candidate K1 values (i.e., when HARQ-ACK is transmitted in slot n, slot n - K1), after SLIV pruning is performed, if HARQ-ACK transmission for one or more of the TDRA row indices corresponding to the K1 is required for G groups, the number of occasions by (G - 1) may be added to the SLIV pruning result. As an example, if G = 1, occasions may not be added to the SLIV pruning result.

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

[0209] - Row index #0: Five SLIV values are associated, and the last SLIV = {S = 0, L = 5}

[0210] - Row index #1: 3 SLIV values are linked, and the last SLIV = {S = 2, L = 5}

[0211] Also, the TDRA entry for S-DCI in the cell may be as follows.

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

[0213] For the cell, when SLIV pruning (i.e., determination of the set of opportunities for candidate PDSCH reception) for a specific DL slot corresponding to a specific K1 is performed based only on the last SLIV, the number of opportunities for receiving candidate PDSCH in the DL slot may be allocated 2 (for example, 1 opportunity for candidate PDSCH reception by M-DCI and 1 opportunity for candidate PDSCH reception by S-DCI).

[0214] Suppose that two groups for two-time bundling are set as in Method 1 of Example 1 above and M = 4 is set. In this case, when row index #0 is indicated by M-DCI, a total of 5 PDSCHs are scheduled, so the PDSCHs may be bundled into 2 groups. On the other hand, when row index #1 is indicated by M-DCI, a total of 3 PDSCHs are scheduled, so the PDSCHs may be bundled into 1 group.

[0215] In this case, since at least two groups are required for row index #0, the final DL slot may have three opportunities for receiving candidate PDSCHs (for example, two opportunities for candidate PDSCH reception by M-DCI (for each group), and one opportunity for PDSCH reception by S-DCI). If, actually, row index #0 or 1 of M-DCI is scheduled, HARQ-ACK information may correspond to the first two opportunities in this opportunity. Here, in the case of row index #1, since there is no PDSCH corresponding to the second group, it may be filled with NACK. And when row index #0 of S-DCI is scheduled, HARQ-ACK information may correspond to the third opportunity. That is, HARQ-ACK information may first correspond to the opportunity for candidate PDSCH reception by M-DCI, and then to the opportunity for candidate PDSCH reception by S-DCI.

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

[0217] - Row index #0: Five SLIV values are associated, and the last SLIV = {S = 9, L = 5}

[0218] - Row index #1: Three SLIV values are associated, and the last SLIV = {S = 10, L = 4}

[0219] Also, the TDRA entry for S-DCI in the cell may be as follows.

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

[0221] When SLIV pruning (i.e., determination of a set of occasions for candidate PDSCH reception) is performed for a specific DL slot corresponding to a specific K1 for the cell based only on the last SLIV, two opportunities for receiving candidate PDSCHs (for example, one opportunity for candidate PDSCH reception by M-DCI and one opportunity for candidate PDSCH reception by S-DCI) may be allocated to the DL slot.

[0222] Assume that, as in Method 1 of Example 1 above, a group for two time bundlings is set and M = 4 is set. In this case, when row index #0 is indicated by M-DCI, a total of five PDSCHs are scheduled, so the PDSCHs may be bundled into two groups. On the other hand, when row index #1 is indicated by M-DCI, a total of three PDSCHs are scheduled, so the PDSCHs may be bundled into one group.

[0223] In this case, since at least two groups are required for row index #0, the number of opportunities for receiving candidate PDSCHs in the final DL slot may be three (for example, two opportunities for candidate PDSCH reception by M-DCI (for each group) and one opportunity for PDSCH reception by S-DCI). If the row index #0 or 1 of M-DCI is actually scheduled, HARQ-ACK information may correspond to the first and third opportunities within the opportunity. Here, in the case of row index #1, the third opportunity may be filled with NACK (since there is no PDSCH corresponding to the second group). When the row index #0 of S-DCI is scheduled, HARQ-ACK information may correspond to the second opportunity. That is, according to SLIV pruning performed based only on the last SLIV, an opportunity is first allocated to row index #0 for S-DCI, and then the row index #0 / 1 for M-DCI is allocated to the next opportunity, so a total of two opportunities may be configured. Here, furthermore, opportunities by time bundling may be configured before the two opportunities, and a total of three opportunities may be allocated to the DL slot. In other words, HARQ-ACK information corresponds to the opportunity for candidate PDSCH reception by S-DCI, and then HARQ-ACK information corresponds to the opportunity for candidate PDSCH reception by M-DCI. If there is an opportunity by time bundling in the opportunity for candidate PDSCH reception by M-DCI, HARQ-ACK information may correspond first.

[0224] Example 3: Method for configuring type-1 HCB when slot-group based PDCCH monitoring is set

[0225] The introduction of a higher SCS such as 480 / 960 kHz SCS may impose a burden on the terminal implementation in performing PDCCH monitoring every slot. Considering this, slot-group based PDCCH monitoring may be introduced.

[0226] FIG. 10 is a diagram illustrating slot group-based PDCCH monitoring according to an embodiment of the present disclosure.

[0227] Referring to FIG. 10, four slots (i.e., Gr = 4) are defined as one slot group, and PDCCH monitoring may be restricted only in a partial area (e.g., the first slot) within the slot group. Such a slot group may be predefined (for each SCS), set by upper layer signaling, or a value derived by the terminal from a search space set configuration. Also, the slot group may be used as a reference for calculating the maximum number of PDCCH candidates and / or the maximum number of non-overlapped control channel elements (CCEs), or may be utilized as a reference for dropping a search space set based on the number criteria.

[0228] According to this embodiment, for the cell, SLIV pruning may be performed on the entire slot group instead of on a specific DL slot corresponding to a specific K1. Here, for a multi-PDSCH case having a specific slot in the slot group as the first PDSCH slot, a scheduling restriction that is scheduled only within the same slot group may be set / defined. That is, for a multi-PDSCH case having a specific slot in the n-th slot group as the first PDSCH slot, all PDSCHs scheduled by the corresponding M-DCI must belong within the n-th slot group, and a constraint is required that no single PDSCH may be scheduled to belong to the (n + 1)-th slot group. That is, when multiple PDSCHs (multi-PDSCH) are scheduled by M-DCI, all of the multiple PDSCHs need to be scheduled within a single slot group.

[0229] Specifically, SLIV pruning may be performed on the entire slot belonging to the slot group where the slot indicated by each K1 becomes the last slot for each K1.

[0230] FIG. 11 is a diagram illustrating the determination of a set of opportunities for candidate PDSCH reception according to an embodiment of the present disclosure.

[0231] Referring to FIG. 11, slot #9 is a UL slot where HARQ-ACK is transmitted, the K1 set = {2, 3, 4, 5, 6, 7}, and when the TDRA entry for M-DCI is set as row indices #0, #1, #2, etc., it is an example of SLIV pruning corresponding to slot group #1. When K1 = 2, the corresponding slot #7 belongs to slot group #1, so SLIV pruning may be performed on the entire K1 = 2 / 3 / 4 / 5 corresponding to the slot group #1. That is, the row indices corresponding to each of K1 = 2 / 3 / 4 / 5 may be arranged as shown in FIG. 11 (under the scheduling restriction). The SLIV pruning process may be performed on the entire 9 SLIV arrays corresponding to slot group #1 (replacing the existing slots with slot groups and for the entire 56 symbols within the slot group). As a result, 4 opportunities may be allocated to the slot group #1. If M-DCI actually schedules PDSCH from slot #5 to 3 with row index #0, the second / third / fourth opportunities of the opportunities may correspond to each PDSCH.

[0232] Embodiment 4: Type-2 HCB configuration method considering M-DCI

[0233] In the existing S-DCI, the counter DAI (C-DAI: counter-DAI) and the total DAI (T-DAI: total-DAI) are each counted by 1 for each DCI or for each PDSCH. On the other hand, in the M-DCI, since there may be multiple PDSCHs corresponding to one DCI, the method of counting the DAI value may be different, and the following methods may be considered.

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

[0235] - Alt 2: Count DAI (C-DAI and T-DAI) for each PDSCH

[0236] Here, if at least one symbol of a specific PDSCH among the scheduled multiple PDSCHs overlaps with the UL symbol set by the upper layer (e.g., RRC) signaling, the PDSCH may not be transmitted. In this case, the DAI for the PDSCH may be omitted without counting.

[0237] - Alt 3: Count the DAI value for every W (W is a natural number) PDSCHs, where the W value may be set by the upper layer (e.g., RRC) signaling (or may be a fixed value in advance).

[0238] Here, when M-DCI is set for multiple cells within the same cell group, the W value is preferably set to a common value for these cells. This is because by aligning the HARQ-ACK configuration units between cells, ambiguity can be eliminated even if a specific DCI is missing.

[0239] Next, for each alternative in this embodiment, a method for configuring C-DAI / T-DAI signaling, HARQ-ACK payload size, and HCB (HARQ-ACK codebook) when CBG is further set will be proposed.

[0240] Also, for each alternative, a method for constructing a single codebook (CB) and a method for constructing individual sub-codebooks (sub-CBs), that is, HARQ-ACK sub-codebooks, for single PDSCH cases and multi-PDSCH cases will be proposed separately.

[0241] In this disclosure, constructing an individual sub-CB can mean that C / T-DAI values are determined and signaled independently for each sub-CB (that is, the order / sum of DCIs / PDSCHs scheduled for each sub-CB is determined / signaled independently). That is, the C-DAI value and the T-DAI value may be applied individually to each HARQ-ACK sub-codebook.

[0242] For example, constructing individual sub-CBs for single PDSCH cases and multi-PDSCH cases can mean a structure in which C / T-DAI values are determined and signaled independently for each of the single PDSCH case and the multi-PDSCH case (that is, the order / sum of DCIs / PDSCHs scheduled for each case is determined / signaled independently). In other words, the DCI corresponding to the single PDSCH case may determine and signal the DAI value only for the single PDSCH case, and the DCI corresponding to the multi-PDSCH case may determine and signal the DAI value only for the multi-PDSCH case. Also, HARQ-ACK payloads corresponding to different sub-CBs may be concatenated to form the final HCB (HARQ-ACK codebook).

[0243] On the one hand, the formation of a single CB can mean a structure where the common C / T-DAI value is determined and signaled as before (i.e., the order / sum of DCI / PDSCH scheduled for a single CB is commonly determined / signaled). For example, the formation of a single CB for a single PDSCH case and a multi-PDSCH case can mean a structure where the C / T-DAI value is counted and signaled by bundling (grouping together) the single PDSCH case and the multi-PDSCH case (i.e., the order / sum of DCI / PDSCH scheduled without distinction for each case is determined / signaled).

[0244] Example 4-1: DAI count by DCI (i.e., Alt1 in Example 4 described above) + single HARQ-ACK CB (codebook) formation

[0245] The terminal can form / generate one CB for a single PDSCH case and a multi-PDSCH case.

[0246] - M-DCI: The existing DL DAI size (i.e., 2 bits for each of C / T-DAI) may be maintained.

[0247] - S-DCI: The existing DL DAI size may be maintained.

[0248] - UL grant: The existing UL DAI size (i.e., 2 bits for T-DAI) may be maintained.

[0249] - HARQ-ACK Payload: It may be determined by the maximum number of PDSCHs (Y) (Y is a natural number) that can be scheduled by the M-DCI. For example, if 2TB is configured (i.e., PDSCH reception carrying two transport blocks in the serving cell is configured or the number of transport blocks (or codewords) that can be scheduled at most by one DCI is set to 2), for a cell where spatial bundling for HARQ-ACK information is not configured, it may be calculated as 2 bits per PDSCH. For a cell where 2TB is configured but spatial bundling is configured, or a cell where 1TB is configured, it may be calculated as 1 bit per PDSCH.

[0250] As another example, when there are X bits per PDSCH (as described above, for a cell where 2TB is configured and spatial bundling for HARQ-ACK information is not configured, X = 2 may be used. For a cell where 2TB is configured but spatial bundling is configured, or a cell where 1TB is configured, X = 1 may be used.), the number of HARQ-ACK bits corresponding to one DAI may be X * Y for both the single PDSCH case and the multiple PDSCH case. If M-DCI is configured for multiple cells (within one cell group), the number of HARQ-ACK bits per DAI may be determined by the maximum X * Y value among any cells. That is, it may be determined by the maximum X * Y value among the X * Y values calculated for each cell in the cell group.

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

[0252] 1) Option 1: The terminal can configure / generate individual sub-CBs. That is, in the case of scheduling TB-based PDSCH in a single PDSCH case and for a multi-PDSCH case, one sub-CB may be configured. And for CBG-based PDSCH scheduling in a single PDSCH case, another sub-CB may be configured.

[0253] - When CBG is set in the cell where M-DCI is set, in a single PDSCH case, the DAI in the M-DCI can indicate the C / T-DAI value for the CBG-based PDSCH. When CBG is not set in the cell where M-DCI is set, in a single PDSCH case, the DAI in the M-DCI can indicate the C / T-DAI value for the TB-based PDSCH.

[0254] - S-DCI or M-DCI: The existing DL DAI size may be maintained.

[0255] - UL grant: 2 bits of T-DAI (for the sub-CB for CBG) may be further required for the existing UL DAI size.

[0256] - HARQ-ACK payload: When scheduling TB-based PDSCH in a single PDSCH case and for the payload of one sub-CB configured for a multi-PDSCH case, it may be configured / determined in the same way as in the above Example 4-1. Also, for the payload of another sub-CB configured for CBG-based PDSCH scheduling in a single PDSCH case, it may be the same as the existing CBG-based sub-CB configuration.

[0257] 2) Option 2: One single sub-CB may be configured. That is, in the case of scheduling TB-based or CBG-based PDSCH in a single PDSCH case and for a multi-PDSCH case, one sub-CB may be configured.

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

[0259] - S-DCI or M-DCI or UL grant: Similar to Example 4-1 above, the DAI size may be maintained.

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

[0261] Example 4-1b: When DCI-specific DAI counting (i.e., Alt 1 in Example 4 above) + single HARQ-ACK CB (codebook) configuration + time bundling are set

[0262] Similar to Example 1 above, when time bundling is set for one or more serving cells (all or part) configured for the terminal, a type-2 HCB configuration is proposed.

[0263] - M-DCI or S-DCI or UL grant: Similar to Example 4-1 above, the DAI size may be maintained.

[0264] - HARQ-ACK payload: The HARQ-ACK payload size may be determined by the (maximum) number of groups (G) (G is a natural number) set for time bundling.

[0265] For example, the number of HARQ-ACK bits corresponding to one DAI may be G (or X*G) for both the single PDSCH case and the multiple PDSCH cases (e.g., depending on whether there is a 2TB setting in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or codewords) that can be scheduled maximally by one DCI), the X value may be 2 or 1. As another example, for a cell with 2TB set and no spatial bundling for HARQ-ACK information, X = 2 may be applicable. For a cell with 2TB set but spatial bundling set, or a cell with 1TB set, X = 1 may be applicable.).

[0266] If M-DCI is set for multiple cells, the HARQ-ACK bit number for each DAI may be determined by the maximum G (or X*G) value among any cells (within one cell group). That is, G (or X*G) may be compared for each cell within the cell group, and the HARQ-ACK bit number for each DAI may be determined based on the maximum G (or X*G) value.

[0267] If there is no PDSCH corresponding to a specific time bundling group (especially when the G value is 2 or more), NACK may be mapped. As an example, if G = 1, the number of HARQ-ACK bits corresponding to one DAI may be 1 (or X) for both the single PDSCH case and the multiple PDSCH cases (for example, depending on whether there is a 2TB setting in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or codewords) that can be maximally scheduled by one DCI), the X value may be 2 or 1). As yet another example, for a cell where 2TB is set and spatial bundling for HARQ-ACK information is not set, X = 2 may be used. For a cell where 2TB is set but spatial bundling is set, or a cell where 1TB is set, X = 1 may be used). Alternatively, if G = 1 is set for all cells (within the same PUCCH cell group) where M-DCI is set, a single CB may be configured for both the single PDSCH case and the multiple PDSCH cases.

[0268] When time bundling is set as in the method, the terminal can configure / generate a single CB for both the single PDSCH case and the multiple PDSCH cases. In this case, when CBG is set for a specific serving cell within the same PUCCH group, separate sub-CBs may be configured. In other words, as in Option 1 of Example 4-1a, when scheduling TB-based PDSCH in the single PDSCH case and for the multiple PDSCH cases (where time bundling is set), one sub-CB may be configured. And for CBG-based PDSCH scheduling in the single PDSCH case, other sub-CBs may be configured. In this case, the specific DCI and HARQ-ACK payload configuration methods may be as follows.

[0269] - When CBG is configured for a cell with M-DCI configured, in the single PDSCH case, the DAI in the M-DCI can indicate the C / T-DAI value for the CBG-based PDSCH. When CBG is not configured for a cell with M-DCI configured, in the single PDSCH case, the DAI in the M-DCI can indicate the C / T-DAI value for the TB-based PDSCH.

[0270] - S-DCI or M-DCI: The existing DL DAI size may be maintained.

[0271] - UL grant: 2 bits of T-DAI (for sub-CBs for CBG) may be further required for the existing UL DAI size.

[0272] - HARQ-ACK payload: In the single PDSCH case, when scheduling the TB-based PDSCH and for the payload of one sub-CB configured for the multiple PDSCH case, it may be the same as when CBG is not configured in the above Example 4-1b (i.e., the number of HARQ-ACK bits corresponding to one DAI may be G or X*G for both the single PDSCH case and the multiple PDSCH case (e.g., depending on whether 2TB is configured in the serving cell (i.e., whether PDSCH reception carrying 2 transport blocks is configured, or the number of transport blocks (or codewords) that can be maximally scheduled by one DCI), the X value may be 2 or 1. As another example, for a cell with 2TB configured and no spatial bundling configured for HARQ-ACK information, X = 2 may be applicable. For a cell with 2TB configured but spatial bundling configured, or a cell with 1TB configured, X = 1 may be applicable.). The payloads of other sub-CBs configured for CBG-based PDSCH scheduling in the single PDSCH case may be the same as the existing CBG-based sub-CB configuration.

[0273] Alternatively, when both M-DCI and CBG are configured within the same PUCCH group, rules may be configured such that time bundling is automatically applied to the multi-PDSCH case (where the G value may be predefined (e.g., G = 1) or set by the base station). Here, it may be defined / set to be composed of a single CB for both the single-PDSCH case and the multi-PDSCH case.

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

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

[0276] - M-DCI: The existing DL DAI size (i.e., 2 bits each for C / T-DAI) may be maintained.

[0277] - S-DCI: The existing DL DAI size may be maintained.

[0278] - UL grant: An additional 2 bits of T-DAI (for the additional sub-CB) may be required for the existing UL DAI size.

[0279] - HARQ-ACK Payload: For a single PDSCH case, the number of HARQ-ACK bits for each sub-CB DAI corresponding to it may be X (for example, based on whether there is a 2TB setting in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or codewords) that can be scheduled maximally by one DCI), the X value may be 2 or 1. As another example, for a cell with 2TB set and no spatial bundling for HARQ-ACK information, X may be 2. For a cell with 2TB set but spatial bundling set, or a cell with 1TB set, X may be 1.). For a multi-PDSCH case, the number of HARQ-ACK bits for each sub-CB DAI corresponding to it is the maximum X*Y value among any cells (within one cell group). That is, it may be determined as the maximum X*Y value among the X*Y values calculated for each cell within the cell group.

[0280] Example 4-2a: When DAI count by DCI (i.e., Alt 1 in Example 4 above) + individual HARQ-ACK sub-CB configuration + CBG is set

[0281] 1) Option 1: The terminal can configure / generate individual sub-CBs (i.e., when scheduling a TB-based PDSCH in a single PDSCH case, the first sub-CB is configured, for a multi-PDSCH case, the second sub-CB is configured, and for CBG-based PDSCH scheduling by a single PDSCH case, the third sub-CB may be configured).

[0282] - When CBG is set in a cell with M-DCI set, in a single PDSCH case, the DAI in the M-DCI can indicate the C / T-DAI value for the CBG-based PDSCH. When CBG is not set in a cell with M-DCI set, in a single PDSCH case, the DAI in the M-DCI can indicate the C / T-DAI value for the TB-based PDSCH.

[0283] - S-DCI or M-DCI: The existing DL DAI size may be maintained.

[0284] - UL grant: Four bits of T-DAI may be further required for the existing UL DAI size (for two additional sub-CBs) (i.e., two bits of T-DAI are added for each sub-CB).

[0285] - HARQ-ACK payload: When scheduling a TB-based PDSCH in a single PDSCH case, the payload of the first sub-CB may be the same as the sub-CB corresponding to the single PDSCH case in Example 4-2 above. The payload of the second sub-CB configured for multiple PDSCH cases may be the same as the sub-CB corresponding to the multiple PDSCH cases in Example 4-2 above. The payload of the third sub-CB configured for CBG-based PDSCH scheduling in a single PDSCH case may be the same as the existing CBG-based sub-CB configuration.

[0286] 2) Option 2: The terminal can configure / generate a first sub-CB for TB-based PDSCH scheduling in a single PDSCH case and configure / generate a second sub-CB that integrates CBG-based PDSCH scheduling for multiple PDSCH cases and single PDSCH cases.

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

[0288] - S-DCI or M-DCI or UL grant: It may be the same as in Example 4-2 above.

[0289] - HARQ-ACK Payload: If the set maximum number of CBGs is C (C is a natural number), the payload size may be configured / determined by the maximum value between the maximum C value (max_C) among any cells (within one cell group) and the maximum X*Y value (max_XY) among any cells (within one cell group) derived according to the above Example 4-2. That is, the number of HARQ-ACK bits corresponding to the second sub-CB DAI may be max{max_C, max_XY} for both the single PDSCH case and the multi-PDSCH case. Also, the number of HARQ-ACK bits for each first sub-CB DAI may be X (X = 1 or 2 depending on the number of TBs and the spatial bundling setting as described above).

[0290] 3) Option 3: It may not be allowed for M-DCI and CBG to be simultaneously (both) configured within the same PUCCH group. Or, when a type-1 HARQ-ACK CB is configured for a cell where M-DCI is configured (or when a type-2 HARQ-ACK CB is not configured for the cell), CBG configuration may be allowed for other cells (not the cell in question) within the same PUCCH group.

[0291] The above Option 1 and / or Option 2 may be supported as optional UE features, and may be defined / set to operate in Option 3 as the default for terminals that do not support Option 1 and / or Option 2. That is, for terminals that do not support Option 1 and / or Option 2, it can be expected that M-DCI and CBG are not simultaneously (both) configured within the same PUCCH group.

[0292] For a terminal that supports both Option 1 and Option 2 above, it may be set by upper layer signaling (e.g., RRC signaling, MAC CE, etc.) as to which method of Option 1 and Option 2 to apply. Alternatively, based on the size between the maximum number of CBGs (i.e., the aforementioned max_C) and the maximum number of PDSCHs or TBs (i.e., the aforementioned max_XY), it may be determined which of Option 1 or Option 2 to apply, thereby preventing the overall codebook size from increasing significantly. For example, if the max_C value and the max_XY value are the same, even if the same CB is configured, the increase in the codebook size is not large, so Option 2 is applied; otherwise, Option 1 may be applied. As yet another example, if the difference between the max_C value and the max_XY value is less than or equal to K (the K value may be predefined (e.g., K = 4) or may be set by upper layer signaling), Option 2 may be applied; otherwise, Option 1 may be applied.

[0293] Example 4 - 2b: When DAI count per DCI (i.e., Alt 1 in Example 4 above) + individual HARQ - ACK sub - CB configuration + time bundling are set

[0294] Propose a type - 2 HCB configuration when time bundling is set for one or more serving cells (all or part) configured for the terminal as in Example 1 above.

[0295] - M - DCI or S - DCI or UL grant: Similar to Example 4 - 1 above, the DAI size may be maintained.

[0296] - HARQ - ACK payload for sub - CBs corresponding to the multi - PDSCH case: It may be determined by the (maximum) number of groups (G) (G is a natural number) set for time bundling.

[0297] For example, the number of HARQ-ACK bits corresponding to one DAI may be G (or, X*G) (for example, depending on whether 2TB is set in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or, codewords) that can be scheduled at most by one DCI), the X value may be 2 or 1. As another example, for a cell where 2TB is set and spatial bundling for HARQ-ACK information is not set, X = 2 may be used. For a cell where 2TB is set but spatial bundling is set, or a cell where 1TB is set, X = 1 may be used.).

[0298] If M-DCI is set for a plurality of cells, the number of HARQ-ACK bits for each DAI may be determined by the maximum G (or, X*G) value among any cells (within one cell group). That is, G (or, X*G) may be compared for each cell within the cell group, and the number of HARQ-ACK bits for each DAI may be determined based on the maximum G (or, X*G) value.

[0299] If there is no PDSCH corresponding to a specific time bundling group, NACK may be mapped. Here, for a cell where M-DCI is set but time bundling is not set, the G value may be replaced by the maximum number of PDSCHs (Y) (Y is a natural number) that the M-DCI can schedule.

[0300] In other words, among a plurality of cells where M-DCI is set (within the same one PUCCH cell group), for cells where time bundling is not set or where time bundling is set and a G value greater than 1 (= the number of PDSCH groups performing time bundling) is set, the number of HARQ-ACK bits for each DAI (for example, the number of HARQ-ACK bits corresponding to one DCI or one DAI value when configuring the HARQ-ACK codebook) may be determined by the maximum value among the Q values calculated for each cell.

[0301] Here, the Q value may be calculated as the product of the maximum number of PDSCHs schedulable by the M-DCI and X in the case of a cell where the M-DCI is set but time bundling is not set (for example, based on whether 2TB is set in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or codewords) that can be maximally scheduled by one DCI), the X value may be 2 or 1. As another example, for a cell where 2TB is set and spatial bundling for HARQ-ACK information is not set, X = 2 may be used. For a cell where 2TB is set but spatial bundling is set, or a cell where 1TB is set, X = 1 may be used.).

[0302] Alternatively, the Q value may be calculated as the product of G and X in the case of a cell where the M-DCI is set and time bundling is set with a G value greater than 1 (for example, based on whether 2TB is set in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or codewords) that can be maximally scheduled by one DCI), the X value may be 2 or 1. As another example, for a cell where 2TB is set and spatial bundling for HARQ-ACK information is not set, X = 2 may be used. For a cell where 2TB is set but spatial bundling is set, or a cell where 1TB is set, X = 1 may be used.).

[0303] - HARQ-ACK payload for sub-CB corresponding to a single PDSCH case: The number of HARQ-ACK bits per sub-CB DAI corresponding to a single PDSCH case is X (e.g., based on whether 2TB is configured in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is configured, or the number of transport blocks (or codewords) that can be maximally scheduled by one DCI), the value of X may be 2 or 1. As another example, for a cell with 2TB configured and no spatial bundling for HARQ-ACK information, X = 2 may be applicable. For a cell with 2TB configured but spatial bundling set, or a cell with 1TB configured, X = 1 may be applicable.).

[0304] If G = 1 is set for any of the cells with M-DCI configured, the HARQ-ACK bits corresponding to the M-DCI of that cell may be carried on the sub-CB corresponding to a single PDSCH case (e.g., based on whether 2TB is configured in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is configured, or the number of transport blocks (or codewords) that can be maximally scheduled by one DCI), the value of X may be 2 or 1. As another example, for a cell with 2TB configured and no spatial bundling for HARQ-ACK information, X = 2 may be applicable. For a cell with 2TB configured but spatial bundling set, or a cell with 1TB configured, X = 1 may be applicable.). That is, one CB may be configured for the multiple PDSCH cases of a cell where a single PDSCH case and M-DCI are configured and G = 1 is set.

[0305] On the other hand, in the DAI signaling using DCI and the configuration of the HARQ-ACK codebook, independent DAI signaling is performed between the following two PDSCH types (i.e., C-DAI and T-DAI are individually applied to the HARQ-ACK sub-codebooks), and individual HARQ-ACK sub-codebooks may be configured.

[0306] - PDSCH Type 1: M-DCI-based PDSCH transmissions without time bundling (i.e., PDSCH scheduled on one or more cells with M-DCI-based scheduling configured but without time bundling), and M-DCI-based PDSCH transmissions with a G (= number of PDSCH groups for time bundling) value greater than 1 configured (i.e., PDSCH scheduled on one or more cells with M-DCI-based scheduling configured and a G value greater than 1 configured as time bundling)

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

[0308] In other words, in relation to the PDSCH type 1, for the PDSCH scheduled on one or more first serving cells where i) M-DCI based scheduling is set but time bundling is not set, or ii) M-DCI based scheduling is set and a G value greater than 1 is set for time bundling, a first HARQ-ACK sub-codebook may be generated. Also, in relation to the PDSCH type 2, for the PDSCH scheduled on one or more second serving cells where i) M-DCI based scheduling is set and G = 1 for time bundling is set, or ii) M-DCI based scheduling is not set, a second HARQ-ACK sub-codebook may be generated. Here, the plurality of serving cells set for the terminal may correspond to the sum of the one or more first serving cells and the one or more second serving cells.

[0309] In this case, individual (UL) DAI fields / information for each of the PDSCH types 1 and 2 may be configured / indicated in the UL DCI. If there is no PDSCH type 1 as described above, DAI signaling may be performed only for the PDSCH type 2, a HARQ-ACK codebook may be configured only for the PDSCH type 2, and only the UL DAI field / information for the PDSCH type 2 may be configured / indicated in the UL DCI.

[0310] Alternatively, independent DAI signaling may be performed between the following two PDSCH types, and individual HARQ-ACK sub-codebooks may be configured. The following Y value may be set / stipulated to 2.

[0311] - PDSCH type 1: M-DCI based PDSCH transmission where the Q value exceeds Y

[0312] - PDSCH type 2: M-DCI based PDSCH transmission where the Q value is less than or equal to Y, M-DCI based PDSCH transmission with G = 1 set, and existing S-DCI based PDSCH transmission

[0313] In this case, individual UL DAI fields / information for each of PDSCH types 1 and 2 may be configured / indicated in the UL DCI. If there is no PDSCH type 1 as described above, DAI signaling is performed only for PDSCH type 2, a HARQ-ACK codebook is configured, and only the UL DAI field / information for PDSCH type 2 may be configured / indicated in the UL DCI.

[0314] Example 4-3: DAI count per PDSCH (i.e., Alt 2 of Example 4 above) + single HARQ-ACK CB (codebook) configuration

[0315] The terminal can configure / generate one CB for both a single PDSCH case and a multiple PDSCH case.

[0316] - M-DCI: It may increase by ceiling{log2(maximum value among N_max values for each CC (or BWP) set within the same cell group)} for the existing DL DAI size (i.e., 2 bits each for C / T-DAI). Here, N_max is the maximum number of PDSCHs schedulable by M-DCI for a specific cell.

[0317] - S-DCI: It may increase by ceiling{log2(maximum value among N_max values for each CC (or BWP) set within the same cell group)} for the existing DL DAI size. Here, N_max is the maximum number of PDSCHs schedulable by M-DCI for a specific cell.

[0318] Here, assume that A is ceiling{log2(maximum value among N_max values for each CC (or BWP) set within the same cell group)}, which is the DAI increase amount. Once the DL DAI of the fallback DL DCI (i.e., DCI format 1_0) is maintained at 2 bits as before, a method of expanding the interval of the indicated DAI value by 2^A may be considered. This is because from the perspective of the reliability of the fallback DL DCI, it is not preferable to increase the DCI size. For example, when the above DAI increase amount is 2 bits, 2^A = 4, so the 2-bit DAI values indicated by the fallback DCI may be scaled by 2^A, i.e., {4, 8, 12, 16} instead of {1, 2, 3, 4}. Thus, if the previous C-DAI value is 5 and the C-DAI value indicated by the fallback DL DCI is 8, the terminal may map the HARQ-ACK information corresponding to C-DAI = 6, 7 to NACK.

[0319] Alternatively, assume A as ceiling{log2(maximum value among N_max values for each CC (or BWP) set within the same cell group) which is the DAI increase amount. Once the DL DAI of the fallback DL DCI (i.e., DCI format 1_0) is maintained at 2 bits as before, the counting step of the DAI may increase by 1 each time in the same way as before. Here, the multi-PDSCH scheduling DCI (or the DCI with the DL DAI size increased by A) and the fallback DCI (or the DCI with the DL DAI size maintained the same as before) may be restricted so as not to indicate the same PUCCH slot. For example, the multi-PDSCH scheduling DCI (or the DCI with the DL DAI size increased by A) may be allowed to indicate the same PUCCH slot only with the non-fallback DCI (or the DCI with the DL DAI size increased by A) of the same / different cells. In other words, the multi-PDSCH scheduling DCI (or the DCI with the DL DAI size increased by A) may not be allowed to indicate the same PUCCH slot with the fallback DCI (or the DCI with the DL DAI size maintained the same as before) of the same / different cells. Here, only the fallback DCI (or the DCI with the DL DAI size maintained the same as before) and the non-fallback DCI (or the DCI other than the multi-PDSCH scheduling DCI among the DCI with the DL DAI size increased by A or the DCI with the DL DAI size increased by A) of the same / different cells can indicate the same PUCCH slot. However, in this case, the DAI field of the non-fallback DCI (or the DCI other than the multi-PDSCH scheduling DCI among the DCI with the DL DAI size increased by A or the DCI with the DL DAI size increased by A) may be defined / set (for example, only 2 bits of the most significant bit (MSB) or the least significant bit (LSB) among 2 + A bits are valid and the remaining bits are ignored) to indicate only values from 1 to 4 (although the size is A larger).

[0320] Alternatively, assume that A is the ceiling of the DAI increase amount {log2(maximum value among the N_max values for each CC (or BWP) set within the same cell group)}. Once the DL DAI of the fallback DL DCI (i.e., DCI format 1_0) is maintained at 2 bits as before, the counting step of the DAI may increase by 1 each time, the same as before. Here, only the PDSCH scheduled by the fallback DCI (or DCI with the DL DAI size maintained the same as before) may be collected and restricted so that another PUCCH is indicated. In other words, it can be expected that the PUCCH resources (especially time resources) indicated by the multi-PDSCH scheduling DCI (or DCI with the DL DAI size increased by A) and the PUCCH resources (especially time resources) indicated by the fallback DCI (or DCI with the DL DAI size maintained the same as before) do not overlap. For example, the multi-PDSCH scheduling DCI may be allowed to indicate the same PUCCH slot only with the same / different cell non-fallback DCI. In other words, the fallback DCI may not be allowed to indicate the same PUCCH slot as the multi-PDSCH scheduling DCI or non-fallback DCI.

[0321] - UL grant: The existing UL DAI size (i.e., T-DAI 2 bits) may be increased by the ceiling of {log2(maximum value among the N_max values for each CC (or BWP) set within the same cell group)}. Here, N_max is the maximum number of PDSCHs that can be scheduled by the M-DCI for a specific cell, and this increase should be applied to both the cell where the M-DCI is set and the cell where it is not set. That is, if the M-DCI is set in at least one serving cell within the same cell group, this increase amount is applied to the UL grant for all serving cells within the same cell group.

[0322] - HARQ-ACK Payload: The number of HARQ-ACK bits per DAI may be X bits (e.g., depending on whether there is a 2TB setting in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or codewords) that can be scheduled maximally by one DCI), the X value may be 2 or 1. As another example, for a cell where 2TB is set and spatial bundling for HARQ-ACK information is not set, X = 2 may be applicable. For a cell where 2TB is set but spatial bundling is set, or a cell where 1TB is set, X = 1 may be applicable.).

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

[0324] The terminal can configure / generate individual sub-CBs (i.e., in the case of scheduling TB-based PDSCH in a single PDSCH case and one sub-CB is configured for multiple PDSCH cases, and another sub-CB may be configured for CBG-based PDSCH scheduling in a single PDSCH case).

[0325] - S-DCI: In the case of a cell where CBG is set without M-DCI setting, the DL DAI size in the non-fallback DCI format (i.e., DCI format 1_1 or 1_2) can either increase as in Option 1-1) of Example 4-3 above or maintain 2 bits as before in Option 1-2). In the case of a cell where CBG is set without M-DCI setting, the DL DAI size in the fallback DCI format (i.e., DCI format 1_0) can increase or maintain 2 bits as in Example 4-3 above. In the case of a cell where M-DCI is set and CBG is also set, the DL DAI size may increase as in Example 4-3 above.

[0326] - M-DCI (case 1): In the case of a cell where M-DCI is set and CBG is not set, the DL DAI size may increase as in the above Example 4-3. Here, in a single PDSCH case, the DAI in the multi-TTI DCI (e.g., multiple PDSCH DCI) can indicate the C / T-DAI value for the TB-based PDSCH.

[0327] - M-DCI (case 2): In the case of a cell where M-DCI is set and CBG is also set, the DL DAI size in the DCI is in an increased state of M_1 bits (>2) (as in the above Example 4-3), and the C / T-DAI value may be indicated by M_1 bits in Option 2-1) (especially in the case of the above Option 1-1), or the C / T-DAI value may be indicated by 2 bits in Option 2-2) (especially in the case of the above Option 1-2). Characteristically, in the case of Option 2-2, the DL DAI field size itself may be reduced to 2 bits for each C / T-DAI by TDRA field verification (in the case of a single PDSCH case) (conversely, in the case of a multiple PDSCH case by TDRA field verification, the DL DAI field size may be M_1 bits). Here, in a single PDSCH case, the DAI in the multi-TTI DCI (e.g., multiple PDSCH DCI) can indicate the C / T-DAI value for the CBG-based PDSCH.

[0328] - UL grant: An additional 2 bits of T-DAI for sub-CB for CBG may be required for the DAI size for the UL grant in the above Example #4-3. That is, when CBG is set in at least one serving cell within the same cell group, the increase amount may be applied to the UL grant for all serving cells within the same cell group.

[0329] - HARQ-ACK Payload: In the case of scheduling TB-based PDSCH in a single PDSCH case and the payload of one sub-CB configured for multiple PDSCH cases may be the same as that in the above Example 4-3. The payload of other sub-CBs configured for CBG-based PDSCH scheduling by a single PDSCH case may be the same as the existing CBG-based sub-CB configuration.

[0330] Example 4-3b: When PDSCH-specific DAI count (i.e., Alt 2 of Example 4 above) + single HARQ-ACK CB (codebook) configuration + time bundling are set

[0331] Propose a type-2 HCB configuration when time bundling is set for one or more serving cells (all or part) set in the terminal as in the above Example 1.

[0332] - M-DCI: It may be the same as the above Example 4-3, or increase the existing DL DAI size (i.e., 2 bits for each of C / T-DAI) by ceiling{log2(maximum value among G_max values for each CC (or BWP) set within the same cell group)} (increase for each of C / T-DAI). At this time, G_max is the number of groups for the (maximum) time bundling set for a specific cell.

[0333] - S-DCI: It may be the same as the above Example 4-3, or increase the existing DL DAI size by ceiling{log2(maximum value among G_max values for each CC (or BWP) set within the same cell group)} (increase for each of C / T-DAI). Here, G_max is the number of groups for the (maximum) time bundling set for a specific cell.

[0334] Here, assume that the DAI increase amount ceiling{log2(the maximum value among the N_max or G_max values for each CC (or BWP) set within 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, a method of expanding the interval of the indicated DAI value by 2^A may be considered. This is because from the perspective of the reliability of the fallback DL DCI, it is not preferable to increase the DCI size. For example, when the above DAI increase amount is 1 bit, 2^A = 2, so the 2-bit DAI values indicated by the fallback DCI may be scaled by 2^A, i.e., {2, 4, 6, 8} instead of {1, 2, 3, 4}. Thus, if the previous C-DAI value is 2 and the C-DAI value indicated by the fallback DL DCI is 4, the terminal may map the HARQ-ACK information corresponding to C-DAI = 3 to NACK.

[0335] - UL grant: It may be the same as in the above Example 4-3 or increase by ceiling{log2(the maximum value among the G_max values for each CC (or BWP) set within the same cell group)} to the existing UL DAI size (i.e., 2 bits for T-DAI). Here, G_max is the number of groups for the (maximum) time bundling set for a specific cell, and this increase should be applied to both the cells where M-DCI is set and the cells where it is not set. That is, if M-DCI is set in at least one serving cell within the same cell group, this increase amount may be applied to the UL grants for all serving cells within the same cell group.

[0336] - HARQ-ACK Payload: If the DAI size for the M-DCI, S-DCI, and UL grant follows the above Example 4-3, the PDSCHs corresponding to G_max (or G assigned to each cell) DAI may be bundled to form the HARQ-ACK payload. Alternatively, when the DAI size for the M-DCI, S-DCI, and UL grant is determined based on G_max, 1 bit of HARQ-ACK may be configured for each DAI.

[0337] Example 4-4: DAI Count per PDSCH (i.e., Alt 2 of Example 4 above) + Individual HARQ-ACK Sub-Codebook (sub-CB) Configuration

[0338] The terminal can configure / generate one sub-CB corresponding to a single PDSCH case and configure / generate other sub-CBs corresponding to multiple PDSCH cases.

[0339] - M-DCI: It may be increased by ceiling{log2(maximum value among N_max values for each CC (or BWP) set within the same cell group)} for the existing DL DAI size (i.e., 2 bits for each of C / T-DAI). Here, N_max is the maximum number of PDSCHs schedulable by the M-DCI for a specific cell.

[0340] - S-DCI: The existing DL DAI size may be maintained. This should be applied to both the cells where the M-DCI is set and the cells where it is not set.

[0341] - UL grant: T-DAI Z (where Z is a natural number) bits may be further required for the additional sub-CB in the existing UL DAI size. Here, Z = ceiling{log2(maximum value among the N_max values for each CC (or BWP) set within the same cell group)}. Here, N_max is the maximum number of PDSCHs schedulable by M-DCI for a specific cell, and this increase should be applied to both the cell where M-DCI is set and the cell where it is not set. That is, if M-DCI is set in at least one serving cell within the same cell group, this increase amount may be applied to the UL grant for all serving cells within the same cell group.

[0342] - HARQ-ACK Payload: The number of HARQ-ACK bits for each sub-CB DAI corresponding to a single PDSCH case may be X (for example, the value of X may be 2 or 1 based on whether there is a 2TB setting in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or codewords) that can be scheduled maximally by one DCI). As another example, for a cell with a 2TB setting and no spatial bundling for HARQ-ACK information, X may be 2. For a cell with a 2TB setting but with spatial bundling set, or a cell with a 1TB setting, X may be 1). The number of HARQ-ACK bits for each sub-CB DAI corresponding to multiple PDSCH cases may also be X (for example, the value of X may be 2 or 1 based on whether there is a 2TB setting in the serving cell (i.e., whether PDSCH reception carrying two transport blocks is set, or the number of transport blocks (or codewords) that can be scheduled maximally by one DCI). As another example, for a cell with a 2TB setting and no spatial bundling for HARQ-ACK information, X may be 2. For a cell with a 2TB setting but with spatial bundling set, or a cell with a 1TB setting, X may be 1).

[0343] Example 4-4a: DAI count per PDSCH (i.e., Alt 2 of Example 4 above) + individual HARQ-ACK sub-CB configuration + when CBG is set

[0344] The terminal can configure / generate individual sub-CBs (i.e., in a single PDSCH case, a first sub-CB may be configured for TB-based PDSCH scheduling, a second sub-CB may be configured for multiple PDSCH cases, and a third sub-CB may be configured for CBG-based PDSCH scheduling in a single PDSCH case).

[0345] - S-DCI: In the case of a cell where CBG is set without M-DCI configuration, the DL DAI size in the non-fallback DCI format (i.e., DCI format 1_1 or 1_2) can maintain 2 bits as before. In the case of a cell where CBG is set without M-DCI configuration, the DL DAI size in the fallback DCI format (i.e., DCI format 1_0) can maintain 2 bits as before. In the case of a cell where M-DCI is set and CBG is also set, the DL DAI size may be maintained as in the above Embodiment 4-4.

[0346] - M-DCI (case 1): In the case of a cell where M-DCI is set and CBG is not set, the DL DAI size may increase as in the above Embodiment 4-4. Here, in a single PDSCH case, the DAI in the multi-TTI DCI (e.g., multiple PDSCH DCI) can indicate the C / T-DAI value for the TB-based PDSCH.

[0347] - M-DCI (case 2): In the case of a cell where M-DCI is set and CBG is also set, the DL DAI size in the DCI may increase to M_2 bits (>2) (as in the above Embodiment 4-4), and the C / T-DAI value may be indicated in 2 bits. Characteristically, depending on the TDRA field check (in the single PDSCH case), the DL DAI field size itself may be reduced to 2 bits for each C / T-DAI (conversely, in the multiple PDSCH case depending on the TDRA field check, the DL DAI field size may be M_2 bits). Here, in a single PDSCH case, the DAI in the multi-TTI DCI (e.g., multiple PDSCH DCI) can indicate the C / T-DAI value for the CBG-based PDSCH.

[0348] - UL grant: 4 bits of T-DAI (for an additional 2 sub-CBs) may be further required for the UL DAI size in the above Embodiment 4-4 (i.e., 2 bits of T-DAI are added for each sub-CB).

[0349] - HARQ-ACK Payload: For the case of scheduling a TB-based PDSCH in a single PDSCH case, the payload of the first sub-CB may be the same as the sub-CB corresponding to the single PDSCH case in the above Example 4-4. The payload of the second sub-CB configured for the multiple PDSCH cases may be the same as the sub-CB corresponding to the multiple PDSCH cases in the above Example 4-4. The payload of the third sub-CB configured for the CBG-based PDSCH scheduling by the single PDSCH case may be the same as the existing CBG-based sub-CB configuration.

[0350] Example 4-4b: When PDSCH-specific DAI count (i.e., Alt 2 of Example 4 above) + individual HARQ-ACK sub-CB configuration + time bundling are set

[0351] Propose a type-2 HCB configuration when time bundling is set for one or more serving cells (all or part) configured for the terminal as in Example 1 above.

[0352] - M-DCI: It may be the same as Example 4-4 above, or increased by ceiling{log2(maximum value among G_max values for each CC (or BWP) set within the same cell group)} for the existing DL DAI size (i.e., 2 bits each for C / T-DAI) (increase for each of C / T-DAI). Here, G_max is the number of groups for the (maximum) time bundling set for a specific cell.

[0353] - S-DCI or UL grant: It may be the same as Example 4-4 above.

[0354] - HARQ-ACK payload for sub-CBs corresponding to multiple PDSCH cases: If the DAI size for the M-DCI follows the above Example 4-4, the PDSCHs corresponding to G_max (or G assigned to each cell) DAI may be bundled to form the HARQ-ACK payload. Alternatively, if the DAI size for the M-DCI is determined based on G_max, 1 HARQ-ACK bit may be configured for each DAI.

[0355] - HARQ-ACK payload for sub-CBs corresponding to a single PDSCH case: The number of HARQ-ACK bits per sub-CB DAI corresponding to a single PDSCH case may be X (for example, based on whether there is a 2TB setting in the serving cell (i.e., whether PDSCH reception carrying 2 transport blocks is configured, or the number of transport blocks (or codewords) that can be maximally scheduled by one DCI), the X value may 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 may be used. For a cell where 2TB is configured but spatial bundling is configured, or a cell where 1TB is configured, X = 1 may be used.).

[0356] Example 4-5: DAI count for each of W (where W is a natural number) PDSCHs (i.e., Alt 3 of Example 4)

[0357] When the W value is the same as N_max_all (where N_max_all means the maximum value among the N_max values for each CC (or BWP) set within the same cell group, and N_max means the maximum number of PDSCHs that can be scheduled by the M-DCI for a specific cell), since the DAI is counted separately for each DCI (i.e., the same meaning as Alt 1 of Example 4 above), the above Example 4-1, Example 4-1a, Example 4-2, Example 4-2a may be applicable.

[0358] On the one hand, when the W value is smaller than N_max_all, the above-described Example 4-3, Example 4-3a, Example 4-4, and Example 4-4a may be applicable. However, here, the mathematical formula for calculating the DAI increase amount may be changed to ceiling{log2(maximum value among N_max / W values for each CC (or BWP) set within the same cell group)}. Also, in the HARQ-ACK payload, the number of HARQ-ACK bits for each DAI may be replaced with X*W bits instead of X bits. (When X = 1) When the number of PDSCHs corresponding to a specific DAI is less than W, for example, when it is K (K < W), the last W - K bits among the HARQ-ACK M bits corresponding to the DAI may be mapped to NACK.

[0359] Example 5: DAI Signaling Method When a Plurality of PUCCHs Corresponding to a Plurality of PDSCHs Scheduled by One DCI are Indicated

[0360] Since DAI counts must be performed individually for PDSCHs corresponding to different PUCCHs, there is a disadvantage in that individual DAI fields are required for the number of PUCCHs. For example, when N PDSCHs are scheduled by one DCI, the PUCCH corresponding to N1 PDSCHs is indicated to be in slot n1, and the PUCCH corresponding to the remaining N2 (i.e., N = N1 + N2, where the value of N1 may be predefined, or set by upper layer signaling, or N1 = ceiling{N / 2}, N2 = floor{N / 2} may be determined, or N1 = floor{N / 2}, N2 = ceiling{N / 2} may be determined.) PDSCHs is indicated to be in slot n2. Here, C-DAI / T-DAI for N1 PDSCHs and C-DAI / T-DAI for N2 PDSCHs may be required respectively. In order to reduce such DCI overhead problems, in the multiple PDSCH case, rules may be defined (or defined) to configure only individual C-DAI fields for 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 field for N1 PDSCHs and the T-DAI field for N2 PDSCHs may be omitted from signaling in the DL DCI. If the terminal misses (e.g., due to decoding failure) the last DCI with (T-DAI information), since there is no T-DAI in the multiple PDSCH case, a HARQ-ACK payload mismatch problem may occur between the base station and the terminal. However, the base station can solve the problem by further scheduling a DCI containing reliable T-DAI. Or, when different PUCCHs are indicated, the base station can solve the problem by a method such as blind detection of the plurality of PUCCHs. Characteristically, in the case of M-DCI, Case 1) more than N (for example, a value such as N = 1 may be predefined, or the N value may be set by upper layer signaling.) When the PDSCH of is scheduled, a plurality of PUCCHs may be indicated, or when N or fewer PDSCHs of Case 2) are scheduled, only one PUCCH may be indicated. In this case, in Case 2, a C-DAI and a T-DAI field may be configured in the DCI, and C-DAI and T-DAI information may be indicated. On the other hand, in Case 1, only a C-DAI1 field / information for N1 PDSCHs and a C-DAI2 field / information for N2 PDSCHs may be configured / indicated respectively. Here, the bits interpreted as the C-DAI and T-DAI fields in Case 2 may be interpreted as C-DAI1 for N1 PDSCHs and C-DAI2 for N2 PDSCHs respectively (or vice versa) in Case 1.

[0361] Alternatively, the N / N1 / N2 values may be in DL slot units rather than in PDSCH units. For example, when N' PDSCHs that span N slots are scheduled by one DCI, the PUCCH corresponding to N1' PDSCHs that span N1 slots is indicated as slot n1, and the PUCCH corresponding to the remaining N2 (i.e., N = N1 + N2, where the N1 value may be predefined or set by upper layer signaling, or N1 = ceiling{N / 2}, N2 = floor{N / 2} may be determined, or N1 = floor{N / 2}, N2 = ceiling{N / 2} may be determined.) PDSCHs that span N2 slots may be indicated as slot n2. Here, C-DAI / T-DAI for the PDSCH that spans N1 slots and C-DAI / T-DAI for the PDSCH that spans N2 slots may be required respectively. To reduce such DCI overhead problems, in the case of multiple PDSCHs, rules may be defined (may be defined) to configure only individual C-DAI fields equal to the number of PUCCHs (without T-DAI). That is, only the C-DAI1 field for the PDSCH that spans N1 slots and the C-DAI2 field for the PDSCH that spans N2 slots are signaled in the DL DCI, and the T-DAI field for the PDSCH that spans N1 slots and the T-DAI field for the PDSCH that spans N2 slots may be omitted from signaling in the DL DCI. If the terminal misses (e.g., due to decoding failure, etc.) the last DCI (with T-DAI information), since there is no T-DAI in the multiple PDSCH case, a HARQ-ACK payload mismatch problem may occur between the base station and the terminal. However, the base station can solve the problem by further scheduling a DCI containing reliable T-DAI. Or, different PUCCHs are indicated and the base station can solve the problem by methods such as blind detection of the plurality of PUCCHs.Specifically, in the case of M-DCI, when a PDSCH that spans more than N slots (for example, a value such as N = 1 is predefined, or the N value may be set by upper layer signaling) is scheduled, multiple PUCCHs may be indicated, or when a PDSCH that spans N or fewer slots is scheduled, only one PUCCH may be indicated. In this case, in Case 2, a C-DAI and a T-DAI field are configured in the DCI, and C-DAI and T-DAI information are indicated. On the other hand, in Case 1, only a C-DAI1 field / information for a PDSCH that spans N1 slots and a C-DAI2 field / information for a PDSCH that spans N2 slots may be configured / indicated. Here, the bits interpreted as the C-DAI and T-DAI fields in Case 2 may be interpreted as C-DAI1 for a PDSCH that spans N1 slots and C-DAI2 for a PDSCH that spans N2 slots (or vice versa) in Case 1.

[0362] Example 6: When performing DCI-specific DAI counting (i.e., Alt 1 of Example 4) + individual sub-CB configuration as in Example 4-2 above, a method for configuring individual sub-CBs is proposed.

[0363] A sub-CB that may contain HARQ-ACK information corresponding to a single PDSCH case is defined as sub-CB#1, and a sub-CB that may contain all or part of the HARQ-ACK information corresponding to multiple PDSCH cases can be defined as sub-CB#2. When defining the number of HARQ-ACK bits corresponding to one DAI as K, generally, the K value corresponding to sub-CB#2 may be larger than the K value corresponding to sub-CB#1. In the following, an S-DCI configured cell may mean a cell in which M-DCI is not configured.

[0364] Case 1) When there is no spatial bundling setting and 2-TB is set in an S-DCI configured cell (and / or an M-DCI configured cell)

[0365] Since at least 2-TB is set in the S-DCI setting cell and spatial bundling is not set, the number of HARQ-ACK bits for each DAI of sub-CB#1 may be determined to be 2 bits. Here, when only one or two PDSCHs of 1-TB or a single PDSCH of 2-TB are scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be included in sub-CB#2. If the HARQ-ACK information corresponding to the PDSCH scheduled by M-DCI as described above is included in sub-CB#1, when only a PDSCH of 1-TB is scheduled by M-DCI, among the 2 HARQ-ACK bits corresponding to the DAI, the first bit carries the ACK or NACK information of the scheduled PDSCH, and the second bit may always be filled with NACK or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) may be repeatedly transmitted. Further, when only two PDSCHs of 2-TB are scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be spatially bundled and converted into 2 bits and included in sub-CB#1.

[0366] On the other hand, when time bundling is set by M-DCI as in Embodiment 4-2b, if the number of time-bundled HARQ-ACK bits for the scheduled PDSCH is 1 or 2, the HARQ-ACK bits may be included in sub-CB#1, otherwise, they may be included in sub-CB#2.

[0367] Case 2) When there is no spatial bundling setting and only 2-TB is set in the M-DCI setting cell

[0368] Since 2-TB is not set in any of the S-DCI configured cells, the number of HARQ-ACK bits for each DAI of sub-CB#1 may be determined to be 1 bit. Here, only when a single PDSCH of 1-TB is scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be included in sub-CB#2. Further, when only one PDSCH of 2-TB is scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be subjected to spatial bundling processing, converted to 1 bit, and included in sub-CB#1.

[0369] On the other hand, when time bundling is set for M-DCI as in Example 4-2b, if the number of time-bundled HARQ-ACK bits for the scheduled PDSCH is 1, the HARQ-ACK bit may be included in sub-CB#1, otherwise, it may be included in sub-CB#2.

[0370] As another method, in this case as well, a method similar to the aforementioned Case 1 can be applied. For example, the number of HARQ-ACK bits for each DAI of sub-CB#1 may be determined to be 2 bits. Here, when only one or two PDSCHs of 1-TB or a single PDSCH of 2-TB are scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be included in sub-CB#2. If the HARQ-ACK information corresponding to the PDSCH scheduled by M-DCI as described above is included in sub-CB#1, when only the PDSCH of 1-TB is scheduled by M-DCI, among the 2 HARQ-ACK bits corresponding to the DAI, the first bit carries the ACK or NACK information of the scheduled PDSCH, and the second bit may always be filled with NACK or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) may be repeatedly transmitted. Similarly, in the case of a 1-TB PDSCH scheduled by S-DCI, among the 2 HARQ-ACK bits corresponding to the DAI, the first bit carries the ACK or NACK information of the scheduled PDSCH, and the second bit may always be filled with NACK or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) may be repeatedly transmitted. Also, when only two PDSCHs of 2-TB are scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be subjected to spatial bundling processing and converted into 2 bits, and may be included in sub-CB#1.

[0371] On the other hand, when time bundling is set for M-DCI as in Embodiment 4-2b, if the number of time-bundled HARQ-ACK bits for the scheduled PDSCH is 1 or 2, the HARQ-ACK bits may be included in sub-CB#1, otherwise, they may be included in sub-CB#2.

[0372] Case 3) If there is a spatial bundling setting or if 2-TB is not set for all cells (within one PUCCH cell group)

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

[0374] On the other hand, when time bundling is set for M-DCI as in Example 4-2b, if the number of time-bundled HARQ-ACK bits for the scheduled PDSCH is 1, the HARQ-ACK bit may be included in sub-CB#1; otherwise, it may be included in sub-CB#2.

[0375] As another method for the foregoing Case 3, the number of HARQ-ACK bits for each DAI of sub-CB#1 may be determined to be 2 bits. Here, similar to the foregoing case 1, when only one or two PDSCHs of 1-TB are scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCH scheduled by the M-DCI may be included in sub-CB#2. Further, in the case of a 1-TB PDSCH scheduled by S-DCI, among the 2 HARQ-ACK bits corresponding to the DAI, the first bit may carry the ACK or NACK information of the scheduled PDSCH, and the second bit may always be filled with NACK or the first bit (i.e., the ACK or NACK information of the PDSCH) may be repeatedly transmitted.

[0376] On the other hand, when time bundling is set for M-DCI as in Embodiment 4-2b, if the number of time-bundled HARQ-ACK bits for the scheduled PDSCH is 1 or 2, the HARQ-ACK bits may be included in sub-CB#1, otherwise, they may be included in sub-CB#2.

[0377] Embodiment 7: When some of the transmissions / receptions of the PDSCH scheduled by M-DCI are omissible, a method for DAI counting and HARQ-ACK CB (codebook) configuration is proposed.

[0378] In this embodiment, the omission of the transmissions / receptions of some PDSCHs may mean at least a part or the whole of the following cases.

[0379] - PDSCH overlapping with the symbol (or the slot containing the symbol) configured as uplink (or flexible) by the upper layer signaling for the common TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon) or the upper layer signaling for the dedicated TDD configuration (e.g., tdd-UL-DL-ConfigurationDedicated)

[0380] - PDSCH included in (or overlapping with) the resources configured / indicated by the upper layer signaling for the rate matching pattern setting (e.g., RateMatchPattern(s))

[0381] Here, as in the above Examples 4-3 (or Examples 4-3a / b) and 4-4 (or Examples 4-4a / b), the following proposes a DAI counting method when the DAI value increases for each PDSCH.

[0382] 1) Option 1: When transmission / reception of some of the multiple PDSCHs scheduled by M-DCI is optional, consecutive values starting from the (C-)DAI value indicated by DCI may be assigned in chronological order only to the actually transmitted / received PDSCHs (not the scheduling criteria). For example, in the case of a terminal that receives an M-DCI scheduling 4 PDSCHs, a part (or all) of the OFDM symbols of the third PDSCH may be configured as uplink (or flexible) by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. Also, when the C-DAI value indicated by the M-DCI corresponds to 3, (skipping the C-DAI value mapping for the third PDSCH) the terminal can recognize that the C-DAI values for the scheduled first / second / fourth PDSCHs are 3 / 4 / 5 respectively.

[0383] 2) Option 2: When transmission / reception of some of the multiple PDSCHs scheduled by M-DCI is omissible, the DAI value may be assigned consecutive values starting from the (C-)DAI value indicated by the DCI in chronological order for all the PDSCHs scheduled by the DCI, regardless of whether there is actual transmission / reception. For example, in the case of a terminal that has received an M-DCI scheduling 4 PDSCHs, a part (or all) of the OFDM symbols of the third PDSCH among them may be configured as uplink (or flexible) by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. Also, when the C-DAI value indicated by the M-DCI corresponds to 3, the terminal can recognize that the C-DAI values for the first / second / third / fourth PDSCHs scheduled are 3 / 4 / 5 / 6 respectively.

[0384] In Option 2 above, the HARQ-ACK information for the (C-)DAI value corresponding to the PDSCH for which transmission / reception is omitted may be mapped to NACK. Also, as in the above Example 4-1 (or Example 4-1a / b) and Example 4-2 (or Example 4-2a / b), when the DAI value increases for each DCI, the HARQ-ACK information for the PDSCH for which transmission / reception is omitted may be mapped to NACK.

[0385] Example 8: When transmission / reception of a part of the PUSCH scheduled by M-DCI is omissible, an aperiodic CSI reporting and a frequency hopping method are proposed.

[0386] In this example, the omission of transmission / reception of some of the PUSCHs can mean some or all of at least the following cases.

[0387] - PUSCH overlapping with a downlink (or flexible) symbol (or slot containing the symbol) configured by upper layer signaling for common TDD configuration (e.g., tdd-UL-DL-ConfigurationCommon) or dedicated TDD configuration (e.g., tdd-UL-DL-ConfigurationDedicated)

[0388] - PUSCH included in (or overlapping with) the resources configured / indicated by upper layer signaling for setting invalid symbol patterns (e.g., invalidSymbolPattern)

[0389] In such cases, an aperiodic CSI reporting and a frequency hopping method are proposed.

[0390] On the other hand, aperiodic CSI reporting by M-DCI can follow the following regulations.

[0391] When DCI format 0_1 schedules two PUSCH allocations, aperiodic CSI reporting is transmitted on the second scheduled PUSCH. When DCI format 0_1 schedules more than two PUSCH allocations, aperiodic CSI reporting is transmitted on the penultimate scheduled PUSCH.

[0392] However, when transmission / reception of some of the plurality of PUSCHs scheduled by M-DCI is omissible, a PUSCH for which an aperiodic CSI report is transmitted may be determined for only the actually transmitted / received PUSCHs (not the scheduling criteria). That is, if the number of actually transmitted / received PUSCHs is two, CSI is reported by the second PUSCH (out of the two actually transmitted / received PUSCHs), and if the number of actually transmitted / received PUSCHs is three or more, CSI may be reported by the second-to-last PUSCH (out of the plurality of actually transmitted / received PUSCHs). Specifically, it may be as follows.

[0393] For example, in the case of a terminal that has received an M-DCI scheduling four PUSCHs, a part (or all) of the OFDM symbols of the third PUSCH may be set to the downlink (or flexible) by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. Here, when an aperiodic CSI report is triggered by the M-DCI, the aperiodic CSI may be reported on the second scheduled PUSCH, which is the second-to-last PUSCH based on the actually transmitted PUSCH.

[0394] On the other hand, when DCI format 0_1 schedules a PUSCH allocation that is not less than two, but only two PUSCHs are transmitted, the aperiodic CSI report is transmitted by the second transmitted PUSCH. When DCI format 0_1 schedules two or more PUSCH allocations and two or more PUSCHs are transmitted, the aperiodic CSI report is transmitted on the second-to-last PUSCH transmitted.

[0395] On the other hand, in frequency hopping for (a plurality of PUSCHs scheduled by M-DCI), when inter-slot hopping is applied, n in the following formula 3μ s The value may increase according to the actually transmitted PUSCH (rather than the scheduled PUSCH). That is, for a PUSCH that is scheduled but not actually transmitted, the parameter n μ s does not have to increase.

[0396] In inter-slot frequency hopping, the starting RB between slots n μ s is given by Equation 3 below.

[0397]

Equation

[0398] In Equation 3, n μ s is the current slot number within the radio frame. Here, multi-slot PUSCH transmission may occur, and RB start is the starting RB within the UL BWP calculated from the resource block allocation information of resource allocation type 1. RB offset is the frequency offset in units of RBs between two frequency hops.

[0399] FIG. 12 is a diagram illustrating a signaling procedure between a base station and a terminal for a control information transmission / reception method according to an embodiment of the present disclosure.

[0400] FIG. 12 illustrates a signaling procedure between a terminal (UE: user equipment) and a base station (BS) based on the previously proposed method (e.g., any one or more combinations of Examples 1 to 8 and detailed examples thereof). The illustration in FIG. 12 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in FIG. 12 may be omitted depending on the situation and / or settings. Also, in FIG. 12, the base station and the terminal are merely examples and may be implemented by the devices illustrated in FIG. 15. For example, the processor 102 / 202 in FIG. 15 can be controlled to transmit and receive channels / signals / data / information, etc. using the transceiver 106 / 206, and can be controlled to store the transmitted or received channels / signals / data / information, etc. in the memory 104 / 204.

[0401] Also, in the operation between the base station and the terminal in FIG. 12, the above-mentioned content may be referred to / used without particular mention.

[0402] The base station may be a general term for an object that transmits and receives data with the terminal. For example, the base station may be a concept including one or more TPs (Transmission Points), one or more TRPs (Transmission and Reception Points), etc. Further, the TP and / or TRP may include a panel of the base station, a transmission and reception unit, etc. Also, "TRP" may be applied in place of expressions such as a panel, an antenna array, a cell (e.g., macro cell / small cell / pico cell, etc.), a TP (transmission point), a base station (base station, gNB, etc.). As described above, the TRP may be divided by information (e.g., index, ID) regarding the CORESET group (or, CORESET pool). As an example, when one terminal is set to transmit and receive with a plurality of TRPs (or, cells), this may mean that a plurality of CORESET groups (or, CORESET pools) are set for one terminal. The setting for such a CORESET group (or, CORESET pool) may be performed by upper layer signaling (e.g., RRC signaling, etc.).

[0403] Referring to FIG. 12, for convenience of explanation, the signaling between one base station and the terminal is considered, but it goes without saying that the signaling method may also be extended and applied to the signaling between a plurality of TRPs and a plurality of UEs. In the following description, the base station may be interpreted as one TRP. Or, the base station may include a plurality of TRPs, or may be one cell including a plurality of TRPs.

[0404] Referring to FIG. 12, the terminal receives the first M-DCI related setting information and / or the second HARQ-ACK related setting information from the base station (S1201).

[0405] Here, the first setting information and the second setting information may be transmitted by upper layer signaling (e.g., RRC signaling, MAC CE, etc.).

[0406] The first setting information can mean setting information (e.g., PDSCH-TimeDomainResourceAllocationListForMultiPDSCH) for setting whether a plurality of PDSCHs can be scheduled by a single DCI. For example, when information for setting scheduling for transmissions of a plurality of PDSCHs (or PUSCHs) by one DCI is provided for the serving cell, scheduling for transmissions of a plurality of PDSCHs (or PUSCHs) by one DCI on the cell (referred to as multi-PDSCH scheduling) may be set / supported. On the other hand, when information for setting scheduling for transmissions of a plurality of PDSCHs (or PUSCHs) by one DCI is not provided for the serving cell, multi-PDSCH scheduling may not be set / supported on the cell.

[0407] The second setting information may include information for setting the type of the HARQ-ACK codebook (e.g., the RRC parameter pdsch-HARQ-ACK-Codebook indicating a type-1 (i.e., quasi-static) HARQ-ACK codebook or a type-2 (i.e., dynamic) HARQ-ACK codebook), information for setting HARQ-ACK bundling (i.e., time bundling), and information regarding the number of HARQ-ack bundling groups (e.g., numberOfHARQBundlingGroups). Here, for example, when information for setting the number of HARQ bundling groups for a specific serving cell is provided, it may be regarded that time bundling is set for the specific serving cell. On the other hand, when information for setting the number of HARQ bundling groups for a specific serving cell is not provided, it may be regarded that time bundling is not set for the specific serving cell.

[0408] In other words, multi-PDSCH scheduling may be configured for one or more of the plurality of serving cells configured in the terminal. For serving cells for which multi-PDSCH scheduling is not configured, one PDSCH may be scheduled by a single DCI as before. And, HARQ-ACK bundling (i.e., time bundling) may be configured for one or more of the one or more serving cells for which multi-PDSCH scheduling is configured. For example, as described above, HARQ-ACK bundling may be configured for the cell by setting the number of HARQ-ACK bundling groups. In this way, one or more groups of HARQ-ACK information may be generated for a plurality of PDSCHs scheduled on a serving cell for which HARQ-ACK bundling is configured. Here, group-specific HARQ-HARQ information may be generated by performing a logical AND operation on the HARQ-ACK information for the plurality of PDSCHs included in each of the one or more groups.

[0409] Here, when the number of HARQ-ACK bundling groups is set to one, a single HARQ-ACK information may be generated, and when the number of HARQ-ACK bundling groups is set to be greater than one, HARQ-ACK information equal to the number of the groups may be generated. On the other hand, for a cell in which HARQ-ACK bundling (i.e., time bundling) is not configured among one or more serving cells for which multi-PDSCH scheduling is configured, HARQ-ACK information may be generated for each of the plurality of PDSCHs scheduled in the cell.

[0410] Here, based on the foregoing Example 1, time bundling may be configured for one or more of the plurality of cells configured in the terminal.

[0411] The terminal receives from the base station an M-DCI and / or an S-DCI that schedules a single or multiple PDSCHs, and receives the scheduled single or multiple PDSCHs (S1202).

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

[0413] As described above, on the cell where the M-DCI is configured among the plurality of serving cells configured for the terminal, one or more PDSCHs may be scheduled by the M-DCI. On the other hand, on the cell where the M-DCI is not configured among the plurality of serving cells configured for the terminal, a single PDSCH may be scheduled by the S-DCI.

[0414] That is, the terminal can receive a DCI (for example, each DCI format for each serving cell) that schedules one or more PDSCHs in each of the plurality of serving cells configured. And the terminal can receive one or more PDSCHs in each of the plurality of serving cells configured (that is, receive a plurality of PDSCHs in the plurality of serving cells configured in total).

[0415] Here, in the DAI signaling, the DAI signaling may be performed based on any one or a combination of one or more detailed embodiments of the above-described Example 4, or based on the above-described Example 5, or based on the above-described Example 7.

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

[0417] Here, based on the aforementioned Example 2, the terminal can configure / generate a type-1 HARQ-ACK codebook when time bundling is set. Or, based on the aforementioned Example 3, the terminal can configure / generate a type-1 HARQ-ACK codebook when slot group-based PDCCH monitoring is set. Or, based on any one or a combination of one or more detailed examples of the aforementioned Example 4 or based on the aforementioned Example 6, the terminal can configure / generate a type-2 HARQ-ACK codebook. Or, based on the aforementioned Example 7, when transmission / reception of a part of the PDSCH scheduled by M-DCI is omitted, the terminal can configure / generate a HARQ-ACK codebook.

[0418] On the other hand, based on the aforementioned Example 1, when only the PDSCH overlapping with the uplink symbol is included in a specific group of the HARQ bundling, the HARQ-ACK information for the specific group may be generated as NACK (negative ACK). Or, when one or more PDSCHs overlapping with the uplink symbol are included in a specific group of the HARQ bundling, the HARQ-ACK information for the specific group may be generated by regarding the HARQ-ACK information for one or more PDSCHs overlapping with the uplink symbol as ACK or NACK (negative ACK).

[0419] The terminal transmits HARQ-ACK information to the base station at the time indicated by the DCI scheduling the PDSCH based on the HARQ-ACK codebook type set by the configuration information (S1204).

[0420] The terminal transmits control information including the previously generated HARQ-ACK codebook to the base station via PUCCH or PUSCH. Here, the control information may further include, in addition to the HARQ-ACK codebook, a scheduling request, channel state information, uplink data (in the case of PUSCH), and the like.

[0421] FIG. 13 is a diagram illustrating the operation of a terminal for a control information transmission / reception method according to an embodiment of the present disclosure.

[0422] In FIG. 13, the operation of a terminal based on a previously proposed method (for example, any one or more combinations of Examples 1 to 8 and detailed examples thereof) is illustrated. The illustration in FIG. 13 is for convenience of explanation and does not limit the scope of the present disclosure. Some steps illustrated in FIG. 13 may be omitted depending on the situation and / or settings. Also, in FIG. 13, the terminal is merely an example and may be implemented by the apparatus illustrated in FIG. 15. For example, the processor 102 / 202 in FIG. 15 can be controlled to transmit and receive channels / signals / data / information, etc. (for example, RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, PHICH, etc.) using the transceiver 106 / 206, and can be controlled to store the transmitted or received channels / signals / data / information, etc. in the memory 104 / 204.

[0423] The terminal receives, from a base station, setting information (hereinafter, referred to as first setting information) for setting HARQ-ACK bundling for one or more serving cells among a plurality of serving cells set for the terminal (S1301).

[0424] Here, the first setting information may further include information for setting the type of the HARQ-ACK codebook (for example, an RRC parameter pdsch-HARQ-ACK-Codebook indicating a type-1 (i.e., quasi-static) HARQ-ACK codebook or a type-2 (i.e., dynamic) HARQ-ACK codebook) and / or information regarding the number of HARQ-ACK bundling groups (for example, numberOfHARQBundlingGroups).

[0425] Also, as described above, the first setting information may correspond to information regarding the number of HARQ-ACK bundling groups. That is, when information for setting the number of HARQ bundling groups for a specific serving cell is provided, it may be regarded that time bundling is set for the specific serving cell. For example, when information for setting the number of HARQ bundling groups for a specific serving cell is provided, it may be regarded that time bundling is set for the specific serving cell. On the other hand, when information for setting the number of HARQ bundling groups for a specific serving cell is not provided, it may be regarded that time bundling is not set for the specific serving cell.

[0426] Also, together with the first setting information (i.e., by one message or information element (IE)), or separately from the first setting information (i.e., by different messages or IEs), the terminal can receive from the base station second setting information (e.g., PDSCH-TimeDomainResourceAllocationListForMultiPDSCH) for setting the scheduling (referred to as multi-PDSCH scheduling) of a plurality of PDSCHs by a single DCI for one or more serving cells among the plurality of serving cells set for the terminal. For example, when information for setting the scheduling for a plurality of PDSCH (or PUSCH) transmissions by one DCI is provided for the serving cell, the scheduling for a plurality of PDSCH (or PUSCH) transmissions by one DCI (referred to as multi-PDSCH scheduling) may be set / supported on the cell. On the other hand, when information for setting the scheduling for a plurality of PDSCH (or PUSCH) transmissions by one DCI is not provided for the serving cell, multi-PDSCH scheduling may not be set / supported on the cell.

[0427] Multi-PDSCH scheduling may be configured for one or more of a plurality of serving cells configured in a terminal. For a serving cell for which multi-PDSCH scheduling is not configured, one PDSCH may be scheduled by a single DCI as before. And HARQ-ACK bundling (i.e., time bundling) may be configured for one or more of the one or more serving cells for which multi-PDSCH scheduling is configured. For example, as described above, HARQ-ACK bundling may be configured for the cell by setting the number of HARQ-ACK bundling groups. In this way, one or more groups of HARQ-ACK information may be generated for a plurality of PDSCHs scheduled on a serving cell for which HARQ-ACK bundling is configured. Here, group-specific HARQ-HARQ information may be generated by performing a logical AND operation on the HARQ-ACK information for the plurality of PDSCHs included in each of the one or more groups.

[0428] Here, when the number of HARQ-ACK bundling groups is set to one, a single HARQ-ACK information may be generated, and when the number of HARQ-ACK bundling groups is set to be greater than one, HARQ-ACK information equal to the number of the groups may be generated. On the other hand, for a cell for which HARQ-ACK bundling (i.e., time bundling) is not configured in a serving cell for which multi-PDSCH scheduling is configured, HARQ-ACK information may be generated for each of the plurality of PDSCHs scheduled in the cell.

[0429] Here, the first configuration information and the second configuration information may be transmitted by upper layer signaling (e.g., RRC signaling, MAC CE, etc.).

[0430] Here, based on the foregoing Example 1, time bundling may be configured for one or more of a plurality of cells configured in a terminal.

[0431] The terminal receives from the base station DCI that schedules 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).

[0432] Here, the DCI may be transmitted by the PDCCH.

[0433] As described above, among the plurality of serving cells configured for the terminal, one or more PDSCHs may be scheduled by M-DCI on the cell where M-DCI is configured. On the other hand, among the plurality of serving cells configured for the terminal, a single PDSCH may be scheduled by S-DCI on the cell where M-DCI is not configured.

[0434] That is, the terminal can receive DCI (for example, each DCI format for each serving cell) that schedules one or more PDSCHs in each of the plurality of configured serving cells. And the terminal can receive one or more PDSCHs in each of the plurality of configured serving cells (that is, receive a plurality of PDSCHs in the plurality of serving cells configured as a whole).

[0435] Here, in the DAI signaling, the DAI signaling may be performed based on any one or a combination of one or more of the detailed embodiments of the foregoing Example 4, or based on the foregoing Example 5, or based on the foregoing Example 7.

[0436] The terminal generates a HARQ-ACK codebook based on HARQ-ACK information for a plurality of PDSCHs, and transmits control information including the generated HARQ-ACK codebook to the base station (S1304).

[0437] Here, the terminal can configure / generate a type-1 HARQ-ACK codebook when time bundling is set based on the foregoing Example 2. Alternatively, the terminal can configure / generate a type-1 HARQ-ACK codebook when slot group-based PDCCH monitoring is set based on the foregoing Example 3.

[0438] Alternatively, the terminal can configure / generate a type-2 HARQ-ACK codebook based on any one or a combination of one or more detailed examples of the foregoing Example 4.

[0439] 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 may be generated by appending the second HARQ-ACK sub-codebook to the first HARQ-ACK sub-codebook.

[0440] In this case, the C-DAI value and the T-DAI value of the DCI may be applied individually to each of the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook.

[0441] Here, the first HARQ-ACK sub-codebook may be generated for PDSCHs on one or more first serving cells where the number of HARQ bundling 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 bundling groups is set to be greater than 1.

[0442] On the other hand, when the second configuration information is received first, for the PDSCH on one or more first serving cells among the plurality of serving cells configured in the terminal, in which the multiplexed PDSCH scheduling is not configured or the number of HARQ bundling groups is set to 1, the first HARQ-ACK sub-codebook may be generated. And for the PDSCH on one or more second serving cells among the one or more serving cells in which the multiplexed PDSCH scheduling is configured, in which the number of HARQ bundling groups is set to be greater than 1 or HARQ bundling is not configured, the second HARQ-ACK sub-codebook may be generated.

[0443] Here, if HARQ bundling is configured for the one or more second serving cells, the second HARQ-ACK sub-codebook may be generated based on the first HARQ-ACK information bits. The number of the first HARQ-ACK information bits may correspond to the maximum value among the products of the number of HARQ bundling groups and the X value over all of the one or more second serving cells. For a cell in which PDSCH reception carrying two transport blocks is configured (i.e., the number of maximum TBs (or codewords) is set to 2 by one DCI) and spatial bundling for HARQ-ACK information (i.e., generating HARQ-ACK information bits by logically ANDing the HARQ-ACK information bits corresponding to the first TB and the second TB) is not configured, the X value may be 2; otherwise, the X value may be 1.

[0444] Alternatively, if the HARQ bundling is not configured for the one or more second serving cells, the second HARQ-ACK sub-codebook may be generated based on second HARQ-ACK information bits. The number of the second HARQ-ACK information bits may correspond to the maximum value among the product of the number of PDSCHs schedulable by a single DCI over all of the one or more second serving cells and an X value. The X value may be 2 for a cell in which PDSCH reception carrying two transport blocks is configured (i.e., the number of maximum TBs (or codewords) is set to 2 by one DCI) and spatial bundling for HARQ-ACK information (i.e., generating HARQ-ACK information bits by logically ANDing HARQ-ACK information bits corresponding to a first TB and a second TB) is not configured, and otherwise the X value may be 1.

[0445] Alternatively, based on the foregoing Example 6, a type-2 HARQ-ACK codebook can be configured / generated. Alternatively, based on the foregoing Example 7, when transmission / reception of a part of PDSCH scheduled by an M-DCI is omitted, a HARQ-ACK codebook can be configured / generated.

[0446] On the other hand, based on the foregoing Example 1, when only the PDSCH overlapping with an uplink symbol is included in a specific group of the HARQ bundling, the HARQ-ACK information for the specific group may be generated as NACK (negative ACK). Alternatively, when one or more PDSCHs overlapping with an uplink symbol are included in a specific group of the HARQ bundling, the HARQ-ACK information for the specific group may be generated by regarding the HARQ-ACK information for the one or more PDSCHs overlapping with the uplink symbol as ACK or NACK (negative ACK).

[0447] As described above, the terminal can generate a HARQ-ACK codebook based on the HARQ-ACK codebook type set by the configuration information. Then, the terminal can transmit control information including the generated HARQ-ACK codebook to the base station via PUCCH or PUSCH. Here, the HARQ-ACK information can be transmitted to the base station at the time indicated by the DCI that schedules the PDSCH. Further, the control information may further include, in addition to the HARQ-ACK codebook, scheduling requests, channel state information, uplink data (in the case of PUSCH), and the like.

[0448] FIG. 14 is a diagram illustrating the operation of a base station with respect to a control information transmission / reception method according to an embodiment of the present disclosure.

[0449] In FIG. 14, the operation of the base station based on the previously proposed method (for example, any one or more combinations of Examples 1 to 8 and detailed examples thereof) is illustrated. The illustration in FIG. 14 is for convenience of explanation and does not limit the scope of the present disclosure. Some of the steps illustrated in FIG. 14 may be omitted depending on the situation and / or configuration. Also, in FIG. 14, the base station is merely an example and may be implemented by the apparatus illustrated in FIG. 15. For example, the processor 102 / 202 in FIG. 15 can be controlled to transmit and receive channels / signals / data / information, etc. (for example, RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, PHICH, etc.) using the transceiver (106 / 206), and can be controlled to store the transmitted or received channels / signals / data / information, etc. in the memory 104 / 204.

[0450] The base station transmits (S1401) to the terminal configuration information (hereinafter, referred to as first configuration information) for setting HARQ-ACK bundling for one or more serving cells among a plurality of serving cells set for the terminal.

[0451] Here, the first setting information may further include information for setting the type of the HARQ-ACK codebook (for example, RRC parameter pdsch-HARQ-ACK-Codebook indicating type-1 (i.e., quasi-static) HARQ-ACK codebook or type-2 (i.e., dynamic) HARQ-ACK codebook) and / or information regarding the number of HARQ-ACK bundling groups (for example, numberOfHARQBundlingGroups).

[0452] Also, as described above, the first setting information may correspond to information regarding the number of HARQ-ACK bundling groups. That is, when information for setting the number of HARQ bundling groups for a specific serving cell is provided, it may be regarded that time bundling is set for the specific serving cell. For example, when information for setting the number of HARQ bundling groups for a specific serving cell is provided, it may be regarded that time bundling is set for the specific serving cell. On the other hand, when information for setting the number of HARQ bundling groups for a specific serving cell is not provided, it may be regarded that time bundling is not set for the specific serving cell.

[0453] Also, together with the first configuration information (i.e., by one message or information element (IE)), or separately from the first configuration information (i.e., by different messages or IEs), the base station can send to the terminal second configuration information (e.g., PDSCH-TimeDomainResourceAllocationListForMultiPDSCH) for configuring the scheduling of multiple PDSCHs by a single DCI for one or more of the plurality of serving cells configured for the terminal (referred to as multi-PDSCH scheduling). For example, when information for configuring the scheduling of multiple PDSCH (or PUSCH) transmissions by one DCI is provided for the serving cell, scheduling of multiple PDSCH (or PUSCH) transmissions by one DCI (referred to as multi-PDSCH scheduling) may be configured / supported on the cell. On the other hand, when information for configuring the scheduling of multiple PDSCH (or PUSCH) transmissions by one DCI is not provided for the serving cell, multi-PDSCH scheduling may not be configured / supported on the cell.

[0454] For one or more of the plurality of serving cells configured in the terminal, multi-PDSCH scheduling may be configured. For a serving cell in which multi-PDSCH scheduling is not configured, one PDSCH may be scheduled by a single DCI as before. And for one or more of the one or more serving cells in which multi-PDSCH scheduling is configured, HARQ-ACK bundling (i.e., time bundling) may be configured. For example, as described above, HARQ-ACK bundling may be configured for the cell by setting the number of HARQ-ACK bundling groups. In this way, for a plurality of PDSCHs scheduled on a serving cell for which HARQ-ACK bundling is configured, HARQ-ACK information may be generated for each of one or more groups. Here, by performing a logical AND operation on the HARQ-ACK information for the plurality of PDSCHs included in each of the one or more groups, HARQ-HARQ information for each group may be generated.

[0455] Here, when the number of HARQ-ACK bundling groups is set to 1, a single HARQ-ACK information may be generated, and when the number of HARQ-ACK bundling groups is set to be greater than 1, HARQ-ACK information equal to the number of the groups may be generated. On the other hand, for a cell in which HARQ-ACK bundling (i.e., time bundling) is not configured in a serving cell for which multi-PDSCH scheduling is configured, HARQ-ACK information may be generated for each of the plurality of PDSCHs scheduled in the cell.

[0456] Here, the first configuration information and the second configuration information may be transmitted by upper layer signaling (e.g., RRC signaling, MAC CE, etc.).

[0457] Here, based on the above-described Example 1, time bundling may be configured for one or more of the plurality of cells configured in the terminal.

[0458] The base station transmits DCI for scheduling one or more PDSCHs in each of a plurality of serving cells set for the terminal (S1402), and the base station transmits a plurality of PDSCHs on the plurality of serving cells set for the terminal (S1403).

[0459] Here, the DCI may be transmitted by a PDCCH.

[0460] As described above, among the plurality of serving cells set for the terminal, one or more PDSCHs may be scheduled by M-DCI on the cell where M-DCI is set. On the other hand, among the plurality of serving cells set for the terminal, a single PDSCH may be scheduled by S-DCI on the cell where M-DCI is not set.

[0461] That is, the base station can transmit DCI (for example, each DCI format for each serving cell) for scheduling one or more PDSCHs in each of a plurality of serving cells set for the terminal. And the base station can transmit one or more PDSCHs in each of a plurality of serving cells set for the terminal (that is, transmit a plurality of PDSCHs in the plurality of serving cells set as a whole).

[0462] Here, in the DAI signaling, the DAI signaling may be performed based on any one or a combination of one or more detailed examples of the detailed example of Embodiment 4 described above, or based on Embodiment 5 described above, or based on Embodiment 7 described above.

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

[0464] Here, based on the aforementioned Example 2, a type-1 HARQ-ACK codebook may be configured / generated when time bundling is set. Alternatively, based on the aforementioned Example 3, a type-1 HARQ-ACK codebook may be configured / generated when slot group-based PDCCH monitoring is set.

[0465] Alternatively, based on any one or a combination of one or more of the detailed examples of the aforementioned Example 4, a type-2 HARQ-ACK codebook may be configured / generated.

[0466] 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 may be generated by appending the second HARQ-ACK sub-codebook to the first HARQ-ACK sub-codebook.

[0467] In this case, the C-DAI value and the T-DAI value of the DCI may be applied individually to each of the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook.

[0468] Here, the first HARQ-ACK sub-codebook may be generated for PDSCHs on one or more first serving cells where the number of HARQ bundling 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 bundling groups is set to be greater than 1.

[0469] On the other hand, when the second configuration information is received first, for the PDSCH on one or more first serving cells among the plurality of serving cells configured in the terminal, in which the multiplexed PDSCH scheduling is not configured or the number of HARQ bundling groups is set to 1, the first HARQ-ACK sub-codebook may be generated. And, for the PDSCH on one or more second serving cells among the one or more serving cells in which the multiplexed PDSCH scheduling is configured, in which the number of HARQ bundling groups is set to be greater than 1 or HARQ bundling is not configured, the second HARQ-ACK sub-codebook may be generated.

[0470] Here, if HARQ bundling is configured for the one or more second serving cells, the second HARQ-ACK sub-codebook may be generated based on the first HARQ-ACK information bits. The number of the first HARQ-ACK information bits may correspond to the maximum value among the products of the number of HARQ bundling groups and the X value over all of the one or more second serving cells. For a cell in which PDSCH reception carrying two transport blocks is configured (i.e., the number of maximum TBs (or codewords) is set to 2 by one DCI) and spatial bundling for HARQ-ACK information (i.e., generating HARQ-ACK information bits by logically ANDing the HARQ-ACK information bits corresponding to the first TB and the second TB) is not configured, the X value may be 2; otherwise, the X value may be 1.

[0471] Alternatively, if the HARQ bundling is not configured for the one or more second serving cells, the second HARQ-ACK sub-codebook may be generated based on the second HARQ-ACK information bits. The number of the second HARQ-ACK information bits may correspond to the maximum value among the product of the number of PDSCHs schedulable by a single DCI across all of the one or more second serving cells and the X value. For a cell in which reception of a PDSCH carrying two transport blocks is configured (i.e., the number of maximum TBs (or codewords) is set to 2 by one DCI) and spatial bundling for HARQ-ACK information (i.e., generating HARQ-ACK information bits by logically ANDing HARQ-ACK information bits corresponding to the first TB and the second TB) is not configured, the X value may be 2; otherwise, the X value may be 1.

[0472] Alternatively, based on the aforementioned Example 6, a type-2 HARQ-ACK codebook may be configured / generated. Alternatively, based on the aforementioned Example 7, when transmission / reception of a part of the PDSCH scheduled by an M-DCI is omitted, a HARQ-ACK codebook may be configured / generated.

[0473] On the other hand, based on the aforementioned Example 1, when only the PDSCH overlapping with an uplink symbol is included in a specific group of the HARQ bundling, the HARQ-ACK information for the specific group may be generated as NACK (negative ACK). Alternatively, when one or more PDSCHs overlapping with an uplink symbol are included in a specific group of the HARQ bundling, the HARQ-ACK information for the specific group may be generated by regarding the HARQ-ACK information for the one or more PDSCHs overlapping with the uplink symbol as ACK or NACK (negative ACK).

[0474] The base station can receive control information including the HARQ-ACK codebook generated as described above from the terminal by means of PUCCH or PUSCH. Here, the HARQ-ACK information may be transmitted from the terminal at the time indicated by the DCI that schedules the PDSCH. Further, in addition to the HARQ-ACK codebook, the control information may further include a scheduling request, channel state information, uplink data (in the case of PUSCH), and the like.

[0475] General apparatus to which the present disclosure is applicable

[0476] FIG. 15 illustrates a block configuration diagram of a wireless communication device according to an embodiment of the present disclosure.

[0477] Referring to FIG. 15, the first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals using various wireless connection technologies (e.g., LTE, NR).

[0478] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 controls the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure. For example, after processing the information in the memory 104 to generate a first information / signal, the processor 102 may transmit a wireless signal including the first information / signal from the transceiver 106. Also, after receiving a wireless signal including a second information / signal from the transceiver 106, the processor 102 can store the information obtained from the signal processing of the second information / signal in the memory 104. The memory 104 may be connected to the processor 102 and can store various information related to the operation of the processor 102. For example, the memory 104 can store software code including instructions for performing part or all of the processes controlled by the processor 102 or for executing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and can transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 can include a transmitter and / or a receiver. The transceiver 106 may be alternatively referred to as an RF (Radio Frequency) unit. In the present invention, the wireless device may mean a communication modem / circuit / chip.

[0479] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure. For example, after the processor 202 processes the information in the memory 204 to generate third information / signals, the processor 202 may transmit a wireless signal including the third information / signals from the transceiver 206. Also, after the processor 202 receives a wireless signal including fourth information / signals from the transceiver 206, the processor 202 may store the information obtained from the 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 instructions for performing part or all of the processes controlled by the processor 202 or for executing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technologies (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be alternatively referred to as an RF unit. In the present invention, the wireless device may mean a communication modem / circuit / chip.

[0480] Hereinafter, the hardware elements of the wireless devices 100 and 200 will be described in more detail. Although not limited thereto, 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, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, an SDU, a message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in the present disclosure, and provide it to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206, and obtain a PDU, an SDU, a message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure.

[0481] One or more processors 102, 202 can be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors 102, 202 may be embodied by hardware, firmware, software, or a combination thereof. As an example, one or more ASICs (Application Specific Integrated Circuits), one or more DSPs (Digital Signal Processors), one or more DSPDs (Digital Signal Processing Devices), one or more PLDs (Programmable Logic Devices), or one or more FPGAs (Field Programmable Gate Arrays) may be included in one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this disclosure may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. The firmware or software configured to execute the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this disclosure may be included in one or more processors 102, 202, stored in one or more memories 104, 204, and driven by one or more processors 102, 202. The descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instruction words, and / or a set of instruction words.

[0482] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and can store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories 104, 204 may be constituted by ROM, RAM, EPROM, flash memory, hard drive, register, cache memory, computer-readable storage medium, and / or combinations thereof. The one or more memories 104, 204 may be located inside and / or outside the one or more processors 102, 202. Also, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 by various techniques such as wired or wireless connections.

[0483] One or more transceivers 106, 206 can transmit user data, control information, radio signals / channels, etc. mentioned in the methods and / or operation sequence diagrams of the present disclosure to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, radio signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and can transmit and receive radio signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or radio signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or radio signals from one or more other devices. Also, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, radio signals / channels, etc. mentioned in the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in the present disclosure via one or more antennas 108, 208. In the present disclosure, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received radio signals / channels, etc. from RF band signals to baseband signals in order to process received user data, control information, radio signals / channels, etc. using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102, 202 from baseband signals to RF band signals. For this purpose, one or more transceivers 106, 206 can include (analog) oscillators and / or filters.

[0484] The embodiments described above are those in which the components and features of the present disclosure are combined in a predetermined form. Each component or feature should be considered as optional unless specifically stated otherwise. Each component or feature may be implemented in a form that does not combine with other components or features. Also, it is possible to combine some components and / or features to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in other embodiments, or may be replaced with corresponding components or features of other embodiments. It is obvious that claims without an explicit citation relationship in the claims can be combined to form embodiments, or can be included as new claims by amendment after filing.

[0485] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be construed in any way as restrictive, but should be considered as exemplary. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and any changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

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

[0487] Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure can include, in addition to LTE, NR, and 6G, Narrowband Internet of Things (NB-IoT) for low-power communication. At this time, for example, the NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (XXX, YYY) of the present disclosure can communicate based on LTE-M technology. At this time, as an example, the LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, the LTE-M technology may be implemented by at least any one of various standards such as 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 above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices (XXX, YYY) of the present disclosure can include at least any one of ZigBee (registered trademark), Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-mentioned names. As an example, the ZigBee technology can generate PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be called by various names.

Industrial Applicability

[0488] Although the method proposed in this disclosure has been mainly described with examples applicable to 3GPP LTE / LTE-A and 5G systems, it is applicable to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method for transmitting HARQ (Hybrid Automatic Repeat and request)-ACK (acknowledgement) information in a wireless communication system, wherein the method performed by a terminal comprises: receiving configuration information for configuring HARQ bundling for one or more serving cells among a plurality of serving cells configured for the terminal; receiving downlink control information (DCI) for scheduling one or more physical downlink shared channels (PDSCHs) in each of the plurality of serving cells; receiving a plurality of PDSCHs in the plurality of serving cells; transmitting HARQ-ACK information for the plurality of PDSCHs, wherein a HARQ-ACK codebook corresponding to the HARQ-ACK information includes a first HARQ-ACK sub-codebook and a second HARQ-ACK sub-codebook, wherein the first HARQ-ACK sub-codebook is determined for one or more first serving cells in which the number of groups of the HARQ bundling is set to 1, and the second HARQ-ACK sub-codebook is determined for one or more second serving cells in which the number of groups of the HARQ bundling is set to be greater than 1.

2. The method according to claim 1, further comprising receiving other configuration information for configuring multi-PDSCH scheduling for scheduling a plurality of PDSCHs by a single DCI for one or more serving cells among the plurality of serving cells.

3. Based on the HARQ bundling being configured for the one or more second serving cells, the second HARQ-ACK sub-codebook is determined based on first HARQ-ACK information bits, wherein the number of the first HARQ-ACK information bits corresponds to the maximum value among the product of the number of groups of the HARQ bundling and the value of X over all of the one or more second serving cells, wherein for a cell in which PDSCH reception for carrying two transport blocks is configured and spatial bundling for HARQ-ACK information is not configured, the value of X is 2; otherwise, the value of X is 1. The method according to claim 1.

4. The method according to claim 1, wherein the C-DAI (counter downlink assignment index) value and the T-DAI (total downlink assignment index) value of the DCI are individually applied to each of the first HARQ-ACK sub-codebook and the second HARQ-ACK sub-codebook.

5. The method according to claim 1, wherein the HARQ-ACK codebook is determined by adding the second HARQ-ACK sub-codebook to the first HARQ-ACK sub-codebook.

6. HARQ-ACK information is generated for each of one or more groups of a plurality of PDSCHs scheduled on the specific serving cell based on the HARQ bundling being set for the specific serving cell, the method according to claim 1.

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

8. The method according to claim 6, wherein the HARQ-ACK information for the specific group is generated as NACK (negative ACK) based on only the PDSCHs overlapping with uplink symbols being included in a specific group of the HARQ bundling.

9. The method according to claim 6, wherein based on one or more PDSCHs overlapping with uplink symbols being included in a specific group of the HARQ bundling, the HARQ-ACK information for the one or more PDSCHs is regarded as ACK or NACK (negative ACK), and the HARQ-ACK information for the specific group is generated.

10. A terminal for transmitting HARQ (Hybrid Automatic Repeat and request)-ACK (acknowledgement) information in a wireless communication system, the terminal comprising: At least one transceiver for transmitting and receiving wireless signals; At least one processor for controlling the at least one transceiver, The at least one processor is Receive setting information for setting HARQ bundling for one or more serving cells among a plurality of serving cells set for the terminal, Receive DCI (downlink control information) for scheduling one or more PDSCHs (physical downlink shared channels) in each of the plurality of serving cells, Receive a plurality of PDSCHs in the plurality of serving cells, Is configured to transmit 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, The first HARQ-ACK sub-codebook is determined for one or more first serving cells in which the number of groups of the HARQ bundling is set to 1, A terminal in which the second HARQ-ACK sub-codebook is determined for one or more second serving cells in which the number of groups of the HARQ bundling is set to be greater than 1.

11. A base station that receives HARQ (Hybrid Automatic Repeat and request)-ACK (acknowledgement) information in a wireless communication system, the base station comprising: At least one transceiver for transmitting and receiving wireless signals, At least one processor for controlling the at least one transceiver, The at least one processor is: Transmit setting information for setting HARQ bundling for one or more serving cells among a plurality of serving cells set for the terminal, Transmit DCI (downlink control information) for scheduling one or more PDSCHs (physical downlink shared channels) in each of the plurality of serving cells, Transmit a plurality of PDSCHs in the plurality of serving cells, Is configured to 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, The first HARQ-ACK sub-codebook is determined for one or more first serving cells in which the number of groups of the HARQ bundling is set to 1, A base station in which the second HARQ-ACK sub-codebook is determined for one or more second serving cells in which the number of groups of the HARQ bundling is set to be greater than 1.

Images