Discontinuous transmission and reception between network entities

Abstract

Systems and techniques for wireless communication are provided. A first network entity (e.g., user equipment (UE)) may receive information indicating a first discontinuous reception (DRX) configuration and information indicating a second DRX configuration. The first DRX configuration indicates a first DRX ON duration of the first network entity. The one or more DRX configuration parameter values of the second DRX configuration are different from the one or more DRX configuration parameter values of the first DRX configuration. A first network entity determines a discontinuous transmission (DTX) enable state of a second network entity (e.g., a base station, such as a gNodeB (gNB)). The DTX enable state corresponds to a DTX enable duration of the second network entity. The first DRX ON duration is within the DTX ON duration of the second network entity. The first network entity receives downlink information from the second network entity during the first DRX ON duration.

Description

TECHNICAL FIELD

[0001] Aspects of the disclosure generally relate to wireless communication. In some implementations, examples of discontinuous transmission (DTX) and discontinuous reception (DRX) between network entities are described. BACKGROUND

[0002] Wireless communication systems are deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These wireless communication systems have evolved over the generations including first-generation analog wireless phone services (1G), second-generation (2G) digital wireless phone services including transitional 2.5G networks, third-generation (3G) Internet-capable high-speed data wireless services, fourth-generation (4G) services (e.g., Long Term Evolution (LTE), WiMax) and fifth-generation (5G) services (e.g., New Radio (NR)). There are many different types of wireless communication systems in use today including cellular systems and personal communication service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the global system for mobile communications (GSM), etc. SUMMARY

[0003] The following presents a simplified summary relating to one or more aspects disclosed herein. As such, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be deemed to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary is merely presented in a simplified form conceptual aspects relating to one or more aspects disclosed herein.

[0004] Systems, methods, apparatuses, and computer readable media for performing wireless communications are disclosed. According to at least one example, a first network entity for wireless communication is provided. The first network entity includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to: receive information indicating a first discontinuous reception (DRX) configuration for the first network entity, wherein the first DRX configuration indicates a first DRX on-duration for the first network entity; receive information indicating a second DRX configuration for the first network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determine a discontinuous transmission (DTX) enable state for a second network entity, wherein the DTX enable state corresponds to a DTX on-duration for the second network entity, and wherein the first DRX on-duration is within the DTX on-duration for the second network entity; and receive downlink information from the second network entity during the first DRX on-duration.

[0005] In another illustrative example, a method of wireless communication at a first network entity is provided. The method includes receiving information indicating a first discontinuous reception (DRX) configuration for the first network entity, wherein the first DRX configuration indicates a first DRX on-duration for the first network entity; receiving information indicating a second DRX configuration for the first network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determining a discontinuous transmission (DTX) enable state for a second network entity, wherein the DTX enable state corresponds to a DTX on-duration for the second network entity, and wherein the first DRX on-duration is within the DTX on-duration for the second network entity; and receiving downlink information from the second network entity during the first DRX on-duration.

[0006] In another illustrative example, a non-transitory computer-readable storage medium includes instructions stored thereon that, when executed by at least one processor, cause the at least one processor to: receive information indicating a first discontinuous reception (DRX) configuration for a first network entity, wherein the first DRX configuration indicates a first DRX on-duration for the first network entity; receive information indicating a second DRX configuration for the first network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determine a discontinuous transmission (DTX) enabled state for a second network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the second network entity, and wherein the first DRX on-duration is within the DTX on-duration for the second network entity; and receive downlink information from the second network entity during the first DRX on-duration.

[0007] In another illustrative example, an apparatus for wireless communication at a first network entity is provided. The apparatus includes means for receiving information indicating a first discontinuous reception (DRX) configuration for the first network entity, wherein the first DRX configuration indicates a first DRX on-duration for the first network entity; means for receiving information indicating a second DRX configuration for the first network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; means for determining a discontinuous transmission (DTX) enabled state for a second network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the second network entity, and wherein the first DRX on-duration is within the DTX on-duration for the second network entity; and means for receiving downlink information from the second network entity during the first DRX on-duration.

[0008] In another illustrative example, a first network entity for wireless communication is provided. The first network entity includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to transmit information indicating a first discontinuous reception (DRX) configuration for a second network entity, wherein the first DRX configuration indicates a first DRX on duration for the second network entity, transmit information indicating a second DRX configuration for the second network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration, determine a discontinuous transmission (DTX) enabled state for the first network entity, wherein the DTX enabled state corresponds to a DTX on duration for the first network entity, and wherein the first DRX on duration is within the DTX on duration for the first network entity, and transmit downlink information to the second network entity during the first DRX on duration.

[0009] In another illustrative example, a method of wireless communication at a first network entity is provided. The method includes transmitting information indicating a first discontinuous reception (DRX) configuration for a second network entity, wherein the first DRX configuration indicates a first DRX on duration for the second network entity, transmitting information indicating a second DRX configuration for the second network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration, determining a discontinuous transmission (DTX) enabled state for the first network entity, wherein the DTX enabled state corresponds to a DTX on duration for the first network entity, and wherein the first DRX on duration is within the DTX on duration for the first network entity, and transmitting downlink information to the second network entity during the first DRX on duration.

[0010] In another illustrative example, a non-transitory computer-readable storage medium includes instructions stored thereon that, when executed by at least one processor, cause the at least one processor to: transmit information indicating a first discontinuous reception (DRX) configuration for a second network entity, wherein the first DRX configuration indicates a first DRX on-duration for the second network entity; transmit information indicating a second DRX configuration for the second network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determine a discontinuous transmission (DTX) enabled state for the first network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the first network entity, and wherein the first DRX on-duration is within the DTX on-duration for the first network entity; and transmit downlink information to the second network entity during the first DRX on-duration.

[0011] In another illustrative example, an apparatus for wireless communication at a first network entity is provided. The apparatus includes means for transmitting information indicating a first discontinuous reception (DRX) configuration for a second network entity, wherein the first DRX configuration indicates a first DRX on-duration for the second network entity; means for transmitting information indicating a second DRX configuration for the second network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; means for determining a discontinuous transmission (DTX) enabled state for the first network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the first network entity, and wherein the first DRX on-duration is within the DTX on-duration for the first network entity; and means for transmitting downlink information to the second network entity during the first DRX on-duration.

[0012] Aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, wireless communication device, and / or processing system as substantially described herein with reference to and as illustrated by the accompanying drawings and specification.

[0013] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions are not to be considered as departing from the scope of the appended claims. The

[0014] While aspects are described in the disclosure by illustration to some examples, those skilled in the art will understand that such aspects can be practiced in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features can include additional components and features for implementation and practice of the claimed and described aspects. For example, transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying size, shape, and constitution.

[0015] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description. This summary is intended to identify certain concepts rather than to limit the scope of the claimed subject matter. The subject matter should be understood from a reading of the entire specification, including the proper aspects of the figures, any or all drawings, and claims.

[0016] The foregoing and other features and aspects will be better understood with reference to the following specification, the claims, and the appended drawings. BRIEF DESCRIPTION OF DRAWINGS

[0017] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of various aspects.

[0018] Figure 1 is a block diagram illustrating an example of a wireless communication network in accordance with some examples;

[0019] Figure 2 is a diagram illustrating a design of a base station and user equipment (UE) device that enables transmission and processing of signals exchanged between the UE and the base station in accordance with some examples;

[0020] Figure 3 is a diagram illustrating an example of a disaggregated base station in accordance with some examples;

[0021] Figure 4 is a block diagram illustrating components of a user equipment (UE) in accordance with some examples;

[0022] Figure 5 is a diagram illustrating an example of physical channels and reference signals in a wireless network in accordance with some examples;

[0023] Figure 6A is a diagram illustrating an example of aligned user equipment (UE) discontinuous reception (DRX) configurations in accordance with some examples;

[0024] Figure 6B is a diagram illustrating an example of unaligned UE DRX configurations in accordance with some examples;

[0025] Figure 7 is a flow diagram illustrating an example of a process for wireless communication in accordance with some examples;

[0026] Figure 8 is a flow diagram illustrating another example of a process for wireless communication in accordance with some examples; and

[0027] Figure 9 is a block diagram illustrating an example of a computing system in accordance with some examples. DETAILED DESCRIPTION

[0028] For illustrative purposes, certain aspects of the present disclosure are provided below. Alternate aspects can be devised without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure, related to those items not specifically described herein, can be omitted or replaced by equivalents known to those skilled in the art for the purposes of this disclosure. Some aspects described herein can be applied independently of one another, and some of them can be combined together in various manners. It will be apparent to those skilled in the art that the various aspects described herein can be practiced without these specific details. The drawings and description are not intended to be limiting.

[0029] The following description provides example aspects only, and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the following description of the example aspects will provide those skilled in the art with an enabling description for implementing an example aspect. It is to be understood that various changes can be made in the function and arrangement of elements without departing from the scope of the application as set forth in the appended claims.

[0030] Wireless communication networks can be deployed to provide various communication services, such as voice, video, packet data, messaging, broadcast, any combination thereof, or other communication services. Wireless communication networks can support both access links and sidelinks for communication between wireless devices. An access link can refer to any communication link between a client device (e.g., a user equipment (UE), a station (STA), or other client device) and a base station (e.g., a 3GPP gNB for 5G / NR, a 3GPP eNB for 4G / LTE, a Wi-Fi access point (AP), or other base station). For example, an access link can support uplink signaling, downlink signaling, connection procedures, and the like. An example of an access link is a Uu link or interface (also referred to as NR-Uu) between a 3GPP gNB and a UE.

[0031] The energy efficiency of wireless communications between a client device (e.g., a UE, etc.) and a base station (e.g., a gNB, etc.) can vary based on a variety of different factors. As used herein, the “energy efficiency” associated with wireless communications at a UE or base station can be referred to interchangeably as the “power consumption” associated with wireless communications at the UE or base station.

[0032] The power consumption for wireless communications can include power consumption associated with transmitting wireless signals and power consumption associated with receiving wireless signals. For example, UE power consumption can include power consumption associated with the UE actively transmitting wireless signals (e.g., to a base station or gNB) and power consumption associated with the UE actively receiving wireless signals (e.g., from a base station or gNB).

[0033] In addition to the power consumption associated with active transmission or reception, a UE also consumes power while in an active or "on" state in which the UE is configured to continuously prepare to transmit or receive data. For example, a UE consumes power while waiting to receive data from a base station or gNB even when the base station or gNB is not transmitting data. The UE remains in a continuously awake state in order to decode downlink data because data in the downlink can arrive at any time. The UE can monitor a physical downlink control channel (PDCCH) in every subframe to check whether the PDCCH is available to schedule or otherwise indicate downlink data for the UE. The UE can consume a large portion of the available power at the UE (e.g., a large portion of the available battery power at the UE) while continuously monitoring the PDCCH for possible downlink (DL) and / or uplink (UL) data.

[0034] In some cases, power saving techniques can be implemented for a client device, a base station, and / or a combination of both. Some power saving techniques are based on managing the energy efficiency or energy consumption of various periodic communications between a UE and a base station. For example, discontinuous reception (DRX) can be used to configure PDCCH periodic monitoring, where a UE wakes up to monitor for downlink data during periodic DRX on states and enters a low-power sleep or idle mode outside of the periodic DRX on states (e.g., during DRX off states). Discontinuous transmission (DTX) can be used to configure periodic transmission of uplink signals by a UE (e.g., during periodic DTX on states), where the UE enters a low-power sleep or idle mode outside of the periodic DTX on states (e.g., during DTX off states).

[0035] In some cases, DRX implemented by a UE can also be referred to as connected mode DRX and can be used to improve UE battery power consumption based on the UE periodically entering a "sleep" state for a "turn-off duration" during which the UE does not monitor a PDCCH. To monitor for possible downlink / uplink data of the PDCCH, the UE can be configured to periodically wake up and remain in an "awake" state for an "on duration." DRX implemented by a UE can also be referred to as "UE-DRX."

[0036] In some cases, DRX can be implemented by a base station or gNB as an energy saving mode for discontinuous reception of UE uplink transmissions by the base station or gNB. DRX implemented by a base station or gNB can also be referred to as "cell DRX" and / or "cellular DRX." When cell DRX is enabled, a gNB can stop monitoring for UL transmissions from UEs associated with a cell that is currently in a cell DRX off state.

[0037] In some cases, the UE can generate and transmit one or more UL transmissions during a UE-DRX ON state (e.g., an ON duration of a UE-DRX cycle) and / or during a UE-DRX OFF state (e.g., an OFF duration of a UE-DRX cycle). For example, the UE can transmit periodic channel state information (CSI) or sounding reference signals (SRS) (e.g., among various other signals and / or transmissions), which can cause the base station to allocate resources to monitor for CSI or SRS transmissions from the UE.

[0038] When cell DRX is enabled, the base station or gNB will receive UL transmissions from the UE that arrive during a cell-DRX ON state (e.g., an ON duration of a cell-DRX cycle). The base station or gNB will not receive UL transmissions from the UE that arrive during a cell-DRX OFF state (e.g., an OFF duration of a cell-DRX cycle).

[0039] Cell DRX and UE-DRX can be separately enabled, implemented, and / or configured. Systems and techniques are needed that can be used to coordinate, configure, and / or control DTX and DRX implemented by various network entities. For example, systems and techniques are needed that can be used to align cell DRX with UE-DRX. For example, when a cell-DRX cycle is aligned with one or more UE-DRX cycles, the base station can allocate resources to other UEs to maximize or increase resource utilization by the base station. Systems and techniques are also needed that can be used to align a UE-DRX cycle with a corresponding cell DTX cycle of a base station or gNB. Systems and techniques are needed that can be used to implement a UE-DRX configuration based on cell DTX information.

[0040] Systems, apparatuses, processes (also referred to as methods), and computer- readable media (collectively referred to as “systems and techniques”) are described herein that can be used to perform discontinuous transmission (DTX) and discontinuous reception (DRX) among network entities. For example, the systems and techniques can be used to enable and / or disable a cell DTX state (e.g., associated with a base station or gNB) based on a traffic load or a number of active users (e.g., UEs) in a cell. In some cases, the systems and techniques can be used to enable and / or disable a cell DRX state based on a traffic load or a number of active users in a cell. The cell DTX state can be aligned with the cell DRX state.

[0041] In some examples, cell DRX and cell DTX can be dynamically enabled and disabled for respective base stations. One or more UEs can be associated with respective base stations. A corresponding UE DRX configuration associated with each of the one or more UEs can be adjusted based on the enabling and disabling of cell DRX and / or cell DTX. For example, the one or more UEs can switch between UE-DRX configurations based on a cell DRX / DTX enabling status of a corresponding base station associated with the one or more UEs.

[0042] In some cases, a UE can receive (e.g., from a base station) a first DRX configuration and a second DRX configuration. The first DRX configuration can be associated with a DTX enabling status of the base station. The second DRX configuration can be associated with a DTX disabling status of the base station. The second DRX configuration can be different than the first DRX configuration. For example, one or more DRX configuration parameter values of the second DRX configuration can be different than one or more DRX configuration parameter values of the first DRX configuration.

[0043] The UE can implement UE-DRX associated with the DTX enabling status of the base station using the first DRX configuration information. For example, the UE can use the first DRX configuration to align a UE-DRX on duration with a cell DTX on duration of the base station. In some cases, the UE can use the first DRX configuration information to align a UE-DRX on duration with a cell DTX on duration and a cell DRX on duration of the base station (e.g., the cell DTX on duration and the cell DRX on duration can be aligned at the base station).

[0044] In some examples, when cell DTX is disabled at the base station, the UE can implement a second (e.g., different) UE-DRX on duration using the second DRX configuration information. For example, the base station can determine a respective second DRX configuration for each of a plurality of UEs (e.g., a plurality of UEs associated with the base station). Each respective second DRX configuration can be associated with a different start time for implementing a respective UE-DRX on duration at each UE. Based on the respective second DRX configuration associated with each UE, the UE-DRX on duration and / or the UE-DRX off duration can be staggered or spread apart between different UEs.

[0045] In some cases, a UE can be configured with multiple sets of UE-DRX configuration parameter values. The UE can switch between different UE-DRX configuration parameter values based on determining that cell DTX / DRX is enabled or disabled. In some cases, the UE can determine that cell DTX / DRX is enabled or disabled based on a dynamic signaling trigger. For example, the UE can receive a PHY or MAC signal (e.g., PDCCH, DCI, etc.) indicating a cell DTX enable or disable state and / or a cell DRX enable or disable state. In some examples, a UE-DRX configuration can utilize different UE-DRX on-duration start offset parameters for a cell DTX enable state and a cell DTX disable state. In some cases, one or more additional UE DRX configuration parameter values between a first UE-DRX configuration and a second UE-DRX configuration can be different, including UE-DRX cycle parameters, UE DRX on-duration timers, UE-DRX inactivity timers, DL and UL retransmission timers, DL and UL round-trip time (RTT) timers, etc.

[0046] In some examples, a UE can be signaled (e.g., by a base station) multiple radio resource control (RRC) UE-DRX configurations. Each RRC message or signal can indicate a different UE-DRX configuration. For example, a first RRC message can indicate a first UE-DRX configuration associated with a cell DTX enable state of the base station, and a second RRC message can indicate a second UE-DRX configuration associated with a cell DTX disable state of the base station. In another example, the UE can receive a single RRC UE-DRX configuration from the base station. The single RRC UE-DRX configuration signal can indicate one or more DRX configuration parameters. Each respective DRX configuration parameter of the one or more DRX configuration parameters can be associated with a first value corresponding to a first UE-DRX configuration and a second value corresponding to a second UE-DRX configuration.

[0047] Additional aspects of systems and techniques will be described with respect to the drawings.

[0048] As used herein, the phrase “based on” is not to be construed as a reference to information, one or more conditions, one or more factors, etc. that are either absolute or exclusive alternatives, in other words, the phrase “based on” should be interpreted as “based, at least in part, on” unless explicitly stated otherwise.

[0049] As used herein, the terms “user equipment” (UE) and “network entity” are not intended to be specific to or otherwise limited to any particular radio access technology (RAT), unless otherwise indicated. Generally, a UE can be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, and / or a tracking device, etc.), a wearable device (e.g., a smartwatch, smart glasses, a wearable ring, and / or an extended reality (XR) device such as a virtual reality (VR) headset, an augmented reality (AR) headset or glasses, or a mixed reality (MR) headset), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an aerial vehicle (e.g., an airplane, a jet, an unmanned aerial vehicle (UAV) or drone, a helicopter, a dirigible, a glider, etc.), and / or an Internet of Things (IoT) device, etc., used by a user to communicate over a wireless communication network. A UE can be mobile or can (e.g., at certain times) be stationary, and can communicate with a radio access network (RAN). As used herein, the term “UE” can be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can communicate with an external network such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on IEEE 802.11 communication standards, etc.), and so on.

[0050] A network entity can be implemented in an aggregated or monolithic base station architecture, or alternatively, in a disaggregated base station architecture, and can include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near- real-time (near-RT) RAN intelligent controller (RIC), or a non-RT RIC. A base station (e.g., with an aggregated / monolithic base station architecture or a disaggregated base station architecture) can operate according to one of a number of RATs in communication with UEs (depending on the network in which it is deployed), and can alternatively be referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station can be used primarily to support wireless access by UEs using the supported RATs, including supporting data, voice, and / or signaling connections for the UEs. In some systems, a base station can provide edge node signaling functions, while in other systems, a base station can provide additional control and / or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to a UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, or a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to an uplink, reverse, or downlink, and / or forward traffic channel.

[0051] The term “network entity” or “base station” (e.g., with an aggregated / monolithic base station architecture or a disaggregated base station architecture) can refer to a single physical transmission reception point (TRP) or multiple physical TRPs that can or can not be co-located. For example, where the term “network entity” or “base station” refers to a single physical TRP, the physical TRP can be a base station antenna corresponding to a cell (or several cell sectors) of the base station. Where the term “network entity” or “base station” refers to multiple co-located physical TRPs, the physical TRPs can be an array of antennas of the base station (e.g., as in a multiple input multiple output (MIMO) system or where the base station employs beamforming). Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs can be a distributed antenna system (DAS) (e.g., a network of spatially separated antennas connected to a common source via transmission medium) or remote radio heads (RRHs) (e.g., remote base stations connected to a serving base station). Alternatively, the non-co-located physical TRPs can be the serving base station from which the UE receives measurement reports and a neighbor base station whose reference radio frequency (RF) signals (e.g., or simply “reference signals”) the UE is measuring. Because, as used herein, a TRP is a point from or to which a base station transmits or receives wireless signals, references to transmitting from or receiving at a base station should be understood to refer to particular TRPs of the base station.

[0052] In some implementations that support positioning of UEs, a network entity or base station can not support wireless access by UEs (e.g., can not support data, voice, and / or signaling connections with UEs), but instead can transmit reference signals to UEs to be measured by the UEs, and / or can receive and measure signals transmitted by UEs. Such a base station can be referred to as a positioning beacon (e.g., where signals are transmitted to UEs) and / or as a location measurement unit (e.g., where signals from UEs are received and measured).

[0053] As described herein, a node (which can be referred to as a node, network node, network entity, or wireless node) can include, be, or can be included in (e.g., as a component of) a base station (e.g., any of the base stations described herein), a UE (e.g., any of the UEs described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which can also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node can be a UE. As another example, a network node can be a base station or network entity. As another example, a first network node can be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a UE. In another aspect of this example, the first network node can be a UE, the second network node can be a base station, and the third network node can be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node can be different relative to these examples. Similarly, a reference to a UE, a base station, an apparatus, a device, a computing system, etc. can include a disclosure of a UE, a base station, an apparatus, a device, a computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Once a particular example has been expanded in accordance with the present disclosure (e.g., a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), the broader example of the narrower example can be interpreted in reverse, but in a broad, generic sense. In the above example in which a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node can refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first set of one or more components, or a first processing entity, etc. that is configured to receive the information; and the second network node can refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second set of one or more components, or a second processing entity, etc.

[0054] As described herein, different terminology can be used in various aspects to describe the communication of information (e.g., any information, signals, and so on). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node can be described as being configured to send information to a second network node. In this example and consistent with the disclosure, the disclosure of the first network node being configured to send information to the second network node includes the disclosure of the first network node being configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the disclosure, the disclosure of the first network node being configured to send information to the second network node includes the disclosure of the second network node being configured to receive, obtain, or decode the information provided, transmitted, output, communicated, or sent by the first network node.

[0055] An RF signal includes an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter can transmit a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, the receiver can receive multiple “RF signals” corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a “multipath” RF signal. As used herein, an RF signal can also be referred to as a “wireless signal” or simply a “signal” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.

[0056] Various aspects of the systems and techniques described herein will now be discussed with regard to the drawings. According to various aspects, Figure 1 An example of a wireless communication system 100 is illustrated. The wireless communication system 100 (e.g., which can also be referred to as a wireless wide area network (WWAN)) can include various base stations 102 and various UEs 104. In some aspects, a base station 102 can also be referred to as a “network entity” or a “network node.” One or more of base stations 102 can be implemented in an aggregated or monolithic base station architecture. Additionally, or alternatively, one or more of base stations 102 can be implemented in a disaggregated base station architecture, and can include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-RT RIC. Base stations 102 can include macro cell base stations (e.g., high power cellular base stations) and / or small cell base stations (e.g., low power cellular base stations). In an aspect, macro cell base stations can include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to a Long Term Evolution (LTE) network), or gNBs (where the wireless communication system 100 corresponds to a NR network), or a combination of both, and small cell base stations can include femto cells, pico cells, micro cells, and the like.

[0057] The base stations 102 can collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or 5G core (5GC)) through backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., the one or more location servers can be part of the core network 170 or can be external to the core network 170). The base stations 102 can perform functions such as, but not limited to, transferring user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with each other directly or indirectly (e.g., through the EPC or 5GC) over backhaul links 134, which can be wired and / or wireless.

[0058] The base stations 102 can wirelessly communicate with the UEs 104. Each of the base stations 102 can provide communication coverage for a respective geographic coverage area 110. In an aspect, a base station 102 in each coverage area 110 can support one or more cells, A “cell” is a logical communication entity for a

[0059] Although the geographic coverage area 110 for each of the base stations 102 can overlap in order to provide stronger indoor and / or outdoor coverage, the same geographic coverage area 110 can be split by different macro cells or small cell base stations 102 into multiple smaller regions or cells 110 with each macro or small cell base station 102 providing service to each region or cell 110 within its geographical coverage area 110. In some examples, the base stations 102 can be referred to as gNBs, NodeBs, eNodeBs, or other similar terminology.

[0060] The communication links 120 between the base stations 102 and the UEs 104 can include uplink (e.g., also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (e.g., also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 can use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links 120 can be established on one or more carrier frequencies. Allocation of carriers can be asymmetric with respect to downlink and uplink (e.g., more or less carriers can be allocated for downlink than for uplink).

[0061] Beamforming, which can also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., one or more of the base stations 102 and UEs 104) to shape or steer a beam of energy in a specific direction, for example, to extract or transfer data via the beam. The beams can also be referred to as streams. Beamforming can be achieved by combining the signals communicated via antenna elements of an antenna array such that signals at particular orientations experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements can be done according to a beamforming weight vector specific to each of the antenna elements. The beamforming weight vector can be a set of values that can be applied by the transmitting device or the receiving device to a symbol carried via each of the antenna elements to shape the beam in a particular orientation. The values in the beamforming weight vector can be determined based on the direction of the beam and the orientation of the antenna elements.

[0062] Transmitting devices and / or receiving devices (e.g., such as one or more of base station 102 and / or UE 104) may use beam sweeping techniques as part of beamforming operations. For example, base station 102 (e.g., or other transmitting device) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 104 (e.g., or other receiving device). Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 102 (or other transmitting device) in different directions. For example, base station 102 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used to identify (e.g., by a transmitting device such as base station 102 or by a receiving device such as UE 104) the beam direction for later transmission or reception by base station 102.

[0063] Some signals, such as data signals associated with a particular receiving device, may be transmitted by base station 102 in a single beam direction (e.g., a direction associated with a receiving device, such as UE 104). In some examples, a beam direction associated with transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 104 may receive one or more of the signals transmitted by base station 102 in different directions and may report to base station 104 an indication of the signal received by UE 104 with the highest signal quality or other acceptable signal quality.

[0064] In some examples, transmission by a device (e.g., by base station 102 or UE 104) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from base station 102 to UE 104, from a transmitting device to a receiving device, etc.). UE 104 may report feedback indicating precoding weights used for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. Base station 102 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), etc.), which may or may not be precoded. UE 104 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port-selective codebook). Although these techniques are described with reference to signals sent by base station 102 in one or more directions, UE 104 may employ similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 104), or to send signals in a single direction (e.g., to send data to a receiving device).

[0065] A receiving device (e.g., a UE 104) can attempt multiple receive configurations (e.g., directional listening) when receiving various signals from base stations 102, such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device can receive via a different antenna subarray, process received signals according to a different antenna subarray, receive according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, or process received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which can be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device can use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration can be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0066] The wireless communications system 100 can further include a WLAN AP 150 in communication with WLAN STAs 152 via communication link 154 in an unlicensed frequency spectrum (e.g., 5 gigahertz (GHz)). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 can perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available. In some examples, the wireless communications system 100 can include devices (e.g., UEs, etc.) that utilize an ultra- wideband (UWB) spectrum for communications with one or more UEs 104, base stations 102, APs 150, etc. The UWB spectrum can range from 3.1 GHz to 10.5 GHz.

[0067] A small cell base station 102' can operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' can employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. A small cell base station 102' employing LTE and / or 5G in an unlicensed frequency spectrum can boost coverage and / or increase capacity of the access network. NR in unlicensed frequency spectrum can be referred to as NR-U. LTE in unlicensed frequency spectrum can be referred to as LTE-U, License Assisted Access (LAA), or MulteFire.

[0068] The wireless communications system 100 can also include millimeter wave (mmW) base stations 180 that can operate in mmW frequencies and / or near mmW frequencies in communication with UEs 182. The mmW base stations 180 can be implemented in an aggregated or monolithic base station architecture, or alternatively in a disaggregated base station architecture (e.g., including one or more of a CU, DU, RU, near-RT RIC, or non-RT RIC). Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range from 30 GHz to 300 GHz and wavelengths

[0069] In some aspects related to 5G, the spectrum in which wireless network nodes or entities (e.g., base stations 102 / 180, UEs 104 / 182) operate is divided into multiple frequency ranges: FR1 (e.g., from 450 megahertz (MHz) to 6,000 MHz), FR2 (e.g., from 24,250 MHz to 52,600 MHz), FR3 (e.g., above 52,600 MHz), and FR4 (e.g., between FR1 and FR2). In multi-carrier systems (such as 5G), one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," or "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCells." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels as well as UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals. For example, since the primary uplink and downlink carriers are typically UE-specific, these UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell can have different downlink primary carriers. The same is true for the uplink primary carrier. The network can change the primary carrier for any UE 104 / 182 at any time. This can be done, for example, to balance the load on different carriers. Since a "serving cell" (e.g., whether PCell or SCell) corresponds to a carrier frequency and / or component carrier that some base stations are using to communicate, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0070] For example, still referring to Figure 1One of the frequencies used by macrocell base station 102 can be an anchor carrier (or "PCell"), and other frequencies used by macrocell base station 102 and / or mmW base station 180 can be secondary carriers ("SCells"). In carrier aggregation, base station 102 and / or UE 104 can use up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz) of spectrum per carrier, with up to a total of Y x MHz (e.g., x component carriers) used for transmission in each direction. The component carriers can or can not be adjacent to each other on the frequency spectrum. The allocation of carriers can be asymmetric, with more or fewer carriers being allocated for downlink than for uplink (e.g., more downlink carriers than uplink carriers). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz carriers in a multi-carrier system can theoretically result in a doubling of data rates (e.g., 40 MHz) as compared to a single 20 MHz carrier.

[0071] To operate on multiple carrier frequencies, base station 102 and / or UE 104 can be equipped with multiple receivers and / or transmitters. For example, UE 104 can have two receivers, "Receiver 1" and "Receiver 2," where "Receiver 1" is a multi-band receiver that can be tuned to frequency band (e.g., carrier frequency) "X" or frequency band "Y," and "Receiver 2" is a single-band receiver that can only be tuned to frequency band "Z." In this example, if UE 104 is being served in frequency band "X," frequency band "X" would be referred to as the PCell or active carrier frequency, and "Receiver 1" would need to be tuned from frequency band "X" to frequency band "Y" (e.g., SCell) to measure frequency band "Y" (and vice versa). By contrast, whether UE 104 is being served in frequency band "X" or frequency band "Y," UE 104 can measure frequency band "Z" without interrupting service on frequency band "X" or frequency band "Y" due to the separate "Receiver 2."

[0072] Wireless communication system 100 can further include UE 164, which can communicate with macrocell base station 102 on communication link 120 and / or with mmW base station 180 on mmW communication link 184. For example, macrocell base station 102 can support a PCell and one or more SCells for UE 164, and mmW base station 180 can support one or more SCells for UE 164.

[0073] The wireless communication system 100 may also include one or more UEs, such as UE 190, that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (e.g., referred to as “side links”). Figure 1 In the example shown in FIG1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this link), and has a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (e.g., UE 190 can indirectly obtain WLAN-based Internet connectivity through this link). In one example, D2D P2P links 192 and 194 can use any well-known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct (Wi-Fi-D), Bluetooth ® etc.) to support.

[0074] Figure 2 A block diagram illustrates an example architecture 200 of a base station 102 and a UE 104 that enables transmission and processing of signals exchanged between the UE and the base station according to some aspects of the present disclosure. The example architecture 200 includes components of the base station 102 and the UE 104, which may be Figure 1 The illustrated example shows one of base stations 102 and one of UEs 104. Base station 102 may be equipped with T antennas 234a through 234t, and UE 104 may be equipped with R antennas 252a through 252r, where in general T > 1 and R > 1.

[0075] At base station 102, a transmit processor 220 can receive data from a data source 212 for one or more UEs, select one or more modulation and coding schemes (MCS) for each UE based on a channel quality indicator (CQI) received from that UE, process (e.g., encode and modulate) the data for each UE based on the MCS selected for that UE, and provide data symbols for all UEs. Transmit processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. Transmit processor 220 can also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and can provide T output symbol streams to T modulators (MODs) 232a through 232t. Modulators 232a through 232t are shown as combined modulator-demodulators (MOD-DEMOD). In some cases, the modulators and demodulators can be separate components. Each modulator 232a through 232t can process a respective output symbol stream (e.g., for an orthogonal frequency division multiplexing (OFDM) scheme, etc.) to obtain an output sample stream. Each modulator 232a through 232t can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals can be transmitted via T antennas 234a through 234t, respectively. According to certain aspects described in more detail below, synchronization signals can be generated with location encoding to convey additional information.

[0076] At the UE 104, the antennas 252a-252r can receive the downlink signals from the base station 102 and / or other base stations and can provide received signals to one or more demodulators (DEMODs) 254a-254r, respectively. The demodulators 254a-254r are shown as combined modulator-demodulators (MOD-DEMOD). In some cases, the modulator and demodulator can be separate components. Each of the demodulators 254a-254r can condition (e.g., filter, amplify, downconvert, and digitize) a received signal to obtain input samples. Each of the demodulators 254a-254r can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 can obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 260, and provide decoded control information and system information to a controller / processor 280. A channel processor can determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), and / or channel quality indicator (CQI), among other examples.

[0077] On the uplink, at the UE 104, a transmit processor 264 can receive and process data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, and / or the like) from the controller / processor 280. Transmit processor 264 can also generate reference symbols for one or more reference signals (e.g., based on a beta value or set of beta values associated with the one or more reference signals). The symbols from transmit processor 264 can be precoded by a TX MIMO processor 266, further processed by modulators 254a-254r (e.g., for DFT-s-OFDM, CP-OFDM, and / or the like), and transmitted to the base station 102. At the base station 102, the uplink signals from UE 104 and other UEs can be received by antennas 234a-234t, processed by demodulators 232a-232t, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information transmitted by the UE 104. The receive processor 238 can provide the decoded data to a data sink 239 and the decoded control information to a controller (e.g., processor) 240. The base station 102 can include a communication unit 244 and communicate with a network controller 231 via the communication unit 244. The network controller 231 can include a communication unit 294, a controller / processor 290, and a memory 292.

[0078] In some aspects, one or more components of UE 104 can be included in a housing. Controller / processor 240 of base station 102, controller / processor 280 of UE 104, and / or any other component(s) of Fig. 2 can perform one or more techniques associated with implicit UCI beta value determination for NR. Figure 2

[0079] Memory 242 and 282 can store data and program codes for base station 102 and UE 104, respectively. Scheduler 246 can schedule UEs for data transmission on the downlink, uplink, and / or sidelink.

[0080] In some aspects, deployment of a communication system, such as a 5G New Radio (NR) system, can be arranged with various components or constituent parts in a number of ways. In a 5G NR system or network, a network node, network entity, mobility element of a network, radio access network (RAN) node, core network node, network element, or network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a BS (e.g., such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmission reception point (TRP), or a cell, etc.) can be implemented as an aggregated base station (e.g., also referred to as a standalone BS or a monolithic BS) or a disaggregated base station.

[0081] An aggregated base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station can be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU or, alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DUs can be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs can also be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0082] ​Base station type operations or network design can consider the aggregate nature of base station functionality. For example, disaggregated base stations can be used in integrated access backhaul (IAB) networks, open radio access networks (O-RAN (e.g., such as network configurations advocated by the O-RAN Alliance)), or virtualized radio access networks (e.g., vRAN, also known as cloud radio access networks (C-RAN)). Disaggregation can include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which can enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0083] Figure 3 is an illustration of an example disaggregated base station 300 architecture. The disaggregated base station 300 architecture can include one or more CUs 310, which can communicate directly with a core network 320 via a backhaul link, or indirectly through one or more disaggregated base station units (e.g., such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both) with the core network 320. The CUs 310 can communicate with one or more distributed units (DUs) 330 via respective fronthaul links (such as F1 interfaces). The DUs 330 can communicate with one or more radio units (RUs) 340 via respective front-haul links. The RUs 340 can communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 can be simultaneously served by multiple RUs 340.

[0084] Figure 3Each of the units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) shown and / or described herein can include one or more interfaces or can be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller providing instructions to the communication interfaces of the units can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally, the units can include a wireless interface, which can include a receiver, a transmitter, or a transceiver (e.g., such as a radio frequency (RF) transceiver) configured to receive or transmit signals, or both, to one or more of the other units over a wireless transmission medium.

[0085] In some aspects, the CU 310 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can utilize an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., central unit-user plane (CU-UP)), control plane functions (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can be in bidirectional communication with the CU-CP units via an interface, such as an El interface. As needed, the CU 310 can be implemented to communicate with the DU 330 for network control and signaling.

[0086] The DU 330 can correspond to a logical unit that includes one or more base station functions for controlling operation of one or more RUs 340. In some aspects, the DU 330 can host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), depending on a functional split (such as a functional split defined by the 3rd Generation Partnership Project (3GPP)). In some aspects, the DU 330 can also host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0087] Lower layer functionality can be implemented by one or more RUs 340. In some deployments, the RUs 340 controlled by the DU 330 can correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc., or both) based on a functional split, such as a lower layer functional split. In such an architecture, the RUs 340 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RUs 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable the DUs 330 and the CUs 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0088] The SMO framework 305 can be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non- virtualized network elements, the SMO framework 305 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (e.g., such as an Ol interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (e.g., such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (e.g., such as instantiating virtualized network elements) via a cloud computing platform interface (e.g., such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, and near-RT RICs 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of a 4G RAN, such as Open eNB (O-eNB) 311, via an Ol interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via an Ol interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support functionality of the SMO framework 305.

[0089] The non-RT RIC 315 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based direction of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled in communication with (e.g., such as via an Al interface) the near-RT RIC 325. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions through an interface (e.g., such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and an O-eNB with the near-RT RIC 325.

[0090] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received at the SMO framework 305 or the non-RT RIC 315 from non-network data sources or from network functions. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (e.g., such as reconfiguration via Ol) or through creation of RAN management policies (e.g., such as Al policies).

[0091] Figure 4 An example of a computing system 470 of a wireless device 407 is illustrated. The wireless device 407 can comprise a client device such as a UE (e.g., UE 104, UE 152, UE 190) or other type of device that can be used by an end user (e.g., a station (STA) configured to communicate using a Wi-Fi interface). For example, the wireless device 407 can comprise a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, a wearable device (e.g., a smartwatch, glasses, an extended reality (XR) device such as a virtual reality (VR), augmented reality (AR), or mixed reality (MR) device, etc.), an Internet of Things (IoT) device, a vehicle, an aircraft, and / or another device configured to communicate over a wireless communication network. The computing system 470 includes software and hardware components that can be electrically coupled or communicatively coupled (e.g., or can otherwise be in communication, as appropriate) via a bus 489. For example, the computing system 470 includes one or more processors 484. The one or more processors 484 can include one or more CPUs, ASICs, FPGAs, APs, GPUs, VPUs, NSPs, microcontrollers, specialized hardware, any combination thereof, and / or other processing devices or systems. The one or more processors 484 can use the bus 489 to communicate between cores and / or with one or more memory devices 486.

[0092] The computing system 470 can also include one or more memory devices 486, one or more digital signal processors (DSPs) 482, one or more SIMs 474, one or more modems 476, one or more wireless transceivers 478, antennas 487, one or more input devices 472 (e.g., a camera, a mouse, a keyboard, a touch-sensitive screen, a touchpad, a keypad, and / or a microphone, etc.), and one or more output devices 480 (e.g., a display, a speaker, and / or a printer, etc.).

[0093] In some aspects, the computing system 470 can include one or more radio frequency (RF) interfaces configured to send and / or receive radio frequency (RF) signals. In some examples, the RF interface can include components such as a modem 476, a wireless transceiver 478, and / or an antenna 487. The one or more wireless transceivers 478 can send and receive wireless signals (e.g., signals 488) from one or more other devices, such as other wireless devices, network devices (e.g., base stations such as eNBs and / or gNBs, Wi-Fi access points (APs) such as routers or range extenders, and / or cloud networks, etc.), via the antenna 487. In some examples, the computing system 470 can include multiple antennas or arrays of antennas that can facilitate simultaneous transmit and receive functionality. The antenna 487 can be an omnidirectional antenna such that radio frequency (RF) signals can be received from and sent in all directions. The wireless signals 488 can be sent via a wireless network. The wireless network can be any wireless network, such as a cellular or telecommunication network (e.g., 3G, 4G, 5G, etc.), a wireless local area network (e.g., a Wi-Fi network), a Bluetooth network, and / or other networks. ™

[0094] In some examples, the wireless signals 488 can be sent directly to other wireless devices using sidelink communication (e.g., using a PC5 interface, using a DSRC interface, etc.). The wireless transceiver 478 can be configured to send RF signals via the antenna 487 in accordance with one or more transmit power parameters that can be associated with one or more regulatory

[0095] In some examples, the one or more wireless transceivers 478 can include an RF front end that includes one or more components, such as amplifiers, mixers (e.g., also referred to as signal multipliers) for down-converting signals, frequency synthesizers (e.g., also referred to as oscillators) that provide a frequency to the mixers, baseband filters, analog-to-digital converters (ADCs), one or more power amplifiers, and other components. The RF front end can generally handle the selection and conversion of the wireless signals 488 to baseband frequencies or intermediate frequencies, and can convert RF signals to the digital domain.

[0096] In some cases, the computing system 470 can include a coding-decoding device (or CODEC) configured to encode and / or decode data sent and / or received using the one or more wireless transceivers 478. In some cases, the computing system 470 can include an encryption-decryption device or component configured to encrypt and / or decrypt data sent and / or received by the one or more wireless transceivers 478 (e.g., in accordance with AES and / or DES standards).​

[0097] The one or more SIMs 474 can each securely store an international mobile subscriber identity (IMSI) number and related key(s) assigned to a user of the wireless device 407. The IMSI and key(s) can be used to identify and authenticate the subscriber when accessing networks provided by network service providers or operators associated with the one or more SIMs 474. The one or more modems 476 can modulate one or more signals to encode information for transmission using the one or more wireless transceivers 478. The one or more modems 476 can also demodulate signals received by the one or more wireless transceivers 478 in order to decode information transmitted. In some examples, the one or more modems 476 can include a Wi-Fi modem, a 4G (or LTE) modem, a 5G (or NR) modem, and / or other types of modems. The one or more modems 476 and the one or more wireless transceivers 478 can be used to communicate data for the one or more SIMs 474.

[0098] The computing system 470 can also include (and / or be in communication with) one or more non-transitory machine-readable storage media (e.g., one or more memory devices 486) 486, which can include, without limitation, local and / or network accessible storage, a disk drive, a drive array, an optical storage device, solid-state storage device such as a RAM and / or ROM, which can be programmable, flash- updateable, and / or the like. Such storage devices can be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and / or the like.

[0099] In various aspects, functionality can be stored as one or more computer programs (e.g., instructions or code) in the memory device(s) 486 and executed by the one or more processors 484 and / or the one or more DSP(s) 482. The computing system 470 can further include software elements (e.g., in the one or more memory devices 486), including, for example, an operating system, device drivers, executable libraries, and / or other code, such as one or more application programs, which can include computer programs provided by various aspects, and / or can be designed to implement methods, and / or configure systems, as described herein.

[0100] Figure 5 FIG. 5 is a diagram illustrating an example 500 of physical channels and reference signals in a wireless network. In some examples, one or more downlink channels and one or more downlink reference signals can carry information from a base station 102 to a UE 104. One or more uplink channels and one or more uplink reference signals can carry information from a UE 104 to a base station 102.

[0101] In some aspects, the downlink channel can include one or more of a physical downlink control channel (PDCCH) carrying downlink control information (DCI), a physical downlink shared channel (PDSCH) carrying downlink data, and / or a physical broadcast channel (PBCH) carrying system information, among other examples. In some aspects, the PDSCH communication can be scheduled by the PDCCH communication.

[0102] In some examples, the uplink channel can include one or more of a physical uplink control channel (PUCCH) carrying uplink control information (UCI), a physical uplink shared channel (PUSCH) carrying uplink data, and / or a physical random access channel (PRACH) for initial network access, among other examples. In some aspects, the UE 104 can transmit acknowledgement (ACK) or negative-acknowledgement (NACK) feedback (e.g., ACK / NACK feedback or ACK / NACK information) in UCI on the PUCCH and / or the PUSCH.

[0103] In some cases, the downlink reference signal can include one or more of a synchronization signal block (SSB), a channel state information (CSI) reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), and / or a phase tracking reference signal (PTRS), among other examples. In some examples, the uplink reference signal can include one or more of a sounding reference signal (SRS), a DMRS, and / or a PTRS, among other examples.

[0104] The SSB can carry or include information for initial network acquisition and synchronization. For example, the SSB can carry or include one or more of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH, and / or a PBCH DMRS. The SSB can be referred to as a synchronization signal / PBCH (SS / PBCH) block. In some aspects, the base station 102 can transmit multiple SSBs on multiple corresponding beams, and the SSBs can be used for beam selection.

[0105] CSI-RSs can carry information used for downlink channel estimation (e.g., downlink CSI acquisition), which can be used for scheduling, link adaptation, or beam management, among other examples. For example, a base station 102 can configure a set of CSI-RSs for a UE 104, and the UE 104 can measure the configured set of CSI-RSs. Based on the CSI-RS measurements, the UE 104 can perform channel estimation and report the channel estimation parameters to the base station 102 (e.g., in a CSI report). For example, the channel estimation parameters can include one or more of a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), a layer indicator (LI), a rank indicator (RI), and / or a reference signal received power (RSRP), among other examples.

[0106] In some examples, the base station 102 can use the CSI report to select transmission parameters for downlink communications to the UE 104. For example, the base station 102 can use the CSI report to select transmission parameters including one or more of a number of transmission layers (e.g., a rank), a precoding matrix (e.g., a precoder), a modulation and coding scheme (MCS), and / or a refined downlink beam (e.g., using a beam refinement procedure or a beam management procedure), among other examples.

[0107] DMRSs can carry information used to estimate a radio channel to demodulate an associated physical channel (e.g., a PDCCH, a PDSCH, a PBCH, a PUCCH, or a PUSCH). The design and mapping of DMRSs can be specific to the physical channel for which the DMRSs are used for estimation. DMRSs are UE-specific, can be beamformed, can be confined in scheduled resources (e.g., rather than transmitted over a wideband), and can be transmitted only when necessary. As shown, DMRSs are used for both downlink communications and uplink communications.

[0108] PTRSs can carry information used to compensate for oscillator phase noise. In some cases, oscillator phase noise can increase as an oscillator carrier frequency increases. In some examples, PTRSs can be utilized at high carrier frequencies (e.g., such as millimeter wave frequencies) to mitigate oscillator phase noise. PTRSs can be used to track the phase of a local oscillator and to enable suppression of phase noise and common phase error (CPE). As shown, in some examples, one or more PTRSs can be used for both downlink communications (e.g., on a PDSCH) and uplink communications (e.g., on a PUSCH). Figure 5

[0109] ​A PRS can carry information associated with timing or ranging measurements by the UE 104. For example, the UE 104 can utilize one or more signals (e.g., PRSs) transmitted by the base station 102 to improve Observed Time Difference of Arrival (OTDOA) positioning performance. In some examples, the PRSs can be pseudo-random Quadrature Phase Shift Keying (QPSK) sequences mapped in a diagonal pattern with frequency and time offsets to avoid collision with cell-specific reference signals and control channels (e.g., PDCCH). The PRSs can be designed to improve detectability by the UE 104, which can need to detect downlink signals from multiple neighboring base stations in order to perform OTDOA-based positioning. Thus, the UE 104 can receive PRSs from multiple cells (e.g., a reference cell and one or more neighboring cells), and can report a Reference Signal Time Difference (RSTD) based on OTDOA measurements associated with the PRSs received from the multiple cells. In some aspects, the base station 102 can calculate a position of the UE 104 based on the RSTD measurements reported by the UE 104.

[0110] In some examples, an SRS can carry information for uplink channel estimation, which can be used for scheduling, link adaptation, precoder selection, and / or beam management, among other examples. The base station 102 can configure one or more SRS resource sets for the UE 104, and the UE 104 can transmit SRSs on the configured SRS resource sets. An SRS resource set can have a configured purpose, such as uplink CSI acquisition, downlink CSI acquisition for reciprocity-based operation, uplink beam management, among other examples. The base station 102 can measure the SRSs, can perform channel estimation based on the measurements, and / or can use the SRS measurements to configure communications with the UE 104.

[0111] As previously mentioned, the systems and techniques described herein can be used to provide improved energy efficiency for wireless communications between a UE and a base station. In one illustrative example, the systems and techniques can provide dynamic implementation of a UE-DRX configuration based on a DTX enable or disable state of the base station or gNB (e.g., a cell DTX enable or disable state) and / or based on a DRX enable or disable state of the base station or gNB (e.g., a cell DRX enable or disable state).

[0112] Figure 6A FIG. 6A is an example of an aligned UE-DRX configuration 600a, illustrative of an example of an aligned UE-DRX configuration, in accordance with some examples. The aligned UE-DRX configuration 600a can correspond to a DTX enable state of the base station or gNB (e.g., a cell DTX enable) and / or a DRX enable state of the base station or gNB (e.g., a cell DRX enable). Figure 6Bis a diagram illustrating an example of a non-aligned UE-DRX configuration 600b in accordance with some examples. The non-aligned UE-DRX configuration 600b can correspond to a DTX disable state (e.g., cell DTX disable) of a base station or gNB and / or a DRX disable state (e.g., cell DRX disable) of the base station or gNB.

[0113] As previously mentioned, a UE-DRX configuration can be used to provide discontinuous reception of DL transmissions at a UE (e.g., discontinuous reception of DL transmissions from a base station by a UE). Similar to UE-DRX, a cell DRX configuration can be used to provide discontinuous reception of UE UL transmissions at a base station. For example, when cell DRX is enabled, a base station or gNB associated with a cell can monitor UL transmissions from some (or all) UEs included in the cell.

[0114] In one illustrative example, when cell DRX is enabled, a base station can periodically monitor UE UL transmissions. For example, a cell DRX enable state can correspond to a cell DRX cycle 610. The base station can monitor UE UL transmissions during a portion of the cell DRX cycle 610 (e.g., a cell DRX on duration 612, a cell DRX on duration 614, etc.). During the remaining time of each cell DRX cycle 610, the base station does not monitor some (or all) UE UL transmissions. For example, the base station can still monitor critical UL channels or signals (e.g., SRS). In some cases, the base station can monitor critical UL channels or signals during a cell DRX off duration, but at a reduced density. For example, a cell DRX off duration can be equal to the cell DRX cycle 610 minus the cell DRX on duration 612 (e.g., during the cell DRX cycle 610, the base station is in a cell DRX on duration or a cell DRX off duration with respect to the cell). In some aspects, the base station can enter a “sleep” or “idle” state during the cell DRX off duration of the cell DRX cycle 610. In some cases, the base station can enter a “sleep” or “idle” state with respect to a first cell (e.g., during a cell DRX off duration of the first cell) and can remain in an active or awake state with respect to a second cell (e.g., during a cell DRX on duration of the second cell, receive UE UL transmissions from UEs located in the second cell associated with the base station).

[0115] Consecutive cell DRX on durations 612 and 614 can be separated by a cell DRX cycle time 610. Consecutive cell DRX off durations can additionally be separated by the cell DRX cycle time 610. In some aspects, the cell DRX on durations and / or the cell DRX off durations can be the same across multiple cell DRX cycles. In other examples, one or more (or both) of the cell DRX on durations and / or the cell DRX off durations can be different (or both) for each of multiple cell DRX cycles.

[0116] A cell DTX configuration can be used to provide discontinuous transmissions from a base station to one or more UEs in a cell. For example, a cell DTX on duration 622 can provide a periodic (e.g., discontinuous) window of time during which the base station can transmit DL transmissions to one or more UEs of the cell (e.g., and during which the UEs can receive DL transmissions from the base station). In one illustrative example, when cell DTX is enabled, the base station can schedule any DL transmissions to UEs in the cell during the cell DTX on duration 622 of a cell DTX cycle 620. During the remaining time of each cell DTX cycle 620, the base station does not transmit some (or all) DL transmissions to one or more UEs of the cell. For example, the base station can still transmit critical DL channels or signals (e.g., SSBs). In some cases, the base station can transmit critical DL channels or signals during the cell DRX off durations, but at a reduced density. For example, the cell DTX off duration can be equal to the cell DTX cycle 620 minus the cell DTX on duration 622 (e.g., the base station is in a cell DTX on duration or a cell DTX off duration relative to the cell during the cell DTX cycle 620). In some aspects, the base station can enter a “sleep” or “idle” state during the cell DTX off duration of the cell DTX cycle 620. In some cases, the base station can enter a “sleep” or “idle” state relative to a first cell (e.g., during a cell DTX off duration of the first cell), and can remain in an active or awake state relative to a second cell (e.g., during a cell DTX on duration of the second cell, transmitting DL transmissions to UEs located in the second cell associated with the base station).

[0117] Consecutive cell DTX on durations 622 and 624 can be separated by a cell DTX cycle time 620. Consecutive cell DTX off durations can additionally be separated by the cell DTX cycle time 620. In some aspects, the cell DTX on durations and / or the cell DTX off durations can be the same across multiple cell DTX cycles. In other examples, one or more (or both) of the cell DTX on durations and / or the cell DTX off durations can be different (or both) for each of multiple cell DTX cycles.

[0118] In some aspects, the systems and techniques described herein can enable (and disable) cell DRX and cell DTX together. For example, enabling cell DRX can be associated with enabling cell DTX, and vice versa. In one illustrative example, a cell DRX timeline (e.g., associated with the cell DRX cycle 610) can be aligned with a cell DTX timeline (e.g., associated with the cell DTX cycle 620). In some cases, the alignment of cell DRX and cell DTX can be based on a tight coupling between UL transmissions and DL transmissions (e.g., PDSCH and HARQ-ACK reporting, PUSCH and potential UL retransmission scheduling PDCCH, etc.).

[0119] In some examples, aligning the cell DRX timeline and the cell DTX timeline can be associated with aligning respective on duration start times with each other. For example, when the cell DRX timeline is aligned with the cell DTX timeline, a start time associated with the cell DRX on duration 612 can be the same as a start time associated with the cell DTX on duration 622. In some examples, the respective start times can be determined relative to a start of the cell DRX cycle 610 or the cell DTX cycle 620, respectively, that includes the on duration. For example, the start time associated with the cell DRX on duration 612 can be determined from (or relative to) a start of the cell DRX cycle 610, and the start time associated with the cell DTX on duration 622 can be determined from (or relative to) a start of the cell DTX cycle 620.

[0120] In some examples, when the cell DRX timeline is aligned with the cell DTX timeline, an ending time associated with the cell DRX on duration 612 can be the same as an ending time associated with the cell DTX on duration 622. In some examples, the respective ending times can be determined relative to a start of the cell DRX cycle 610 or the cell DTX cycle 620, respectively, that includes the on duration. For example, the ending time associated with the cell DRX on duration 612 can be determined from or relative to a start of the cell DRX cycle 610, and the ending time associated with the cell DTX on duration 612 can be determined from or relative to a start of the cell DTX cycle 620.

[0121] In some aspects, the cell DRX on duration 612 can be within the cell DTX on duration 622. For example, the cell DTX on duration 622 can include or overlap in time with the cell DRX on duration 612. In some cases, when the cell DRX on duration 612 is within the cell DTX on duration 622, a start time of the cell DRX on duration 612 is the same as or later than a start time of the cell DTX on duration 622, and an end time of the cell DRX on duration 612 is the same as or before an end time of the cell DTX on duration 622.

[0122] In one illustrative example, one or more UEs in a cell associated with the cell DRX cycle 610 and the cell DTX cycle 620 can obtain or receive information indicating the cell DTX of the serving base station or gNB (e.g., information indicating a cell DTX parameter implemented by the base station or gNB associated with the cell). In some examples, a corresponding UE-DRX cycle for each respective UE of the one or more UEs associated with the cell can be aligned at least with the cell DTX cycle 620. In examples where the cell DTX cycle 620 is aligned with the cell DRX cycle 610, the respective UE-DRX cycle can additionally be aligned with the cell DRX cycle 610.

[0123] For example, a first UE can be associated with a respective UE-DRX configuration to implement a first UE-DRX ON duration 632. A second UE can be associated with a different UE-DRX configuration to implement a second UE-DRX ON duration 642. A third UE can be associated with another UE-DRX configuration to implement a third UE-DRX ON duration 652. In one illustrative example, the UE-DRX ON durations 632, 642, 652 can be aligned with one another (e.g., have the same ON duration start time, fully overlap in time, etc.).

[0124] The UE-DRX ON durations 632, 642, 652 can have equal lengths and / or can have different lengths. For example, as shown, the first UE-DRX ON duration 632 is the shortest ON duration, the second UE-DRX ON duration 642 is the longest ON duration, and the third UE-DRX ON duration 652 is longer than the first UE-DRX ON duration 632 but shorter than the second UE-DRX ON duration 642. Figure 6A

[0125] In one illustrative example, the UE-DRX ON durations used by each respective UE can be aligned with at least the cell DTX ON duration 622. For example, each of the UE-DRX ON durations 632, 642, 652 can be within the cell DTX ON duration 622 (e.g., the respective start and end times of each UE-DRX ON duration can be within the start and end times of the cell DTX ON duration 622). In some aspects, one or more (or all) of the UE-DRX ON durations 632, 642, 652 can be aligned with the cell DTX ON duration 622 but do not share the same start time as the cell DTX ON duration 622.

[0126] In some aspects, based on the start time of each respective UE-DRX ON duration being the same as or after the start time of the cell DTX ON duration, the UE-DRX ON durations used by each respective UE can be aligned with the cell DTX ON duration. In this example, each respective UE does not wake up (e.g., exit a relatively low power "sleep" or "idle" state associated with a UE-DRX OFF duration) to attempt to receive any DL transmissions from the base station until at least the cell DTX ON duration in which the base station is configured to transmit DL transmissions begins. In one illustrative example, aligning the start times of each UE-DRX ON duration 632, 642, 652 with the start time of the cell DTX ON duration 622 can be used to provide power savings at each UE.​

[0127] For example, if the UE-DRX on-duration starts before the cell DTX on-duration, the UE can waste power by unnecessarily monitoring the PDCCH for an indication of a DL transmission during the base station's cell DTX off state (e.g., during which no dynamically scheduled DL transmissions will be in the air from the base station to the cell's UEs for the cell DTX off duration).

[0128] In some examples, the UE-DRX on-duration used by each respective UE can be aligned with the cell DTX on-duration based on the end time of each respective UE-DRX on-duration being the same as or before the end time of the cell DTX on-duration. In this example, each respective UE does not remain in an awake state and does not monitor the PDCCH for a DL transmission indication during the base station's cell DTX off state (e.g., during which no dynamically scheduled DL transmissions will be in the air from the base station to the cell's UEs for the cell DTX off duration).

[0129] In some aspects, the UE-DRX cycle time can be the same as one or more of (or both) the cell DRX cycle time 610 and / or the cell DTX cycle time 620. In some cases, the UE-DRX cycle time can be equal to a multiple of the cell DRX cycle time 610 and / or the cell DTX cycle time 620. For example, when the UE-DRX cycle time is equal to a multiple of the cell DTX cycle time, the UE-DRX on-duration will align with a subset of the cell DTX on-durations (e.g., if the UE-DRX cycle time is equal to four times the cell DTX cycle time, the UE-DRX on-duration will align with every fourth cell DTX on-duration). In some examples, the UE-DRX configuration for each respective UE of the cell can be the same across multiple consecutive UE-DRX cycles and cell DTX cycles 620. For example, a first UE can receive one UE-DRX configuration corresponding to the base station's cell DTX enabled state and / or cell DRX enabled state, and can use this one UE-DRX configuration to implement a UE-DRX on-duration 632 (e.g., corresponding to a first cell DTX cycle with a cell DTX on-duration 622) that is the same as a later UE-DRX on-duration 634 (e.g., corresponding to a second cell DTX cycle with a cell DTX on-duration 624).

[0130] The second UE can receive one UE-DRX configuration corresponding to the cell DTX enabled state and / or the cell DRX enabled state of the base station, and can use the one UE-DRX configuration to implement a UE-DRX ON duration 642 (e.g., corresponding to the first cell DTX cycle with cell DTX ON duration 622) that is the same as a later UE-DRX ON duration 644 (e.g., corresponding to the second cell DTX cycle with cell DTX ON duration 624). The third UE can receive one UE-DRX configuration corresponding to the cell DTX enabled state and / or the cell DRX enabled state of the base station, and can use the one UE-DRX configuration to implement a UE-DRX ON duration 652 (e.g., corresponding to the first cell DTX cycle with cell DTX ON duration 622) that is the same as a later UE-DRX ON duration 654 (e.g., corresponding to the second cell DTX cycle with cell DTX ON duration 624).

[0131] As will be described in greater depth below, each UE of a cell can receive one or more UE-DRX configurations from a serving base station or gNB associated with the cell and / or associated with one or more UEs of the cell. In some aspects, each UE of the cell can receive or otherwise determine a respective first UE-DRX configuration associated with a DTX enabled state of the base station. The respective first UE-DRX configuration can be used to implement a UE-DRX ON duration within a cell DTX ON duration of each cell DTX cycle.

[0132] Each UE of the cell can additionally receive or otherwise determine a respective second UE-DRX configuration associated with a DTX disabled state of the base station. The respective second UE-DRX configuration can be used to implement a UE-DRX ON duration that is offset or staggered relative to the remaining UE-DRX ON durations of the UEs in the cell, as will be described below with respect to Figure 6B In some cases, the respective second UE-DRX configuration can be implemented based on a determination that the serving base station or gNB for the UE cell disables (e.g., does not enable) cell DTX.

[0133] In some examples, cell DRX and cell DTX can be dynamically enabled and disabled for respective base stations and / or particular cells served by respective base stations. For example, cell DRX and cell DTX can be enabled or disabled based on analyzing an overall traffic load of a particular cell. In some aspects, cell DTX and / or cell DRX can be implemented based on determining a relatively lower traffic load of a particular cell and / or based on determining a relatively fewer number of active UEs in a cell. In some examples, cell DTX and / or cell DRX can be disabled based on determining a relatively higher traffic load of a cell. In some aspects, by enabling or disabling cell DTX and cell DRX based on a traffic load and / or a number of active users associated with a cell, these systems and techniques can be used to implement dynamic power savings to maximize network energy gain.

[0134] In one illustrative example, UE-DRX can be enabled during a cell DTX / DRX enabled state (e.g., corresponding to the example of Figure 6A ) and during a cell DTX / DRX disabled state (e.g., corresponding to the example of Figure 6B ). UE-DRX configurations corresponding to a cell DTX enabled state can indicate UE-DRX configuration parameter values corresponding to respective UE-DRX on durations that are aligned with (e.g., within) a cell DTX on duration. UE-DRX configurations corresponding to a cell DTX disabled state can indicate UE-DRX configuration parameter values corresponding to respective UE-DRX on durations that are not aligned with one another (e.g., respective UE-DRX on durations of one or more UEs of a cell can be staggered based on determining a cell DTX disabled state). In some examples, staggering UE-DRX on durations during a cell DTX disabled state can be used to maximize opportunities for multi-user scheduling while saving UE power consumption.

[0135] In some aspects, a corresponding UE-DRX configuration associated with each UE of a particular cell can be adjusted based on determining an enabled or disabled state of cell DTX and / or cell DRX at a serving base station of the particular cell. A first UE-DRX configuration (e.g., associated with a cell DTX enabled state) and a second UE-DRX configuration (e.g., associated with a cell DTX disabled state) can each include one or more DRX configuration parameter values. One or more (or all) of the DRX configuration parameter values can be different between the first DRX configuration (e.g., for configuring UE-DRX during a cell DTX enabled state) and the second DRX configuration (e.g., for configuring UE-DRX during a cell DTX disabled state).

[0136] In one illustrative example, the DRX configuration parameter values can include at least an on-duration start offset indicating a time offset between a start of a cycle (e.g., a start of a UE-DRX cycle, a start of a cell DTX cycle, a start of a cell DRX cycle, etc.) and a start of each respective UE-DRX on-duration. For example, a first UE-DRX configuration for each UE of the cell (e.g., associated with a cell DTX enabled state) can indicate a same or similar on-duration start offset for each UE, where each respective on-duration start offset enables a respective UE-DRX on-duration within the cell DTX on-duration.

[0137] A second UE-DRX configuration for each UE of the cell (e.g., associated with a cell DTX disabled state) can indicate different on-duration start offsets for each UE, where each respective on-duration start offset enables a respective UE-DRX on-duration that does not overlap or partially overlaps with a remaining UE-DRX on-duration of the UE of the cell.

[0138] For example, Figure 6B is an example diagram illustrating an example of a non-aligned UE-DRX configuration 600b in accordance with some examples. Figure 6B UE1, UE2, and UE3 of FIG. 6A can be the same as or similar to UE1, UE2, and UE3 of Figure 6A UE1, UE2, and UE3 of FIG. 6A. In some aspects, each UE can be associated with a same UE-DRX cycle 660 (e.g., each UE uses the same UE-DRX cycle 660 to implement its corresponding cell DTX disabled UE-DRX configuration). In one illustrative example, each UE of the cell can be configured with different UE-DRX configurations, where each UE-DRX on-duration is associated with a different portion of the UE-DRX cycle 660 and does not overlap in time with the remaining UE-DRX on-durations.

[0139] For example, during each UE-DRX cycle 660, UE1 can implement a UE-DRX on duration 663 at the beginning of the UE-DRX cycle 660 when the cell DTX is in a disabled state. In some examples, the start time of the UE1 DRX on duration 663 can be the same as or similar to the start time of the UE-DRX cycle 660. The end time of the UE1 DRX on duration 663 is followed (or simultaneous with) by the start time of a UE2 UE-DRX on duration 673. The UE2 DRX on duration 673 can be non-overlapping (e.g., staggered) in time with the UE1 DRX on duration 673. A third UE (UE3) can implement a UE3 DRX on duration 683 with a start time that is the same as or after the end time of the UE2 DRX on duration 673. The UE3 DRX on duration 683 and the UE2 DRX on duration 673 can be non-overlapping (e.g., staggered) in time.

[0140] In some aspects, the staggering of different UE DRX on durations for UEs (e.g., UE1, UE2, UE3) of a cell can be the same for each repetition of the UE-DRX cycle 660. For example, the UE1 DRX on duration 665 (and the associated on duration start offset relative to the start of the second UE-DRX cycle) can be the same as the UE1 DRX on duration 663 and the associated on duration start offset relative to the start of the first UE-DRX cycle 660. The UE2 DRX on duration 675 (and the associated on duration start offset relative to the start of the second UE-DRX cycle) can be the same as the UE2 DRX on duration 673 and the associated on duration start offset relative to the start of the first UE-DRX cycle 660. The UE3 DRX on duration 685 (and the associated on duration start offset relative to the start of the second UE-DRX cycle) can be the same as the UE3 DRX on duration 683 and the associated on duration start offset relative to the start of the first UE-DRX cycle 660.

[0141] In some cases, the DRX configuration parameter values can additionally include one or more (or all) of a UE-DRX cycle value, an on duration timer value, an inactivity timer value, a DL retransmission timer value, a UL retransmission timer value, a DL RTT timer value, a UL RTT timer value, and the like.

[0142] In one illustrative example, a UE can be configured with multiple sets of UE-DRX configuration parameter values. Based on a determination and / or a signal that cell DTX and cell DRX are enabled or disabled, the UE can switch from using a first set of UE-DRX configuration parameters corresponding to a cell DTX (and cell DRX) enabled state to using a second set of UE-DRX configuration parameters corresponding to a cell DTX (and cell DRX) disabled state.

[0143] In some aspects, each of one or more UEs associated with a particular cell (e.g., and a serving base station or gNB of the particular cell) can be configured by the serving base station or gNB with a first and second set of UE-DRX configuration parameter values. For example, a serving base station or gNB associated with a cell including at least UE1, UE2, and UE3 can be configured to configure each UE with a respective first UE-DRX configuration (e.g., corresponding to a cell DTX enabled state and Figure 6A a UE-DRX configuration) and a respective second UE-DRX configuration (e.g., corresponding to a cell DTX disabled state and Figure 6B a UE-DRX configuration).

[0144] In one illustrative example, enabling and / or disabling cell DTX and cell RTX at a serving base station or gNB of a cell associated with a UE can be triggered based on dynamic signaling. For example, a base station can signal or indicate to UEs of a cell when cell DTX and cell RTX are enabled, disabled, and / or change state. In some aspects, dynamic signaling of a cell DTX enabled or disabled state can be based on one or more PHY signals (e.g., PDCCH, DCI, etc.) transmitted by the serving base station or gNB and received by one or more UEs of the cell. In another example, dynamic signaling of a cell DTX enabled or disabled state can be based on one or more MAC signals transmitted by the serving base station or gNB and received by one or more UEs of the cell. In some cases, a cell DTX enabled or disabled state can be indicated to one or more UEs of a cell based on a PDCCH, DCI, and / or MAC-CE, among other examples.

[0145] In some aspects, the UE can determine a DTX enabled state and / or a DTX disabled state of a serving base station or gNB associated with a cell of the UE based on one or more timer values. For example, the UE can determine a DTX enabled state of a base station based on receiving or not receiving a signal relative to a time period. In some cases, the signal can be a particular broadcast signal from the base station. In some examples, an expected signal and / or the time period can be configured for the base station and each of one or more UEs served by the base station. In some examples, the UE can determine a DTX enabled state of a base station based on not receiving a signal relative to the time period (e.g., a timer interval). In some examples, the UE can determine a DTX disabled state of a base station based on receiving a signal relative to the time period (e.g., a timer interval). In some cases, a same time period (e.g., timer interval) can be used to determine a DTX enabled state and a DTX disabled state based on not receiving or receiving a signal, respectively, relative to the time period. In some examples, different time periods (e.g., timer intervals) can be used to determine a DTX enabled state based on not receiving a signal relative to a first time period or a DTX disabled state based on receiving a signal relative to a second time period.

[0146] In some cases, cell DTX can be enabled and disabled separately (e.g., independently) from cell DRX being enabled and disabled. Separate signaling can be used to indicate to one or more UEs when cell DTX is enabled or disabled, and when cell DRX is enabled or disabled. In some aspects, cell DTX and cell DRX can be enabled and disabled together (e.g., when the cell DTX timeline aligns with the cell DRX timeline, as previously described above).

[0147] In one illustrative example, a first DRX configuration for a UE (e.g., corresponding to a DTX enabled state of a serving base station or gNB) can differ from a second DRX configuration for the UE (e.g., corresponding to a DTX disabled state of the serving base station or gNB) by at least a value of a UE-DRX on duration start offset parameter. As noted above, the UE-DRX on duration start offset parameter can indicate an offset (e.g., a time delay or time difference) between a start of a UE-DRX cycle of a particular UE and a start of a DRX on duration. In some examples, the UE-DRX on duration start offset parameter can correspond to a drx-LongCycleStartOffset parameter.

[0148] In some cases, the first DRX configuration for the UE can differ from the second DRX configuration for the UE by at least a value of a UE-DRX on-duration start offset parameter and one or more additional DRX configuration parameter values. For example, the one or more additional DRX configuration parameter values that differ between the first DRX configuration for the UE and the second DRX configuration can include a DRX on-duration (e.g., corresponding to a drx-onDurationTimer parameter), a DRX cycle duration (e.g., corresponding to a drx-LongCycleStartOffset parameter), a DRX inactivity timer (e.g., corresponding to a drx-InactivityTimer parameter), a DL retransmission timer (e.g., corresponding to a drx-RetransmissionTimerDL), a UL retransmission timer (e.g., corresponding to a drx-RetransmissionTimerUL), a DL round-trip time (RTT) timer (e.g., corresponding to a drx-HARQ-RTT-TimerDL parameter), and / or a UL RTT timer (e.g., corresponding to a drx-HARQ-RTT-TimerUL parameter).

[0149] In some aspects, different UE-DRX configuration parameter values (e.g., a first DRX configuration corresponding to a cell DTX enabled state and a second DRX configuration corresponding to a cell DTX disabled state) can be indicated using multiple transmissions or signals from a serving base station or gNB to one or more UEs of a particular cell. For example, a UE can be provided with multiple RRC UE-DRX configurations, where at least a UE-DRX on-duration start offset parameter has a different value. For example, a first RRC UE-DRX configuration can indicate a first DRX configuration for a particular UE, where the particular UE implements the first DRX configuration based on determining a DTX enabled state of a serving base station or gNB. A second RRC UE-DRX configuration can indicate a second DRX configuration for the particular UE, where the particular UE implements the second DRX configuration based on determining a DTX disabled state of the serving base station or gNB (and / or based on failing to determine a DTX enabled state of the serving base station or gNB).

[0150] In another example, a same RRC UE-DRX configuration for a particular UE can be configured with multiple values for each DRX configuration parameter that is different between a first DRX configuration and a second DRX configuration. For example, a single RRC UE-DRX configuration can include a first on-duration start offset value corresponding to a first DRX configuration and can include a second on-duration start offset value corresponding to a second DRX configuration. DRX configuration parameters that are the same between the first DRX configuration and the second DRX configuration can be represented in the single RRC UE-DRX configuration using a single value. For example, if a particular UE uses a same UE-DRX cycle length for both a first DRX configuration parameter and a second DRX configuration parameter, a single RRC UE-DRX configuration can include only one value for the UE-DRX cycle length parameter. In some cases, a UE-DRX configuration can be secondary DRX group. The secondary DRX group can share a same on-duration start offset parameter value with a primary DRX group. Remaining DRX parameters can differ between the primary DRX group and the secondary DRX group. Different DRX configurations (and associated parameters) for the primary DRX group and the secondary DRX group can be indicated to the UE by the base station using separate transmissions (e.g., separate RRC UE-DRX configurations for the primary DRX group and the secondary DRX group) and / or can be indicated using a single transmission (e.g., a single RRC UE-DRX configuration including first and second values for DRX configuration parameters that differ between the primary DRX group and the secondary DRX group).

[0151] In another illustrative example, a UE can receive information indicating a DRX configuration for the UE associated with a DTX disable state for a cell from a serving base station or gNB. For example, the UE can receive a cell DTX disable state UE-DRX configuration parameter in a same or similar manner as described above for the second DRX configuration.

[0152] The UE can obtain a cell DTX enable state UE-DRX configuration parameter (e.g., the first DRX configuration described above) by overriding one or more DRX configuration parameter values of the cell DTX disable UE-DRX configuration. For example, the UE can override one or more DRX configuration parameter values for the cell DTX disable UE-DRX configuration using corresponding parameter values in one or more of (or both) a cell DTX configuration implemented by the base station and / or a cell DRX configuration implemented by the base station. In some aspects, the cell DTX configuration and / or the cell DRX configuration implemented by the base station can be signaled to the UE by the base station or can otherwise be available at the UE based on registering or communicating with a serving base station or gNB associated with a cell of the UE.

[0153] For example, the overlay may be performed based on one or more configuration parameters that are the same between the cell DTX configuration, the cell DRX configuration, and the UE-DRX configuration during the cell DTX enabled state (e.g., Figure 6A ). Shared configuration parameters between the cell DTX / DRX configuration and the UE-DRX configuration may include at least an on-duration start offset and a DRX cycle. For example, when cell DTX is enabled, the UE-DRX configuration may be aligned with the cell DTX on-duration (e.g., within the cell DTX on-duration), and the cell DTX cycle 620 may be the same as the UE-DRX cycle for each UE in the cell. Because the cell DTX cycle 620 is the same as the UE-DRX cycle, the cell DTX cycle 620 and the UE-DRX cycle have the same start time.

[0154] In some cases, UE-DRX can be implemented based on PDCCH monitoring dynamically granting scheduling or triggering (e.g., corresponding to or indicating one or more downlink transmissions from a serving base station or gNB to the UE). In some examples, the UE can perform autonomous transmissions and / or receptions that are not dynamically scheduled or triggered by the PDCCH. In one illustrative example, systems and techniques can be used to align autonomous UE transmissions and / or receptions with cell DTX and cell DRX. For example, aligning the period associated with autonomous UE transmissions and / or receptions with the period associated with cell DTX and cell DRX can improve UE and network power efficiency. In some cases, when cell DTX and cell DRX are enabled, the signal density and / or number of channels associated with autonomous UE transmissions and / or receptions can be reduced. Based on the reduced signal density and / or number of channels, the serving base station or gNB can reduce blind detection of potential UE uplink transmissions. Additionally, one or more UEs in the cell can reduce their power consumption based on the reduced transmissions from the serving base station or gNB.

[0155] In another illustrative example, the UE may switch between different UE-DRX configurations based on the cell DTX and cell DRX enabled or disabled state of the serving base station or gNB (e.g., as described above), and may additionally switch between different UE configurations based on the channel and / or signal type associated with communications between the UE and the serving base station or gNB. For example, different UE-DRX configurations may be provided for one or more (or all) of configured PUSCH grants, semi-persistently scheduled PDSCHs, search space sets (SSSs) or SSS groups for PDCCH monitoring, PUCCH resources, scheduling requests, random access resources, active bandwidth parts (BWPs), etc.

[0156] In some cases, the systems and techniques described herein can be used to implement UE configurations for one or more UEs that are implementing or running an extended reality (XR) application or service. In some examples, the XR application or service can be associated with both high peak throughput and low latency service requirements (e.g., service requirements from a serving base station or gNB). In one illustrative example, the systems and techniques can be used to maintain service continuity for XR UEs when a serving base station or gNB enables and disables cell DTX and / or cell DRX for a cell of the XR UEs. For example, cell DTX and cell DRX can be enabled and disabled without interrupting service for the XR UEs and / or XR users.

[0157] In some cases, even a single XR user can consume a large portion of available resources in a cell. When traffic load in a cell is not low (e.g., relatively high), the number of active users in the cell can be relatively small if some users have high throughput (e.g., are XR users). In one illustrative example, the systems and techniques can maintain service continuity for XR users based on implementing cell DRX / DTX enabling and disabling that is transparent to the XR users and XR services. For example, the systems and techniques can maintain service continuity for XR users by configuring cell DTX cycles and cell DRX cycles to align with XR traffic periods.

[0158] In one illustrative example, cell DTX and cell DRX cycles of a serving base station or gNB associated with one or more XR UEs, XR users, and / or XR services, etc. can align with non-integer periods of XR traffic. For example, a non-integer period of XR traffic can correspond to an XR video generation rate. In some aspects, a 30 frames per second (fps) XR video generation rate can correspond to a 33.33 ms period. A 60 fps XR video generation rate can correspond to a 16.66 ms period. A 120 fps XR video generation rate can correspond to an 8.33 ms period. In some aspects, a single cell DTX cycle or a single cell DRX cycle can be configured for all XR users of a cell based on a highest video generation rate among the XR users of the cell (e.g., in examples where XR users of a cell have different XR video generation rates).

[0159] Figure 7is a flow chart illustrating an example of a process 700 for wireless communication. The process 700 can be performed by a first network entity or by a component or system (e.g., a chip set) of the first network entity. The first network entity can be a UE (e.g., a mobile device such as a mobile phone, a network-connected wearable device such as a watch, an extended reality device such as a virtual reality (VR) device or an augmented reality (AR) device, a vehicle or a component or system of a vehicle, or other types of UEs) or other types of network entities. In some examples, the first network entity can be a UE that is the same as or similar to one or more UEs in any of Figure 1 、 Figure 2 、 Figure 3 、 Figure 4 , etc. The operations of process 700 can be implemented as software components that are executed and run on one or more processors (e.g., processor 910 of Figure 9 or other processors). Further, the transmission and reception of signals by the wireless communication devices in process 700 can be enabled via one or more antennas and / or one or more wireless transceivers (e.g., the antennas and / or wireless transceivers of any of Figure 2 、 Figure 4 、 Figure 9 , etc.).

[0160] At block 702, the first network entity (or a component thereof) can receive information indicating a first discontinuous reception (DRX) configuration for the first network entity, where the first DRX configuration indicates a first DRX on duration for the first network entity. For example, the first network entity can be the same as or similar to one or more of the UE 104 of Figure 1 , Figure 2 , Figure 3 , Figure 4 the user equipment computing system 470 of Figure 6A In some cases, the first DRX on duration for the first network entity can be the same as or similar to one or more of the UE DRX on durations 632, 642, 652 (and / or the UE DRX on durations 634, 644, 654) of Figure 1 , Figure 2 ,

[0161] In some cases, the first DRX configuration includes a first plurality of values, where each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters. For example, the plurality of DRX configuration parameters can include one or more of a DRX on-duration value, a DRX on-duration start offset value, a DRX cycle duration value, a DRX on-duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round-trip time (RTT) timer value, or a UL RTT timer value.

[0162] In some cases, to receive the information indicating the first DRX configuration, the first network entity (or a component thereof) can receive, from a second network entity (e.g., a base station, a gNB, etc.), a first radio resource control (RRC) signal including the information indicating the first DRX configuration.

[0163] In some cases, to receive the information indicating the first DRX configuration, the first network entity (or a component thereof) can receive configuration information associated with a second network entity (e.g., a base station, a gNB, etc.), where the configuration information includes the information indicating the first DRX configuration. For example, the first DRX configuration of the first network entity (e.g., a UE) can be associated with a DTX enablement status of the second network entity (e.g., a base station, a gNB, etc.). In some cases, the first DRX configuration of the first network entity can be the same as or similar to a DTX configuration of the second network entity.

[0164] In some examples, the first DRX on-duration overlaps in time with at least a portion of a respective DRX on-duration associated with each UE of a plurality of UEs, the first network entity included in the plurality of UEs. For example, the first DRX on-duration can be the same as or similar to the UE1 DRX on-duration 632, which overlaps in time with at least a portion of respective DRX on-durations 642, 652 associated with UE2 and UE3, respectively. Figure 6A In some examples, the first DRX on-duration overlaps in time with at least a portion of a respective DRX on-duration associated with each UE of a plurality of UEs, the first network entity included in the plurality of UEs. For example, the first DRX on-duration can be the same as or similar to the UE1 DRX on-duration 632, which overlaps in time with at least a portion of respective DRX on-durations 642, 652 associated with UE2 and UE3, respectively.

[0165] In some cases, the first DRX on-duration and the respective DRX on-duration associated with each UE of the plurality of UEs are within a DTX on-duration of the second network entity. For example, the first DRX on-duration 632 and the respective DRX on-durations 642 and 652 are each within the cell DTX on-duration 622 of the Figure 6A In some examples, the first DRX configuration can indicate a DRX cycle duration, where the DRX cycle duration is the same as a DTX cycle duration associated with the DTX enablement status. For example, the DRX cycle duration can be the same as the cell DTX cycle duration 624 of the Figure 6AThe DTX cycle duration of the cell DTX cycle 620 is the same as the DTX cycle duration of the UE DTX cycle 630.

[0166] In some examples, the first DRX configuration indicates a first DRX on duration start offset associated with the first network entity. The first DRX on duration start offset can be the same as a respective DRX on duration start offset associated with each of the plurality of UEs. For example, Figure 6A Each of the UE-DRX on durations 632, 642, 652 is associated with the same DRX on duration start offset. In some examples, the first DRX on duration start offset is a time offset from a start of a DTX cycle associated with a DTX enabled state of the second network entity (e.g., base station, gNB, etc.). For example, the DTX cycle associated with the DTX enabled state can be the same as or similar to the cell DTX cycle 620 of the first network entity. Figure 6A

[0167] At block 704, the first network entity (or a component thereof) can receive information indicating a second DRX configuration for the first network entity, where one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration. In some examples, the first DRX configuration is associated with a DTX enabled state of a second network entity (e.g., base station, gNB, etc.) and the second DRX configuration is associated with a DTX disabled state of the second network entity.

[0168] In some cases, the first DRX configuration is received based on receiving, from the second network entity, a first RRC signal including information indicating the first DRX configuration. The second DRX configuration can be received based on receiving, from the second network entity, a second RRC signal including information indicating the second DRX configuration. The second RRC signal is different from the first RRC signal.

[0169] In some examples, receiving the information indicating the first DRX configuration and receiving the information indicating the second DRX configuration includes receiving, from the second network entity, a RRC signal including information indicating the first DRX configuration and including information indicating the second DRX configuration. In some cases, the RRC signal indicates one or more DRX configuration parameters, where each respective DRX configuration parameter of the one or more DRX configuration parameters is associated with a first value corresponding to the first DRX configuration and a second value corresponding to the second DRX configuration.

[0170] ​In some examples, to receive the information indicating the first DRX configuration, the first network entity (or a component thereof) is configured to receive configuration information associated with the second network entity. For example, the first network entity can receive DTX configuration information of the second network entity, where the DTX configuration includes the information indicating the first DRX configuration. For example, the first DRX configuration can be the same as or otherwise based on one or more parameters of the DTX configuration corresponding to a DTX enablement status of the second network entity.

[0171] In some aspects, a DRX on-duration start offset parameter value included in the second DRX configuration can be replaced with a corresponding on-duration start offset parameter value included in the configuration information associated with the network entity. In some cases, a DRX cycle duration parameter value included in the second DRX configuration can be replaced with a corresponding cycle duration parameter value included in the configuration information associated with the second network entity. In some cases, the configuration information associated with the second network entity includes one or more of a DRX configuration associated with the second network entity or a DTX configuration associated with the second network entity.

[0172] In some cases, the first DRX configuration includes a first plurality of values, where each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters. The second DRX configuration can include a second plurality of values, where each value of the second plurality of values corresponds to a respective DRX configuration parameter of the plurality of DRX configuration parameters. In some examples, at least one value of the second plurality of values corresponds to a particular DRX configuration parameter and is different than at least one value of the first plurality of values that corresponds to the particular DRX configuration parameter. For example, the particular DRX configuration parameter can include one or more of a DRX on-duration value, a DRX on-duration start offset value, a DRX cycle duration value, a DRX on-duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round-trip time (RTT) timer value, or a UL RTT timer value.

[0173] At block 706, the first network entity (or a component thereof) can determine a discontinuous transmission (DTX) enablement status of the second network entity, where the DTX enablement status corresponds to a DTX on-duration of the second network entity, and where the first DRX on-duration is within the DTX on-duration of the second network entity. For example, the DTX enablement status can correspond to a DTX on-duration 622 of Figure 6A The first DRX on-duration can be the same as or similar to a UE1 DRX on-duration 632 of Figure 6A which is within the DTX on-duration 622 of Figure 6Awithin a DTX on duration 622 of the DTX enabled state.

[0174] In some examples, the DTX enabled state is aligned with the DRX enabled state of the second network entity based on the DTX enabled state having a period that is a multiple of a period of the DRX enabled state of the second network entity, or the DRX enabled state having a period that is a multiple of a period of the DTX enabled state of the second network entity. For example, Figure 6A The DTX enabled state 622 of the first network entity can be aligned with Figure 6A the DRX enabled state 612 of the second network entity. The period of the DTX enabled state can be the same as or similar to the cell DTX cycle 620, and the period of the DRX enabled state can be the same as or similar to the cell DRX cycle 610. In some cases, at least a portion of a DTX on duration corresponding to the DTX enabled state (e.g., the cell DTX on duration 622) can overlap with at least a portion of a DRX on duration corresponding to the DRX enabled state (e.g., the cell DRX on duration 612).

[0175] In some cases, the period of the DTX enabled state is the same as the period of the DRX enabled state. In some examples, the DTX enabled state is aligned with the DRX enabled state based on a DTX on duration start offset associated with the period of the DTX enabled state being the same as a DRX on duration start offset associated with the period of the DRX enabled state.

[0176] In some aspects, to determine the DTX enabled state of the second network entity, the first network entity (or a component thereof) is configured to receive, from the second network entity, information indicating the DTX enabled state of the second network entity. In some examples, the first network entity (or a component thereof) can determine the DTX enabled state of the second network entity based on receiving or not receiving a signal relative to a time period. For example, the first network entity can determine the DTX enabled state of the second network entity based on not receiving a signal relative to the time period, and can determine the DTX disabled state of the second network entity based on receiving a signal relative to the time period.

[0177] In some cases, the second DRX configuration indicates a second DRX on duration of the first network entity and is associated with the DTX disabled state of the second network entity. The second DRX on duration can not overlap in time with a respective DRX on duration associated with each of a plurality of user equipment (UEs). For example, the second DRX on duration can not overlap in time with a respective DRX on duration associated with each of a plurality of user equipment (UEs). Figure 6BUE1 DRX on duration 663 is the same or similar to UE2 DRX on duration 673 and UE3 DRX on duration 683, which do not overlap in time with respective DRX on durations 672 and 683 associated with UE2 and UE3, respectively. In some cases, the first network entity (or a component thereof) can be configured to receive downlink information from the second network entity during the second DRX on duration. In some examples, the respective DRX on durations associated with each of the plurality of UEs and the second DRX on duration are associated with a same DRX cycle duration. For example, Figure 6B UE1 DRX on duration 663, UE2 DRX on duration 673, and UE3 DRX on duration 683 can each be associated with a same DRX cycle duration of a cell DRX cycle 660.

[0178] In some cases, the second DRX configuration indicates a second DRX on duration start offset associated with the first network entity, where the second DRX on duration start offset is different from respective DRX on duration start offsets associated with each of the plurality of UEs. For example, Figure 6B UE1 DRX on duration 663, UE2 DRX on duration 673, and UE3 DRX on duration 683 can each be associated with a different respective DRX on duration start offset. The offset can be a time offset relative to the DRX cycle 660.

[0179] At block 708, the first network entity (or a component thereof) can receive downlink information from the second network entity during the first DRX on duration. In some cases, the first DRX configuration is associated with a DTX enable status of the second network entity and a channel type associated with the downlink information. For example, the channel type associated with the downlink information can be a configured grant physical uplink shared channel (PUSCH), a semi-persistent scheduling physical downlink shared channel (PDSCH), a search space set (SSS), or a SSS group for physical downlink control channel (PDCCH) monitoring. In some cases, the channel type associated with the downlink information is associated with a physical uplink control channel (PUCCH) resource, a scheduling request, a random access resource, or an active bandwidth part (BWP).

[0180] In some examples, a cycle associated with the DTX enabled state is the same as a cycle associated with a DTX disabled state of the second network entity, where the cycle and a cycle of extended reality (XR) transmissions associated with the XR service of the first network entity are aligned. In some cases, one or more of a DTX cycle period associated with the DTX enabled state of the second network entity or a DRX cycle period associated with the DRX enabled state are aligned with non-integer periods corresponding to an extended reality (XR) video generation rate of the first network entity. In some examples, a start time associated with the first DRX on duration is the same as or after a start time associated with the DTX on duration, and an end time associated with the first DRX on duration is the same as or before an end time associated with the DTX on duration.

[0181] Figure 8 is a flow diagram illustrating another example of a process 800 for wireless communication. The process 800 can be performed by a first network entity or by a component or system of the first network entity (e.g., a chipset). The first network node can be a base station (e.g., a gNB, an eNB, or other base station), a portion of a base station (e.g., a CU, a DU, a RU, a RIC, or other portion of a base station having a disaggregated architecture), or other type of network entity. In some examples, the first network entity can be the same as or similar to one or more base stations of any of Figure 1 Figure 2 Figure 3 and the like. The operations of process 800 can be implemented as software components that are executed and run on one or more processors (e.g., processor(s) 910 of computing system 900, or other processors). Further, the transmission and reception of signals by the wireless communication devices in process 800 can be enabled via one or more antennas and / or one or more wireless transceivers (e.g., antennas and / or wireless transceivers of any of the devices of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10). Figure 9 Figure 2 Figure 4 Figure 9

[0182] At block 802, the first network entity (or a component thereof) can transmit information indicating a first discontinuous reception (DRX) configuration for a second network entity, where the first DRX configuration indicates a first DRX on duration for the second network entity. For example, the second network entity can be the same as or similar to the UE 104 of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10, the UE 104 of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10, the UE 104 of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10, and / or the user equipment computing system 470 of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10. Figure 1 Figure 2 Figure 3 Figure 4 In some cases, the first DRX on duration of the second network entity can be the same as or similar to a DRX on duration of the UE 104 of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10, the UE 104 of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10, the UE 104 of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10, and / or the user equipment computing system 470 of FIGS. 1, 2, 3, 4, 5, 6, 7, 8, 9, and / or 10. Figure 6A ​​​​​​​​​one or more of the UE DRX on durations 632, 642, 652 (and / or the UE DRX on durations 634, 644, 654) of the UE 1. In some examples, the first DRX configuration is associated with a discontinuous transmission (DTX) enable state of the first network entity. For example, the first network entity can be a base station, a gNB, and / or the like, and can be associated with Figure 1 the base station 102, 180, Figure 2 one or more of the base station 102, and / or the like.

[0183] In some cases, the first DRX configuration includes a first plurality of values, where each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters. For example, the plurality of DRX configuration parameters can include one or more of: a DRX on duration value, a DRX on duration start offset value, a DRX cycle duration value, a DRX on duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round trip time (RTT) timer value, or a UL RTT timer value.

[0184] In some cases, to transmit the information indicating the first DRX configuration, the first network entity (or a component thereof) can transmit, to a second network entity (e.g., a UE), a first radio resource control (RRC) signal including the information indicating the first DRX configuration.

[0185] In some cases, to transmit the information indicating the first DRX configuration, the first network entity (or a component thereof) can transmit configuration information associated with the first network entity (e.g., a base station, a gNB, and / or the like), where the configuration information includes the information indicating the first DRX configuration. For example, the first DRX configuration of the second network entity (e.g., a UE) can be associated with a DTX enable state of the first network entity (e.g., a base station, a gNB, and / or the like). In some cases, the first DRX configuration of the second network entity can be the same as or similar to a DTX configuration of the first network entity.

[0186] In some examples, the first DRX on duration overlaps in time with at least a portion of a respective DRX on duration associated with each UE of a plurality of UEs, the first network entity included in the plurality of UEs. For example, the first DRX on duration can be the same as or similar to the UE 1 DRX on duration 632, which overlaps in time with at least a portion of the respective DRX on durations 642, 652 associated with the UE 2 and the UE 3, respectively. Figure 6A

[0187] ​At block 804, the first network entity (or a component thereof) can transmit information indicating a second DRX configuration for the second network entity, where one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration. For example, the first DRX configuration (e.g., corresponding to a DTX enabled state for the first network entity) can include a first plurality of values, where each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters. The second DRX configuration (e.g., corresponding to a DTX disabled state for the first network entity) can include a second plurality of values, where each value of the second plurality of values corresponds to a respective DRX configuration parameter of the plurality of DRX configuration parameters. At least one value of the second plurality of values corresponds to a particular DRX configuration parameter and is different from at least one value of the first plurality of values that corresponds to the particular DRX configuration parameter. In some examples, the particular DRX configuration parameter includes one or more of: a DRX on duration value, a DRX on duration start offset value, a DRX cycle duration value, a DRX on duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round trip time (RTT) timer value, or a UL RTT timer value.

[0188] At block 806, the first network entity (or a component thereof) can determine a discontinuous transmission (DTX) enabled state for the first network entity, where the DTX enabled state corresponds to a DTX on duration for the first network entity, and where the first DRX on duration is within the DTX on duration for the first network entity. In some cases, the DTX enabled state for the first network entity can correspond to a cell DTX on duration 622 of Figure 6A and / or can correspond to a cell DTX cycle 620 of Figure 6A In some examples, the first network entity (or a component thereof) can transmit information indicating the DTX enabled state for the first network entity to the second network entity (e.g., a UE). In some examples, the first network entity (or a component thereof) can indicate the DTX enabled state for the first network entity to the second network entity (e.g., a UE) based on transmitting or not transmitting a signal relative to a time period. For example, the first network entity (or a component thereof) can indicate the DTX enabled state for the first network entity based on not transmitting a signal relative to the time period. The first network entity (or a component thereof) can indicate a DTX disabled state for the first network entity based on transmitting a signal relative to the time period.

[0189] In some cases, the DTX enabled state is aligned with a DRX enabled state for the first network entity. For example, the DTX enabled state (e.g., a DTX on duration 622) can be aligned with a DRX on duration 620 for the first network entity. Figure 6AThe DTX on duration 622) may be related to the DRX enabled state of the first network entity (e.g., Figure 6A In some cases, the DTX enabled state of the first network entity may be aligned with the DRX enabled state of the first network entity based on: the period of the DTX enabled state (e.g., such as Figure 6A The cell DTX cycle 620) is a period of the DRX enabled state of the first network entity (e.g., such as Figure 6A In some cases, at least a portion of the DTX-on Duration corresponding to the DTX-enabled state overlaps with at least a portion of the DRX-on Duration corresponding to the DRX-enabled state.

[0190] In some examples, the periodicity of the DTX enabled state is the same as the periodicity of the DRX enabled state. Figure 6A The cell DTX cycle 620 can be Figure 6A The cell DRX cycle 610 is the same. In some cases, the DTX enabled state is aligned with the DRX enabled state based on the DTX on-duration start offset associated with the period of the DTX enabled state and the DRX on-duration start offset associated with the period of the DRX enabled state being the same.

[0191] At block 808, the first network entity (or a component thereof) may send downlink information to the second network entity during the first DRX On Duration. In some cases, the first DRX configuration is associated with the DTX enabled state of the first network entity and a channel type associated with the downlink information. For example, the channel type associated with the downlink information may be a configured grant physical uplink shared channel (PUSCH), a semi-persistently scheduled physical downlink shared channel (PDSCH), a search space set (SSS), or an SSS group for physical downlink control channel (PDCCH) monitoring. In some cases, the channel type associated with the downlink information is associated with a physical uplink control channel (PUCCH) resource, a scheduling request, a random access resource, or an active bandwidth part (BWP).

[0192] In some examples, the period associated with the DTX enabled state is the same as the period associated with the DTX disabled state of the first network entity, where the period and a period of XR transmissions associated with an extended reality (XR) service of the second network entity (e.g., UE) are aligned. In some cases, one or more of a DTX cycle period associated with the DTX enabled state of the first network entity or a DRX cycle period associated with the DRX enabled state is aligned with a non-integer period corresponding to an extended reality (XR) video generation rate of the second network entity (e.g., UE). In some examples, a start time associated with the first DRX on duration is the same as or after a start time associated with the DTX on duration, and an end time associated with the first DRX on duration is the same as or before an end time associated with the DTX on duration.

[0193] In some examples, the processes described herein (e.g., process 700, process 800, and / or other processes described herein) can be performed by a computing device or apparatus (e.g., a network node, such as a UE, a base station, a portion of a base station, etc.). For example, as noted above, process 700 can be performed by a UE, and process 800 can be performed by a base station or a portion of a base station. In another example, process 700 and / or process 800 can be performed by a computing device having Figure 9 the computing architecture illustrated in FIG. 9. For example, a wireless communication device having the computing architecture illustrated in FIG. 9 can include components of a UE, and can implement operations of the UE 102, the UE 202, the UE 302, the UE 402, the UE 502, the UE 602, the UE 702, the UE 802, and / or the like. Figure 9 In some examples, a wireless communication device having the computing architecture illustrated in FIG. 9 can include components of a base station, and can implement operations of the base station 104, the base station 204, the base station 304, the base station 404, the base station 504, the base station 604, the base station 704, the base station 804, and / or the like. Figure 7 and / or Figure 8 operations of the UE 102, the UE 202, the UE 302, the UE 402, the UE 502, the UE 602, the UE 702, the UE 802, and / or the like.

[0194] In some cases, a computing device or apparatus can include various components, such as one or more input devices, one or more output devices, one or more processors, one or more microprocessors, one or more microcomputers, one or more cameras, one or more sensors, and / or other components that are configured to perform the steps of processes described herein. In some examples, a computing device can include a display, one or more network interfaces configured to communicate and / or receive data, any combination thereof, and / or other components. The one or more network interfaces can be configured to communicate and / or receive wired and / or wireless data, including data according to 3G, 4G, 5G, and / or other cellular standards, data according to WiFi (802.1 lx) standards, data according to Bluetooth ™ standards, data according to Internet Protocol (IP) standards, and / or other types of data.

[0195] Components of computing devices can be implemented in circuitry. For example, components can include or be implemented using electronic circuitry, and / or can be implemented using computer software, firmware, or any combination thereof, and / or can be implemented using computer software, firmware, or any combination thereof, executing on one or more programmable electronic circuit(s) (e.g., microprocessors, graphics processing units (GPUs), digital signal processors (DSPs), central processing units (CPUs), and / or other suitable electronic circuitry), and / or can be implemented using computer software, firmware, or any combination thereof, for performing various operations described herein.

[0196] Processes 700 and 800 are illustrated as logical flow graphs, the operations of which represent a sequence of operations that can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored, for example, on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and / or in parallel to implement the processes.

[0197] Additionally, processes 700, 800, and / or other processes described herein can be performed under the control of one or more computer systems configured with executable instructions, and can be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processing units, by hardware or combinations thereof. As noted above, the code can be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. Computer-readable or machine-readable storage media can be non-transitory.

[0198] Figure 9 is a diagram that illustrates an example of a system for implementing certain aspects of the technology. Specifically, Figure 9 An example of a computing system 900 is illustrated, which can be, for example, any computing device that makes up an internal computing system, a remote computing system, a camera, or any component thereof, where the components of the system communicate with one another using a connection 905. The connection 905 can be a physical connection using a bus, or a direct connection into a processor 910, such as in a chipset architecture. The connection 905 can also be a virtual connection, a networking connection, or a logical connection.

[0199] In some aspects, the computing system 900 is a distributed system in which the functionality described herein can be distributed within a data center, multiple data centers, a peer-to-peer network, etc. In some aspects, one or more of the described system components represent many such components each performing some or all of the functionality the component is described to perform. In some aspects, the components can be physical or virtual devices.

[0200] The example system 900 includes at least one processing unit (CPU or processor) 910 and a connection 905 that communicatively couples various system components including the system memory 915, such as read-only memory (ROM) 920 and random-access memory (RAM) 925, to the processor 910. The computing system 900 can include a cache of the processor 910 in which some of the system components can be held in order to increase access speed. The computing system 900 can further include memory storage components 930 on which the processor 910 can execute.

[0201] The processor 910 can include any general purpose processor and a hardware service or software service, such as the services 932, 934, and 936 stored in storage device 930, configured to control the processor 910 as well as a specific or special-purpose processor where software instructions are incorporated into the actual processor design. The processor 910 can essentially be a completely self-contained computing system, containing multiple cores or processors, a bus, memory controller, and cache, etc. Multi-core processing systems can be symmetric or asymmetric.

[0202] To enable user interaction, the computing system 900 includes an input device 945, which can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and the like. The computing system 900 can also include output device(s) 935, which can be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multi-modal systems can enable a user to provide multiple types of input to communicate with the computing system 900.

[0203] The computing system 900 can include communication interface 940 that can generally govern and manage the user input and system output. The communication interface can receive and / or send wired or wireless communications using wired and / or wireless transceivers, including utilizing audio jacks / plugs, microphone jacks / plugs, universal serial bus (USB) ports / plugs, Apple ™ Lightning ™ ports / plugs, Ethernet ports / plugs, fiber optic ports / plugs, dedicated wired ports / plugs, 3G, 4G, 5G, and / or other cellular data network wireless signal transfers, Bluetooth ™ wireless signal transfers, Bluetooth ™Low power (BLE) wireless signal transfer, IBEACON ™ wireless signal transfer, radio frequency identification (RFID) wireless signal transfer, near field communication (NFC) wireless signal transfer, dedicated short-range communications (DSRC) wireless signal transfer, 802.11 Wi-Fi wireless signal transfer, wireless local area network (WLAN) signal transfer, visible light communication (VLC), worldwide interoperability for microwave access (WiMAX), infrared (IR) communication wireless signal transfer, public switched telephone network (PSTN) signal transfer, integrated services digital network (ISDN) signal transfer, ad hoc network signal transfer, radio wave signal transfer, microwave signal transfer, infrared signal transfer, visible light signal transfer, ultraviolet light signal transfer, wireless signal transfer along the electromagnetic spectrum, or some combination thereof. The communication interface 940 can also include one or more global navigation satellite system (GNSS) receivers or transceivers for determining a location of the computing system 900 based on one or more signals received from one or more satellites associated with one or more GNSS systems. GNSS systems include, but are not limited to, the United States’ Global Positioning System (GPS), the Russian Global Navigation Satellite System (GLONASS), the Chinese BeiDou Navigation Satellite System (BDS), and the European Galileo GNSS. There is no limitation as to operation on any particular hardware arrangement, and thus the underlying features herein can be readily substituted for improved hardware or firmware arrangements as they are developed.

[0204] The storage device 930 can be a non-volatile and / or non-transitory and / or computer-readable memory device, and can be a hard disk or other type of computer readable medium such as a cassette tape, flash memory card, solid-state memory device, digital versatile disc, cartridge tape, flexible disk, floppy disk, hard disk, magnetic tape, magnetic strip / magnetic stripe, any other magnetic storage medium, flash memory, memristor memory, any other solid-state memory, compact disc read-only memory (CD-ROM) optical disc, rewritable compact disc (CD) optical disc, digital video disc (DVD) optical disc, Blu-ray disc (BDD) optical disc, holographic optical disc, another optical medium, secure digital (SD) card, micro secure digital (microSD) card, Memory Stick ®card, a smart card chip, an EMV chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, another integrated circuit (IC) chip / card, a random access memory (RAM), a static RAM (SRAM), a dynamic RAM (DRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash EPROM (FLASHEPROM), a cache memory (e.g., a level 1 (L1) cache, a level 2 (L2) cache, a level 3 (L3) cache, a level 4 (L4) cache, a level 5 (L5) cache, or other (L#) cache), a resistive random access memory (RRAM / ReRAM), a phase change memory (PCM), a spin transfer torque RAM (STT-RAM), another memory chip or cartridge, and / or a combination thereof.

[0205] Storage devices 930 may include software services, servers, services, and the like. When the code defining such software is executed by processor 910, the code enables the system to perform a function. In some aspects, hardware services that perform a particular function may include software components stored on a computer-readable medium that interfaces with the necessary hardware components (such as processor 910, connection 905, output device 935, etc.) to perform the function. The term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions and / or data. Computer-readable media may include non-transitory media that can store data and does not include carrier waves and / or transient electronic signals propagated wirelessly or via wired connections. Examples of non-transitory media may include, but are not limited to, magnetic disks or tapes, optical storage media (such as compact discs (CDs) or digital versatile discs (DVDs)), flash memory, memory, or storage devices. Computer-readable media can store thereon code and / or machine-executable instructions that can represent a process, function, subroutine, program, routine, subroutine, module, software package, category, or any combination of instructions, data structures, or program statements. A code segment can be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, independent variables, parameters, or memory contents. Information, independent variables, parameters, data, etc. can be passed, forwarded, or sent via any suitable means, including memory sharing, message passing, token passing, network sending, etc.

[0206] In the description above, specific details are set forth in order to provide a thorough understanding of various aspects and examples provided herein. However, one skilled in the art will recognize that the application is not limited to the specifics recited. Thus, although exemplary aspects of the application have been described in detail herein, it should be understood that the inventive concepts can be embodied in other ways without departing from the scope of the application. The detailed description is to be considered in conjunction with the drawings and the appended claims and various embodiments can be used in a variety of environments and applications. Therefore, the description and drawings are to be regarded as illustrative in nature and not as restrictive. The methods are described in a particular, sequential order. However, it should be understood that in alternative aspects, the methods can be performed in different orders than those described.

[0207] For the sake of explanation, in some instances the techniques can be presented with reference to specific configurations and arrangements of functional blocks, components, steps or routines. One skilled in the art will recognize that the aspects can be practiced with other elements and in other arrangements and configurations, without departing from the scope of the aspects. For example, the steps can be performed in an order other than that described. Additionally, the steps can be performed by different components or structures or under different arrangements and architectures. Furthermore, various other aspects are disclosed and can be apparent from the disclosure and these aspects can be implemented and used separately or in combination with other aspects disclosed herein.

[0208] Furthermore, those skilled in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0209] Various aspects can be described herein as processes or methods, which can be depicted as flowchart illustrations, flow diagrams, data flow diagrams, structure diagrams, or block diagrams. Although the processes can be described in a particular sequential order, many of the processes can be performed concurrently, in parallel, or concurrently. Further, the order of the processes can be re-arranged. The processes terminate when their functions are completed, but can also terminate in the middle of the processes. The processes can correspond in part to the methods, functions, procedures, subroutines, subprograms, etc. When the processes correspond to functions, the functions can return results, data, information, etc. to the calling function or the main function.

[0210] The processes and methods described above can be implemented using stored computer-executable instructions or computer-executable instructions accessible from a computer-readable medium. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or a processing device to perform a certain function or group of functions. Portions of computer resources used can be accessed over a network. The computer-executable instructions can be, for example, binaries, intermediate format instructions such as assembly language, firmware, source code, etc. Examples of computer-readable media that can be used to store instructions, information used by the described examples, and / or information created during execution of the described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, etc.

[0211] In some aspects, computer-readable storage devices, media and memory can include cables or wireless signals that contain bitstreams, etc. However, non-transitory computer-readable storage media specifically excludes such media as power supply, carrier waves, electromagnetic waves, and signals per se, among others, when referred to.

[0212] Those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that can be referenced throughout the above description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof consistent with the particular application, as would be understood by one of ordinary skill in the art.

[0213] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and may be implemented in any of a variety of form factors. When implemented in software, firmware, middleware, or microcode, program code or code segments (e.g., a computer program product) for performing the necessary tasks may be stored in a computer-readable or machine-readable medium. A processor may perform the necessary tasks. Examples of form factors include: a laptop, smartphone, mobile phone, tablet, or other small form factor personal computer, personal digital assistant, rack-mounted device, stand-alone device, etc. The functionality described herein may also be embodied in a peripheral device or add-in card. By way of further example, such functionality may also be implemented on different chips or circuit boards in different processes executed on a single device.

[0214] Instructions, media for transmitting such instructions, computing resources for executing them, and other structures for supporting such computing resources are example means for providing the functionality described in this disclosure.

[0215] The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of a variety of devices, such as general-purpose computers, wireless communication devices, or integrated circuit devices with multiple uses, including applications in wireless communication devices and other devices. Any features described as modules or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques may be implemented at least in part by a computer-readable data storage medium containing program code, which includes instructions that, when executed, perform one or more of the methods, algorithms, and / or operations described above. The computer-readable data storage medium may form part of a computer program product, which may include packaging materials. The computer-readable medium may include memory or data storage media, such as random access memory (RAM) (such as synchronous dynamic random access memory (SDRAM)), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, and the like. Additionally or alternatively, the techniques may be implemented at least in part by a computer-readable communication medium that carries or communicates program code in the form of instructions or data structures and that can be accessed, read, and / or executed by a computer, such as a propagated signal or wave.

[0216] The program code can be executed by a processor, which can include one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application-specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Such a processor can be configured to perform any of the techniques described in this disclosure. A general-purpose processor can be a microprocessor; but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Accordingly, the term “processor,” as used herein can refer to any of the foregoing structure, any combination of the foregoing structure, or any other structure or apparatus suitable for implementation of the techniques described herein.

[0217] Those of ordinary skill in the art will appreciate that the less than (“<”) and greater than (“>”) symbols or terms used herein can be replaced with less than or equal to (“ ”) ” and greater than or equal to (“ ”) symbols, respectively, without departing from the scope of this description.

[0218] Where components are described as being “configured to” perform certain operations, such configuration can be accomplished, for example, by designing the electronic circuitry or other hardware of the components to perform the operation, by programming the components (e.g., microprocessors or other suitable electronic circuits) to perform the operation, or any combination thereof.

[0219] The phrase “coupled to” or “communicatively coupled to” means a direct or indirect physical connection between any components, and / or a direct or indirect communication between any components (e.g., connected to another component through a wired or wireless connection and / or other suitable communication interface).

[0220] Claim language or other language reciting “at least one of” a set and / or “one or more of” a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, claim language reciting “at least one of A and B” or “at least one of A or B” means A, B, or A and B. In another example, claim language reciting “at least one of A, B, and C” or “at least one of A, B, or C” means A, B, C, or A and B or A and C or B and C, A and B and C, or any repetition of information or data (e.g., A and A, B and B, C and C, A and A and B, etc.), or any other ordering, repetition, or combination of A, B, and C. Language reciting “at least one of” a set and / or “one or more of” a set does not limit the set to the items listed in the set. For example, claim language reciting “at least one of A and B” or “at least one of A or B” can mean A, B, or A and B, and can additionally include items not listed in the set of A and B.

[0221] Exemplary aspects of the present disclosure include:

[0222] Aspect 1. A first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to: receive information indicating a first discontinuous reception (DRX) configuration for the first network entity, wherein the first DRX configuration indicates a first DRX on-duration for the first network entity; receive information indicating a second DRX configuration for the first network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determine a discontinuous transmission (DTX) enabled state for a second network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the second network entity, and wherein the first DRX on-duration is within the DTX on-duration for the second network entity; and receive downlink information from the second network entity during the first DRX on-duration.

[0223] Aspect 2. The first network entity of Aspect 1, wherein: the first DRX configuration is associated with the DTX enabled state for the second network entity; and the second DRX configuration is associated with a DTX disabled state for the second network entity.

[0224] Aspect 3. The first network entity of any of aspects 1 through 2, wherein the DTX enabled state is aligned with a DRX enabled state of the second network entity based on: a period of the DTX enabled state being a multiple of a period of the DRX enabled state of the second network entity, or a period of the DRX enabled state being a multiple of a period of the DTX enabled state of the second network entity; and at least a portion of a DTX on duration corresponding to the DTX enabled state overlapping at least a portion of a DRX on duration corresponding to the DRX enabled state.

[0225] Aspect 4. The first network entity of aspect 3, wherein: the period of the DTX enabled state is the same as the period of the DRX enabled state; and the DTX enabled state is aligned with the DRX enabled state based on a DTX on duration start offset associated with the period of the DTX enabled state being the same as a DRX on duration start offset associated with the period of the DRX enabled state.

[0226] Aspect 5. The first network entity of any of aspects 1 through 4, wherein to determine the DTX enabled state of the second network entity, the at least one processor is configured to: receive information from the second network entity indicating the DTX enabled state of the second network entity.

[0227] Aspect 6. The first network entity of any of aspects 1 through 5, wherein to determine the DTX enabled state of the second network entity, the at least one processor is configured to: determine the DTX enabled state of the second network entity based on receiving or not receiving a signal relative to a time period.

[0228] Aspect 7. The first network entity of aspect 6, wherein the at least one processor is configured to: determine the DTX enabled state of the second network entity based on not receiving the signal relative to the time period.

[0229] Aspect 8. The first network entity of any of aspects 6 through 7, wherein the at least one processor is configured to: determine a DTX disabled state of the second network entity based on receiving the signal relative to the time period.

[0230] Aspect 9. The first network entity of any of aspects 1 through 8, wherein: the first DRX configuration comprises a first plurality of values, wherein each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters; the second DRX configuration comprises a second plurality of values, wherein each value of the second plurality of values corresponds to a respective DRX configuration parameter of the plurality of DRX configuration parameters; and at least one value of the second plurality of values corresponds to a particular DRX configuration parameter and is different than at least one value of the first plurality of values that corresponds to the particular DRX configuration parameter.

[0231] Aspect 10. The first network entity of aspect 9, wherein the particular DRX configuration parameter comprises one or more of: a DRX on duration value, a DRX on duration start offset value, a DRX cycle duration value, a DRX on duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round trip time (RTT) timer value, or a UL RTT timer value.

[0232] Aspect 11. The first network entity of any of aspects 1 through 10, wherein the first DRX on duration overlaps in time with at least a portion of a respective DRX on duration associated with each user equipment (UE) of a plurality of UEs, the first network entity included in the plurality of UEs.

[0233] Aspect 12. The first network entity of aspect 11, wherein the first DRX on duration and the respective DRX on duration associated with each UE of the plurality of UEs is within the DTX on duration.

[0234] Aspect 13. The first network entity of any of aspects 11 through 12, wherein the first DRX configuration indicates a first DRX on duration start offset associated with the first network entity, and wherein the first DRX on duration start offset is the same as a respective DRX on duration start offset associated with each UE of the plurality of UEs.

[0235] Aspect 14. The first network entity of aspect 13, wherein the first DRX on duration start offset is a time offset from a start of a DTX cycle associated with the DTX enablement state.

[0236] Aspect 15. The first network entity of any of aspects 11 through 14, wherein the first DRX configuration indicates a DRX cycle duration, and wherein the DRX cycle duration is the same as a DTX cycle duration associated with the DTX enabled state.

[0237] Aspect 16. The first network entity of any of aspects 1 through 15, wherein the second DRX configuration indicates a second DRX ON duration for the first network entity and is associated with a DTX disabled state for the second network entity, and wherein the second DRX ON duration does not overlap in time with a respective DRX ON duration associated with each of a plurality of user equipment (UEs).

[0238] Aspect 17. The first network entity of aspect 16, wherein the at least one processor is further configured to receive downlink information from the second network entity during the second DRX ON duration.

[0239] Aspect 18. The first network entity of any of aspects 16 through 17, wherein the respective DRX ON duration associated with each of the plurality of UEs and the second DRX ON duration are associated with a same DRX cycle duration.

[0240] Aspect 19. The first network entity of any of aspects 16 through 18, wherein: the second DRX configuration indicates a second DRX ON duration start offset associated with the first network entity, and wherein the second DRX ON duration start offset is different from a respective DRX ON duration start offset associated with each of the plurality of UEs.

[0241] Aspect 20. The first network entity of any of aspects 1 through 19, wherein: to receive the information indicating the first DRX configuration, the at least one processor is configured to receive, from the second network entity, a first radio resource control (RRC) signal including the information indicating the first DRX configuration; and to receive the information indicating the second DRX configuration, the at least one processor is configured to receive, from the second network entity, a second RRC signal including the information indicating the second DRX configuration.

[0242] Aspect 21. The first network entity of any one of Aspects 1-20, wherein, to receive the information indicating the first DRX configuration and to receive the information indicating the second DRX configuration, the at least one processor is configured to receive, from the second network entity, a radio resource control (RRC) signal that includes the information indicating the first DRX configuration and that includes the information indicating the second DRX configuration.

[0243] Aspect 22. The first network entity of Aspect 21, wherein the RRC signal indicates one or more DRX configuration parameters, and wherein each respective DRX configuration parameter of the one or more DRX configuration parameters is associated with a first value corresponding to the first DRX configuration and a second value corresponding to the second DRX configuration.

[0244] Aspect 23. The first network entity of any one of Aspects 1-22, wherein: to receive the information indicating the first DRX configuration, the at least one processor is configured to receive configuration information associated with the second network entity, wherein the configuration information includes the information indicating the first DRX configuration.

[0245] Aspect 24. The first network entity of Aspect 23, wherein the at least one processor is configured to replace a DRX on duration start offset parameter value included in the second DRX configuration with a respective on duration start offset parameter value included in the configuration information associated with the second network entity, or to replace a DRX cycle duration parameter value included in the second DRX configuration with a respective cycle duration parameter value included in the configuration information associated with the second network entity.

[0246] Aspect 25. The first network entity of any one of Aspects 23-24, wherein the configuration information associated with the second network entity includes one or more of a DRX configuration associated with the second network entity or a DTX configuration associated with the second network entity.

[0247] Aspect 26. The first network entity of any one of Aspects 1-25, wherein the first DRX configuration is associated with the DTX enable status of the second network entity and a channel type associated with the downlink information.

[0248] Aspect 27. The first network entity of aspect 26, wherein the channel type associated with the downlink information is a configured grant physical uplink shared channel (PUSCH), a semi-persistent scheduling physical downlink shared channel (PDSCH), a search space set (SSS), or a SSS group for physical downlink control channel (PDCCH) monitoring.

[0249] Aspect 28. The first network entity of any one of aspects 26-27, wherein the channel type associated with the downlink information is associated with a physical uplink control channel (PUCCH) resource, a scheduling request, a random access resource, or an active bandwidth part (BWP).

[0250] Aspect 29. The first network entity of any one of aspects 1-28, wherein a period associated with the DTX enabled state is the same as a period associated with a DTX disabled state of the second network entity, and wherein the period and a period of an extended reality (XR) transmission associated with an XR service of the first network entity are aligned.

[0251] Aspect 30. The first network entity of any one of aspects 1-29, wherein one or more of a DTX cycle period associated with the DTX enabled state of the second network entity or a DRX cycle period associated with a DRX enabled state is aligned with a non-integer period corresponding to an extended reality (XR) video generation rate of the first network entity.

[0252] Aspect 31. The first network entity of any one of aspects 1-30, wherein: a start time associated with the first DRX on duration is the same as or after a start time associated with the DTX on duration; and an end time associated with the first DRX on duration is the same as or before an end time associated with the DTX on duration.

[0253] Aspect 32. A first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to: transmit information indicating a first discontinuous reception (DRX) configuration for a second network entity, wherein the first DRX configuration indicates a first DRX on-duration for the second network entity; transmit information indicating a second DRX configuration for the second network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determine a discontinuous transmission (DTX) enabled state for the first network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the first network entity, and wherein the first DRX on-duration is within the DTX on-duration for the first network entity; and transmit downlink information to the second network entity during the first DRX on-duration.

[0254] Aspect 33. The first network entity of aspect 32, wherein: the first DRX configuration is associated with the DTX enabled state for the first network entity; and the second DRX configuration is associated with a DTX disabled state for the first network entity.

[0255] Aspect 34. The first network entity of any one of aspects 32 to 33, wherein the DTX enabled state is aligned with a DRX enabled state for the first network entity based on: a period of the DTX enabled state being a multiple of a period of the DRX enabled state for the first network entity, or a period of the DRX enabled state being a multiple of a period of the DTX enabled state for the first network entity; and at least a portion of the DTX on-duration corresponding to the DTX enabled state overlapping at least a portion of a DRX on-duration corresponding to the DRX enabled state.

[0256] Aspect 35. The first network entity of aspect 34, wherein: the period of the DTX enabled state is the same as the period of the DRX enabled state; and the DTX enabled state is aligned with the DRX enabled state based on a DTX on-duration start offset associated with the period of the DTX enabled state being the same as a DRX on-duration start offset associated with the period of the DRX enabled state.

[0257] Aspect 36. The first network entity of any one of aspects 32 to 35, wherein the at least one processor is configured to: transmit, to the second network entity, information indicating the DTX enabled state for the first network entity.

[0258] Aspect 37. The first network entity of any one of aspects 32 through 36, wherein the at least one processor is configured to indicate the DTX enable status of the first network entity to the second network entity based on transmitting or not transmitting a signal relative to a time period.

[0259] Aspect 38. The first network entity of aspect 37, wherein the at least one processor is configured to indicate the DTX enable status of the first network entity based on not transmitting the signal relative to the time period.

[0260] Aspect 39. The first network entity of any one of aspects 37 through 38, wherein the at least one processor is configured to indicate a DTX disable status of the first network entity based on transmitting the signal relative to the time period.

[0261] Aspect 40. The first network entity of any one of aspects 32 through 39, wherein: the first DRX configuration comprises a first plurality of values, wherein each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters; the second DRX configuration comprises a second plurality of values, wherein each value of the second plurality of values corresponds to a respective DRX configuration parameter of the plurality of DRX configuration parameters; and at least one value of the second plurality of values corresponds to a particular DRX configuration parameter and is different than at least one value of the first plurality of values that corresponds to the particular DRX configuration parameter.

[0262] Aspect 41. The first network entity of aspect 40, wherein the particular DRX configuration parameter comprises one or more of: a DRX on duration value, a DRX on duration start offset value, a DRX cycle duration value, a DRX on duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round trip time (RTT) timer value, or a UL RTT timer value.

[0263] Aspect 42. The first network entity of any one of aspects 32 through 41, wherein the first DRX on duration overlaps in time with at least a portion of a respective DRX on duration associated with each user equipment (UE) of a plurality of UEs, the second network entity included in the plurality of UEs.

[0264] Aspect 43. The first network entity of aspect 42, wherein the first DRX on duration and the respective DRX on duration associated with each UE of the plurality of UEs is within the DTX on duration.

[0265] Aspect 44. The first network entity of any of aspects 42 through 43, wherein the first DRX configuration indicates a first DRX on duration start offset associated with the second network entity, and wherein the first DRX on duration start offset is the same as a respective DRX on duration start offset associated with each UE of the plurality of UEs.

[0266] Aspect 45. The first network entity of aspect 44, wherein the first DRX on duration start offset is a time offset from a start of a DTX cycle associated with the DTX enabled state.

[0267] Aspect 46. The first network entity of any of aspects 42 through 45, wherein the first DRX configuration indicates a DRX cycle duration, and wherein the DRX cycle duration is the same as a DTX cycle duration associated with the DTX enabled state.

[0268] Aspect 47. The first network entity of any of aspects 32 through 46, wherein the second DRX configuration indicates a second DRX on duration of the second network entity and is associated with a DTX disabled state of the first network entity, and wherein the second DRX on duration does not overlap in time with a respective DRX on duration associated with each UE of a plurality of user equipment (UEs).

[0269] Aspect 48. The first network entity of aspect 47, wherein the at least one processor is further configured to transmit downlink information to the second network entity during the second DRX on duration.

[0270] Aspect 49. The first network entity of any of aspects 47 through 48, wherein the respective DRX on duration associated with each UE of the plurality of UEs and the second DRX on duration are associated with a same DRX cycle duration.

[0271] Aspect 50. The first network entity of any of aspects 47 through 48, wherein: the second DRX configuration indicates a second DRX on duration start offset associated with the second network entity, and wherein the second DRX on duration start offset is different than a respective DRX on duration start offset associated with each UE of the plurality of UEs.

[0272] Aspect 51. The first network entity of any of aspects 32 through 50, wherein: to transmit the information indicating the first DRX configuration, the at least one processor is configured to transmit, to the second network entity, a first radio resource control (RRC) signal that includes the information indicating the first DRX configuration; and to transmit the information indicating the second DRX configuration, the at least one processor is configured to transmit, to the second network entity, a second RRC signal that includes the information indicating the second DRX configuration.

[0273] Aspect 52. The first network entity of any of aspects 32 through 51, wherein, to transmit the information indicating the first DRX configuration and to transmit the information indicating the second DRX configuration, the at least one processor is configured to transmit, to the second network entity, a radio resource control (RRC) signal that includes the information indicating the first DRX configuration and that includes the information indicating the second DRX configuration.

[0274] Aspect 53. The first network entity of aspect 52, wherein the RRC signal indicates one or more DRX configuration parameters, and wherein each respective DRX configuration parameter of the one or more DRX configuration parameters is associated with a first value corresponding to the first DRX configuration and a second value corresponding to the second DRX configuration.

[0275] Aspect 54. The first network entity of any of aspects 32 through 53, wherein: to transmit the information indicating the first DRX configuration, the at least one processor is configured to transmit configuration information associated with the first network entity, wherein the configuration information includes the information indicating the first DRX configuration.

[0276] Aspect 55. The first network entity of aspect 54, wherein the at least one processor is configured to replace a DRX on duration start offset parameter value included in the second DRX configuration with a respective on duration start offset parameter value included in the configuration information associated with the first network entity or to replace a DRX cycle duration parameter value included in the second DRX configuration with a respective cycle duration parameter value included in the configuration information associated with the first network entity.

[0277] Aspect 56. The first network entity of any of aspects 54 through 55, wherein the configuration information associated with the first network entity includes one or more of a DRX configuration associated with the first network entity or a DTX configuration associated with the first network entity.

[0278] Aspect 57. The first network entity of any one of aspects 32 to 56, wherein the first DRX configuration is associated with the DTX enabled state of the first network entity and a channel type associated with the downlink information.

[0279] Aspect 58. The first network entity of aspect 57, wherein the channel type associated with the downlink information is a configured grant physical uplink shared channel (PUSCH), a semi-persistent scheduling physical downlink shared channel (PDSCH), a search space set (SSS), or a SSS group for physical downlink control channel (PDCCH) monitoring.

[0280] Aspect 59. The first network entity of any one of aspects 57 to 58, wherein the channel type associated with the downlink information is associated with a physical uplink control channel (PUCCH) resource, a scheduling request, a random access resource, or an active bandwidth part (BWP).

[0281] Aspect 60. The first network entity of any one of aspects 32 to 59, wherein a period associated with the DTX enabled state is the same as a period associated with a DTX disabled state of the first network entity, and wherein the period and a period of an extended reality (XR) transmission associated with an XR service of the second network entity are aligned.

[0282] Aspect 61. The first network entity of any one of aspects 32 to 60, wherein one or more of a DTX cycle period associated with the DTX enabled state of the first network entity or a DRX cycle period associated with a DRX enabled state is aligned with a non-integer period corresponding to an extended reality (XR) video generation rate of the second network entity.

[0283] Aspect 62. The first network entity of any one of aspects 32 to 61, wherein: a start time associated with the first DRX on-duration is the same as or after a start time associated with the DTX on-duration; and an end time associated with the first DRX on-duration is the same as or before an end time associated with the DTX on-duration.

[0284] Aspect 63. A method for wireless communication at a first network entity, the method comprising: receiving information indicating a first discontinuous reception (DRX) configuration for the first network entity, wherein the first DRX configuration indicates a first DRX on-duration of the first network entity; receiving information indicating a second DRX configuration for the first network entity, wherein one or more DRX configuration parameter values ​​of the second DRX configuration are different from one or more DRX configuration parameter values ​​of the first DRX configuration; determining a discontinuous transmission (DTX) enable state of the second network entity, wherein the DTX enable state corresponds to a DTX on-duration of the second network entity, and wherein the first DRX on-duration is within the DTX on-duration of the second network entity; and receiving downlink information from the second network entity during the first DRX on-duration.

[0285] Aspect 64. The method of aspect 63, wherein: the first DRX configuration is associated with the DTX enabled state of the second network entity; and the second DRX configuration is associated with the DTX disabled state of the second network entity.

[0286] Aspect 65. A method according to any one of Aspects 63 to 64, wherein the DTX enabled state is aligned with the DRX enabled state of the second network entity based on the following items: the period of the DTX enabled state is a multiple of the period of the DRX enabled state of the second network entity, or the period of the DRX enabled state is a multiple of the period of the DTX enabled state of the second network entity; and at least a portion of the DTX on duration corresponding to the DTX enabled state overlaps with at least a portion of the DRX on duration corresponding to the DRX enabled state.

[0287] Aspect 66. A method according to Aspect 65, wherein: the period of the DTX enabled state is the same as the period of the DRX enabled state; and based on the DTX on-duration start offset associated with the period of the DTX enabled state and the DRX on-duration start offset associated with the period of the DRX enabled state being the same, the DTX enabled state is aligned with the DRX enabled state.

[0288] Aspect 67. The method according to any one of aspects 63 to 66, wherein determining the DTX enablement status of the second network entity comprises: receiving information indicating the DTX enablement status of the second network entity from the second network entity.

[0289] Aspect 68. The method of any of aspects 63 through 67, wherein determining the DTX enablement status of the second network entity comprises determining the DTX enablement status of the second network entity based on receiving or not receiving a signal relative to a time period.

[0290] Aspect 69. The method of aspect 68, further comprising determining the DTX enablement status of the second network entity based on not receiving the signal relative to the time period.

[0291] Aspect 70. The method of any of aspects 68 through 69, further comprising determining a DTX disablement status of the second network entity based on receiving the signal relative to the time period.

[0292] Aspect 71. The method of any of aspects 63 through 70, wherein: the first DRX configuration comprises a first plurality of values, wherein each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters; the second DRX configuration comprises a second plurality of values, wherein each value of the second plurality of values corresponds to a respective DRX configuration parameter of the plurality of DRX configuration parameters; and at least one value of the second plurality of values corresponds to a particular DRX configuration parameter and is different than at least one value of the first plurality of values that corresponds to the particular DRX configuration parameter.

[0293] Aspect 72. The method of aspect 71, wherein the particular DRX configuration parameter comprises one or more of: a DRX on duration value, a DRX on duration start offset value, a DRX cycle duration value, a DRX on duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round trip time (RTT) timer value, or a UL RTT timer value.

[0294] Aspect 73. The method of any of aspects 63 through 72, wherein the first DRX on duration overlaps in time with at least a portion of a respective DRX on duration associated with each user equipment (UE) of a plurality of UEs, the first network entity included in the plurality of UEs.

[0295] Aspect 74. The method of aspect 73, wherein the first DRX on duration and the respective DRX on duration associated with each UE of the plurality of UEs are within the DTX on duration.

[0296] Aspect 75. The method of any of aspects 73-74, wherein the first DRX configuration indicates a first DRX on duration start offset associated with the first network entity, and wherein the first DRX on duration start offset is the same as a respective DRX on duration start offset associated with each UE of the plurality of UEs.

[0297] Aspect 76. The method of aspect 75, wherein the first DRX on duration start offset is a time offset from a start of a DTX cycle associated with the DTX enabled state.

[0298] Aspect 77. The method of any of aspects 73-76, wherein the first DRX configuration indicates a DRX cycle duration, and wherein the DRX cycle duration is the same as a DTX cycle duration associated with the DTX enabled state.

[0299] Aspect 78. The method of any of aspects 63-77, wherein the second DRX configuration indicates a second DRX on duration of the first network entity and is associated with a DTX disabled state of the second network entity, and wherein the second DRX on duration does not overlap in time with a respective DRX on duration associated with each UE of a plurality of user equipment (UEs).

[0300] Aspect 79. The method of aspect 78, further comprising: receiving downlink information from the second network entity during the second DRX on duration.

[0301] Aspect 80. The method of any of aspects 78-79, wherein the respective DRX on duration associated with each UE of the plurality of UEs and the second DRX on duration are associated with a same DRX cycle duration.

[0302] Aspect 81. The method of any of aspects 78-80, wherein: the second DRX configuration indicates a second DRX on duration start offset associated with the first network entity, and wherein the second DRX on duration start offset is different than a respective DRX on duration start offset associated with each UE of the plurality of UEs.

[0303] Aspect 82. The method of any of aspects 63 through 81, wherein: receiving the information indicating the first DRX configuration comprises receiving, from the second network entity, a first radio resource control (RRC) signal comprising the information indicating the first DRX configuration; and receiving the information indicating the second DRX configuration comprises receiving, from the second network entity, a second RRC signal comprising the information indicating the second DRX configuration.

[0304] Aspect 83. The method of any of aspects 63 through 82, wherein receiving the information indicating the first DRX configuration and receiving the information indicating the second DRX configuration comprises: receiving, from the second network entity, a radio resource control (RRC) signal comprising the information indicating the first DRX configuration and comprising the information indicating the second DRX configuration.

[0305] Aspect 84. The method of aspect 83, wherein the RRC signal indicates one or more DRX configuration parameters, and wherein each respective DRX configuration parameter of the one or more DRX configuration parameters is associated with a first value corresponding to the first DRX configuration and a second value corresponding to the second DRX configuration.

[0306] Aspect 85. The method of any of aspects 63 through 84, wherein receiving the information indicating the first DRX configuration comprises: receiving configuration information associated with the second network entity, wherein the configuration information comprises the information indicating the first DRX configuration.

[0307] Aspect 86. The method of aspect 85, further comprising: replacing a DRX on duration start offset parameter value included in the second DRX configuration with a respective on duration start offset parameter value included in the configuration information associated with the second network entity; or replacing a DRX cycle duration parameter value included in the second DRX configuration with a respective cycle duration parameter value included in the configuration information associated with the second network entity.

[0308] Aspect 87. The method of any of aspects 85 through 86, wherein the configuration information associated with the second network entity comprises one or more of a DRX configuration associated with the second network entity or a DTX configuration associated with the second network entity.

[0309] Aspect 88. The method of any of aspects 63 through 87, wherein the first DRX configuration is associated with the DTX enablement status of the second network entity and a channel type associated with the downlink information.

[0310] Aspect 89. The method of aspect 88, wherein the channel type associated with the downlink information is a configured grant physical uplink shared channel (PUSCH), a semi-persistent scheduling physical downlink shared channel (PDSCH), a search space set (SSS), or a SSS group for physical downlink control channel (PDCCH) monitoring.

[0311] Aspect 90. The method of any of aspects 88-89, wherein the channel type associated with the downlink information is associated with a physical uplink control channel (PUCCH) resource, a scheduling request, a random access resource, or an active bandwidth part (BWP).

[0312] Aspect 91. The method of any of aspects 63-90, wherein a period associated with the DTX enabled state is the same as a period associated with a DTX disabled state of the second network entity, and wherein the period is aligned with a period of an extended reality (XR) transmission associated with an XR service of the first network entity.

[0313] Aspect 92. The method of any of aspects 63-91, wherein one or more of a DTX cycle period associated with the DTX enabled state of the second network entity or a DRX cycle period associated with a DRX enabled state is aligned with a non-integer period corresponding to an extended reality (XR) video generation rate of the first network entity.

[0314] Aspect 93. The method of any of aspects 63-92, wherein: a start time associated with the first DRX on duration is the same as or after a start time associated with the DTX on duration; and an end time associated with the first DRX on duration is the same as or before an end time associated with the DTX on duration.

[0315] Aspect 94. A method for wireless communication at a first network entity, comprising: transmitting information indicating a first discontinuous reception (DRX) configuration for a second network entity, wherein the first DRX configuration indicates a first DRX on-duration for the second network entity; transmitting information indicating a second DRX configuration for the second network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determining a discontinuous transmission (DTX) enabled state for the first network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the first network entity, and wherein the first DRX on-duration is within the DTX on-duration for the first network entity; and transmitting downlink information to the second network entity during the first DRX on-duration.

[0316] Aspect 95. The method of aspect 94, wherein: the first DRX configuration is associated with the DTX enabled state for the first network entity; and the second DRX configuration is associated with a DTX disabled state for the first network entity.

[0317] Aspect 96. The method of any one of aspects 94-95, wherein the DTX enabled state is aligned with a DRX enabled state for the first network entity based on: a period of the DTX enabled state being a multiple of a period of the DRX enabled state for the first network entity, or a period of the DRX enabled state being a multiple of a period of the DTX enabled state for the first network entity; and at least a portion of the DTX on-duration corresponding to the DTX enabled state overlapping at least a portion of a DRX on-duration corresponding to the DRX enabled state.

[0318] Aspect 97. The method of aspect 96, wherein: the period of the DTX enabled state is the same as the period of the DRX enabled state; and the DTX enabled state is aligned with the DRX enabled state based on a DTX on-duration start offset associated with the period of the DTX enabled state being the same as a DRX on-duration start offset associated with the period of the DRX enabled state.

[0319] Aspect 98. The method of any one of aspects 94-97, wherein the at least one processor is configured to: transmit, to the second network entity, information indicating the DTX enabled state for the first network entity.

[0320] Aspect 99. The method of any of aspects 94 through 98, further comprising indicating the DTX enablement status of the first network entity to the second network entity based on transmitting or not transmitting a signal relative to a time period.

[0321] Aspect 100. The method of aspect 99, further comprising indicating the DTX enablement status of the first network entity based on not transmitting the signal relative to the time period.

[0322] Aspect 101. The method of any of aspects 99 through 100, further comprising indicating a DTX disablement status of the first network entity based on transmitting the signal relative to the time period.

[0323] Aspect 102. The method of any of aspects 94 through 101, wherein: the first DRX configuration comprises a first plurality of values, wherein each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters; the second DRX configuration comprises a second plurality of values, wherein each value of the second plurality of values corresponds to a respective DRX configuration parameter of the plurality of DRX configuration parameters; and at least one value of the second plurality of values corresponds to a particular DRX configuration parameter and is different than at least one value of the first plurality of values that corresponds to the particular DRX configuration parameter.

[0324] Aspect 103. The method of aspect 102, wherein the particular DRX configuration parameter comprises one or more of: a DRX on duration value, a DRX on duration start offset value, a DRX cycle duration value, a DRX on duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round trip time (RTT) timer value, or a UL RTT timer value.

[0325] Aspect 104. The method of any of aspects 94 through 103, wherein the first DRX on duration overlaps in time with at least a portion of a respective DRX on duration associated with each user equipment (UE) of a plurality of UEs, the second network entity included in the plurality of UEs.

[0326] Aspect 105. The method of aspect 104, wherein the first DRX on duration and the respective DRX on duration associated with each UE of the plurality of UEs are within the DTX on duration.

[0327] Aspect 106. The method of any of aspects 104 through 105, wherein the first DRX configuration indicates a first DRX on duration start offset associated with the second network entity, and wherein the first DRX on duration start offset is the same as a respective DRX on duration start offset associated with each UE of the plurality of UEs.

[0328] Aspect 107. The method of aspect 106, wherein the first DRX on duration start offset is a time offset from a start of a DTX cycle associated with the DTX enabled state.

[0329] Aspect 108. The method of any of aspects 104 through 107, wherein the first DRX configuration indicates a DRX cycle duration, and wherein the DRX cycle duration is the same as a DTX cycle duration associated with the DTX enabled state.

[0330] Aspect 109. The method of any of aspects 94 through 108, wherein the second DRX configuration indicates a second DRX on duration of the second network entity and is associated with a DTX disabled state of the first network entity, and wherein the second DRX on duration does not overlap in time with a respective DRX on duration associated with each UE of a plurality of user equipment (UEs).

[0331] Aspect 110. The method of aspect 109, further comprising: transmitting downlink information to the second network entity during the second DRX on duration.

[0332] Aspect 111. The method of any of aspects 109 through 110, wherein the respective DRX on duration associated with each UE of the plurality of UEs and the second DRX on duration are associated with a same DRX cycle duration.

[0333] Aspect 112. The method of aspect 109, wherein: the second DRX configuration indicates a second DRX on duration start offset associated with the second network entity, and wherein the second DRX on duration start offset is different than a respective DRX on duration start offset associated with each UE of the plurality of UEs.

[0334] Aspect 113. The method of aspect 94, wherein: transmitting the information indicating the first DRX configuration comprises transmitting, to the second network entity, a first radio resource control (RRC) signal comprising the information indicating the first DRX configuration; and transmitting the information indicating the second DRX configuration comprises transmitting, to the second network entity, a second RRC signal comprising the information indicating the second DRX configuration.

[0335] Aspect 114. The method of aspect 94, wherein transmitting the information indicating the first DRX configuration and transmitting the information indicating the second DRX configuration comprises: transmitting, to the second network entity, a radio resource control (RRC) signal comprising the information indicating the first DRX configuration and comprising the information indicating the second DRX configuration.

[0336] Aspect 115. The method of aspect 114, wherein the RRC signal indicates one or more DRX configuration parameters, and wherein each respective DRX configuration parameter of the one or more DRX configuration parameters is associated with a first value corresponding to the first DRX configuration and a second value corresponding to the second DRX configuration.

[0337] Aspect 116. The method of any of aspects 94 through 115, wherein transmitting the information indicating the first DRX configuration comprises: transmitting configuration information associated with the first network entity, wherein the configuration information comprises the information indicating the first DRX configuration.

[0338] Aspect 117. The method of aspect 116, further comprising: replacing a DRX on duration start offset parameter value included in the second DRX configuration with a respective on duration start offset parameter value included in the configuration information associated with the first network entity; or replacing a DRX cycle duration parameter value included in the second DRX configuration with a respective cycle duration parameter value included in the configuration information associated with the first network entity.

[0339] Aspect 118. The method of any of aspects 116 through 117, wherein the configuration information associated with the first network entity comprises one or more of a DRX configuration associated with the first network entity or a DTX configuration associated with the first network entity.

[0340] Aspect 119. The method of any of aspects 94 through 118, wherein the first DRX configuration is associated with the DTX enable status of the first network entity and a channel type associated with the downlink information.

[0341] Aspect 120. The method of aspect 119, wherein the channel type associated with the downlink information is a configured grant physical uplink shared channel (PUSCH), a semi-persistent scheduling physical downlink shared channel (PDSCH), a search space set (SSS), or a SSS group for physical downlink control channel (PDCCH) monitoring.

[0342] Aspect 121. The method of any of aspects 119-120, wherein the channel type associated with the downlink information is associated with a physical uplink control channel (PUCCH) resource, a scheduling request, a random access resource, or an active bandwidth part (BWP).

[0343] Aspect 122. The method of any of aspects 94-121, wherein a period associated with the DTX enabled state is the same as a period associated with a DTX disabled state of the first network entity, and wherein the period is aligned with a period of an extended reality (XR) transmission associated with an XR service of the second network entity.

[0344] Aspect 123. The method of any of aspects 94-122, wherein one or more of a DTX cycle period associated with the DTX enabled state of the first network entity or a DRX cycle period associated with a DRX enabled state is aligned with a non-integer period corresponding to an extended reality (XR) video generation rate of the second network entity.

[0345] Aspect 124. The method of any of aspects 94-123, wherein: a start time associated with the first DRX on duration is the same as or after a start time associated with the DTX on duration; and an end time associated with the first DRX on duration is the same as or before an end time associated with the DTX on duration.

[0346] Aspect 125. A non-transitory computer-readable medium having instructions thereon, the instructions, when executed by one or more processors, cause the one or more processors to perform operations in accordance with any of aspects 1-31.

[0347] Aspect 126. A non-transitory computer-readable medium having instructions thereon, the instructions, when executed by one or more processors, cause the one or more processors to perform operations in accordance with any of aspects 32-62.

[0348] Aspect 127. A non-transitory computer-readable medium having instructions thereon, the instructions, when executed by one or more processors, cause the one or more processors to perform operations in accordance with any of aspects 63 through 93.

[0349] Aspect 128. A non-transitory computer-readable medium having instructions thereon, the instructions, when executed by one or more processors, cause the one or more processors to perform operations in accordance with any of aspects 94 through 124.

[0350] Aspect 129. An apparatus for wireless communication, the apparatus comprising one or more means for performing the operations of any of aspects 1 through 31.

[0351] Aspect 130. An apparatus for wireless communication, the apparatus comprising one or more means for performing the operations of any of aspects 32 through 62.

[0352] Aspect 131. An apparatus for wireless communication, the apparatus comprising one or more means for performing the operations of any of aspects 63 through 93.

[0353] Aspect 132. An apparatus for wireless communication, the apparatus comprising one or more means for performing the operations of any of aspects 94 through 124.

Claims

1. A first network entity for wireless communication, the first network entity comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to: receive information indicating a first discontinuous reception (DRX) configuration for the first network entity, wherein the first DRX configuration indicates a first DRX on-duration for the first network entity; receive information indicating a second DRX configuration for the first network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determine a discontinuous transmission (DTX) enabled state of a second network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the second network entity, and wherein the first DRX on-duration is within the DTX on-duration for the second network entity; and receive downlink information from the second network entity during the first DRX on-duration.

2. The first network entity of claim 1, wherein: the first DRX configuration is associated with the DTX enabled state of the second network entity; and the second DRX configuration is associated with a DTX disabled state of the second network entity.

3. The first network entity of claim 1, wherein the DTX enabled state is aligned with a DRX enabled state of the second network entity based on: a period of the DTX enabled state being a multiple of a period of the DRX enabled state of the second network entity, or a period of the DRX enabled state being a multiple of a period of the DTX enabled state of the second network entity; and at least a portion of the DTX on-duration corresponding to the DTX enabled state overlapping at least a portion of a DRX on-duration corresponding to the DRX enabled state.

4. The first network entity of claim 3, wherein: the period of the DTX enabled state is the same as the period of the DRX enabled state; and the DTX enabled state is aligned with the DRX enabled state based on a DTX on-duration start offset associated with the period of the DTX enabled state being the same as a DRX on-duration start offset associated with the period of the DRX enabled state.

5. The first network entity of claim 1, wherein to determine the DTX enabled state of the second network entity, the at least one processor is configured to: receive information from the second network entity indicating the DTX enabled state of the second network entity.

6. The first network entity of claim 1, wherein to determine the DTX enabled state of the second network entity, the at least one processor is configured to: determine the DTX enabled state of the second network entity based on receiving or not receiving a signal relative to a time period. ​ 7. The first network entity of claim 6, wherein the at least one processor is configured to: determine the DTX enable status of the second network entity based on not receiving the signal with respect to the time period.

8. The first network entity of claim 6, wherein the at least one processor is configured to: determine a DTX disable status of the second network entity based on receiving the signal with respect to the time period.

9. The first network entity of claim 1, wherein: the first DRX configuration comprises a first plurality of values, wherein each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters; the second DRX configuration comprises a second plurality of values, wherein each value of the second plurality of values corresponds to a respective DRX configuration parameter of the plurality of DRX configuration parameters; and at least one value of the second plurality of values corresponds to a particular DRX configuration parameter and is different than at least one value of the first plurality of values that corresponds to the particular DRX configuration parameter.

10. The first network entity of claim 9, wherein the particular DRX configuration parameter comprises one or more of a DRX on duration value, a DRX on duration start offset value, a DRX cycle duration value, a DRX on duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round trip time (RTT) timer value, or a UL RTT timer value.

11. The first network entity of claim 1, wherein the first DRX on duration overlaps in time with at least a portion of a respective DRX on duration associated with each user equipment (UE) of a plurality of UEs, the first network entity included in the plurality of UEs.

12. The first network entity of claim 11, wherein the first DRX on duration and the respective DRX on duration associated with each UE of the plurality of UEs is within the DTX on duration.

13. The first network entity of claim 11, wherein the first DRX configuration indicates a first DRX on duration start offset associated with the first network entity, and wherein the first DRX on duration start offset is the same as a respective DRX on duration start offset associated with each UE of the plurality of UEs.

14. The first network entity of claim 13, wherein the first DRX on duration start offset is a time offset from a start of a DTX cycle associated with the DTX enable status.

15. The first network entity of claim 11, wherein the first DRX configuration indicates a DRX cycle duration, and wherein the DRX cycle duration is the same as a DTX cycle duration associated with the DTX enable status.

16. The first network entity of claim 1 , wherein the second DRX configuration indicates a second DRX on-duration of the first network entity and is associated with a DTX disabled state of the second network entity, and wherein the second DRX on-duration does not temporally overlap with a corresponding DRX on-duration associated with each of a plurality of user equipments (UEs).

17. The first network entity of claim 16, wherein the at least one processor is further configured to: Downlink information is received from the second network entity during the second DRX On-Duration.

18. The first network entity of claim 16, wherein the respective DRX On-Duration associated with each of the plurality of UEs and the second DRX On-Duration are associated with a same DRX cycle duration.

19. The first network entity according to claim 16, wherein: The second DRX configuration indicates a second DRX OnDuration start offset associated with the first network entity, and wherein the second DRX OnDuration start offset is different from a corresponding DRX OnDuration start offset associated with each of the plurality of UEs.

20. The first network entity according to claim 1, wherein: To receive the information indicative of the first DRX configuration, the at least one processor is configured to receive, from the second network entity, a first radio resource control (RRC) signal including the information indicative of the first DRX configuration; and To receive the information indicating the second DRX configuration, the at least one processor is configured to receive, from the second network entity, a second RRC signal including the information indicating the second DRX configuration.

21. The first network entity of claim 1 , wherein to receive the information indicating the first DRX configuration and to receive the information indicating the second DRX configuration, the at least one processor is configured to: A radio resource control (RRC) signal is received from the second network entity, the radio resource control (RRC) signal including the information indicating the first DRX configuration and including the information indicating the second DRX configuration.

22. The first network entity of claim 21 , wherein the RRC signal indicates one or more DRX configuration parameters, and wherein each respective DRX configuration parameter of the one or more DRX configuration parameters is associated with a first value corresponding to the first DRX configuration and a second value corresponding to the second DRX configuration.

23. The first network entity of claim 1 , wherein to receive the information indicating the first DRX configuration, the at least one processor is configured to: Configuration information associated with the second network entity is received, wherein the configuration information includes the information indicating the first DRX configuration.

24. The first network entity of claim 23, wherein the at least one processor is configured to: replace a DRX on duration start offset parameter value included in the second DRX configuration with a corresponding on duration start offset parameter value included in the configuration information associated with the second network entity; or replace a DRX cycle duration parameter value included in the second DRX configuration with a corresponding cycle duration parameter value included in the configuration information associated with the second network entity.

25. The first network entity of claim 23, wherein the configuration information associated with the second network entity comprises one or more of a DRX configuration associated with the second network entity or a DTX configuration associated with the second network entity.

26. The first network entity of claim 1, wherein the first DRX configuration is associated with the DTX enable status of the second network entity and a channel type associated with the downlink information.

27. The first network entity of claim 26, wherein the channel type associated with the downlink information is a configured grant physical uplink shared channel (PUSCH), a semi-persistent scheduling physical downlink shared channel (PDSCH), a search space set (SSS), or an SSS group for physical downlink control channel (PDCCH) monitoring.

28. The first network entity of claim 26, wherein the channel type associated with the downlink information is associated with a physical uplink control channel (PUCCH) resource, a scheduling request, a random access resource, or an active bandwidth part (BWP).

29. The first network entity of claim 1, wherein a period associated with the DTX enable status is the same as a period associated with a DTX disable status of the second network entity, and wherein the period and a period of an extended reality (XR) transmission associated with an XR service of the first network entity are aligned.

30. The first network entity of claim 1, wherein one or more of a DTX cycle period associated with the DTX enable status of the second network entity or a DRX cycle period associated with a DRX enable status is aligned with a non-integer period corresponding to an extended reality (XR) video generation rate of the first network entity.

31. The first network entity of claim 1, wherein: a start time associated with the first DRX on duration is the same as or after a start time associated with the DTX on duration; and an end time associated with the first DRX on duration is the same as or before an end time associated with the DTX on duration.

32. A first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to: ​ transmitting information indicating a first discontinuous reception (DRX) configuration for a second network entity, wherein the first DRX configuration indicates a first DRX on-duration for the second network entity; transmitting information indicating a second DRX configuration for the second network entity, wherein one or more DRX configuration parameter values of the second DRX configuration are different from one or more DRX configuration parameter values of the first DRX configuration; determining a discontinuous transmission (DTX) enabled state for the first network entity, wherein the DTX enabled state corresponds to a DTX on-duration for the first network entity, and wherein the first DRX on-duration is within the DTX on-duration for the first network entity; and transmitting downlink information to the second network entity during the first DRX on-duration.

33. The first network entity of claim 32, wherein: the first DRX configuration is associated with the DTX enabled state for the first network entity; and the second DRX configuration is associated with a DTX disabled state for the first network entity.

34. The first network entity of claim 32, wherein the DTX enabled state is aligned with a DRX enabled state for the first network entity based on: a period of the DTX enabled state being a multiple of a period of the DRX enabled state for the first network entity, or a period of the DRX enabled state being a multiple of a period of the DTX enabled state for the first network entity; and at least a portion of the DTX on-duration corresponding to the DTX enabled state overlapping at least a portion of a DRX on-duration corresponding to the DRX enabled state.

35. The first network entity of claim 34, wherein: the period of the DTX enabled state is the same as the period of the DRX enabled state; and the DTX enabled state is aligned with the DRX enabled state based on a DTX on-duration start offset associated with the period of the DTX enabled state being the same as a DRX on-duration start offset associated with the period of the DRX enabled state.

36. The first network entity of claim 32, wherein the at least one processor is configured to: transmit, to the second network entity, information indicating the DTX enabled state for the first network entity.

37. The first network entity of claim 32, wherein the at least one processor is configured to: indicate, to the second network entity, the DTX enabled state for the first network entity based on transmitting or not transmitting a signal relative to a time period.

38. The first network entity of claim 37, wherein the at least one processor is configured to: indicate the DTX enabled state for the first network entity based on not transmitting the signal relative to the time period.

39. The first network entity of claim 37, wherein the at least one processor is configured to: ​ to indicate a DTX disable state of the first network entity based on transmitting the signal relative to the time period.

40. The first network entity of claim 32, wherein: the first DRX configuration comprises a first plurality of values, wherein each value of the first plurality of values corresponds to a respective DRX configuration parameter of a plurality of DRX configuration parameters; the second DRX configuration comprises a second plurality of values, wherein each value of the second plurality of values corresponds to a respective DRX configuration parameter of the plurality of DRX configuration parameters; and at least one value of the second plurality of values corresponds to a particular DRX configuration parameter and is different than at least one value of the first plurality of values that corresponds to the particular DRX configuration parameter.

41. The first network entity of claim 40, wherein the particular DRX configuration parameter comprises one or more of a DRX on duration value, a DRX on duration start offset value, a DRX cycle duration value, a DRX on duration timer value, a DRX inactivity timer value, a downlink (DL) retransmission timer value, an uplink (UL) retransmission timer value, a DL round trip time (RTT) timer value, or a UL RTT timer value.

Images