Method and apparatus for handling overlap between network DRX duration and HARQ feedback occasion for network energy saving in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. In particular, the present disclosure provides a method and apparatus for handling an overlap between a DRX duration and a HARQ feedback occasion relative to an NES. The method includes: receiving configuration information for a network discontinuous reception (NW DRX) operation from a base station; receiving downlink data from the base station based on the NW DRX operation; a timing to identify hybrid automatic repeat request (HARQ) information of downlink data overlaps with a duration of the NW DRX operation; and transmitting HARQ information of downlink data to the base station at a timing overlapping with the duration of the NW DRX operation.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system (or mobile communication system). Specifically, the present disclosure relates to an apparatus, method, and system for processing the overlap between network discontinuous reception (DRX) duration and hybrid automatic repeat request (HARQ) feedback opportunity in a wireless communication system to achieve network energy saving (NES). Background Art

[0002] Fifth-generation (5G) mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. This technology can be implemented not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands, known as millimeter waves, including 28 GHz and 39 GHz. Furthermore, consideration is being given to implementing 6G mobile communication technology (referred to as the Beyond 5G system) in terahertz (THz) frequency bands (e.g., the 95 GHz to 3 THz band) in order to achieve transmission rates fifty times faster than 5G mobile communication technology and ultra-low latency that is one-tenth that of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), standardization is underway on beamforming and massive MIMO for alleviating radio wave path loss and increasing radio wave transmission distance in millimeter waves, values ​​supporting dynamic operation for efficient utilization of millimeter wave resources and time slot formats (e.g., operation with multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and wideband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low-density parity check) codes for large data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services to be supported by 5G mobile communication technology, discussions on the improvement and performance enhancement of initial 5G mobile communication technology are underway, and there is already physical layer standardization on technologies such as V2X (Vehicle to Everything) for assisting driving determination of autonomous vehicles based on information about the position and status of vehicles transmitted by vehicles and for enhancing user convenience, NR-U (New Unlicensed Radio) which aims at system operation that complies with various regulatory requirements in unlicensed frequency bands, NR UE power saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable, and positioning.

[0005] In addition, there is ongoing standardization in air interface architecture / protocols, including Industrial Internet of Things (IIoT) technologies for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (2-step RACH for NR) for simplifying the random access procedure. There is also ongoing standardization in system architecture / services regarding the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, the already exponentially growing number of connected devices will be connected to the communication network, necessitating the enhanced functionality and performance of 5G mobile communication systems and the integrated operation of connected devices. To this end, new research is being conducted related to extended reality (XR), aiming to effectively support AR (augmented reality), VR (virtual reality), MR (mixed reality), and other technologies through the use of artificial intelligence (AI) and machine learning (ML), AI service support, meta-space service support, and drone communications, with improved 5G performance and reduced complexity.

[0007] Furthermore, such development of 5G mobile communication systems will serve as the foundation for developing not only new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, but also multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, and high-dimensional spatial multiplexing technologies using OAM (orbital angular momentum) and RIS (reconfigurable smart surfaces), but also full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for achieving system optimization and internalizing end-to-end AI support functions by leveraging satellites and AI (artificial intelligence) from the design stage, and next-generation distributed computing technologies for implementing services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Problem Solution

[0009] Recently, in terms of network energy saving, there is a need to enhance the handling of overlap between DRX duration and HARQ opportunities.

[0010] Aspects of the present disclosure are directed to addressing at least the above-mentioned problems and / or disadvantages and providing at least the advantages described below. Therefore, one aspect of the present disclosure is to provide a communication method and system for aggregating a fifth-generation (5G) communication system, which is configured to support higher data rates than the fourth generation (4G).

[0011] According to one aspect of the present disclosure, a method performed by a terminal is provided. The method includes: receiving configuration information for network discontinuous reception (NW DRX) from a base station; receiving downlink data from the base station; identifying that a timing of hybrid automatic repeat request (HARQ) information for the downlink data overlaps with a duration of the NW DRX; and transmitting the HARQ information for the downlink data to the base station during the timing overlapping with the duration of the NW DRX.

[0012] According to another aspect of the present disclosure, a terminal is provided. The terminal includes: a transceiver; and a controller coupled to the transceiver and configured to: receive configuration information for network discontinuous reception (NW DRX) from a base station, receive downlink data from the base station, identify that a timing of hybrid automatic repeat request (HARQ) information for the downlink data overlaps with a duration of the NW DRX, and transmit the HARQ information for the downlink data to the base station during the timing overlapping with the duration of the NW DRX.

[0013] According to another aspect of the present disclosure, a method performed by a base station is provided. The method includes: transmitting configuration information for network discontinuous reception (NW DRX) to a terminal; transmitting downlink data to the terminal; and receiving hybrid automatic repeat request (HARQ) information for the downlink data from the terminal in a timing of HARQ information overlapping with the NW DRX duration by temporarily resuming reception during the NW DRX duration.

[0014] According to another aspect of the present disclosure, a base station is provided. The base station includes: a transceiver; and a controller coupled to the transceiver and configured to: transmit configuration information for network discontinuous reception (NW DRX) to a terminal, transmit downlink data to the terminal, and receive hybrid automatic repeat request (HARQ) information for the downlink data from the terminal in a timing of HARQ information that overlaps with the NW DRX duration by temporarily resuming reception during the NW DRX duration.

[0015] According to various embodiments of the present disclosure, network energy saving may be enhanced according to efficient handling of DRX duration and HARQ feedback opportunities.

[0016] Before proceeding with the following detailed description, it may be helpful to set forth definitions of certain words and phrases used in this patent document: the terms "include" and "comprising" and their derivatives mean, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated" and "associated with" and their derivatives may mean include, be included in, interconnected with, contain, be contained in, connect to or be connected with, be coupled to or be coupled with, be communicative with, cooperate with, interleave, juxtapose, be proximate to, be bound to or be bound with, have, have properties thereof, or the like; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device being implemented in hardware, firmware, or software, or some combination of at least two identical devices. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0017] Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed of computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random-access memory (RAM), hard drives, compact disks (CDs), digital video disks (DVDs), or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored as well as media in which data can be stored and later rewritten, such as rewritable optical disks or erasable memory devices.

[0018] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0020] Figure 1 An example of a DRX cycle according to an embodiment of the present disclosure is shown;

[0021] Figure 2 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown.

[0022] Figure 3 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown;

[0023] Figure 4 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown;

[0024] Figure 5 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown;

[0025] Figure 6 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown;

[0026] Figure 7 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown;

[0027] Figure 8 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown;

[0028] Figure 9 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown;

[0029] Figure 10 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown;

[0030] Figure 11 shows a terminal according to an embodiment of the present disclosure; and

[0031] Figure 12 A base station according to an embodiment of the present disclosure is shown.

[0032] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0033] The following discussion Figures 1 to 12 The various embodiments used to describe the principles of the present disclosure in this patent document are only illustrative and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0034] The following description, with reference to the accompanying drawings, is provided to facilitate a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these details should be considered merely illustrative. Therefore, those skilled in the art will recognize that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. Furthermore, descriptions of well-known functions and structures may be omitted for clarity and conciseness.

[0035] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be understood by those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0036] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0037] The term "substantially" means that the recited features, parameters or values ​​need not be achieved precisely, but deviations or changes, including, for example, tolerances, measurement errors, measurement precision limitations and other factors known to those skilled in the art, may occur in amounts that do not negate the effect that the feature is intended to provide.

[0038] As is known to those skilled in the art, the blocks of a flowchart (or sequence diagram) and the combination of the flowcharts can be represented and executed by computer program instructions. These computer program instructions can be loaded onto a processor of a general-purpose computer, a special-purpose computer, or a programmable data processing device. When the loaded program instructions are executed by the processor, they create means for performing the functions described in the flowchart. Because computer program instructions can be stored in a computer-readable memory available in a special-purpose computer or a programmable data processing device, an article of manufacture can also be created that performs the functions described in the flowchart. Because the computer program instructions can be loaded onto a computer or a programmable data processing device, when executed as a process, they can perform the operations of the functions described in the flowchart.

[0039] The blocks of the flowchart may correspond to modules, segments, or codes containing one or more executable instructions that implement one or more logical functions, or may correspond to portions thereof. In some cases, the functions described by the blocks may be performed in an order different from the order listed. For example, two blocks listed in order may be executed simultaneously or in reverse order.

[0040] Throughout this specification, the terms "unit," "module," and the like may refer to software or hardware components capable of performing a function or operation, such as a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC). However, "unit," etc., is not limited to hardware or software. Units, etc., may be configured to reside in an addressable storage medium or drive one or more processors. Units, etc., may refer to software components, object-oriented software components, class components, task components, processes, functions, properties, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, or variables. The functions provided by components and units may be combinations of smaller components and units, and may be combined with other components and units to form larger components and units. Components and units may be configured to drive devices or one or more processors in a secure multimedia card.

[0041] Before the detailed description, terms or definitions necessary for understanding the present disclosure are described, but these terms should be interpreted in a non-restrictive manner.

[0042] A “base station (BS)” is an entity that communicates with a user equipment (UE) and may be referred to as a BS, base transceiver station (BTS), node B (NB), evolved NB (eNB), access point (AP), 5GNB (5GNB), or gNB.

[0043] A “UE” is an entity communicating with a BS and may be referred to as a UE, a device, a mobile station (MS), a mobile equipment (ME), or a terminal.

[0044] In fifth-generation wireless communication systems operating in high-frequency (millimeter wave) bands, UEs and gNBs use beamforming to communicate with each other. Beamforming technology is used to mitigate propagation path loss and increase the propagation range for communications in higher-frequency bands. Beamforming uses high-gain antennas to enhance transmission and reception performance. Beamforming can be categorized as transmit (TX) beamforming, performed on the transmitting end, and receive (RX) beamforming, performed on the receiving end. TX beamforming generally increases directivity by using multiple antennas to densely distribute the area of ​​propagation in a specific direction. In this context, a collection of multiple antennas is referred to as an antenna array, and each antenna in the array is referred to as an array element. Antenna arrays can be configured in various forms, such as linear arrays and planar arrays. The use of TX beamforming increases signal directivity, thereby increasing propagation range. Furthermore, since signals are rarely transmitted in directions other than their directivity, signal interference on other receiving ends is significantly reduced. A receiving end can perform beamforming on RX signals using an RX antenna array. RX beamforming increases the strength of RX signals transmitted in a specific direction by concentrating propagation in that direction. It also excludes signals transmitted in directions other than the specific direction from the RX signal, effectively blocking interfering signals. Using beamforming technology, a transmitter can generate multiple transmit beam patterns in different directions. Each of these transmit beam patterns is also referred to as a TX beam. Wireless communication systems operating at high frequencies use multiple narrow TX beams to transmit signals within a cell, as each narrow TX beam provides coverage for a portion of the cell. The narrower the TX beam, the higher the antenna gain, thus increasing the propagation distance of signals transmitted using beamforming. A receiver can also generate multiple RX beam patterns in different directions. Each of these receive patterns is also referred to as an RX beam.

[0045] The fifth-generation wireless communication system supports both standalone operation mode and dual connectivity (DC). In DC, multiple Rx / Tx UEs can be configured to utilize resources provided by two different nodes (or base stations) connected via a non-ideal backhaul. One node acts as a master node (MN), while the other acts as a secondary node (SN). The MN and SN are connected via a network interface, with at least the MN connected to the core network. NR also supports multi-RAT dual connectivity (MR-DC) operation, whereby a UE in a radio resource control (RRC) connection (RRC_CONNECTED) is configured to utilize radio resources provided by two different schedulers located in two different nodes connected via a non-ideal backhaul and providing either Evolved UMTS Terrestrial Radio Access (E-UTRA) (i.e., if the node is an ng-eNB) or NR access (i.e., if the node is a gNB). In NR for an RRC_CONNECTED UE not configured with carrier aggregation (CA) / DC, only one serving cell comprises the primary cell.

[0046] For UEs in RRC_CONNECTED mode configured with CA / DC, the term "serving cell" is used to refer to the set of cells that includes a special cell and all secondary cells. In NR, the term "master cell group" (MCG) refers to the group of serving cells associated with a primary node, consisting of a primary cell (pCell) and optionally one or more secondary cells (sCells). In NR, the term "secondary cell group" (SCG) refers to the group of serving cells associated with a secondary node, consisting of a primary SCG cell (PSCell) and optionally one or more sCells. In NR, a pCell refers to a serving cell in an MCG operating on the primary frequency, where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. In NR for UEs configured with CA, an sCell is a cell that provides additional radio resources above a dedicated cell. A PSCell refers to a serving cell in an SCG, where the UE performs random access when performing a reconfiguration with synchronization. For dual connectivity operation, the term "SpCell" (i.e., special cell) refers to a pCell in an MCG or a PSCell in an SCG; otherwise, the term "special cell" refers to a pCell.

[0047] PDCCH in the fifth-generation wireless communication system: In the fifth-generation wireless communication system, the physical downlink control channel (PDCCH) is used to schedule downlink (DL) transmissions on the physical downlink shared channel (PDSCH) and uplink (UL) transmissions on the physical uplink shared channel (PUSCH), where the downlink control information (DCI) on the PDCCH includes: downlink allocation including at least the modulation and coding format, resource allocation and hybrid automatic repeat request (HARQ) information related to the downlink shared channel (DL-SCH); uplink scheduling grant includes at least the modulation and coding format, resource allocation, and hybrid ARQ information related to the uplink shared channel (UL-SCH). In addition to scheduling, the PDCCH can be used for: activating and deactivating configured PUSCH transmissions using configured grants; activating and deactivating PDSCH semi-persistent transmissions; notifying one or more UEs of the slot format; notifying one or more UEs of physical resource blocks (PRBs) and orthogonal frequency division multiplexing (OFDM) symbols, where the UEs can assume no transmissions are intended for the UE; transmitting transmit power control (TPC) commands for the physical uplink control channel (PUCCH) and PUSCH; transmitting one or more TPC commands for SRS transmission by one or more UEs; switching the active bandwidth portion of a UE; and initiating a random access procedure. A UE monitors a set of PDCCH candidates during configured listening opportunities in one or more configured control resource sets (CORESETs), according to the corresponding search space configuration. A CORESET consists of a set of PRBs with a duration of one to three OFDM symbols. Multiple resource elements (REGs) and multiple control channel elements (CCEs) are defined within a CORESET, where each CCE comprises a set of REGs. Multiple control channels are formed by aggregating CCEs. Different coding rates for the control channel are achieved by aggregating different numbers of CCEs. Both interleaved and non-interleaved CCE-to-REG mapping are supported within the CORESET. Polarization coding is used for the PDCCH. Each resource element group carrying a PDCCH carries its own demodulation reference signal (DMRS). Quadrature Phase Shift Keying (QPSK) modulation is used for the PDCCH.

[0048] In fifth-generation wireless communication systems, the GNB signals a list of search space configurations for each configured BWP, where each search configuration is uniquely identified by an identifier. The gNB explicitly signals the identifiers of search space configurations to be used for specific purposes (e.g., paging reception, SI reception, random access response reception). NR search space configurations include monitoring-periodicity-PDCCH-slot, monitoring-offset-PDCCH-slot, monitoring-symbols-PDCCH-within-slot, and duration. The UE uses the parameters PDCCH monitoring period (Monitoring-periodicity-PDCCH-slot), PDCCH monitoring offset (Monitoring-offset-PDCCH-slot), and PDCCH monitoring pattern (Monitoring-symbols-PDCCH-within-slot) to determine the PDCCH monitoring timing within a timeslot. The PDCCH monitoring opportunity is in time slots "x" to x+duration, where the time slot with number "x" in the radio frame with number "y" satisfies the following equation:

[0049] (y * (number of slots in a radio frame) + x - Monitoring-offset-PDCCH-slot) mod(Monitoring-periodicity-PDCCH-slot) = 0;

[0050] The starting symbol of a PDCCH monitoring opportunity in each slot with a PDCCH monitoring opportunity is given by monitoring-symbols-PDCCH-within-slot. The length of the PDCCH monitoring opportunity (in symbols) is given in the coreset associated with the search space. The search space configuration includes the identifier of the coreset configuration associated with it. For each configured BWP, the GNB signals a list of coreset configurations, where each coreset configuration is uniquely identified by an identifier. Note that each radio frame has a duration of 10 ms. A radio frame is identified by a radio frame number or system frame number. Each radio frame consists of several slots, where the number of slots in a radio frame and the duration of the slots depend on the subcarrier spacing. In NR, the number of slots in a radio frame and the duration of the slots depend on the radio frame of each supported SCS. Each coreset configuration is associated with a list of transmission configuration indicator (TCI) states. Each TCI state is configured with a DL reference signal (RS) identifier (synchronization signal and physical broadcast channel block (SSB) or channel state information reference signal (CSI-RS)). The gNB signals a list of TCI states corresponding to the coreset configuration via RRC signaling. One of the TCI states in the TCI state list is activated and indicated to the UE by the gNB via a Medium Access Control (MAC) Control Element (CE). The TCI state indicates the DL TX beam used by the gNB to transmit PDCCHs in PDCCH monitoring opportunities in the search space (the DL TX beam is quasi-co-located (QCLed) with the SSB / CSI-RS of the TCI state). For the PDSCH, the TCI state of the scheduled PDCCH can be used for the scheduled PDSCH. Alternatively, the TCI state of the PDCCH with the lowest coreset ID in the slot is used for the PDSCH. An alternating combination of RRC, MAC CE, and DCI is used to indicate the TCI state for the PDSCH. The RRC configures the list of TCI states, the MAC CE indicates a subset of these TCI states, and the DCI indicates one of the TCI states from the list indicated in the MAC CE.

[0051] Bandwidth Adaptation in Fifth-Generation Wireless Communication Systems: Bandwidth Adaptation (BA) is supported in fifth-generation wireless communication systems. With BA, the UE's receive and transmit bandwidth need not be as large as the cell's bandwidth and can be adjusted: the width can be commanded to change (e.g., shrinking during periods of low activity to save power); the location can be moved in the frequency domain (e.g., to increase scheduling flexibility); and the subcarrier spacing can be ordered to change (e.g., to allow for different services). A subset of a cell's total cell bandwidth is called a bandwidth part (BWP). BA is implemented by configuring an RRC-connected UE with a BWP and informing the UE which configured BWP is currently active. When BA is configured, the UE can monitor the PDCCH only on one active BWP; that is, the UE does not monitor the PDCCH across the entire DL frequency range of the serving cell.

[0052] In the RRC Connected state, a UE is configured with one or more DL and UL BWPs for each configured serving cell (i.e., PCell or SCell). For an activated serving cell, there is always one active UL and DL BWP at any point in time. BWP switching within the serving cell is used for each activation of an inactive BWP and deactivation of an active BWP. BWP switching is controlled by the PDCCH indicating a downlink assignment or uplink grant, by the bwp-InactivityTimer, by RRC signaling, or by the MAC entity itself when initiating a random access procedure. When adding a SpCell or activating an SCell, the DL BWP and UL BWP, indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id, respectively, are active without receiving a PDCCH indicating a downlink assignment or uplink grant. The active BWP of a serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and BWP switching is common for both UL and DL. When the BWP inactivity timer expires, the UE switches the active DL BWP to the default DL BWP or the initial DL BWP (if no default DL BWP is configured).

[0053] Random Access in Fifth Generation Wireless Communication Systems: 5G wireless communication systems support random access (RA). RA is used to achieve uplink (UL) time synchronization. RA is used by non-synchronized UEs in the RRC CONNECTED state during initial access, handover, radio resource control (RRC) connection re-establishment procedures, scheduling request transmission, secondary cell group (SCG) addition / modification, beam failure recovery, and UL data or control information transmission. Several types of random access procedures are supported.

[0054] Paging in fifth generation wireless communication systems: In fifth generation (also known as New Radio (NR)) wireless communication systems, a UE may be in one of the following RRC states: RRC IDLE, RRC INACTIVE, and RRC CONNECTED. The RRC states may be further characterized as follows.

[0055] In the RRC_IDLE state, UE-specific discontinuous reception (DRX) can be configured by upper layers (i.e., non-access stratum (NAS)). The UE listens to short messages sent on the DCI with the Paging Radio Network Temporary Identifier (P-RNTI); uses the 5G-S-Temporary Mobile Subscription Identifier (5G-S-TMSI) to monitor the paging channel for core network (CN) paging; performs neighbor cell measurements and cell (re)selection; obtains system information and sends an SI request (if configured).

[0056] In the RRC_INACTIVE state, UE-specific DRX can be configured by upper layers or the RRC layer. In this state, the UE stores the UE inactive access stratum (AS) context. The RAN-based notification area is configured by the RRC layer. The UE listens to short messages sent on DCI with the P-RNTI; monitors the paging channel for CN paging using 5G-S-TMSI and RAN paging using the fullI-RNTI; performs neighbor cell measurements and cell (re)selection; performs Radio Access Network (RAN)-based notification area updates periodically and when moving outside the configured RAN-based notification area; obtains system information and sends an SI request (if configured).

[0057] In RRC_CONNECTED, the UE stores the AS context. Unicast data is sent to and received from the UE. At lower layers, the UE may be configured with UE-specific DRX. If configured, the UE monitors short messages sent on the DCI with the P-RNTI; monitors the control channel associated with the shared data channel to determine if data is scheduled for the shared data channel; provides channel quality and feedback information; performs neighbor cell measurements and measurement reports; and obtains system information.

[0058] The NR-based 5G or Next Generation Radio Access Network (NG-RAN) consists of NG-RAN nodes, of which the gNB provides NR user plane and control plane protocol termination to the UE. The gNB is also connected to the 5GC via the NG interface, more specifically, to the Access and Mobility Management Function (AMF) via the NG-C interface, and to the User Plane Function (UPF) via the NG-U interface. In fifth-generation (also known as NR or New Radio) wireless communication systems, UEs can use Distributed Receiving (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. In the RRC_IDLE / RRC_INACTIVE states, the UE wakes up for short periods at regular intervals (i.e., every DRX cycle) to receive paging, SI update notifications, and emergency notifications.

[0059] Paging messages are sent using the PDSCH. If a paging message is present in the PDSCH, the PDCCH is addressed to the P-RNTI. The P-RNTI is common to all UEs. The UE identity (i.e., S-TMSI for RRC_IDLE UEs or I-RNTI for RRC_INACTIVE UEs) is included in the paging message to indicate paging for a specific UE. The paging message may include multiple UE identities for paging multiple UEs. The paging message is broadcast on the data channel (i.e., PDSCH) (i.e., the PDCCH is masked with the P-RNTI). SI updates and emergency notifications are included in the DCI, and the PDCCH carrying the DCI is addressed to the P-RNTI. In RRC idle / inactive mode, the UE monitors one paging occasion (PO) in each DRX cycle. In RRC idle / inactive mode, the UE monitors the PO in the initial DL BWP.

[0060] In the RRC connected state, the UE monitors one or more POs to receive SI update notifications and emergency notifications. In the RRC connected state, the UE can monitor any PO in the paging DRX cycle and monitor at least one PO in the SI modification period. In the RRC idle / inactive mode, the UE monitors the PO in every DRX cycle in its active DL BWP. The PO is a set of "S" PDCCH monitoring opportunities for paging, where "S" is the number of SSBs transmitted in the cell (i.e., the SSB consists of the Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) and the Physical Broadcast Channel (PBCH)). The UE first determines the paging frame (PF) and then determines the PO relative to the determined PF. One PF is a radio frame (10ms).

[0061] - The PF of a UE is a radio frame with a system frame number "SFN" that satisfies the equation (SFN+PF_offset) mod T = (T div N)*(UE_ID mod N).

[0062] The index (i_s) indicating the index of the PO is determined by i_s = floor (UE_ID / N) mod Ns.

[0063] -T is the DRX cycle of the UE.

[0064] *In RRC_INACTIVE state, T is determined by the shortest of the UE-specific DRX value configured by RRC, the UE-specific DRX value configured by NAS, and the default DRX value broadcast in system information.

[0065] *In RRC_IDLE state, T is determined by the shortest of the UE-specific DRX value configured by NAS and the default DRX value broadcast in system information. If UE-specific DRX is not configured by upper layers (i.e., NAS), the default value applies.

[0066] -N: Total number of paging frames in T.

[0067] -Ns: Number of paging occasions of PF.

[0068] -PF_offset: Offset used for PF determination.

[0069] -UE_ID: 5G-S-TMSI mod 1024.

[0070] - The parameters Ns, nAndPagingFrameOffset, and the length of the default DRX cycle are signaled in System Information Block 1 (SIB1). The values ​​of N and PF_offset are derived from the parameter nAndPagingFrameOffset. If the UE does not have a 5G-S-TMSI, for example when the UE has not yet registered on the network, the UE can use UE_ID = 0 as the default identity in the above PF and i_s formulas.

[0071] -Determine the PDCCH monitoring occasion for paging based on the paging search space configuration (paging-SearchSpace) signaled by the gNB.

[0072] -When SearchSpaceId = 0 is configured for pagingSearchSpace, the PDCCH monitoring occasions for paging are the same as those for RMSI. When SearchSpaceId = 0 is configured for pagingSearchSpace, Ns is 1 or 2. For Ns = 1, there is only one PO starting at the first PDCCH monitoring occasion for paging in the PF. For Ns = 2, PO is in the first half-frame (i_s = 0) or the second half-frame (i_s = 1) of the PF.

[0073] When a SearchSpaceId other than 0 is configured for the pagingSearchSpace, the UE monitors the (i_s+1)th PDCCH monitoring occasion for paging. The PDCCH monitoring occasions for paging are determined based on the paging search space configuration (paging-SearchSpace) signaled by the gNB. PDCCH monitoring occasions for paging that do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are numbered sequentially starting from zero, starting with the first PDCCH monitoring occasion for paging in the PF. The gNB signals the parameter firstPDCCH-MonitoringOccasionOfPO for each PDCCH monitoring occasion corresponding to the PF. When firstPDCCH-MonitoringOccasionOfPO is signaled, the (i_s+1)th PDCCH monitoring occasion is a set of "S" consecutive PDCCH monitoring occasions for paging, starting from the PDCCH monitoring occasion number indicated by firstPDCCH-MonitoringOccasionOfPO (i.e., the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter). Otherwise, the (i_s+1)th PO is the set of "S" consecutive PDCCH monitoring occasions for paging, starting from the (i_s * S)th PDCCH monitoring occasion for paging. "S" is the number of SSBs actually transmitted, as determined by the parameter ssb-PositionsInBurst signaled in SystemInformationBlock1 received from the gNB. The parameter first-PDCCH-MonitoringOccasionOfPO is signaled in SIB1 for paging in the initial DL BWP. For paging in DL BWPs other than the initial DL BWP, the parameter first-PDCCH-MonitoringOccasionOfPO is signaled in the corresponding BWP configuration.

[0074] Figure 1An example of a DRX cycle according to an embodiment of the present disclosure is shown;

[0075] Connected mode UE-specific DRX: In the 5G wireless communication system, the PDCCH monitoring activity of the UE in RRC connected mode is dominated by DRX. When DRX is configured, the UE can monitor the PDCCH (addressed to the cell RNTI (C-RNTI), cancellation indication RNTI (CI-RNTI), configured scheduling RNTI (CS-RNTI), interruption RNTI (INT-RNTI, slot format indication RNTI (SFI-RNTI), semi-persistent CSI RNTI (SP-CSI-RNTI), TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI, availability indicator RNTI (AI-RNTI), sidelink RNTI (SL-RNTI), sidelink configuration scheduling RNTI (SLCS-RNTI) and SL semi-persistent scheduling V-RNTI) discontinuously. DRX is characterized by the following:

[0076] - On-duration: The duration that the UE waits to receive the PDCCH after waking up. If the UE successfully decodes the PDCCH, the UE remains awake and starts the inactivity timer;

[0077] - Inactivity timer: The duration that the UE waits for successful decoding of the PDCCH, starting from the last successful decoding of the PDCCH. If this fails, the UE may go back to sleep. The UE may restart the inactivity timer after a single successful decoding of the PDCCH, only for the first transmission (i.e., not for retransmissions);

[0078] - Retransmission timer: the duration for which retransmissions can be expected;

[0079] - Period: Periodic repetition of the specified on-duration, followed by a possible period of inactivity (see below Figure 5 );as well as

[0080] -Active Period: The total duration that the UE monitors the PDCCH. This includes the "on duration" of the DRX cycle, the time the UE performs continuous reception when the inactivity timer has not expired, and the time the UE performs continuous reception when waiting for a retransmission opportunity.

[0081] The serving cells of the MAC entity can be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure the second DRX group, there is only one DRX group and all serving cells belong to this one DRX group. When two DRX groups are configured, each serving cell is uniquely assigned to either of the two groups. The DRX parameters configured separately for each DRX group are: drx-onDurationTimer, drx-InactivityTimer. The DRX parameters common to the DRX group are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerUL, downlinkHARQ-FeedbackDisabled (optional) and uplinkHARQ-Mode (optional).

[0082] Figure 2 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown.

[0083] When DRX is configured, the active period for the serving cells in the DRX group includes the time and at the same time:

[0084] - the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or

[0085] -drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is running on any serving cell in the DRX group; or

[0086] -ra-ContentionResolutionTimer or msgB-ResponseWindow is running; or

[0087] - a Scheduling Request is sent on the PUCCH and is pending. If the serving cell is part of a non-terrestrial network, the active period starts after the Scheduling Request is sent when the SR_COUNTER is 0 for all SRs with pending SRs plus the UE-gNB RTT; or

[0088] -After successfully receiving a random access response to a random access preamble that was not selected by the MAC entity among the contention-based random access preambles, a newly transmitted PDCCH indicating a C-RNTI addressed to the MAC entity has not been received.

[0089] Based on the current operation when configuring UE-specific DRX connection mode:

[0090] *If the PDCCH indicates a DL transmission or if a MAC PDU is received in a configured downlink assignment for unicast:

[0091] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0092] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0093] * If drx-HARQ-RTT-TimerDL expires:

[0094] **If the data of the corresponding HARQ process is not successfully decoded:

[0095] **Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0096] *When drx-RetransmissionTimerDL is running, the UE is considered to be in the active period

[0097] Figure 3 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown.

[0098] At the same time, in order to save energy in the network, cell discontinuous transmission (DTX) and / or cell DRX can be configured:

[0099] *The periodic cell DTX / DRX pattern is configured by UE-specific RRC signaling messages.

[0100] *Cell DTX and cell DRX modes may be configured and operated separately (eg, one RRC configuration set for DL ​​and another for UL).

[0101] *UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0102] like Figure 3 As shown, if the HARQ feedback opportunity overlaps with the NW DRX duration, HARQ feedback is not sent (310, 320). According to the current operation, when the UE has not sent HARQ feedback, drx-HARQ-RTT-TimerDL is not started. Since drx-HARQ-RTT-TimerDL is not started, RetransmissionTimerDL is also not started (330). Therefore, if neither the on-duration timer nor the inactivity timer is running, the UE may not be able to receive the PDCCH for retransmission. When the on-duration timer and the inactivity timer are not running, running the RetransmissionTimerDL timer ensures that the UE can receive the PDCCH for retransmission.

[0103] [Method 1]

[0104] Figure 4 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown.

[0105] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0106] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0107] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that occurs periodically in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that occurs periodically in each "Period", and does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, Physical Random Access Channel (PRACH), etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0108] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources for DL / PDSCH transmission), or the UE receives a MAC PDU (e.g., Figure 4 shown):

[0109] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration (410) of the cell on which the HARQ feedback is to be sent; this may be the same or different than the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on the SpCell or PUCCH SCell, and DL transmissions may be on the SpCell, PUCCH SCell, or any other SCell):

[0110] **Instead of skipping DL HARQ feedback, the UE or (the MAC entity in the UE) sends DL HARQ feedback in a HARQ feedback opportunity (420);

[0111] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0112] **The UE or (MAC entity in the UE) stops the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0113] * Otherwise (non-overlapping case):

[0114] **The UE or (the MAC entity in the UE) sends DL HARQ feedback in a HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed. The UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerDL for the corresponding HARQ process.

[0115] * If drx-HARQ-RTT-TimerDL expires:

[0116] **If the data of the corresponding HARQ process is not successfully decoded:

[0117] ***The UE or (the MAC entity in the UE) starts the drx-RetransmissionTimerDL (430) of the corresponding HARQ process in the first symbol after the expiration of the drx-HARQ-RTT-TimerDL.

[0118] *The cell on which the HARQ feedback is to be sent by the UE or (the MAC entity in the UE) may be the same as or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on the SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE or (the MAC entity in the UE) receives the indicated DL / PDSCH transmission.

[0119] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0120] The base station transmits a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL transport blocks (TBs) in the indicated resources (which are the cell's PDSCH resources). The resources used for DL ​​transmissions may also be configured downlink allocations for unicast (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources for DL / PDSCH transmissions).

[0121] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0122] * The HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for DL ​​transmissions overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0123] **Instead of skipping reception of DL HARQ feedback in a HARQ feedback opportunity, the base station receives DL HARQ feedback in the HARQ feedback opportunity (the base station temporarily resumes reception during a portion of the network DRX duration that overlaps with the HARQ feedback opportunity)

[0124] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0125] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0126] **If drx-HARQ-RTT-TimerDL expires:

[0127] ***If the data of the corresponding HARQ process is not successfully decoded (i.e., HARQ NACK is rcvd):

[0128] *****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0129] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on a SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0130] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0131] [Method 1-1: Sidelink aspect]

[0132] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0133] *If PUCCH resources are configured:

[0134] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0135] ***Instead of skipping SL HARQ feedback, the UE or (the MAC entity in the UE) sends SL HARQ feedback to the gNB at the HARQ feedback opportunity;

[0136] ***The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL of the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying SL HARQ feedback is sent;

[0137] ***UE or (MAC entity in UE) stops drx-RetransmissionTimerSL of the corresponding HARQ process.

[0138] **Otherwise (non-overlapping case):

[0139] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0140] *Otherwise (PUCCH resources are not configured)

[0141] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding physical sidelink shared channel (PSSCH) transmission ends;

[0142] **Stop the drx-RetransmissionTimerSL corresponding to the HARQ process.

[0143] * If drx-HARQ-RTT-TimerSL expires:

[0144] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0145] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0146] **If PUCCH resources are not configured for SL grant:

[0147] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0148] [Method 1A]

[0149] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0150] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0151] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0152] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources used for DL / PDSCH transmission), or the UE receives a MAC PDU in a configured downlink allocation (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources used for DL / PDSCH transmission):

[0153] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent; this may be the same or different from the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on the SpCell or PUCCH SCell, and DL transmissions may be on the SpCell, PUCCH SCell, or any other SCell):

[0154] **If configured by the network (e.g. the network may send an indication in RRC signalling or PDCCH / DCI or system information, which may be per cell or per cell group or per BWP, and the UE applies the indication accordingly) the UE sends HARQ feedback in the HARQ feedback opportunity of the cell during the network DRX duration (of that cell):

[0155] ***Instead of skipping DL HARQ feedback, the UE or (the MAC entity in the UE) sends DL HARQ feedback in the HARQ feedback opportunity;

[0156] ***The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0157] ***UE or (MAC entity in UE) stops drx-RetransmissionTimerDL of the corresponding HARQ process.

[0158] **otherwise:

[0159] ***The UE (or a MAC entity in the UE) skips DL HARQ feedback transmission in a HARQ feedback opportunity that overlaps (partially or completely) with the network DRX duration.

[0160] * Otherwise (non-overlapping case):

[0161] **The UE or (the MAC entity in the UE) sends DL HARQ feedback in a HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed. The UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerDL for the corresponding HARQ process.

[0162] * If drx-HARQ-RTT-TimerDL expires:

[0163] **If the data of the corresponding HARQ process is not successfully decoded:

[0164] **Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0165] *The cell on which the HARQ feedback is to be sent by the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on the SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE received the indicated DL / PDSCH transmission.

[0166] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0167] The base station sends a PDCCH indicating the resources to be used for DL ​​transmission. The base station sends the DL TB in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmission can also be a configured downlink allocation for unicast (Configured Grant Type 1 or Configured Grant Type 2).

[0168] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0169] * The HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for DL ​​transmissions overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0170] **If configured by the network (e.g. the network may send an indication in RRC signalling or PDCCH / DCI or system information, which may be per cell or per cell group or per BWP, and the UE applies the indication accordingly) the UE sends HARQ feedback in the HARQ feedback opportunity of the cell during the network DRX duration (of that cell):

[0171] ***Instead of skipping reception of DL HARQ feedback in a HARQ feedback opportunity, the base station receives DL HARQ feedback in the HARQ feedback opportunity (the base station temporarily resumes reception during a portion of the network DRX duration that overlaps with the HARQ feedback opportunity);

[0172] ***Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0173] ***Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0174] ***If drx-HARQ-RTT-TimerDL expires:

[0175] ****If the data of the corresponding HARQ process is not successfully decoded (i.e., HARQ NACK is received):

[0176] *****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0177] **otherwise:

[0178] ***The base station skips reception of DL HARQ feedback in HARQ feedback opportunities that overlap (partially or completely) with the network DRX duration.

[0179] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on a SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0180] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0181] [Method 1A-1: Sidelink aspect]

[0182] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0183] *If PUCCH resources are configured:

[0184] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0185] ***If configured by the network (e.g. the network may send an indication in RRC signalling or PDCCH / DCI or system information, which may be per cell or per cell group or per BWP, and the UE applies the indication accordingly) the UE sends HARQ feedback in the HARQ feedback opportunity of the cell during the network DRX duration (of that cell):

[0186] ****Instead of skipping SL HARQ feedback, the UE or (the MAC entity in the UE) sends SL HARQ feedback to the gNB at the HARQ feedback opportunity;

[0187] ****The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL of the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying SL HARQ feedback is transmitted;

[0188] ****UE or (MAC entity in UE) stops drx-RetransmissionTimerSL of the corresponding HARQ process.

[0189] ***otherwise:

[0190] ****UE or (MAC entity within the UE) does not send SL HARQ feedback to the gNB during HARQ feedback opportunities

[0191] **Otherwise (non-overlapping case):

[0192] The UE or (the MAC entity in the UE) sends SL HARQ feedback in a HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback completes transmission. The UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0193] *Otherwise (PUCCH resources are not configured):

[0194] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0195] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0196] * If drx-HARQ-RTT-TimerSL expires:

[0197] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0198] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0199] **If PUCCH resources are not configured for SL grant:

[0200] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0201] [Method 2]

[0202] Figure 5 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown.

[0203] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0204] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0205] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0206] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources for DL / PDSCH transmission), or the UE receives a MAC PDU (e.g., Figure 5 shown):

[0207] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration (510) of the cell on which the HARQ feedback is to be sent; this may be the same or different from the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on the SpCell or PUCCH SCell, and DL transmissions may be on the SpCell, PUCCH SCell, or any other SCell):

[0208] **The UE or (MAC entity within the UE) does not send DL HARQ feedback at the HARQ feedback opportunity (520);

[0209] **The UE or (the MAC entity in the UE) starts the drx-RetransmissionTimerDL (530) of the corresponding HARQ process in the first symbol after the end of the corresponding DL / PDSCH reception (or in the first symbol at an offset after the end of the corresponding DL / PDSCH reception, where the offset is predefined or signaled by the base station in RRC signaling or system information);

[0210] *otherwise:

[0211] **UE or (MAC entity in UE) sends DL HARQ feedback in HARQ feedback opportunity;

[0212] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0213] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0214] **If drx-HARQ-RTT-TimerDL expires:

[0215] ***If the data of the corresponding HARQ process is not successfully decoded:

[0216] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0217] *The cell on which the HARQ feedback is to be sent by the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on an SpCell or PUCCH Scell, and the DL transmission may be on the SpCell or PUCCH Scell ​​or any other Scell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE received the indicated DL / PDSCH transmission.

[0218] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0219] The base station transmits a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL TBs in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmissions may also be configured downlink allocations for unicast (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources for DL / PDSCH transmissions).

[0220] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0221] *If the HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for a DL transmission overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0222] **Skip the reception of DL HARQ feedback at the HARQ feedback opportunity;

[0223] **Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the end of the corresponding DL / PDSCH reception (or in the first symbol at an offset after the end of the corresponding DL / PDSCH reception, where the offset is signaled by the base station in RRC signaling or system information).

[0224] *otherwise:

[0225] **Receive DL HARQ feedback at the HARQ feedback opportunity;

[0226] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity carrying DL HARQ feedback;

[0227] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0228] **If drx-HARQ-RTT-TimerDL expires:

[0229] ***If the data of the corresponding HARQ process is not successfully decoded (i.e., HARQ NACK is received):

[0230] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0231] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on an SpCell or PUCCH Scell, and the DL transmission may be on the SpCell or PUCCH Scell ​​or any other Scell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0232] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0233] [Method 2-1: Sidelink aspect]

[0234] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0235] *If PUCCH resources are configured:

[0236] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0237] ***The UE or (MAC entity within the UE) does not send SL HARQ feedback at the HARQ feedback opportunity;

[0238] ***The UE or (the MAC entity in the UE) starts the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the end of the corresponding PSSCH transmission (or in the first symbol at an offset after the end of the corresponding PSSCH transmission, where the offset is predefined or signaled by the base station in RRC signaling or system information);

[0239] **Otherwise (non-overlapping case):

[0240] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0241] *Otherwise (PUCCH resources are not configured):

[0242] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0243] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0244] * If drx-HARQ-RTT-TimerSL expires:

[0245] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0246] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0247] **If PUCCH resources are not configured for SL grant:

[0248] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0249] [Method 2A]

[0250] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0251] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0252] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0253] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources used for DL / PDSCH transmission), or the UE receives a MAC PDU in a configured downlink assignment (configured grant type 1 or configured grant type 2 indicating periodic resources used for DL / PDSCH transmission):

[0254] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent; this may be the same or different from the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on the SpCell or PUCCH SCell, and DL transmissions may be on the SpCell, PUCCH SCell, or any other SCell):

[0255] **The UE or (MAC entity within the UE) does not send DL HARQ feedback at the HARQ feedback opportunity;

[0256] **If the network configures (e.g. the network may send an indication in RRC signalling or PDCCH / DCI or system information, which may be per cell or per cell group or per BWP, and the UE applies the indication accordingly) the UE starts drx-RetransmissionTimerDL in the first symbol after the end of PDSCH transmission (of that cell) in case of overlap (or if enhanced DRX operation for NES is indicated / configured by the network):

[0257] ***The UE or (the MAC entity in the UE) starts the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the end of the corresponding DL / PDSCH reception (or in the first symbol at an offset after the end of the corresponding DL / PDSCH reception, where the offset is signaled by the base station in RRC signaling or system information);

[0258] *otherwise:

[0259] **UE or (MAC entity in UE) sends DL HARQ feedback in HARQ feedback opportunity;

[0260] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0261] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0262] **If drx-HARQ-RTT-TimerDL expires:

[0263] ***If the data of the corresponding HARQ process is not successfully decoded:

[0264] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0265] *The cell on which the HARQ feedback is to be sent by the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on the SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE received the indicated DL / PDSCH transmission.

[0266] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0267] The base station transmits a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL TBs in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmissions may also be configured downlink allocations for unicast (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources for DL / PDSCH transmissions).

[0268] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0269] * If the HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for a DL transmission overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received);

[0270] **Skip the reception of DL HARQ feedback at the HARQ feedback opportunity;

[0271] **If the network configures (e.g. the network may send an indication in RRC signalling or PDCCH / DCI or system information, which may be per cell or per cell group or per BWP, and the UE applies the indication accordingly) the UE starts drx-RetransmissionTimerDL in the first symbol after the end of PDSCH transmission (of that cell) in case of overlap (or if enhanced DRX operation for NES is indicated / configured by the network):

[0272] ***Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the end of the corresponding DL / PDSCH transmission (or in the first symbol at an offset after the end of the corresponding DL / PDSCH transmission, where the offset is signaled by the base station in RRC signaling or system information);

[0273] *otherwise:

[0274] **Receive DL HARQ feedback at the HARQ feedback opportunity;

[0275] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on a SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0276] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0277] [Method 2A-1: Sidelink aspect]

[0278] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0279] *If PUCCH resources are configured:

[0280] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0281] ***The UE or (MAC entity within the UE) does not send SL HARQ feedback at the HARQ feedback opportunity;

[0282] ***If the network configures (e.g. the network may send an indication in RRC signalling or PDCCH / DCI or system information, which may be per cell or per cell group or per BWP, and the UE applies the indication accordingly) the UE starts drx-RetransmissionTimerSL in the first symbol after the end of PSSCH transmission at the overlapped opportunity (or if enhanced DRX operation for NES is indicated / configured by the network):

[0283] ****The UE or (the MAC entity in the UE) starts the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the end of the corresponding PSSCH transmission (or in the first symbol at an offset after the end of the corresponding PSSCH transmission, where the offset is predefined or signaled by the base station in RRC signaling or system information);

[0284] **Otherwise (non-overlapping case):

[0285] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0286] *Otherwise (PUCCH resources are not configured):

[0287] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0288] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0289] * If drx-HARQ-RTT-TimerSL expires:

[0290] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0291] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0292] **If PUCCH resources are not configured for SL grant:

[0293] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0294] [Method 3]

[0295] Figure 6 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown.

[0296] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0297] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0298] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0299] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources for DL / PDSCH transmission), or the UE receives a MAC PDU (e.g., Figure 6 shown):

[0300] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration (610) of the cell on which the HARQ feedback is to be sent; this may be the same or different from the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on a SpCell or PUCCH Scell, and DL transmissions may be on a SpCell, PUCCH Scell, or any other Scell):

[0301] **The UE or (MAC entity within the UE) does not send DL HARQ feedback at the HARQ feedback opportunity (620);

[0302] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity.

[0303] **If drx-HARQ-RTT-TimerDL expires:

[0304] ***If the data of the corresponding HARQ process is not successfully decoded:

[0305] ****Start the drx-RetransmissionTimerDL (630) of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0306] *otherwise:

[0307] **UE or (MAC entity in UE) sends DL HARQ feedback in HARQ feedback opportunity;

[0308] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0309] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0310] **If drx-HARQ-RTT-TimerDL expires:

[0311] ***If the data of the corresponding HARQ process is not successfully decoded:

[0312] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0313] *The cell on which the HARQ feedback is to be sent by the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on an SpCell or PUCCH Scell, and the DL transmission may be on the SpCell or PUCCH Scell ​​or any other Scell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE received the indicated DL / PDSCH transmission.

[0314] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0315] The base station transmits a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL TBs in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmissions may also be configured downlink allocations for unicast (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources for DL / PDSCH transmissions).

[0316] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0317] *If the HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for a DL transmission overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0318] **Skip the reception of DL HARQ feedback at the HARQ feedback opportunity;

[0319] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity;

[0320] **If drx-HARQ-RTT-TimerDL expires:

[0321] ***Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0322] *otherwise:

[0323] **Receive DL HARQ feedback at the HARQ feedback opportunity;

[0324] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity carrying DL HARQ feedback;

[0325] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0326] **If drx-HARQ-RTT-TimerDL expires:

[0327] ***Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0328] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on an SpCell or PUCCH Scell, and the DL transmission may be on the SpCell or PUCCH Scell ​​or any other Scell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0329] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0330] [Method 3-1: Sidelink aspect]

[0331] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0332] *If PUCCH resources are configured:

[0333] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0334] ***UE or (MAC entity within the UE) does not send SL HARQ feedback at the HARQ feedback opportunity

[0335] ***The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity for SL HARQ feedback on the PUCCH; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0336] **Otherwise (non-overlapping case):

[0337] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0338] *Otherwise (PUCCH resources are not configured):

[0339] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0340] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0341] * If drx-HARQ-RTT-TimerSL expires:

[0342] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0343] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0344] **If PUCCH resources are not configured for SL grant:

[0345] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0346] [Method 3A]

[0347] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0348] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0349] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0350] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources used for DL / PDSCH transmission), or the UE receives a MAC PDU in a configured downlink allocation (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources used for DL / PDSCH transmission):

[0351] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent; this may be the same or different from the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on a SpCell or PUCCH Scell, and DL transmissions may be on a SpCell, PUCCH Scell, or any other Scell):

[0352] **The UE or (MAC entity within the UE) does not send DL HARQ feedback at the HARQ feedback opportunity;

[0353] **If the network configures (e.g. the network may send an indication in RRC signaling or PDCCH / DCI or system information, which may be per-cell or per-cell-group or per-BWP, and the UE applies the indication accordingly) when not sending HARQ feedback in a HARQ feedback opportunity (of that cell) in case of overlap, the UE starts drx-HARQ-RTT-TimerDL in the first symbol after the end of the HARQ feedback opportunity (or if enhanced DRX operation for NES is indicated / configured by the network):

[0354] ***The UE or (MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity;

[0355] ***If drx-HARQ-RTT-TimerDL expires:

[0356] ****If the data of the corresponding HARQ process is not successfully decoded:

[0357] *****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0358] *otherwise:

[0359] **UE or (MAC entity in UE) sends DL HARQ feedback in HARQ feedback opportunity;

[0360] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0361] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0362] **If drx-HARQ-RTT-TimerDL expires:

[0363] ***If the data of the corresponding HARQ process is not successfully decoded:

[0364] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0365] *The cell on which the HARQ feedback is to be sent by the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on the SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE received the indicated DL / PDSCH transmission.

[0366] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0367] The base station sends a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL TBs in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmissions can also be configured downlink allocations for unicast (configured grant type 1 or configured grant type 2 indicating periodic resources for DL / PDSCH transmissions).

[0368] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0369] *If the HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for a DL transmission overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0370] **Skip the reception of DL HARQ feedback at the HARQ feedback opportunity;

[0371] **If the network configures (e.g. the network may send an indication in RRC signaling or PDCCH / DCI or system information, which may be per-cell or per-cell-group or per-BWP, and the UE applies the indication accordingly) when not sending HARQ feedback in a HARQ feedback opportunity (of that cell) in case of overlap, the UE starts drx-HARQ-RTT-TimerDL in the first symbol after the end of the HARQ feedback opportunity (or if enhanced DRX operation for NES is indicated / configured by the network):

[0372] ***Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity;

[0373] ***If drx-HARQ-RTT-TimerDL expires:

[0374] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0375] *otherwise:

[0376] **Receive DL HARQ feedback at the HARQ feedback opportunity;

[0377] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the end of the HARQ Feedback Opportunity carrying DL HARQ feedback;

[0378] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0379] **If drx-HARQ-RTT-TimerDL expires:

[0380] ***If the data of the corresponding HARQ process is not successfully decoded (i.e., HARQ NACK is received):

[0381] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0382] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on a SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0383] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0384] [Method 3A-1: Sidelink aspect]

[0385] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0386] *If PUCCH resources are configured:

[0387] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0388] ***The UE or (MAC entity within the UE) does not send SL HARQ feedback at the HARQ feedback opportunity;

[0389] ***If the network configures (e.g. the network may send an indication in RRC signaling or PDCCH / DCI or system information, which may be per-cell or per-cell-group or per-BWP, and the UE applies the indication accordingly) when not sending HARQ feedback in an overlapping HARQ feedback opportunity, the UE starts drx-HARQ-RTT-TimerSL in the first symbol after the end of the HARQ feedback opportunity (or if enhanced DRX operation for NES is indicated / configured by the network):

[0390] ****The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity for SL HARQ feedback on the PUCCH; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0391] **Otherwise (non-overlapping case):

[0392] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0393] *Otherwise (PUCCH resources are not configured):

[0394] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0395] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0396] * If drx-HARQ-RTT-TimerSL expires:

[0397] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0398] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0399] **If PUCCH resources are not configured for SL grant:

[0400] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0401] [Method 4]

[0402] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0403] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0404] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0405] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources for DL / PDSCH transmission), or the UE receives a MAC PDU (e.g., Figure 4 shown):

[0406] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent; this may be the same or different from the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on the SpCell or PUCCH SCell, and DL transmissions may be on the SpCell, PUCCH SCell, or any other SCell):

[0407] **The UE or (MAC entity within the UE) does not send DL HARQ feedback at the HARQ feedback opportunity;

[0408] * Otherwise (non-overlapping case):

[0409] **The UE or (the MAC entity in the UE) sends DL HARQ feedback in a HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL for the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed. The UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerDL for the corresponding HARQ process.

[0410] **If drx-HARQ-RTT-TimerDL expires:

[0411] ***If the data of the corresponding HARQ process is not successfully decoded:

[0412] ****The UE or (the MAC entity in the UE) starts the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the expiration of the drx-HARQ-RTT-TimerDL.

[0413] *The cell on which the HARQ feedback is to be sent by the UE or (the MAC entity in the UE) may be the same as or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on the SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE or (the MAC entity in the UE) receives the indicated DL / PDSCH transmission.

[0414] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0415] The base station transmits a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL TBs in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmissions may also be configured downlink allocations for unicast (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources for DL / PDSCH transmissions).

[0416] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0417] *If the HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for a DL transmission overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0418] **The base station did not receive DL HARQ feedback at the HARQ feedback opportunity

[0419] *otherwise:

[0420] **The base station receives DL HARQ feedback at the HARQ feedback opportunity;

[0421] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0422] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0423] **If drx-HARQ-RTT-TimerDL expires:

[0424] ***If the data of the corresponding HARQ process is not successfully decoded (i.e., HARQ NACK is received):

[0425] The drx-RetransmissionTimerDL of the corresponding HARQ process is started in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0426] The cell on which HARQ feedback is to be received from the UE may be the same as or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on a SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be sent from the same cell as or different from the cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0427] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0428] [Method 4-1: Sidelink aspects]

[0429] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0430] *If PUCCH resources are configured:

[0431] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0432] ***The UE or (MAC entity within the UE) does not send SL HARQ feedback to the gNB during the HARQ feedback opportunity.

[0433] **Otherwise (non-overlapping case):

[0434] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0435] *Otherwise (PUCCH resources are not configured):

[0436] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0437] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0438] * If drx-HARQ-RTT-TimerSL expires:

[0439] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0440] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0441] **If PUCCH resources are not configured for SL grant:

[0442] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0443] [Method 5]

[0444] Figure 7Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown.

[0445] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0446] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0447] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0448] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources for DL / PDSCH transmission), or the UE receives a MAC PDU (e.g., Figure 7 shown):

[0449] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration (710) of the cell on which the HARQ feedback is to be sent; this may be the same or different from the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on the SpCell or PUCCH SCell, and DL transmissions may be on the SpCell, PUCCH SCell, or any other SCell):

[0450] **The UE or (MAC entity within the UE) does not send DL HARQ feedback at the HARQ feedback opportunity (720);

[0451] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the network DRX duration (or in the first symbol at the offset after the end of the network DRX duration);

[0452] **If drx-HARQ-RTT-TimerDL expires:

[0453] ***If the data of the corresponding HARQ process is not successfully decoded:

[0454] ****Start the drx-RetransmissionTimerDL (730) of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0455] *otherwise:

[0456] **UE or (MAC entity in UE) sends DL HARQ feedback in HARQ feedback opportunity;

[0457] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0458] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0459] **If drx-HARQ-RTT-TimerDL expires:

[0460] ***If the data of the corresponding HARQ process is not successfully decoded:

[0461] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0462] *The cell on which the HARQ feedback is to be sent by the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on the SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE received the indicated DL / PDSCH transmission.

[0463] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0464] The base station transmits a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL TBs in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmissions may also be configured downlink allocations for unicast (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources for DL / PDSCH transmissions).

[0465] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0466] *If the HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for a DL transmission overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0467] **Skip the reception of DL HARQ feedback at the HARQ feedback opportunity;

[0468] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the network DRX duration (or in the first symbol at the offset after the end of the network DRX duration);

[0469] **If drx-HARQ-RTT-TimerDL expires:

[0470] ***Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0471] *otherwise:

[0472] **Receive DL HARQ feedback at the HARQ feedback opportunity;

[0473] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity carrying DL HARQ feedback;

[0474] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0475] **If drx-HARQ-RTT-TimerDL expires:

[0476] ***Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0477] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on a SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0478] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0479] [Method 5-1: Sidelink aspects]

[0480] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0481] *If PUCCH resources are configured:

[0482] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0483] ***UE or (MAC entity within the UE) does not send SL HARQ feedback to the gNB during HARQ feedback opportunities

[0484] ***The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL of the corresponding HARQ process in the first symbol after the end of the network DRX duration (or in the first symbol at the offset after the end of the network DRX duration);

[0485] ***UE or (MAC entity in UE) stops drx-RetransmissionTimerSL of the corresponding HARQ process.

[0486] **Otherwise (non-overlapping case):

[0487] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0488] *Otherwise (PUCCH resources are not configured):

[0489] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0490] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0491] * If drx-HARQ-RTT-TimerSL expires:

[0492] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0493] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0494] **If PUCCH resources are not configured for SL grant:

[0495] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0496] [Method 6]

[0497] Figure 8 Another example of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunity according to an embodiment of the present disclosure is shown.

[0498] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0499] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0500] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0501] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources for DL / PDSCH transmission), or the UE receives a MAC PDU (e.g., Figure 8 shown):

[0502] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration (810) of the cell on which the HARQ feedback is to be sent; this may be the same or different than the cell receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on the SpCell or PUCCH SCell, and DL transmissions may be on the SpCell, PUCCH SCell, or any other SCell):

[0503] **The UE or (MAC entity within the UE) does not send DL HARQ feedback at the HARQ feedback opportunity (820);

[0504] **The UE or (the MAC entity in the UE) starts the drx-RetransmissionTimerDL (830) of the corresponding HARQ process in the first symbol after the end of the NW DRX duration (or in the first symbol at an offset after the end of the NW DRX duration, where the offset is predefined or signaled by the base station in RRC signaling or system information);

[0505] *otherwise:

[0506] **UE or (MAC entity in UE) sends DL HARQ feedback in HARQ feedback opportunity;

[0507] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0508] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0509] **If drx-HARQ-RTT-TimerDL expires:

[0510] ***If the data of the corresponding HARQ process is not successfully decoded:

[0511] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0512] *The cell on which the HARQ feedback is to be sent by the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on the SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE received the indicated DL / PDSCH transmission.

[0513] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0514] The base station transmits a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL TBs in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmissions may also be configured downlink allocations for unicast (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources for DL / PDSCH transmissions).

[0515] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0516] *If the HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for a DL transmission overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0517] **Skip the reception of DL HARQ feedback at the HARQ feedback opportunity;

[0518] **The drx-RetransmissionTimerDL of the corresponding HARQ process is started in the first symbol after the end of the NW DRX duration (or in the first symbol at an offset after the end of the NW DRX duration, where the offset is signaled by the base station in RRC signaling or system information).

[0519] *otherwise:

[0520] **Receive DL HARQ feedback at the HARQ feedback opportunity;

[0521] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity carrying DL HARQ feedback;

[0522] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0523] **If drx-HARQ-RTT-TimerDL expires:

[0524] ***If the data of the corresponding HARQ process is not successfully decoded (i.e., HARQ NACK is received):

[0525] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0526] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on a SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0527] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0528] [Method 6-1: Sidelink aspects]

[0529] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0530] *If PUCCH resources are configured:

[0531] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0532] ***The UE or (MAC entity within the UE) does not send SL HARQ feedback to the gNB during the HARQ feedback opportunity;

[0533] ***The UE or (the MAC entity in the UE) starts the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the end of the NW DRX duration (or in the first symbol at an offset after the end of the NW DRX duration, where the offset is predefined or signaled by the base station in RRC signaling or system information);

[0534] **Otherwise (non-overlapping case):

[0535] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0536] *Otherwise (PUCCH resources are not configured):

[0537] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0538] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0539] * If drx-HARQ-RTT-TimerSL expires:

[0540] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0541] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0542] **If PUCCH resources are not configured for SL grant:

[0543] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0544] [Method 7]

[0545] Figure 9 and Figure 10 Other examples of PDCCH reception with respect to overlap of network DRX duration and HARQ feedback opportunities according to embodiments of the present disclosure are shown.

[0546] The UE is in the RRC_CONNECTED state. The UE is configured with a connected mode DRX configuration using RRC signaling (as previously described). For network energy conservation, cell DTX and / or cell DRX can be configured via UE-specific RRC signaling messages, where a periodic cell DTX / DRX pattern is configured. Cell DTX and cell DRX patterns can be configured and operated separately (e.g., one RRC configuration set for DL ​​and another for UL). UE-specific DRX can be configured in cells that support cell DTX and / or cell DRX.

[0547] The periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)). Alternatively, the periodic cell DTX pattern may be configured by the "Duration" and "Period" fields, wherein during the "Duration" interval that occurs periodically in each "Period", the cell performs transmission, and during the interval "Period-Duration", the cell does not perform transmission (or stops certain transmissions (e.g., PDSCH, PBCH, SSB, etc.)).

[0548] A periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the "Duration" interval that periodically occurs in each "Period". Alternatively, a periodic cell DRX pattern may be configured using the "Duration" and "Period" fields, wherein the cell performs reception during the "Duration" interval that periodically occurs in each "Period", while the cell does not perform reception (or stops certain receptions, such as PUCCH, PUSCH, PRACH, etc.) during the interval "Period-Duration". During a cell-level DRX duration in which the network (i.e., base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell, the UE does not transmit (or does not transmit) certain transmissions on the uplink of that cell.

[0549] The UE (or a MAC entity in the UE) receives a PDCCH indicating a DL / PDSCH transmission for unicast (i.e., resources for DL / PDSCH transmission), or the UE receives a MAC PDU (e.g., Figure 9 and Figure 10 shown):

[0550] *The UE or (the MAC entity in the UE) determines the HARQ feedback opportunity, where the HARQ feedback opportunity starts at an offset K1 from the end of the DL / PDSCH transmission.

[0551] * If the HARQ feedback opportunity used to send DL HARQ feedback for a DL / PDSCH transmission (indicated by PDCCH or configured downlink assignment) overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration (910, 920, 1010, 1020) of the cell on which the HARQ feedback is to be sent; this may be the same or different cell from the one receiving the DL / PDSCH transmission indicated by PDCCH or the configured downlink assignment; HARQ feedback is sent on the SpCell or PUCCH SCell, and DL transmissions may be on the SpCell, PUCCH SCell, or any other SCell):

[0552] **The UE or (MAC entity in the UE) determines another HARQ feedback opportunity, wherein the HARQ feedback opportunity starts at an offset K1' from the end of the network DRX duration (925). K1' may be signaled in an RRC signaling message or in the PDCCH. The time duration (symbols) and frequency resources (PRBs) of the HARQ feedback opportunity may be the same as the HARQ feedback opportunity that overlaps with the network DRX duration. The value of K1' used here may be the same as or different from K1 (e.g., Figure 9 shown).

[0553] **(Alternatively) the UE or (the MAC entity in the UE) determines another HARQ feedback opportunity, where the HARQ feedback opportunity starts at an offset K1' from the end of the DL / PDSCH transmission (1025). K1' may be signaled in an RRC signaling message or in the PDCCH. The time duration (symbols) and frequency resources (PRBs) of the HARQ feedback opportunity may be the same as the HARQ feedback opportunity that overlaps with the network DRX duration. The value of K1' used here is different from K1 (e.g. Figure 10 shown).

[0554] **The UE or (the MAC entity within the UE) sends DL HARQ feedback in the determined HARQ feedback opportunity (925, 1025);

[0555] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0556] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0557] **If drx-HARQ-RTT-TimerDL expires:

[0558] ***If the data of the corresponding HARQ process is not successfully decoded:

[0559] **** In the first symbol after the expiration of drx-HARQ-RTT-TimerDL, the drx-RetransmissionTimerDL of the corresponding HARQ process is started (930, 1030).

[0560] *otherwise:

[0561] **UE or (MAC entity in UE) sends DL HARQ feedback in HARQ feedback opportunity

[0562] **The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the corresponding transmission of the DL HARQ feedback is completed;

[0563] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0564] **If drx-HARQ-RTT-TimerDL expires:

[0565] ***If the data of the corresponding HARQ process is not successfully decoded:

[0566] ****Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0567] *The cell on which the HARQ feedback is to be sent by the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is received; HARQ feedback is sent on the SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH SCell or any other SCell. The PDCCH indicating the DL transmission may be received from the same or different cell as the cell on which the UE received the indicated DL / PDSCH transmission.

[0568] The base station configures cell-specific DRX for one or more serving cells. During the cell-level DRX duration of a cell, the network (ie, the base station) does not receive transmissions (or certain transmissions) from the UE on the uplink of that cell.

[0569] The base station transmits a PDCCH indicating the resources to be used for DL ​​transmissions. The base station transmits DL TBs in the indicated resources (these resources are the PDSCH resources of the cell). The resources used for DL ​​transmissions may also be configured downlink allocations for unicast (indicated by a configured grant type 1 or configured grant type 2 configuration indicating periodic resources for DL / PDSCH transmissions).

[0570] *When a DL TB is transmitted, HARQ feedback from the UE is expected in the HARQ feedback opportunity corresponding to the DL TB.

[0571] * Determine the HARQ feedback timing, where the HARQ feedback timing starts at offset K1 from the end of DL / PDSCH transmission

[0572] *If the HARQ feedback opportunity (indicated by PDCCH or configured downlink assignment) used to receive DL HARQ feedback for a DL transmission overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell over which the HARQ feedback is received):

[0573] **Determine another HARQ feedback opportunity, where the HARQ feedback opportunity begins at an offset K1' from the end of the network DRX duration. K1' may be signaled in an RRC signaling message or in the PDCCH. The time duration (symbols) and frequency resources (PRBs) of the HARQ feedback opportunity may be the same as those of the HARQ feedback opportunity that overlaps with the network DRX duration. The value of K1' used here may be the same as or different from K1.

[0574] **(Alternative) Determine another HARQ feedback opportunity, where the HARQ feedback opportunity begins at an offset K1' from the end of DL / PDSCH transmission. K1' can be signaled in an RRC signaling message or in the PDCCH. The time duration (symbols) and frequency resources (PRBs) of the HARQ feedback opportunity can be the same as the HARQ feedback opportunity that overlaps with the network DRX duration. The value of K1' used here is different from K1.

[0575] **Receive DL HARQ feedback at the HARQ feedback opportunity;

[0576] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity carrying DL HARQ feedback;

[0577] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0578] **If drx-HARQ-RTT-TimerDL expires:

[0579] ***Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0580] *otherwise:

[0581] **Receive DL HARQ feedback at the HARQ feedback opportunity;

[0582] **Start the drx-HARQ-RTT-TimerDL of the corresponding HARQ process in the first symbol after the end of the HARQ feedback opportunity carrying DL HARQ feedback;

[0583] **Stop the drx-RetransmissionTimerDL of the corresponding HARQ process.

[0584] **If drx-HARQ-RTT-TimerDL expires:

[0585] ***Start the drx-RetransmissionTimerDL of the corresponding HARQ process in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0586] *The cell on which HARQ feedback is to be received from the UE may be the same or different from the cell on which the DL / PDSCH transmission indicated by the PDCCH or configured downlink assignment is sent; HARQ feedback is received on a SpCell or PUCCH SCell, and the DL transmission may be on the SpCell or PUCCH Scell ​​or any other Scell. The PDCCH indicating the DL transmission may be sent from the same or different cell on which the indicated DL / PDSCH transmission is sent to the UE.

[0587] In one embodiment, the network DRX duration in the above description may be a cell-level inactivity duration, wherein the cell does not receive any transmission from the UE, or does not receive any dedicated transmission from the UE, or does not receive certain transmissions (eg, PUCCH / PUSCH) from the UE.

[0588] [Method 7-1: Sidelink aspects]

[0589] The UE (or a MAC entity in the UE) receives a PDCCH indicating SL transmission (ie, resources for SL transmission), or transmits a MAC PDU in a configured sidelink grant.

[0590] *If PUCCH resources are configured:

[0591] **The UE or (MAC entity in the UE) determines the HARQ feedback opportunity, where the HARQ feedback opportunity starts from the end of the PSSCH transmission to another UE or the offset K1 from the PSFCH reception of the UE to which the PSSCH is transmitted.

[0592] **If the HARQ feedback opportunity for sending SL HARQ feedback on PUCCH overlaps (partially or completely) with the network DRX duration (i.e., the cell-level DRX duration of the cell on which the HARQ feedback is to be sent):

[0593] ***Determine another HARQ feedback opportunity, where the HARQ feedback opportunity begins at an offset K1' from the end of the network DRX duration. K1' may be signaled in an RRC signaling message or in the PDCCH. The time duration (symbols) and frequency resources (PRBs) of the HARQ feedback opportunity may be the same as those of the HARQ feedback opportunity that overlaps with the network DRX duration. The value of K1' used here may be the same as or different from K1.

[0594] *** (Alternative) Determine another HARQ feedback opportunity, where the HARQ feedback opportunity begins at an offset K1' from the end of PSSCH transmission to another UE or from the PSFCH reception of the UE to which PSSCH is transmitted. K1' can be signaled in an RRC signaling message or in the PDCCH. The time duration (symbols) and frequency resources (PRBs) of the HARQ feedback opportunity can be the same as those of the HARQ feedback opportunity that overlaps with the network DRX duration. The value of K1' used here is different from K1.

[0595] ***The UE or (MAC entity within the UE) sends SL HARQ feedback to the gNB in ​​the new HARQ feedback opportunity;

[0596] ***The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL of the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying SL HARQ feedback is sent;

[0597] ***UE or (MAC entity in UE) stops drx-RetransmissionTimerSL of the corresponding HARQ process.

[0598] **Otherwise (non-overlapping case):

[0599] ***The UE or (the MAC entity in the UE) sends SL HARQ feedback in the HARQ feedback opportunity. The UE or (the MAC entity in the UE) starts the drx-HARQ-RTT-TimerSL for the corresponding HARQ process in the first symbol after the corresponding PUCCH carrying the SL HARQ feedback ends transmission; the UE or (the MAC entity in the UE) stops the drx-RetransmissionTimerSL for the corresponding HARQ process.

[0600] *Otherwise (PUCCH resources are not configured):

[0601] **Start the drx-HARQ-RTT-TimerSL of the corresponding HARQ process at the first symbol after the corresponding PSSCH transmission ends;

[0602] **Stop the drx-RetransmissionTimerSL of the corresponding HARQ process.

[0603] * If drx-HARQ-RTT-TimerSL expires:

[0604] **If the HARQ NACK feedback for the corresponding HARQ process is sent on the PUCCH; or

[0605] **If the HARQ NACK feedback for the corresponding HARQ process is not sent on the PUCCH; or

[0606] **If PUCCH resources are not configured for SL grant:

[0607] ***Start the drx-RetransmissionTimerSL of the corresponding HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerSL.

[0608] By replacing the parameter drx-HARQ-RTT-TimerDL with drx-HARQ-RTT-TimerDL-PTM and replacing the parameter drx-RetransmissionTimerDL with drx-RetransmissionTimerDL-PTM, the embodiments and methods described in Methods 1 to 7 can also be applied to the case of Multicast and Broadcast Service (MBS), that is, if the PDCCH indicates DL multicast transmission and if HARQ feedback is enabled.

[0609] Figure 11 A terminal according to an embodiment of the present disclosure is shown.

[0610] refer to Figure 11 , the terminal includes a transceiver 1110, a controller 1120, and a memory 1130. The controller 1120 may refer to a circuit, an application specific integrated circuit (ASIC), or at least one processor. The transceiver 1110, the controller 1120, and the memory 1130 are configured to execute, for example, Figures 1 to 10 The operation of the UE shown in the figures or described above. Although the transceiver 1110, the controller 1120, and the memory 1130 are shown as separate entities, they can be implemented as a single entity, such as a single chip. Alternatively, the transceiver 1110, the controller 1120, and the memory 1130 can be electrically connected or coupled to each other.

[0611] The transceiver 1110 may transmit and receive signals to and from other network entities (eg, a base station or another terminal).

[0612] The controller 1120 may control the UE to perform the function according to one of the foregoing embodiments.

[0613] In one embodiment, the terminal's operations can be implemented using a memory 1130 storing corresponding program codes. Specifically, the terminal can be equipped with a memory 1130 to store program codes for implementing the desired operations. To perform the desired operations, the controller 1120 can read and execute the program codes stored in the memory 1130 using a processor or a central processing unit (CPU).

[0614] Figure 12 A base station according to an embodiment of the present disclosure is shown.

[0615] refer to Figure 12 , the base station includes a transceiver 1210, a controller 1220 and a memory 1230. The transceiver 1210, the controller 1220 and the memory 1230 are configured to execute, for example, Figures 1 to 10 The operations of the network (e.g., gNB) shown in the figures or described above are described in detail. Although transceiver 1210, controller 1220, and memory 1230 are shown as separate entities, they may be implemented as a single entity, such as a single chip. Transceiver 1210, controller 1220, and memory 1230 may be electrically connected or coupled to each other.

[0616] The transceiver 1210 can send and receive signals to and from other network entities (e.g., terminals). The controller 1220 can control the base station to perform functions according to one of the above-described embodiments. The controller 1220 can be a circuit, an ASIC, or at least one processor. In one embodiment, the base station's operations can be implemented using a memory 1230 storing corresponding program code. Specifically, the base station can be equipped with the memory 1230 to store program code for implementing desired operations. To perform the desired operations, the controller 1220 can read and execute the program code stored in the memory 1230 using a processor or CPU.

[0617] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

[0618] As described above, the embodiments disclosed in the specification and the drawings are merely for presenting specific examples to easily explain the contents of the present disclosure and to aid understanding, but are not intended to limit the scope of the present disclosure. Therefore, the scope of the present disclosure should be analyzed to include all changes or modifications derived from the technical concepts of the present disclosure other than the embodiments disclosed herein.

[0619] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: receiving configuration information for network discontinuous reception (NW DRX) from a base station; receiving downlink data from a base station; Identifying that the timing of Hybrid Automatic Repeat Request (HARQ) information for downlink data overlaps with the duration of NW DRX; as well as At a timing overlapping with the NW DRX duration, HARQ information of downlink data is transmitted to the base station.

2. The method according to claim 1, further comprising: In the first symbol after the transmission of the HARQ information is completed, a DRX HARQ round trip time timer (drx-HARQ-RTT-TimerDL) for the downlink of the corresponding HARQ process is started.

3. The method according to claim 2, further comprising: When drx-HARQ-RTT-TimerDL expires, start the DRX retransmission timer (drx-RetransmissionTimerDL) of the downlink corresponding to the HARQ process in the first symbol after the expiration of drx-HARQ-RTT-TimerDL; and While drx-RetransmissionTimerDL is running, a Physical Downlink Control Channel (PDCCH) for retransmission is received from the base station.

4. The method according to claim 1, wherein Downlink data is received based on the PDCCH received from the base station.

5. A method performed by a base station in a wireless communication system, the method comprising: Sending configuration information for network discontinuous reception (NW DRX) to the terminal; Sending downlink data to the terminal; as well as By temporarily resuming reception during the duration of NW DRX, hybrid automatic repeat request (HARQ) information of downlink data is received from the terminal in a timing of HARQ information overlapping with the duration of NW DRX.

6. The method according to claim 5, wherein: A DRX HARQ round trip time timer (drx-HARQ-RTT-TimerDL) for a downlink corresponding to the HARQ process is started in the first symbol after reception of HARQ information is completed.

7. The method according to claim 5, wherein: Downlink data is transmitted based on the Physical Downlink Control Channel (PDCCH) sent to the terminal. When drx-HARQ-RTT-TimerDL expires, the DRX retransmission timer (drx-RetransmissionTimerDL) of the downlink corresponding to the HARQ process is started in the first symbol after the expiration of drx-HARQ-RTT-TimerDL, and The method further comprises: When drx-RetransmissionTimerDL is running, a Physical Downlink Control Channel (PDCCH) for retransmission is sent to the terminal.

8. A terminal in a wireless communication system, the terminal comprising: transceiver; as well as A controller is coupled to the transceiver and is configured to: Receive configuration information for network discontinuous reception (NW DRX) from the base station, Receive downlink data from the base station, The timing of identifying the hybrid automatic repeat request (HARQ) information for downlink data overlaps with the duration of NW DRX, and At a timing overlapping with the NW DRX duration, HARQ information of downlink data is transmitted to the base station.

9. The terminal according to claim 8, wherein: The controller is also configured to: In the first symbol after the transmission of the HARQ information is completed, a DRX HARQ round trip time timer (drx-HARQ-RTT-TimerDL) for the downlink of the corresponding HARQ process is started.

10. The terminal according to claim 9, wherein: The controller is also configured to: When drx-HARQ-RTT-TimerDL expires, the DRX retransmission timer (drx-RetransmissionTimerDL) of the downlink corresponding to the HARQ process is started in the first symbol after the expiration of drx-HARQ-RTT-TimerDL, and While drx-RetransmissionTimerDL is running, a Physical Downlink Control Channel (PDCCH) for retransmission is received from the base station. The terminal according to claim 8 , wherein: Downlink data is received based on the PDCCH received from the base station.

12. A base station in a wireless communication system, the base station comprising: transceiver; as well as A controller is coupled to the transceiver and is configured to: Sends configuration information for network discontinuous reception (NW DRX) to the terminal, Send downlink data to the terminal, and By temporarily resuming reception during the duration of NW DRX, hybrid automatic repeat request (HARQ) information of downlink data is received from the terminal in a timing of HARQ information overlapping with the duration of NW DRX.

13. The base station according to claim 12, wherein: A DRX HARQ round trip time timer (drx-HARQ-RTT-TimerDL) for a downlink corresponding to the HARQ process is started in the first symbol after reception of HARQ information is completed.

14. The base station according to claim 13, wherein: When drx-HARQ-RTT-TimerDL expires, the DRX retransmission timer (drx-RetransmissionTimerDL) of the downlink of the corresponding HARQ process is started in the first symbol after the expiration of drx-HARQ-RTT-TimerDL, and The controller is further configured as follows: When drx-RetransmissionTimerDL is running, a Physical Downlink Control Channel (PDCCH) for retransmission is sent to the terminal.

15. The base station according to claim 12, wherein: Downlink data is transmitted based on the PDCCH transmitted to the terminal.

Images