Method and device for transmitting and receiving uplink control information in wireless communication system

Abstract

A method and a device for performing communication in a wireless communication system are disclosed. A method performed by a first terminal according to an embodiment of the present disclosure may comprise the steps of: receiving first information related to a first discontinuous transmission (DTX) inactive period of a first cell from a base station; configuring a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook on the basis that a first physical downlink shared channel (PDSCH) reception occasion is excluded from among one or more PDSCH reception occasions of a second cell; and transmitting uplink control information (UCI) including the HARQ-ACK codebook to the base station, wherein the first PDSCH reception occasion of the second cell is based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell, which is included in the first DTX inactive period.

Description

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

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

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users' demand for higher-speed services, necessitating a more advanced mobile communication system.

[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] The technical problem of the present disclosure is to provide a method and device for transmitting and receiving uplink control information in a wireless communication system.

[0005] The technical problem of the present disclosure is to provide a method and device for transmitting and receiving HARQ-ACK information for downlink transmission in a wireless communication system to which network energy saving (NES) is applied.

[0006] The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the technical field to which the present disclosure belongs from the description below.

[0007] A method performed by a terminal in a wireless communication system according to one aspect of the present disclosure comprises the steps of: receiving first information related to a first discontinuous transmission (DTX) inactive period of a first cell from a base station; configuring a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on exclusion of a first PDSCH reception opportunity among at least one physical downlink shared channel (PDSCH) reception occasion of a second cell; and transmitting uplink control information (UCI) including the HARQ-ACK codebook to the base station, wherein the first PDSCH reception opportunity of the second cell may be based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX inactive period.

[0008] In one aspect of the present disclosure, a method performed by a base station in a wireless communication system includes the steps of: transmitting first information related to a first discontinuous transmission (DTX) inactive period of a first cell to a terminal; receiving uplink control information (UCI) including an HARQ-ACK codebook configured by the terminal from the terminal, wherein the HARQ-ACK codebook is configured based on a first PDSCH reception opportunity being excluded from at least one physical downlink shared channel (PDSCH) reception occasion of a second cell, and the first PDSCH reception opportunity of the second cell may be based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX inactive period.

[0009] According to the present disclosure, a method and device for transmitting and receiving uplink control information in a wireless communication system can be provided.

[0010] According to the present disclosure, a method and device for transmitting and receiving HARQ-ACK information for downlink transmission in a wireless communication system to which network energy saving (NES) is applied can be provided.

[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the description below.

[0012] The accompanying drawings, which are incorporated in and are part of the detailed description to aid in understanding the present disclosure, provide embodiments of the present disclosure and, together with the detailed description, describe the technical features of the present disclosure.

[0013] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0014] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0015] FIG. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied.

[0016] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied.

[0017] FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0018] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.

[0019] FIG. 7 is a diagram for explaining an example of a transmission operation of uplink control information of a terminal according to the present disclosure.

[0020] FIG. 8 is a diagram for explaining an example of an operation that supports transmission of uplink control information of a terminal by a base station according to the present disclosure.

[0021] Figure 9 illustrates a Type-1 HARQ-ACK codebook configuration applicable to the present disclosure.

[0022] FIG. 10 illustrates a NES-based PDSCH and related HARQ-ACK codebook configuration and transmission procedure according to an embodiment of the present disclosure.

[0023] FIG. 11 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0024] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to explain exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present disclosure. However, one of ordinary skill in the art will appreciate that the present disclosure may be practiced without these specific details.

[0025] In some cases, to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0026] In the present disclosure, when a component is said to be "connected," "coupled," or "connected" to another component, this may include not only a direct connection but also an indirect connection in which another component exists between them. Furthermore, the terms "comprises" or "has" in the present disclosure specify the presence of the mentioned features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0027] In this disclosure, terms such as “first,” “second,” etc. are used only to distinguish one component from another and are not used to limit the components, and do not limit the order or importance between the components unless specifically stated otherwise. Accordingly, 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.

[0028] The terminology used herein is for the purpose of describing particular embodiments and is not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. The term "and / or" as used herein may refer to any one of the associated enumerated items, or is meant to refer to and encompass any and all possible combinations of two or more of them. Furthermore, the use of " / " between words in this disclosure has the same meaning as "and / or" unless otherwise stated.

[0029] The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in the wireless communication network may be performed in a process of controlling the network and transmitting or receiving a signal from a device (e.g., a base station) that manages the wireless communication network, or in a process of transmitting or receiving a signal to or between terminals connected to the wireless network.

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

[0031] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI (Artificial Intelligence) system / module, RSU (road side unit), robot, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, UAV (Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0032] The following technologies can be used in various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, and SC-FDMA. CDMA can be implemented using wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (Global System for Mobile communications) / GPRS (General Packet Radio Service) / EDGE (Enhanced Data Rates for GSM Evolution). OFDMA can be implemented using 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 a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

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

[0034] For 3GPP LTE, see 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).

[0035] For 3GPP NR, see 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 (Overall description of NR and New Generation-Radio Access Network (NG-RAN)), and TS 38.331 (Radio Resource Control Protocol Specification).

[0036] Abbreviations for terms that may be used in this disclosure are defined as follows.

[0037] - BM: beam management

[0038] - CQI: Channel Quality Indicator

[0039] - CRI: Channel state information - reference signal resource indicator

[0040] - CSI: Channel State Information

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

[0042] - CSI-RS: Channel state information - reference signal

[0043] - DMRS: Demodulation Reference Signal

[0044] - FDM: frequency division multiplexing

[0045] - FFT: fast Fourier transform

[0046] - IFDMA: interleaved frequency division multiple access

[0047] - IFFT: inverse fast Fourier transform

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

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

[0050] - MAC: Medium Access Control

[0051] - NZP: non-zero power

[0052] - OFDM: orthogonal frequency division multiplexing

[0053] - PDCCH: Physical downlink control channel

[0054] - PDSCH: Physical downlink shared channel

[0055] - PMI: precoding matrix indicator

[0056] - RE: resource element

[0057] - RI: Rank indicator

[0058] - RRC: Radio Resource Control

[0059] - RSSI: Received signal strength indicator

[0060] - Rx: Reception

[0061] - QCL: quasi co-location

[0062] - SINR: signal to interference and noise ratio

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

[0064] - TDM: Time Division Multiplexing

[0065] - TRP: transmission and reception point

[0066] - TRS: Tracking Reference Signal

[0067] - Tx: transmission

[0068] - UE: user equipment

[0069] - ZP: Zero Power

[0070] System General

[0071] As more and more communication devices demand greater communication capacity, the need for improved mobile broadband communications compared to existing radio access technologies (RATs) is emerging. Furthermore, massive machine type communications (MTC), which connects numerous devices and objects to provide diverse services anytime, anywhere, is also a key issue to be considered in next-generation communications. Furthermore, communication system design that considers reliability and latency-sensitive services / terminals is being discussed. Accordingly, the introduction of next-generation RATs that consider enhanced mobile broadband communication (eMBB), massive MTC (MMTC), and ultra-reliable and low latency communication (URLLC) is being discussed. For convenience, these technologies are referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.

[0072] A new RAT system, including NR, uses OFDM or a similar transmission 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 under different numerologies can coexist within a single cell.

[0073] A 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.

[0074] Figure 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0075] Referring to Fig. 1, the NG-RAN consists of gNBs that provide NG-RA (NG-Radio Access) user plane (i.e., new AS (access stratum) sublayer / PDCP (packet data convergence protocol) / RLC (radio link control) / MAC / PHY) and control plane (RRC) protocol termination for UE. The gNBs are interconnected via Xn interfaces. 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.

[0076] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0077] NR systems can support multiple numerologies. Numerologies can be defined by subcarrier spacing and cyclic prefix (CP) overhead. Multiple subcarrier spacings can be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band. Furthermore, NR systems can support various frame structures corresponding to multiple numerologies.

[0078] Below, we examine OFDM numerologies and frame structures that can be considered in NR systems. The various OFDM numerologies supported in NR systems can be defined as shown in Table 1 below.

[0079] μΔf=2 μ ·15 [kHz]CP015 Normal 130 Normal 260 Normal, Extended 3120 Normal 4240 Normal

[0080] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands, when the SCS is 30 kHz / 60 kHz, it supports dense-urban, lower latency, and wider carrier bandwidth, and when the SCS is 60 kHz or higher, it supports a bandwidth larger than 24.25 GHz to overcome phase noise. The NR frequency band is defined by two types of frequency ranges (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. In addition, FR2 can mean millimeter wave (mmW).

[0081] Frequency Range Designation Corresponding Frequency Range Subcarrier Spacing FR1410MHz - 7125MHz 15, 30, 60kHz FR224250MHz - 52600MHz 60, 120, 240kHz

[0082] Regarding the frame structure in the NR system, the sizes of the various fields in the time domain are T c =1 / (Δf max ·N f ) is expressed as a multiple of the time unit. Here, Δf max =480·10 3 Hz, and N f =4096. Downlink and uplink transmissions are T f =1 / (Δf max N f / 100)·T c = It is organized into radio frames with a duration of 10ms. Here, each radio frame is T sf =(Δf max N f / 1000)·T c = It consists of 10 subframes with a duration of 1ms. In this case, there may be one set of frames for uplink and one set of frames for downlink. In addition, transmission in uplink frame number i from a terminal is T earlier than the start of the corresponding downlink frame from the terminal. TA =(N TA +N TA,offset )T c It should start before. For the subcarrier spacing configuration μ, slots are n within a subframe. s μ ∈{0,..., N slot subframe,μ-1} are numbered in increasing order, and n within a radio frame. s,f μ ∈{0,..., N slot frame,μ -1} are numbered in increasing order. One slot is N symb slot It consists of consecutive OFDM symbols, and N symb slot is determined by CP. Slot n in subframe s μ The start of OFDM symbol n in the same subframe s μ N symb slot are aligned temporally with the start of the OFDM signal. Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or uplink slot can be utilized.

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

[0084] μN symb slot N slot frame,μ N slot subframe,μ01410111420221440431480841416016

[0085] μN symb slot N slot frame,μ N slot subframe,μ212404

[0086] FIG. 2 is an example when μ=2 (SCS is 60 kHz), and referring to Table 3, 1 subframe can include 4 slots. 1 subframe={1,2,4} slots illustrated in FIG. 2 is an example, and the number of slot(s) that can be included in 1 subframe is defined as in Table 3 or Table 4. In addition, a mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols. With respect to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered. Hereinafter, the physical resources that can be considered in an NR system will be described in detail. First, with respect to antenna ports, antenna ports are defined such that the channel through which a symbol on an antenna port is carried can be inferred from the channel through which another symbol on the same antenna port is carried. Two antenna ports are said to be in a QC / QCL (quasi co-located or quasi co-location) relationship if the large-scale properties of the channel through which a symbol on one antenna port is carried can be inferred from the channel through which a symbol on another antenna port is carried. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0087] Fig. 3 illustrates a resource grid in a wireless communication system to which the present disclosure can be applied. Referring to Fig. 3, the resource grid is N in the frequency domain. RB μ N sc RB It consists of subcarriers, and one subframe is 14·2 μ It is described as an example, but not limited to, that it consists of OFDM symbols. In an NR system, the transmitted signal is N RB μ N sc RB One or more resource grids consisting of subcarriers and 2 μ N symb (μ) is described by OFDM symbols. Here, N RB μ ≤N RB max,μ is. The above N RB max,μ represents the maximum transmission bandwidth, which may vary not only between numerologies but also between uplink and downlink. In this case, one resource grid may be configured for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is referred to as a resource element and is uniquely identified by an index pair (k, l').

[0088] Here, k=0,...,N RB μ N sc RB -1 is the index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 indicates the position of the symbol within the subframe. When referring to a resource element in a slot, an index pair (k,l) is used. Here, l=0,...,N symb μ-1. The resource element (k,l') for μ and antenna port p is a complex value a k,l' (p,μ) . If there is no risk of confusion or if a particular antenna port or numerology is not specified, the indices p and μ can be dropped, resulting in a complex value of a k,l' (p) or a k,l' This can be. Also, a resource block (RB) is N in the frequency domain. sc RB =12 is defined as consecutive subcarriers.

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

[0090] - offsetToPointA for the Primary Cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the UE for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

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

[0092] Common resource blocks (CRBs) are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of CRB 0 for a subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between the resource elements (k, l) and the subcarrier spacing setting μ is given by the following mathematical expression 1.

[0093]

[0094] In Equation 1, k is defined relative to point A such that k = 0 corresponds to the subcarrier centered at point A. Physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ -Numbered from -1, where i is the number of BWP. Physical resource block n in BWP i PRB and common resource block n CRB The relationship between them is given by the mathematical formula 2 below.

[0095]

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

[0097] FIG. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied. FIG. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0098] Referring to FIGS. 4 and 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot includes seven symbols, but in the case of an extended CP, one slot includes six symbols.

[0099] A carrier comprises multiple subcarriers in the frequency domain. An RB (Resource Block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth 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 can comprise up to N (e.g., 5) BWPs. Data communication is performed through activated BWPs, and only one BWP can be activated for a single terminal. Each element in the resource grid is referred to as a Resource Element (RE), to which one complex symbol can be mapped.

[0100] The NR system can support up to 400 MHz per component carrier (CC). If a terminal operating in such a wideband CC always operates with the radio frequency (RF) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, when considering multiple use cases operating within a single wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Alternatively, each terminal may have different maximum bandwidth capabilities. Considering this, the base station can instruct the terminal to operate only in a portion of the bandwidth of the wideband CC, rather than the entire bandwidth. This portion of bandwidth is conveniently defined as the bandwidth part (BWP). A BWP can be composed of consecutive RBs on the frequency axis and can correspond to a single numerology (e.g., subcarrier spacing, CP length, slot / mini-slot interval).

[0101] Meanwhile, a base station can configure multiple BWPs even within a single CC configured for a terminal. For example, a BWP occupying a relatively small frequency domain can be configured in a PDCCH monitoring slot, while the PDSCH indicated by the PDCCH can be scheduled on a larger BWP.

[0102] Alternatively, if UEs are concentrated in a specific BWP, some UEs can be assigned to different BWPs for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, some spectrum in the middle of the total bandwidth can be excluded and both BWPs can be assigned within the same slot. In other words, the base station can assign at least one DL / UL BWP to UEs associated with a wideband CC.

[0103] The base station can activate at least one DL / UL BWP among the DL / UL BWP(s) configured at a specific point in time (by L1 signaling or MAC CE (Control Element) or RRC signaling, etc.). In addition, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, switching to a designated DL / UL BWP may be performed when a timer value expires based on a timer. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, since the UE may not receive the configuration for the DL / UL BWP when performing the initial access process or before the RRC connection is set up, the DL / UL BWP assumed by the UE in such a situation is defined as the initially active DL / UL BWP.

[0104] FIG. 6 illustrates physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the same.

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

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

[0107] A terminal that has completed an initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).

[0108] Meanwhile, when accessing a base station for the first time or when there are no radio resources for signal transmission, the terminal may perform a random access procedure (RACH) with the base station (steps S603 to S606). To this end, the terminal may transmit a specific sequence as a preamble via the random access channel (RACH) (steps S603 and S605) and receive a response message to the preamble via the PDCCH and the corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure may additionally be performed.

[0109] The terminal that has performed the procedure described above can then perform PDCCH / PDSCH reception (S607) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S608) as general uplink / downlink signal transmission procedures. In particular, the terminal receives downlink control information (DCI) through the PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and its format varies depending on its intended use.

[0110] Meanwhile, the control information that the terminal transmits to the base station via the uplink or that the terminal receives from the base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In the case of the 3GPP LTE system, the terminal can transmit the above-described control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

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

[0112] DCI Format Utilization 0_0 Scheduling of PUSCH within a cell 0_1 Scheduling of one or multiple PUSCH within a cell, or indicating cell group (CG: cell group) downlink feedback information to the UE 0_2 Scheduling of PUSCH within a cell 1_0 Scheduling of PDSCH within a DL cell 1_1 Scheduling of PDSCH within a cell 1_2 Scheduling of PDSCH within a cell

[0113] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to scheduling of PUSCH (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.), multi-antenna related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information (e.g., PUSCH power control, etc.), and control information included in each DCI format may be predefined.

[0114] DCI format 0_0 is used for scheduling PUSCH in a cell. The information contained in DCI format 0_0 is transmitted after being scrambled with a CRC (cyclic redundancy check) by a C-RNTI (cell radio network temporary identifier, Cell RNTI), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI).

[0115] DCI format 0_1 ​​is used to indicate scheduling of one or more PUSCHs in a cell, or configure grant (CG) downlink feedback information to the UE. The information contained in DCI format 0_1 ​​is CRC-scrambled and transmitted using the C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI.

[0116] DCI format 0_2 is used for scheduling PUSCH in a cell. The information contained in DCI format 0_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

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

[0118] DCI format 1_0 is used for scheduling PDSCH in a DL cell. The information contained in DCI format 1_0 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0119] DCI format 1_1 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_1 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0120] DCI format 1_2 is used for scheduling PDSCH in a single cell. The information contained in DCI format 1_2 is CRC-scrambled and transmitted using C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0121] Transmission and reception of HARQ-ACK (hybrid automatic repeat request-acknowledgement) information considering network energy saving (NES)

[0122] A terminal can support beamforming-based reception for downlink reception. That is, the terminal can receive a downlink signal using a specific beam among multiple candidate beams. When the terminal is in connected mode, the base station and the terminal can maintain an optimal beam for the terminal through a beam management (BM) process. Accordingly, the base station can transmit a downlink physical channel (e.g., PDCCH, PDSCH, etc.) using an optimal transmit (TX) beam suitable for the terminal, and the terminal can receive the downlink physical channel using an optimal receive (RX) beam.

[0123] To improve wireless communication systems, methods to reduce power consumption of network nodes (e.g., base stations, cells, TRPs, relays, etc.) are being discussed.

[0124] In this regard, considering the power saving operation (NES) of the network node, a PDSCH transmission / reception section that the terminal cannot receive may occur, and a problem may arise in which unnecessary AHRQ-ACK information is included in the HARQ-ACK codebook.

[0125] In this disclosure, a method for a terminal connected to a base station performing an NES operation to receive transmission / retransmission for a downlink channel (e.g., PDSCH) and configure a HARQ-ACK codebook for the downlink channel depending on whether the NES operation is performed is described through various examples. The examples below mainly assume transmission / reception operations of a PDSCH and HARQ-ACK information therefor, but the scope of the present disclosure is not limited thereto, and the examples of the present disclosure can be similarly applied to other downlink channels and HARQ-ACK information therefor.

[0126] In the present disclosure, the fact that a network node (e.g., a base station) operates in NES mode may mean that the following operations are performed. For example, the network node may set multiple intervals (i.e., discontinuous transmission (DTX) intervals of the network node) in advance to disable / OFF transmission of specific DL signal(s) during specific time intervals. The network node may dynamically indicate to a terminal one of the multiple OFF intervals set. The terminal may be aware that the DL signal associated with the OFF interval will not be transmitted from the network node within the indicated OFF interval. Accordingly, power consumption of the network node and the terminal may be saved.

[0127] In NES mode, OFF intervals can be defined in the time, frequency, and / or spatial domains. For example, OFF intervals can be defined in the time domain, and the time lengths of multiple OFF intervals can be the same or different. For example, OFF intervals can be defined in the frequency domain, such as through BWP switching, dynamic RB adaptation, etc. For example, OFF intervals can also be defined in the spatial domain by semi-statically or dynamically disabling a specific antenna port of a network node (i.e., the network node does not transmit / receive radio signals through that antenna port).

[0128] To implement the operations described herein, a network node can activate or deactivate the NES mode. For example, if a single base station controls multiple cells, the NES mode can be activated or deactivated independently for each cell. Furthermore, the network node can also inform the terminal of information regarding the NES activation or deactivation.

[0129] Unless otherwise specified in the present disclosure, configuration of a terminal by a base station may include providing the corresponding configuration information to the terminal via higher layer (e.g., RRC) signaling. Unless otherwise specified in the present disclosure, commands / instructions by a base station to a terminal may include providing the commands / instructions to the terminal via MAC CE and / or DCI. Unless otherwise specified in the present disclosure, predefined information for a base station and a terminal may include information that the base station and the terminal already have without separate signaling / command / instruction.

[0130] In the present disclosure, with respect to the operation of a terminal connected to a network node supporting NES operation, different first and second sections may be set / determined according to one or more of the following cases.

[0131] - Case 1. The first section operates in NES mode and the second section operates in non-NES mode.

[0132] - Case 2. The first interval is the inactive time of the cell DTX and the second interval is the active time of the cell DTX (i.e., the first interval corresponds to the time interval during which the network node does not transmit (TX) to a specific cell, and the second interval corresponds to the time interval during which the network node transmits (TX) to a specific cell).

[0133] - Case 3. The first period is the inactive time of the terminal DRX and the second period is the active time of the terminal DRX (i.e., the first period corresponds to the time period in which the terminal does not perform reception (RX), and the second period corresponds to the time period in which the terminal performs reception (RX).

[0134] - Case 4. The first period is the inactive time of the cell DRX and the second period is the active time of the cell DRX (i.e., the first period corresponds to the time period in which the network node does not perform reception (RX), and the second period corresponds to the time period in which the network node performs reception (RX).

[0135] - Case 5. The first period is the inactive time of the terminal DTX and the second period is the active time of the terminal DTX (i.e., the first period corresponds to the time period during which the terminal does not perform transmission (TX), and the second period corresponds to the time period during which the terminal performs transmission (TX).

[0136] Based on the configuration of the network node, only the second interval or both the first interval and the second interval may be configured for each cell, BWP, frequency, RS for RLF (radio link failure), antenna port (AP), AP group, and / or antenna element group.

[0137] With respect to the first and second sections described above, a time section other than the first section may correspond to the second section, and a time section other than the second section may correspond to the first section. Additionally, the network node may separately set the first section and the second section for each of the cases described above. At this time, for different cases, a case may arise where a specific time section is the first section or the second section. Considering this, if a specific time section belongs only to the first section, the terminal may perform the operation of the first section of the present disclosure, and if it belongs only to the second section, the terminal may perform the operation of the second section of the present disclosure. Additionally or alternatively, if the first and second sections overlap, the terminal may perform only the operation of the first section of the present disclosure or may preferentially perform the operation of the first section. Additionally or alternatively, if the first and second sections overlap, the terminal may perform only the operation of the second section of the present disclosure or may preferentially perform the operation of the second section.

[0138] In this disclosure, based on the first and second sections related to NES, a method for transmitting and receiving downlink channels and uplink feedback information therefor by network nodes and terminals is described through specific examples.

[0139] FIG. 7 is a diagram for explaining an example of a transmission operation of uplink control information of a terminal according to the present disclosure.

[0140] In FIGS. 7 and 8, the first cell may be expressed as a scheduling cell, a NES cell, a DTX-enabled cell, etc., and the second cell may be expressed as a scheduled cell, a non-NES cell, a DTX-enabled cell, etc.

[0141] The terminal can receive first information related to the first DTX (discontinuous transmission) inactive period of the first cell from the base station (S710).

[0142] Here, the first DTX deactivation period may be associated with a network energy saving (NES) mode for the first cell. For example, the terminal may be configured / instructed with information regarding a time period related to the NES mode-based operation of the network through upper layer signaling and / or dynamic signaling. The terminal may determine / define the activation period and the deactivation period based on the information. In this regard, with respect to the NES operation of the network, any period other than the first DTX period within the first cell may correspond to an activation period.

[0143] The first information for setting / indicating the first DTX deactivation period on the first cell may be transmitted to the terminal via a system information block (SIB), an RRC message, a MAC-CE, or / and DCI.

[0144] Based on the fact that the first PDSCH reception opportunity is excluded from at least one physical downlink shared channel (PDSCH) reception opportunity of the second cell, the terminal may configure a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook (S720).

[0145] Here, the first PDSCH reception opportunity of the second cell may be based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX deactivation period. That is, at least one PDSCH transmitted from the second cell may be scheduled by a PDCCH transmitted from the first cell.

[0146] For example, the HARQ-ACK codebook may be configured with HARQ-ACK information for each PDSCH transmission in the remaining PDSCH reception opportunities except for the first PDSCH reception opportunity associated with the first PDCCH monitoring opportunity belonging to the first DTX period of the first cell. In addition, the HARQ-ACK codebook may be configured regardless of the second DTX deactivation period set in the second cell.

[0147] As an example of the present disclosure, the HARQ-ACK codebook may include HARQ-ACK information for each PDSCH reception in the remaining PDSCH reception opportunities except for the first PDSCH reception opportunity among at least one PDSCH reception opportunity of the second cell, and may not include ACK information related to the first PDSCH reception opportunity of the second cell.

[0148] As another example of the present disclosure, the HARQ-ACK codebook may include HARQ-ACK information for each PDSCH reception in the remaining PDSCH reception opportunities excluding the first PDSCH reception opportunity among at least one PDSCH reception opportunity of the second cell, and may include NACK information related to the first PDSCH reception opportunity of the second cell. That is, the terminal may generate a NACK for the first PDSCH reception opportunity based on the first PDCCH monitoring opportunity belonging to the first DTX period of the first cell, and include the generated NACK in the HARQ-ACK codebook.

[0149] Among at least one PDSCH reception opportunity of the second cell, each PDSCH reception in the remaining PDSCH reception opportunities, excluding the first PDSCH reception opportunity, may be based on a second PDCCH monitoring opportunity that is not included in the first DTX deactivation period. That is, each PDSCH reception in the remaining PDSCH reception opportunities may be scheduled / activated by the PDCCH in the second PDCCH monitoring opportunity.

[0150] Here, the configuration of the HARQ-ACK codebook can be semi-statically set by the base station. That is, the terminal can configure a type-1 HARQ-ACK codebook (or semi-static codebook) according to the base station settings.

[0151] The terminal can transmit uplink control information (UCI) containing the HARQ-ACK codebook to the base station (S730). For example, the terminal can transmit UCI to the base station via the PUCCH or PUSCH.

[0152] For example, a terminal may transmit UCI to a base station in a specific UL slot. At least one PDSCH reception opportunity may be established based on at least one slot offset relative to a specific uplink slot. That is, the specific uplink slot may be a slot that is shifted by at least one slot offset relative to the slot(s) in which at least one PDSCH reception opportunity of the second cell is established. The terminal may receive at least one slot offset from the base station via an RRC message or DCI.

[0153] The method performed by the terminal described in the example of FIG. 7 may be performed by the first device (100) of FIG. 11. For example, one or more processors (102) of the first device (100) of FIG. 11 may receive first information related to a first DTX inactivation period of a first cell from a base station through one or more transceivers (106). Based on the exclusion of the first PDSCH reception opportunity among at least one PDSCH reception opportunity of a second cell, the one or more processors (102) may configure a HARQ-ACK codebook. The one or more processors (102) may transmit a UCI including the HARQ-ACK codebook to the base station through one or more transceivers (106).

[0154] The above memory (104) can store instructions for performing the method described in the example of FIG. 7 when executed by one or more processors (102).

[0155] FIG. 8 is a diagram for explaining an example of an operation that supports transmission of uplink control information of a terminal by a base station according to the present disclosure.

[0156] The base station can transmit first information related to the first DTX deactivation period of the first cell to the terminal (S810).

[0157] That is, the base station can set / instruct the terminal to set the first DTX deactivation period of the first cell, and may not transmit other channels / signals during the first DTX deactivation period.

[0158] The base station can receive a UCI including a HARQ-ACK codebook from the terminal (S820).

[0159] Here, based on the exclusion of the first PDSCH reception opportunity among at least one PDSCH reception opportunity of the second cell, the HARQ-ACK codebook may be configured by the terminal. In addition, the first PDSCH reception opportunity of the second cell may be based on the first PDCCH monitoring opportunity of the first cell included in the first DTX deactivation period. Since the description related to the HARQ-ACK codebook has been described with reference to FIG. 7, a duplicate description will be omitted.

[0160] The method performed by the base station described in the example of FIG. 8 may be performed by the second device (200) of FIG. 11. For example, one or more processors (202) of the second device (200) of FIG. 11 may transmit first information related to the first DTX inactivity period of the first cell to the terminal via one or more transceivers (206). The one or more processors (202) may receive UCI including a HARQ-ACK codebook from the terminal via one or more transceivers (206).

[0161] Furthermore, one or more memories (204) of the second device (200) may store instructions for performing the method described in the example of FIG. 8 when executed by one or more processors (202).

[0162] Below, various examples of NES-based PDSCH and HARQ-ACK codebook configuration and transmission / reception according to the present disclosure are described.

[0163] Example 1

[0164] This embodiment relates to a method for transmitting and receiving PDSCH and HARQ-ACK information via PUCCH / PUSCH based on a time interval related to NES.

[0165] When the first and second sections are set as described above, the terminal may be configured to receive only a PDSCH including a DL slot / symbol corresponding to the second section. Additionally or alternatively, in this case, the terminal may be configured to receive only a PDSCH that does not include a DL slot / symbol corresponding to the first section (i.e., a PDSCH that does not overlap with the first section). Additionally or alternatively, in this case, the terminal may be configured to receive only a PDSCH in which all DL slots / symbols constituting the PDSCH are included in the second section (i.e., a PDSCH that is fully included in the second section).

[0166] Here, the PDSCH may correspond to a PDSCH that is dynamically scheduled through DCI, an SPS PDSCH that is periodically allocated, or a PDSCH that retransmits a transport block (TB) of an SPS PDSCH.

[0167] In relation to the PDSCH procedure considering the aforementioned NES, a network node may allocate resources (i.e., PUCCH resources) of the PUCCH (hereinafter, referred to as A / N PUCCH for clarity of explanation) for transmitting and receiving HARQ-ACK information for the PDSCH. In this regard, the resources may be allocated through DCI scheduling the PDSCH or non-scheduling DCI. For example, non-scheduling DCI may include DCI with an invalid FDRA field or DCI activating / releasing SPS.

[0168] At this time, the terminal may transmit the A / N PUCCH only during the activation time of the second interval, or may transmit the A / N PUCCH only during a separate UL-specific activation time or PUCCH-specific activation time aligned with the activation time of the second interval. For example, if the terminal receives the PDSCH during the activation time of the second interval, the separate UL-specific activation time or PUCCH-specific activation time may be set before / after a certain offset based on the activation time of the second interval.

[0169] In this regard, when a UL-specific activation time or a PUCCH-specific activation time is set, the UE may define a time interval for the UL-specific activation time or the PUCCH-specific activation time, and when the UL-specific activation time or the PUCCH-specific activation time is not set, the UE may define an activation time interval of the second interval. The UE may transmit a HARQ-ACK for an SPS PDSCH received in the defined time interval via the PUCCH or PUSCH. In this case, the UE may transmit the PUCCH / PUSCH only when all UL slot(s) or UL symbol(s) of the PUCCH or PUSCH are included within the defined time interval. That is, the UE may be configured / defined to transmit HARQ-ACK information for the SPS PDSCH only when all UL slot(s) or UL symbol(s) of the PUCCH or PUSCH are included within the defined time interval. Alternatively, the terminal may be configured / defined to transmit PUCCH / PUSCH even if only some of the UL slot(s) or UL symbol(s) of PUCCH or PUSCH are included within the defined time interval.

[0170] In relation to the above-described operation, if the resources of PUCCH / PUSCH for transmitting / receiving HARQ-ACK information for PDSCH are not included in the above-described defined time interval (e.g., the time interval determined / defined to activate the operation of the network node / terminal), or are included only in part, the terminal may operate based on one or more of the following options, depending on the settings of the network node, etc.

[0171] Option 1-1

[0172] The terminal may operate to transmit the corresponding PUCCH or PUSCH.

[0173] For example, if a terminal receives an SPS PDSCH transmitted in whole or in part during the activation time of the second period, the terminal can transmit the PUCCH / PUSCH even if the PUCCH / PUSCH for transmitting HARQ-ACK information therefor is not included in the defined time period or is included only in part.

[0174] However, if an SPS PDSCH transmission occurs that is not entirely or partially included in the activation time of the second period (i.e., an SPS PDSCH transmission that overlaps the deactivation time of the first period occurs), the terminal may not transmit a PUCCH / PUSCH for transmitting HARQ-ACK information for the SPS PDSCH, regardless of whether the terminal receives the SPS PDSCH.

[0175] For another example, if a terminal receives a PDSCH transmitted in whole or in part during the activation time of the second period, even if the PUCCH / PUSCH resource for transmitting HARQ-ACK information for the same is not included in the defined time period or is only partially included, the terminal may not transmit the corresponding PUCCH / PUSCH. Thereafter, if some or all of an alternative PUCCH resource configured by the base station through higher layer signaling (e.g., RRC, etc.) or indicated through DCI is included in the defined time period, the terminal may transmit HARQ-ACK information for the corresponding PDSCH through the alternative PUCCH resource.

[0176] In this regard, the alternative PUCCH resource may be set as a PUCCH resource delayed by an offset from the PUCCH slot that the terminal was unable to transmit. Here, the offset value may be set via higher-layer signaling (e.g., RRC, etc.) or indicated via DCI.

[0177] Alternatively, the alternative PUCCH resource may be allocated by DCI indicating the PUCCH resource that could not be transmitted. For example, the DCI may be defined to indicate not only the K1 value (i.e., slot offset value) and the PRI (PUCCH resource indicator) value for the PUCCH resource that could not be transmitted, but also the K1 value (hereinafter referred to as the alternative K1 value) and the PRI value (hereinafter referred to as the alternative PRI value) for the alternative PUCCH resource. Alternatively, information on the alternative K1 value and the alternative PRI value may be configured via higher layer signaling (e.g., RRC, etc.) or may be indicated via DCI indicating cell DRX / DTX related information. If the base station does not separately configure / indicate the alternative PRI value, the UE may also apply the PRI value for the PUCCH resource that could not be transmitted to the alternative PUCCH resource.

[0178] Alternatively, the base station can allocate alternative PUCCH resources through a separate DCI. In this case, the separate DCI can be defined to indicate both an alternative K1 value and an alternative PRI value. If the base station does not separately set / indicate an alternative PRI value, the terminal can also apply the PRI value for the PUCCH resources that were not transmitted to the alternative PUCCH resources. The separate DCI is CRC scrambled based on a separate RNTI / C-RNTI / CS-RNTI and can be transmitted and received during the activation time of the second period. In addition, the separate DCI can be a non-scheduling DCI that schedules a new PDSCH during the activation time of the second period, or does not schedule a PDSCH.

[0179] Additionally, deferred HARQ-ACK information for an alternative PUCCH resource for the corresponding PDSCH may be configured as a separate sub-codebook. In this case, when the deferred HARQ-ACK information is multiplexed with new HARQ-ACK information for a PDSCH received after the start of the activation time of the second period, the terminal may configure a HARQ-ACK codebook by concatenating a separate sub-codebook for the deferred HARQ-ACK information with a sub-codebook for the new HARQ-ACK information.

[0180] Additionally, with respect to the aforementioned method, even if the corresponding PUCCH / PUSCH exists within a defined time interval, the terminal may exceptionally be configured / defined to transmit the corresponding PUCCH / PUSCH, depending on the configuration (e.g., RRC configuration) or instruction (e.g., MAC CE, DCI, etc.) of the network node.

[0181] Options 1-2

[0182] The terminal may operate to skip the corresponding PUCCH or PUSCH, or may operate to not transmit the corresponding HARQ-ACK information by considering the corresponding HARQ-ACK information as disabled.

[0183] Options 1-3

[0184] The terminal may delay the corresponding PUCCH or PUSCH after the activation time and transmit the delayed HARQ-ACK information through an alternative PUCCH resource. In this case, the activation time may be the previously defined time, i.e., the activation time of the second period and / or the UL / PUCCH-specific activation time.

[0185] In this regard, the alternative PUCCH resource may be set as a PUCCH resource delayed by an offset from the PUCCH slot that the terminal was unable to transmit. Here, the offset value may be set via higher-layer signaling (e.g., RRC, etc.) or indicated via DCI.

[0186] Alternatively, the alternative PUCCH resource may be allocated by DCI indicating the PUCCH resource that could not be transmitted. For example, the DCI may be defined to indicate not only the K1 value (i.e., slot offset value) and the PRI (PUCCH resource indicator) value for the PUCCH resource that could not be transmitted, but also the K1 value (hereinafter referred to as the alternative K1 value) and the PRI value (hereinafter referred to as the alternative PRI value) for the alternative PUCCH resource. Alternatively, information on the alternative K1 value and the alternative PRI value may be configured via higher layer signaling (e.g., RRC, etc.) or may be indicated via DCI indicating cell DRX / DTX related information. If the base station does not separately configure / indicate the alternative PRI value, the UE may also apply the PRI value for the PUCCH resource that could not be transmitted to the alternative PUCCH resource.

[0187] Alternatively, the base station can allocate alternative PUCCH resources through a separate DCI. In this case, the separate DCI can be defined to indicate both an alternative K1 value and an alternative PRI value. If the base station does not separately set / indicate an alternative PRI value, the terminal can also apply the PRI value for the PUCCH resources that were not transmitted to the alternative PUCCH resources. The separate DCI is CRC scrambled based on a separate RNTI / C-RNTI / CS-RNTI and can be transmitted and received during the activation time of the second period. In addition, the separate DCI can be a non-scheduling DCI that schedules a new PDSCH during the activation time of the second period, or does not schedule a PDSCH.

[0188] Additionally, deferred HARQ-ACK information for an alternative PUCCH resource for the corresponding PDSCH may be configured as a separate sub-codebook. In this case, when the deferred HARQ-ACK information is multiplexed with new HARQ-ACK information for a PDSCH received after the start of the activation time of the second period, the terminal may configure a HARQ-ACK codebook by concatenating a separate sub-codebook for the deferred HARQ-ACK information with a sub-codebook for the new HARQ-ACK information.

[0189] Options 1-4

[0190] Since the corresponding PUCCH / PUSCH cannot be transmitted, the terminal may operate to invalidate or skip the corresponding PDSCH.

[0191] That is, the terminal cannot transmit HARQ-ACK information for the corresponding PDSCH via the aforementioned PUCCH / PUSCH within the defined time interval. Accordingly, even if the corresponding PDSCH is included in the second interval, the terminal may not receive the corresponding PDSCH, invalidate the received TB, or invalidate the corresponding PDSCH resource.

[0192] Additionally, in addition to actions based on one or more of the aforementioned options, the terminal may perform the following exceptional actions:

[0193] For example, if the DCI received by the terminal schedules transmission of a PDSCH that is not entirely or partially included in the activation time of the second period, it may be considered that transmission of a PUCCH / PUSCH for transmitting and receiving HARQ-ACK information for the corresponding PDSCH is entirely or partially included in the defined time period. In this case, the terminal may operate to receive the corresponding PDSCH and transmit HARQ-ACK information therefor through the corresponding PUCCH / PUSCH. Alternatively, the terminal may operate not to receive the corresponding PDSCH and not to transmit HARQ-ACK information therefor. Alternatively, the terminal may operate not to transmit HARQ-ACK information therefor regardless of whether the corresponding PDSCH is received. Alternatively, the terminal may operate to transmit NACK information through the corresponding PUCCH / PUSCH regardless of whether the corresponding PDSCH is received.

[0194] For another example, even if the transmission of PUCCH / PUSCH for transmitting and receiving HARQ-ACK information is fully or partially included in the defined time interval, a case may be considered in which transmission of PDSCH occurs that is not fully or partially included in the activation time of the second interval. In this case, the terminal may receive the corresponding PDSCH and operate so as not to transmit HARQ-ACK information therefor through the corresponding PUCCH / PUSCH. Alternatively, the terminal may operate so as to transmit NACK information through the corresponding PUCCH / PUSCH. Alternatively, the terminal may operate so as not to receive the corresponding PDSCH and also not to transmit the corresponding PUCCH / PUSCH.

[0195] In this regard, the method of not transmitting HARQ-ACK information in the present disclosure may be based on a method of not generating HARQ-ACK for TB received in the MAC layer. Alternatively, the method of not transmitting HARQ-ACK information in the present disclosure may be based on a method of not transmitting HARQ-ACK information in the PHY layer even if HARQ-ACK information is generated in the MAC layer. Alternatively, the method of not transmitting HARQ-ACK information in the present disclosure may be based on a method of invalidating the HARQ-ACK information or the PUCCH or PUSCH (or the UCI of the PUSCH) transmitting the HARQ-ACK information in the PHY layer even if the HARQ-ACK is generated in the MAC layer.

[0196] Example 2

[0197] This embodiment relates to a method for configuring and transmitting / receiving a Type-1 HARQ-ACK codebook based on a time interval related to NES.

[0198] A Type-1 HARQ-ACK codebook may correspond to a HARQ-ACK codebook that is semi-statically configured via higher layer signaling (e.g., RRC message, etc.). That is, a Type-1 HARQ-ACK codebook may be referred to as a semi-static based HARQ-ACK codebook.

[0199] With respect to a Type-1 HARQ-ACK codebook, a UE may receive / be instructed via DCI to receive offset information (e.g., a PDSCH-to-HARQ_feedback timing indicator) between a DL slot for receiving a PDSCH and a UL slot for reporting HARQ-ACK information / feedback therefor. The offset information may be referred to as "K1". That is, with respect to a Type-1 HARQ-ACK codebook, a UE may configure HARQ-ACK information for one or more PDSCHs located prior to one or more K1 values ​​based on a specific UL slot into a Type-1 HARQ-ACK codebook, and transmit the Type-1 HARQ-ACK codebook to a base station in the corresponding UL slot.

[0200] Figure 9 illustrates a Type-1 HARQ-ACK codebook configuration applicable to the present disclosure.

[0201] Referring to FIG. 9, when a Type-1 HARQ-ACK codebook configuration method is set, a terminal configured with one or more serving cells can configure a HARQ-ACK codebook to be transmitted in a PUCCH transmission resource slot for each serving cell.

[0202] At this time, the HARQ-ACK codebook can be configured to include each HARQ-ACK bit for all PDSCH reception occasions located K1 slots prior to the corresponding PUCCH transmission resource slot.

[0203] With respect to the Type-1 HARQ-ACK codebook configuration, for the sake of clarity of explanation, a PDSCH reception opportunity (i.e., a slot located prior to the slot of the PUCCH resource configured to transmit HARQ-ACK information by a slot offset, i.e., K1 slots) may be referred to as a “K1 slot.”

[0204] For example, in the first serving cell (e.g., CC#1), it is assumed that four PDSCHs are transmitted / scheduled to the UE based on four K1 values ​​based on the HARQ-ACK PUCCH timing. That is, four PDSCH reception opportunities can be set / indicated based on four different K1 values. At this time, the UE receives the PDCCH scheduling each PDSCH in each PDCCH monitoring occasion, and can obtain information (e.g., “K0”) about the slot offset between the PDCCH and the PDSCH through the DCI received through the corresponding PDCCH. In the case of the first serving cell illustrated in FIG. 9, the K0 value is indicated as 1 (i.e., 1 slot), and based on this, the UE can receive four PDSCHs transmitted from the base station. In this case, the terminal can configure four HARQ-ACK bits for four PDSCHs into a HARQ-ACK codebook and transmit it to the base station in the HARQ-ACK PUCCH timing slot.

[0205] In a second serving cell (e.g., CC#2), it is assumed that four PDSCHs are transmitted / scheduled to the UE based on four K1 values ​​based on the HARQ-ACK PUCCH timing. That is, four PDSCH reception opportunities can be set / indicated based on four different K1 values. At this time, the UE receives the PDCCH scheduling each PDSCH in each PDCCH monitoring opportunity, and can obtain information (e.g., “K0”) about the slot offset between the PDCCH and the PDSCH through the DCI received through the corresponding PDCCH. In the case of the second serving cell illustrated in FIG. 9, the K0 value is indicated as 2 (i.e., two slots), and based on this, the UE can receive only two PDSCHs (e.g., the first PDSCH and the last PDSCH in the CC#2 case of FIG. 9) among the four PDSCHs transmitted from the base station. At this time, the terminal can indicate the HARQ-ACK bit as NACK for two PDSCHs that cannot be received.

[0206] With respect to the first and second periods for the aforementioned NES operation, some or all of the PDSCH reception opportunities (i.e., K1 slots) set / indicated by the base station through certain signaling (e.g., RRC messages, MAC CEs, DCIs, etc.) may be included in the first period. Alternatively, all or some of the corresponding PDSCH reception opportunities may not be included in the second period. In the present disclosure, such cases are referred to / determined as the PDSCH reception opportunities corresponding to NES off.

[0207] In describing the present disclosure, a cell that satisfies at least one of the criteria described below may be determined to be an NES off-cell.

[0208] - A specific cell that is included in or corresponds to a symbol / slot in which the allocated PUCCH resource or the corresponding HARQ-ACK codebook transmission time / interval is in a DRX / DTX inactive or cell deactivation state.

[0209] - A specific cell included in or corresponding to a symbol / slot that is in DRX / DTX inactive or cell inactive state at the time of receiving DCI (e.g., DL DCI / UL DCI including DAI, DCI requesting Type 3 codebook, etc.) or at a time X ms prior to the time of receiving said DCI.

[0210] - A specific cell that is included in or corresponds to a symbol / slot in which the allocated PUCCH resource or HARQ-ACK codebook transmission time interval is X ms prior to the time of receiving DCI (e.g., DL DCI / UL DCI including DAI, DCI requesting Type 3 codebook, etc.) or the time of receiving the DCI is in a DRX / DTX inactive or cell inactive state.

[0211] - When N TBs are scheduled to one or more cells with one DCI as multi-PDSCH or multi-cell PDSCH transmission is applied, a cell that satisfies one or more of the following conditions related to PDSCH(s) containing K TBs (K is 1 or a value greater than or equal to N) out of N TBs

[0212] -- Condition where all or part of the PDSCH resources for K TBs are included in symbols / slots in DRX / DTX disabled or cell disabled state.

[0213] In this regard, the terminal may configure a Type-1 HARQ-ACK codebook based on one or more of the options described below, and transmit / report the same to the base station.

[0214] First, we explain the methods applicable to cases where only one serving cell is configured for a terminal.

[0215] Option 2-1-1

[0216] If a specific PDSCH reception opportunity(s) located K1 slots prior to the slot of the PUCCH resource for transmitting HARQ-ACK information is NES off, the terminal may not transmit the corresponding PUCCH.

[0217] Option 2-1-2

[0218] If a specific PDSCH reception opportunity(s) located K1 slots prior to the slot of the PUCCH resource for transmitting HARQ-ACK information is NES off, the terminal may indicate the HARQ-ACK bit(s) for the specific PDSCH reception opportunity(s) as NACK.

[0219] Option 2-1-3

[0220] If a specific PDSCH reception opportunity(s) located K1 slots prior to a slot of PUCCH resources for transmitting HARQ-ACK information is NES off, the terminal can configure a HARQ-ACK codebook using only HARQ-ACK bit(s) corresponding to the remaining PDSCH reception opportunities excluding the specific PDSCH reception opportunity(s).

[0221] At this time, if there are no PDSCH reception opportunities other than the specific PDSCH reception opportunity(s), the terminal may not configure a HARQ-ACK codebook and may not transmit.

[0222] Next, when multiple serving cells, such as CA, are configured for a terminal, or when multiple serving cells are configured and activated, methods applicable to all serving cells configured via upper layer signaling (e.g., RRC message, etc.) (regardless of activation) or all serving cells activated (via MAC CE, etc.) are described.

[0223] Option 2-2-1

[0224] If all PDSCH reception opportunities of all cells located K1 slots prior to the slot of the PUCCH resource for transmitting HARQ-ACK information are NES off, the terminal may not transmit the corresponding PUCCH.

[0225] Option 2-2-2

[0226] If all PDSCH reception opportunity(s) of a specific cell located K1 slots prior to the slot of the PUCCH resource for transmitting HARQ-ACK information are NES off, the terminal can configure a HARQ-ACK codebook only with HARQ-ACK bit(s) corresponding to the PDSCH reception opportunity(s) for the remaining cell(s) excluding the cell(s).

[0227] At this time, if there are no cells other than the corresponding cell(s), the terminal may not configure a HARQ-ACK codebook and may not transmit.

[0228] Option 2-2-3

[0229] If specific PDSCH reception opportunity(s) of all cells located K1 slots prior to the slot of PUCCH resources for transmitting HARQ-ACK information are NES off, the terminal can configure a HARQ-ACK codebook using only HARQ-ACK bit(s) corresponding to the remaining PDSCH reception opportunity(s) excluding the specific PDSCH reception opportunity(s) for all cells.

[0230] At this time, if there are no PDSCH reception opportunities other than the specific PDSCH reception opportunity(s) in a certain cell, the terminal may configure a HARQ-ACK codebook only with the HARQ-ACK bit(s) corresponding to the PDSCH reception opportunity(s) for the remaining cells excluding the cell(s). Additionally, if there are no remaining cells other than the cell(s), the terminal may not configure a HARQ-ACK codebook and may not transmit.

[0231] Option 2-2-4

[0232] If the specific PDSCH reception opportunity(s) of all cells located K1 slots prior to the slot of the PUCCH resource for transmitting HARQ-ACK information are NES off, the terminal may indicate the HARQ-ACK bit(s) for the specific PDSCH reception opportunity(s) as NACK.

[0233] Option 2-2-5

[0234] If a specific PDSCH reception opportunity(s) located K1 slots prior to a slot of PUCCH resources for transmitting HARQ-ACK information is NES off, the terminal can configure a HARQ-ACK codebook using only HARQ-ACK bit(s) corresponding to the remaining PDSCH reception opportunities(s) excluding the specific PDSCH reception opportunity(s) of the cell.

[0235] At this time, if there are no PDSCH reception opportunities other than the specific PDSCH reception opportunity(s) in the corresponding cell, the terminal may configure a HARQ-ACK codebook only with HARQ-ACK bit(s) corresponding to the PDSCH reception opportunity(s) for the remaining cells excluding the corresponding cell. Additionally, if there are no remaining cells other than the corresponding cell(s), the terminal may not configure a HARQ-ACK codebook and may not transmit.

[0236] FIG. 10 illustrates a NES-based PDSCH and related HARQ-ACK codebook configuration and transmission procedure according to an embodiment of the present disclosure.

[0237] Referring to FIG. 10, a network node can transmit settings related to NES mode, settings related to SPS PDSCH, etc. to a terminal via an RRC message (S1010).

[0238] The network node may transmit a PDCCH / PDSCH to the terminal in the first slot (e.g., slot#1) based on the settings and / or predefined information (S1020).

[0239] Additionally, based on the settings and / or predefined information, etc., a deactivation operation based on the NES mode in the network node and terminal (e.g., a deactivation operation of cell DTX / DRX) may be applied (S1030).

[0240] Based on the deactivation operation, the network node can transmit PDCCH / PDSCH to the terminal in the second slot (e.g., slot#2) (S1040).

[0241] In this regard, based on the operation(s) described above in the present disclosure, the terminal can confirm / judge PDSCH transmission opportunity(s) for configuring a HARQ-ACK codebook, and configure a HARQ-ACK codebook including HARQ-ACK bit(s) for the corresponding PDSCH transmission opportunity(s) (S1050).

[0242] If a HARQ-ACK codebook is configured, the terminal may transmit the corresponding HARQ-ACK codebook to the network node via PUCCH / PUSCH (S1060). Alternatively, if the terminal does not configure a HARQ-ACK codebook, the terminal may drop the transmission of the corresponding HARQ-ACK information.

[0243] With regard to the configuration and transmission of the HARQ-ACK codebook described in FIG. 10, the specific method(s) described / proposed through the embodiments of the present disclosure may be applied.

[0244] Example 3

[0245] This embodiment relates to a method for configuring and transmitting / receiving a HARQ-ACK codebook for an SPS PDSCH based on a time interval related to an NES.

[0246] That is, in this embodiment, a method of configuring and transmitting / receiving a HARQ-ACK codebook for an SPS PDSCH is explained through specific examples in relation to the embodiments described above in the present disclosure.

[0247] For example, based on the embodiment(s) of the present disclosure, when one or more SPS configurations are configured and activated, a terminal that receives SPS PDSCH(s) through one or more cells for the activated SPS configuration(s) may transmit HARQ-ACK information for the corresponding SPS PDSCH(s) through PUCCH resource(s) based on the configuration. For example, the corresponding PUCCH resource(s) may be determined based on an SPS-PUCCH-AN-List configuration or an n1PUCCH-AN configuration configured for the terminal.

[0248] In this regard, the terminal may configure a HARQ-ACK codebook based on one or more of the following options, or may operate to determine whether to transmit the corresponding PUCCH (or UCI).

[0249] Option 3-1-1

[0250] For a specific SPS configuration of a specific cell, HARQ-ACK bit(s) for a specific SPS PDSCH slot that falls entirely or partially within the first interval (i.e., overlaps with the first interval) may not be included in the HARQ-ACK codebook. Accordingly, the UE may configure a HARQ-ACK codebook for the SPS, excluding the corresponding HARQ-ACK bit(s), and including the HARQ-ACK bit(s) in the following examples.

[0251] For example, for the remaining cell(s) excluding the specific cell, a HARQ-ACK codebook may be configured to include HARQ-ACK bit(s) for SPS PDSCH slot(s) of all activated SPS configuration(s). Additionally, for the specific cell, the HARQ-ACK bit(s) for SPS slot(s) of all remaining activated SPS configuration(s) excluding the specific SPS configuration may be included in the HARQ-ACK codebook. Additionally, for the specific SPS configuration of the specific cell, a HARQ-ACK codebook may be configured to include only HARQ-ACK bit(s) for SPS PDSCH slot(s) excluding the specific SPS PDSCH slot(s) that belong to the first period in whole or in part.

[0252] The terminal may transmit the HARQ-ACK codebook configured as described above via PUCCH or PUSCH. In this case, if there are no HARQ-ACK bit(s) (i.e., HARQ-ACK bit(s) to be included in the HARQ-ACK codebook) as in the examples described above, the terminal may not report HARQ-ACK information for SPS.

[0253] Option 3-1-2

[0254] For a specific SPS configuration of a specific cell, the HARQ-ACK bit(s) for a specific SPS PDSCH slot that falls entirely or partially within the first interval (i.e., overlaps with the first interval) may be indicated as a NACK. That is, the corresponding HARQ-ACK bit(s) may be included as NACK information in the HARQ-ACK codebook.

[0255] Option 3-1-3

[0256] For a specific SPS configuration of a specific cell, if all SPS PDSCH slots belong entirely or partially to the first interval (i.e., if all SPS PDSCH slots overlap with the first interval), the corresponding HARQ-ACK bit(s) may not be included in the HARQ-ACK codebook. Therefore, the terminal may configure the HARQ-ACK codebook for the SPS by excluding the corresponding HARQ-ACK bit(s) and including the HARQ-ACK bit(s) in the following example.

[0257] For example, for the remaining cell(s) excluding the specific cell, a HARQ-ACK codebook may be configured including HARQ-ACK bit(s) for SPS PDSCH slot(s) of all activated SPS configuration(s). Additionally, for the specific cell, HARQ-ACK bit(s) for SPS slot(s) of all activated SPS configuration(s) excluding the specific SPS configuration may be included in the HARQ-ACK codebook.

[0258] The terminal may transmit the HARQ-ACK codebook configured as described above via PUCCH or PUSCH. In this case, if there are no HARQ-ACK bit(s) (i.e., HARQ-ACK bit(s) to be included in the HARQ-ACK codebook) as in the examples described above, the terminal may not report HARQ-ACK information for SPS.

[0259] Option 3-1-4

[0260] For a specific SPS configuration of a specific cell, if all SPS PDSCH slots belong entirely or partially to the first interval (i.e., if all SPS PDSCH slots overlap with the first interval), the corresponding HARQ-ACK bit(s) may not be included in the HARQ-ACK codebook. Therefore, the terminal may configure the HARQ-ACK codebook for the SPS by excluding the corresponding HARQ-ACK bit(s) and including the HARQ-ACK bit(s) in the following example.

[0261] For example, for the remaining cell(s) excluding the specific cell in question, a HARQ-ACK codebook can be configured including HARQ-ACK bit(s) for SPS PDSCH slot(s) of all activated SPS configuration(s).

[0262] The terminal may transmit the HARQ-ACK codebook configured as described above via PUCCH or PUSCH. In this case, if there are no HARQ-ACK bit(s) (i.e., HARQ-ACK bit(s) to be included in the HARQ-ACK codebook) as in the examples described above, the terminal may not report HARQ-ACK information for SPS.

[0263] Option 3-1-5

[0264] For a specific SPS configuration of a specific cell, if all SPS PDSCH slots belong entirely or partially to the first interval (i.e., overlap with the first interval), the corresponding HARQ-ACK bit(s) may be indicated as NACK. That is, the corresponding HARQ-ACK bit(s) may be included as NACK information in the HARQ-ACK codebook.

[0265] Option 3-1-6

[0266] For all SPS configurations of a particular cell, if all SPS PDSCH slots belong entirely or partially to the first interval (i.e., overlap with the first interval), the corresponding HARQ-ACK bit(s) may be indicated as NACK. That is, the corresponding HARQ-ACK bit(s) may be included as NACK information in the HARQ-ACK codebook.

[0267] Additionally, with respect to the operations described above in the present disclosure, a terminal that receives an SPS PDSCH through one serving cell for the activated SPS configuration(s) may operate to configure a HARQ-ACK codebook or determine whether to transmit the corresponding PUCCH (or UCI) based on one or more of the following methods.

[0268] Option 3-2-1

[0269] If all SPS PDSCH slots for all SPS configurations of the serving cell belong entirely or partially to the first interval (i.e., overlap with the first interval), the corresponding HARQ-ACK bit(s) may not be included in the HARQ-ACK codebook. Accordingly, the UE may configure the HARQ-ACK codebook by including HARQ-ACK bit(s) for the remaining PDCCH / PDSCH transmissions (e.g., SPS activation / release) excluding HARQ-ACK information for the SPS PDSCH.

[0270] Option 3-2-2

[0271] For all SPS configurations of a serving cell, if all SPS PDSCH slots belong entirely or partially to the first interval (i.e., overlap with the first interval), the corresponding HARQ-ACK bit(s) may be indicated as NACK. That is, the corresponding HARQ-ACK bit(s) may be included as NACK information in the HARQ-ACK codebook.

[0272] Option 3-2-3

[0273] For all SPS configurations of a serving cell, if all SPS PDSCH slots belong entirely or partially to the first interval (i.e., overlap with the first interval), the terminal may not transmit the corresponding PUCCH (or PUSCH).

[0274] Additionally, with respect to the operations described above in the present disclosure, a terminal that receives an SPS PDSCH through multiple serving cells (set to carrier aggregation (CA)) for an activated SPS configuration(s) may operate to configure a HARQ-ACK codebook or determine whether to transmit the corresponding PUCCH (or UCI) based on one or more of the following methods.

[0275] Option 3-3-1

[0276] For all SPS configurations of all serving cells, if all SPS PDSCH slots belong entirely or partially to the first period (i.e., overlap with the first period), the corresponding HARQ-ACK bit(s) may not be included in the HARQ-ACK codebook. Accordingly, the UE may configure the HARQ-ACK codebook by including HARQ-ACK bit(s) for the remaining PDCCH / PDSCH transmissions (e.g., SPS activation / release) excluding HARQ-ACK information for the SPS PDSCH.

[0277] Option 3-3-2

[0278] For all SPS configurations of all serving cells, if all SPS PDSCH slots belong entirely or partially to the first interval (i.e., overlap with the first interval), the corresponding HARQ-ACK bit(s) may be indicated as NACK. That is, the corresponding HARQ-ACK bit(s) may be included as NACK information in the HARQ-ACK codebook.

[0279] Option 3-3-3

[0280] For all SPS configurations of all serving cells, if all SPS PDSCH slots belong entirely or partially to the first interval (i.e., overlap with the first interval), the terminal may not transmit the corresponding PUCCH (or PUSCH).

[0281] Option 3-3-4

[0282] If a specific serving cell belongs to the first period, the HARQ-ACK bit(s) for the SPS configuration(s) in that cell may not be included in the HARQ-ACK codebook. Therefore, for the remaining cell(s) excluding the specific cell, the HARQ-ACK bit(s) for the SPS PDSCH slot(s) of all activated SPS configuration(s) may be included in the HARQ-ACK codebook.

[0283] Option 3-3-5

[0284] If a specific serving cell belongs to the first period, the HARQ-ACK bit(s) for the SPS configuration(s) in that cell may be indicated as NACK. That is, the corresponding HARQ-ACK bit(s) may be included as NACK information in the HARQ-ACK codebook.

[0285] Option 3-3-6

[0286] If the SPS transmission for a specific SPS configuration of a specific serving cell falls (entirely or partially) within the first interval (i.e., all SPS PDSCH slots overlap with the first interval), the HARQ-ACK bit(s) for the corresponding SPS configuration(s) of the corresponding cell may not be included in the HARQ-ACK codebook. Accordingly, the UE may configure the HARQ-ACK codebook for the SPS, excluding the corresponding HARQ-ACK bit(s), and including the HARQ-ACK bit(s) in the following examples.

[0287] For example, for the remaining cell(s) excluding the specific cell, a HARQ-ACK codebook may be configured including HARQ-ACK bit(s) for SPS PDSCH slot(s) of all activated SPS configuration(s). Additionally, for the specific cell, HARQ-ACK bit(s) for SPS slot(s) of all activated SPS configuration(s) excluding the specific SPS configuration may be included in the HARQ-ACK codebook.

[0288] The terminal may transmit the HARQ-ACK codebook configured as described above via PUCCH or PUSCH. In this case, if there are no HARQ-ACK bit(s) (i.e., HARQ-ACK bit(s) to be included in the HARQ-ACK codebook) as in the examples described above, the terminal may not report HARQ-ACK information for SPS.

[0289] Option 3-3-7

[0290] If the SPS transmission for a specific SPS configuration of a specific serving cell falls (entirely or partially) within the first interval (i.e., all SPS PDSCH slots overlap with the first interval), the HARQ-ACK bit(s) for that SPS configuration(s) of that cell may be indicated as NACK. That is, the HARQ-ACK bit(s) may be included as NACK information in the HARQ-ACK codebook.

[0291] Additionally, when A / N PUCCH for SPS is set, the base station may instruct the terminal to configure a codebook as described below through an RRC message or / and DCI (e.g., SPS activation DCI, etc.).

[0292] Option 3-4-1

[0293] The base station can configure the terminal via an RRC message whether to configure the HARQ-ACK codebook for SPS only for the remaining serving cells, excluding the NES off-cells.

[0294] Option 3-4-2

[0295] The base station can instruct the terminal via DCI whether to configure the HARQ-ACK codebook for SPS only for the remaining serving cells, excluding the NES off-cells.

[0296] Option 3-4-3

[0297] The base station can configure a codebook to indicate NACK as all HARQ-ACK information for SPS for NES-off cells and ACK or NACK for all HARQ-ACKs of the remaining serving cell(s) through an RRC message to the terminal.

[0298] Option 3-4-4

[0299] The base station can instruct the terminal via DCI whether to configure a codebook that indicates NACK as all HARQ-ACK information for SPS for cells with NES off and ACK or NACK for all HARQ-ACKs of the remaining serving cell(s).

[0300] Example 4

[0301] This embodiment relates to a method for configuring a HARQ-ACK codebook when cross-carrier scheduling is applied. Cross-carrier scheduling is a general term for a method in which channels / signals are scheduled in a scheduled cell through control information received in the scheduling cell.

[0302] A terminal receiving a PDSCH transmission set to a type-1 HARQ-ACK codebook can determine whether the scheduling cell or / and the scheduled cell is a NES-off cell, and can configure the HARQ-ACK codebook according to the options described below.

[0303] Option 4-1-1

[0304] If some or all of the K0 slot(s) of a scheduling cell that can schedule PDSCH(s) for a specific K1 slot of the scheduled cell are NES off, the HARQ-ACK bit for the corresponding PDSCH(s) may be indicated / set to NACK or excluded from the Type-1 HARQ-ACK codebook.

[0305] That is, if all or part of the PDCCH monitoring opportunity(s) of a scheduling cell that can schedule / indicate specific PDSCH reception opportunity(s) of the scheduled cell fall within an interval associated with NES off, the HARQ-ACK bit for the corresponding PDSCH opportunity(s) may be indicated / set as NACK or excluded from the Type-1 HARQ-ACK codebook.

[0306] Option 4-1-2

[0307] If some or all of the K0 slot(s) of a scheduling cell that can schedule PDSCH(s) for a specific K1 slot of the scheduled cell are NES off, the HARQ-ACK bit for the corresponding PDSCH(s) may be indicated / set to NACK or excluded from the Type-1 HARQ-ACK codebook.

[0308] That is, if all or part of the PDSCH reception opportunity(s) of a scheduling cell that can schedule / indicate specific PDSCH reception opportunity(s) of the scheduled cell fall within an interval associated with NES off, the HARQ-ACK bit for the corresponding PDSCH opportunity(s) may be indicated / set as NACK or excluded from the Type-1 HARQ-ACK codebook.

[0309] Option 4-1-3

[0310] If some or all of a particular K1 slot of a scheduled cell is NES off of the scheduling cell, the HARQ-ACK bit for that PDSCH may be indicated / set to NACK or excluded from the Type-1 HARQ-ACK codebook.

[0311] That is, if all or part of a specific PDSCH reception opportunity(s) of a scheduled cell fall within or correspond to an interval associated with an NES off within the scheduled cell, the HARQ-ACK bit for that PDSCH reception opportunity may be indicated / set to NACK or excluded from the Type-1 HARQ-ACK codebook.

[0312] Option 4-1-4

[0313] If some or all of a particular K1 slot of a scheduled cell is NES off for the scheduled cell, the HARQ-ACK bit for that PDSCH may be indicated / set to NACK or excluded from the Type-1 HARQ-ACK codebook.

[0314] That is, if all or part of a specific PDSCH reception opportunity(s) of a scheduled cell fall within or correspond to an interval associated with an NES off within the scheduled cell, the HARQ-ACK bit for that PDSCH reception opportunity may be indicated / set to NACK or excluded from the Type-1 HARQ-ACK codebook.

[0315] Option 4-1-5

[0316] If a HARQ-ACK PUCCH slot overlaps partly or entirely with the NES off-period of a specific scheduling cell, the HARQ-ACK bits for the PDSCH in all scheduled cells configured through that scheduling cell may be indicated as NACK or excluded from the type-1 HARQ-ACK codebook.

[0317] Option 4-1-6

[0318] If a HARQ-ACK PUCCH slot overlaps partly or entirely with the NES off-period of a specific scheduled cell, the HARQ-ACK bit for the PDSCH in that scheduled cell may be indicated as NACK or excluded from the type-1 HARQ-ACK codebook.

[0319] Additionally, when an A / N PUCCH is configured for a Type-1 HARQ-ACK codebook, the base station may configure / instruct the terminal to configure the codebook via an RRC message or / and DCI according to the options described below. At this time, the DCI may be a DCI indicating NES on / off or a DCI allocating a PUCCH (e.g., when a Type-1 HARQ-ACK codebook or a Type-2 HARQ-ACK codebook is configured).

[0320] Option 4-2-1

[0321] The base station can configure the terminal via an RRC message whether to configure the HARQ-ACK codebook only for the remaining serving cells, excluding the NES off-cells.

[0322] Option 4-2-2

[0323] The base station can instruct the terminal via DCI whether to configure the HARQ-ACK codebook only for the remaining serving cells, excluding the NES off-cells.

[0324] Option 4-2-3

[0325] The base station can configure a codebook to indicate to the terminal via an RRC message whether all HARQ-ACKs for cells with NES off are NACKs and all HARQ-ACKs for the remaining serving cells are ACKs or NACKs.

[0326] Option 4-2-4

[0327] The base station can instruct the terminal via DCI whether to configure a codebook that indicates NACK for all HARQ-ACKs for cells with NES off and ACK or NACK for all HARQ-ACKs for the remaining serving cells.

[0328] General devices to which the present disclosure may be applied

[0329] FIG. 11 illustrates a block diagram of a wireless communication device according to one embodiment of the present disclosure.

[0330] Referring to FIG. 11, the first device (100) and the second device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR).

[0331] A first device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure.

[0332] For example, the processor (102) may process information in the memory (104) to generate first information / signal and then transmit a wireless signal including the first information / signal through the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal through the transceiver (106) and then store information obtained from signal processing of the second information / signal in the memory (104).

[0333] The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0334] The second 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) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). In addition, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present disclosure, a device may also mean a communication modem / circuit / chip.

[0335] Hereinafter, the hardware elements of the device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement 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 Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in the present disclosure. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed in the present disclosure, and provide the signals 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 obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed in the present disclosure.

[0336] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software configured to perform 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, proposals, methods and / or operation flowcharts disclosed in this disclosure may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0337] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0338] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of the present disclosure, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled 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, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in the present disclosure, via one or more antennas (108, 208). In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0339] The embodiments described above are combinations of components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form embodiments of the present disclosure by combining some components and / or features. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form embodiments or incorporated as new claims through post-application amendments.

[0340] It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present disclosure are intended to be included within the scope of the present disclosure.

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

[0342] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. At this time, 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 can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0343] The method proposed in this disclosure is explained with a focus on examples applied to 3GPP LTE / LTE-A and 5G systems, but can be applied to various wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: A step of receiving first information related to a first discontinuous transmission (DTX) inactive period of a first cell from a base station; A step of configuring a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the exclusion of a first PDSCH reception opportunity among at least one physical downlink shared channel (PDSCH) reception occasion of a second cell; and A step of transmitting uplink control information (UCI) including the HARQ-ACK codebook to the base station, A method wherein the first PDSCH reception opportunity of the second cell is based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX deactivation period.

2. In paragraph 1, A method wherein the HARQ-ACK codebook includes HARQ-ACK information for each PDSCH reception in the remaining PDSCH reception opportunities excluding the first PDSCH reception opportunity among the at least one PDSCH reception opportunities, and does not include ACK information related to the first PDSCH reception opportunity.

3. In paragraph 1, The above UCI is transmitted to the base station in a specific uplink slot, A method in which at least one PDSCH reception opportunity is set based on at least one slot offset relative to the specific uplink slot.

4. In paragraph 1, A method in which NACK (negative acknowledgment) information related to the first PDSCH reception opportunity is included in the HARQ-ACK codebook.

5. In paragraph 3, A method wherein at least one slot offset is received from the base station via radio resource control (RRC) or downlink control information (DCI).

6. In paragraph 2, A method wherein each PDSCH reception in the remaining PDSCH reception opportunities is based on a second PDCCH monitoring opportunity that is not included in the first DTX deactivation interval.

7. In paragraph 1, A method wherein the configuration of the above HARQ-ACK codebook is set semi-statically by the base station.

8. In paragraph 1, The method wherein the first DTX deactivation period is associated with a network energy saving (NES) mode for the first cell.

9. In paragraph 1, A method in which the above HARQ-ACK codebook is transmitted through a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

10. In paragraph 1, A method wherein the above HARQ-ACK codebook is configured regardless of the second DTX deactivation period set in the second cell.

11. In a terminal performing communication in a wireless communication system, the terminal: one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Receiving first information related to a first DTX (discontinuous transmission) inactive period of a first cell from a base station through the one or more transceivers; Constructing a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the exclusion of a first PDSCH reception opportunity among at least one physical downlink shared channel (PDSCH) reception occasion of a second cell; and Uplink control information (UCI) including the HARQ-ACK codebook is set to be transmitted to the base station through the one or more transceivers, A terminal wherein the first PDSCH reception opportunity of the second cell is based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX deactivation period.

12. A method performed by a base station in a wireless communication system, the method comprising: A step of transmitting first information related to a first DTX (discontinuous transmission) inactive section of a first cell to a terminal; A step of receiving uplink control information (UCI) including a HARQ-ACK codebook configured by the terminal from the terminal, The HARQ-ACK codebook is configured based on the exclusion of a first PDSCH reception opportunity among at least one physical downlink shared channel (PDSCH) reception occasion of the second cell, A method wherein the first PDSCH reception opportunity of the second cell is based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX deactivation period.

13. In a base station performing communication in a wireless communication system, the base station: one or more transceivers; and comprising one or more processors connected to said one or more transceivers, One or more of the above processors: Transmitting first information related to a first DTX (discontinuous transmission) inactive period of a first cell to a terminal via the one or more transceivers; It is configured to receive uplink control information (UCI) including a HARQ-ACK codebook configured by the terminal from the terminal through the one or more transceivers, The HARQ-ACK codebook is configured based on the exclusion of a first PDSCH reception opportunity among at least one physical downlink shared channel (PDSCH) reception occasion of the second cell, A base station, wherein the first PDSCH reception opportunity of the second cell is based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX deactivation period.

14. In a processing device configured to control a terminal to perform communication in a wireless communication system, the processing device: one or more processors; and One or more computer memories operatively connected to said one or more processors and storing instructions that perform operations based on execution by said one or more processors, The above actions are: An operation of receiving first information related to a first discontinuous transmission (DTX) inactive period of a first cell from a base station; An operation of configuring a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the exclusion of a first PDSCH reception opportunity among at least one physical downlink shared channel (PDSCH) reception occasion of a second cell; and Including an operation of transmitting uplink control information (UCI) including the HARQ-ACK codebook to the base station, A processing device wherein the first PDSCH reception opportunity of the second cell is based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX deactivation period.

15. One or more non-transitory computer-readable media storing one or more instructions, The above one or more commands are executed by one or more processors, and the device performs communication in a wireless communication system: Receive first information related to a first discontinuous transmission (DTX) inactive period of a first cell from a base station; Constructing a hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook based on the exclusion of a first PDSCH reception opportunity among at least one physical downlink shared channel (PDSCH) reception occasion of a second cell; and It is controlled to transmit uplink control information (UCI) including the above HARQ-ACK codebook to the base station, A computer-readable medium wherein the first PDSCH reception opportunity of the second cell is based on a first physical downlink control channel (PDCCH) monitoring occasion of the first cell included in the first DTX deactivation period.

Images