DCI for cell DTX / DRX configuration and cell shutdown

Abstract

Various aspects of the present disclosure relate to receiving (802) a cell discontinuous transmission and / or reception (DTX / DRX) configuration for a plurality of serving cells. Aspects of the present disclosure may involve receiving (804) a downlink control information (DCI) signal for at least a serving cell corresponding to the cell DTX / DRX configuration, wherein the DCI further includes an indication of cell shutdown. Aspects of the disclosure may further involve performing (806) a cell search based at least in part on the cell shutdown and the cell DTX / DRX configuration.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically to enhanced downlink control information (DCI) for indicating joint cell discontinuous transmission and / or discontinuous reception (DTX / DRX) and indicating whether a cell is being shut down. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may also be referred to as evolved NodeB (eNodeB), next-generation NodeB (gNB), or other suitable terms. For example, each network communication device of a base station may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system may support wireless communication across various radio access technologies, including third-generation (3G) radio access technology (RAT), fourth-generation (4G) RAT, fifth-generation (5G) RAT, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)). Summary of the Invention

[0003] The article “a” preceding an element is not limited and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, the word “or,” as used in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”), indicates an inclusive list such that a list of at least one of, for example, A, B, or C, means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, without departing from the scope of this disclosure, an example step described as “based on condition A” may be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, the term “set” may comprise one or more elements.

[0004] Some embodiments of the methods and apparatus described herein may include components for receiving cell discontinuous transmission and / or discontinuous reception (DTX / DRX) configurations of multiple serving cells from a network entity. The methods and apparatus described herein may include components for receiving DCI signals for serving cells corresponding at least to cell DTX / DRX configurations, wherein the DCI signals further include an indication of cell shutdown. The methods and apparatus described herein may include components for performing cell search at least in part based on cell shutdown and cell DTX / DRX configurations.

[0005] In some implementations, the methods and apparatus described herein may further include components for transmitting cell DTX / DRX configurations of multiple serving cells to the UE. The methods and apparatus described herein may include components for transmitting DCI signals for serving cells corresponding at least to the cell DTX / DRX configurations, wherein the DCI signals further include an indication of cell shutdown. The methods and apparatus described herein may include components for deactivating serving cells at least in part based on cell shutdown and cell DTX / DRX configurations. Attached Figure Description

[0006] Figure 1 Examples of wireless communication systems according to aspects of this disclosure are described.

[0007] Figure 2 Examples of protocol stacks for wireless communication based on aspects of this disclosure are described.

[0008] Figure 3A This describes an instance of the abstract syntax mark 1 (ASN.1) representing the Discontinuous Reception (DRX) configuration information element (IE) according to aspects of this disclosure.

[0009] Figure 3B yes Figure 3A The DRX configuration is a continuation of IE.

[0010] Figure 4 This describes an example of an ASN.1 representation of a cell DTX / DRX configuration IE according to aspects of this disclosure.

[0011] Figure 5 An example of a user equipment (UE) 500 according to aspects of this disclosure is described.

[0012] Figure 6 An example of processor 600 according to aspects of this disclosure is described.

[0013] Figure 7 An example of a network equipment (NE) 700 according to aspects of this disclosure is described.

[0014] Figure 8A flowchart illustrating the method performed by the UE according to aspects of this disclosure.

[0015] Figure 9 A flowchart illustrating the method performed by NE according to aspects of this disclosure. Detailed Implementation

[0016] Generally, this disclosure describes systems, methods, and apparatuses for cell measurement and access network energy-saving cells. In some embodiments, computer-executable code embedded in a computer-readable medium may be used to perform the methods. In some embodiments, the apparatus or system may include a computer-readable medium containing computer-readable code that, when executed by a processor, causes the apparatus or system to perform at least a portion of the solutions described below.

[0017] One of the fundamental challenges for more efficient network implementations in 5G NR is energy consumption. While user-side devices are often seen as the primary target for further energy savings, the need to further reduce network-side energy consumption is gaining more attention due to higher operating costs and the lack of ubiquitous energy supply from renewable energy sources. Renewable energy is being more widely implemented due to environmental regulations and corporate initiatives to reduce carbon emissions.

[0018] One way to achieve such network energy saving is through Discontinuous Transmission (DTX) and / or Discontinuous Reception (DRX), whereby, for energy saving, the cell suspends the transmission and / or reception of a set of selected signals / channels for a configured period of time. Obviously, a drawback of cell DTX and / or DRX is the degraded network performance due to the cell's inactivity during the cell DTX and / or DRX inactive periods.

[0019] To address the network power consumption issues discussed herein, this disclosure describes techniques for joint Layer 1 (L1) triggering of cell DTX and / or cell DRX and for instructing cell shutdown to UE groups. Advantageously, the cell shutdown instruction allows UE groups to proactively search for another cell, thereby avoiding service interruptions from cell shutdown. More specifically, this disclosure describes enhanced cell DTX / DRX configurations that implement the following solutions:

[0020] According to the first solution, the enhanced cell DTX / DRX configuration enables an enhanced physical downlink control channel (PDCCH) with a DCI format that supports joint L1 triggering for cell DTX / DRX and cell shutdown, wherein the DCI field in the PDCCH transmission is based at least on the higher layer configuration of cell DTX / DRX, and the higher layer configuration for cell shutdown is enabled or disabled.

[0021] According to an aspect of the second solution, the enhanced cell DTX / DRX configuration enables priority rules for the applicability of the cell shutdown indicator relative to the cell DTX / DRX indicator in the DCI, wherein if cell shutdown is triggered, the cell shutdown indicator overrides the cell DTX / DRX indicator.

[0022] According to the third solution, the enhanced cell DTX / DRX configuration enables a defined application time T for cell shutdown. AP Where, in T relative to the time of receiving DCI AP Cell shutdown is applied after a certain number of time units (e.g., time slots or ms).

[0023] The aspects of this disclosure are described in the context of wireless communication systems. It should be noted that one or more aspects from different solutions may be combined.

[0024] Figure 1 This section describes an example of a wireless communication system 100 according to aspects of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an LTE-A network. In some other embodiments, the wireless communication system 100 may be a New Radio (NR) network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0025] One or more NEs 102 may be distributed across a geographical area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receiving signaling, transmitting signaling) via a Uu interface.

[0026] NE 102 can provide a geographic coverage area within which it can support services for one or more UEs 104. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some embodiments, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas associated with the same or different radio access technologies may overlap, but different geographic coverage areas may be associated with different NEs 102.

[0027] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, and other instances thereof.

[0028] UE 104 may be able to support direct wireless communication with other UE 104 via a communication link. For example, UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0029] NE 102 may support communication with CN 106 or with another NE 102 or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate with each other or indirectly (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmitting entities (which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs)).

[0030] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route or interconnect packets to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions of one or more UEs 104 served by one or more NEs 102 associated with CN 106, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.).

[0031] CN 106 can communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session with CN 106 via NE 102 (e.g., a Protocol Data Unit (PDU) session or a PDN connection, etc.). CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0032] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 may support different resource structures. For example, NE 102 and UE 104 may support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 may support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 may support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 may support various frame structures based on one or more parameter sets.

[0033] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some embodiments, the first parameter set (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.

[0034] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0035] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may contain a certain number (e.g., quantity) of symbols (e.g., Orthogonal Frequency Domain Multiplexing (OFDM) symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot for the regular cyclic prefix and the extended cyclic prefix, the number of time slots per subframe, and the number of time slots per frame may depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.

[0036] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 may support one or more operating frequency bands, such as frequency range names FR1 (410MHz to 7.125GHz), FR2 (24.25GHz to 52.6GHz), FR3 (7.125GHz to 24.25GHz), FR4 (52.6GHz to 114.25GHz), FR4a or FR4-1 (52.6GHz to 71GHz), and FR5 (114.25GHz to 300GHz). In some embodiments, NE 102 and UE 104 may perform wireless communication on one or more of the operating frequency bands. In some embodiments, FR1 may be used by NE 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.

[0037] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set containing a 15 kHz subcarrier spacing (e.g., μ = 0); a second parameter set containing a 30 kHz subcarrier spacing (e.g., μ = 1); and a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ = 2). FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ = 2); and a fourth parameter set containing a 120 kHz subcarrier spacing (e.g., μ = 3).

[0038] Wireless communication in unlicensed spectrum (also known as “shared spectrum”) offers several significant cost advantages compared to licensed spectrum, allowing communication to avoid covering the licensed spectrum of operators and instead use unlicensed spectrum based on local regulations in a specific geographic location. From a 3GPP (3rd Generation Partnership Project) technical perspective, unlicensed operation can occur on the Uu interface (referred to as NR-U) or on a sidelink interface (e.g., SL-U).

[0039] For initial access, UE 104 detects candidate cells and performs downlink (DL) synchronization. For example, a gNB (e.g., an embodiment of NE 102) may transmit a synchronization signal called a Synchronization Signal Block (SSB) and a broadcast channel (SS / PBCH). The synchronization signal is a predefined data sequence known to UE 104 (or derived using information already stored at UE 104) and is positioned at a predefined time location relative to frame / subframe boundaries, etc. UE 104 searches for SSBs and uses them to obtain DL timing information (e.g., symbol timing) for DL ​​synchronization. UE 104 may also decode System Information (SI) based on SSBs. It should be noted that for beam-based communication, each DL beam may be associated with a corresponding SSB.

[0040] After performing DL synchronization and acquiring basic system information (such as the Master Information Block (MIB) and System Information Block Type 1 (SIB1)), UE 104 performs uplink (UL) synchronization and resource requests by performing a random access procedure known as the "RACH procedure" by selecting and transmitting a preamble on the Physical Random Access Channel (PRACH). The PRACH preamble is transmitted during the RACH timing (i.e., a predetermined set of time-frequency resources available for receiving the PRACH preamble). It should be noted that for beam-based communication, UE 104 may select a specific DL beam and transmit the PRACH preamble on the corresponding UL beam. In such embodiments, a mapping between SSBs and RACH timings may exist, allowing the network to determine which beam UE 104 has selected.

[0041] To complete the RACH process, after transmitting the PRACH preamble (also known as "Msg1"), the UE 104 monitors the Random Access Response (RAR) message (also known as "Msg2"). The gNB transmits UL timing adjustment information in the RAR and can also schedule UL resources known as the initial uplink grant.

[0042] In 3GPP New Radio (NR), a gNB can transmit up to 64 SSBs and up to 64 corresponding copies of the Physical Downlink Control Channel (PDCCH) and / or Physical Downlink Shared Channel (PDSCH) for SIB1 delivery in high-frequency bands (e.g., 28 GHz). Even under very low traffic load conditions, this can lead to significant network power consumption. According to 3GPP Technical Report (TR) 38.864 (v18.1.0), for network power saving, on-demand SSB and / or SIB1 (SSB / SIB1) transmission and cells without SSB / SIB1 transmission should be considered. When a cell does not transmit SSB / SIB1, for a UE to access that cell, the UE should obtain the SI of that cell from other associated carriers / cells and synchronize from those other associated carriers / cells. When a cell is inactive for an extended period, a UE served by that cell can trigger SSB / SIB1 transmission by sending a request to that cell.

[0043] Figure 2 An example of a protocol stack 200 according to aspects of this disclosure is described. In some embodiments, the protocol stack 200 may be an NR protocol stack. Although Figure 2 The illustration shows UE 206, RAN node 208, and 5G core network (5GC) 210 (e.g., including at least AMF), but these represent a group of UEs 104 interacting with NE 102 (e.g., a base station) and CN 106. As depicted, protocol stack 200 includes user plane protocol stack 202 and control plane protocol stack 204. User plane protocol stack 202 includes PHY layer 212, MAC sublayer 214, Radio Link Control (RLC) sublayer 216, Packet Data Convergence Protocol (PDCP) sublayer 218, and Serving Data Adaptation Protocol (SDAP) sublayer 220. Control plane protocol stack 204 includes PHY layer 212, MAC sublayer 214, RLC sublayer 216, and PDCP sublayer 218. Control plane protocol stack 204 also includes Radio Resource Control (RRC) layer 222 and Non-Access Plane (NAS) layer 224.

[0044] The AS layer 226 (also referred to as the "AS protocol stack") of the user plane protocol stack 202 consists of at least SDAP, PDCP, RLC, and MAC sublayers and a physical layer. The AS layer 228 of the control plane protocol stack 204 consists of at least RRC, PDCP, RLC, and MAC sublayers and a physical layer. Layer 1 (L1) contains the PHY layer 212. Layer 2 (L2) is divided into the SDAP sublayer 220, PDCP sublayer 218, RLC sublayer 216, and MAC sublayer 214. Layer 3 (L3) contains the RRC layer 222 and NAS layer 224 for the control plane, and includes, for example, the Internet Protocol (IP) layer and / or PDU layer (not depicted) for the user plane. L1 and L2 are referred to as "lower layers," while L3 and above (e.g., transport layer, application layer) are referred to as "higher layers" or "upper layers."

[0045] PHY layer 212 provides a transport channel to MAC sublayer 214. PHY layer 212 can perform beam failure detection procedures using energy detection thresholds, as described herein. In some embodiments, PHY layer 212 can send a beam failure indication to the MAC entity at MAC sublayer 214. MAC sublayer 214 provides a logical channel to RLC sublayer 216. RLC sublayer 216 provides an RLC channel to PDCP sublayer 218. PDCP sublayer 218 provides radio bearers to SDAP sublayer 220 and / or RRC layer 222. SDAP sublayer 220 provides QoS flows to the core network (e.g., 5GC). RRC layer 222 provides the addition, modification, and release of carrier aggregation and / or dual connectivity. RRC layer 222 also manages the establishment, configuration, maintenance, and release of SRBs and data radio bearers (DRBs).

[0046] NAS layer 224 is located between UE 206 and the AMF in 5GC 210. NAS messages are transparently transmitted through the RAN. NAS layer 224 is used to manage the establishment of communication sessions and to maintain continuous communication with UE 206 when UE 206 moves between different cells in the RAN. In contrast, AS layers 226 and 228 are located between UE 206 and the RAN (i.e., RAN node 208) and carry information through the radio portion of the network. Although in Figure 2 It is not described in the text, but the IP layer exists above the NAS layer 224, the transport layer exists above the IP layer, and the application layer exists above the transport layer.

[0047] MAC sublayer 214 is the lowest sublayer in the L2 architecture of the NR protocol stack. Its connection to the PHY layer 212 below is via the transport channel, and its connection to the RLC sublayer 216 above is via the logical channel. Therefore, MAC sublayer 214 performs multiplexing and demultiplexing between the logical and transport channels: on the transmitting side, MAC sublayer 214 constructs a MAC PDU (also known as a transport block (TB)) from the MAC Service Data Unit (SDU) received via the logical channel, and on the receiving side, MAC sublayer 214 recovers the MAC SDU from the MAC PDU received via the transport channel.

[0048] In the radio protocol architecture described herein, the term "SDU" refers to a data unit received by a sublayer from a higher sublayer or transmitted by a sublayer to a higher sublayer. Similarly, the term "PDU" refers to a data unit transmitted by a sublayer to a lower sublayer or received by a sublayer from a lower sublayer.

[0049] MAC sublayer 214 provides data transmission services to RLC sublayer 216 via logical channels, which are either control logical channels carrying control data (e.g., RRC signaling) or service logical channels carrying user plane data. On the other hand, data from MAC sublayer 214 is exchanged with PHY layer 212 via transport channels classified as UL or DL. The data is multiplexed into the transport channels depending on how it is transmitted in the air.

[0050] PHY layer 212 is responsible for the actual transmission of data and control information via the air interface; that is, PHY layer 212 carries all information from the MAC transport channel through the air interface on the transmitting side. Some important functions performed by PHY layer 212 include coding and modulation, link adaptation (e.g., Adaptive Modulation and Coding (AMC)), power control, cell search and random access (for initial synchronization and handover purposes), and other measurements of RRC layer 221 (within 3GPP systems (i.e., NR and / or LTE systems) and between systems). PHY layer 212 performs transmission based on transmission parameters such as modulation scheme, coding rate (i.e., modulation and coding scheme (MCS)), and the number of physical resource blocks (PRBs).

[0051] In some embodiments, protocol stack 200 may be the NR protocol stack used in a 5G NR system. It should be noted that LTE implementations of protocol stack 200 may include a structure similar to the NR protocol stack, the difference being that the LTE protocol stack lacks the SDAP sublayer 220 in AS layer 226, EPC replaces 5GC 510, and NAS layer 224 is located between the UE 206 and the MME in the EPC. It should also be noted that this disclosure distinguishes between protocol layers (e.g., the aforementioned PHY layer 212, MAC sublayer 214, RLC sublayer 216, PDCP sublayer 218, SDAP sublayer 220, RRC layer 222, and NAS layer 224) and the transmit layer (also referred to as the "MIMO layer" or "data stream") in multiple-input multiple-output (MIMO) communication.

[0052] Cell DTX (Discontinuous Transmit) and DRX (Discontinuous Receive) are mechanisms in 3GPP cellular networks used to save power and optimize network resource usage. For network energy conservation, cell DTX can be used to reduce the power consumption of a base station (e.g., gNB) by turning off the transmitter when there is no user data to transmit. Similarly, cell DRX can be used to reduce the power consumption of a base station by entering a low-power state, in which the receiver is partially or completely turned off for a specific time interval, i.e., when no UL (Ultra-Low) transmissions are expected to be received from the UE.

[0053] Regarding the cell DTX / DRX framework, the current 3GPP framework supports cell DTX / DRX operation through two modes: Mode 1 and Mode 2. In Mode 1, the network uses RRC configuration and activation for cell DTX / DRX, with separate development signal notification configuration and activation. In Mode 2, the network uses RRC configuration for cell DTX / DRX with L1 activation via a PDCCH corresponding to DCI format 2_9, which only corresponds to cell DTX / DRX and does not include cell shutdown triggering. However, a drawback of the conventional cell DTX / DRX framework is that it does not include cell shutdown configuration and / or activation in traditional designs.

[0054] Regarding the Conditional Handover (CHO) procedure, if no cell shutdown is indicated to the UE and a set of candidate cells exists for conditional handover, the UE will conditionally hand over to one of the candidate cells if the CHO metric set meets a threshold. However, a drawback of the conventional CHO procedure is that handover only occurs after the performance metric value drops beyond the threshold, rather than being network-triggered due to the anticipated shutdown of a cell.

[0055] Regarding the Radio Link Failure (RLF) procedure, if the serving cell is not indicated to the UE as disabled, and if there is no candidate cell in the CHO set, the RLF procedure is performed to establish a connection with a new cell. However, a drawback of the conventional RLF procedure is that establishing a connection with a new cell after the RLF causes a large delay.

[0056] Regarding DRX connected to the UE, the UE's MAC entity can be configured with DRX functionality via RRC. This DRX functionality controls the UE's cell radio network temporary identifier (C-RNTI), cancellation indication radio network temporary identifier (CI-RNTI), configured scheduling radio network temporary identifier (CS-RNTI), interruption / preemption radio network temporary identifier (INT-RNTI), slot format indicator radio network temporary identifier (SFI-RNTI), semi-persistent channel state information radio network temporary identifier (SP-CSI-RNTI), transmit power control physical uplink control channel absence, etc., for the MAC entity. PDCCH monitoring activities for Transmit Power Control Physical Uplink Shared Channel Radio Network Temporary Identifier (TPC-PUCCH-RNTI), Transmit Power Control Sounding Reference Signal Radio Network Temporary Identifier (TPC-SRS-RNTI), Availability Indication Scheduling Radio Network Temporary Identifier (AI-RNTI), Sidelink Radio Network Temporary Identifier (SL-RNTI), Sidelink Configured Scheduling Radio Network Temporary Identifier (SLCS-RNTI), and Sidelink (SL) Semi-Persistent Scheduling Variable Radio Network Temporary Identifier (V-RNTI).

[0057] When using DRX operation, the MAC entity shall also monitor the PDCCH as required in other clauses of this specification. When in the RRC_CONNECTED state, if DRX is configured, the MAC entity may use DRX operation to monitor the PDCCH discontinuously for all active serving cells. Otherwise, the MAC entity will monitor the PDCCH (e.g., as specified in 3GPP Technical Specification (TS) 38.213).

[0058] RRC controls DRX operation by configuring one or more of the following parameters: A) drx-onDurationTimer: the duration at the start of the DRX cycle; B) drx-SlotOffset: the delay before starting drx-onDurationTimer; C) drx-InactivityTimer: the duration after the PDCCH timing, where the PDCCH indicates a new UL, DL, or SL transmission for the MAC entity; D) drx-RetransmissionTimerDL (per DL HARQ procedure except for broadcast procedures): the maximum duration until a DL retransmission is received; E) drx-RetransmissionTimerUL (per UL... HARQ procedure): The maximum duration until an authorization for UL retransmission is received; F) drx-LongCycleStartOffset: The drx-StartOffset of the long DRX cycle and the subframe that defines the start of the long and short DRX cycles; G) ddrx-ShortCycle (optional): The short DRX cycle; H) drx-ShortCycleTimer (optional): The duration for which the UE should follow the short DRX cycle; I) drx-HARQ-RTT-TimerDL (per DL HARQ procedure except broadcast procedure): The minimum duration before the DL assignment for HARQ retransmission is expected by the MAC entity; J) drx-HARQ-RTT-TimerUL (per UL HARQ procedure): The minimum duration before the UL HARQ retransmission authorization is expected by the MAC entity; K) drx-RetransmissionTimerSL (per SL HARQ procedure): The maximum duration until an authorization for SL retransmission is received; L) drx-HARQ-RTT-TimerSL (per SL HARQ procedure): The maximum duration until an authorization for SL retransmission is received; HARQ procedure): Minimum duration before the expected SL retransmission authorization by the MAC entity; M) ps-Wakeup (optional): Configuration to initiate the associated drx-onDurationTimer if the DCP is monitored but not detected; N) ps-TransmitOtherPeriodicCSI (optional): Configuration to report periodic channel state information (CSI) that is not L1-RSRP on the Physical Uplink Control Channel (PUCCH) during the duration indicated by drx-onDurationTimer, if the DCP is configured but the associated drx-onDurationTimer is not initiated.(O)ps-TransmitPeriodicL1-RSRP (Optional): Configuration to transmit periodic CSI as L1-RSRP on the PUCCH for the duration indicated by drx-onDurationTimer during the period when DCP is configured but the associated drx-onDurationTimer is not started; (P)downlinkHARQ-FeedbackDisabled (Optional): Configuration to disable HARQ feedback per DL HARQ procedure; (Q)uplinkHARQ-Mode (Optional): Configuration to set HARQmodeA or HARQmodeB per UL HARQ procedure; or a combination thereof.

[0059] The serving cell of a MAC entity can be configured by RRC into two DRX groups with separate DRX parameters. When no secondary DRX group is configured by RRC, there is only one DRX group, and all serving cells belong to this single 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 and drx-InactivityTimer. The DRX parameters common to all DRX groups are: drx-SlotOffset, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, drx-LongCycleStartOffset, drx-ShortCycle (optional), drx-ShortCycleTimer (optional), drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL.

[0060] When DRX is configured, the active time of a serving cell in a DRX group includes the following times: A) when the drx-onDurationTimer or drx-InactivityTimer configured for the DRX group is running; or B) when the drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, or drx-RetransmissionTimerSL is running on any serving cell in the DRX group; or C) when the ra-ContentionResolutionTimer or msgB-ResponseWindow is running; or D) when a scheduling request (SR) is sent on the PUCCH and pending (if the serving cell is part of a non-terrestrial network, the active time begins after the SR transmission, which is performed when SR_COUNTER is 0 for all SR configurations with pending SRs plus UE-gNB round-trip time (RTT); or E) when a new transmission of a C-RNTI indicating addressing to a MAC entity has not been received after a successful reception of a random access response to a random access preamble not selected by the MAC entity in a contention-based random access preamble.

[0061] The following MAC timers are used for DRX operations in non-terrestrial networks: A) HARQ-RTT-TimerDL-NTN (per DL Hybrid Automatic Repeat Request (HARQ) procedure configured with HARQ feedback enabled): the minimum duration expected by the MAC entity before a DL assignment for HARQ retransmission; and B) HARQ-RTT-TimerUL-NTN (per UL HARQ procedure configured with HARQModeA): the minimum duration expected by the MAC entity before a UL HARQ retransmission authorization.

[0062] When the DRX is not configured and the multicast DRX is configured for Group Radio Network Temporary Identifier (G-RNTI) or Group CS-RNTI (G-CS-RNTI), the MAC entity should monitor the PDCCH (e.g., as specified in 3GPP TS 38.213). If a MAC PDU is received in a configured downlink assignment for unicast; or if the PDCCH indicates DL unicast transmission, then the MAC entity stops the drx-RetransmissionTimer DL-PTM corresponding to the HARQ procedure.

[0063] When DRX is configured, if a MAC PDU is received in a configured downlink assignment for unicast, and if the serving cell is configured with downlinkHARQ-FeedbackDisabled and the corresponding HARQ procedure is configured with HARQ feedback enabled, then the MAC entity should set the HARQ-RTT-TimerDL-NTN of the corresponding HARQ procedure to be equal to drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value, and start the HARQ-RTT-TimerDL-NTN of the corresponding HARQ procedure in the first symbol after the corresponding transmission carrying the DL HARQ feedback ends.

[0064] Otherwise, if a MAC PDU is received in a configured downlink assignment for unicast, but the serving cell is not configured with downlinkHARQ-FeedbackDisabled, the MAC entity should start the corresponding HARQ procedure's drx-HARQ-RTT-TimerDL in the first symbol after the corresponding transmission carrying the DL HARQ feedback has ended. When a MAC PDU is received in a configured downlink assignment for unicast, the MAC entity further stops the corresponding HARQ procedure's timer drx-RetransmissionTimerDL and the corresponding HARQ procedure's timer drx-RetransmissionTimerDL-PTM.

[0065] When DRX is configured, if a MAC PDU is transmitted in a configured uplink grant and does not receive an LBT failure indication from the lower layer, then if the serving cell is configured with uplinkHARQ-Mode and if the corresponding HARQ procedure is configured with HARQModeA, then the MAC entity should set the HARQ-RTT-TimerUL-NTN of the corresponding HARQ procedure to be equal to drx-HARQ-RTT-TimerUL plus the latest available UE-gNB RTT value.

[0066] Furthermore, if drx-LastTransmissionUL is configured, the MAC entity should start the HARQ-RTT-TimerUL-NTN for the corresponding HARQ procedure in the first symbol after the last transmission (within the bundle) of the corresponding PUSCH transmission. Otherwise, if a MAC PDU is transmitted in a configured uplink grant and no LBT failure indication is received from the lower layer, but the serving cell is not configured with uplinkHARQ-Mode, then if drx-LastTransmissionUL is not configured, the MAC entity should start the timer HARQ-RTT-TimerUL-NTN for the corresponding HARQ procedure in the first symbol after the first transmission (within the bundle) of the corresponding PUSCH transmission.

[0067] Otherwise, if a MAC PDU is transmitted in a configured uplink grant and no LBT failure indication is received from the lower layer, but the serving cell is not configured with uplinkHARQ-Mode, then if drx-LastTransmissionUL is configured, the MAC entity will initiate drx-HARQ-RTT-TimerUL for the corresponding HARQ procedure in the first symbol after the last transmission (within the bundle) of the corresponding PUSCH transmission. However, if drx-LastTransmissionUL is not configured, the MAC entity should initiate drx-HARQ-RTT-TimerUL for the corresponding HARQ procedure in the first symbol after the first transmission (within the bundle) of the corresponding PUSCH transmission.

[0068] Furthermore, when DRX is configured and MAC PDU is transmitted in configured uplink grant and no LBT failure indication is received from the lower layer, the MAC entity should stop the corresponding HARQ procedure's drx-RetransmissionTimerUL at the first transmission (within the bundle) of the corresponding PUSCH transmission.

[0069] When DRX is configured, if a MAC PDU is transmitted in a configured sidelink grant, and if PUCCH resources are configured, the MAC entity should initiate the drx-HARQ-RTT-TimerSL for the corresponding HARQ procedure in the first symbol after the completion of the transmission of the corresponding PUCCH carrying SL HARQ feedback; or, if no PUCCH is transmitted, initiate the corresponding HARQ procedure in the first symbol after the completion of the transmission of the corresponding PUCCH resource carrying SL HARQ feedback. The MAC entity should further stop the drx-RetransmissionTimerSL for the corresponding HARQ procedure.

[0070] Otherwise, if the PUCCH resource is not configured, the MAC entity should start the corresponding HARQ procedure's drx-HARQ-RTT-TimerSL at the first symbol after the corresponding PSSCH transmission ends, and should stop the corresponding HARQ procedure's drx-RetransmissionTimerSL.

[0071] When DRX is configured, if the drx-HARQ-RTT-TimerDL expires and the data for the corresponding HARQ procedure is not successfully decoded, the MAC entity should start the drx-RetransmissionTimerDL for the corresponding HARQ procedure in the first symbol after the drx-HARQ-RTT-TimerDL expires.

[0072] When DRX is configured, if HARQ-RTT-TimerDL-NTN expires and the data for the corresponding HARQ procedure is not successfully decoded, the MAC entity should start drx-RetransmissionTimerDL for the corresponding HARQ procedure in the first symbol after HARQ-RTT-TimerDL-NTN expires.

[0073] When DRX is configured, if drx-HARQ-RTT-TimerUL expires, the MAC entity should start the corresponding HARQ procedure's drx-RetransmissionTimerUL in the first symbol after drx-HARQ-RTT-TimerUL expires.

[0074] When DRX is configured, if HARQ-RTT-TimerUL-NTN expires, the MAC entity should start the corresponding HARQ procedure drx-RetransmissionTimerUL in the first symbol after HARQ-RTT-TimerUL-NTN expires.

[0075] When DRX is configured, if drx-HARQ-RTT-TimerSL expires, then if a HARQ NACK feedback for the corresponding HARQ procedure is transmitted on the PUCCH, or if a HARQ NACK feedback for the corresponding HARQ procedure is generated but not transmitted on the PUCCH, or if PUCCH resources are not configured for SL granting, then the MAC entity should initiate drx-RetransmissionTimerSL for the corresponding HARQ procedure in the first symbol after drx-HARQ-RTT-TimerSL expires. It should be noted that when sl-PUCCH-Config is configured by RRC, the UE handles the drx-RetransmissionTimerSL operation, but the PUCCH resources are scheduled differently than when sl-PUCCH-Config is not configured.

[0076] When DRX is configured, if a PDCCH indication addressed to C-RNTI or CS-RNTI is received, or a DRX command MAC CE or long DRX command MAC CE indicated by a configured downlink assignment for unicast transmission is received, then the MAC entity should stop the drx-onDurationTimer for each DRX group; and should stop the drx-InactivityTimer for each DRX group.

[0077] When DRX is configured, if the drx-InactivityTimer of a DRX group expires, and if a short DRX cycle is configured, the MAC entity should start or restart the drx-ShortCycleTimer for this DRX group in the first symbol after the drx-InactivityTimer expires, and should use a short DRX cycle for this DRX group. Otherwise, if the drx-InactivityTimer of a DRX group expires but a short DRX cycle is not configured, the MAC entity should use a long DRX cycle for this DRX group.

[0078] When DRX is configured, if a DRX command MAC CE is received, indicated by a PDCCH addressing to a C-RNTI or CS-RNTI, or by a configured downlink assignment for unicast transmission, then if a short DRX cycle is configured, the MAC entity should start or restart the drx-ShortCycleTimer for each DRX group in the first symbol after the DRX command MAC CE is received; and a short DRX cycle should be used for each DRX group. Otherwise, if a DRX command MAC CE is received, indicated by a PDCCH addressing to a C-RNTI or CS-RNTI, or by a configured downlink assignment for unicast transmission, but a short DRX cycle is not configured, then the MAC entity should use a long DRX cycle for each DRX group.

[0079] When DRX is configured, if the drx-ShortCycleTimer of a DRX group expires, the MAC entity should use a long DRX cycle for this DRX group.

[0080] When DRX is configured, if a long DRX command MAC CE is received, the MAC entity should stop the drx-ShortCycleTimer for each DRX group and use a long DRX cycle for each DRX group.

[0081] When DRX is configured, if a short DRX cycle is used for a DRX group, and [(SFN×10)+subframe number] modulo (drx-ShortCycle) = (drx-StartOffset) modulo (drx-ShortCycle), then the MAC entity should start the drx-onDurationTimer for this DRX group after drx-SlotOffset starting from the subframe.

[0082] When DRX is configured, if a long DRX cycle is used for a DRX group, and [(SFN×10)+subframe number] modulo (drx-LongCycle) = drx-StartOffset, then if DCP monitoring is configured for an active DL BWP (e.g., as specified in 3GPP TS 38.213), and if A) a DCP indication received from the lower layer associated with the current DRX cycle indicates the start of a drx-onDurationTimer (e.g., as specified in 3GPP TS 38.213); or B) considering that the authorization / assignment / DRX command MAC CE / long DRX command MAC CE and the scheduling request sent are received during the active time period when monitoring PDCCH transmissions in the search space indicated by the recoverySearchSpaceId of the special cell (SpCell) identified by C-RNTI while the MAC entity is running the ra-ResponseWindow, the DCP indication received during the active time period associated with the current DRX cycle is as specified in 3GPP TS 38.213; or if the DCP indication received during the active time period ... All DCP timings in the time domain specified in 38.213; or if ps-Wakeup is configured to true and has not yet received a DCP indication associated with the current DRX cycle from the lower layer, then the MAC entity should start drx-onDurationTimer after drx-SlotOffset starting from the subframe.

[0083] Otherwise, if a long DRX cycle is used for a DRX group, and [(SFN×10)+subframe number] modulo (drx-LongCycle) = drx-StartOffset, but DCP monitoring is not configured for the active DL BWP, then the MAC entity should start the drx-onDurationTimer for this DRX group after the drx-SlotOffset starting from the subframe. Note that for the case of misaligned SFNs spanning carriers within a cell group, the SFN of the SpCell is used to calculate the DRX duration.

[0084] When DRX is configured, if the DRX group is active, the MAC entity should monitor the PDCCH on the serving cell in this DRX group, as specified in 3GPP TS 38.213. If the PDCCH indicates a DL transmission; or if the PDCCH indicates a single HARQ feedback (e.g., as specified in 3GPP TS 38.213); or if the PDCCH indicates a retransmission of HARQ feedback (e.g., as specified in 3GPP TS 38.213), then if the serving cell is configured with downlinkHARQ-FeedbackDisabled and if the corresponding HARQ procedure is configured with HARQ feedback enabled, then the MAC entity should set the HARQ-RTT-TimerDL-NTN of the corresponding HARQ procedure to be equal to drx-HARQ-RTT-TimerDL plus the latest available UE-gNB RTT value; and should start the HARQ-RTT-TimerDL-NTN of the corresponding HARQ procedure in the first symbol after the corresponding transmission carrying the DL HARQ feedback has ended.

[0085] However, for the above conditions, if the serving cell is not configured with downlinkHARQ-FeedbackDisabled, the MAC entity should initiate or restart the drx-HARQ-RTT-TimerDL of the corresponding HARQ procedure in the first symbol after the completion of the corresponding transmission carrying the DL HARQ feedback. It should be noted that when the HARQ feedback is delayed at a PDSCH-to-HARQ_feedback timing indicating an inapplicable k1 value (e.g., as specified in 3GPP TS 38.213), the corresponding transmission sending the DL HARQ feedback will be indicated in a later PDCCH requesting HARQ-ACK feedback. As used herein, HARQ-ACK can collectively represent a positive acknowledgment (ACK), a negative acknowledgment (NACK), and a DTX. ACK means the transport block (TB) was correctly received, while NACK (or NAK) means the TB was incorrectly received, and DTX means the TB was not detected.

[0086] When DRX is configured, if the DRX group is active, the MAC entity should monitor the PDCCH on the serving cell in this DRX group, as specified in 3GPP TS 38.213. If the PDCCH indicates a DL transmission; or if the PDCCH indicates a single HARQ feedback (e.g., as specified in 3GPP TS 38.213); or if the PDCCH indicates a retransmission of the HARQ feedback (e.g., as specified in 3GPP TS 38.213), the MAC entity should stop the drx-RetransmissionTimerDL for the corresponding HARQ procedure whose HARQ feedback is reported; and should stop the drx-RetransmissionTimerDL-PTM for the corresponding HARQ procedure. If the PDSCH-to-HARQ_feedback timing indication does not apply to a k1 value (e.g., as specified in 3GPP TS 38.213), then the MAC entity should initiate the drx-RetransmissionTimerDL in the first symbol after the (final) PDSCH transmission (in-bundle) (end) of the corresponding HARQ procedure.

[0087] Additionally, when the DRX group is active, if the PDCCH indicates a UL transmission, and if the serving cell is configured with uplinkHARQ-Mode, and if the corresponding HARQ procedure is configured with HARQModeA, then the MAC entity should set the HARQ-RTT-TimerUL-NTN of the corresponding HARQ procedure to be equal to drx-HARQ-RTT-TimerUL plus the latest available UE-gNB RTT value. Furthermore, if drx-LastTransmissionUL is configured, then the MAC entity should initiate the HARQ-RTT-TimerUL-NTN of the corresponding HARQ procedure in the first symbol after the last transmission (within the bundle) of the corresponding PUSCH transmission. Otherwise, the MAC entity should initiate the HARQ-RTT-TimerUL-NTN of the corresponding HARQ procedure in the first symbol after the first transmission (within the bundle) of the corresponding PUSCH transmission.

[0088] Otherwise, if the PDCCH indicates a UL transmission but the serving cell is not configured with uplinkHARQ-Mode, then if drx-LastTransmissionUL is configured, the MAC entity should initiate drx-HARQ-RTT-TimerUL for the corresponding HARQ procedure in the first symbol after the last transmission (within the bundle) of the corresponding PUSCH transmission; otherwise, the MAC entity should initiate drx-HARQ-RTT-TimerUL for the corresponding HARQ procedure in the first symbol after the first transmission (within the bundle) of the corresponding PUSCH transmission. Furthermore, when the PDCCH indicates a UL transmission, the MAC entity should stop drx-RetransmissionTimerUL for the corresponding HARQ procedure.

[0089] Additionally, when the DRX group is active, if the PDCCH indicates an SL transmission, and if the PUCCH resource is configured, the MAC entity should initiate the drx-HARQ-RTT-TimerSL for the corresponding HARQ procedure in the first symbol after the completion of the corresponding PUCCH transmission carrying SL HARQ feedback; or, if no PUCCH transmission has occurred, it should initiate the drx-HARQ-RTT-TimerSL for the corresponding HARQ procedure in the first symbol after the completion of the corresponding PUCCH resource carrying SL HARQ feedback. The MAC entity should further stop the drx-RetransmissionTimerSL for the corresponding HARQ procedure. Otherwise, if the PDCCH indicates an SL transmission but the PUCCH resource is not configured, the MAC entity should initiate the drx-HARQ-RTT-TimerSL for the corresponding HARQ procedure at the first symbol after the PDCCH timing ends; and should stop the drx-RetransmissionTimerSL for the corresponding HARQ procedure.

[0090] Additionally, when a DRX group is active, if the PDCCH indicates a new transmission (DL, UL, or SL) on the serving cell within this DRX group, the MAC entity should initiate or restart the drx-InactivityTimer for this DRX group in the first symbol after the PDCCH reception ends. It should be noted that PDCCHs indicating SPS activation, configured with authorization type 2, or configured sidelink authorization with configuration authorization type 2 are considered to indicate a new transmission. Further note that if the PDCCH reception contains two PDCCH candidates from corresponding search spaces (e.g., as described in Clause 10.1 of 3GPP TS 38.213), the MAC entity should initiate or restart the drx-InactivityTimer for this DRX group in the first symbol after the later-ending PDCCH candidate ends.

[0091] Additionally, when the DRX group is active, if the HARQ procedure receives downlink feedback and indicates confirmation, the MAC entity should stop the corresponding HARQ procedure's drx-RetransmissionTimerUL.

[0092] When DRX is configured, if power-saving downlink control information (DCP) monitoring is configured for active DL BWP (e.g., as specified in 3GPP TS 38.213); and if the current symbol n occurs within the drx-onDurationTimer duration; and if the drx-onDurationTimer associated with the current DRX cycle is not started, then the MAC entity will not be active if, taking into account the authorization / assignment / DRX command MAC CE / long DRX command MAC CE received up to 4ms before symbol n and the scheduling requests sent when evaluating all DRX active time conditions specified in this clause; and if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or if, taking into account the multicast assignment / DRX command MAC CE received up to 4ms before symbol n for multicast broadcast service (MBS) when evaluating all DRX active time conditions and all multicast sessions are configured for multicast DRX, the MAC entity will not be active if, in addition to the multicast assignment / DRX command MAC CE received up to 4ms before symbol n. CE, if all multicast DRXs are not active, then the MAC entity should not transmit periodic SRS and semi-persistent SRS (e.g., as defined in 3GPP TS 38.214); and should not report semi-persistent CSIs configured on the PUSCH; and if ps-TransmitPeriodicL1-RSRP is not configured to be true, then the MAC entity should not report periodic CSIs as L1-RSRPs on the PUCCH; and if ps-TransmitOtherPeriodicCSI is not configured to be true, then the MAC entity should not report periodic CSIs that are not L1-RSRPs on the PUCCH.

[0093] When DRX is configured but none of the above conditions apply, then in the current symbol n, if the authorization / assignment scheduled on the serving cell in this DRX group during the evaluation of all DRX activity time conditions specified in this clause, as well as the DRX command MAC CE / long DRX command MAC CE received up to 4ms before symbol n and the scheduling requests sent, the DRX group will not be active; and if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or, in the current symbol n, if the multicast assignment / DRX command MAC CE for MBS received up to 4ms before symbol n during the evaluation of all DRX activity time conditions and all multicast sessions corresponding to the DRX group are configured for multicast DRX, all multicast DRX corresponding to the DRX group will not be active, then the MAC entity should not send periodic SRS and semi-persistent SRS as defined in 3GPP TS38.214 in this DRX group; and should not report CSI on PUCCH and semi-persistent CSI configured on PUSCH in this DRX group.

[0094] However, if the CSI mask is set by the upper layer, then in the current symbol n, if the authorization / assignment scheduled on the serving cell in this DRX group when evaluating all DRX activity time conditions specified in this clause, and the DRX command MAC CE / long DRX command MAC CE received up to 4ms before symbol n, the drx-onDurationTimer of the DRX group will not run; and if allowCSI-SRS-Tx-MulticastDRX-Active is not configured, or, in the current symbol n, if the drx-onDurationTimerPTM of all multicast DRXs corresponding to the DRX group will not run when evaluating all DRX activity time conditions and all multicast sessions corresponding to the DRX group are configured for multicast DRX, then the MAC entity should not report CSI on the PUCCH in this DRX group.

[0095] It should be noted that if the UE, according to procedures (e.g., as specified in 3GPP TS 38.213), multiplexes the CSI configured on the PUCCH with other overlapping UCIs, and if the CSI shielding is set by the upper layer, reports this CSI multiplexed with other UCIs on the PUCCH resource outside the DRX activity time of the DRX group in which this PUCCH is configured or outside the on-duration period of the DRX group in which this PUCCH is configured, then it is up to the UE implementation to decide whether to report this CSI multiplexed with other UCIs.

[0096] Regardless of whether the MAC entity is monitoring the PDCCH on the serving cell in the DRX group, when such a situation is anticipated, the MAC entity transmits HARQ feedback, aperiodic CSI on the PUSCH, and aperiodic SRS on the serving cell in the DRX group (e.g., as defined in 3GPP TS 38.214).

[0097] If the PDCCH is not a complete PDCCH event (e.g., the activity time begins or ends in the middle of the PDCCH event), then the MAC entity does not need to monitor the PDCCH.

[0098] Figures 3A to 3B This document describes an exemplary DRX configuration for Internet Explorer based on aspects of this disclosure. Descriptions of the fields for DRX configuration of Internet Explorer are shown in Table 1 below.

[0099]

[0100]

[0101] Table 1: Description of DRX-Config IE Fields

[0102] Regarding Rel-18-based cell DTX / DRX, the following signals / channels are expected to be affected by cell DTX / DRX, for example, by UEs that do not monitor the reception of DL signals / channels or do not transmit UL signals / channels, respectively:

[0103] In some embodiments, the UE does not monitor SPS timings during cell DTX inactivity periods; for example, it is assumed that the gNB does not transmit PDSCH to the UE during such SPS timings during cell DTX inactivity periods. In some embodiments, the UE does not transmit during configured authorization (CG) timings during cell DRX inactivity periods. In some embodiments, the UE does not transmit during SR timings that overlap with cell DRX inactivity periods; for example, SR transmissions are discarded during cell DRX inactivity periods.

[0104] The UE does not anticipate receiving and / or processing the periodic / semi-persistent Channel State Information Reference Signal (CSI-RS) configured in the CSI-ReportConfig with a reportQuantity containing RI (for CSI reporting) during the inactive period of cell DTX. The UE does not anticipate transmitting periodic / semi-persistent CSI reports during the inactive period of cell DRX.

[0105] The UE does not anticipate transmitting periodic / semi-persistent SRS during inactive periods of cell DRX, except when SRS is used for positioning. The UE does not anticipate monitoring PDCCH associated with DCI formats 2_0 to 2_5 during inactive periods of cell DTX.

[0106] On the other hand, the following signals / channels are expected to be unaffected by cell DTX / DRX:

[0107] For both gNBs and Rel-18 and legacy UEs, there is no impact on RACH, paging, and SIB during idle / inactive periods. The UE monitors the PDCCH for RAR during cell DTX inactivity. `ra-ResponseWindow` can be used as a legacy start. The UE monitors the PDCCH for RACH message 4 (Msg4) during cell DTX inactivity. `ra-ContentionResolutionTimer` can be used as a legacy start.

[0108] Once the gNB identifies an emergency call or public safety-related service (e.g., MPS / MCS), the network ensures that the emergency call is not affected (e.g., cell DTX / DRX can be deactivated). When the gNB receives a dynamic grant (DG) during cell DTX / DTX, the UE follows the grant assignment (i.e., similar to conventional methods). This includes DL HARQ feedback.

[0109] The HARQ-ACK of the transmitted SPS PDSCH is unaffected by the inactivity period of the cell DRX. The SRS used for positioning is unaffected by cell DRX operation. The HARQ-ACK of the DCI format of the unscheduled PDSCH is unaffected by the inactivity period of the cell DRX.

[0110] Regarding the supported DTX / DRX modes for cells, the following has been agreed upon:

[0111] The cell DRX / DTX mode configuration is universal for Rel-18 UEs within the cell. Separate DTX and DRX configurations are supported, allowing cell DTX to be configured even without a cell DRX. Periodic cell DTX / DRX configurations are explicitly signaled to the UE.

[0112] The periodic cell DTX / DRX mode is configured by UE-specific RRC signaling. The cell DTX / DRX configuration includes at least: periodicity, start time slot / offset, and activation duration. In some embodiments, cell DTX / DRX is implicitly activated / deactivated via RRC signaling; that is, it is activated immediately upon RRC configuration and deactivated once the RRC configuration is released.

[0113] The start timer formula (including SlotOffset) from the UE C-DRX's onDurationTimer will be reused to specify the start of cellDTX-onDurationTimer (and cellDRX-onDurationTimer) in 3GPP TS 38.321, which is expected to have the same value range as the UE C-DRX long cycle. When both are configured, the start duration and cycle parameters are common between cell DTX and DRX.

[0114] If C-DRX is configured and the retransmission timer is running, the UE is expected to monitor the PDCCH, as in the conventional approach. The network decides whether to schedule retransmissions outside the cell DTX activity period; that is, when the DRX retransmission timer is running, the UE should monitor the PDCCH regardless of cell DTX activity. The network ensures at least partial overlap between the UE's C-DRX activation duration and the cell DTX / DRX activation duration, for example, by periodically configuring cell DTX / DRX and C-DRX to multiples of each other.

[0115] It was also agreed that Layer 1 (L1) signaling would be supported for activation and deactivation of cell DTX / DRX. More specifically, the following has been agreed upon:

[0116] The cell DRX / DTX mode configuration is universal for Rel-18 UEs within the cell. The group common L1 signaling using PDCCH for cell DTX / DRX activation and deactivation is based on the new DCI format 2_X, which is monitored in the common search space.

[0117] DCI format 2_X contains at least N information block fields, each containing signaling for activation or deactivation of the "Cell DTX and / or DRX Configuration" for the "Serving Cell". If necessary, the DCI may also include spare / reserved padding bits to match the size configured for DCI 2_X. For a serving cell configured with Supplemental Uplink (SUL), the same bit applies to both Non-Supplemental (i.e., Normal) Uplink (NUL) and SUL.

[0118] For each serving cell activated / deactivated via L1 signaling with cell DTX and / or cell DRX configured, the start bit position of the information block in DCI format 2_X is provided by UE-specific higher-layer signaling.

[0119] The DCI format 2_X information block fields for activation and deactivation of cell DTX and DRX configuration support separate (activation / deactivation) signaling for cell DTX and cell DRX, namely an activation / deactivation signaling subfield for cell DTX configuration and an activation / deactivation signaling subfield for cell DRX configuration, i.e., a separate 1-bit indication for each of the activation / deactivation of a cell DTX and a cell DRX.

[0120] Depending on whether higher-layer signaling configures one or both of the cell DTX and cell DRX for a given serving cell, the information block field in DCI format 2_X is of variable size, i.e., 1 or 2 bits. If both are configured, the first bit corresponds to the activation / deactivation of the cell DTX configuration, and the second bit corresponds to the activation / deactivation of the cell DRX configuration. Otherwise, 1 bit corresponds to either the configured cell DTX or cell DRX configuration.

[0121] DCI Format 2_X supports activation / deactivation of cell DTX / DRX configurations for multiple serving cells, and also supports per-cell activation / deactivation, where the UE monitors DCI Format 2_X within a single serving cell. A new RNTI, such as nes-RNTI, is configured by a higher layer for scrambling DCI Format 2_X.

[0122] The search space group configuration for the new DCI format 2_X and the DCI size for DCI format 2_X are both included in the RRC parameter list for the activation and deactivation of cell DTX / DRX in the new DCI format 2_X.

[0123] Define the delay value (D) applied after receiving DCI format 2_X in the cell DTX / DRX configuration for activation / deactivation, where the UE is expected to apply cell DTX or DRX activation / deactivation changes at the beginning of slot k, where the SCS of slot X is relative to the active DL or UL BWP of the serving cell, respectively. Slot k is the first slot whose start is no earlier than the start of slot n+D, where n is the slot containing the PDCCH of DCI format 2_X with SCS based on PDCCH, and the possible values ​​of D with respect to SCS are provided in Table 2.

[0124] SCS (kHz) of PDCCH D (in time slots) 15 3 30 6 60 12 120 24 480 96 960 192

[0125] Table 2: Values ​​of D related to SCS

[0126] For the following solutions, one or more of the following assumptions may be maintained.

[0127] Unless otherwise stated, transmission and reception are assumed from a network perspective, that is, transmission means network transmission and reception means network reception.

[0128] Unless otherwise stated, the following concepts are used interchangeably: network node, transmit-receive point (TRP), panel, antenna group, antenna port group, uniform linear array, cell, node, radio head, communication (e.g., signal / channel) associated with a control resource set (CORESET) pool, and communication associated with a transmit configuration indicator (TCI) state from a transmit configuration that includes at least two TCI states.

[0129] As used in this article, a matrix means a sequence of fields of arbitrary dimensions, an array of values ​​(vector), a standard 2D matrix, and more generally a Q-dimensional matrix (tensor), where Q≥2 are integer values.

[0130] Several implementation schemes are described below. Depending on the possible implementation schemes, one or more elements or features from one or more of the described implementation schemes may be combined.

[0131] According to an aspect of the first solution, the enhanced cell DTX / DRX configuration enables an enhanced PDCCH with a DCI format that supports cell DTX / DRX and cell shutdown joint L1 triggering, wherein the DCI field in the PDCCH transmission is based at least on the higher layer configuration of cell DTX / DRX, and the higher layer configuration of cell shutdown is enabled or disabled.

[0132] In the first implementation, cell shutdown is referred to by at least one of the following: A) cell shutdown; B) cell handover; C) conditional handover (CHO); D) cell sleep; E) cell deactivation; F) cell disablement; G) handover command; H) handover trigger; I) cell offloading; (J) energy-saving (e.g., NES-specific) CHO execution condition; or K) a combination thereof. An example of a CHO is an energy-saving (e.g., NES-specific) CHO.

[0133] In a second implementation of the first solution, the cell shutdown indication is included in the PDCCH corresponding to DCI format 2_9 with higher layer parameters, such as cellTurnOffConfig, cellTurnOff, and nes-CondHandover as conditions, wherein the DCI field corresponding to cell shutdown is included only if the higher layer parameter corresponding to cell shutdown is configured.

[0134] In the first instance of this second implementation scheme, the higher-layer parameters for cell shutdown are included as a portion of the RRC configuration information element used for cell shutdown configuration, handover, conditional handover, or a combination thereof. In the second instance, the higher-layer parameters for cell shutdown are included as a portion of the cell DTX / DRX configuration.

[0135] The cell DTX / DRX configuration IE (e.g., CellDTXDRX-Config IE) is used to configure cell DTX / DRX related parameters. Cell DTX is only configured when C-DRX is configured.

[0136] Figure 4 This describes an exemplary cell DTX / DRX configuration IE according to aspects of this disclosure. The cell DTX / DRX configuration is a set of parameters that defines how and when the UE should enter or exit low-power state, and the frequency at which it should monitor the network for incoming data. Descriptions of the fields of the cell DTX / DRX configuration IE are shown in Table 3 below.

[0137]

[0138] Table 3: Description of CellDTXDRX-Config IE Fields

[0139] In the third implementation of the first solution, it is not expected that the UE will transmit or receive signals and channels from the cell after a given time following receiving an instruction to activate or enable cell shutdown.

[0140] According to an aspect of the second solution, the enhanced cell DTX / DRX configuration enables priority rules for the applicability of the cell shutdown indicator relative to the cell DTX / DRX indicator in the DCI, wherein if cell shutdown is triggered, the cell shutdown indicator overrides the cell DTX / DRX indicator.

[0141] The first implementation of the second solution corresponds to DCI format 2_9, where both cell DTX / DRX and cell shutdown are configured at a higher layer, with cell shutdown associated with a lower priority (e.g., LSB bits in the block). If the UE is configured with the higher-layer parameter CellDTXDRX-Config, then the higher layer configures one or more blocks for the UE, where the following fields are defined for each block:

[0142] Provides a 1-bit field for cell DTX / DRX indication if the higher-level parameter cellDTXDRXconfigType is configured as "dtx" or "drx" and the higher-level parameter cellTurnOff is not configured.

[0143] Provides a 1-bit field for cell shutdown indication if the higher-level parameter cellDTXDRXconfigType is not configured and the higher-level parameter cellTurnOff is configured;

[0144] Provides a 2-bit field for cell DTX / DRX indication. If cellDTXDRXconfigType is configured as “dtxdrx” and the higher-level parameter cellTurnOff is not configured, the MSB corresponds to the cell DTX configuration and the LSB corresponds to the cell DRX configuration.

[0145] Provides a 2-bit field for cell DTX / DRX indication if cellDTXDRXconfigType is configured as "dtx" or "drx" and the higher-level parameter cellTurnOff is configured, where MSB corresponds to cell DTX / DRX configuration and LSB corresponds to cell shutdown indication;

[0146] The 3-bit field, if cellDTXDRXconfigType is configured as "dtxdrx" and the higher-level parameter cellTurnOff is configured, provides cell DTX / DRX indication in two most significant bits (MSB), where MSB corresponds to cell DTX configuration and LSB corresponds to cell DRX configuration, and provides cell shutdown indication in one least significant bit (LSB).

[0147] In the first embodiment, the size of DCI format 2_9 is indicated by the higher layer parameter sizeDCI-2-9.

[0148] The second implementation of the second solution corresponds to DCI format 2_9, where both cell DTX / DRX and cell shutdown are configured by a higher layer, with cell shutdown associated with a higher priority (e.g., the MSB bit in the block). If the UE is configured with the higher-layer parameter CellDTXDRX-Config, then the higher layer configures one or more blocks for the UE, where the following fields are defined for each block:

[0149] Provides a 1-bit field for cell DTX / DRX indication if the higher-level parameter cellDTXDRXconfigType is configured as "dtx" or "drx" and the higher-level parameter cellTurnOff is not configured.

[0150] Provides a 1-bit field for cell shutdown indication if the higher-level parameter cellDTXDRXconfigType is not configured and the higher-level parameter cellTurnOff is configured;

[0151] Provides a 2-bit field for cell DTX / DRX indication. If cellDTXDRXconfigType is configured as “dtxdrx” and the higher-level parameter cellTurnOff is not configured, the MSB corresponds to the cell DTX configuration and the LSB corresponds to the cell DRX configuration.

[0152] Provides a 2-bit field for cell DTX / DRX indication if cellDTXDRXconfigType is configured as "dtx" or "drx" and the higher-level parameter cellTurnOff is configured, where MSB corresponds to cell shutdown indication and LSB corresponds to cell DTX / DRX configuration;

[0153] The 3-bit field, if cellDTXDRXconfigType is configured as "dtxdrx" and the higher-level parameter cellTurnOff is configured, has one MSB providing a cell shutdown indication and the remaining two bits (i.e., LSB) providing a cell DTX / DRX indication, where the remaining two MSB bits correspond to the cell DTX configuration and the remaining two LSB bits correspond to the cell DRX configuration.

[0154] In the second embodiment, the size of DCI format 2_9 is indicated by the higher layer parameter sizeDCI-2-9.

[0155] In some implementations, for NES-enabled UEs (or UEs capable of NES), a cell shutdown indication (or energy-saving (e.g., NES-specific) CHO execution condition indication) is supported (e.g., signaling included in DCI format 2_9) and cell shutdown has no higher-level configuration. In some implementations, a cell shutdown indication is supported, and for NES-enabled UEs, cell shutdown has no higher-level configuration if at least one of the events in the measIds within the condTriggerConfig associated with the target candidate cell in condRRCReconfig is configured with nesEvent.

[0156] The third implementation of the second solution corresponds to DCI format 2_9, where cell shutdown does not have higher-level configuration, and cell shutdown is associated with lower priority. If the UE is configured with the higher-level parameter CellDTXDRX-Config, then the higher-level layer configures one or more blocks for the UE, where the following fields are defined for each block:

[0157] Provides a 1-bit field for indicating cell shutdown if the higher-level parameter cellDTXDRXconfigType is not configured.

[0158] Provides a 2-bit field for cell DTX / DRX indication. If cellDTXDRXconfigType is configured as "dtx" or "drx", the MSB corresponds to the cell DTX / DRX configuration and the LSB corresponds to the cell shutdown indication.

[0159] The 3-bit field, if cellDTXDRXconfigType is configured as "dtxdrx", includes two MSB bits that provide cell DTX / DRX indication, where the MSB corresponds to the cell DTX configuration and the LSB corresponds to the cell DRX configuration, and the LSB provides cell shutdown indication.

[0160] In the third implementation, the size of DCI format 2_9 is indicated by the higher layer parameter sizeDCI-2-9.

[0161] The fourth implementation of the second solution corresponds to DCI format 2_9, where cell shutdown does not have higher-level configuration, and cell shutdown is associated with higher priority. If the UE is configured with the higher-level parameter CellDTXDRX-Config, then the higher-level layer configures one or more blocks for the UE, where the following fields are defined for each block:

[0162] Provides a 1-bit field for indicating cell shutdown if the higher-level parameter cellDTXDRXconfigType is not configured.

[0163] Provides a 2-bit field for cell DTX / DRX indication. If cellDTXDRXconfigType is configured as "dtx" or "drx", the MSB corresponds to the cell shutdown indication and the LSB corresponds to the cell DTX / DRX configuration.

[0164] The 3-bit field, if cellDTXDRXconfigType is configured as "dtxdrx", has the MSB providing a cell shutdown indication; and the remaining 2 (LSB) bits provide a cell DTX / DRX indication, where the remaining 2 MSB bits correspond to the cell DTX configuration and the remaining 2 LSB bits correspond to the cell DRX configuration.

[0165] In the fourth embodiment, the size of DCI format 2_9 is indicated by the higher layer parameter sizeDCI-2-9.

[0166] In a fifth implementation of the second solution, if the DCI field bit corresponding to cell shutdown is set to one (“1”) or enabled, the UE is expected to ignore the values ​​of the DCI fields corresponding to cell DTX and / or cell DRX (if applicable). In some implementations, if the DCI field bit corresponding to cell shutdown is set to one (“1”) or enabled or activated, the UE is not expected to receive the values ​​of the DCI fields corresponding to cell DTX and / or cell DRX (if applicable, set to “1” or enabled or activated). In other words, cell shutdown bits can be prioritized such that if the cell shutdown DCI bit is enabled / activated (e.g., if set to “1”), then other cell DTX / DRX bits are ignored.

[0167] According to the third solution, the enhanced cell DTX / DRX configuration enables a defined application time T for cell shutdown. AP Where, in T relative to the time of receiving DCI AP Cell shutdown is applied after a certain time unit (e.g., a time slot or ms). Under this method, if the UE receives a DCI with an indication that the cell has been shut down at time slot n, the UE expects the cell to be shut down after the application time.

[0168] In the first instance, the UE expects the cell to start (or end) T after slot n. AP ms off. In the second instance, the UE expects the cell to be off after slot n for T seconds. AP ms off. In the third instance, the UE expects the cell to be T after time slot n. AP The time slot is closed.

[0169] In the first implementation of the third solution, the unit of application time is T. AP It is presented in the form of milliseconds or time slot indexes. In the second implementation of the third solution, T AP It is a higher-level configuration, where T AP The value is selected from a set of code points, such as {100,200,500,1000,2000,4000,5000,10000}ms.

[0170] In the third implementation of the third solution, T AP It is a fixed value, such as 1000ms. In the first example, the value of the application time is based on the subcarrier spacing (SCS) value of the OFDM signal, where the application time in the time slot sequence is proportional to the SCS value.

[0171] In the fourth implementation of the third solution, T APThis is L1 indicated in the DCI, where DCI format 2_9 includes additional fields indicating the application time value. In the first instance, the codebook of the application time value is included as part of the higher-layer configuration corresponding to cell shutdown.

[0172] In the second instance, the codebook for the application time value is set by rules, for example, rules based on the SCS value of the OFDM signal, wherein the application time in the time slot sequence is proportional to the SCS value.

[0173] In the fifth implementation of the third solution, when cell DTX and / or cell DRX are configured, the UE expects (or assumes) that the cell will be shut down at the beginning of the cell DRX / DTX activity cycle, rather than before the start of the time slot with the minimum time gap that is received with the DCI2_9 cell shutdown indication with the bit set to "1".

[0174] In the sixth implementation of the third solution, the UE expects (or assumes) that the cell will shut down at the beginning of a subframe / slot based on the cell shutdown start offset and possible cell shutdown cycles / periods and slot offsets, rather than before the start of a slot with the minimum time gap of the slot with the received DCI 2_9 cell shutdown indication having a bit set to "1".

[0175] For example, if [(SFN×10)+subframe number] modulo (cellturnoff-Cycle) = (cellturnoff-StartOffset), then the UE expects (or assumes) that the cell will be turned off after cellturnoff-SlotOffset from the start of the subframe.

[0176] In some instances, the cell shutdown cycle / period value may be fixed in the specification, such as 1ms or a value based on a timer (e.g., the T310 timer). In some instances, cellturnoff-SlotOffset may not be configured (e.g., step 2> UE expects (or assumes) that the cell will be shut down from the start of the subframe that satisfies step 1>), or the cell shutdown cycle / period value may be fixed in the specification.

[0177] In the seventh implementation of the third solution, a cell shutdown instruction for the second serving cell, or a DCI format 2_9 indicating an NES-specific CHO execution condition, can be received on the first serving cell. The cell shutdown application time or subframe / time slot is determined based on the subframe / time slot of the first serving cell.

[0178] Figure 5An example of a UE 500 according to aspects of this disclosure is described. UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, memory 504, controller 506, or transceiver 508, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, and electrically).

[0179] Processor 502, memory 504, controller 506, or transceiver 508, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may be a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured or otherwise supporting components for performing the functions described in this disclosure.

[0180] Processor 502 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, central processing unit (CPU), ASIC, field-programmable gate array (FPGA), or any combination thereof). In some embodiments, processor 502 may be configured to operate memory 504. In some other embodiments, memory 504 may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory 504 to cause UE 500 to perform various functions of this disclosure.

[0181] Memory 504 may comprise volatile or non-volatile memory. Memory 504 may store computer-readable, computer-executable code containing instructions that, when executed by processor 502, cause UE 500 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 504 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0182] In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to cause UE 500 to perform one or more of the UE functions described herein (e.g., instructions stored in memory 504 are executed by processor 502). Thus, processor 502 may support wireless communication at UE 500 according to the examples disclosed herein. For example, UE 500 may be configured to support components for, for example, receiving cell DTX / DRX configurations for multiple serving cells from a network entity. In some embodiments, cell DTX / DRX configurations include RRC signaling for a set of parameters for DTX / DRX operation in the cell.

[0183] UE 500 may be configured to support components for receiving DCI signals for a serving cell that at least corresponds to a cell DTX / DRX configuration, wherein the DCI includes an indication of cell shutdown. In some embodiments, the DCI signal includes a PDCCH transmission corresponding to DCI format 2_9. In some embodiments, the size of DCI format 2_9 is configured by higher-layer signaling.

[0184] In some embodiments, the cell shutdown indication includes an NES CHO indication. In some embodiments, the cell DTX / DRX configuration includes higher-layer parameters for an NES-specific CHO.

[0185] The UE 500 can be configured to support components for performing cell search based at least in part on cell shutdown and cell DTX / DRX configuration.

[0186] In some embodiments, the UE 500 is configured to receive a cell shutdown configuration for at least one serving cell. In some embodiments, both the cell DTX / DRX configuration and the cell shutdown configuration are higher-level configurations.

[0187] In some embodiments, the DCI signal includes multiple blocks associated with multiple serving cells. In some embodiments, a corresponding block among the multiple blocks includes a one-bit field that indicates a cell shutdown operation based at least in part on: 1) cell shutdown parameters being configured and 2) cell DTX / DRX type parameters not being configured.

[0188] In some embodiments, a corresponding block among a plurality of blocks includes at least in part a one-bit field that indicates cell DTX / DRX operation based on: 1) a DTX / DRX type parameter configured for cell DTX or cell DRX, and 2) a cell shutdown parameter not configured.

[0189] In some embodiments, a corresponding block among a plurality of blocks includes at least in part a two-bit field indicating cell DTX / DRX operation based on: 1) cell DTX / DRX type parameters configured for both cell DTX and cell DRX, and 2) cell shutdown parameters not configured.

[0190] In some embodiments, a corresponding block among a plurality of blocks includes a two-bit field that indicates a cell shutdown operation at least in part based on cell shutdown parameters configured to cell DTX or cell DRX (e.g., using 1 bit), and further at least in part based on cell shutdown parameters configured to indicate a cell shutdown operation.

[0191] In some embodiments, a corresponding block among a plurality of blocks includes a three-bit field that indicates cell DTX / DRX operation at least in part based on cell DTX / DRX type parameters configured for both cell DTX and cell DRX (e.g., using 2 bits), and further indicates cell shutdown operation at least in part based on cell shutdown parameters.

[0192] In some embodiments, UE 500 is configured to determine the cell shutdown application time of the serving cell. In some embodiments, UE 500 is further configured to ignore transmissions or receptions associated with the serving cell, at least in part, based on the cell shutdown application time.

[0193] In some embodiments, the application time for cell shutdown is configured from a set of candidate values ​​or indicated in the DCI signal. In some embodiments, the UE 500 may calculate the application time for cell shutdown by referring to the reception time of the DCI signal. In other embodiments, the application time for cell shutdown is set by a rule or a fixed value.

[0194] Controller 506 manages the input and output signals of UE 500. Controller 506 can also manage peripheral devices not integrated into UE 500. In some implementations, controller 506 may utilize, for example... Or an operating system (OS) of another operating system. In some implementations, controller 506 may be implemented as part of processor 502.

[0195] In some embodiments, UE 500 may include at least one transceiver 508. In other embodiments, UE 500 may have more than one transceiver 508. Transceiver 508 may represent a wireless transceiver. Transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

[0196] Receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, receiver chain 510 may include one or more antennas for receiving signals over the air or over a wireless medium. Receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 510 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 510 may include at least one decoder for decoding / processing the demodulated signal to receive transmitted data.

[0197] Transmitter chain 512 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0198] Figure 6 An example of a processor 600 according to aspects of this disclosure is described. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0199] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 600) or contained within the processor chipset (e.g., processor 600) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), and others)).

[0200] Controller 602 can be configured to manage and coordinate various operations of processor 600 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 600 to support various operations according to the examples described herein. For example, controller 602 can operate as a control unit of processor 600, generating control signals that manage the operation of various components of processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0201] Controller 602 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 604 and determine subsequent instructions to be executed to enable processor 600 to support various operations according to the examples described herein. Controller 602 may be configured to track the memory addresses of instructions associated with memory 604. Controller 602 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 602 may be configured to interpret instructions and determine control signals to be output to other components of processor 600 to enable processor 600 to support various operations according to the examples described herein. Alternatively or additionally, controller 602 may be configured to manage data flow within processor 600. Controller 602 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0202] Memory 604 may include one or more caches (e.g., memory local to processor 600 or included in processor 600, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some embodiments, memory 604 may reside within or on the processor chipset (e.g., local to processor 600). In some other embodiments, memory 604 may reside outside the processor chipset (e.g., remote from processor 600).

[0203] Memory 604 may store computer-readable, computer-executable code containing instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions. For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some instances, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be individually or collectively configured to perform the various functions described herein.

[0204] One or more ALUs 606 may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALUs 606 may reside within or on a processor chipset (e.g., processor 600). In some other embodiments, one or more ALUs 606 may reside outside the processor chipset (e.g., processor 600). One or more ALUs 606 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 606 may receive input operands and an opcode that determines the operation to be performed. One or more ALUs 606 may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 606s to handle conditional operations, comparisons, and bitwise operations.

[0205] In various embodiments, according to the examples disclosed herein, processor 600 may support wireless communication for the UE. For example, processor 600 may be configured to support components for receiving, for example, cell DTX / DRX configuration for multiple serving cells from a network entity. In some embodiments, cell DTX / DRX configuration includes RRC signaling for a set of parameters for DTX / DRX operation in the cell.

[0206] Processor 600 may be configured to support components for receiving DCI signals for a serving cell that at least corresponds to a cell DTX / DRX configuration, wherein the DCI includes an indication of cell shutdown. In some embodiments, the DCI signal includes a PDCCH transmission corresponding to DCI format 2_9. In some embodiments, the size of DCI format 2_9 is configured by higher-layer signaling.

[0207] In some embodiments, the cell shutdown indication includes an NES CHO indication. In some embodiments, the cell DTX / DRX configuration includes higher-layer parameters for an NES-specific CHO.

[0208] The processor 600 can be configured to support components for performing cell search based at least in part on cell shutdown and cell DTX / DRX configuration.

[0209] In some embodiments, the processor 600 is configured to receive a cell shutdown configuration for at least one serving cell. In some embodiments, both the cell DTX / DRX configuration and the cell shutdown configuration are higher-level configurations.

[0210] In some embodiments, the DCI signal includes multiple blocks associated with multiple serving cells. In some embodiments, a corresponding block among the multiple blocks includes a one-bit field that indicates a cell shutdown operation based at least in part on: 1) cell shutdown parameters being configured and 2) cell DTX / DRX type parameters not being configured.

[0211] In some embodiments, a corresponding block among a plurality of blocks includes at least in part a one-bit field that indicates cell DTX / DRX operation based on: 1) a DTX / DRX type parameter configured for cell DTX or cell DRX, and 2) a cell shutdown parameter not configured.

[0212] In some embodiments, a corresponding block among a plurality of blocks includes at least in part a two-bit field indicating cell DTX / DRX operation based on: 1) cell DTX / DRX type parameters configured for both cell DTX and cell DRX, and 2) cell shutdown parameters not configured.

[0213] In some embodiments, a corresponding block among a plurality of blocks includes a two-bit field that indicates a cell shutdown operation at least in part based on cell shutdown parameters configured to cell DTX or cell DRX (e.g., using 1 bit), and further at least in part based on cell shutdown parameters configured to indicate a cell shutdown operation.

[0214] In some embodiments, a corresponding block among a plurality of blocks includes a three-bit field that indicates cell DTX / DRX operation at least in part based on cell DTX / DRX type parameters configured for both cell DTX and cell DRX (e.g., using 2 bits), and further indicates cell shutdown operation at least in part based on cell shutdown parameters.

[0215] In some embodiments, the processor 600 is configured to determine the cell shutdown application time of the serving cell. In some embodiments, the processor 600 is further configured to ignore transmissions or receptions associated with the serving cell, at least in part, based on the cell shutdown application time.

[0216] In some embodiments, the application time for cell shutdown is configured from a set of candidate values ​​or indicated in the DCI signal. In some embodiments, the processor 600 may calculate the application time for cell shutdown with reference to the reception time of the DCI signal. In other embodiments, the application time for cell shutdown is set by a rule or a fixed value.

[0217] In various implementations, according to the examples disclosed herein, processor 600 may support base station functionality. For example, processor 600 may be configured to support components for transmitting, for example, cell DTX / DRX configurations for multiple serving cells to a group of one or more UEs. In some embodiments, cell DTX / DRX configuration includes RRC signaling for a set of parameters for DTX / DRX operation in the cell.

[0218] The processor 600 may be configured to support components for transmitting DCI signals for a serving cell that at least corresponds to a cell DTX / DRX configuration, wherein the DCI signals further include an indication of cell shutdown. In some embodiments, the DCI signals include PDCCH transmissions corresponding to DCI format 2_9. In some embodiments, the size of DCI format 2_9 is configured by higher-layer signaling.

[0219] In some embodiments, the cell shutdown indication includes an NES CHO indication. In some embodiments, the cell DTX / DRX configuration includes higher-layer parameters for an NES-specific CHO.

[0220] The processor 600 can be configured to support components for deactivating a serving cell, at least in part, based on cell shutdown and cell DTX / DRX configuration.

[0221] In some embodiments, the processor 600 is configured to (e.g., to the group of UEs) transmit a cell shutdown configuration for at least one serving cell. In some embodiments, both the cell DTX / DRX configuration and the cell shutdown configuration are higher-level configurations.

[0222] In some embodiments, the DCI signal includes multiple blocks associated with multiple serving cells. In some embodiments, a corresponding block among the multiple blocks includes a one-bit field that indicates a cell shutdown operation based at least in part on: 1) cell shutdown parameters being configured and 2) cell DTX / DRX type parameters not being configured.

[0223] In some embodiments, a corresponding block among a plurality of blocks includes at least in part a one-bit field that indicates cell DTX / DRX operation based on: 1) a DTX / DRX type parameter configured for cell DTX or cell DRX, and 2) a cell shutdown parameter not configured.

[0224] In some embodiments, a corresponding block among a plurality of blocks includes at least in part a two-bit field indicating cell DTX / DRX operation based on: 1) cell DTX / DRX type parameters configured for both cell DTX and cell DRX, and 2) cell shutdown parameters not configured.

[0225] In some embodiments, a corresponding block among a plurality of blocks includes a two-bit field that indicates a cell shutdown operation at least in part based on cell shutdown parameters configured to cell DTX or cell DRX (e.g., using 1 bit), and further at least in part based on cell shutdown parameters configured to indicate a cell shutdown operation.

[0226] In some embodiments, a corresponding block among a plurality of blocks includes a three-bit field that indicates cell DTX / DRX operation at least in part based on cell DTX / DRX type parameters configured for both cell DTX and cell DRX (e.g., using 2 bits), and further indicates cell shutdown operation at least in part based on cell shutdown parameters.

[0227] Figure 7 This describes an example of NE 700 according to aspects of this disclosure. NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, memory 704, controller 706, or transceiver 708, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively ground, communicatively ground, functional ground, electronic ground, electrical ground).

[0228] Processor 702, memory 704, controller 706, or transceiver 708, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may be a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured or otherwise supporting components for performing the functions described in this disclosure.

[0229] Processor 702 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 702 may be configured to operate memory 704. In some other embodiments, memory 704 may be integrated into processor 702. Processor 702 may be configured to execute computer-readable instructions stored in memory 704 to cause NE 700 to perform various functions of this disclosure.

[0230] Memory 704 may comprise volatile or non-volatile memory. Memory 704 may store computer-readable, computer-executable code containing instructions that, when executed by processor 702, cause NE 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 704 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.

[0231] In some implementations, processor 702 and memory 704 coupled to processor 702 may be configured to cause NE 700 to perform one or more of the RAN functions described herein (e.g., by processor 702 executing instructions stored in memory 704). Thus, processor 702 may support wireless communication at NE 700 according to the examples disclosed herein. For example, NE 700 may be configured to support components for transmitting, for example, cell DTX / DRX configurations for multiple serving cells to a group of one or more UEs. In some embodiments, cell DTX / DRX configuration includes RRC signaling for a set of parameters for DTX / DRX operation in the cell.

[0232] The NE 700 can be configured to support components for transmitting DCI signals for a serving cell that at least corresponds to a cell DTX / DRX configuration, wherein the DCI signals further include an indication of cell shutdown. In some embodiments, the DCI signals include PDCCH transmissions corresponding to DCI format 2_9. In some embodiments, the size of DCI format 2_9 is configured by higher-layer signaling.

[0233] In some embodiments, the cell shutdown indication includes an NES CHO indication. In some embodiments, the cell DTX / DRX configuration includes higher-layer parameters for an NES-specific CHO.

[0234] The NE 700 can be configured to support components for deactivating serving cells, at least in part, based on cell shutdown and cell DTX / DRX configuration.

[0235] In some embodiments, the NE 700 is configured (e.g., to the group of UEs) to transmit a cell shutdown configuration for at least one serving cell. In some embodiments, both the cell DTX / DRX configuration and the cell shutdown configuration are configured at a higher layer.

[0236] In some embodiments, the DCI signal includes multiple blocks associated with multiple serving cells. In some embodiments, a corresponding block among the multiple blocks includes a one-bit field that indicates a cell shutdown operation based at least in part on: 1) cell shutdown parameters being configured and 2) cell DTX / DRX type parameters not being configured.

[0237] In some embodiments, a corresponding block among a plurality of blocks includes at least in part a one-bit field that indicates cell DTX / DRX operation based on: 1) a DTX / DRX type parameter configured for cell DTX or cell DRX, and 2) a cell shutdown parameter not configured.

[0238] In some embodiments, a corresponding block among a plurality of blocks includes at least in part a two-bit field indicating cell DTX / DRX operation based on: 1) cell DTX / DRX type parameters configured for both cell DTX and cell DRX, and 2) cell shutdown parameters not configured.

[0239] In some embodiments, a corresponding block among a plurality of blocks includes a two-bit field that indicates a cell shutdown operation at least in part based on cell shutdown parameters configured to cell DTX or cell DRX (e.g., using 1 bit), and further at least in part based on cell shutdown parameters configured to indicate a cell shutdown operation.

[0240] In some embodiments, a corresponding block among a plurality of blocks includes a three-bit field that indicates cell DTX / DRX operation at least in part based on cell DTX / DRX type parameters configured for both cell DTX and cell DRX (e.g., using 2 bits), and further indicates cell shutdown operation at least in part based on cell shutdown parameters.

[0241] Controller 706 manages the input and output signals of NE 700. Controller 706 can also manage peripheral devices not integrated into NE 700. In some implementations, controller 706 may utilize, for example... Or an operating system of other operating systems. In some implementations, controller 706 may be implemented as part of processor 702.

[0242] In some embodiments, the NE 700 may include at least one transceiver 708. In other embodiments, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0243] Receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, receiver chain 710 may include one or more antennas for receiving signals over the air or over a wireless medium. Receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 710 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 710 may include at least one decoder for decoding / processing the demodulated signal to receive transmitted data.

[0244] Transmitter chain 712 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0245] Figure 8 An embodiment of method 800 according to aspects of this disclosure is depicted. Operation of method 800 may be implemented by the UE described herein. In some embodiments, the UE may execute a set of instructions to control functional elements of the UE to perform the described functions.

[0246] At step 802, method 800 may include (e.g., from a base station) receiving cell DTX / DRX configurations for multiple serving cells. The operation of step 802 may be performed according to the examples described herein. In some embodiments, aspects of the operation of step 802 may be as described regarding... Figure 5 The UE described is used for execution.

[0247] At step 804, method 800 may include receiving a DCI for a serving cell corresponding at least to a cell DTX / DRX configuration, the DCI containing an indication of cell shutdown. The operation of step 804 may be performed according to the examples described herein. In some embodiments, aspects of the operation of step 804 may be as described regarding... Figure 5 The UE described is used for execution.

[0248] At step 806, method 800 may include performing cell search based at least in part on cell shutdown and cell DTX / DRX configuration. The operation of step 806 may be performed according to the examples described herein. In some embodiments, aspects of the operation of step 806 may be as described regarding... Figure 5 The UE described is used for execution.

[0249] It should be noted that the method 800 described herein describes one possible implementation, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.

[0250] Figure 9 An embodiment of method 900 according to aspects of this disclosure is depicted. Operation of method 900 may be implemented by the NE described herein. In some embodiments, the NE may execute a set of instructions to control the functional elements of the NE to perform the described functions.

[0251] At step 902, method 900 may include (e.g., transmitting to the UE) cell DTX / DRX configuration for multiple serving cells. The operation of step 902 may be performed according to the examples described herein. In some embodiments, aspects of the operation of step 902 may be as described regarding... Figure 7 The described NE is used for execution.

[0252] At step 904, method 900 may include transmitting a DCI for a serving cell that at least corresponds to the cell's DTX / DRX configuration, the DCI containing an indication of cell shutdown. The operation of step 904 may be performed according to the examples described herein. In some embodiments, aspects of the operation of step 904 may be as described regarding... Figure 7 The described NE is used for execution.

[0253] At step 906, method 900 may include deactivating the serving cell at least in part based on cell shutdown and cell DTX / DRX configuration. The operation of step 906 may be performed according to the examples described herein. In some embodiments, aspects of the operation of step 906 may be as described regarding... Figure 7 The described NE is used for execution.

[0254] It should be noted that the method 900 described herein describes one possible implementation, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.

[0255] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; and At least one processor, coupled to and configured to enable the UE to: Receive cell discontinuous transmission and / or reception DTX / DRX configuration from network entities for multiple serving cells; Receive downlink control information (DCI) signals for serving cells that correspond at least to the DTX / DRX configuration of the cell, wherein the DCI signals further include an indication of cell shutdown; and Cell search is performed at least in part based on the cell shutdown and the cell DTX / DRX configuration.

2. The UE according to claim 1, wherein the indication of cell shutdown includes an indication of Network Energy Saving (NES) Conditional Handover (CHO).

3. The UE according to claim 1, wherein the cell DTX / DRX configuration includes Radio Resource Control (RRC) signaling, and wherein the DCI signal includes Physical Downlink Control Channel (PDCCH) transmission corresponding to DCI format 2_9.

4. The UE according to claim 3, wherein the size of the DCI format 2_9 is configured by higher-layer signaling.

5. The UE according to claim 1, wherein the cell DTX / DRX configuration includes higher-layer parameters for network power saving NES-specific CHO.

6. The UE of claim 1, wherein the at least one processor is configured to enable the UE to receive a cell shutdown configuration for the at least one serving cell, wherein both the cell DTX / DRX configuration and the cell shutdown configuration are higher-level configurations.

7. The UE of claim 1, wherein the DCI signal comprises a plurality of blocks associated with the plurality of serving cells, wherein a respective block of the plurality of blocks comprises a one-bit field configured, at least in part, based on DTX / DRX type parameters for cell discontinuous transmission of DTX or cell discontinuous reception of DRX and cell shutdown parameters not configured to indicate cell DTX / DRX operation.

8. The UE of claim 1, wherein the DCI signal comprises a plurality of blocks associated with the plurality of serving cells, wherein a corresponding block of the plurality of blocks comprises a one-bit field that is configured at least in part based on cell shutdown parameters and not configured based on cell DTX / DRX type parameters to indicate a cell shutdown operation.

9. The UE of claim 1, wherein the DCI signal comprises a plurality of blocks associated with the plurality of serving cells, wherein a corresponding block of the plurality of blocks comprises a two-bit field configured, at least in part, based on cell DTX / DRX type parameters for discontinuous transmission DTX and discontinuous reception DRX and cell shutdown parameters not configured to indicate cell DTX / DRX operation.

10. The UE of claim 1, wherein the DCI signal comprises a plurality of blocks associated with the plurality of serving cells, wherein a respective block of the plurality of blocks comprises a two-bit field configured to indicate a cell shutdown operation based at least in part on cell shutdown parameters for cell discontinuous transmit DTX or cell discontinuous receive DRX, and further configured to indicate a cell shutdown operation based at least in part on cell shutdown parameters.

11. The UE of claim 1, wherein the DCI signal comprises a plurality of blocks associated with the plurality of serving cells, wherein a corresponding block of the plurality of blocks comprises a three-bit field configured at least in part based on cell DTX / DRX type parameters to indicate cell DTX / DRX operation for cell discontinuous transmission DTX and cell discontinuous reception DRX, and further configured at least in part based on cell shutdown parameters to indicate cell shutdown operation.

12. The UE of claim 1, wherein the at least one processor is configured to enable the UE to determine the application time for cell shutdown of the serving cell.

13. The UE of claim 12, wherein the at least one processor is configured to cause the UE to ignore transmissions or receptions associated with the serving cell at least in part based on the application time during which the cell is turned off.

14. The UE of claim 12, wherein the application time of the cell shutdown is calculated with reference to the reception time of the DCI signal, and wherein the application time of the cell shutdown is set by a rule or a fixed value.

15. The UE of claim 12, wherein the application time of the cell shutdown is configured from a set of candidate values ​​or indicated in the DCI signal.

16. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured to enable the processor to: Receive cell discontinuous transmission and / or reception DTX / DRX configuration from network entities for multiple serving cells; Receive downlink control information (DCI) signals for serving cells that correspond at least to the DTX / DRX configuration of the cell, wherein the DCI signals further include an indication of cell shutdown; and Cell search is performed at least in part based on the cell shutdown and the cell DTX / DRX configuration.

17. A base station for wireless communication, comprising: At least one memory; and At least one processor, coupled to and configured to enable the base station to: Transmit cell discontinuous transmission and / or receive DTX / DRX configuration for multiple serving cells to at least one user equipment (UE); Transmit downlink control information (DCI) signals for a serving cell that corresponds at least to the DTX / DRX configuration of the said cell, wherein the DCI signals further include an indication of cell shutdown; and The serving cell is deactivated at least in part based on the cell shutdown and the cell DTX / DRX configuration.

18. The base station of claim 17, wherein the indication of cell shutdown includes an indication of Network Energy Saving (NES) Conditional Handover (CHO), and wherein the cell DTX / DRX configuration includes higher-layer parameters for NES-specific CHOs.

19. The base station of claim 17, wherein the cell DTX / DRX configuration includes Radio Resource Control (RRC) signaling, wherein the DCI signal includes Physical Downlink Control Channel (PDCCH) transmission corresponding to DCI format 2_9, and wherein the size of DCI format 2_9 is configured by higher-layer signaling.

20. A method performed by a base station, the method comprising: Transmit cell discontinuous transmission and / or reception DTX / DRX configurations for multiple serving cells to the user equipment (UE); Transmit downlink control information (DCI) signals for a serving cell that corresponds at least to the DTX / DRX configuration of the said cell, wherein the DCI signals further include an indication of cell shutdown; and The serving cell is deactivated at least in part based on the cell shutdown and the cell DTX / DRX configuration.

Images