MESSAGE FOR NETWORK ENTITY DISCONTINUOUS RECEPTION OR DISCONTINUOUS TRANSMISSION

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a first network entity may transmit a first message to a neighboring second network entity, where the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity. The first network entity may start at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing. The second network entity may adjust communication scheduling or a measurement configuration. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for messaging for network entity discontinuous reception or discontinuous transmission.

BACKGROUND

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by an apparatus of a first network entity. The method may include transmitting a first message to a second network entity, where the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity. The method may include starting at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

Some aspects described herein relate to a method of wireless communication performed by an apparatus of a second network entity. The method may include receiving, from a first network entity, a first message that indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The method may include adjusting one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

Some aspects described herein relate to an apparatus of a first network entity for wireless communication. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to cause the first network entity to transmit a first message to a second network entity, where the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The one or more processors may be individually or collectively configured to cause the first network entity to start at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

Some aspects described herein relate to an apparatus of a second network entity for wireless communication. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be individually or collectively configured to cause the second network entity to receive, from a first network entity, a first message that indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The one or more processors may be individually or collectively configured to cause the second network entity to adjust one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a first network entity. The set of instructions, when executed by one or more processors of the first network entity, may cause the first network entity to transmit a first message to a second network entity, where the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The set of instructions, when executed by one or more processors of the first network entity, may cause the first network entity to start at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a second network entity. The set of instructions, when executed by one or more processors of the second network entity, may cause the second network entity to receive, from a first network entity, a first message that indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The set of instructions, when executed by one or more processors of the second network entity, may cause the second network entity to adjust one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting a first message to another apparatus, where the first message indicates one or more of a DRX timing of the apparatus or a DTX timing of the apparatus. The apparatus may include means for starting at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from another apparatus, a first message that indicates one or more of a DRX timing of the other apparatus or a DTX timing of the other apparatus. The apparatus may include means for adjusting one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

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

DETAILED DESCRIPTION

FIG.1is a diagram illustrating an example of a wireless network100, in accordance with the present disclosure. The wireless network100may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network100may include a user equipment (UE)120or multiple UEs120(shown as a UE120a, a UE120b, a UE120c, a UE120d, and a UE120e). The wireless network100may also include one or more network entities, such as base stations110(shown as a BS110a, a BS110b, a BS110c, and a BS110d), and/or other network entities. A base station110is a network entity that communicates with UEs120. A base station110(sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Entity B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and/or a transmission reception point (TRP). Each base station110may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term “cell” can refer to a coverage area of a base station110and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.

The wireless network100may include one or more relay stations. A relay station is a network entity that can receive a transmission of data from an upstream station (e.g., a network entity or a UE120) and send a transmission of the data to a downstream station (e.g., a UE120or a network entity). A relay station may be a UE120that can relay transmissions for other UEs120. In the example shown inFIG.1, the BS110d(e.g., a relay base station) may communicate with the BS110a(e.g., a macro base station) and the UE120din order to facilitate communication between the BS110aand the UE120d. A base station110that relays communications may be referred to as a relay station, a relay base station, a relay, or the like.

A network controller130may couple to or communicate with a set of network entities and may provide coordination and control for these network entities. The network controller130may communicate with the base stations110via a backhaul communication link. The network entities may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.

In some aspects, a first network entity (e.g., base station110) may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit a first message to a second network entity, where the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity. The communication manager150may start at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

In some aspects, a second network entity (e.g., base station110) may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may receive, from a first network entity, a first message that indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The communication manager150may adjust one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

The network controller130may include a communication unit294, a controller/processor290, and a memory292. The network controller130may include, for example, one or more devices in a core network. The network controller130may communicate with the network entity via the communication unit294.

A controller/processor of a network entity (e.g., the controller/processor240of the base station110), the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform one or more techniques associated with messaging for network entity DRX or DTX, as described in more detail elsewhere herein. For example, the controller/processor240of the base station110, the controller/processor280of the UE120, and/or any other component(s) ofFIG.2may perform or direct operations of, for example, process1000ofFIG.10, process1100ofFIG.11, and/or other processes as described herein. The memory242and the memory282may store data and program codes for the network entity and the UE120, respectively. In some examples, the memory242and/or the memory282may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the network entity and/or the UE120, may cause the one or more processors, the UE120, and/or the network entity to perform or direct operations of, for example, process1000ofFIG.10, process1100ofFIG.11, and/or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a first network entity (e.g., base station110) includes means for transmitting a first message to a second network entity, where the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity; and/or means for starting at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing. In some aspects, the means for the first network entity to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

In some aspects, a second network entity (e.g., base station110) includes means for receiving, from a first network entity, a first message that indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity; and/or means for adjusting one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

FIG.3is a diagram illustrating an example of a disaggregated base station300, in accordance with the present disclosure.

The disaggregated base station300architecture may include one or more CUs310that can communicate directly with a core network320via a backhaul link, or indirectly with the core network320through one or more disaggregated base station units (such as a Near-RT RIC325via an E2 link, or a Non-RT RIC315associated with a Service Management and Orchestration (SMO) Framework305, or both). A CU310may communicate with one or more DUs330via respective midhaul links, such as an F1 interface. The DUs330may communicate with one or more RUs340via respective fronthaul links. The fronthaul link, the midhaul link, and the backhaul link may be generally referred to as “communication links.” The RUs340may communicate with respective UEs120via one or more RF access links. In some aspects, the UE120may be simultaneously served by multiple RUs340. The DUs330and the RUs340may also be referred to as “O-RAN DUs (O-DUs”) and “O-RAN RUs (O-RUs)”, respectively. A network entity may include a CU, a DU, an RU, or any combination of CUs, DUs, and RUs. A network entity may include a disaggregated base station or one or more components of the disaggregated base station, such as a CU, a DU, an RU, or any combination of CUs, DUs, and RUs. A network entity may also include one or more of a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface for or serve a UE, mobile station, sensor/actuator, or other wireless device.

Lower-layer functionality can be implemented by one or more RUs340. In some deployments, an RU340, controlled by a DU330, may correspond to a logical node that hosts 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, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s)340can be implemented to handle over the air (OTA) communication with one or more UEs120. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s)340can be controlled by the corresponding DU330. In some scenarios, this configuration can enable the DU(s)330and the CU310to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

FIG.4is a diagram illustrating an example400of downlink semi-persistent scheduling (SPS) communication and an example410of uplink configured grant (CG) communication, in accordance with the present disclosure. SPS communications may include periodic downlink communications that are configured for a UE, such that a network entity does not need to transmit (e.g., directly or via one or more network entities) separate downlink control information (DCI) to schedule each downlink communication, thereby conserving signaling overhead. CG communications may include periodic uplink communications that are configured for a UE, such that the network entity does not need to transmit (e.g., directly or via one or more network entities) separate DCI to schedule each uplink communication, thereby conserving signaling overhead.

As shown in example400, a UE may be configured with an SPS configuration for SPS communications. For example, the UE may receive the SPS configuration via an RRC message transmitted by a network entity (e.g., directly to the UE or via one or more network entities). The SPS configuration may indicate a resource allocation associated with SPS downlink communications (e.g., in a time domain, frequency domain, spatial domain, and/or code domain) and a periodicity at which the resource allocation is repeated, resulting in periodically reoccurring scheduled SPS occasions405for the UE. The SPS configuration may also configure hybrid automatic repeat request (HARQ)-acknowledgement (ACK) (HARQ-ACK) feedback resources for the UE to transmit HARQ-ACK feedback for SPS physical downlink shared channel (PDSCH) communications received in the SPS occasions405.

The network entity may transmit SPS activation DCI to the UE (e.g., directly or via one or more network entities) to activate the SPS configuration for the UE. The network entity may indicate, in the SPS activation DCI, communication parameters, such as an MCS, a resource block (RB) allocation, and/or antenna ports, for the SPS PDSCH communications to be transmitted in the scheduled SPS occasions405. The UE may begin monitoring the SPS occasions405based at least in part on receiving the SPS activation DCI. The UE may refrain from monitoring configured SPS occasions405prior to receiving the SPS activation DCI. The network entity may transmit SPS reactivation DCI to the UE (e.g., directly or via one or more network entities) to change the communication parameters for the SPS PDSCH communications.

In some cases, such as when there is no downlink traffic to transmit to the UE, the network entity may transmit SPS cancellation DCI to the UE (e.g., directly or via one or more network entities) to temporarily cancel or deactivate one or more subsequent SPS occasions405for the UE. The SPS cancellation DCI may deactivate only a subsequent one SPS occasion405or a subsequent N SPS occasions405(where N is an integer). SPS occasions405after the one or more (e.g., N) SPS occasions405subsequent to the SPS cancellation DCI may remain activated. Based at least in part on receiving the SPS cancellation DCI, the UE may refrain from monitoring the one or more (e.g., N) SPS occasions405subsequent to receiving the SPS cancellation DCI. The network entity may transmit SPS release DCI to the UE (e.g., directly or via one or more network entities) to deactivate the SPS configuration for the UE. The UE may stop monitoring the scheduled SPS occasions405based at least in part on receiving the SPS release DCI.

As shown in example410, a UE may be configured with a CG configuration for CG communications. For example, the UE may receive the CG configuration via an RRC message transmitted by a network entity (e.g., directly to the UE or via one or more network entities). The CG configuration may indicate a resource allocation associated with CG uplink communications (e.g., in a time domain, frequency domain, spatial domain, and/or code domain) and a periodicity at which the resource allocation is repeated, resulting in periodically reoccurring scheduled CG occasions415for the UE. In some examples, the CG configuration may identify a resource pool or multiple resource pools that are available to the UE for an uplink transmission. The CG configuration may configure contention-free CG communications (e.g., where resources are dedicated for the UE to transmit uplink communications) or contention-based CG communications (e.g., where the UE contends for access to a channel in the configured resource allocation, such as by using a channel access procedure or a channel sensing procedure).

The network entity may transmit CG activation DCI to the UE (e.g., directly or via one or more network entities) to activate the CG configuration for the UE. The network entity may indicate, in the CG activation DCI, communication parameters, such as an MCS, an RB allocation, and/or antenna ports, for the CG physical uplink shared channel (PUSCH) communications to be transmitted in the scheduled CG occasions415. The UE may begin transmitting in the CG occasions415based at least in part on receiving the CG activation DCI.

The network entity may transmit CG reactivation DCI to the UE (e.g., directly or via one or more network entities) to change the communication parameters for the CG PUSCH communications. Based at least in part on receiving the CG reactivation DCI, the UE may begin transmitting in the scheduled CG occasions415using the communication parameters indicated in the CG reactivation DCI. In some cases, such as when the network entity is expected to override a scheduled CG communication for a higher priority communication, the network entity may transmit CG cancellation DCI to the UE (e.g., directly or via one or more network entities) to temporarily cancel or deactivate one or more subsequent CG occasions415for the UE. The network entity may transmit CG release DCI to the UE (e.g., directly or via one or more network entities) to deactivate the CG configuration for the UE. The UE may stop transmitting in the scheduled CG occasions415based at least in part on receiving the CG release DCI.

FIG.5is a diagram illustrating an example500of using a transmit inactivity period, in accordance with the present disclosure. Example500shows a network entity510(e.g., base station110) and a UE520(e.g., UE120) that may communicate with each other via a wireless network (e.g., wireless network100).

Energy costs make up a large percentage of the operating costs for a network. Accordingly, networks are being designed to be more energy efficient and environmentally responsible. These designs may include the use of a sleep state by the network entity510, where the network entity510powers down radio components or other components (partially or fully) at times to reduce energy consumption.

In some aspects, the network entity510may indicate a transmit inactivity period that allows the network entity510and/or the UE520more opportunities than current network configurations to enter a sleep state and thus consume less energy. The network entity510may indicate this transmit inactivity period to UEs. As a result, the network entity510and UEs520served by the network entity510may have more opportunities to sleep and to reduce power consumption.

In some implementations, the transmit inactivity period may be indicated as a pattern (e.g., a pattern of inactive BS TX Inactive states relative to active states), and the pattern may be a dynamic pattern or a periodic pattern. The network entity510may indicate the dynamic pattern via an RRC message and/or Layer 1 (L1) signaling (e.g., DCI, a MAC control element (MAC CE)). For example, the network entity510may use RRC signaling to configure the UE520with the option of transmitting group common DCI in the cell to indicate the “BS TX Inactive” state. The group common DCI may trigger the start and duration of the “BS TX Inactive” state. UEs may then pause monitoring for physical downlink control channel (PDCCH) communications and pause measuring periodic or semi-persistent channel state information reference signals (CSI-RS s) (if configured) during the “BS TX Inactive” state (or mode). The time duration during which the network entity510is in the BS TX Inactive state may be referred to as a network “transmit inactivity period.” The transmit inactivity period may be a period between active states or a period when the network entity510is powered down below a threshold power level. Example500shows an example transmit inactivity period522.

In some aspects, the network entity510may define, trigger, and/or configure one or more transmit inactivity periods for the BS TX Inactive state without affecting downlink traffic performance. However, before initiating (and indicating) a transmit inactivity period, the network entity510may check whether one or more conditions are satisfied. If the conditions are satisfied, the network entity510may generate an indication of a transmit inactivity period, as shown by reference number525. For example, the network entity510may generate the indication if a condition is satisfied where there is no downlink traffic with a latency requirement that is less than the period (time duration) of the transmit inactivity period (in the cell or in neighbor cells) and there is no periodic downlink traffic (e.g., SPS traffic) with a period that is shorter than the period of the transmit inactivity period. In other words, the network entity510may check that there is no low-latency downlink traffic to be transmitted. If there is such downlink traffic, the network entity may not initiate or indicate a transmit inactivity period.

While the network entity510may check for downlink traffic, the network entity may also check for uplink traffic because of the downlink traffic that is associated with scheduling the uplink traffic. For example, the network entity510may generate the indication (and initiate the BS TX Inactive state) if a condition is satisfied where there is no uplink traffic with a latency requirement that is less than the period of the transmit inactivity period, no uplink traffic is dynamically scheduled (via DCI), and retransmissions are allowed (via DCI) (in the current cell or in neighbor cells). The network entity510may generate the indication if a condition is satisfied where there is no periodic uplink traffic (e.g., CG) with a period that is shorter than the period of the transmit inactivity period and retransmissions are configured. If there is such uplink traffic, the network entity may not initiate or indicate a transmit inactivity period. Note that the network entity510may ensure that a synchronization signal block (SSB) is not skipped if certain types of UEs are present (e.g., UEs that use features specified by 3GPP Release 17) and that radio access channel (RACH) occasions (ROs) are not skipped. The network entity510may be aware of the above conditions by using Release 17 signaling procedures (e.g., RRC signaling, DCI, a MAC CE).

If the above conditions for downlink traffic and uplink traffic are satisfied, the network entity510may generate the indication of a transmit inactivity period. During the transmit inactivity period, the network entity510may also adjust the transmit power of the network entity510. This may include, for example, reducing power of the network entity510for transmitting during the transmit inactivity period. The reduction of the power for transmitting may be part of entering an inactive state or a sleep state. By contrast, an active state or awake state may include a state of processing (e.g., decoding and/or demodulating) downlink signals, uplink signals, and/or channels. The amount of power that the network entity510consumes during an awake state may scale (increase or decrease) based at least in part on a quantity of component carriers (CCs), resource utilization, a quantity of antenna ports, a quantity of spatial layers, and/or a quantity of antenna elements.

Example500also shows how the network entity510may ramp power down from an active state to a sleep state and ramp power back up to an active state. As the time between active states increases, more components can be turned off (power withdrawn) to conserve more power, including a radio (radio components) that is used for transmission and/or reception. For example, the network entity510may switch off the radio frequency (RF) part and/or a broadband part of a transmit chain, such that the network entity510will not transmit any communications. Switching between a transmit (downlink) active state (transmitting) and a transmit inactive state (not transmitting) may be an operation of a DTX mode, also referred to as “BS in DTX mode.” The transmit active state of the network entity510may be referred to as a “BS transmit active” state, and the inactive transmit state of the network entity510may be referred to as a “BS TX inactive” state. During the inactive transmit state, there are no downlink transmissions and the network entity510can enter a sleep state. During the active transmit state, downlink transmissions are possible, and the network entity510cannot enter the sleep state.

The network entity510may reduce power by varying amounts. For example, a sleep state may include varying levels of sleep, such as a micro sleep, a light sleep, or a deep sleep. A micro sleep may cause the network entity510to use a reduced amount of power for the radio as compared to the active state. This reduction in power may be much less than the reduction in power for a deep sleep (e.g., a deep sleep may have a reduction in power that is 15 times that of a micro sleep). However, a micro sleep may have very little transition time (e.g., less than 1 millisecond (ms)) and may use little transition energy. A light sleep may be a sleep level between a micro sleep and a deep sleep, with a power reduction that is, for example, half that of a deep sleep. A light sleep may have a slower transition time (e.g., 6 ms) than a micro sleep, but may still be quicker than a deep sleep. A light sleep may cause the network entity510to use additional transition energy (relative power vs. ms) that can be about 20 times that of a micro sleep. A deep sleep may have the longest sleep period and/or the greatest energy reduction. The deep sleep may also have the longest transition time (e.g., 20 ms) and cause the network entity510to use the greatest amount of energy for transition (e.g., about 100 times that of the micro sleep).

As shown by reference number530, the network entity510may transmit the indication. The indication may specify a periodic BS DTX pattern, with “BS Tx Active” and “BS Tx Inactive” durations, or a dynamic BS DTX pattern, in which “BS Tx Inactive” periods are triggered dynamically by the network entity510.

As shown by reference number535, the network entity510may adjust a power (e.g., decrease power, set a new power) for transmitting based at least in part on the indication. This may include adjusting the power to be at a reduced level during the transmit inactivity period. For example, as shown by reference number540, the UE520may adjust a power for receiving during the transmit inactivity period. The UE520may use the indication of the transmit inactivity period to reduce power to a receiving radio (e.g., enter a sleep state), or perform other operations that do not involve the network entity510, during the transmit inactivity period of the network entity510. During the transmit inactivity period, the UE520may pause (refrain from) actions such as PDCCH monitoring (shown by reference number545) and/or CSI-RS measuring (shown by reference number550). This is because during the transmit inactivity period, the network entity510may not transmit PDCCH communications, periodic CSI-RSs, and semi-persistent CSI-RSs. In this way, the network entity510may reduce power consumption. The UE520may also reduce power consumption and conserve battery power.

If the UE520exits the transmit inactivity period, the UE520may remain in an active state (e.g., awake) for the duration of an inactivity timer (e.g., which may extend the active time). The UE120may start the inactivity timer at a time at which the PDCCH communication is received (e.g., in a transmission time interval in which the PDCCH communication is received, such as a slot or a subframe). The UE520may remain in the active state until the inactivity timer expires, at which time the UE520may enter the sleep state (e.g., for the inactive transmit time). During the duration of the inactivity timer, the UE520may continue to monitor for PDCCH communications, may obtain a downlink data communication (e.g., on a downlink data channel, such as a PDSCH) scheduled by the PDCCH communication, and/or may prepare and/or transmit an uplink communication (e.g., on a PUSCH) scheduled by the PDCCH communication. The UE520may restart the inactivity timer after each detection of a PDCCH communication for the UE520for an initial transmission (e.g., but not for a retransmission).

In some aspects, the network entity510may utilize an inactive receive time or a “BS in DRX mode,” where DRX is discontinuous reception. The receive inactive state of the network entity510may be referred to as a “BS Rx Inactive” state or a receive inactivity period. In the receive inactivity period, the network entity510may cause radio receiver components or other components to enter a sleep state (e.g., micro sleep, light sleep, deep sleep).

FIG.6is a diagram illustrating examples600and602of transmit inactivity periods, in accordance with the present disclosure.

Example600shows a periodic DTX pattern of inactive transmit states (BS TX Inactive), each inactive transmit state having a transmit inactivity period. The network entity510may transmit the indication of the transmit inactivity period using, for example, RRC signaling. This may include via system information (SI) or via dedicated RRC signaling.

Example602shows dynamically triggered transmit inactivity states, where a triggering DCI indicates a timing of one or more transmit inactivity states. This may include a combination of RRC signaling and L1 signaling. The RRC level configuration may configure the option of having transmit inactivity periods and a list of N transmit inactivity periods with associated parameters (e.g., starting slot offset, duration), as part of a DTX pattern. The RRC signaling may include information about the periodic DTX pattern or DTX configurations in an information element (IE) in a system information block (SIB). The DCI may trigger one of the N RRC configured transmit inactivity periods. In case of signaling via an SIB, paging to UEs is expected and an update of a DTX pattern is possible only after a paging cycle. The minimum value of a paging cycle may be 32 radio frames.

For both the periodic DTX pattern and the dynamic DTX pattern, the start of a transmit inactivity period implies that UEs do not monitor for PDCCH communications and do not perform CSI-RS measurements (of all types). In some aspects, the set or list of configured transmit inactivity periods may be reconfigured. In some aspects, the network entity510may switch from a periodic DTX pattern to a dynamic DTX pattern. DRX may follow similar patterns.

As indicated above,FIG.6provides some examples. Other examples may differ from what is described with regard toFIG.6.

FIG.7is a diagram illustrating examples700and702of DCI formats, in accordance with the present disclosure.

Example700shows a DCI format 2_0 for signaling a transmit inactivity period. The DCI format may include a DCI identifier (ID) and slot format indicators (SFIs), if configured. The DCI may further include a BS TX Inactive trigger. The BS TX Inactive trigger may indicate one of multiple preconfigured DTX patterns that may include a starting slot offset (e.g., a starting slot or sub-slot from a current slot) and/or a duration (e.g., quantity of slots or sub-slots).

Example702shows a DCI format 2_0 that may be scrambled with an SFI radio network temporary identifier (RNTI). This may include up to 128 bits. The DCI may include information for SFIs, RBs, channel occupancy time (COT), and search space set groups, if configured. The DCI may further include a BS TX Inactive trigger. The BS TX Inactive trigger may indicate a starting slot offset and/or a duration. By triggering transmit inactivity states, the network entity510may increase the opportunities to enter the sleep state and reduce power consumption.

FIG.8is a diagram illustrating an example800of a network entity that may enter a transmit inactivity state, in accordance with the present disclosure. A first network entity810(e.g., base station110) and a second network entity815(e.g., base station110) may transmit multiple beams to multiple UEs. Each beam may be associated with a transmission configuration indicator (TCI) state. The network entity810may determine to enter a transmit inactivity state during two downlink slots of a configured slot pattern. Network entity815may be scheduled to receive uplink communications during these slots and other slots. The UEs served by network entity815may be scheduled to transmit with a higher transmit power during these slots in anticipation of interference from communications involving network entity810. However, network entity810is entering a DTX mode and a DRX mode during these slots. Network entity815is not aware of the upcoming DTX mode and DRX mode of network entity810. Consequently, the UEs communicating with network entity815may consume more energy than necessary when transmitting with a higher transmit power when no other communications with network entity810are scheduled. Furthermore, communications involving network entity810may interfere with communications involving network entity815in other slots. Such interference may degrade communications and waste processing resources and signaling resources. Network entity810may transmit a deactivation message when deactivating but the deactivation message may be too infrequent for network entity815to effectively conserve energy. The Xn message payload may also be large and frequent exchanges may consume a significant amount of signaling resources if the deactivation message is transmitted for each switch to a transmit inactivity state.

FIG.9is a diagram illustrating an example900of a message indicating a DRX timing or a DTX timing, in accordance with the present disclosure. Example900shows a network entity910(e.g., base station110) and a UE920(e.g., UE120) that may communicate with each other via a wireless network (e.g., wireless network100). Network entity910may be a serving cell. Network entity910may also communicate with network entity930over an Xn application protocol (XnAP) interface. Network entity930may be a neighboring network entity to network entity910. For example, some UEs served by network entity910may also be served by or interfere with UEs served by network entity930.

According to various aspects described herein, network entity910may transmit a first message to network entity930, as shown by reference number935. The first message may indicate a DRX timing of a DRX mode or a DTX timing of a DTX mode of network entity910. The DRX timing may indicate a pattern (e.g., periodicity) for a DRX mode, such as when the network entity930is in a receive inactivity state for a receive inactivity period of the DRX mode and when the network entity930is in a receive activity state (on duration) for a receive activity period of a DRX mode. The pattern or periodicity may include an interval of activity periods between inactivity periods, or a length of a cycle. The DTX timing may indicate a pattern (e.g., periodicity) for a DRX mode, such as when the network entity930is in a transmit inactivity state (on duration) for a transmit inactivity period of a DTX mode and when the network entity930is in a transmit activity state for a transmit activity period of the DTX mode. The first message may be a modification of an existing information element (IE) for served cells that is transmitted by network entity910or a message specific to indicating a DRX timing or a DTX timing. The first message may indicate a semi-persistent pattern for DTX, a dynamic pattern for DTX, a semi-persistent pattern for DRX, and/or a dynamic pattern for DRX. Semi-persistent may include semi-static or periodic. Network entity910may transmit the first message via RRC or L1 signaling.

In some aspects, the DRX timing may include parameters, such as a starting slot for the DRX mode and an ending slot for the DRX mode. The DTX timing may include parameters, such as a starting slot for a DTX mode and an ending slot for the DTX mode. The parameters may include a duration (e.g., quantity of slots, milliseconds (ms)) for the DRX mode or the DTX mode. The duration may indicate the ending slot. That is, given a starting slot and a duration, the ending slot may be determined (implicitly indicated). Parameters may also include a starting slot offset of a cycle.

The pattern for DRX and/or the pattern for DTX may be periodic or follow a specified frequency or timing. Alternatively, the pattern may be dynamic (indicate a present pattern and not a periodic pattern). The indication of a dynamic pattern may be transmitted when a network entity transmit inactivity state or a network entity receive inactivity state is triggered and if a backhaul is available. If the pattern is dynamic, the starting slot (first slot) may be a current slot or a slot that has already occurred (e.g., negative slot value). The starting slot may be retroactive, where one or more network entity transmit inactive states and/or network entity receive inactive states are reported (e.g., reportedSignaling support). The pattern may be among network entities (e.g., inter-gNB coordination) or within a split-network entity (e.g., intra-gNB coordination, disaggregated base station coordination).

In some aspects, the first message may indicate a different inactivity pattern or parameters (e.g., starting slot, ending slot, duration) for DRX than for DTX. Alternatively, in some aspects, the first message may indicate that the pattern or the parameters are the same for DRX as for DTX. For example, if the first message includes a starting slot, an ending slot, and an indication that the DRX pattern and the DTX pattern are the same, the DTX mode and the DRX mode for network entity810both start at the starting slot and end at the ending slot.

As shown by reference number940, network entity910may start a DRX mode according to the DRX timing and/or a DTX mode according to the DTX timing. Using the DRX mode or the DTX mode may include reducing power to radio components as described in connection withFIG.5. The network entity910may communicate based at least in part on the DRX timing or the DTX timing. For example, the network entity910may transmit communications before the starting slot for a DTX mode and refrain from transmitting until after the ending slot for the DTX mode. The network entity910may receive communications before the starting slot for the DRX mode and refrain from receiving until after the ending slot for the DRX mode.

In some aspects, as shown by reference number950, network entity930may transmit a second message. The second message may be a response message in response to the first message. For example, the second message may indicate acceptance of the DRX timing or DTX timing. The second message may be a reused message, such as an NG-RAN NODE CONFIGURATION UPDATE message. The second message may be adaptive in size. For example, the second message may transmit only information related to a network entity inactivity state (e.g., a DRX mode, a DTX mode) when DRX or DTX information is to be provided. The network entity910may start the DRX mode and/or the DTX mode at reference number940based at least in part on the second message indicating acceptance or confirms the use of the DRX timing and/or the DTX timing.

In some aspects, the network entity910may not start the DRX mode and/or the DTX mode based at least in part on the second message indicating no acceptance of the DRX mode and the DTX mode. The network entity910may adjust the DRX timing of the DRX mode and/or the DTX timing of the DTX mode if the second message indicates no acceptance. The network entity910may also proceed with the DRX timing of the DRX mode and/or the DTX timing of the DTX mode if the second message indicates no acceptance.

As shown by reference number945, network entity930may adjust communication scheduling or a measurement configuration for UEs served by network entity930based at least in part on the DRX timing and/or the DTX timing. For example, network entity930may schedule (or be more likely to schedule or prioritize scheduling) UE transmissions and/or receptions during the transmit inactivity period of the DTX mode of network entity930and/or the receive inactivity period of the DRX mode of the network entity930. For example, network entity930may schedule data transmissions and/or CSI-RSs to UEs at cell edges or to UEs experiencing interference from neighboring network entities when network entity910is in a transmit inactivity state of a DTX mode. Network entity930may schedule an aperiodic CSI-RS (A-CSI-RS) to UEs in the cell during transmit inactivity states and/or receive inactivity states of network entity910. Network entity930may be aware that the A-CSI-RS measurements will be “clean” from interference from network entity910. Network entity930may not schedule (or be less likely to schedule or deprioritize scheduling) UE transmissions and/or receptions during the transmit activity period of the DTX mode of network entity930and/or the receive activity period of the DRX mode of the network entity930. If the first message includes retroactive DTX or DRX information, network entity930may consider the DTX or DRX information when receiving CSI reports from UEs in covered cells of network entity930.

In some aspects, network entity930may configure CSI interference measurement (CSI-IM) measurements (as part of a measurement configuration) for UEs served by network entity930based at least in part on transmit inactivity periods of a DTX mode of the network entity910. The network entity930may be aware that the IM measurement is “free” from interference from network entity910during transmit inactivity periods of a DTX mode of the network entity910.

In some aspects, network entity930may enter a DRX mode and/or a DTX mode based at least in part on the DRX mode and/or the DTX mode of network entity910such that there is less interference between communications of UEs served by network entity910and UEs served by network entity930.

Apart from network entity910conserving energy when switching to a network entity inactivity state, neighboring network entities, such as network entity930, may conserve energy and avoid interference during a transmit activity period of a DRX mode and/or a receive activity period of a DTX mode of network entity910. By sharing a DRX timing and/or a DTX timing, a network entity may better coordinate communications and measurements with neighboring network entities to improve communications and reduce collisions and interference. As a result, the network entities may conserve power and signaling resources.

FIG.10is a diagram illustrating an example process1000performed, for example, by a first network entity, in accordance with the present disclosure. Example process1000is an example where the first network entity (e.g., base station110, network entity910) performs operations associated with messaging for network entity DTX or DRX.

As shown inFIG.10, in some aspects, process1000may include transmitting a first message to a (neighboring) second network entity, where the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity (block1010). For example, the first network entity (e.g., using communication manager1208and/or transmission component1204depicted inFIG.12) may transmit a first message to a second network entity, where the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity, as described above.

As further shown inFIG.10, in some aspects, process1000may include starting at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing (block1020). For example, the first network entity (e.g., using communication manager1208and/or activity component1210depicted inFIG.12) may start at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing, as described above.

In a first aspect, process1000includes communicating based at least in part on the DRX timing or the DTX timing.

In a second aspect, alone or in combination with the first aspect, the first message indicates that the DRX timing and the DTX timing are the same and indicates a starting slot and an ending slot for the DRX timing and the DTX timing.

In a third aspect, alone or in combination with one or more of the first and second aspects, the first message indicates one or more of a starting slot and an ending slot for the DRX timing, or a starting slot and an ending slot for the DTX timing.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first message is a node configuration update message.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the first message is dedicated to network entity transmission or reception activity.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process1000includes receiving, from the second network entity, a second message associated with accepting or not accepting the one or more of the DRX timing or the DTX timing indicated in the first message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the second message is a node configuration update acknowledge message.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the second message is dedicated to providing a response associated with network entity transmission or reception activity.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, starting the at least one of the DRX mode or the DTX mode includes starting the at least one of the DRX mode according to the DRX timing or the DTX mode according to the DTX timing based at least in part on the second message indicating acceptance of the DRX timing or the DTX timing.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the first message indicates one or more of a semi-persistent pattern or a dynamic pattern for DTX, or a semi-persistent pattern or a dynamic pattern for DRX.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the first message indicates a first slot for the dynamic pattern for DTX, and the first slot has already occurred.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the DRX timing includes a periodicity of the DRX mode or the DTX timing includes a periodicity of the DTX mode.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the first message indicates a DTX starting offset of a DTX cycle or a DRX starting offset of a DRX cycle.

FIG.11is a diagram illustrating an example process1100performed, for example, by a second network entity, in accordance with the present disclosure. Example process1100is an example where the second network entity (e.g., base station110, network entity930) performs operations associated with messaging for network entity DTX or DRX.

As shown inFIG.11, in some aspects, process1100may include receiving, from a first network entity, a first message that indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity (block1110). For example, the second network entity (e.g., using communication manager1208and/or reception component1202depicted inFIG.12) may receive, from a first network entity, a first message that indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity, as described above.

As further shown inFIG.11, in some aspects, process1100may include adjusting one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing (block1120). For example, the second network entity (e.g., using communication manager1208and/or adjustment component1212depicted inFIG.12) may adjust one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing, as described above.

In a first aspect, the first message indicates that the DRX timing and the DTX timing are the same and indicates a starting slot and an ending slot for the DRX timing and the DTX timing.

In a second aspect, alone or in combination with the first aspect, the first message indicates one or more of a starting slot and an ending slot for the DRX timing, or a starting slot and an ending slot for the DTX timing.

In a third aspect, alone or in combination with one or more of the first and second aspects, the first message is a node configuration update message.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the first message is dedicated to network entity transmission or reception activity.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, process1100includes transmitting, to the first network entity, a second message associated with accepting or not accepting the one or more of the DRX timing or the DTX timing indicated in the first message.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process1100includes one or more of adjusting communication scheduling, starting a DRX mode, starting a DTX mode, or adjusting measurements based at least in part on the second message indicating acceptance of the DRX timing or the DTX timing.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the second message is a node configuration update acknowledge message.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the second message is dedicated to providing a response associated with network entity transmission or reception activity.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the first message indicates one or more of a semi-persistent pattern or a dynamic pattern for DTX, or a semi-persistent pattern or a dynamic pattern for DRX.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the first message indicates a first slot for the dynamic pattern for DTX, and the first slot has already occurred.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, adjusting the one or more of the communication scheduling or the measurement configuration includes adjusting the one or more of the communication scheduling or the measurement configuration based at least in part on one or more of a DRX pattern that occurs based at least in part on the DRX timing or a DTX pattern that occurs based at least in part on the DTX timing.

FIG.12is a diagram of an example apparatus1200for wireless communication, in accordance with the present disclosure. The apparatus1200may be a first network entity (e.g., base station110, network entity910) or a second network entity (e.g., neighboring base station, base station110, network entity930). The first network entity and/or the second network entity may include the apparatus1200. In some aspects, the apparatus1200includes a reception component1202and a transmission component1204, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1200may communicate with another apparatus1206(such as a UE, a base station, or another wireless communication device) using the reception component1202and the transmission component1204. As further shown, the apparatus1200may include the communication manager1208. The communication manager1208may control and/or otherwise manage one or more operations of the reception component1202and/or the transmission component1204. In some aspects, the communication manager1208may include one or more antennas, a modem, a controller/processor, a memory, or a combination thereof, of the network entity described in connection withFIG.2. The communication manager1208may be, or be similar to, the communication manager150depicted inFIGS.1and2. For example, in some aspects, the communication manager1208may be configured to perform one or more of the functions described as being performed by the communication manager150. In some aspects, the communication manager1208may include the reception component1202and/or the transmission component1204. The communication manager1208may include an activity component1210and/or an adjustment component1212, among other examples.

In some aspects, if the apparatus1200is the first network entity, the transmission component1204may transmit a first message to a second network entity, where the first message indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The activity component1210may start at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.

The transmission component1204and/or the reception component1202may communicate based at least in part on the DRX timing or the DTX timing. The reception component1202may receive, from the second network entity, a second message associated with accepting or not accepting the one or more of the DRX timing or the DTX timing indicated in the first message.

In some aspects, if the apparatus1200is the second network entity or acting as a neighboring network entity, the reception component1202may receive, from a first network entity, a first message that indicates one or more of a DRX timing of the first network entity or a DTX timing of the first network entity. The adjustment component1212may adjust one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.

The transmission component1204may transmit, to the first network entity, a second message associated with accepting or not accepting the one or more of the DRX timing or the DTX timing indicated in the first message.

The following provides an overview of some Aspects of the present disclosure:Aspect 1: A method of wireless communication performed by an apparatus of a first network entity, comprising: transmitting a first message to a second network entity, wherein the first message indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity; and starting at least one of a DRX mode according to the DRX timing or a DTX mode according to the DTX timing.Aspect 2: The method of Aspect 1, further comprising communicating based at least in part on the DRX timing or the DTX timing.Aspect 3: The method of Aspect 1 or 2, wherein the first message indicates that the DRX timing and the DTX timing are the same and indicates a starting slot and an ending slot for the DRX timing and the DTX timing.Aspect 4: The method of Aspect 1 or 2, wherein the first message indicates one or more of: a starting slot and an ending slot for the DRX timing, or a starting slot and an ending slot for the DTX timing.Aspect 5: The method of any of Aspects 1-4, wherein the DRX timing includes a periodicity of the DRX mode or the DTX timing includes a periodicity of the DTX mode.Aspect 6: The method of any of Aspects 1-5, wherein the first message indicates a DTX starting offset of a DTX cycle or a DRX starting offset of a DRX cycle.Aspect 7: The method of any of Aspects 1-6, wherein the first message is a node configuration update message.Aspect 8: The method of any of Aspects 1-6, wherein the first message is dedicated to network entity transmission or reception activity.Aspect 9: The method of any of Aspects 1-8, further comprising receiving, from the second network entity, a second message associated with accepting or not accepting the one or more of the DRX timing or the DTX timing indicated in the first message.Aspect 10: The method of Aspect 9, wherein the second message is a node configuration update acknowledge message.Aspect 11: The method of Aspect 9, wherein the second message is dedicated to providing a response associated with network entity transmission or reception activity.Aspect 12: The method of any of Aspects 9-11, wherein starting the at least one of the DRX mode or the DTX mode includes starting the at least one of the DRX mode according to the DRX timing or the DTX mode according to the DTX timing based at least in part on the second message indicating acceptance of the DRX timing or the DTX timing.Aspect 13: The method of any of Aspects 1-12, wherein the first message indicates one or more of: a semi-persistent pattern or a dynamic pattern for DTX; or a semi-persistent pattern or a dynamic pattern for DRX.Aspect 14: The method of Aspect 13, wherein the first message indicates a first slot for the dynamic pattern for DTX, and wherein the first slot has already occurred.Aspect 15: A method of wireless communication performed by an apparatus of a second network entity, comprising: receiving, from a first network entity, a first message that indicates one or more of a discontinuous reception (DRX) timing of the first network entity or a discontinuous transmission (DTX) timing of the first network entity; and adjusting one or more of communication scheduling or a measurement configuration based at least in part on the one or more of the DRX timing or the DTX timing.Aspect 16: The method of Aspect 15, wherein the first message indicates that the DRX timing and the DTX timing are the same and indicates a starting slot and an ending slot for the DRX timing and the DTX timing.Aspect 17: The method of Aspect 15, wherein the first message indicates one or more of: a starting slot and an ending slot for the DRX timing, or a starting slot and an ending slot for the DTX timing.Aspect 18: The method of any of Aspects 15-17, wherein the first message is a node configuration update message.Aspect 19: The method of any of Aspects 15-17, wherein the first message is dedicated to network entity transmission or reception activity.Aspect 20: The method of any of Aspects 15-19, further comprising transmitting, to the first network entity, a second message associated with accepting or not accepting the one or more of the DRX timing or the DTX timing indicated in the first message.Aspect 21: The method of Aspect 20, further comprising one or more of adjusting communication scheduling, starting a DRX mode, starting a DTX mode, or adjusting measurements based at least in part on the second message indicating acceptance of the DRX timing or the DTX timing.Aspect 22: The method of Aspect 20 or 21, wherein the second message is a node configuration update acknowledge message.Aspect 23: The method of Aspect 20 or 21, wherein the second message is dedicated to providing a response associated with network entity transmission or reception activity.Aspect 24: The method of any of Aspects 15-23, wherein the first message indicates one or more of: a semi-persistent pattern or a dynamic pattern for DTX; or a semi-persistent pattern or a dynamic pattern for DRX.Aspect 25: The method of Aspect 24, wherein the first message indicates a first slot for the dynamic pattern for DTX, and wherein the first slot has already occurred.Aspect 26: The method of any of Aspects 15-25, wherein adjusting the one or more of the communication scheduling or the measurement configuration includes adjusting the one or more of the communication scheduling or the measurement configuration based at least in part on one or more of a DRX pattern that occurs based at least in part on the DRX timing or a DTX pattern that occurs based at least in part on the DTX timing.Aspect 27: An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-26.Aspect 28: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of Aspects 1-26.Aspect 29: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-26.Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-26.Aspect 31: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-26.