Method and apparatus for transmitting and receiving control information in a 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] This 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 technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, mobile communication systems have expanded beyond voice to include data services, and currently, the explosive increase in traffic is causing resource shortages. Furthermore, users are demanding faster services, so there is a need for more advanced mobile communication systems.

[0003] The requirements for next-generation mobile communication systems are broad, including the ability to handle explosive data traffic, a dramatic increase in transmission rates per user, a significantly increased number of connected devices, extremely low end-to-end latency, and support for high energy efficiency. To this end, various technologies such as dual connectivity, massive multiple input / output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being researched. [Overview of the project] [Problems that the invention aims to solve]

[0004] The technical problem addressed by this disclosure is to provide a method and apparatus for scheduling one or more downlink transmissions and / or one or more uplink transmissions using a single downlink control information.

[0005] The technical problem addressed in this disclosure is to provide a method and apparatus for sending 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 challenge of this disclosure is to provide a method and apparatus for sending and receiving HARQ-ACK codebooks when HARQ-ACK information is generated for multiple PDSCHs in predetermined groups.

[0007] The technical challenges addressed in this disclosure are not limited to those mentioned above, and other technical challenges not mentioned will be clearly understood by those with ordinary skill in the art to which this disclosure pertains from the following description. [Means for solving the problem]

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

[0010] According to embodiments of this disclosure, the transmission efficiency of scheduling downlink control information for downlink transmissions and / or uplink transmissions can be increased by using one downlink control information to support scheduling for one or more downlink transmissions and / or one or more uplink transmissions.

[0011] According to the embodiments of this disclosure, the overhead of HARQ-ACK information bits can be reduced by generating HARQ-ACK information for a plurality of PDSCHs in predetermined groups.

[0012] The effects derived from this disclosure are not limited to those mentioned above, and any other effects not mentioned above will be clearly understood by a person with ordinary skill in the art to which this disclosure pertains from the following description. [Brief explanation of the drawing]

[0013] The accompanying drawings, included as part of the detailed description to aid in understanding this disclosure, provide examples relating to this disclosure and illustrate the technical features of this disclosure together with the detailed description.

[0014] [Figure 1] This figure illustrates the structure of a wireless communication system to which this disclosure applies. [Figure 2] This figure illustrates a frame structure in a wireless communication system to which this disclosure is applicable. [Figure 3] This figure illustrates a resource grid in a wireless communication system to which this disclosure is applicable. [Figure 4] This figure illustrates a physical resource block in a wireless communication system to which this disclosure applies. [Figure 5] This figure illustrates a slot structure in a wireless communication system to which this disclosure is applicable. [Figure 6] This figure illustrates physical channels used in wireless communication systems to which this disclosure applies, and general signal transmission and reception methods using them. [Figure 7] This figure illustrates the HARQ-ACK process for downlink data in a wireless communication system to which this disclosure is applicable. [Figure 8] This figure illustrates the processing steps and structure of TB in a wireless communication system to which this disclosure is applicable. [Figure 9] This figure illustrates a CBG-based HARQ process in a wireless communication system to which this disclosure is applicable. [Figure 10] This figure illustrates a slot group-based PDCCH monitoring according to one embodiment of the present disclosure. [Figure 11] This figure illustrates the determination of a set of occasions for candidate PDSCH reception according to one embodiment of the present disclosure. [Figure 12] This figure illustrates a signaling procedure between a base station and a terminal for a control information transmission and reception method according to one embodiment of the present disclosure. [Figure 13] This figure illustrates the operation of a terminal in relation to a control information transmission and reception method according to one embodiment of the present disclosure. [Figure 14] This figure illustrates the operation of a base station with respect to a control information transmission and reception method according to one embodiment of the present disclosure. [Figure 15] This is a block diagram illustrating an example of a wireless communication device according to one embodiment of the present disclosure. [Modes for carrying out the invention]

[0015] Preferred embodiments relating to this disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of this disclosure and is not intended to represent the only possible embodiments of this disclosure. The detailed description below includes specific details to provide a complete understanding of this disclosure. However, those skilled in the art will understand that this disclosure is implementable without such specific details.

[0016] In some cases, to avoid ambiguity of the concepts in this disclosure, known structures and devices may be omitted, or they may be shown in the form of block diagrams focusing on the core function of each structure and device.

[0017] In this disclosure, when one component is “connected,” “joined,” or “linked” to another component, this can include not only a direct connection but also an indirect connection in which other components exist between them. Furthermore, in this disclosure, the terms “includes” or “have” identify the presence of the referred features, stages, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, stages, operations, elements, components and / or groups thereof.

[0018] In this disclosure, terms such as “first,” “second,” etc., are used solely to distinguish one component from another, and are not used to limit the components, nor do they limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0019] The terms used in this disclosure are for illustrative purposes relating to specific embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and in the attached claims, singular forms are intended to include plural forms unless otherwise specified in the context. The terms “and / or” used in this disclosure may refer to one of the related enumerated items, or to any and all possible combinations of two or more of them. In this disclosure, “ / ” between words has the same meaning as “and / or” unless otherwise specified.

[0020] This disclosure describes a wireless communication network or wireless communication system, where operations performed in the wireless communication network may occur in the process of a device (e.g., a base station) controlling the network and transmitting or receiving signals, or in the process of a terminal connected to the wireless network transmitting or receiving signals to or from the network.

[0021] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0022] In the following, downlink (DL) refers to communication from the base station to the terminal, and uplink (UL) refers to 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 referred to as the first communication device, and the terminal as the second communication device. The term Base Station (BS) may be replaced with terms such as fixed station, Node B, eNB (evolved-Node B), gNB (Next Generation Node B), BTS (base transceiver system), Access Point (AP), network (5G network), AI (Artificial Intelligence) system / module, RSU (roadside unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. Furthermore, the term "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 (roadside unit), robot, AI (Artificial Intelligence) module, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, and VR (Virtual Reality) device.

[0023] The following technologies may be used in various wireless connection systems such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. 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, and E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP® (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) which uses E-UTRA, and LTE-A (Advanced) / LTE-A pro are advanced versions of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-A pro.

[0024] For clarity, the explanation will be based on 3GPP communication systems (e.g., LTE-A, NR), but the technical concepts of this disclosure are not limited thereto. LTE refers to 3GPP TS (Technical Specification) 36.xxx Release 8 and later technologies. More specifically, LTE technologies from 3GPP TS 36.xxx Release 10 onwards are called LTE-A, and LTE technologies from 3GPP TS 36.xxx Release 13 onwards are called LTE-A pro. 3GPP NR refers to TS 38.xxx Release 15 and later technologies. LTE / NR may be referred to as a 3GPP system. "xxx" means the standard document detail number. LTE / NR may be referred to as a 3GPP system. For background information, terminology, abbreviations, etc., used in this disclosure, refer to the standard documents published prior to this disclosure. For example, refer to the following documents.

[0025] For 3GPP LTE, you can refer 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), and TS 36.331 (Radio Resource Control).

[0026] For 3GPP NR, you can refer 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)), and TS 38.331 (Radio Resource Control Protocol Standard).

[0027] Abbreviations of terms used in this 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] General System

[0062] As more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Massive Machine Type Communications (MTC), which connects numerous devices and things to provide various services anytime, anywhere, is also a major consideration in next-generation communications. In addition, communication system design that takes into account reliability and latency-sensitive services / terminals is being discussed. Thus, the introduction of next-generation RATs that consider eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc., is being discussed, and for convenience in this disclosure, this technology will be referred to as NR. NR is an expression representing an example of 5G RAT.

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

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

[0065] Figure 1 illustrates the structure of a wireless communication system to which this disclosure applies.

[0066] Referring to Figure 1, the NG-RAN consists of gNBs that provide control plane (RRC) protocol termination for the NG-RA (NG-Radio Access) user plane (i.e., the new AS (access stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and 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] Figure 2 illustrates a frame structure in a wireless communication system to which this disclosure is applicable.

[0068] The NR system can support a number of numerologies, which may be defined by subcarrier spacing and cyclic prefix (CP) overhead. These number of subcarrier spacings may be derived by scaling the fundamental (reference) subcarrier spacing by an integer N (or μ). Furthermore, even assuming that very low subcarrier spacings are not used at very high carrier frequencies, the numerology used may be selected independently of the frequency band. The NR system may also support various frame structures based on these number of numerologies.

[0069] The following describes the OFDM numerologies and frame structures that can be considered in the NR system. Many of the 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, an SCS of 15kHz supports wide area on traditional cellular bands, an SCS of 30kHz / 60kHz supports dense-urban areas, lower latency, and wider carrier bandwidth, and an SCS of 60kHz or higher supports bandwidths greater than 24.25GHz to overcome phase noise.

[0072] The NR frequency band is defined as a frequency range of two types (FR1 and FR2). FR1 and FR2 may be configured as shown in Table 2 below. Furthermore, FR2 can represent millimeter waves (mmW).

[0073] [Table 2]

[0074] In relation to the frame structure in an NR system, the sizes of various fields in the time domain are T c = 1 / (Δf max ·N f It is expressed as a multiple of the time unit of ). Here, Δf max =480·10 3 It is Hz, Nf = 4096. Downlink and uplink transmissions are based on 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 consists 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 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 subcarrier spacing configuration μ, a slot is numbered in increasing order of n s μ ∈{0,...,N slot subframe,μ -1} within a subframe and in increasing order of n<00​​​​​​​​​​​​​​​​​​​The start and timing are aligned. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in the downlink slot or uplink slot can be used.

[0075] Table 3 shows the number of OFDM symbols per slot in a general CP (N symb slot ), Number of slots per wireless frame (N slot frame,μ ), Number of slots per subframe (N slot subframe,μ Table 4 shows the number of OFDM symbols per slot, the number of slots per wireless frame, and the number of slots per subframe in the extended CP.

[0076] [Table 3]

[0077] [Table 4]

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

[0079] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, and carrier parts may be considered. The following describes in detail the physical resources that can be considered in an NR system.

[0080] First, in relation to antenna ports, an antenna port is defined such that the channel on which a symbol is carried on an antenna port can be inferred from the channel on which other symbols on the same antenna port are carried. If the large-scale property of the channel on which a symbol is carried on one antenna port can be inferred from the channel on which a symbol is carried on another antenna port, then the two antenna ports can be said to be in a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale property includes one or more of the following: delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0081] Figure 3 illustrates a resource grid in a wireless communication system to which this disclosure applies.

[0082] Referring to Figure 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, with one subframe being 14.2 μ This description exemplifies the use of OFDM symbols, but is not limited to them. In an NR system, the transmitted signal is N RBμ N sc RB One or more resource grids and 2 μ N symb (μ) This is explained by the OFDM symbol, where N RB μ ≤N RB max,μ The above N RB max,μ This represents the maximum transmission bandwidth, which may vary not only in terms of numerology but also between the uplink and downlink. In this case, one resource grid may be set up for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element, and is indexed to It is uniquely identified by JPEG0007896725000005.jpg10144, where k=0,...,N RB μ N sc RB -1 is an index in the frequency domain, JPEG0007896725000006.jpg12133 represents the position of a symbol within a subframe. When indicating resource elements in a slot, an index pair (k,l) is used, where l = 0, ..., N symb μ -1. Resource elements for μ and antenna port p. JPEG0007896725000007.jpg11147 is a complex value. This corresponds to JPEG0007896725000008.jpg811. When there is no risk of confusion, or when a specific antenna port or numerology is not identified, indices p and μ may be dropped, and as a result, the complex value JPEG0007896725000009.jpg912 or It could be JPEG0007896725000010.jpg912. Also, the resource block (RB) is N in the frequency domain. sc RB This is defined as a series of 12 consecutive subcarriers.

[0083] Point A acts as the common reference point for the resource block grid and is obtained as follows:

[0084] - The 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 resource block units, assuming a 15kHz subcarrier spacing for FR1 and a 60kHz subcarrier spacing for FR2.

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

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

[0087]

number

[0088] In Equation 1, k is defined relative to point A such that k=0 corresponds to a subcarrier centered at point A. The physical resource block ranges from 0 to N within the bandwidth part (BWP). BWP,i size,μ The numbers are assigned down to -1, where i is the BWP number. In BWP i, the physical resource block n PRB and common resource block n CRB The relationship between them is given by equation 2 below.

[0089]

number

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

[0091] Figure 4 illustrates a physical resource block in a wireless communication system to which this disclosure applies. Figure 5 illustrates a slot structure in a wireless communication system to which this disclosure applies.

[0092] Referring to Figures 4 and 5, a slot contains multiple symbols in the time domain. For example, in a general CP, one slot contains seven symbols, while in an extended CP, one slot contains six symbols.

[0093] A carrier wave contains multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) is defined as multiple consecutive (physical) resource blocks in the frequency domain and can correspond to a single numerology (e.g., SCS, CP length, etc.). A carrier wave can contain up to N (e.g., 5) BWPs. Data communication takes place over activated BWPs, and only one BWP may be activated for a single terminal. In a resource grid, each element is called a resource element (RE) and may be mapped to a single complex symbol.

[0094] An NR system may support up to 400 MHz per component carrier (CC). If a terminal operating on such a wideband CC keeps its radio frequency (RF) chip on for the entire CC at all times, terminal battery consumption may increase. Alternatively, considering various use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing) may be supported for each frequency band within that CC. Alternatively, terminals may have different capabilities for the maximum bandwidth. Taking this into consideration, a base station may instruct terminals to operate only on a portion of the wideband CC's bandwidth rather than the entire bandwidth, and this portion of the bandwidth is conveniently defined as a bandwidth part (BWP). A BWP may consist of consecutive RBs on the frequency axis and may correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / minislot interval).

[0095] On the other hand, a base station can configure multiple BWPs within a single CC configured on a terminal. For example, a PDCCH monitoring slot can be configured with a BWP occupying a relatively small frequency range, while a PDSCH instructed by the PDCCH may be scheduled on a larger BWP. Alternatively, if UEs are concentrated on a particular BWP, other BWPs may be configured on some terminals for load balancing. Or, considering frequency domain inter-cell interference cancellation between adjacent cells, a portion of the spectrum of the total bandwidth can be excluded, and both BWPs can be configured within the same slot. In other words, a base station can configure at least one DL / UL BWP on terminals associated with a broadband CC. A base station can activate at least one DL / UL BWP among those configured at a given time (by L1 signaling, MAC CE (Control Element), or RRC signaling, etc.). Furthermore, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, or RRC signaling, etc.). Alternatively, it may switch to a designated DL / UL BWP when a timer expires. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, in situations such as when a terminal is in the initial access process or before the RRC connection is set up, the configuration for the DL / UL BWP may not be received. In such situations, the DL / UL BWP assumed by the terminal is defined as the initial active DL / UL BWP.

[0096] Figure 6 illustrates physical channels used in wireless communication systems to which this disclosure applies, and general signal transmission and reception methods using them.

[0097] In wireless communication systems, a terminal receives information from a base station via the downlink and transmits information to the base station via the uplink. The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information being transmitted and received.

[0098] When a terminal is powered on or enters a new cell, it performs an initial cell search (S601), including synchronizing with the base station. To do this, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and obtain information such as the cell identifier (ID). Subsequently, the terminal receives the physical broadcast channel (PBCH) from the base station to obtain intra-cell broadcast information. Meanwhile, during the initial cell search phase, the terminal can receive a downlink reference signal (DL RS) to check the downlink channel status.

[0099] Once the terminal has completed its initial cell search, it can receive the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) via the information carried on the PDCCH, thereby obtaining more specific system information (S602).

[0100] On the other hand, if the terminal is initially connected to a base station or does not have radio resources for signal transmission, it can perform a Random Access Procedure (RACH) to the base station (stages S603 to S606). To do this, 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 to the preamble on the PDCCH and the corresponding PDSCH (S604 and S606). In the case of a conflict-based RACH, a Contention Resolution Procedure can also be performed.

[0101] A terminal that has performed the procedures described above can then perform general uplink / downlink signal transmission procedures, such as receiving PDCCH / PDSCH (S607) and transmitting Physical Uplink Shared Channel (PUSCH) / Physical Uplink Control Channel (PUCCH) (S608). In particular, the terminal receives Downlink Control Information (DCI) via PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format differs depending on its purpose of use.

[0102] On the other hand, control information that a terminal transmits to or receives from a base station on the uplink 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 the above-mentioned control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0103] Table 5 shows an example of the 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.), Transport Block (TB) 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.), multiplex antenna related information (e.g., DMRS sequence initialization information, antenna ports, CSI requests, etc.), and power control information (e.g., PUSCH power control, etc.). The control information included in each DCI format may be predefined.

[0106] DCI format 0_0 is used for scheduling PUSCH within a single cell. The information contained in DCI format 0_0 is scrambled using CRC (cyclic redundancy check) by C-RNTI (Cell RNTI: Cell Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) before transmission.

[0107] DCI format 0_1 ​​is used to instruct terminals to schedule one or more pushes in a single cell, or to provide configured grant (CG) downlink feedback information. The information contained in DCI format 0_1 ​​is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.

[0108] DCI format 0_2 is used for scheduling pushes within a single cell. The information contained in DCI format 0_2 is CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI before transmission.

[0109] Next, DCI formats 1_0, 1_1, and 1_2 may 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.), multiplex antenna related information (e.g., antenna ports, TCI (transmission configuration indicator), SRS (sounding reference signal) requests, etc.), and PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be predefined.

[0110] DCI format 1_0 is used for PDSCH scheduling within a single DL cell. The information contained in DCI format 1_0 is CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI before transmission.

[0111] DCI format 1_1 is used for PDSCH scheduling within a single cell. The information contained in DCI format 1_1 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0112] DCI format 1_2 is used for PDSCH scheduling within a single cell. The information contained in DCI format 1_2 is transmitted after being CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

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

[0114] Figure 7 illustrates the HARQ-ACK process for downlink data in a wireless communication system to which this disclosure is applicable.

[0115] Referring to Figure 7, the terminal can detect the PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 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 format 1_0, 1_1 may include the following information:

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

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

[0118] - PDSCH-to-HARQ feedback timing indicator: K1 is indicated.

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

[0120] - PUCCH resource indicator (PRI): Specifies the PUCCH resource to be used for UCI transmission from among multiple PUCCH resources in the PUCCH resource set.

[0121] Subsequently, after the terminal receives a PDSCH at slot #(n+K0) according to the scheduling information for slot #n, it can transmit a UCI using PUCCH at slot #(n+K1). Here, the UCI includes a HARQ-ACK response to the PDSCH. If the PDSCH is configured to transmit up to one TB, the HARQ-ACK response may consist of 1 bit. If the PDSCH is configured to transmit up to two TBs, the HARQ-ACK response may consist of 2 bits if spatial bundling is not configured, and 1 bit if spatial bundling is configured. If the time for transmitting HARQ-ACKs to multiple PDSCHs is specified as slot #(n+K1), the UCI transmitted at slot #(n+K1) includes HARQ-ACK responses to multiple PDSCHs.

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

[0123] LTE supports TB (Transport Block) based HARQ processes. NR supports both TB-based and CBG-based HARQ processes.

[0124] Figure 8 illustrates the processing steps and structure of a TB in a wireless communication system to which this disclosure is applicable.

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

[0126] Referring to Figure 8, the transmitter adds a CRC (e.g., 24 bits) (TB CRC) to the TB for error checking. The transmitter can then divide the TB+CRC into multiple code blocks, taking into account the size of the channel encoder. For example, in LTE, the maximum size of a code block is 6144 bits. Therefore, if the TB size is 6144 bits or less, no code block is formed. If the TB size is greater than 6144 bits, the TB is divided into 6144-bit units, forming multiple code blocks. Each code block is individually added with a CRC (e.g., 24 bits) (CB CRC) for error checking. After channel coding and rate matching, each code block is combined to form a codeword. 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] Figure 9 illustrates a CBG-based HARQ process in a wireless communication system to which this disclosure is applicable.

[0128] In a CBG-based HARQ process, data scheduling and the resulting HARQ process may be performed on a CBG basis.

[0129] Referring to Figure 9, the terminal can receive information from the base station regarding the number of code block groups M per transmission block via a higher-layer signal (e.g., an RRC signal) (S1602). Subsequently, the terminal can receive an initial data transmission from the base station (by PDSCH) (S1604). Here, the data includes a transmission block, each transmission block includes multiple code blocks, and these multiple code blocks may be divided into one or more code block groups. Here, some of the code block groups may contain ceiling (K / M) code blocks, and the remaining code blocks may contain flooring (K / M) code blocks. K represents the number of code blocks in the data. Subsequently, the terminal can feed back code block group-based A / N information to the base station for the data (S1606), and the base station can retransmit the data based on the code block groups (S1608). The A / N information may be transmitted by PUCCH or PUSCH. Here, the A / N information includes multiple A / N bits for the data, each A / N bit representing a specific A / N response generated for each code block group in relation to the data. The payload size of the A / N information may be kept constant based on M, regardless of the number of code block groups that make up the data.

[0130] Dynamic / Semi-static HARQ-ACK Codebook System

[0131] NR supports both dynamic and quasi-static HARQ-ACK codebook methods. The HARQ-ACK (or A / N) codebook may be replaced by the HARQ-ACK payload.

[0132] When the dynamic HARQ-ACK codebook scheme is configured, the A / N payload size changes according to the actual number of DL data items scheduled. For this reason, 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 using the CC (Component Carrier) (or cell) first scheme and is used to specify the position of the A / N bits in the A / N codebook. The total DAI indicates the slot-unit scheduling cumulative value up to the current slot and is used to determine the size of the A / N codebook.

[0133] When a quasi-static A / N codebook scheme is configured, the size of the A / N codebook is fixed (to its maximum value) regardless of the actual number of DL data scheduled. Specifically, the (maximum) A / N payload (size) transmitted by one PUCCH in one slot may be determined to be the number of A / N bits corresponding to all combinations (hereinafter referred to as the bundling window) of all CCs set on the terminal and all DL scheduling slots (or PDSCH transmission slots or PDCCH monitoring slots) in which the A / N transmission timing can be indicated. For example, a DL grant DCI (PDCCH) contains PDSCH-to-A / N timing information, and the PDSCH-to-A / N timing information can have one of several values ​​(e.g., k). For example, if a PDSCH is received in slot #m and the PDSCH-to-A / N timing information in the DL grant DCI (PDCCH) that schedules the PDSCH indicates k, the A / N information for the PDSCH may be transmitted in slot #(m+k). For example, k may be given as {1, 2, 3, 4, 5, 6, 7, 8}. On the other hand, when 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 #(nk). 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 / Ns). Here, the A / N information may be replaced with an A / N codebook or an A / N payload. Also, a slot may be understood / replaced with a candidate opportunity for DL ​​data reception. As illustrated, the bundling window is determined based on the PDSCH-to-A / N timing relative 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 configurations defined in the NR standard are as follows: When the UE is set to the semi-static PDSCH HARQ-ACK codebook parameter, the UE decides to report a Type-1 HARQ-ACK codebook (i.e., a semi-static HARQ-ACK codebook). On the other hand, when the UE is set to the dynamically set PDSCH HARQ-ACK codebook (or pdsch-HARQ-ACK-Codebook-r16) parameter, the UE decides to report a Type-2 HARQ-ACK codebook (i.e., a dynamic HARQ-ACK codebook).

[0135] HARQ-ACK codebook configuration method for multiple PDSCH scheduling

[0136] - PUSCH: Physical Uplink Shared Channel

[0137] - RRM: Radio Resource Management

[0138] - SCS: Subcarrier 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 (This is an indicator value for the starting symbol index and the number of symbols within a slot of a PDSCH and / or PUSCH. It may be set as a component of an entry that constitutes a TDRA field within the PDCCH that schedules the said PDSCH and / or PUSCH.)

[0146] - BWP: Bandwidth Part (may consist of a contiguous resource block (RB) on the frequency axis. It can correspond to a single numerology (e.g., SCS, CP length, slot / mini-slot duration). Multiple BWPs may be configured on a single carrier (the number of BWPs per carrier may also be limited), but the number of activated BWPs may be limited to a portion of them per carrier (e.g., one).)

[0147] - CORESET: Control Resource Set (This refers to the time-frequency resource area in which 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 specifies the symbol level DL / UL direction within a specific slot, transmitted via 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, average spread, and spatial Rx parameter obtained from one RS may also be applied to another RS ​​(or the antenna port of that RS). In an NR system, four QCL types are defined as follows: "type A": {Doppler shift, Doppler spread, average delay, delay spread}, "type B": {Doppler shift, Doppler spread}, "type C": {Doppler shift, average delay}, "type D": {Spatial Rx parameter}. For a given DL RS antenna port, the first DL RS is 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 to QCL type Y (Y = A, B, C, or D, where X ≠ Y).

[0153] - TCI: Transmission Configuration Indication (A single TCI state includes a QCL relationship between one or more DL RSs, such as a PDSCH DM-RS port, a PDCCH DM-RS port, or a CSI-RS resource's CSI-RS port. For the "Transmission Configuration Indication" field within the DCI that schedules the PDSCH, the TCI state index corresponding to each code point constituting that field is activated by a 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, this TCI state is set between DL RSs, but in subsequent releases, setting between DL RSs and UL RSs or between UL RSs may be permitted. Examples of UL RSs include SRS, PUSCH DM-RS, and PUCCH DM-RS.)

[0154] - SRI: SRS resource indicator (This indicates one of the SRS resource index values ​​set in the "SRS resource indicator" field within the DCI that schedules the PUSCH. When a terminal transmits a PUSCH, it can use the same spatial domain transmission filter used for sending and receiving reference signals linked to that SRS resource. Here, a reference RS is set by RRC signaling using the SRS-SpatialRelationInfo parameter for each SRS resource, and the reference RS may be an SS / PBCH block, CSI-RS, or SRS.)

[0155] - TRP: Transmission and Reception Point

[0156] To increase the transmission efficiency of scheduling DCIs for PDSCHs and / or PUSCHs, a single DCI may support multiple PDSCH (or PUSCH) transmissions. For convenience, in this disclosure, such DCIs are referred to as M-DCIs, and DCIs that schedule a single PDSCH (or PUSCH) are referred to as S-DCIs.

[0157] For example, scheduling for multiple PDSCH (or PUSCH) transmissions may be configured at a terminal by higher-layer signaling (e.g., RRC signaling) using a single DCI. For each of the one or more serving cells configured at a terminal, it may be configured whether or not scheduling for multiple PDSCH (or PUSCH) transmissions is performed using a single DCI. For example, if information for configuring scheduling for multiple PDSCH (or PUSCH) transmissions is provided to the serving cell using a single DCI, then scheduling for multiple PDSCH (or PUSCH) transmissions may be configured / supported on that cell using a single DCI. On the other hand, if information for configuring scheduling for multiple PDSCH (or PUSCH) transmissions is not provided to the serving cell using a single DCI, then scheduling for multiple PDSCH (or PUSCH) transmissions may not be configured / supported on that cell using a single DCI.

[0158] Here, even with M-DCI, depending on the circumstances, only a single PDSCH may be scheduled, or multiple PDSCHs may be scheduled. For example, when configuring a TDRA entry in M-DCI, only one SLIV may be linked to a row index #A, while multiple SLIVs may be linked to a row index #B. In this case, when row index #A is specified in M-DCI, it means that only a single PDSCH will be scheduled in that DCI, while when row index #B is specified in M-DCI, it means that multiple PDSCHs will be scheduled in that DCI. For convenience, when a PDSCH is scheduled in S-DCI or when only one PDSCH is scheduled in M-DCI (or when SPS PDSCH release or SCell dormancy is indicated in DCI), it is called a single-PDSCH case, and when multiple PDSCHs are scheduled in M-DCI, it is called a multi-PDSCH case.

[0159] Therefore, in this disclosure, we propose a type-1 (i.e., semi-static) or type-2 (i.e., dynamic) HARQ-ACK codebook (HCB) configuration method that takes into account the multiple PDSCH case.

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

[0161] In high-frequency NR systems (for example, those exceeding 52.6 GHz up to 71 GHz, which for convenience of explanation will be named FR3 (or FR2-2)), larger SCSs may be introduced. Assuming that the scalability of the OFDM symbol interval (duration) and CP length defined in the current NR system is maintained, the lengths shown in Table 6 below may be defined as OFDM symbol intervals and CP lengths for each SCS.

[0162] [Table 6]

[0163] In the FR3 (or FR2-2) frequency band, PDCCH monitoring may be performed in one slot per multiple slots, taking into consideration the monitoring capability of the terminal. To account for the reduced monitoring occasion area resulting from this, an operation may be introduced in which multiple PDSCHs and / or multiple PUSCHs are scheduled by a single DCI. However, the PDSCHs and / or PUSCHs instructed by such a DCI may also be instructed to be transmitted in other frequency ranges besides FR3 (or FR2-2). In other words, the M-DCI proposed in this disclosure is not limited to NR systems operating in FR3 (or FR2-2), but may be applied in other frequency ranges as well.

[0164] Example 1: Time bundling setting method

[0165] Considering the 480 / 960kHz SCS introduced in the FR3 band, the absolute time of multiple PDSCHs can be very short, especially when multiple PDSCHs are scheduled in multiple slot areas by M-DCI. Therefore, the channel may not change significantly within that time interval (or multiple PDSCHs), and the decoding success / failure results for multiple PDSCHs may be identical. If a time bundling interval is set taking this into consideration, the HARQ-ACK payload can be reduced by bundling (i.e., performing a logical AND operation on) the HARQ-ACK results within that interval. Therefore, we propose a specific time bundling method.

[0166] In other words, when HARQ time bundling is set up 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 bundling groups, HARQ groups, or HARQ bundling groups, etc.), and HARQ-ACK information may be generated for each of the one or more groups.

[0167] For example, time bundling may be configured on a terminal by higher-layer signaling (e.g., RRC signaling). The presence or absence of time bundling may be configured for each of the one or more serving cells configured on the terminal. For example, if information for configuring time bundling is provided to the serving cell, time bundling may be configured / supported for multiple PDSCHs scheduled on that cell. On the other hand, if information for configuring time bundling is not provided to the serving cell, time bundling may not be configured / supported for multiple PDSCHs scheduled on that cell.

[0168] For convenience of explanation, this disclosure refers to the bundling of HARQ-ACK information for multiple PDSCHs as time bundling, but this disclosure is not limited to this term, and other names such as HARQ bundling or HARQ-ACK bundling may be used.

[0169] - Method 1: We 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 multi-PDSCH cases involving M (where M is a natural number) or fewer PDSCHs, the PDSCHs may be bundled into one group, and for multi-PDSCH cases involving more than M PDSCHs, the PDSCHs may be bundled into two groups. Here, the value of M may be half 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, if the actual number of scheduled PDSCHs is N (>M), the first M PDSCHs (for example, the first M PDSCHs in the time domain) may be bundled into group 1, and the remaining NM PDSCHs may be bundled into group 2. Alternatively, 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: We propose a time bundling method based on the number of slots occupied by each PDSCH. That is, multiple PDSCHs are bundled (grouped) into one or more groups based on a predetermined number of PDSCH slots.

[0172] Specifically, for multiple PDSCH cases with L (where L is a natural number) or fewer slots, the PDSCHs may be bundled into one group, and for multiple PDSCH cases with more than L slots, the PDSCHs may be bundled into two groups. Here, the L value may be half of the maximum number of PDSCH slots that the M-DCI set in the cell (or among all cells set in the terminal) can schedule (i.e., the maximum value of 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 calculation, ceiling calculation, rounding, etc.). Alternatively, the L value may be set by higher layer signaling. Specifically, if the slot interval from the first scheduled PDSCH slot to the last PDSCH slot is K slots (>L), the PDSCHs in the first L slot interval may be bundled into group 1, and the PDSCHs in the remaining KL slot intervals may be bundled into group 2. Alternatively, the PDSCHs in the first ceil(K / 2) slot intervals may be bundled into group 1, and the PDSCHs in the remaining floor(K / 2) slot intervals may be bundled into group 2.

[0173] - Method 3: Regardless of the number of PDSCHs and slots, multiple PDSCHs may always be time-bundled into groups of two. If the actual number of 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 to define G (where G is a natural number) groups, and multiple PDSCHs can be time-bundled (or grouped) into these G groups. Here, each PDSCH can be mapped to a group in the order it is scheduled (or valid) (in ascending order of group index) (in other words, multiple PDSCHs can be mapped to each group in chronological order, and this process can be repeated cyclically until all PDSCHs are mapped to a group). For example, if five PDSCHs are scheduled (or valid) by one DCI and G=4, then PDSCH #0 / 4 can correspond 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 a symbol (or a slot containing such a symbol) that has been set to uplink (or flexible) by a parameter for TDD UL-DL common configuration (e.g., tdd-UL-DL-ConfigurationCommon) or a parameter for TDD UL-DL specific configuration (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 PDSCHs are mapped to bundling groups in the scheduled PDSCH order (i.e., regardless of PDSCH validity), a particular bundling group may contain a mixture of valid and invalid PDSCHs (both belonging to it), or it may contain only invalid PDSCHs. If a particular bundling group contains a mixture of valid and invalid PDSCHs (both belonging to it), the terminal can treat the invalid PDSCHs as ACKs and perform a logical AND operation on that bundling group. However, if a particular bundling group contains only invalid PDSCHs, the terminal may treat those invalid PDSCHs as NACKs, or the HARQ-ACK information corresponding to that bundling group may be treated as NACKs. For example, in the above example, 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 particular bundling group), the HARQ-ACK information corresponding to PDSCH#4 may be considered an ACK. As another example, assuming that PDSCH#1 mapped to group #1 in the above example is an invalid PDSCH (i.e., only invalid PDSCHs exist in a particular bundling group), the HARQ-ACK information corresponding to PDSCH#1 may be considered a NACK, or the HARQ-ACK information corresponding to group #1 may be considered a NACK.

[0176] Methods 1-3 described above primarily focus on the case where the number of groups is 2 for the sake of explanation, but the same methods can be extended to cases where the number of groups is greater than 2 or 1.

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

[0178] When the number of HARQ - bundling groups (numberOfHARQ - BundlingGroups) is set for the serving cell c by the UE (that is, 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: transport block group) 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 setting it like this, within the 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. 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 of the PDSCH 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 (that is, N CBG / TB,max HARQ-ACKThe number of maximum CBGs per transport block (maxCodeBlockGroupsPerTransportBlock) indicating

[0180] For the number C of code blocks (CBs) within a transport block, the UE determines the number M of CBGs and the number N of HARQ-ACK bits for the transport block 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 a CBG, it generates a NACK for the HARQ-ACK information bits of the CBG. If the UE receives two transport blocks, the UE concatenates the HARQ-ACK information bits for the CBGs of the second transport block after the HARQ-ACK information bits for the CBGs of the first transport block.

[0182] The HARQ-ACK codebook contains N CBG / TB,max HARQ-ACK HARQ-ACK information bits and for a transport block, if N CBG / TB HARQ-ACK <N CBG / TB,max HARQ-ACK then 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 transport block within the HARQ-ACK codebook.

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

[0184] If the UE correctly detects each of N CBG / TB HARQ-ACK CBGs but N CBG / TBHARQ-ACK If TB cannot be accurately detected for each CBG, the UE will be N CBG / TB HARQ-ACK A NACK value is generated for each CBG.

[0185] On the other hand, in the generation of a bundled group, as mentioned above, the bundled group may be generated based on a pre-configured SLIV linked to the TDRA information instructed by DCI. Here, if a particular bundled group may contain a mixture of valid and invalid PDSCHs (both may belong to it), or if only invalid PDSCHs may exist, the method for generating HARQ-ACKs for that bundled group needs to be defined. Here, a valid PDSCH can mean a PDSCH that does not overlap with a symbol (or a slot containing such a symbol) that has been set as an uplink (or flexible) by a parameter for TDD UL-DL common configuration (e.g., tdd-UL-DL-ConfigurationCommon) or a parameter for TDD UL-DL specific configuration (e.g., tdd-UL-DL-ConfigurationDedicated). On the other hand, an invalid PDSCH can mean a PDSCH that overlaps with a symbol (or a slot containing such a symbol) that is set as uplink (or flexible) by a parameter for common TDD UL-DL configuration (e.g., tdd-UL-DL-ConfigurationCommon) or a parameter for TDD UL-DL-specific configuration (e.g., tdd-UL-DL-ConfigurationDedicated). If a particular bundling group contains both valid and invalid PDSCHs (i.e., both belong to it), it is preferable that the HARQ-ACK information corresponding to that bundling group generates ACK information when all valid PDSCHs belonging to that bundling group are accurately received, and generates a NACK in other cases (i.e., when even one of the valid PDSCHs belonging to that bundling group is not accurately received). In other words, in the generation of HARQ-ACK information corresponding to the bundling group (to which both valid and invalid PDSCHs belong),

[0186] Alternative (Alt) 1: Consider (or assume) that invalid PDSCHs were received correctly,

[0187] Alt 2: It is preferable to ignore invalid PDSCHs.

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

[0189] Alt 1: When the number of HARQ-BundlingGroups for serving cell c is set in 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, N is the maximum number of PDSCH receptions scheduled in DCI format on the serving cell. max PDSCH For this, the maximum number of TBGs N TBG,max HARQ-ACK,c This is provided by numberOfHARQ-BundlingGroups. UE is N on serving cell c. PDSCH,c When the UE detects a DCI format that schedules individual PDSCH receptions, N CBG / TB,max HARQ-ACK =N TBG,max HARQ-ACK,c and C=N PDSCH,c By setting it as such, and assuming that a PDSCH that overlaps with a UL symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for a TBG in at least one actual PDSCH reception is accurately received, N PDSCH,c N for 1TB within a single PDSCH receiver TBG,max HARQ-ACK,c Generates a number of HARQ-ACK information bits for the second TB. TBG,max HARQ-ACK,c Generates individual HARQ-ACK information bits.

[0190] Alt 2: When the number of HARQ-BundlingGroups is set for serving cell c in 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, N is the maximum number of PDSCH receptions scheduled in DCI format on the serving cell. max PDSCH For this, the maximum number of TBGs N TBG,max HARQ-ACK,c This is provided by numberOfHARQ-BundlingGroups. UE is N on serving cell c. PDSCH,c When the UE detects a DCI format that schedules individual PDSCH receptions, N CBG / TB,max HARQ-ACK =N TBG,max HARQ-ACK,c and C=N PDSCH,c By setting it as such, and by ignoring PDSCHs that overlap with UL symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated for TBG in at least one actual PDSCH receive, N PDSCH,c N for 1TB within a single PDSCH receiver TBG,max HARQ-ACK,c Generates a number of HARQ-ACK information bits for the second TB. TBG,max HARQ-ACK,c Generates the number of HARQ-ACK information bits.

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

[0192] The HARQ-ACK timing (slot) may be determined by applying the K1 value (as indicated by the DCI) (in this disclosure, K1 means the slot interval between the PDSCH transmission slot and the HARQ-ACK transmission slot for the reception of the PDSCH) relative to the last PDSCH transmission slot (in time) among the multiple PDSCHs scheduled by the M-DCI. Based on this, the HARQ-ACK feedback for all of the multiple PDSCHs scheduled by the DCI may be transmitted collectively in that (single) HARQ-ACK timing.

[0193] As a result, HARQ-ACK feedback is multiplexed (i.e., HARQ-ACK information bits are included in one codebook) only between M-DCIs (and S-DCIs that indicate the same slot as the HARQ-ACK time (slot) corresponding to the last PDSCH transmission slot as the HARQ-ACK time) (and S-DCIs that indicate the same slot as the HARQ-ACK time (slot) corresponding to the last PDSCH transmission slot as the HARQ-ACK time) (for all PDSCHs scheduled by the DCI), and may be transmitted in the same single HARQ-ACK time.

[0194] On the other hand, in the case of an existing Type-1 HCB with a set of K1 values ​​for multiple candidates (e.g., K_N), the terminal calculates all possible combinations of PDSCH occasions (SLIVs) that can be transmitted within the K1 DL slots prior to the HARQ-ACK transmission slot for each K1 value (set for each cell in that cell). The terminal then constructs an occasion for receiving a candidate PDSCH corresponding to each DL slot (including determining the HARQ-ACK bit position / order corresponding to each SLIV) (this is defined as "SLIV pruning"). For each occasion included in the set of occasions for receiving a candidate PDSCH obtained through this process, HARQ-ACK information bits are constructed, and these HARQ-ACK information bits can be concatenated to construct the overall HARQ-ACK codebook.

[0195] In other words, after setting up multiple candidate HARQ timings in advance by RRC signaling, the base station can instruct a terminal to select one of the candidate HARQ timings via (DL grant) DCI. In this case, the terminal can operate to transmit A / N feedback for (multiple) PDSCH receptions in multiple slots (or sets of slots) corresponding to the overall candidate HARQ timing set at the instructed HARQ timing. Here, HARQ timing means PDSCH-to-A / N timing / interval. HARQ timing may be expressed on a slot basis. For example, if A / N transmission is instructed to be in slot #m, the A / N information may include response information for PDSCH reception in slot #(mi). Here, slot #(mi) corresponds to the slot corresponding to the candidate HARQ timing. Here, if the candidate HARQ timing is set to i={2,3,4,5}, and the A / N transmission time is instructed to be #(n+5)(=m), the terminal can generate / transmit A / N information for PDSCH reception in slots #n~#(n+3)(=mi) (i.e., A / N feedback for all four slots). Here, the A / N response for PDSCH reception in slots #n+1 / #n+3 may be processed as a NACK.

[0196] Some of the standards related to this are as follows:

[0197] In serving cell c, the activated DL BWP and the activated UL BWP, the UE is in slot n U M for candidate PDSCH reception that can transmit the HARQ-ACK information in PUCCH A,C Determine the set of occasions. When serving cell c is deactivated, M for candidate PDSCH reception. A,C The DL BWP provided by firstActiveDownlinkBWP-Id is used as the activated DL BWP to determine the set of opportunities. The determination is based on the following:

[0198] a) The above 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 PDCCH for DCI format 1_0 on serving cell c, and not to monitor PDCCH for DCI format 1_1 or DCI format 1_2, then K1 will be provided by slot timing values ​​{1, 2, 3, 4, 5, 6, 7, 8}.

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

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

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

[0203] b) The determination is based on a set of row indexes R of a table that, in conjunction with the activated DL BWP, defines the respective sets of slot offset K0 and SLIV (start and length indicators), and the PDSCH mapping type for receiving the PDSCH. Here, the row indexes R of the table are provided as the union of row indexes of the time domain resource allocation table for the DCI format configured for the UE to monitor the PDCCH for serving cell c.

[0204] - When referenceOfSLIVDCI-1-2 is provided to the UE, in each row index in the set of row indexes of a table for DCI format 1_2 that has slot offset K0=0 and PDSCH mapping type B, if the starting symbol S0>0 and for each PDCCH monitoring occasion in the set of PDCCH monitoring occasions that have different starting symbols in slots monitoring PDCCH for DCI format 1_2, if S+S0+L≦14 for a normal cyclic prefix and S+S0+L≦12 for an extended cyclic prefix, the UE replaces the starting symbol S of the row index in the set of row indexes of the table with S+S0 and adds a new row index.

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

[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 reception that can transmit the HARQ-ACK information in PUCCH in a particular slot may be determined based only on the last SLIV of each row in the TDRA table. For example, one or more rows in the TDRA table may be specified with multiple SLIV values ​​for scheduling multiple PDSCHs. For example, row index 2 may be set / defined as {SLIV1, SLIV2, SLIV3}, row index 3 as {SLIV4, SLIV5}. In this case, the set of occasions for candidate PDSCH reception may be determined based only on the last SLIV of each row in the TDRA table. That is, the set of occasions for candidate PDSCH reception may be determined by considering only row index 2 as {SLIV3} and row index 3 as {SLIV5}.

[0207] After SLIV pruning is performed on each DL slot corresponding to each K1 within a set of multiple candidate K1 values ​​(i.e., slot n-K1 if a HARQ-ACK is sent in slot n), if even one of the TDRA row indexes corresponding to that K1 requires sending a HARQ-ACK to G groups, then (G-1) occasions may be added to the SLIV pruning result. For example, if G=1, then no occasions may be added to the SLIV pruning result.

[0208] For example, the TDRA item (entry) for M-DCI in a specific cell can be as follows:

[0209] - Row index #0: 5 SLIV values ​​are linked (coordinated), and the last SLIV = {S=0,L=5}

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

[0211] Furthermore, the TDRA entry for S-DCI in the cell in question can be as follows:

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

[0213] If SLIV pruning (i.e., determination of the set of opportunities for candidate PDSCH reception) is performed on a specific DL slot corresponding to a specific K1 in that cell based only on the last SLIV, then two opportunities for candidate PDSCH reception may be assigned to that DL slot (for example, one opportunity for candidate PDSCH reception by M-DCI and one opportunity for candidate PDSCH reception by S-DCI).

[0214] Suppose two time-bundling groups are set up 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 the candidate PDSCH (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, the second opportunity may be filled with NACK (since there is no PDSCH corresponding to the second group). 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 a candidate PDSCH (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 a group for two time bundlings is set as in Method 1 of the above Example 1 and M = 4 is set. In this case, when the 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 the 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 row index #0 requires at least two groups, the final DL slot may have three opportunities for receiving candidate PDSCHs (for example, two opportunities for receiving candidate PDSCHs by M-DCI (for each group), and one opportunity for receiving PDSCHs by S-DCI). If row index #0 or 1 for M-DCI is actually scheduled, the first and third opportunities within that opportunity may be associated with HARQ-ACK information, where, in the case of row index #1, the third opportunity may be filled with NACK (because there is no PDSCH corresponding to the second group). If row index #0 for S-DCI is scheduled, the second opportunity may be associated with HARQ-ACK information. That is, according to SLIV pruning performed based only on the last SLIV, an opportunity is first assigned to row index #0 for S-DCI, and then row index #0 / 1 for M-DCI is assigned to the next opportunity, so a total of two opportunities may be formed. Here, the opportunity due to 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, then HARQ-ACK information corresponds to the opportunity for candidate PDSCH reception by M-DCI, and if there is an opportunity due to time bundling in the opportunity for candidate PDSCH reception by M-DCI, HARQ-ACK information may correspond to it first.

[0224] Example 3: Type-1 HCB configuration method when slot-group based PDCCH monitoring is configured.

[0225] With the introduction of higher SCS such as 480 / 960kHz, performing PDCCH monitoring for each slot can become a burden on terminal implementation. Considering this, slot-group based PDCCH monitoring may be introduced.

[0226] Figure 10 illustrates a slot group-based PDCCH monitoring according to one embodiment of the present disclosure.

[0227] Referring to Figure 10, four slots (i.e., Gr=4) are defined as one slot group, and PDCCH monitoring may be restricted to only a portion of the area within that slot group (e.g., the first slot). Such slot groups may be predefined (per SCS), set by upper-layer signaling, or be values ​​derived by the terminal from the search space set setting. Furthermore, such slot groups may be used as a criterion for calculating the maximum number of PDCCH candidates and / or the maximum number of non-overlapped control channel elements (CCEs), or may be used as a criterion for dropping the search space set based on that number criterion.

[0228] In this embodiment, SLIV pruning may be performed on the entire slot group rather than on the specific DL slot corresponding to a specific K1 for the cell in question. Here, for a multiple PDSCH case in which a specific slot within the slot group is the first PDSCH slot, a scheduling restriction may be set / defined that schedules must be limited to within the same slot group. That is, for a multiple PDSCH case in which a specific slot within the nth slot group is the first PDSCH slot, all PDSCHs scheduled by the corresponding M-DCI must belong to the nth slot group, and no PDSCH should be scheduled to belong to the (n+1)th slot group. In other words, when multiple PDSCHs are scheduled by the M-DCI, all of the multiple PDSCHs must be scheduled within a single slot group.

[0229] Specifically, SLIV pruning may be performed on all slots belonging to the slot group in which the slot designated by each K1 is the last slot.

[0230] Figure 11 illustrates the determination of a set of occasions for candidate PDSCH reception according to one embodiment of the present disclosure.

[0231] Referring to Figure 11, this is an example of SLIV pruning corresponding to slot group #1, where slot #9 is the UL slot to which the HARQ-ACK is sent, the K1 set = {2, 3, 4, 5, 6, 7}, and the TDRA entries for M-DCI are set as row indices #0, #1, and #2. 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 slot group #1. That is, the row indices corresponding to K1 = 2 / 3 / 4 / 5 may be aligned as shown in Figure 11 (under the aforementioned scheduling constraint). The SLIV pruning process may be performed on the entire 9 SLIV sequences corresponding to slot group #1 (replacing existing slots with slot groups, and on the entire 56 symbols within those slot groups). As a result, slot group #1 may be allocated 4 opportunities. If M-DCI actually schedules up to three PDSCHs from slot #5 to row index #0, then the second, third, and fourth opportunities in that instance may correspond to each PDSCH.

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

[0233] In existing S-DCI systems, the counter DAI (C-DAI) and total DAI (T-DAI) are counted one for each DCI or each PDSCH. On the other hand, in M-DCI, there may be multiple PDSCHs corresponding to a single DCI, so the method for counting DAI values ​​may differ, and the following methods may be considered.

[0234] - Alt 1: Count DAI (C-DAI and T-DAI) by DCI.

[0235] - Alt 2: Count DAI (C-DAI and T-DAI) by PDSCH.

[0236] Here, if at least one symbol of a particular PDSCH among several scheduled PDSCHs overlaps with a UL symbol set in higher-layer (e.g., RRC) signaling, that PDSCH does not need to be transmitted. In this case, the DAI for that PDSCH may be omitted from the count.

[0237] - Alt 3: Count the DAI values ​​for each of the W PDSCHs (W is a natural number), where the value of W may be set by higher-level signaling (e.g., RRC) (or it may be a fixed value beforehand).

[0238] Here, it is preferable that the W value be set to a common value for all cells when M-DCI is set for multiple cells within the same cell group. This is because aligning the HARQ-ACK configuration units between cells eliminates ambiguity even if a specific DCI is missing.

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

[0240] Also, for each alternative, for the single PDSCH case and the multi-PDSCH case, a method for constructing a single codebook (CB) and a method for constructing an individual sub-codebook (i.e., HARQ-ACK sub-codebook) for each will be proposed separately.

[0241] In this disclosure, constructing an individual sub-CB means that the C / T-DAI value is determined and signaled independently for each sub-CB (i.e., the order / sum of the DCI / PDSCH 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 an individual sub-CB for the single PDSCH case and the multi-PDSCH case means that the C / T-DAI value is determined and signaled independently for each of the single PDSCH case and the multi-PDSCH case (i.e., the order / sum of the DCI / PDSCH 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, the HARQ-ACK payloads corresponding to different sub-CBs may be concatenated to form the final HCB (HARQ-ACK codebook).

[0243] On the other hand, configuring a single CB means a structure in which a common C / T-DAI value is determined and signaled, as in existing systems (i.e., the order / sum of DCI / PDSCH scheduled for a single CB is determined / signaled in common). For example, configuring a single CB for single PDSCH cases and multiple PDSCH cases means a structure in which the C / T-DAI value is counted and signaled for both single PDSCH cases and multiple PDSCH cases together (i.e., the order / sum of DCI / PDSCH scheduled for each case is determined / signaled without distinction).

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

[0245] The terminal can configure / generate one CB for both single PDSCH cases and multiple PDSCH cases.

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

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

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

[0249] - HARQ-ACK payload: May be determined by the maximum number of PDSCHs (Y) (where Y is a natural number) that M-DCI can schedule. For example, if 2TB is set (i.e., PDSCH reception carrying 2 transmission blocks is set for the serving cell, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI is set to 2), and spatial bundling for HARQ-ACK information is not set for a cell, then 2 bits may be calculated per PDSCH. For cells where 2TB is set but spatial bundling is set, or for cells where 1TB is set, then 1 bit may be calculated per PDSCH.

[0250] As yet another example, if there are X bits per PDSCH (as mentioned above, for cells where 2TB is set and spatial bundling for HARQ-ACK information is not set, X=2; for cells where 2TB is set but spatial bundling is set, or for cells where 1TB is set, X=1), 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 set for multiple cells (within one cell group), the number of HARQ-ACK bits for each DAI may be determined by the maximum X*Y value among any of the cells. That is, it may be determined by the maximum X*Y value among the X*Y values ​​calculated for each cell within the cell group.

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

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

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

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

[0255] - UL Grant: The existing UL DAI size may require an additional 2 bits for T-DAI (for sub-CB for CBG).

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

[0257] 2) Option 2: A single sub-CB may be configured. That is, one sub-CB may be configured for scheduling TB-based or CBG-based PDSCH in a single PDSCH case, or for multiple PDSCH cases.

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

[0259] - S-DCI or M-DCI or UL grant: The DAI size may be maintained, as in Example 4-1 above.

[0260] - HARQ-ACK payload: If the set maximum number of CBGs is C (where C is a natural number), the payload size may be composed of / determined by the maximum C value (max_C) among any cell (within a single cell group) and the maximum X*Y value (max_XY) among any cell (within a single cell group) (derived by 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 case.

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

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

[0263] - M-DCI or S-DCI or UL grant: The DAI size may be maintained, as in Example 4-1 above.

[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 case (for example, the X value may be 2 or 1 depending on whether the serving cell is configured for 2TB (i.e., whether PDSCH reception carrying two transmission blocks is configured, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell configured for 2TB and without spatial bundling for HARQ-ACK information, X may be 2. For a cell configured for 2TB but with spatial bundling, or for a cell configured for 1TB, X may be 1).

[0266] If M-DCI is set for multiple 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 a single cell group). In other words, the G (or X*G) values ​​for each cell within a cell group may be compared, and the number of HARQ-ACK bits for each DAI may be determined based on the maximum G (or X*G) value.

[0267] If there is no PDSCH corresponding to a particular time bundling group (especially if the G value is 2 or greater), the NACK may be mapped. For 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 case (for example, the X value may be 2 or 1 depending on whether the serving cell is configured with 2TB (i.e., whether a PDSCH receiver carrying two transmission blocks is configured, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI)). As yet another example, for a cell configured with 2TB and no spatial bundling for HARQ-ACK information, X may be 2. For a cell configured with 2TB but with spatial bundling, or for a cell configured with 1TB, X may be 1). Alternatively, if G=1 is set for all cells (within the same PUCCH cell group) for which M-DCI is configured, a single CB may be configured for both single PDSCH cases and multiple PDSCH cases.

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

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

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

[0271] - UL Grant: The existing UL DAI size may require an additional 2 bits for T-DAI (for sub-CB for CBG).

[0272] - HARQ-ACK payload: The payload of a single sub-CB configured for scheduling a TB-based PDSCH in a single PDSCH case and for a multiplexed PDSCH case may be the same as in the above example 4-1b where CBG is not set (i.e., the number of HARQ-ACK bits corresponding to one DAI may be G or X*G for both single PDSCH and multiplexed PDSCH cases (for example, the X value may be 2 or 1 depending on whether 2TB is set for the serving cell (i.e., whether a PDSCH receiver carrying two transmission blocks is set or not, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI)). Further examples include when 2TB is set and spatial bundling of HARQ-ACK information For cells where bundling is not set, X may be 2. For cells where 2TB is set but spatial bundling is set, or for cells where 1TB is set, X may be 1. The payload of other sub-CBs configured for CBG-based PDSCH scheduling using a single PDSCH case may be the same as that of existing CBG-based sub-CB configurations.

[0273] Alternatively, when both M-DCI and CBG are configured within the same PUCCH group, rules may be set to automatically apply time bundling to multiple PDSCH cases (where the G value may be predefined (e.g., G=1) or set by the base station). Here, single CB may be defined / set to be configured for single PDSCH cases and multiple PDSCH cases.

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

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

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

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

[0278] - UL Grant: The existing UL DAI size may require an additional 2 bits of T-DAI (for the additional sub-CB).

[0279] - HARQ-ACK payload: The number of HARQ-ACK bits per sub-CB DAI corresponding to a single PDSCH case is X (for example, the value of X may be 2 or 1 depending on whether the serving cell is configured with 2TB (i.e., whether PDSCH reception carrying two transmission blocks is configured, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell configured with 2TB and no spatial bundling for HARQ-ACK information, X may be 2. For a cell configured with 2TB but with spatial bundling, or for a cell configured with 1TB, X may be 1). The number of HARQ-ACK bits per sub-CB DAI corresponding to a multiple PDSCH case is the maximum X*Y value among any cell (within a single 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 DCI-specific DAI count (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., a first sub-CB may be configured when scheduling a TB-based PDSCH in a single PDSCH case, a second sub-CB may be configured for a multiple PDSCH case, and a third sub-CB may be configured for CBG-based PDSCH scheduling by a single PDSCH case).

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

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

[0284] - UL Grant: The existing UL DAI size may require an additional 4 bits of T-DAI (for the two additional sub-CBs) (i.e., 2 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 a multiple PDSCH case may be the same as the sub-CB corresponding to the multiple PDSCH case 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 in multiple PDSCH cases and single PDSCH cases.

[0287] - When a CBG is set in a cell where an M-DCI is set, the DAI within the M-DCI can indicate the C / T-DAI value for the second sub-CB in a single PDSCH case. When a CBG is not set in a cell where an M-DCI is set, the DAI within the 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: May be the same as in Example 4-2 above.

[0289] - HARQ-ACK payload: If the set maximum number of CBGs is C (where C is a natural number), the payload size may be configured / determined by the maximum value of the maximum C value (max_C) and the maximum X*Y value (max_XY) (derived by Example 4-2 above) among any cell (within a single cell group). 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 multiple 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 is not required that M-DCI and CBG be set simultaneously (together) within the same PUCCH group. Alternatively, if a type-1 HARQ-ACK CB is set for a cell in which M-DCI is set (or if a type-2 HARQ-ACK CB is not set for that cell), then CBG setting may be permitted for other cells within the same PUCCH group (not that cell).

[0291] Option 1 and / or Option 2 may be supported as selective UE features, and for terminals that do not support Option 1 and / or Option 2, Option 3 may be defined / configured as the default. In other words, for terminals that do not support Option 1 and / or Option 2, it can be expected that M-DCI and CBG within the same PUCCH group will not be configured simultaneously (both).

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

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

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

[0295] - M-DCI or S-DCI or UL grant: The DAI size may be maintained, as in Example 4-1 above.

[0296] - HARQ-ACK payload for sub-CBs corresponding to multiple PDSCH cases: 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, the X value may be 2 or 1 depending on whether the serving cell is configured for 2TB (i.e., whether PDSCH reception carrying two transmission blocks is configured, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell configured for 2TB and without spatial bundling for HARQ-ACK information, X may be 2. For a cell configured for 2TB but with spatial bundling, or for a cell configured for 1TB, X may be 1).

[0298] If M-DCI is set for multiple 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 a single cell group). In other words, the G (or X*G) values ​​for each cell within a cell group may be compared, 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 cells where M-DCI is set but time bundling is not set, the G value may be replaced with the maximum number of PDSCHs (Y) (where Y is a natural number) that the M-DCI can schedule.

[0300] In other words, for multiple cells (within the same PUCCH cell group) where M-DCI is set, and for cells where time bundling is not set, or where time bundling is set and a G (= number of PDSCH groups to be time-bundled) value greater than 1 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 HARQ-ACK codebook configuration) 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 that the M-DCI can schedule and X, in the case of a cell where M-DCI is set but time bundling is not set (for example, the X value may be 2 or 1 depending on whether 2TB is set for the serving cell (i.e., whether or not PDSCH reception carrying two transmission blocks is set, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell where 2TB is set and spatial bundling for HARQ-ACK information is not set, X may be 2. For a cell where 2TB is set but spatial bundling is set, or for a cell where 1TB is set, X may be 1).

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

[0303] - 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 is X (for example, the value of X may be 2 or 1 depending on whether the serving cell is configured for 2TB (i.e., whether PDSCH reception carrying two transmission blocks is configured or not, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell configured for 2TB and without spatial bundling for HARQ-ACK information, X may be 2. For a cell configured for 2TB but with spatial bundling, or for a cell configured for 1TB, X may be 1).

[0304] If G=1 is set for any of the cells in which M-DCI is set, the HARQ-ACK bit corresponding to the M-DCI of that cell may be placed on the sub-CB corresponding to the single PDSCH case (for example, the X value may be 2 or 1 depending on whether 2TB is set for the serving cell (i.e., whether PDSCH reception carrying two transmission blocks is set or not, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell in which 2TB is set and spatial bundling for HARQ-ACK information is not set, X may be 2. For a cell in which 2TB is set but spatial bundling is set, or for a cell in which 1TB is set, X may be 1). In other words, one CB may be configured for the single PDSCH case and the multiple PDSCH case of a cell in which M-DCI is set and G=1 is set.

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

[0306] - PDSCH Type 1: M-DCI-based PDSCH transmissions without time bundling (i.e., PDSCHs scheduled on one or more cells where M-DCI-based scheduling is set but time bundling is not set), and M-DCI-based PDSCH transmissions with a G value greater than 1 (i.e., PDSCHs scheduled on one or more cells where M-DCI-based scheduling is set and a G value greater than 1 is set as time bundling).

[0307] - PDSCH Type 2: M-DCI-based PDSCH transmissions with G=1 (i.e., PDSCH scheduled on one or more cells with M-DCI-based scheduling configured and G=1 with time bundling configured), 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, a first HARQ-ACK subcodebook may be generated for PDSCHs scheduled on one or more first serving cells in relation to PDSCH type 1, i) where M-DCI-based scheduling is set but time bundling is not set, or ii) where M-DCI-based scheduling is set and a G value greater than 1 is set for time bundling. Also, a second HARQ-ACK subcodebook may be generated for PDSCHs scheduled on one or more second serving cells in relation to PDSCH type 2, i) where M-DCI-based scheduling is set and time bundling is set to G=1, or ii) where M-DCI-based scheduling is not set. Here, the multiple serving cells set on 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, the UL DCI may be configured / indicated with separate (UL)DAI fields / information for PDSCH types 1 and 2, respectively. If no PDSCH type 1 exists as described above, DAI signaling may be performed only for PDSCH type 2, a HARQ-ACK codebook may be configured only for PDSCH type 2, and the UL DCI may be configured / indicated with only UL DAI fields / information for PDSCH type 2.

[0310] Alternatively, independent DAI signaling may be performed between the following two PDSCH types, and separate HARQ-ACK sub-codebooks may be constructed. The Y value below may be set / specified as 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 set to 1, and existing S-DCI-based PDSCH transmission

[0313] In this case, the UL DCI may be configured / instructed to contain separate UL DAI fields / information for PDSCH types 1 and 2, respectively. If, as described above, PDSCH type 1 does not exist, DAI signaling may be performed only for PDSCH type 2, a HARQ-ACK codebook may be configured, and the UL DCI may be configured / instructed to contain only UL DAI fields / information for PDSCH type 2.

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

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

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

[0317] - S-DCI: The existing DL DAI size may be increased by ceiling{log2(the maximum value among the N_max values ​​set for each CC (or BWP) within the same cell group)} (increased for each C / T-DAI). Here, N_max is the maximum number of PDSCHs that can be scheduled for a particular cell using M-DCI.

[0318] Here, let's assume that the DAI increment, ceiling{log2(the maximum value among the N_max values ​​for each CC (or BWP) set within the same cell group)}, is A. For the time being, we can consider a method in which the DL DAI of the fallback DL DCI (i.e., DCI format 1_0) is kept at 2 bits as before, while widening the interval of the indicated DAI values ​​to 2^A. This is because increasing the DCI size is undesirable from the standpoint of reliability of the fallback DL DCI. For example, if the above DAI increment is 2 bits, then 2^A = 4, so the 2-bit DAI values ​​indicated by the fallback DCI can be scaled by 2^A to {4, 8, 12, 16} (instead of {1, 2, 3, 4}). Therefore, if the previous C-DAI value was 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 and 7 with the NACK.

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

[0320] Alternatively, assume that the DAI increase amount ceiling{log2(the maximum value among the N_max values ​​for each CC (or BWP) set within the same cell group)} is A. For the time being, the DL DAI of the fallback DL DCI (i.e., DCI format 1_0) may be kept at 2 bits as before, and the counting step of the DAI may also be increased by 1, the same as before. Here, it may be restricted so that only PDSCHs scheduled in the fallback DCI (or DCI in which the DL DAI size is kept the same as before) are collected and another PUCCH is instructed. In other words, the terminal can expect that the PUCCH resources (especially time resources) instructed in the multiple PDSCH scheduling DCI (or DCI in which the DL DAI size has increased by A) and the PUCCH resources (especially time resources) instructed in the fallback DCI (or DCI in which the DL DAI size is kept the same as before) will not overlap. For example, a multiple PDSCH scheduling DCI may only be allowed to point to the same PUCCH slot with the same / different cell non-fallback DCI. In other words, a fallback DCI may not be allowed to point to the same PUCCH slot with a multiple PDSCH scheduling DCI or a non-fallback DCI.

[0321] - UL grant: The existing UL DAI size (i.e., T-DAI 2 bits) may be increased by ceiling{log2(the maximum N_max value among the CC (or BWP) set within the same cell group)}. Here, N_max is the maximum number of PDSCHs that can be scheduled with M-DCI for a given cell, and this increase should apply to cells with or without M-DCI. In other words, if M-DCI is set for at least one serving cell within the same cell group, this increase will be applied to UL grants for all serving cells within that cell group.

[0322] - HARQ-ACK payload: The number of HARQ-ACK bits per DAI may be X bits (for example, the value of X may be 2 or 1 depending on whether the serving cell is configured for 2TB (i.e., whether PDSCH reception carrying two transmission blocks is configured, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell configured for 2TB and without spatial bundling for HARQ-ACK information, X may be 2. For a cell configured for 2TB but with spatial bundling, or for a cell configured for 1TB, X may be 1).

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

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

[0325] - S-DCI: For cells with CBG set but without M-DCI setting, the DL DAI size in the non-fallback DCI format (i.e., DCI format 1_1 or 1_2) can be increased as in Example 4-3 above, or option 1-2) can remain at 2 bits as before. For cells with CBG set but without M-DCI setting, the DL DAI size in the fallback DCI format (i.e., DCI format 1_0) can be increased or remain at 2 bits as in Example 4-3 above. For cells with both M-DCI and CBG set, the DL DAI size may be increased 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 Example 4-3 above. Here, in a single PDSCH case, the DAI in a multi-TTI DCI (e.g., multiple PDSCH DCI) can indicate the C / T-DAI value for a 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 increased to M_1 bits (>2) (as in Example 4-3 above), and the C / T-DAI value may be indicated by option 2-1) M_1 bits (especially in the case of option 1-1), or by option 2-2) 2 bits (especially in the case of option 1-2). Characteristically, in the case of option 2-2, the DL DAI field size itself may be reduced to 2 bits each for C / T-DAI by TDRA field verification (in the case of a single PDSCH) (conversely, in the case of a multiple PDSCH by TDRA field verification, the DL DAI field size may be M_1 bit). Here, in the case of a single PDSCH, the DAI in a multi-TTI DCI (e.g., a multiple PDSCH DCI) can indicate the C / T-DAI value for a CBG-based PDSCH.

[0328] - UL Grant: The DAI size for the UL grant in Example #4-3 above may require an additional 2 bits of T-DAI (for the sub-CB for CBG). That is, if a CBG is set in at least one serving cell within the same cell group, the increase may be applied to the UL grant for all serving cells within the same cell group.

[0329] - HARQ-ACK payload: The payload of one sub-CB configured for scheduling a TB-based PDSCH in a single PDSCH case and for a multiple PDSCH case may be the same as in Example 4-3 above. The payload of other sub-CBs configured for CBG-based PDSCH scheduling in 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 in Example 4 above) + single HARQ-ACK CB (codebook) configuration + time bundling is set

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

[0332] - M-DCI: This may be the same as in Example 4-3 above, or it may be increased 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 DL DAI size (i.e., 2 bits each for C / T-DAI). In this case, G_max is the number of groups for (maximum) time bundling set for a particular cell.

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

[0334] Here, let's assume that the DAI increment 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. For the time being, while keeping the DL DAI of the fallback DL DCI (i.e., DCI format 1_0) at 2 bits as before, a method may be considered to widen the interval of the indicated DAI values ​​to 2^A. This is because increasing the DCI size is undesirable from the standpoint of reliability of the fallback DL DCI. For example, if the above DAI increment amount is 1 bit, then 2^A = 2, so the 2-bit DAI values ​​indicated by the fallback DCI may be scaled by 2^A to {2, 4, 6, 8} (instead of {1, 2, 3, 4}). As a result, if the previous C-DAI value was 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: This may be the same as in Example 4-3 above, or it may be increased by ceiling{log2(the maximum G_max value among the CC (or BWP) set within the same cell group)} to the existing UL DAI size (i.e., T-DAI 2 bits). Here, G_max is the number of groups for (maximum) time bundling set for a particular cell, and this increase should apply to both cells where M-DCI is set and 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 may be applied to the UL grant for all serving cells within the same cell group.

[0336] - HARQ-ACK payload: If the DAI sizes for the M-DCI, S-DCI, and UL grants are determined according to Example 4-3 above, the HARQ-ACK payload may be constructed by bundling PDSCHs corresponding to G_max (or G DAIs assigned to each cell). Alternatively, if the DAI sizes for the M-DCI, S-DCI, and UL grants are determined based on G_max, one HARQ-ACK bit may be constructed for each DAI.

[0337] Example 4-4: DAI count by PDSCH (i.e., Alt 2 in Example 4 above) + individual HARQ-ACK subcodebook (sub-CB) configuration

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

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

[0340] - S-DCI: Existing DL DAI size may be maintained. This should apply to cells where M-DCI is set and cells where it is not set.

[0341] - UL Grant: The existing UL DAI size may require an additional T-DAI Z (where Z is a natural number) bits (for additional sub-CBs). Here, Z = ceiling{log2(the maximum N_max value among the CC (or BWP) set within the same cell group)}, where N_max is the maximum number of PDSCHs that can be scheduled with M-DCI for a given cell, and this increase should apply to both cells with and without M-DCI. That is, if M-DCI is set for at least one serving cell within the same cell group, this increase may be applied to the UL grant for all serving cells within that cell group.

[0342] - HARQ-ACK payload: The number of HARQ-ACK bits per sub-CB DAI corresponding to a single PDSCH case may be X (for example, the value of X may be 2 or 1 depending on whether the serving cell is configured for 2TB (i.e., whether a PDSCH receiver carrying two transmission blocks is configured, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell configured for 2TB and without spatial bundling for HARQ-ACK information, X may be 2. For a cell configured for 2TB but with spatial bundling, or for a cell configured for 1TB, X may be 1). The number of HARQ-ACK bits per sub-CB DAI corresponding to the multiple PDSCH case may also be X (for example, the value of X may be 2 or 1 depending on whether the serving cell is configured for 2TB (i.e., whether PDSCH reception carrying two transmission blocks is configured or not, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell configured for 2TB and without spatial bundling for HARQ-ACK information, X may be 2. For a cell configured for 2TB but with spatial bundling, or for a cell configured for 1TB, X may be 1).

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

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

[0345] - S-DCI: For cells with CBG set but without M-DCI setting, 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. For cells with CBG set but without M-DCI setting, the DL DAI size in the fallback DCI format (i.e., DCI format 1_0) can maintain 2 bits as before. For cells with both M-DCI and CBG set, the DL DAI size may be maintained as in Example 4-4 above.

[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 Example 4-4 above. Here, in a single PDSCH case, the DAI in a multi-TTI DCI (e.g., multiple PDSCH DCI) can indicate the C / T-DAI value for a 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 within the DCI is increased to M_2 bits (>2) (as in Example 4-4 above), and the C / T-DAI value may be indicated by 2 bits. Characteristically, the DL DAI field size itself may be reduced to 2 bits each for C / T-DAI by TDRA field verification (in the case of a single PDSCH) (conversely, if it is a multiple PDSCH case by TDRA field verification, the DL DAI field size may be M_2 bits). Here, in the case of a single PDSCH, the DAI within a multi-TTI DCI (e.g., a multiple PDSCH DCI) can indicate the C / T-DAI value for a CBG-based PDSCH.

[0348] - UL Grant: The UL DAI size of Example 4-4 above may require an additional 4 bits of T-DAI (for the two additional sub-CBs) (i.e., 2 bits of T-DAI are added for each sub-CB).

[0349] - 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-4 above. The payload of the second sub-CB configured for a multiple PDSCH case may be the same as the sub-CB corresponding to the multiple PDSCH case in Example 4-4 above. The payload of the third sub-CB configured for CBG-based PDSCH scheduling using a 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 in Example 4 above) + individual HARQ-ACK sub-CB configuration + time bundling is set.

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

[0352] - M-DCI: This may be the same as in Example 4-4 above, or it may be increased 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 DL DAI size (i.e., 2 bits each for C / T-DAI). Here, G_max is the number of groups for (maximum) time bundling set for a particular cell.

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

[0354] - HARQ-ACK payload for sub-CB corresponding to multiple PDSCH cases: If the DAI size for the M-DCI follows the above example 4-4, the HARQ-ACK payload may be constructed by bundling PDSCHs corresponding to G_max (or G assigned to each cell) DAIs. Alternatively, if the DAI size for the M-DCI is determined based on G_max, one HARQ-ACK bit may be constructed 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, the value of X may be 2 or 1 depending on whether the serving cell is configured for 2TB (i.e., whether PDSCH reception carrying two transmission blocks is configured or not, or the maximum number of transmission blocks (or codewords) that can be scheduled by one DCI). As another example, for a cell configured for 2TB and without spatial bundling for HARQ-ACK information, X may be 2. For a cell configured for 2TB but with spatial bundling, or for a cell configured for 1TB, X may be 1).

[0356] Examples 4-5: DAI count for each PDSCH of W (where W is a natural number) (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 ​​set for each CC (or BWP) within the same cell group, and N_max means the maximum number of PDSCHs that can be scheduled for a particular cell using M-DCI), the DAI is counted by DCI (i.e., Alt 1 in Example 4 above), so Examples 4-1, 4-1a, 4-2, and 4-2a above may be applied.

[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 Multiple PUCCHs Corresponding to Multiple PDSCHs Scheduled by One DCI are Indicated

[0360] One disadvantage is that a separate DAI field is required for each PDSCH, as DAI counts must be performed individually between PDSCHs that correspond to different PUCCHs. For example, when N PDSCHs are scheduled in one DCI, the PUCCH corresponding to N1 PDSCHs may be designated as slot n1, and the PUCCH corresponding to the remaining N2 (i.e., N=N1+N2, where the value of N1 is predefined, set by upper-layer signaling, or determined as N1=ceiling{N / 2}, N2=floor{N / 2}, or N1=floor{N / 2}, N2=ceiling{N / 2}) PDSCHs may be designated as slot n2. Here, C-DAI / T-DAI may be required for N1 PDSCHs and C-DAI / T-DAI may be required for N2 PDSCHs. To mitigate this DCI overhead problem, in multiple PDSCH cases, a rule may be established (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 N1 PDSCHs and the C-DAI2 field for N2 PDSCHs are signaled in DL DCI, and the T-DAI field for N1 PDSCHs and the T-DAI field for N2 PDSCHs may be omitted from DL DCI signaling. If a terminal misses the last DCI (which contains T-DAI information) (for example, due to a decoding failure), a HARQ-ACK payload mismatch problem between the base station and the terminal may occur because there is no T-DAI in that multiple PDSCH case. However, the base station can solve this problem by scheduling further DCIs that contain reliable T-DAI. Alternatively, if different PUCCHs are indicated, the base station can solve the problem by a method such as blind detection of the multiple PUCCHs. Characteristically, in the case of M-DCI, Case 1) N more than N (for example, a value such as N=1 may be defined in advance, or the value of N may be set by upper-layer signaling).Case 1) When a PDSCH is scheduled, multiple PUCCHs may be indicated, or Case 2) When N or fewer PDSCHs are scheduled, only one PUCCH may be indicated. In this case, in Case 2, C-DAI and T-DAI fields may be configured within the DCI, and C-DAI and T-DAI information may be indicated. On the other hand, in Case 1, only the C-DAI1 field / information for N1 PDSCHs and the C-DAI2 field / information for N2 PDSCHs may be configured / indicated. Here, the bits that are interpreted as C-DAI and T-DAI fields in Case 2 may be interpreted as C-DAI1 for N1 PDSCHs and C-DAI2 for N2 PDSCHs (or vice versa) in Case 1.

[0361] Alternatively, the N / N1 / N2 values ​​may be in DL slot units rather than PDSCH units. For example, when N' PDSCHs spanning N slots are scheduled in one DCI, the PUCCH corresponding to the N1' PDSCHs spanning N1 slots may be designated as slot n1, and the PUCCH corresponding to the remaining N2 (i.e., N=N1+N2, where the value of N1 is predefined or set by upper-layer signaling, or N1=ceiling{N / 2}, N2=floor{N / 2}, or N1=floor{N / 2}, N2=ceiling{N / 2}) slots may be designated as slot n2. Here, C-DAI / T-DAI may be required for the PDSCHs spanning N1 slots and for the PDSCHs spanning N2 slots, respectively. To mitigate such DCI overhead issues, in multiple PDSCH cases, a rule may be established (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 PDSCHs spanning N1 slots and the C-DAI2 field for PDSCHs spanning N2 slots are signaled in DL DCI, and the T-DAI field for PDSCHs spanning N1 slots and the T-DAI field for PDSCHs spanning N2 slots may be omitted from DL DCI signaling. If a terminal misses the last DCI (which contains T-DAI information) (for example, due to a decoding failure), a HARQ-ACK payload mismatch problem between the base station and the terminal may occur because there is no T-DAI in that multiple PDSCH case. However, the base station can solve this problem by scheduling further DCIs that contain reliable T-DAI. Alternatively, if different PUCCHs are instructed, the base station can solve the problem by performing blind detection of the multiple PUCCHs.Characteristically, in the case of M-DCI, if a PDSCH spanning more than N slots is scheduled (for example, N may be predefined as a value such as 1, or the value of N may be set by upper-layer signaling), multiple PUCCHs may be indicated, or if a PDSCH spanning N or fewer slots is scheduled, only one PUCCH may be indicated. In this case, in Case 2, C-DAI and T-DAI fields are configured within the DCI, and C-DAI and T-DAI information is indicated, while in Case 1, only the C-DAI1 field / information for PDSCHs spanning N1 slots and the C-DAI2 field / information for PDSCHs spanning N2 slots may be configured / indicated. Here, the bits that are interpreted as C-DAI and T-DAI fields in Case 2 may be interpreted in Case 1 as C-DAI1 for a PDSCH spanning N1 slots and C-DAI2 for a PDSCH spanning N2 slots (or vice versa).

[0362] Example 6: When configuring DCI-based DAI counts (i.e., Alt 1 in Example 4) + individual sub-CBs as in Example 4-2 above, we propose a method for configuring individual sub-CBs.

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

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

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

[0366] On the other hand, when time bundling is set in M-DCI as in Example 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 2-TB is set only in the M-DCI setting cell.

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

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

[0370] As another method, a method similar to that in Case 1 can also be applied in this case. For example, the number of HARQ-ACK bits for each DAI in sub-CB#1 may be determined to be 2 bits. Here, if only one or two 1-TB PDSCHs or a single 2-TB PDSCH is scheduled by the 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, as described above, the HARQ-ACK information corresponding to a PDSCH scheduled by M-DCI is included in sub-CB#1, and only 1-TB PDSCHs are scheduled by M-DCI, then of the two HARQ-ACK bits corresponding to the DAI, the first bit carries the ACK or NACK information of the scheduled PDSCH, and the second bit is either always filled with NACK or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) is repeatedly transmitted. Similarly, in the case of a 1-TB PDSCH scheduled by S-DCI, of the two HARQ-ACK bits corresponding to the DAI, the first bit carries the ACK or NACK information of the scheduled PDSCH, and the second bit is either always filled with NACK or the first bit (i.e., the ACK or NACK information of the scheduled PDSCH) is repeatedly transmitted. Furthermore, if only two 2-TB PDSCHs are scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCHs scheduled by M-DCI may be spatially bundled to convert it to 2 bits and included in sub-CB#1.

[0371] On the other hand, when time bundling is set in M-DCI as in Example 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 spatial bundling is configured, or if 2-TB is not configured for all cells (within a single PUCCH cell group)

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

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

[0375] As an alternative to Case 3, the number of HARQ-ACK bits for each DAI in sub-CB#1 may be determined to be 2 bits. Here, similar to Case 1, if only one or two 1-TB PDSCHs are scheduled by M-DCI, the HARQ-ACK information corresponding to the PDSCHs scheduled by M-DCI may be included in sub-CB#1. In other cases, the HARQ-ACK information corresponding to the PDSCHs scheduled by M-DCI may be included in sub-CB#2. Furthermore, in the case of a 1-TB PDSCH scheduled by S-DCI, of 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 is always 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 in M-DCI as in Example 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] Example 7: When some transmissions / receptions of PDSCHs scheduled by M-DCI can be omitted, we propose a method for configuring DAI counting and HARQ-ACK CB (codebook).

[0378] In this embodiment, the omission of some PDSCH transmission / reception can mean at least some or all of the following:

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

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

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

[0382] 1) Option 1: When some of the transmission / reception of multiple PDSCHs scheduled by M-DCI can be omitted, a sequence of values ​​starting from the (C-)DAI value indicated by the DCI may be assigned to only the PDSCHs that were actually transmitted / received (not based on the scheduling criteria), in chronological order. For example, if a terminal receives an M-DCI with four PDSCHs scheduled, part (or all) of the OFDM symbols of the third PDSCH may be set to 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, and fourth scheduled PDSCHs are 3 / 4 / 5, respectively (by skipping the C-DAI value mapping for the third PDSCH).

[0383] 2) Option 2: When some of the transmission / reception of multiple PDSCHs scheduled by M-DCI are optional, the DAI values ​​may be assigned sequentially to all PDSCHs scheduled by DCI, regardless of whether actual transmission / reception occurred, starting from the (C-)DAI value indicated by DCI. For example, if a terminal receives an M-DCI with four PDSCHs scheduled, part (or all) of the OFDM symbols of the third PDSCH may be set to 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, and fourth scheduled PDSCHs are 3 / 4 / 5 / 6, respectively.

[0384] In option 2 above, the HARQ-ACK information for the (C-)DAI value corresponding to a PDSCH with omitted transmission / reception may be mapped to NACK. Also, in cases where the DAI value increases for each DCI, such as in Examples 4-1 (or Examples 4-1a / b) and 4-2 (or Examples 4-2a / b) above, the HARQ-ACK information corresponding to a PDSCH with omitted transmission / reception may be mapped to NACK.

[0385] Example 8: We propose an aperiodic CSI reporting and frequency hopping method when some transmissions / receptions of PUSCH scheduled by M-DCI are optional.

[0386] In this embodiment, the omission of some PUSCH transmissions / receptions can mean at least some or all of the following:

[0387] - Pushes overlapping with symbols (or slots containing such symbols) configured as downlinks (or flexible) by upper-layer signaling for common TDD configurations (e.g., tdd-UL-DL-ConfigurationCommon) or upper-layer signaling for dedicated TDD configurations (e.g., tdd-UL-DL-ConfigurationDedicated).

[0388] - A PUSCH contained in (or overlapping with) a resource set / indicated by higher-level signaling for setting an invalid symbol pattern (e.g., invalidSymbolPattern)

[0389] In the cases described above, we propose aperiodic CSI reporting and frequency hopping methods.

[0390] On the other hand, non-periodic CSI reporting by M-DCI can follow the following regulations:

[0391] When DCI format 0_1 ​​schedules two PUSCH assignments, aperiodic CSI reports are transmitted on the second scheduled PUSCH. When DCI format 0_1 ​​schedules two or more PUSCH assignments, aperiodic CSI reports are transmitted on the second-to-last (penultimate) scheduled PUSCH.

[0392] However, when the transmission / reception of some of the multiple PUSCHs scheduled by M-DCI can be omitted, the PUSCH from which the aperiodic CSI report is sent may be determined based only on the PUSCHs that were actually transmitted / received (rather than the scheduling criteria). That is, if two PUSCHs were actually transmitted / received, the CSI would be reported by the second PUSCH (of the two PUSCHs actually transmitted / received), and if three or more PUSCHs were actually transmitted / received, the CSI would be reported by the second-to-last PUSCH (of the multiple PUSCHs actually transmitted / received). Specifically, this may be as follows:

[0393] For example, in the case of a terminal that receives an M-DCI with four scheduled pushes, part (or all) of the OFDM symbols of the third push may be set to downlink (or flexible) by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. If an aperiodic CSI report is triggered by the M-DCI, an aperiodic CSI may be reported on the second scheduled push, which is the second push after the push that is actually transmitted.

[0394] On the other hand, if DCI format 0_1 ​​schedules no less than two push assignments, but only two pushes are sent, the aperiodic CSI report is transmitted on the second push. If DCI format 0_1 ​​schedules two or more push assignments, and two or more pushes are sent, the aperiodic CSI report is transmitted on the penultimate push.

[0395] On the other hand, when inter-slot hopping is applied in frequency hopping (for multiple pushes scheduled by M-DCI), in equation 3 below, nμ s The value may increase according to the PUSCH actually sent (not the scheduled PUSCH criterion). That is, for PUSCH that was scheduled but not actually sent, the parameter n μ s The value does not need to increase.

[0396] In inter-slot frequency hopping, slot n μ s The starting RB during this period is given by equation 3 below.

[0397]

number

[0398] In equation 3, n μ s This is the current slot number within the wireless frame. Here, multiple slot push transmissions may occur, and RB start This is the starting RB within the UL BWP, calculated from the resource block allocation information of resource allocation type 1. offset This is the frequency offset in RB units between two frequency hops.

[0399] Figure 12 illustrates a signaling procedure between a base station and a terminal for a control information transmission and reception method according to one embodiment of the present disclosure.

[0400] Figure 12 illustrates a signaling procedure between a terminal (UE: user equipment) and a base station (BS: base station) based on the previously proposed method (e.g., one or more of the detailed embodiments of Examples 1-8 and their respective detailed embodiments). The illustration in Figure 12 is for illustrative purposes only and does not limit the scope of this disclosure. Some steps illustrated in Figure 12 may be omitted depending on the circumstances and / or settings. Also, the base station and terminal in Figure 12 are merely illustrative and may be embodied by the equipment illustrated in Figure 15. For example, the processor 102 / 202 in Figure 15 can be controlled to send and receive channels / signals / data / information etc. using transceivers 106 / 206, and can be controlled to store the transmitted or received channels / signals / data / information etc. in memory 104 / 204.

[0401] Furthermore, in the operation between the base station and the terminal shown in Figure 12, the above information may be referenced / utilized without further mention.

[0402] The term "base station" may refer collectively to the objects that transmit and receive data with terminals. For example, the base station may be a concept that includes one or more TPs (Transmission Points) and one or more TRPs (Transmission and Reception Points). Furthermore, TPs and / or TRPs may include the base station's panel, transmission and reception unit, etc. Also, "TRP" may be applied as a substitute for expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell), TP (transmission point), and base station (gNB, etc.). As mentioned above, TRPs may be distinguished by information related to CORESET groups (or CORESET pools) (e.g., index, ID). For example, if one terminal is configured to transmit and receive with multiple TRPs (or cells), this means that multiple CORESET groups (or CORESET pools) are configured for that one terminal. Such configurations for CORESET groups (or CORESET pools) may be performed using higher-level signaling (e.g., RRC signaling).

[0403] Referring to Figure 12, for the sake of explanation, signaling between one base station and a terminal is considered, but of course, this signaling scheme can be extended and applied to signaling between multiple TRPs and multiple UEs. In the following explanation, a base station may be interpreted as one TRP. Alternatively, a base station may include multiple TRPs, or it may be a single cell containing multiple TRPs.

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

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

[0406] The first configuration information can mean configuration information (e.g., PDSCH-TimeDomainResourceAllocationListForMultiPDSCH) for determining whether multiple PDSCHs can be scheduled by a single DCI. For example, if information is provided to a serving cell for setting up scheduling for multiple PDSCH (or PUSCH) transmissions by a single DCI, then scheduling for multiple PDSCH (or PUSCH) transmissions by a single DCI (this is called multiple PDSCH scheduling) may be set up / supported on that cell. On the other hand, if information is not provided to a serving cell for setting up scheduling for multiple PDSCH (or PUSCH) transmissions by a single DCI, then multiple PDSCH scheduling may not be set up / supported on that cell.

[0407] The second configuration information may include information for setting the type of HARQ-ACK codebook (e.g., 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), information for setting HARQ-ACK bundling (i.e., time bundling), and information for the number of HARQ-ACK bundling groups (e.g., numberOfHARQBundlingGroups). Here, for example, if information for setting the number of HARQ bundling groups for a particular serving cell is provided, it may be considered that time bundling has been set for that particular serving cell. On the other hand, if information for setting the number of HARQ bundling groups for a particular serving cell is not provided, it may be considered that time bundling has not been set for that particular serving cell.

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

[0409] Here, if the number of HARQ-ACK bundling groups is set to 1, a single HARQ-ACK piece of information may be generated, and if the number of HARQ-ACK bundling groups is set to more than 1, HARQ-ACK pieces of information may be generated for each group. On the other hand, for one or more serving cells in which multiple PDSCH scheduling is set but HARQ-ACK bundling (i.e., time bundling) is not set, HARQ-ACK pieces of information may be generated for each of the multiple PDSCHs scheduled in that cell.

[0410] Here, based on the aforementioned Embodiment 1, time bundling may be set for one or more of the multiple cells configured in the terminal.

[0411] The terminal receives M-DCI and / or S-DCI from the base station to schedule a single or multiplex PDSCH, and receives the scheduled single or multiplex PDSCH (S1202).

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

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

[0414] In other words, the terminal can receive DCIs (e.g., a separate DCI format for each serving cell) that schedule one or more PDSCHs in each of the configured serving cells. The terminal can then receive one or more PDSCHs in each of the configured serving cells (i.e., receive multiple PDSCHs in the configured serving cells as a whole).

[0415] In this case, DAI signaling may be performed based on any one or more of the detailed embodiments of Example 4 described above, or based on Example 5 described above, or based on Example 7 described above.

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

[0417] Here, the terminal can configure / generate a type-1 HARQ-ACK codebook when time bundling is configured, based on the aforementioned Embodiment 2. Alternatively, the terminal can configure / generate a type-1 HARQ-ACK codebook when slot group-based PDCCH monitoring is configured, based on the aforementioned Embodiment 3. Alternatively, the terminal can configure / generate a type-2 HARQ-ACK codebook based on any one or more of the detailed embodiments of Embodiment 4, or based on the aforementioned Embodiment 6. Alternatively, based on the aforementioned Embodiment 7, the terminal can configure / generate a HARQ-ACK codebook when some of the PDSCH transmissions / receptions scheduled by M-DCI are omitted.

[0418] On the other hand, based on the above-described embodiment 1, when a specific group of the HARQ bundle contains only PDSCHs that overlap with the uplink symbol, the HARQ-ACK information for the specific group may be generated as NACK (negative ACK). Alternatively, when a specific group of the HARQ bundle contains one or more PDSCHs that overlap with the uplink symbol, the HARQ-ACK information for the specific group may be generated by considering the one or more PDSCHs that overlap with the uplink symbol as ACK or NACK (negative ACK).

[0419] The terminal transmits HARQ-ACK information to the base station at the time instructed 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 scheduling requests, channel status information, uplink data (in the case of PUSCH), etc., in addition to the HARQ-ACK codebook.

[0421] Figure 13 illustrates the operation of a terminal in relation to a control information transmission and reception method according to one embodiment of the present disclosure.

[0422] Figure 13 illustrates the operation of a terminal based on the previously proposed method (for example, one or more of the (detailed) embodiments from Examples 1-8 and their detailed embodiments). The illustration in Figure 13 is for illustrative purposes only and does not limit the scope of the present disclosure. Some steps illustrated in Figure 13 may be omitted depending on the circumstances and / or settings. Also, the terminal in Figure 13 is merely an example and may be embodied by the device illustrated in Figure 15. For example, the processor 102 / 202 in Figure 15 can be controlled to send and receive channels / signals / data / information etc. (e.g., RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, PHICH, etc.) using transceivers 106 / 206, and can be controlled to store the transmitted or received channels / signals / data / information etc. in memory 104 / 204.

[0423] The terminal receives configuration information (hereinafter referred to as "first configuration information") from the base station for setting up HARQ-ACK bundling for one or more serving cells among the multiple serving cells configured on the terminal (S1301).

[0424] Here, the first configuration information may further include information for setting the type of HARQ-ACK codebook (e.g., 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 (e.g., numberOfHARQBundlingGroups).

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

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

[0427] Multiple PDSCH scheduling may be configured for one or more serving cells among the multiple serving cells configured on the terminal. For serving cells where multiple PDSCH scheduling is not configured, one PDSCH may be scheduled by a single DCI as in the existing system. HARQ-ACK bundling (i.e., time bundling) may be configured for one or more serving cells among the one or more serving cells where multiple PDSCH scheduling is configured. For example, as described above, HARQ-ACK bundling may be configured for a cell by setting the number of HARQ-ACK bundling groups. In this way, HARQ-ACK information may be generated for one or more groups for multiple PDSCHs scheduled on a serving cell where 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 multiple PDSCHs included in each of the one or more groups.

[0428] Here, if the number of HARQ-ACK bundling groups is set to 1, a single HARQ-ACK piece of information may be generated, and if the number of HARQ-ACK bundling groups is set to more than 1, HARQ-ACK pieces of information may be generated for each group. On the other hand, for a serving cell in which multiple PDSCH scheduling is set but HARQ-ACK bundling (i.e., time bundling) is not set, HARQ-ACK pieces of information may be generated for each of the multiple PDSCHs scheduled in that cell.

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

[0430] Here, based on the aforementioned Embodiment 1, time bundling may be set for one or more of the multiple cells configured in the terminal.

[0431] The terminal receives a DCI from the base station to schedule one or more PDSCHs on each of the multiple serving cells configured for the terminal (S1302), and the terminal receives multiple PDSCHs from the base station on the multiple serving cells configured for the terminal (S1303).

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

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

[0434] In other words, the terminal can receive DCIs (e.g., a separate DCI format for each serving cell) that schedule one or more PDSCHs in each of the configured serving cells. The terminal can then receive one or more PDSCHs in each of the configured serving cells (i.e., receive multiple PDSCHs in the configured serving cells as a whole).

[0435] In this case, DAI signaling may be performed based on any one or more of the detailed embodiments of Example 4 described above, or based on Example 5 described above, or based on Example 7 described above.

[0436] The terminal generates a HARQ-ACK codebook based on HARQ-ACK information for multiple 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 configured based on the aforementioned Embodiment 2. Alternatively, the terminal can configure / generate a type-1 HARQ-ACK codebook when slot group-based PDCCH monitoring is configured based on the aforementioned Embodiment 3.

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

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

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

[0441] Here, the first HARQ-ACK subcodebook may be generated for PDSCHs on one or more first serving cells where the number of HARQ bundling groups is set to 1. Then, the second HARQ-ACK subcodebook may be generated for PDSCHs on one or more second serving cells where the number of HARQ bundling groups is set to a value greater than 1.

[0442] On the other hand, if the second configuration information is received first, the first HARQ-ACK subcodebook may be generated for PDSCHs on one or more first serving cells among the multiple serving cells configured in the terminal where the multiple PDSCH scheduling is not configured or the number of HARQ bundling groups is set to 1. Then, the second HARQ-ACK subcodebook may be generated for PDSCHs on one or more second serving cells among the one or more serving cells where the multiple PDSCH scheduling is configured, where the number of HARQ bundling groups is set to more than 1 or HARQ bundling is not configured.

[0443] Here, if HARQ bundling is set for one or more second serving cells, the second HARQ-ACK subcodebook may be generated based on the first HARQ-ACK information bits. The number of the first HARQ-ACK information bits may be the maximum of the product of the number of HARQ bundling groups and the X value across all of the one or more second serving cells. For cells where PDSCH reception carrying two transmission blocks is set (i.e., the number of maximum TB (or codewords) is set to 2 by one DCI) and spatial bundling for HARQ-ACK information (i.e., HARQ-ACK information bits are generated by performing a logical AND operation on the HARQ-ACK information bits corresponding to the first TB and the second TB) is not set, the X value may be 2; otherwise, the X value may be 1.

[0444] Alternatively, if HARQ bundling is not set for one or more of the second serving cells, the second HARQ-ACK subcodebook may be generated based on the second HARQ-ACK information bits. The number of the second HARQ-ACK information bits may be the maximum product of the number of PDSCHs that can be scheduled by a single DCI across all of the one or more second serving cells and the X value. The X value may be 2 for cells where PDSCH reception carrying two transmission blocks is set (i.e., the number of maximum TB (or codewords) is set to 2 by one DCI) and spatial bundling for HARQ-ACK information (i.e., HARQ-ACK information bits are generated by performing a logical AND operation on the HARQ-ACK information bits corresponding to the first TB and the second TB) is not set; otherwise, the X value may be 1.

[0445] Alternatively, a type-2 HARQ-ACK codebook can be configured / generated based on the aforementioned Example 6. Or, based on the aforementioned Example 7, a HARQ-ACK codebook can be configured / generated when some transmissions / receptions of PDSCH scheduled by M-DCI are omitted.

[0446] On the other hand, based on the above-described embodiment 1, when a specific group of the HARQ bundle contains only PDSCHs that overlap with the uplink symbol, the HARQ-ACK information for the specific group may be generated as NACK (negative ACK). Alternatively, when a specific group of the HARQ bundle contains one or more PDSCHs that overlap with the uplink symbol, the HARQ-ACK information for the specific group may be generated by considering the one or more PDSCHs that overlap 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. The terminal can then 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. In addition to the HARQ-ACK codebook, the control information may also include scheduling requests, channel status information, uplink data (in the case of PUSCH), etc.

[0448] Figure 14 illustrates the operation of a base station for a control information transmission and reception method according to one embodiment of the present disclosure.

[0449] Figure 14 illustrates the operation of a base station based on the previously proposed method (e.g., one or more of the (detailed) embodiments from Examples 1-8 and their detailed embodiments). The illustration in Figure 14 is for illustrative purposes only and does not limit the scope of the present disclosure. Some steps illustrated in Figure 14 may be omitted depending on the circumstances and / or settings. Also, the base station in Figure 14 is merely an example and may be embodied by the device illustrated in Figure 15. For example, the processor 102 / 202 in Figure 15 can be controlled to transmit and receive channels / signals / data / information etc. (e.g., RRC signaling, MAC CE, DCI for UL / DL scheduling, SRS, PDCCH, PDSCH, PUSCH, PUCCH, PHICH, etc.) using transceivers (106 / 206), and can be controlled to store the transmitted or received channels / signals / data / information etc. in memory 104 / 204.

[0450] The base station transmits to the terminal configuration information (hereinafter referred to as "first configuration information") for setting up HARQ-ACK bundling for one or more serving cells among the multiple serving cells configured on the terminal (S1401).

[0451] Here, the first configuration information may further include information for setting the type of HARQ-ACK codebook (e.g., 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 (e.g., numberOfHARQBundlingGroups).

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

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

[0454] Multiple PDSCH scheduling may be configured for one or more serving cells among the multiple serving cells configured on the terminal. For serving cells where multiple PDSCH scheduling is not configured, one PDSCH may be scheduled by a single DCI as in the existing system. HARQ-ACK bundling (i.e., time bundling) may be configured for one or more serving cells among the one or more serving cells where multiple PDSCH scheduling is configured. For example, as described above, HARQ-ACK bundling may be configured for a cell by setting the number of HARQ-ACK bundling groups. In this way, HARQ-ACK information may be generated for one or more groups for multiple PDSCHs scheduled on a serving cell where 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 multiple PDSCHs included in each of the one or more groups.

[0455] Here, if the number of HARQ-ACK bundling groups is set to 1, a single HARQ-ACK piece of information may be generated, and if the number of HARQ-ACK bundling groups is set to more than 1, HARQ-ACK pieces of information may be generated for each group. On the other hand, for a serving cell in which multiple PDSCH scheduling is set but HARQ-ACK bundling (i.e., time bundling) is not set, HARQ-ACK pieces of information may be generated for each of the multiple PDSCHs scheduled in that cell.

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

[0457] Here, based on the aforementioned Embodiment 1, time bundling may be set for one or more of the multiple cells configured in the terminal.

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

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

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

[0461] In other words, a base station can send a DCI (for example, a separate DCI format for each serving cell) that schedules one or more PDSCHs in each of the multiple serving cells configured on the terminal. The base station can then send one or more PDSCHs in each of the multiple serving cells configured on the terminal (i.e., send multiple PDSCHs in the multiple serving cells configured overall).

[0462] In this case, DAI signaling may be performed based on any one or more of the detailed embodiments of Example 4 described above, or based on Example 5 described above, or based on Example 7 described above.

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

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

[0465] Alternatively, a type-2 HARQ-ACK codebook may be constructed / generated based on any one or more of the detailed embodiments of Example 4 described above.

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

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

[0468] Here, the first HARQ-ACK subcodebook may be generated for PDSCHs on one or more first serving cells where the number of HARQ bundling groups is set to 1. Then, the second HARQ-ACK subcodebook may be generated for PDSCHs on one or more second serving cells where the number of HARQ bundling groups is set to a value greater than 1.

[0469] On the other hand, if the second configuration information is received first, the first HARQ-ACK subcodebook may be generated for PDSCHs on one or more first serving cells among the multiple serving cells configured in the terminal where the multiple PDSCH scheduling is not configured or the number of HARQ bundling groups is set to 1. Then, the second HARQ-ACK subcodebook may be generated for PDSCHs on one or more second serving cells among the one or more serving cells where the multiple PDSCH scheduling is configured, where the number of HARQ bundling groups is set to more than 1 or HARQ bundling is not configured.

[0470] Here, if HARQ bundling is set for one or more second serving cells, the second HARQ-ACK subcodebook may be generated based on the first HARQ-ACK information bits. The number of the first HARQ-ACK information bits may be the maximum of the product of the number of HARQ bundling groups and the X value across all of the one or more second serving cells. For cells where PDSCH reception carrying two transmission blocks is set (i.e., the maximum number of TB (or codewords) is set to 2 by one DCI) and spatial bundling for HARQ-ACK information (i.e., HARQ-ACK information bits are generated by performing a logical AND operation on the HARQ-ACK information bits corresponding to the first TB and the second TB) is not set, the X value may be 2; otherwise, the X value may be 1.

[0471] Alternatively, if HARQ bundling is not set for one or more second serving cells, the second HARQ-ACK subcodebook may be generated based on the second HARQ-ACK information bits. The number of the second HARQ-ACK information bits may be the maximum product of the number of PDSCHs that can be scheduled by a single DCI across all of the one or more second serving cells and the X value. For cells where PDSCH reception carrying two transmission blocks is set (i.e., the maximum number of TB (or codewords) is set to 2 by one DCI) and spatial bundling for HARQ-ACK information (i.e., generating HARQ-ACK information bits by performing a logical AND operation on the HARQ-ACK information bits corresponding to the first TB and the second TB) is not set, the X value may be 2; otherwise, the X value may be 1.

[0472] Alternatively, a type-2 HARQ-ACK codebook may be configured / generated based on the aforementioned embodiment 6. Or, based on the aforementioned embodiment 7, a HARQ-ACK codebook may be configured / generated when some transmissions / receptions of the PDSCH scheduled by M-DCI are omitted.

[0473] On the other hand, based on the above-described embodiment 1, when a specific group of the HARQ bundle contains only PDSCHs that overlap with the uplink symbol, the HARQ-ACK information for the specific group may be generated as NACK (negative ACK). Alternatively, when a specific group of the HARQ bundle contains one or more PDSCHs that overlap with the uplink symbol, the HARQ-ACK information for the specific group may be generated by considering the one or more PDSCHs that overlap 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 via PUCCH or PUSCH. Here, the HARQ-ACK information may be transmitted from the terminal at the time indicated by the DCI scheduling the PDSCH. In addition to the HARQ-ACK codebook, the control information may also include scheduling requests, channel status information, uplink data (in the case of PUSCH), etc.

[0475] Apparatus to which this disclosure applies in general

[0476] Figure 15 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0477] Referring to Figure 15, the first wireless device 100 and the second wireless device 200 can transmit and receive wireless signals using various wireless connectivity 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 may control the memory 104 and / or the transceiver 106 and be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. For example, the processor 102 may process information in the memory 104 to generate first information / signals and then transmit a wireless signal containing the first information / signals from the transceiver 106. Alternatively, the processor 102 may receive a wireless signal containing second information / signals from the transceiver 106 and then store information obtained from signal processing of the second information / signals in the memory 104. The memory 104 may be linked to the processor 102 and can store various information related to the operation of the processor 102. For example, memory 104 may store software code that includes instructions for performing some or all of the processes controlled by processor 102, or for executing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. Here, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). Transceiver 106 may be coupled with processor 102 and can transmit and / or receive radio signals via one or more antennas 108. Transceiver 106 may include a transmitter and / or receiver. Transceiver 106 may be replaced with an RF (Radio Frequency) unit. In the present invention, wireless equipment may mean a communication modem / circuit / chip.

[0479] The second wireless device 200 includes one or more processors 202, 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 be configured to embody the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. For example, the processor 202 may process information in the memory 204 to generate third information / signals and then transmit a wireless signal containing the third information / signals from the transceiver 206. Alternatively, the processor 202 may receive a wireless signal containing fourth information / signals from the transceiver 206 and then store information obtained from signal processing of the fourth information / signals in the memory 204. The memory 204 may be linked to the processor 202 and can store various information related to the operation of the processor 202. For example, memory 204 may store software code that includes instructions for performing some or all of the processes controlled by processor 202, or for executing the descriptions, functions, procedures, suggestions, methods and / or operation sequence diagrams disclosed herein. Here, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to embody wireless communication technology (e.g., LTE, NR). Transceiver 206 may be coupled with processor 202 and can transmit and / or receive radio signals via one or more antennas 208. Transceiver 206 may include a transmitter and / or receiver. Transceiver 206 may be replaced with an RF unit. In the present invention, wireless equipment may mean a communication modem / circuit / chip.

[0480] The hardware elements of the wireless devices 100,200 will be described in more detail below. However, one or more protocol layers may be embodied by one or more processors 102,202. For example, one or more processors 102,202 may embodied one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102,202 may generate one or more PDUs (Protocol Data Units) and / or one or more SDUs (Service Data Units) by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure. One or more processors 102,202 may generate messages, control information, data or information by means of the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure. One or more processors 102,202 can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information by means of the functions, procedures, suggestions, and / or methods disclosed in this disclosure and provide them to one or more transceivers 106,206. One or more processors 102,202 can receive signals (e.g., baseband signals) from one or more transceivers 106,206 and can acquire PDUs, SDUs, messages, control information, data, or information by means of the descriptions, functions, procedures, suggestions, methods, and / or operation sequence diagrams disclosed in this disclosure.

[0481] One or more processors 102,202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102,202 may be embodied by hardware, firmware, software, or a combination thereof. For 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. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be contained in one or more processors 102,202 or stored in one or more memories 104,204 and driven by one or more processors 102,202. The descriptions, functions, procedures, suggestions, methods and / or sequence diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions and / or sets of instructions.

[0482] One or more memories 104,204 may be connected to one or more processors 102,202 and can store various forms of data, signals, messages, information, programs, code, instructions and / or commands. One or more memories 104,204 may consist of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104,204 may be located inside and / or outside of one or more processors 102,202. Furthermore, one or more memories 104,204 may be connected to one or more processors 102,202 by various technologies such as wired or wireless connections.

[0483] One or more transceivers 106,206 can transmit user data, control information, radio signals / channels, etc., as referred to in the methods and / or operation sequence diagrams of this disclosure, to one or more other devices. One or more transceivers 106,206 can receive user data, control information, radio signals / channels, etc., as referred to in the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure, from one or more other devices. For example, one or more transceivers 106,206 may be coupled with one or more processors 102,202 to 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. Furthermore, 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., as referred to in the descriptions, functions, procedures, proposals, methods and / or operation sequence diagrams disclosed in this disclosure, via one or more antennas 108,208. In this disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106,206 may convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102,202. One or more transceivers 106,206 may convert the user data, control information, radio signals / channels, etc., processed by one or more processors 102,202, from baseband signals to RF band signals. To this end, one or more transceivers 106,206 may include (analog) oscillators and / or filters.

[0484] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly mentioned. Each component or feature may be implemented in a form that does not combine with other components or features. It is also possible to combine some components and / or features to constitute embodiments of the present disclosure. The order of operations described in embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in other embodiments, or replaced by corresponding components or features of other embodiments. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to constitute embodiments, or may be included as new claims by amendment after filing.

[0485] It will be obvious to those skilled in the art that this disclosure can be embodied in other specific forms, provided that the essential features of this disclosure are not deviated from. Therefore, the above-mentioned detailed description should not be constrained in any way and should be considered illustrative. The scope of this disclosure should be determined by a reasonable interpretation of the attached claims, and any modifications within the equivalent scope of this disclosure are included within the scope of this disclosure.

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

[0487] Here, the wireless communication technologies embodied in the wireless devices 100,200 of this disclosure may include, in addition to LTE, NR, and 6G, Narrowband Internet of Things (NB-IoT) for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be embodied by standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the names given above. Additionally or alternatively, the wireless communication technology embodied in the wireless devices (XXX,YYY) of this disclosure may communicate based on LTE-M technology. In this case, for example, 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, LTE-M technology may be embodied by at least one of various standards, including 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 names mentioned above. Additionally or alternatively, wireless communication technologies embodied in the wireless equipment (XXX, YYY) of this disclosure may include at least one of ZigBee®, Bluetooth®, and Low Power Wide Area Network (LPWAN), taking low-power communication into consideration, and is not limited to the names mentioned above. As an example, ZigBee technology can generate personal area networks (PANs) 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 described primarily in terms of its application to 3GPP LTE / LTE-A and 5G systems, it is applicable to a variety of other wireless communication systems as well.

Claims

1. A method for transmitting HARQ (Hybrid Automatic Repeat and Request)-ACK (acknowledgement) information in a wireless communication system, The above method is performed by a terminal, The stage of receiving configuration information that specifies the number of HARQ bundling groups, The process involves receiving DCI (downlink control information) to schedule one or more PDSCHs (physical downlink shared channels) in each of multiple serving cells, The steps include receiving multiple PDSCHs in the multiple serving cells, The step includes transmitting HARQ-ACK information to the plurality of PDSCHs, Based on the provision of the aforementioned configuration information, the HARQ-ACK information is generated for the PDSCH receiving group for the plurality of PDSCHs, A NACK (negative ACK) value is generated for PDSCH receive groups associated only with PDSCHs that overlap with the uplink symbol. The HARQ-ACK codebook corresponding to the HARQ-ACK information includes a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook. Based on the fact that the number of HARQ bundling groups is set to 1 for one or more first serving cells, and that the number of HARQ bundling groups is set to a value greater than 1 for one or more second serving cells, The first HARQ-ACK subcodebook is determined for one or more first serving cells, and A method for determining the second HARQ-ACK subcodebook for one or more second serving cells.

2. The method according to claim 1, further comprising the step of receiving other configuration information for setting up multiple PDSCH scheduling for scheduling multiple PDSCHs by a single DCI for one or more of the multiple serving cells.

3. Based on the fact that HARQ bundling is set for one or more second serving cells, the second HARQ-ACK subcodebook is determined based on the first HARQ-ACK information bits. The number of the first HARQ-ACK information bits corresponds to the maximum value of the product of the number of HARQ bundling groups and the value of X across all of the one or more second serving cells. The method according to claim 1, wherein for a cell in which a PDSCH receiver carrying two transport blocks is set and spatial bundling for HARQ-ACK information is set, the value of X is 1.

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

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

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

7. The method according to claim 1, wherein the HARQ-ACK information for one or more PDSCHs is deemed to be an ACK value or a NACK value based on the fact that one or more PDSCHs overlapping with an uplink symbol are included in the group.

8. A terminal for transmitting HARQ (Hybrid Automatic Repeat and Request)-ACK (acknowledgement) information in a wireless communication system, wherein the terminal is: At least one transmitting / receiving unit for sending and receiving wireless signals, Includes at least one processor for controlling the at least one transmitting / receiving unit, The aforementioned at least one processor is Receive configuration information indicating the number of HARQ bundling groups, Each of the multiple serving cells receives DCI (downlink control information) to schedule one or more PDSCHs (physical downlink shared channels), Multiple PDSCHs are received in the multiple serving cells. It is configured to transmit HARQ-ACK information to the aforementioned multiple PDSCHs, Based on the provision of the aforementioned configuration information, the HARQ-ACK information is generated for the PDSCH receiving group for the plurality of PDSCHs, A NACK (negative ACK) value is generated for PDSCH receive groups associated only with PDSCHs that overlap with the uplink symbol. The HARQ-ACK codebook corresponding to the HARQ-ACK information includes a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook. Based on the fact that the number of HARQ bundling groups is set to 1 for one or more first serving cells, and that the number of HARQ bundling groups is set to a value greater than 1 for one or more second serving cells, The first HARQ-ACK subcodebook is determined for one or more first serving cells, and A terminal in which the second HARQ-ACK subcodebook is determined for one or more second serving cells.

9. A method for receiving HARQ (Hybrid Automatic Repeat and Request)-ACK (acknowledgement) information in a wireless communication system, The above method is performed by a base station. The stage of sending configuration information that specifies the number of HARQ bundling groups, The process involves sending DCI (downlink control information) to schedule one or more PDSCHs (physical downlink shared channels) in each of multiple serving cells, The steps include transmitting multiple PDSCHs in the multiple serving cells, The step includes receiving HARQ-ACK information for the plurality of PDSCHs, Based on the provision of the aforementioned configuration information, the HARQ-ACK information is generated for the PDSCH receiving group for the plurality of PDSCHs, A NACK (negative ACK) value is generated for PDSCH receive groups associated only with PDSCHs that overlap with the uplink symbol. The HARQ-ACK codebook corresponding to the HARQ-ACK information includes a first HARQ-ACK subcodebook and a second HARQ-ACK subcodebook. Based on the fact that the number of HARQ bundling groups is set to 1 for one or more first serving cells, and that the number of HARQ bundling groups is set to a value greater than 1 for one or more second serving cells, The first HARQ-ACK subcodebook is determined for one or more first serving cells, and A method for determining the second HARQ-ACK subcodebook for one or more second serving cells.

Images