Aligning user equipment (UE) behavior to network power saving state

Abstract

Aspects of the present disclosure relate to reducing energy consumption in a wireless communication system. For example, based on a broadcast network / cell DTX configuration, a UE may accommodate its DRX behavior. Based on the provided network / cell DTX configuration, the UE may change or modify a timer (e.g., drx timer state), and / or avoid starting an uncompleted uplink procedure while the network / cell is DTX.

Description

Technical Field

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 484,298, filed on February 10, 2023, entitled "ALIGNING USER EQUIPMENT (UE) BEHAVIOR TO NETWORK ENERGY SAVING STATES", the entire content of which is incorporated herein by reference. Technical Field

[0003] This disclosure relates to wireless communication and, more particularly, to aligning user equipment (UE) behavior to network energy saving states. Background Art

[0004] A wireless communication system may include one or more network communication devices, such as base stations, which may also be referred to as eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UEs) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing 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)). Additionally, a wireless communication system may support wireless communication across various radio access technologies, which include third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth-generation (6G)).

[0005] Although the adoption of 5G and technologies beyond 5G enables wireless communication systems to provide enhanced services at high data rates, these enhanced services typically rely on denser networks, such as networks with an increased number of cell sites and / or antennas, larger bandwidths, additional frequency bands, etc. Additionally, as the number of devices and services increases, potential environmental impacts and operating costs due to device emissions and energy consumption may also increase, as well as other unforeseen drawbacks.

[0006] In some cases, the network can achieve energy savings by implementing discontinuous transmission (DTX) and / or discontinuous reception (DRX) of cells. During cell DTX / DRX, the serving cell behavior during the inactive period or time can include: the gNB turning off all transmissions and receptions for data services and reference signals (e.g., all downlink (DL) / uplink (UL) channels and DL / UL signals); the gNB turning off its transmission / reception only for data services (and still sending / receiving reference signals); the gNB turning off its dynamic data transmission / reception (and still performing transmission / reception in periodic resources); and / or the gNB only sending reference signals. SUMMARY OF THE INVENTION

[0007] The present disclosure relates to methods, apparatuses, and systems for supporting reduction of energy consumption in a wireless communication system by adapting UE DRX behavior based on a broadcast network / cell DTX configuration. The UE can change or modify a timer (e.g., the drx timer state) based on the provided network / cell DTX configuration, and / or avoid initiating an uplink process that cannot be completed when the network / cell is in DTX and other technologies.

[0008] Some implementations of the methods and apparatuses described herein may also include UE wireless communication, which includes at least one memory and at least one processor, the at least one processor being coupled to the at least one memory and configured to cause the UE: receive a first configuration from a network entity based on the DTX configuration of the network entity, where the first configuration includes: a first timer that controls an active duration at the start of a cell DTX cycle; receive a second configuration associated with the DRX behavior of the UE from the network entity, where the second configuration includes a set of timers; and determine whether to monitor a physical downlink control channel (PDCCH) at least in part based on the state of the first timer and the state of the set of timers.

[0009] In some implementations of the methods and apparatuses described herein, the DTX configuration identifies an active transmission time period of a network entity.

[0010] In some implementations of the methods and apparatuses described herein, the first timer includes a cell-specific on-duration timer.

[0011] In some implementations of the methods and apparatuses described herein, the processor is configured to cause the UE: determine whether to monitor the PDCCH at least in part based on whether the first timer is running.

[0012] In some implementations of the methods and apparatuses described herein, the processor is configured to cause the UE: determine whether to monitor the PDCCH at least in part based on whether the UE is in an active time according to the second configuration.

[0013] In some implementations of the methods and apparatuses described herein, the processor is configured to cause the UE to determine whether to monitor the PDCCH based at least in part on whether the UE is in the DRX active time according to a second configuration.

[0014] Some implementations of the methods and apparatuses described herein may also include a processor for wireless communication, the processor including at least one controller coupled to at least one memory and configured to cause the processor to: receive a first configuration from the network entity based on the DTX configuration of the network entity, where the first configuration includes: a first timer that controls the active duration at the start of the cell DTX cycle; receive a second configuration associated with the DRX behavior of the processor from the network entity, where the second configuration includes a set of timers; and determine whether to monitor the PDCCH based at least in part on the state of the first timer and the states of the set of timers.

[0015] In some implementations of the methods and apparatuses described herein, the DTX configuration identifies the active transmission time period of the network entity.

[0016] In some implementations of the methods and apparatuses described herein, the first timer includes a cell-specific on-duration timer.

[0017] In some implementations of the methods and apparatuses described herein, the controller is configured to cause the processor to determine whether to monitor the PDCCH based at least in part on whether the first timer is running.

[0018] In some implementations of the methods and apparatuses described herein, the controller is further configured to cause the processor to determine whether to monitor the PDCCH based at least in part on whether the processor is in the active time according to the second configuration.

[0019] In some implementations of the methods and apparatuses described herein, the controller is configured to cause the processor to determine whether to monitor the PDCCH based at least in part on whether the processor is in the active time according to the second configuration.

[0020] Some implementations of the methods and apparatuses described herein may also include a method performed by the UE, the method including: receiving a first configuration from the network entity based on the DTX configuration of the network entity, where the first configuration includes: a first timer that controls the active duration at the start of the cell DTX cycle; receiving a second configuration associated with the DRX behavior of the processor from the network entity, where the second configuration includes a set of timers; and determining whether to monitor the PDCCH based at least in part on the state of the first timer and the states of the set of timers.

[0021] Some implementations of the methods and apparatuses described herein may also include a network entity for wireless communication, the network entity including at least one memory and at least one processor, the at least one processor being coupled to the at least one memory and configured to cause the network entity to: generate a timer configuration based on the DTX configuration of the network entity, and send the timer configuration to one or more UEs.

[0022] In some implementations of the methods and apparatuses described herein, the DTX configuration identifies a pattern of an inactive transmission time period of the network entity.

[0023] In some implementations of the methods and apparatuses described herein, the network entity sends the timer configuration via L1 / L2 signaling.

[0024] In some implementations of the methods and apparatuses described herein, the network entity sends the timer configuration to one or more UEs via a broadcast message.

[0025] Some implementations of the methods and apparatuses described herein may also include a method performed by the network entity, the method including: generating a timer configuration based on the DTX configuration of the network entity, and sending the timer configuration to one or more UEs.

[0026] In some implementations of the methods and apparatuses described herein, the DTX configuration identifies a pattern of an inactive transmission time period of the network entity.

[0027] In some implementations of the methods and apparatuses described herein, the network entity sends the timer configuration via L1 / L2 signaling.

[0028] In some implementations of the methods and apparatuses described herein, the network entity sends the timer configuration to one or more UEs via a broadcast message. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 An example of a wireless communication system is shown that supports aligning UE behavior to network energy saving states in accordance with aspects of the present disclosure.

[0030] Figure 2 An example of a diagram is shown that supports configuring a timer for a UE in accordance with aspects of the present disclosure.

[0031] Figure 3 An example of a diagram is shown that supports configuring another timer for a UE in accordance with aspects of the present disclosure.

[0032] Figure 4 An example of a diagram is shown that supports a UE following a modified active time procedure in accordance with aspects of the present disclosure.

[0033] Figure 5An example of a diagram supporting a UE to follow another modified active time process according to an aspect of the present disclosure is shown.

[0034] Figure 6 An example of a diagram supporting network / cell DTX configuration according to an aspect of the present disclosure is shown.

[0035] Figure 7 An example of a diagram supporting network DTX configuration according to an aspect of the present invention is shown.

[0036] Figure 8 An example of a diagram supporting a UE to follow another modified active time process according to an aspect of the present disclosure is shown.

[0037] Figure 9 An example of a block diagram of a device supporting aligning UE behavior to a network energy saving state according to an aspect of the present disclosure is shown.

[0038] Figure 10 A flowchart of a method supporting modification of DRX behavior of a UE according to an aspect of the present disclosure is shown.

[0039] Figure 11 A flowchart of a method supporting sending timer configuration to one or more UEs according to an aspect of the present disclosure is shown. Detailed Description

[0040] Although the implementation of a network energy consumption model can significantly enable the network to achieve energy saving, such a model may adversely affect the operation and performance of various devices of the network, such as cells (e.g., base stations) and UEs.

[0041] For example, when the network adopts DTX for one or more serving cells, UEs associated with the serving cells may waste energy and resources when remaining in an active reception mode (e.g., not in DRX) (such as monitoring a downlink (DL) channel (e.g., PDCCH channel), initiating a process that will cause a network response (e.g., an L2 process), etc.).

[0042] Currently, the network can configure a (Media Access Control) MAC entity with DRX functionality, and this DRX functionality controls the activity of a UE's physical downlink control channel (PDCCH) monitoring for various MAC entity identifiers. When using DRX operation, the MAC entity can also monitor the PDCCH. For example, when in the RRC_CONNECTED mode, when DRX is configured for all active serving cells, the MAC entity can non - continuously monitor the PDCCH using previously defined DRX operations (e.g., in TS38.213).

[0043] Previous solutions may include changing the DRX configuration of each UE based on the network DTX configuration, which indicates the on / off DTX periods of the network. However, these solutions may result in a significant amount of signaling (e.g., due to changing the DRX configuration of each connected UE in the cell).

[0044] To mitigate these drawbacks, the network may modify UE behavior (e.g., change or modify the DRX configuration of the UE) without signaling support. Instead, the UE adapts its DRX behavior based on the broadcast network / cell DTX configuration. For example, the UE may change or modify a timer (e.g., the drx timer state) based on the provided network / cell DTX configuration. Additionally, UE battery usage may be enhanced or optimized, such as when a UE using the techniques described herein avoids initiating an L2 process that cannot be completed due to the lack of DL signaling during network / cell DTX.

[0045] Accordingly, the network may modify UE behavior without the need to signal to each UE individually, saving network resources and preventing unnecessary execution of UE processes, among other benefits.

[0046] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure are also illustrated and described with reference to device diagrams and flowcharts.

[0047] Figure 1 An example of a wireless communication system 100 that supports aligning UE behavior to network energy-saving states among UEs is shown in accordance with aspects of the present disclosure. The wireless communication system 100 may include one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or include other suitable radio access technologies such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support techniques such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0048] One or more network entities 102 may be dispersed throughout a geographical area to form a wireless communication system 100. The one or more network entities 102 described herein may be or include or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via the Uu interface.

[0049] The network entity 102 may provide a geographical coverage area 112, and the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographical coverage area 112. For example, according to one or more radio access technologies, the network entity 102 and the UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcasting, etc.). In some implementations, the network entity 102 may be movable, such as a satellite associated with a non-terrestrial network. In some implementations, different geographical coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographical coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0050] One or more UEs 104 may be dispersed throughout the geographical area of the wireless communication system 100. The UE 104 may include or may be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, the UE 104 may be referred to as a unit, station, terminal, or client, etc. Additionally, or alternatively, the UE 104 may be referred to as an Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine type communication (MTC) device, etc. In some implementations, the UE 104 may be fixed in the wireless communication system 100. In some other implementations, the UE 104 may be mobile in the wireless communication system 100.

[0051] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1Some examples of the UE 104 are shown. The UE 104 is capable of communicating with various types of devices, such as the network entity 102, other UEs 104, or network devices (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network device), as Figure 1 shown. Additionally, or alternatively, the UE 104 may support communication with other network entities 102 or UEs 104 that may act as relays in the wireless communication system 100.

[0052] The UE 104 is also capable of supporting wireless communication directly with other UEs 104 via the communication link 114. For example, the UE 104 may support wireless communication directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as in a vehicle-to-vehicle (V2V) deployment, a vehicle-to-everything (V2X) deployment, or a cellular V2X deployment, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support wireless communication directly with another UE 104 via the PC5 interface.

[0053] The network entity 102 may support communication with the core network 106, or with another network entity 102, or both. For example, the network entity 102 may be connected to the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The network entities 102 may communicate with each other via the backhaul link 116 (e.g., via X2, Xn, or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other either directly or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, intelligent radio heads, or transmission and reception points (TRPs).

[0054] In some implementations, network entity 102 can be configured in a split architecture that can be configured to utilize a protocol stack physically or logically distributed between two or more network entities 102, such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 102 can include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near-real-time RIC (Near-RT RIC), a non-real-time RIC (Non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0055] The RU can also be referred to as a radio head, an intelligent radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission and reception point (TRP). One or more components of network entity 102 in a split RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a split RAN architecture can be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0056] The division of functions between the CU, DU, and RU can be flexible and can support different functions, depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are to be executed at the CU, DU, or RU. For example, a functional split of the protocol stack can be adopted between the CU and the DU, such that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host higher protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and the one or more DUs or RUs can host lower protocol layers, such as layer 1 (L1) (e.g., the physical (PHY) layer) or L2 (e.g., the radio link control (RLC) layer, the media access control (MAC) layer) functions and signaling, and can each be at least partially controlled by the CU 160.

[0057] Additionally, or alternatively, functional split of the protocol stack can be adopted between the DU and the RU, such that the DU can support one or more layers of the protocol stack, and the RU can support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU can be within a protocol layer (e.g., for some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

[0058] The CU can be further functionally split into a CU control plane (CU-CP) and a CU user plane (CU-UP) function. The CU can be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u), and the DU can be connected to one or more RUs via a fronthaul communication link (e.g., Open fronthaul (FH) interface). In some implementations, the midhaul communication link or the fronthaul communication link can be implemented according to the interface (e.g., channel) between the layers of the protocol stack supported by the respective network entities 102 communicating via such communication links.

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

[0060] The core network 106 can communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 108 can include an application server 118. In some implementations, one or more UEs 104 can communicate with the application server 118. The UE 104 can establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 can use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session can be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0061] In the wireless communication system 100, the network entity 102 and the 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 implementations, the network entity 102 and the UE 104 can support different resource structures. For example, the network entity 102 and the UE 104 can support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 can support a single frame structure. In some other implementations, such as in 5G and in other suitable radio access technologies, the network entity 102 and the UE 104 can support various frame structures (i.e., multiple frame structures). Based on one or more digital technologies, the network entity 102 and the UE 104 can support various frame structures.

[0062] One or more digital technologies can be supported in the wireless communication system 100, and the digital technologies can include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ = 0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technology (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) can utilize one time slot per subframe. The second digital technology (e.g., μ = 1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ = 2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth digital technology (e.g., μ = 3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. The fifth digital technology (e.g., μ = 4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0063] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, e.g., a duration of 10 milliseconds (ms). In some implementations, each frame can include a plurality of subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, e.g., a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0064] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe can include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe can also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz (i.e., μ = 0, μ = 1, μ = 2, μ = 3, μ = 4) can 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 can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots for a subframe can depend on the digital technology. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot can include 12 symbols. For the number of symbols per time slot for both the normal cyclic prefix and the extended cyclic prefix, the relationship between the number of time slots per subframe and the number of time slots per frame can depend on the digital technology. It should be understood that a reference to a first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and time slots.

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

[0066] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ = 0) that includes a 15 kHz subcarrier spacing; a second digital technology (e.g., μ = 1) that includes a 30 kHz subcarrier spacing; and a third digital technology (e.g., μ = 2) that includes a 60 kHz subcarrier spacing. FR2 can be associated with one or more digital technologies (e.g., at least 2 digital technologies). For example, FR2 can be associated with the following: a third digital technology (e.g., μ = 2) that includes a 60 kHz subcarrier spacing; and a fourth digital technology (e.g., μ = 3) that includes a 120 kHz subcarrier spacing.

[0067] As described herein, in some embodiments, a network or cell (e.g., serving cell) can activate a DTX / DRX configuration. For example, the cell DTX / DRX mode can be activated / deactivated via dynamic L1 / L2 signaling and UE-specific RRC signaling. Both UE-specific signaling and common L1 / L2 signaling can be used to activate / deactivate the cell DTX / DRX mode.

[0068] When the access stratum (AS) receives cell DTX / DRX information from the network, the AS notifies the non-access stratum (NAS) of the DTX / DRX time of the network, and the NAS supervises NAS procedures (e.g., registration (update), service request, etc.) based on the DTX / DRX time. Thus, the network applies cell DTX / DRX in the time domain, such as when the UE is in the RRC_CONNECTED state. For example, the gNB may configure periodic cell DTX / DRX, and the gNB may use UE-specific RRC signaling to configure the serving cell.

[0069] In addition, the network may configure the cell DTX mode and the cell DRX mode separately (e.g., one RRC configuration set for DL (downlink) and another RRC configuration set for UL (uplink)) or the cell DTX mode and the cell DRX mode may be configured together. Among other parameters, the following parameters may be part of the cell DTX / DRX configuration: periodicity, start time slot / offset, on-duration, etc.

[0070] As described herein, the network may modify UE behavior (e.g., change or modify the DRX configuration of the UE) without signaling support. The UE adapts its DRX behavior based on the broadcast network / cell DTX configuration. For example, based on the provided network / cell DTX configuration, the UE may change or modify a timer (e.g., the drx timer state).

[0071] Figure 2 An example of FIG. 200 supporting the configuration of a UE's timer according to aspects of the present disclosure is shown. The timing mode 205 includes a series of repeating network / cell periods, including a network on-period 210, followed by a network DTX period 220 (e.g., during which the network does not transmit). As described herein, network / cell DTX generally refers to non-transmission across all channels / signals and / or non-transmission for one or more specific channels / signals.

[0072] The UE includes a timer that controls the duration for which the UE should not expect any PDCCH / PDSCH (physical downlink shared channel) data from the serving cell (e.g., the cell is in the network DTX period 220). As shown, the timer starts when the network / cell moves to DTX (e.g., starts the network DTX period 220).

[0073] In some cases, a new timer is configured and / or maintained for each serving cell, and / or a new timer is configured / maintained for each cell group or MAC entity (e.g., the timer applies to all serving cells belonging to a cell group (e.g., MCG (master cell group) or SCG (secondary cell group))). In some cases, a new timer is configured / maintained for each UE.

[0074] When the timer is running, the UE is in DRX (inactive time) and does not monitor the PDCCH because the network / cell is in DTX and thus does not perform DL transmissions (e.g., PDCCH / PDSCH and / or SSB / CSI-RS (synchronization signal block) / channel state information reference signal) that would be received by the UE. Therefore, the timer is started when the network / cell moves to (or is about to move to) DTX, causing the UE to move to DRX. As shown, when the timer expires, the UE ends DRX and starts receiving DL transmissions, which may occur as the network / cell has moved back to the active transmission mode.

[0075] In some cases, the network / gNB configures a new timer. The network / gNB may send timer configurations, such as configurations indicating or defining a time period during which the network / cell will stop sending data / control / reference symbols in the DL, and how these DTX time periods will repeat with a given configured periodicity (e.g., the periodicity of the time period). The network / cell may use L1 / L2 signaling to indicate to the UE the start time and stop time of the DTX period of the network / cell.

[0076] In some cases, the network may broadcast the DTX mode, and each UE that receives the broadcast may set a new timer value and configuration accordingly. For example, the UE may start a new timer when moving into a DTX period (as Figure 2 shown), where the timer runs for the duration of the DTX period of the network / cell. When the network / cell moves back to the on period (e.g., starts performing DL signal / channel transmissions), the timer stops or expires because the timer configuration is aligned to the network DTX configuration.

[0077] In some cases, when a new timer associated with network / cell DTX starts running (e.g., aligned with the network / cell entering a DTX period), the UE may stop all DRX-related timers. DRX-related timers may include: drx-OndurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, and / or drx-RetransmissionTimerSL. Stopping the DRX-related timers may also stop the active time of the UE, causing the UE to stop monitoring the PDCCH, as defined in TS38.321, and is defined as follows:

[0078] When DRX is configured, the active time for a serving cell in a DRX group includes the time when the following occur:

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

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

[0081] - the ra-ContentionResolutionTimer (as described in Clause 5.1.5) or msgB-ResponseWindow (as described in Clause 5.1.4a) is running; or

[0082] - a scheduling request is sent on the PUCCH and is pending (as described in Clause 5.4.4 or 5.22.1.5). If the serving cell is part of a non-terrestrial network, the active time starts after the scheduling request transmission, which is performed when SR_COUNTER is configured to 0 for all SRs with pending (multiple) SRs plus the UE-gNB RTT; or

[0083] - after successfully receiving a random access response for a random access preamble not selected by the MAC entity in a contention-based random access preamble, a PDCCH indicating a new transmission addressed to the MAC entity's C-RNTI has not been received (as described in Clauses 5.1.4 and 5.1.4a).

[0084] In addition, in some cases, the UE stops all DRX-related timers and resets the timers when a new timer is started, and / or the UE may pause the DRX-related timers when a new timer is running (such as during the DTX period of the network / cell).

[0085] In some embodiments, the timer or timer configuration may be based on, or start from, the network / cell active transmission period. Figure 3 FIG. 300 shows an example of supporting another timer for configuring a UE according to an aspect of the present disclosure.

[0086] With Figure 2Similar to the timing mode 205, the timing mode 305 includes a series of repeating network / cell periods, including a network on period 310, followed by a network DTX period 320 (e.g., the network does not transmit during this period). However, the new timer for the UE controls the duration for which the UE expects the network / cell to be in the "active time" mode and thus sends DL signals to the UE, such as PDCCH / PDSCH or any kind of RS in the serving cell. Thus, in such embodiments, the timer starts when the network / cell enters the network on period 310 and ends or expires when the network switches to the DTX period 320.

[0087] In some cases, the new timer can be configured and / or maintained per serving cell and indicates the duration for which the UE expects the network / cell to be in a non-DTX state in the corresponding serving cell. As described herein, the timer can be configured / maintained for a given cell group or MAC entity (e.g., the timer applies to all serving cells belonging to a cell group (e.g., MCG or SCG)).

[0088] In some embodiments, for the duration that the new timer is running, the UE follows the DRX procedure (e.g., defined in TS38.321). For example, considering the grants / allocations / DRX command MAC CE / long DRX command MAC CE received and the scheduling requests sent when evaluating all DRX active time conditions (e.g., checking whether the drx-related timers are running in the time slot) specified in the DRX procedure, the UE determines when the MAC entity is in the active time for a given time slot.

[0089] Figure 4 An example of FIG. 400 supporting a UE to follow a modified active time procedure according to aspects of the present disclosure is shown. As described herein, the network timing mode 405 includes a series of repeating network / cell periods, including a network on period 410, followed by a network DTX period 415 (e.g., the network does not transmit during this period).

[0090] The first UE configured with the legacy procedure follows the DRX configuration 420, where a series of active reception periods 425 (e.g., an on-duration period, followed by an extended active time period) are not aligned with the network DTX configuration / cell DTX configuration. Instead, the UE configured with one or more timers (e.g., the new timer) described herein implements and / or follows the active time configuration 430, which has a series of active reception periods 435 aligned with the network / cell network on period 410.

[0091] Figure 5FIG. 500 illustrates an example of a figure supporting a UE to follow another modified active time process according to aspects of the present disclosure. As described herein, network timing pattern 505 includes a series of repeating network / cell periods, including network on periods 510, followed by network DTX periods 515 (e.g., during which the network does not transmit).

[0092] A first UE configured with a legacy process follows DRX configuration 520, where a series of active reception periods 525 (e.g., on-duration periods, followed by extended active time periods) are not aligned to the network's DTX configuration / cell DTX configuration (e.g., the periods extend into the network's DTX). In contrast, a UE that has been configured with one or more timers (e.g., new timers) described herein implements and / or follows active time configuration 530, which has a series of active reception periods 535 aligned to the network / cell network on periods 510. For example, the duration of the active reception periods 535 can be shorter to avoid starting before the start of the network / cell's active transmission period.

[0093] In some cases, when the new timer is not running (e.g., the network / cell is in an inactive time / DTX), such as when the timer controls the period during which the network / cell is in active transmission, the UE / MAC may not be in the active time within the time slot.

[0094] In some cases, when the new timer controlling the non-DTX period of the network / cell expires or ends (e.g., when the network / cell moves into DTX), the UE stops all DRX-related timers. Timers that can be stopped as described herein include drx-OnDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, and drx-RetransmissionTimerSL. When the timer is stopped, the active time of the UE stops, and the UE stops monitoring the PDCCH.

[0095] In some cases, the UE will stop all DRX-related timers and reset them when the new timer expires, and / or pause the DRX-related timers when the new timer controlling the DRX duration of the network / cell is not running.

[0096] In addition, in some cases, the network / gNB configures timers according to the NES configuration. The network can configure a mode that defines the period during which the network will stop transmitting control / data and / or reference symbols (e.g., or any type of DL transmission), such as where the period (e.g., DTX period) repeats with a given configured periodicity, as described herein.

[0097] As described herein, the network determines the network / cell DTX configuration, such as before activating the NES mode. Figure 6 An example of FIG. 600 supporting network / cell DTX configuration in accordance with aspects of the present disclosure is shown. The DTX configuration 605 can include repeating DTX periods, including a cell transmission on period 610 (e.g., where the cell is actively transmitting) and a cell transmission off period 620 (e.g., where the cell is not actively transmitting or is in DRX).

[0098] In some cases, the network / cell signals the cell DTX configuration 605 to each UE, which is applicable when activating energy savings using dedicated RRC signaling or broadcast signaling. In some cases, the DTX configuration can be a set of DRX parameters. Similar to the DRX configuration associated with conventional DRX operation, the DTX configuration 605 can include a DTX cycle that includes a cell transmission on period 610 and a cell transmission off period 620.

[0099] For example, the cell transmission on period 610 (e.g., “NW on Duration” or “NES_onDuration” defined in milliseconds) can be the period during which the network circuitry will operate or is operating, and the network transmits via the DL channel / signal. Thus, the on and off / DTX durations together form the network DTX duration (e.g., DTX configuration 605), and each DTX cycle period (e.g., configured by RRC) repeats.

[0100] In some cases, the network can use a parameter indicating an offset to a reference point such as a subframe boundary to control the start position of the DTX cycle. When the DTX cycle starts, network transmission is activated for a preconfigured duration (such as “NES-onDuration”). For example, a new timer (e.g., drx-onDurationTimerNES) is set to the value “NES-onDuration” configured within the network / cell DTX configuration.

[0101] As described herein, when a new timer (e.g., drx_onDurationTimerNES) is running, the UE will apply the legacy DRX process and determine whether a time slot is in the active time based on the status of the drx-related timer and the signals received from the network (e.g., grant / DRX control command) or the signals transmitted on the uplink (e.g., SR). In some cases, the network / cell on-duration (e.g., the time period when drx_onDurationTimerNES is running) is not dynamically extended (e.g., by the transmission of PDCCH / DCI (downlink control information)). Therefore, even if the network sends PDCCH / PDSCH at the end or near the end of the on-duration (e.g., only before the network moves to the DTX period), the UE will not extend the active time (e.g., the network on-duration is not extended).

[0102] In some embodiments, the UE or the MAC entity maintains two active times, one active time is managed by the legacy DRX process (e.g., the status of the drx-related timer), and an additional active time is controlled by the network DTX configuration (e.g., controlled by a new timer introduced for network energy saving as described herein). This additional active time (e.g., referred to as NW_active time) represents the on-duration of the UE when the network is transmitting via the DL channel.

[0103] The UE active time (as determined by the legacy DRX process) can be a subset of the NW_active time and the legacy UE active time, or shorter than the NW_active time and the legacy UE active time. Therefore, the UE can only be in the active time during the NW_active time. For example, as described herein, the NW_active time is a configured semi-static mode and cannot be dynamically extended in some cases.

[0104] In some embodiments, the network dynamically extends the network on-time (e.g., by means of PDCCH / DCI, the time period when the network is transmitting via the DL channel). Figure 7 FIG. 700 shows an example of FIG. 700 supporting network DTX configuration 705 according to an aspect of the present disclosure. The DTX configuration 705 includes a network on-duration 710, followed by an extended on-duration 715, and then a network DRX period 720.

[0105] For example, during the network on-time (e.g., NW_active time), such as when a first timer (e.g., drx-OndurationTimerNES) is running, the UE starts a second timer in response to receiving DCI (e.g., a predefined DCI format). As another example, the second timer (e.g., drx-InactivityTimerNES) is configured according to the network DTX configuration.

[0106] In some embodiments, the DCI that triggers the start of the second timer and extends the network on-duration (e.g., NW_Active Time) is a new DCI format monitored by all UEs in the cell. The DCI that triggers the start of drx-InactivityTimerNES is a DCI addressed to a new RNTI, which can be a group common RNTI, such as NES-RNTI. The new DCI format or DCI addressed to a new RNTI (e.g., NES-RNTI) may not allocate resources (e.g., for PDSCH), but is used to extend the network on-duration (e.g., NE_Active Time).

[0107] In some cases, not every PDCCH that receives and schedules an initial transmission during the NW-Active Time extends the NW-Active Time. Only the PDCCH / DCI addressed to a new RNTI (Radio Network Temporary Identifier), or a new DCI format, or a DCI with a field set to a specific predefined value can trigger the start of drx-InactivityTimerNES.

[0108] In some embodiments, the UE may disable the DRX configuration configured for the UE and follow the network DTX mode / configuration provided by broadcast or dedicated signaling. The UE may monitor the PDCCH (e.g., Active Time) during the period when the network is in the on state (e.g., performing DL channel / signal transmission), and the UE does not monitor the PDCCH (e.g., DRX state) during the period when the network is in the DTX state (e.g., not performing DL channel / signal transmission). For example, when the network / cell provides a network DTX configuration, the UE autonomously disables or considers itself not to be configured with a DRX configuration.

[0109] In some embodiments, the UE starts the drx-On Duration timer at the start of the network on-duration. The UE may not follow its configured DRX cycle, but instead follow the cycle provided by the network DTX configuration (e.g., start the drx-On Duration timer at the start of each network on-duration). Thus, the drx timer values are maintained (e.g., only the start of the drx-On Duration timer is shifted), and the start of the DRX cycle is aligned with the network on-duration.

[0110] Figure 8 An example of FIG. 800 supporting a UE to follow another modified active time process according to aspects of the present disclosure is shown. As described herein, the network timing mode 805 includes a series of repeating network / cell periods, including a network on-period 810, followed by a network DTX period 815 (e.g., during which the network does not transmit).

[0111] A first UE configured with a legacy process follows a DRX configuration 820, where a series of active reception periods 825 (e.g., an on-duration period followed by an extended active time period) are not aligned with the network's DTX configuration / cell DTX configuration (e.g., the periods are extended into the network's DTX). Instead, a UE with a DRX cycle aligned with the network on-period 810 implements and / or follows an active time configuration 830 with a series of active reception periods 835 aligned with the network / cell network on-period 810.

[0112] In some embodiments, the UE may switch to a dormant bandwidth part (BWP) configured for the serving cell during a network-off / DTX period. When the network moves from a network-off / DTX state to an on state, the UE may switch back to the active BWP as previously configured. For example, the UE stores the previously active BWP before entering the dormant BWP and autonomously switches to that BWP when leaving the dormant BWP.

[0113] As another example, the UE may switch to the BWP (e.g., DL BWP) indicated by firstOutsideActiveTimeBWP-Id or by firstWithinActiveTimeBWP-Id when leaving the dormant BWP. For example, new triggers for entering and leaving the dormant BWP of the serving cell are defined based on the network moving from an on state to a network-off / DTX state and / or from a network-off / DTX state to an on state. In some cases, the UE switching to the dormant BWP when the network is in DTX means that the UE / MAC does not monitor the PDCCH or receive any DL data transmissions on the PDSCH, nor does it perform any uplink transmissions.

[0114] In some cases, it is beneficial not to allow UL transmissions, such as for cases where it is desired that the gNB turns off all transmissions and receptions for data traffic and / or reference signals during a network DTX inactive period (e.g., where the network is in a DTX and DRX state).

[0115] In some cases, there may be different levels of energy saving for a cell, such as only disabling DL transmissions on certain / all DL channels / signals, or also disabling the reception of UL transmissions. It may be assumed that the network notifies the UEs being served in the corresponding cell about the energy saving configuration currently being (or to be) used in the cell.

[0116] Currently, the dormant BWP configuration is only supported for SCell (e.g., the dormant BWP configuration for SpCell or PUCCH SCell is not supported). However, the dormant BWP can also be supported for PCell / SpCell or PUCCH SCell. Additionally, when switching to the dormant BWP, the UE may not clear any configured downlink allocations and any configured uplink authorizations of type 2 associated with the cell.

[0117] In some embodiments, the UE may apply the same behavior on the current active BWP as when the BWP is a dormant BWP. The UE may not switch the BWP when entering / leaving the network DTX period, but instead may consider the current active BWP as dormant.

[0118] In some embodiments, the UE may consider the cell as temporarily deactivated during the period when the network is in the DTX state for the cell (e.g., SCell or PCell / sPCell). When temporarily deactivating the cell, the UE may not clear any configured downlink allocations and any configured uplink authorizations of type 2 associated with the cell (e.g., SPS and CG allocations / configurations may be maintained and only suspended).

[0119] The UE may also maintain the PUSCH resources configured for semi-persistent CSI reporting associated with the cell. Additionally, when the cell is temporarily deactivated due to network DTX / DRX, the UE may also maintain the content of the HARQ (Hybrid Automatic Repeat reQuest) buffer (e.g., not flush the HARQ buffer).

[0120] In some embodiments, when the network is in the DTX / DRX state for the corresponding cell, the UE may be in a state associated with the UE's behavior, called the cell state. This new state may be a state in addition to the already defined cell states, and the cell state is the active state. In some cases, the field / parameter cell state may be applied to PCell / PScell as well as SCell. When the network is in the off / DTX / DRX state for the corresponding cell, the new cell state, which can be the NES state, defines the UE behavior.

[0121] For example, during the period when the network / gNB is in the DTX / DRX state (e.g., not sending any / some DL channels / signals and / or not receiving any UL transmissions), the UE autonomously sets the cell state to the "NES_state". The UE behavior in the new cell state "NES state" may include:

[0122] No transmission is performed on the uplink shared channel (UL-SCH) on the BWP; no transmission is performed on the radio access channel (RACH) on the BWP; no monitoring of PDCCH is performed on the BWP; no transmission of PUCCH is performed on the BWP; no CSI for the BWP is reported; no transmission of sounding reference signal (SRS) is performed on the BWP; no reception of the downlink shared channel DL-SCH is performed on the BWP; any configured downlink allocation of authorization type 2 and configured uplink authorization on the BWP are suspended; any configured uplink authorization of authorization type 1 on the inactive BWP is suspended; and so on.

[0123] In some embodiments, the UE does not initiate a random access procedure (RACH) procedure triggered for a situation where the random access response window overlaps (at least partially) with the network DTX / off duration. If the RACH procedure is triggered (e.g., to request UL resources or triggered by a PDCCH command or beam failure recovery (BFR)), the UE checks whether the RAR window falls within the duration of the network DTX.

[0124] For the case where the RAR window overlaps (partially) with the network DTX duration, the UE does not initiate the RACH procedure (e.g., the UE does not perform RACH preamble transmission). For example, for the case where the contention resolution window falls within the network DTX period, the UE does not initiate the (triggered) RACH procedure.

[0125] In some cases, the UE determines whether the RACH preamble transmission resource (for initial RACH preamble transmission) occurs at least a certain predetermined time offset before the start of the network DTX period for a situation such as when the RACH procedure is triggered. Thus, the UE can perform the RACH procedure only when the time offset is greater than a predetermined threshold.

[0126] In some embodiments, for the case where the duration / offset between the D-SR resource on the PUCCH and the start of the next network DTX period is less than a preconfigured threshold, the UE may not send the triggered SR (initial transmission of SR) on the PUCCH. For example, the threshold is configured by higher layer signaling.

[0127] For the case where the SR transmission on the PUCCH is not performed, the UE may not increment the SR transmission counter. In this case, when the network DTX period immediately follows the SR transmission, the UE sends the SR on the PUCCH (e.g., the network cannot schedule UL resources for the transmission of the buffer status report (BSR)). In this case, the network may postpone the DTX state and send DL information (e.g., DCI) to the UE. In parallel, the UE may not immediately stop receiving on the DL channel.

[0128] Figure 9 FIG. 900 is an example of a block diagram of a device 902 that supports aligning UE behavior to a network energy saving state in accordance with aspects of the present disclosure. The device 902 may be an example of the network entity 102 or the UE 104 as described herein. The device 902 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 902 may include components for two-way communication, including components for sending as well as receiving communication, such as a processor 904, a memory 906, a transceiver 908, and an I / O controller 910. These components may communicate electronically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0129] The processor 904, the memory 906, the transceiver 908, or various combinations or various components thereof may be examples of components for performing various aspects of the present disclosure as described herein. For example, the processor 904, the memory 906, the transceiver 908, or various combinations or components thereof may support a method for performing one or more operations described herein.

[0130] In some implementations, the processor 904, the memory 906, the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., as a communication management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of components configured to or otherwise support performing the functions described in the present disclosure. In some implementations, the processor 904 and the memory 906 coupled to the processor 904 may be configured to perform one or more functions described herein (e.g., the processor 904 executes instructions stored in the memory 906).

[0131] For example, in accordance with an example disclosed herein, the processor 904 may support wireless communication at the device 902. The processor 904 may be configured to or otherwise support components for: receiving a first configuration from the network entity based on a DTX configuration of the network entity, where the first configuration includes: a first timer for controlling an active duration at the start of a cell DTX cycle; receiving a second configuration associated with a DRX behavior of the UE from the network entity, where the second configuration includes a set of timers; and determining whether to monitor a PDCCH based at least in part on a state of the first timer and a state of the set of timers.

[0132] As another example, according to the examples disclosed herein, the processor 904 may support wireless communication at the device 902. The processor 904 may be configured to or otherwise support components for: generating a timer configuration based on a DTX configuration of a network entity; and sending the timer configuration to one or more UEs.

[0133] The processor 904 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 904 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 904. The processor 904 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 906) to cause the device 902 to perform various functions of the present disclosure.

[0134] The memory 906 may include random access memory (RAM) and read-only memory (ROM). The memory 906 may store computer-readable, computer-executable code including instructions that, when executed by the processor 904, cause the device 902 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. In some implementations, the code may not be directly executable by the processor 904, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 906 may also include a basic input / output system (BIOS) that may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0135] The I / O controller 910 may manage input and output signals for the device 902. The I / O controller 910 may also manage peripheral devices not integrated into the device M02. In some implementations, the I / O controller 910 may represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 910 may utilize an operating system such as or another known operating system. In some implementations, the I / O controller 910 may be implemented as part of a processor (such as processor M06). In some implementations, a user may interact with the device 902 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0136] In some implementations, device 902 may include a single antenna 912. However, in some other implementations, device 902 may have more than one antenna 912 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 908 may communicate bidirectionally via one or more antennas 912 (such as the wired or wireless links described herein). For example, transceiver 908 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 908 may also include a modem to modulate packets to provide modulated packets to one or more antennas 912 for transmission, and to demodulate packets received from one or more antennas 912.

[0137] Figure 10 A flowchart of a method 1000 for modifying DRX behavior of a UE in support of aspects of the present disclosure is shown. Operations of method 1000 may be implemented by a device or components thereof as described herein. For example, operations of method 1000 may be performed by a UE as described with reference to Figures 1 to 8 the UE described. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0138] At 1005, the method may include receiving a first configuration from the network entity based on the DTX configuration of the network entity, where the first configuration includes: a first timer that controls an active duration at the start of a cell DTX cycle. The operation of 1005 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1005 may be performed by a device as described with reference to Figure 1 the device described.

[0139] At 1010, the method may include: receiving a second configuration associated with the DRX behavior of the UE from the network entity, where the second configuration includes a set of timers. The operation of 1010 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1010 may be performed by a device as described with reference to Figure 1 the device described.

[0140] At 1015, the method may include: determining whether to monitor the PDCCH based at least in part on the state of the first timer and the state of the set of timers. The operation of 1015 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1010 may be performed by a device as described with reference to Figure 1 the device described.

[0141] Figure 11FIG. 1000 is a flow chart showing a method 1000 for supporting sending timer configurations to one or more UEs in accordance with aspects of the present disclosure. Operations of method 1100 may be implemented by a device or components thereof as described herein. For example, operations of method 1100 may be performed by a network entity as referenced Figures 1 to 8 described. In some implementations, a device may execute a set of instructions to control functional elements of the device to perform the functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the functions.

[0142] At 1105, the method may include generating a timer configuration based on the DTX configuration of the network entity. The operation of 1105 may be performed in accordance with examples described herein. In some implementations, aspects of the operation of 1105 may be performed by a device as referenced Figure 1 described.

[0143] At 1110, the method may include sending the timer configuration to one or more UEs. The operation of 1110 may be performed in accordance with examples described herein. In some implementations, aspects of the operation of 1105 may be performed by a device as referenced Figure 1 described.

[0144] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Additionally, aspects from two or more methods may be combined.

[0145] The various illustrative blocks and components described in connection with the present disclosure may be implemented or performed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0146] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions can also be physically located in various positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0147] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor.

[0148] Any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0149] As used herein (including in the claims), the "or" used in a list of items (e.g., a list of items beginning with phrases such as "at least one of...", or "one or more of...", or "one or both of...") indicates an inclusive list, such that a list of at least one of A, B, or C, for example, means A, or B, or C, or AB, or AC, or BC, or ABC (i.e., A, and B, and C). Also, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, without departing from the scope of the present disclosure, an example step described as "based on condition A" can 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". Further, as used herein (including in the claims), a "set" can include one or more elements.

[0150] When referring to network entities, the terms "send", "receive", or "communicate" can refer to any part of a network entity of a RAN (e.g., a base station, a CU, a DU, an RU) communicating with another device (e.g., directly or via one or more other network entities).

[0151] The description set forth herein in conjunction with the drawings describes example configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "superior to other examples". The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, the techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0152] The description herein is provided to enable a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to a person of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded 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 the at least one memory and configured to cause the UE to: Receive a first configuration from the network entity based on a discontinuous transmission (DTX) configuration of the network entity, wherein the first configuration includes: a first timer that controls an active duration at the start of a cell DTX period; Receive a second configuration from the network entity associated with the discontinuous reception (DRX) behavior of the UE, wherein the second configuration includes a set of timers; and Determine whether to monitor a physical downlink control channel (PDCCH) at least in part based on the state of the first timer and the state of the set of timers.

2. The UE according to claim 1, wherein the DTX configuration identifies an active transmission time period of the network entity.

3. The UE according to claim 1, wherein the first timer includes a cell-specific on-duration timer.

4. The UE according to claim 1, wherein the processor is configured to cause the UE to: determine whether to monitor the PDCCH at least in part based on whether the first timer is running.

5. The UE according to claim 1, wherein the processor is configured to cause the UE to: determine whether to monitor the PDCCH at least in part based on whether the UE is in an active time according to the second configuration.

6. The UE according to claim 1, wherein the processor is configured to cause the UE to: determine whether to monitor the PDCCH at least in part based on whether the UE is in a DRX active time according to the second configuration.

7. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured to cause the processor to: Receive a first configuration from the network entity based on a discontinuous transmission (DTX) configuration of the network entity, wherein the first configuration includes: a first timer that controls an active duration at the start of a cell DTX period; Receive a second configuration from the network entity associated with the discontinuous reception (DRX) behavior of the processor, wherein the second configuration includes a set of timers; and Determine whether to monitor a physical downlink control channel (PDCCH) at least in part based on the state of the first timer and the state of the set of timers.

8. The processor according to claim 7, wherein the DTX configuration identifies an active transmission time period of the network entity.

9. The processor according to claim 7, wherein the first timer includes a cell-specific on-duration timer.

10. The processor according to claim 7, wherein the controller is configured to cause the processor to: determine whether to monitor the PDCCH at least in part based on whether the first timer is running.

11. The processor according to claim 7, wherein the controller is further configured to cause the processor to determine whether to monitor the PDCCH at least in part based on whether the processor is in an active time according to the second configuration.

12. The processor according to claim 7, wherein the controller is configured to cause the processor to determine whether to monitor the PDCCH at least in part based on whether the processor is in an active time according to the second configuration.

13. A network entity for wireless communication, comprising: at least one memory; and at least one processor, coupled to the at least one memory and configured to cause the network entity to: generate a timer configuration based on a discontinuous transmission (DTX) configuration of the network entity; and send the timer configuration to one or more user equipments (UEs).

14. The network entity according to claim 13, wherein the DTX configuration identifies a pattern of an inactive transmission time period of the network entity.

15. The network entity according to claim 13, wherein the network entity sends the timer configuration via L1 / L2 signaling.

16. The network entity according to claim 13, wherein the network entity sends the timer configuration to the one or more UEs via a broadcast message.

17. A method performed by a network entity, the method comprising: generating a timer configuration based on a discontinuous transmission (DTX) configuration of the network entity; and sending the timer configuration to one or more user equipments (UEs).

18. The method according to claim 17, wherein the DTX configuration identifies a pattern of an inactive transmission time period of the network entity.

19. The method according to claim 17, wherein the network entity sends the timer configuration via L1 / L2 signaling.

20. The method according to claim 17, wherein the network entity sends the timer configuration to the one or more UEs via a broadcast message.

Images