Patent Description:
A base station may transmit data and control information on the downlink to a UE or may receive data and control information on the uplink from the UE.

In fifth generation (<NUM>) new radio (NR) wireless communication systems, UEs may be configured to conserve power by entering a low power operating mode (e.g., a "sleep" mode) when a discontinuous reception (DRX) timer expires or when the UEs receive a DRX medium access control (MAC) control element (MAC-CE) from a base station. The base station may transmit the DRX MAC-CE to the UE based on a determination that there is no more data to be transmitted to the UE by the base station, and thus the UE may enter the low power operating mode. However, for at least some applications, data communicated between the UE and the base station may be predominately transmitted by the UE to the base station in an uplink (UL) data session. The base station may not know when the UE has finished the UL data session, which may result in the base station failing to transmit a DRX MAC-CE to the UE, thereby preventing the UE from entering the low power operating mode, and reducing power consumption, prior to expiration of the DRX timer even though there is no more data to be communicated between the UE and the base station. 3GPP TSG-RAN R2-<NUM> discloses transition into RRC_INACTIVE or RRC_IDLE, in response to an indication of the UE not having data stored in the buffer.

The following summarizes some aspects of the present disclosure to provide a basic understanding of the discussed technology. This summary is not an extensive overview of all contemplated features of the disclosure and is intended neither to identify key or critical elements of all aspects of the disclosure nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts of one or more aspects of the disclosure in summary form as a prelude to the more detailed description that is presented later.

In one aspect of the disclosure, a method of wireless communication includes determining, at a user equipment (UE), that a current data transmission to a network entity is complete. The method further includes transmitting, to the network entity and based on the determination, an indication to terminate a discontinuous reception (DRX) active time assigned to the UE.

In an additional aspect of the disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor, and a memory coupled to the at least one processor. The at least one processor, when executing instructions stored in the memory, is configured to cause the apparatus to determine that a current data transmission to a network entity is complete. The at least one processor is further configured to initiate transmission, to the network entity and based on the determination, of an indication to terminate a DRX active time.

In an additional aspect of the disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes means for determining, at a UE, that a current data transmission to a network entity is complete. The apparatus further includes means for transmitting, to the network entity and based on the determination, an indication to terminate a DRX active time assigned to the UE.

In an additional aspect of the disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations including determining, at a UE, that a current data transmission to a network entity is complete. The operations further include initiating transmission, to the network entity and based on the determination, of an indication to terminate a DRX active time assigned to the UE.

In an additional aspect of the disclosure, a method of wireless communication includes receiving, at a network entity from a UE, an indication to terminate a DRX active time assigned to the UE. The method further includes determining whether to terminate the DRX active time based on whether a current data transmission to the UE is complete.

In an additional aspect of the disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes at least one processor, and a memory coupled to the at least one processor. The at least one processor, when executing instructions stored in the memory, is configured to cause the apparatus to receive, from a UE, an indication to terminate a DRX active time assigned to the UE. The at least one processor is further configured to determine whether to terminate the DRX active time based on whether a current data transmission to the UE is complete.

In an additional aspect of the disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes means for receiving, at a network entity from a UE, an indication to terminate a DRX active time assigned to the UE. The apparatus further includes means for determining whether to terminate the DRX active time based on whether a current data transmission to the UE is complete.

In an additional aspect of the disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations including receiving, at a network entity from a UE, an indication to terminate a DRX active time assigned to the UE. The operations further include determining whether to terminate the DRX active time based on whether a current data transmission to the UE is complete.

Other aspects, features, and implementations will become apparent to those of ordinary skill in the art, upon reviewing the following description of specific, exemplary aspects in conjunction with the accompanying figures. While features may be discussed relative to certain aspects and figures below, all aspects can include one or more of the advantageous features discussed herein. In other words, while one or more aspects may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various aspects. In similar fashion, while exemplary aspects may be discussed below as device, system, or method aspects the exemplary aspects can be implemented in various devices, systems, and methods.

The present disclosure provides systems, apparatus, methods, and computer-readable media for enabling user equipment (UE)-initiated discontinuous reception (DRX) medium access control (MAC) control elements (MAC-CEs). For example, a UE described herein may be configured to determine that a current data transmission (e.g., transmission of one or more data packets, such as during an uplink (UL) data session or an UL data burst) with a network entity, such as a base station, is completed. In some implementations, the UE may determine that the current data transmission is completed based on a determination that a buffer configured to store data for transmission to the network entity is empty. In some other alternatives, the determination may be based on an indication from an application executed by the UE. Based on this determination, the UE may transmit a DRX MAC-CE to the network entity. The DRX MAC-CE may indicate that a DRX active time is to be terminated at the UE. In some implementations, the indication may include a one-byte MAC-CE that is included as padding in a physical uplink shared channel (PUSCH) transmission to the network entity and that includes a logical channel identifier (ID) associated with the UE.

In some implementations, the network entity may authorize the UE to terminate the DRX active time based on the DRX MAC-CE from the UE. For example, the network entity may transmit a downlink communication to the UE based on a determination that a current downlink (DL) transmission (e.g., transmission of one or more data packets, such as during a DL data session or a DL data burst) is complete. In some implementations, the determination is based on a determination that there is no data stored at the network entity for transmission to the UE (e.g., that a buffer at the network entity configured to store data for transmission to the UE is empty). Based on the downlink communication from the network entity, the UE may terminate the DRX active time and transition into a low power operating mode (e.g., a "sleep" mode) to conserve power. If the UE does not receive the downlink communication from the network entity, the UE may remain in an active operating mode.

In some other implementations, the UE may determine whether to terminate the DRX active time instead of relying on authorization from the network entity. To illustrate, the UE may initiate a transmission timer based on transmitting the DRX MAC-CE to the network entity. If the transmission timer expires without the UE receiving a DL communication from the network entity, the UE may enter the low power operating mode. If the UE receives a DL communication, such as a message scheduling or including DL data or a hybrid automatic request (HARQ) retransmission grant, from the network entity, the UE may maintain the active operating mode to receive or transmit additional data.

Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some aspects, the present disclosure provides techniques for enabling UE-initiated DRX MAC-CEs. For example, a UE may transmit a DRX MAC-CE to a network entity based on a determination that the UE has completed a current UL data transmission (e.g., an UL data session or an UL data burst). Transmitting the DRX MAC-CE may enable the UE to more quickly enter the low power operating mode than waiting for the network entity to determine that a data session is complete or for expiration of a DRX active timer. Entering the low power operating mode enables the UE to conserve power, as compared to remaining in the active operating mode. The techniques described herein may reduce power consumption at particular types of UEs that would otherwise not be able to reduce power consumption using DRX. As one example, UEs configured to perform extended reality (XR) applications (or augmented reality (AR) or virtual reality (VR) applications), or battery powered video cameras, may transmit a frame approximately every <NUM> milliseconds (ms). Transmitting each frame may takes approximately <NUM>-<NUM> milliseconds. If such UEs are assigned a typical <NUM> DRX active time, the UEs may not be able to enter the low power operating mode because a new frame will need to be transmitted before expiration of the DRX active time. As another example, wearable UEs, such as smart watches, fitness devices, etc., may benefit from entering the low power operating mode after a traffic burst is complete. However, the traffic burst may be driven by the UE, and the network entity may not know that the traffic burst is complete in order to instruct the UE to terminate the DRX active time before expiration of the DRX active timer, which may limit the amount of power saving at the UE.

This disclosure relates generally to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communications systems, also referred to as wireless communications networks. In various implementations, the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5th Generation (<NUM>) or new radio (NR) networks (sometimes referred to as "<NUM> NR" networks, systems, or devices), as well as other communications networks. As described herein, the terms "networks" and "systems" may be used interchangeably.

A TDMA network may, for example implement a radio technology such as Global System for Mobile Communication (GSM). The 3rd Generation Partnership Project (3GPP) defines standards for the GSM EDGE (enhanced data rates for GSM evolution) radio access network (RAN), also denoted as GERAN. GERAN is the radio component of GSM/EDGE, together with the network that joins the base stations (for example, the Ater and Abis interfaces) and the base station controllers (A interfaces, etc.). The radio access network represents a component of a GSM network, through which phone calls and packet data are routed from and to the public switched telephone network (PSTN) and Internet to and from subscriber handsets, also known as user terminals or user equipments (UEs). A mobile phone operator's network may comprise one or more GERANs, which may be coupled with Universal Terrestrial Radio Access Networks (UTRANs) in the case of a UMTS/GSM network. Additionally, an operator network may also include one or more long term evolution (LTE) networks, or one or more other networks. The various different network types may use different radio access technologies (RATs) and radio access networks (RANs).

An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) <NUM>, IEEE <NUM>, IEEE <NUM>, flash-OFDM and the like. In particular, LTE is a release of UMTS that uses E-UTRA. For example, the 3GPP is a collaboration between groups of telecommunications associations that aims to define a globally applicable third generation (<NUM>) mobile phone specification. 3GPP LTE is a 3GPP project which was aimed at improving the universal mobile telecommunications system (UMTS) mobile phone standard. The present disclosure may describe certain aspects with reference to LTE, <NUM>, or <NUM> NR technologies; however, the description is not intended to be limited to a specific technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Indeed, one or more aspects of the present disclosure are related to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

<NUM> networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface. To achieve these goals, further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for <NUM> NR networks. The <NUM> NR will be capable of scaling to provide coverage (<NUM>) to a massive Internet of things (IoTs) with an ultra-high density (e.g., ~<NUM> nodes/km<NUM>), ultra-low complexity (e.g., ~<NUM> of bits/sec), ultra-low energy (e.g., ~<NUM>+ years of battery life), and deep coverage with the capability to reach challenging locations; (<NUM>) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., -<NUM>% reliability), ultra-low latency (e.g., ~ <NUM> millisecond (ms)), and users with wide ranges of mobility or lack thereof; and (<NUM>) with enhanced mobile broadband including extreme high capacity (e.g., ~ <NUM> Tbps/km<NUM>), extreme data rates (e.g., multi-Gbps rate, <NUM>+ Mbps user experienced rates), and deep awareness with advanced discovery and optimizations.

<NUM> NR devices, networks, and systems may be implemented to use optimized OFDM-based waveform features. These features may include scalable numerology and transmission time intervals (TTIs); a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD) or frequency division duplex (FDD) design; and advanced wireless technologies, such as massive multiple input, multiple output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility. Scalability of the numerology in <NUM> NR, with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments. For example, in various outdoor and macro coverage deployments of less than <NUM> FDD or TDD implementations, subcarrier spacing may occur with <NUM>, for example over <NUM>, <NUM>, <NUM>, <NUM>, and the like bandwidth. For other various outdoor and small cell coverage deployments of TDD greater than <NUM>, subcarrier spacing may occur with <NUM> over <NUM> or <NUM> bandwidth. For other various indoor wideband implementations, using a TDD over the unlicensed portion of the <NUM> band, the subcarrier spacing may occur with <NUM> over a <NUM> bandwidth. Finally, for various deployments transmitting with mmWave components at a TDD of <NUM>, subcarrier spacing may occur with <NUM> over a <NUM> bandwidth.

The scalable numerology of <NUM> NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. <NUM> NR also contemplates a self-contained integrated subframe design with uplink or downlink scheduling information, data, and acknowledgement in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink or downlink that may be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet the current traffic needs.

For clarity, certain aspects of the apparatus and techniques may be described below with reference to example <NUM> NR implementations or in a <NUM>-centric way, and <NUM> terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to <NUM> applications.

Moreover, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate with any combination of licensed or unlicensed spectrum depending on loading and availability. Accordingly, it will be apparent to a person having ordinary skill in the art that the systems, apparatus and methods described herein may be applied to other communications systems and applications than the particular examples provided.

While aspects and implementations are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, implementations or uses may come about via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail devices, purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more described aspects. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described aspects. It is intended that innovations described herein may be practiced in a wide variety of implementations, including both large devices or small devices, chip-level components, multi-component systems (e.g. radio frequency (RF)-chain, communication interface, processor), distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.

<FIG> is a block diagram illustrating details of an example wireless communication system. The wireless communication system may include wireless network <NUM>. Wireless network <NUM> may, for example, include a <NUM> wireless network. As appreciated by those skilled in the art, components appearing in <FIG> are likely to have related counterparts in other network arrangements including, for example, cellular-style network arrangements and non-cellular-style-network arrangements (e.g., device to device or peer to peer or ad hoc network arrangements, etc.).

Wireless network <NUM> illustrated in <FIG> includes a number of base stations <NUM> and other network entities. A base station may be a station that communicates with the UEs and may also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, and the like. Each base station <NUM> may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to this particular geographic coverage area of a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In implementations of wireless network <NUM> herein, base stations <NUM> may be associated with a same operator or different operators (e.g., wireless network <NUM> may include a plurality of operator wireless networks). Additionally, in implementations of wireless network <NUM> herein, base station <NUM> may provide wireless communications using one or more of the same frequencies (e.g., one or more frequency bands in licensed spectrum, unlicensed spectrum, or a combination thereof) as a neighboring cell. In some examples, an individual base station <NUM> or UE <NUM> may be operated by more than one network operating entity. In some other examples, each base station <NUM> and UE <NUM> may be operated by a single network operating entity.

A base station may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, or other types of cell. A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station or a home base station. In the example shown in <FIG>, base stations 105d and 105e are regular macro base stations, while base stations 105a-105c are macro base stations enabled with one of <NUM> dimension (3D), full dimension (FD), or massive MIMO. Base stations 105a-105c take advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station which may be a home node or portable access point. A base station may support one or multiple (e.g., two, three, four, and the like) cells.

Wireless network <NUM> may support synchronous or asynchronous operation. In some scenarios, networks may be enabled or configured to handle dynamic switching between synchronous or asynchronous operations.

UEs <NUM> are dispersed throughout the wireless network <NUM>, and each UE may be stationary or mobile. It should be appreciated that, although a mobile apparatus is commonly referred to as user equipment (UE) in standards and specifications promulgated by the 3GPP, such apparatus may additionally or otherwise be referred to by those skilled in the art as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, a gaming device, an augmented reality device, vehicular component device or module, or some other suitable terminology. Within the present document, a "mobile" apparatus or UE need not necessarily have a capability to move, and may be stationary. Some non-limiting examples of a mobile apparatus, such as may include implementations of one or more of UEs <NUM>, include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a laptop, a personal computer (PC), a notebook, a netbook, a smart book, a tablet, and a personal digital assistant (PDA). A mobile apparatus may additionally be an "Internet of things" (IoT) or "Internet of everything" (IoE) device such as an automotive or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-copter, a quad-copter, a smart energy or security device, a solar panel or solar array, municipal lighting, water, or other infrastructure; industrial automation and enterprise devices; consumer and wearable devices, such as eyewear, a wearable camera, a smart watch, a health or fitness tracker, a mammal implantable device, gesture tracking device, medical device, a digital audio player (e.g., MP3 player), a camera, a game console, etc.; and digital home or smart home devices such as a home audio, video, and multimedia device, an appliance, a sensor, a vending machine, intelligent lighting, a home security system, a smart meter, etc. In one aspect, a UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE may be a device that does not include a UICC. In some aspects, UEs that do not include UICCs may also be referred to as IoE devices. UEs 115a-115d of the implementation illustrated in <FIG> are examples of mobile smart phone-type devices accessing wireless network <NUM> A UE may also be a machine specifically configured for connected communication, including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. UEs 115e-<NUM> illustrated in <FIG> are examples of various machines configured for communication that access wireless network <NUM>.

A mobile apparatus, such as UEs <NUM>, may be able to communicate with any type of the base stations, whether macro base stations, pico base stations, femto base stations, relays, and the like. In <FIG>, a communication link (represented as a lightning bolt) indicates wireless transmissions between a UE and a serving base station, which is a base station designated to serve the UE on the downlink or uplink, or desired transmission between base stations, and backhaul transmissions between base stations. UEs may operate as base stations or other network nodes in some scenarios. Backhaul communication between base stations of wireless network <NUM> may occur using wired or wireless communication links.

In operation at wireless network <NUM>, base stations 105a-105c serve UEs 115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity. Macro base station 105d performs backhaul communications with base stations 105a-105c, as well as small cell, base station 105f. Macro base station 105d also transmits multicast services which are subscribed to and received by UEs 115c and 115d.

Wireless network <NUM> of implementations supports mission critical communications with ultra-reliable and redundant links for mission critical devices, such UE 115e, which is a drone. Redundant communication links with UE 115e include from macro base stations 105d and 105e, as well as small cell base station 105f. Other machine type devices, such as UE 115f (thermometer), UE <NUM> (smart meter), and UE <NUM> (wearable device) may communicate through wireless network <NUM> either directly with base stations, such as small cell base station 105f, and macro base station 105e, or in multi-hop configurations by communicating with another user device which relays its information to the network, such as UE 115f communicating temperature measurement information to the smart meter, UE <NUM>, which is then reported to the network through small cell base station 105f. Wireless network <NUM> may also provide additional network efficiency through dynamic, low-latency TDD communications or FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-<NUM> communicating with macro base station 105e.

<FIG> shows a block diagram illustrating examples of base station <NUM> and UE <NUM> according to one or more aspects, which may be any of the base stations and one of the UEs in <FIG>. For a restricted association scenario (as mentioned above), base station <NUM> may be small cell base station 105f in <FIG>, and UE <NUM> may be UE 115c or 115D operating in a service area of base station 105f, which in order to access small cell base station 105f, would be included in a list of accessible UEs for small cell base station 105f. Base station <NUM> may also be a base station of some other type. As shown in <FIG>, base station <NUM> may be equipped with antennas 234a through 234t, and UE <NUM> may be equipped with antennas 252a through 252r for facilitating wireless communications.

At base station <NUM>, transmit processor <NUM> may receive data from data source <NUM> and control information from controller <NUM> (e.g., a processor). The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid-ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. Additionally, transmit processor <NUM> may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. Transmit processor <NUM> may also generate reference symbols, e.g., for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. Transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, or the reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a through 232t. For example, spatial processing performed on the data symbols, the control symbols, or the reference symbols may include precoding. Each modulator <NUM> may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

At UE <NUM>, the antennas 252a through 252r may receive the downlink signals from base station <NUM> and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. MIMO detector <NUM> may obtain received symbols from demodulators 254a through 254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. Receive processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE <NUM> to data sink <NUM>, and provide decoded control information to a controller <NUM> (e.g., a processor).

On the uplink, at UE <NUM>, transmit processor <NUM> may receive and process data (e.g., for a physical uplink shared channel (PUSCH)) from data source <NUM> and control information (e.g., for a physical uplink control channel (PUCCH)) from controller <NUM>. Additionally, transmit processor <NUM> may generate reference symbols for a reference signal. The symbols from transmit processor <NUM> may be precoded by TX MIMO processor <NUM> if applicable, further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to base station <NUM>. At base station <NUM>, the uplink signals from UE <NUM> may be received by antennas <NUM>, processed by demodulators <NUM>, detected by MIMO detector <NUM> if applicable, and further processed by receive processor <NUM> to obtain decoded data and control information sent by UE <NUM>. Receive processor <NUM> may provide the decoded data to data sink <NUM> and the decoded control information to controller <NUM>.

Controllers <NUM> and <NUM> may direct the operation at base station <NUM> and UE <NUM>, respectively. Controller <NUM> or other processors and modules at base station <NUM> or controller <NUM> or other processors and modules at UE <NUM> may perform or direct the execution of various processes for the techniques described herein, such as to perform or direct the execution illustrated in <FIG>, or other processes for the techniques described herein. Memories <NUM> and <NUM> may store data and program codes for base station <NUM> and UE <NUM>, respectively. Scheduler <NUM> may schedule UEs for data transmission on the downlink or uplink.

In some cases, UE <NUM> and base station <NUM> may operate in a shared radio frequency spectrum band, which may include licensed or unlicensed (e.g., contention-based) frequency spectrum. In an unlicensed frequency portion of the shared radio frequency spectrum band, UEs <NUM> or base stations <NUM> may traditionally perform a medium-sensing procedure to contend for access to the frequency spectrum. For example, UE <NUM> or base station <NUM> may perform a listen-before-talk or listen-before-transmitting (LBT) procedure such as a clear channel assessment (CCA) prior to communicating in order to determine whether the shared channel is available. In some implementations, a CCA may include an energy detection procedure to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that a channel is occupied. Specifically, signal power that is concentrated in a certain bandwidth and exceeds a predetermined noise floor may indicate another wireless transmitter. A CCA also may include detection of specific sequences that indicate use of the channel. For example, another device may transmit a specific preamble prior to transmitting a data sequence. In some cases, an LBT procedure may include a wireless node adjusting its own backoff window based on the amount of energy detected on a channel or the acknowledge/negative-acknowledge (ACK/NACK) feedback for its own transmitted packets as a proxy for collisions.

The present disclosure provides systems, apparatus, methods, and computer-readable media for enabling UE-initiated discontinuous reception (DRX) medium access control (MAC) control elements (MAC-CEs). For example, a UE described herein may be configured to determine that a current data transmission (e.g., transmission of one or more data packets, such as during an uplink (UL) data session or an UL data burst) with a network entity, such as a base station, is completed. In some implementations, the UE may determine that the current data transmission is completed based on a determination that a buffer configured to store data for transmission to the network entity is empty. In some other implementations, the determination may be based on an indication from an application executed by the UE Based on this determination, the UE may transmit a DRX MAC-CE to the network entity. The DRX MAC-CE may indicate that a DRX active time is to be terminated at the UE. In some implementations, the indication may include a one-byte MAC-CE that is included as padding in a physical uplink shared channel (PUSCH) transmission to the network entity and that includes a logical channel identifier (ID) associated with the UE.

<FIG> is a block diagram of an example wireless communications system <NUM> that supports UE-initiated DRX MAC-CEs according to one or more aspects. In some implementations, wireless communications system <NUM> may implement aspects of wireless network <NUM>. Wireless communications system <NUM> includes UE <NUM> and a network entity <NUM>. Network entity <NUM> may include or correspond to a base station, such as base station <NUM>, a network, a network core, or another network device, as illustrative, non-limiting examples. Although one UE <NUM> and one network entity <NUM> are illustrated, in some other implementations, wireless communications system <NUM> may generally include multiple UEs <NUM>, and may include more than one network entity <NUM>.

UE <NUM> can include a variety of components (such as structural, hardware components) used for carrying out one or more functions described herein. For example, these components can include a processor <NUM>, a memory <NUM>, a buffer <NUM>, an optional DRX active timer <NUM>, an optional transmission timer <NUM>, a transmitter <NUM>, and a receiver <NUM>. Processor <NUM> may be configured to execute instructions stored at memory <NUM> to perform the operations described herein. In some implementations, processor <NUM> includes or corresponds to controller <NUM>, and memory <NUM> includes or corresponds to memory <NUM>.

Buffer <NUM> may be configured to store data for transmission to network entity <NUM>. For example, buffer <NUM> may be configured to store one or more data packets that are scheduled to be transmitted to network entity <NUM> as part of an UL data session or data burst. DRX active timer <NUM> may be configured to signal a duration of a DRX active time at UE <NUM>. In some implementations, DRX active timer <NUM> has a duration of <NUM>. In other implementations, DRX active timer <NUM> has a different duration, such as <NUM>, <NUM>, or <NUM>, as non-limiting examples. Transmission timer <NUM> may be configured to signal a duration of a time period between UE <NUM> transmitting a DRX MAC CE and UE <NUM> terminating the DRX active time at UE <NUM>. In some implementations, transmission timer <NUM> has a duration of approximately <NUM>.

Transmitter <NUM> is configured to transmit reference signals, control information, and data to one or more other devices, and receiver <NUM> is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitter <NUM> may transmit signaling, control information, and data, and receiver <NUM> may receive signaling, control information, and data, via a network, such as a wired network, a wireless network, or a combination thereof. For example, UE <NUM> may be configured to transmit or receive signaling, control information, and data via a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate. In some implementations, transmitter <NUM> and receiver <NUM> may be integrated in a transceiver. Additionally, or alternatively, transmitter <NUM>, receiver <NUM>, or both may include and correspond to one or more components of UE <NUM> described with reference to <FIG>.

Network entity <NUM> can include a variety of components (such as structural, hardware components) used for carrying out one or more functions described herein. For example, these components can include a processor <NUM>, a memory <NUM>, a transmitter <NUM>, a receiver <NUM>, and a buffer <NUM>. Processor <NUM> may be configured to execute instructions stored at memory <NUM> to perform the operations described herein. In some implementations, processor <NUM> includes or corresponds to controller <NUM>, and memory <NUM> includes or corresponds to memory <NUM>.

Transmitter <NUM> is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and receiver <NUM> is configured to receive reference signals, control information, and data from one or more other devices. For example, transmitter <NUM> may transmit signaling, control information, and data, and receiver <NUM> may receive signaling, control information, and data, via a network, such as a wired network, a wireless network, or a combination thereof. For example, network entity <NUM> may be configured to transmit or receive data via a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communications network now known or later developed within which permits two or more electronic devices to communicate. In some implementations, transmitter <NUM> and receiver <NUM> may be integrated in a transceiver. Additionally, or alternatively, transmitter <NUM>, receiver <NUM> or both may include and correspond to one or more components of base station <NUM> described with reference to <FIG>.

Buffer <NUM> may be configured to store data for transmission to UE <NUM>. For example, buffer <NUM> may be configured to store one or more data packets that are scheduled to be transmitted to UE <NUM> as part of a DL data session or data burst.

In some implementations, wireless communications system <NUM> implements a <NUM> New Radio (NR) network. For example, wireless communications system <NUM> may include multiple <NUM>-capable UEs <NUM> and multiple <NUM>-capable network entities <NUM>, such as UEs and network entities configured to operate in accordance with a <NUM> NR network protocol such as that defined by the 3GPP.

During operation of the wireless communications system <NUM>, UE <NUM> and network entity <NUM> may communicate control information and data via one or more wireless networks. For example, UE <NUM> may transmit one or more UL data packets to network entity <NUM> and may receive one or more DL data packets from network entity <NUM>. The control information or data may be communicated as part of a data session between UE <NUM> and network entity <NUM>.

Additionally, at an initiation of the data session, or upon a scheduled time to transmit UL data or receive DL data at UE <NUM>, UE <NUM> may initiate DRX active timer <NUM>. DRX active timer <NUM> may track a duration of a DRX active time at UE <NUM>. During the DRX active time, UE <NUM> may be configured to maintain (e.g., remain in) an active operating mode. For example, UE <NUM> may maintain power to processor <NUM>, transmitter <NUM>, receiver <NUM>, one or more other components, portions thereof, or a combination thereof, in order to monitor one or more channels, such as a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), or another channel. By remaining in the active operating mode and monitoring the PDCCH, PDSCH, or other channels, UE <NUM> may be able to receive control information or data from network entity <NUM>.

At some time prior to expiration of DRX active timer <NUM>, UE <NUM> may determine that a current data transmission to network entity <NUM> is complete. For example, the data session, or a UL data burst, may be complete if UE <NUM> determines that no more data is to be transmitted to network entity <NUM> in the immediate future (e.g., within a particular time period). The determination may be based on a status of buffer <NUM>. For example, UE <NUM> may determine that the current data transmission (e.g., the data session or the UL data burst) is complete based on determining that buffer <NUM> is empty (e.g., that no data is stored at buffer <NUM> for transmission to network entity <NUM>). Alternatively, UE <NUM> may determine that the current data transmission is not complete based on determining that buffer <NUM> stores at least one data packet for transmission to network entity <NUM>. Although described as being based on the status of buffer <NUM>, in some other implementations, UE <NUM> may determine that the current data transmission is complete based on other information, such as an indication from the application layer of an application executed by UE <NUM>. For example, an application requesting transmission of data to network entity <NUM> may signal to UE <NUM> that no more data is to be transmitted, at least for a particular time period.

Based on the determination, UE <NUM> may generate an indication to terminate the DRX active time assigned to UE <NUM>. In some implementations, the indication includes or corresponds to a DRX MAC-CE <NUM>. For example, UE <NUM> may generate a MAC structure including control information that indicates a request by UE <NUM> to terminate the DRX active time. In some implementations, DRX MAC-CE <NUM> may be a one-byte MAC-CE. In other implementations, DRX MAC-CE <NUM> may have a different size, such as larger than one byte or smaller than one byte. In some implementations, DRX MAC-CE <NUM> only includes a logical channel identifier (ID) <NUM> associated with DRX MAC-CE <NUM> (e.g., no information in addition to logical channel ID <NUM>). For example, a header of DRX MAC-CE <NUM> may include logical channel ID <NUM>. In some other implementations, DRX MAC-CE <NUM> includes additional information as well as logical channel ID <NUM>.

UE <NUM> may transmit DRX MAC-CE <NUM> to network entity <NUM>. For example, UE <NUM> may transmit DRX MAC-CE <NUM> individually, or as part of a message, to network entity <NUM>. In some implementations, DRX MAC-CE <NUM> is included in a physical uplink shared channel (PUSCH) transmission <NUM> to network entity <NUM>. In some such implementations, DRX MAC-CE <NUM> may be included as padding in PUSCH transmission <NUM>. For example, DRX MAC-CE <NUM> may replace one or more bits reserved as padding within PUSCH transmission <NUM>. The reservation of the padding may be based on a wireless communication standard specification, such as a 3GPP wireless communication standard specification.

In some implementations, UE <NUM> is configured wait for authorization from network entity <NUM> before terminating the DRX active time period. To illustrate, network entity <NUM> may receive downlink communication <NUM> from UE <NUM> and determine whether to authorize termination of the DRX active time based on a determination whether a current data transmission to UE <NUM> is complete (e.g., whether network entity <NUM> has data for transmission to UE <NUM>, such as a DL data session or a DL data burst). In some implementations, the determination is based on a status of buffer <NUM>. For example, if buffer <NUM> is empty, network entity <NUM> may determine that there is no data to be transmitted to UE <NUM> (e.g., that the current DL data transmission is completed). Based on this determination, network entity <NUM> may determine to authorize termination of the DRX active time at UE <NUM>. However, if buffer <NUM> stores at least one data packet (or network entity <NUM> otherwise determines that the DL data transmission is not complete), network entity <NUM> may determine that there is data to be transmitted to UE <NUM> (e.g., that a data session or a DL data burst is not complete). Based on this determination, network entity <NUM> may determine not to authorize termination of the DRX active time at UE <NUM>. Although described as being based on the status of buffer <NUM>, in some other implementations, network entity <NUM> may determine that the data session or the DL data burst is complete based on other information, such as an indication from the application layer of an application executed by network entity <NUM>.

Based on a determination to terminate the DRX active time at UE <NUM>, network entity <NUM> may generate and transmit downlink communication <NUM> to UE <NUM>. In some implementations, downlink communication <NUM> includes or corresponds to a DRX MAC-CE. In some such implementations, downlink communication <NUM> is a one-byte MAC-CE that only includes a logical channel ID associated with downlink communication <NUM>. In some other implementations, downlink communication <NUM> has a different size or includes other information. Network entity <NUM> may transmit downlink communication <NUM> to UE <NUM> individually or in a message. For example, downlink communication <NUM> may be included in a PDCCH transmission to UE <NUM>. In some implementations, downlink communication <NUM> may be included in bits reserved as padding of the PDCCH transmission.

Receipt of downlink communication <NUM> may enable UE <NUM> to terminate the DRX active time at UE <NUM>. For example, UE <NUM> may receive downlink communication <NUM> and may terminate the DRX active time based on receiving downlink communication <NUM>. In some implementations, terminating the DRX active time may include terminating (e.g., stopping) DRX active timer <NUM>. Based on terminating the DRX active time, UE <NUM> may transition into a low power operating mode (e.g., a "sleep" mode). For example, UE <NUM> may power down one or more of processor <NUM>, transmitter <NUM>, receiver <NUM>, one or more other components, portions thereof, or a combination thereof. During operation in the low power operating mode, UE <NUM> does not monitor one or more channels, such as the PDCCH or the PDSCH, for transmissions from network entity <NUM>. UE <NUM> may remain in the low power operating mode for a remainder of a current DRX cycle. A duration of the DRX cycle may be preconfigured at UE <NUM>.

Based on a determination not to terminate the DRX active time at UE <NUM>, network entity <NUM> may not transmit any DRX MAC-CEs to UE <NUM>. Instead, network entity <NUM> may transmit a DL communication <NUM> to UE <NUM> based on a determination that the current DL transmission is not complete (e.g., a determination that data is stored in buffer <NUM> or that an indication has been received from an application, as non-limiting examples). DL communication <NUM> may be configured to schedule transmission of at least a portion of the data or may include at least a portion of the data. UE <NUM> may maintain (e.g., remain in) the active operating mode if a DRX MAC-CE, such as downlink communication <NUM>, is not received from network entity <NUM>. Thus, UE <NUM> may be monitoring the PDCCH or the PDSCH for DL communication <NUM> from network entity <NUM>. In some implementations, UE <NUM> may restart DRX active timer <NUM> based on receiving DL communication <NUM> from network entity <NUM>.

In some other implementations, UE <NUM> is configured to terminate the DRX active time period without explicit authorization from network entity <NUM>, such as receipt of the DRX MAC-CE <NUM>. In some such implementations, UE <NUM> may initiate transmission timer <NUM> based on transmitting DRX MAC-CE <NUM> to network entity <NUM>. A duration of transmission timer <NUM> may be based on a processing timer of network entity <NUM> associated with DRX MAC-CE <NUM> and a reception time of a DL communication from network entity <NUM> at UE <NUM>. For example, the duration of transmission timer <NUM> may be at least the amount of time that network entity <NUM> takes to process DRX MAC-CE <NUM> combined with the amount of time required for UE <NUM> to receive a DL assignment of additional data from network entity <NUM>. In some implementations, the duration of transmission timer <NUM> is approximately <NUM>. For example, the amount of time that network entity <NUM> takes to process DRX MAC-CE <NUM> may be approximately <NUM>, and the amount of time to receive a DL communication from network entity <NUM> may be approximately <NUM>. In other implementations, the duration of transmission timer <NUM> is less than <NUM> or greater than <NUM>.

UE <NUM> may terminate the DRX active time based on expiration of transmission timer <NUM> without receipt of a DL communication from network entity <NUM>. For example, if UE <NUM> does not receive a DL assignment of additional data from network entity <NUM> by the expiration of transmission timer <NUM>, UE <NUM> may terminate the DRX active time. In some implementations, terminating the DRX active time includes terminating (e.g., stopping) DRX active timer <NUM>. Based on terminating the DRX active time, UE <NUM> may transition into the low power operating mode. UE <NUM> may remain in the low power operating mode for a remainder of a current DRX cycle. During operation in the low power operating mode, UE <NUM> may not monitor one or more channels, such as the PDCCH or the PDSCH, for DL communications from network entity <NUM>.

If network entity <NUM> determines that UE <NUM> should not terminate the DRX active time, network entity <NUM> may generate and transmit DL communication <NUM> to UE <NUM>. For example, network entity <NUM> may transmit DL communication <NUM> based on a determination that buffer <NUM> is not empty (e.g., stores data), or based on an indication from the application layer. DL communication <NUM> may be configured to schedule transmission of at least a portion of the data or may include at least a portion of the data. UE <NUM> may receive DL communication <NUM> from network entity <NUM> and may maintain (e.g., remain in) the active operating mode based on receipt of DL communication <NUM>. UE <NUM> may then monitor the PDCCH or the PDSCH for additional DL communications from network entity <NUM>. In some implementations, UE <NUM> may restart DRX active timer <NUM> based on receiving DL communication <NUM> from network entity <NUM>.

Additionally or alternatively, network entity <NUM> may determine that a transport block (TB) associated with DRX MAC-CE <NUM> is not successfully received at network entity <NUM>. For example, the TB may have too many errors to be decodable, or may not be received by network entity <NUM>. Based on this determination, network entity <NUM> may generate and transmit a hybrid automatic repeat request (HARQ) retransmission grant <NUM> to UE <NUM>. HARQ retransmission grant <NUM> may indicate the TB associated with DRX MAC-CE <NUM> and may request retransmission of the TB. UE <NUM> may receive HARQ retransmission grant <NUM> and, based on receiving HARQ retransmission grant <NUM> prior to expiration of transmission timer <NUM>, UE <NUM> may restart transmission timer <NUM>. For example, UE <NUM> may retransmit the TB and DRX MAC-CE <NUM> to network entity <NUM> and may restart transmission timer <NUM> upon retransmission of DRX MAC-CE <NUM>.

As described with reference to <FIG>, the present disclosure provides techniques for enabling UE-initiated DRX MAC-CEs. For example, UE <NUM> may transmit DRX MAC-CE <NUM> to network entity <NUM> based on a determination that UE <NUM> has no more data to transmit to network entity <NUM>, at least for a particular time period. Because DRX MAC-CE <NUM> may be a one-byte MAC-CE that only includes logical channel ID <NUM>, DRX MAC-CE <NUM> may be transmitted quickly and may have low overhead with respect to wireless communications system <NUM>. Additionally, because UE <NUM> may transition into the low power operating mode, based on either receipt of DRX MAC-CE <NUM> or expiration of transmission timer <NUM>, UE <NUM> may transition into the low power operating mode prior to expiration of DRX active timer <NUM>, which reduces power consumption at UE <NUM>. Enabling UE-initiated requests to terminate the DRX active time may reduce power consumption of particular types of UEs, such as UEs configured to perform XR, AR, or VR applications, battery powered video cameras, or wearable devices (e.g., smart watches, fitness devices, etc.), which would otherwise result in greater power consumption using typical DRX techniques.

Referring to <FIG>, a flow diagram illustrating an example process <NUM> performed by a UE for transmitting a DRX MAC-CE according to one or more aspects is shown. Example operations (also referred to as "blocks") of the process <NUM> will also be described with respect to UE <NUM> as illustrated in <FIG> is a block diagram illustrating an example UE <NUM> configured to transmit a DRX MAC-CE according to one or more aspects. UE <NUM> includes the structure, hardware, and components as illustrated for UE <NUM> of <FIG> or <FIG>. For example, UE <NUM> includes controller <NUM>, which operates to execute logic or computer instructions stored in memory <NUM>, as well as controlling the components of UE <NUM> that provide the features and functionality of UE <NUM>. UE <NUM>, under control of controller <NUM>, transmits and receives signals via wireless radios 601a-r and antennas 252a-r. Wireless radios 601a-r include various components and hardware, as illustrated in <FIG> for UE <NUM>, including modulator or demodulators 254a-r, MIMO detector <NUM>, receive processor <NUM>, transmit processor <NUM>, and TX MIMO processor <NUM>.

As shown, memory <NUM> may include buffer <NUM>, DRX control logic <NUM>, transmit logic <NUM>, and DRX active timer <NUM>. Buffer <NUM> may be configured to store data for transmission to a network entity. DRX control logic <NUM> may be configured to control a DRX active time at UE <NUM>, such as by terminating the DRX active time. Transmit logic <NUM> may be configured to enable transmission of signaling or messages to a base station. DRX active timer <NUM> may be configured to track the DRX active time at UE <NUM>. UE <NUM> may receive signals from or transmit signals to one or more network entities, such as base station <NUM> of <FIG>, network entity <NUM> of <FIG>, a core network, a core network device, or a network entity as illustrated in <FIG>.

Referring to <FIG>, a flow diagram illustrating process <NUM> is shown. In some implementations, process <NUM> may be performed by UE <NUM> or UE <NUM>. In some other implementations, process <NUM> may be performed by an apparatus configured for wireless communication. For example, the apparatus may include at least one processor, and a memory coupled to the processor. The processor may be configured to perform operations of process <NUM>. In some other implementations, process <NUM> may be performed or executed using a non-transitory computer-readable medium having program code recorded thereon. The program code may be program code executable by a computer for causing the computer to perform operations of process <NUM>.

As illustrated at block <NUM>, UE <NUM> determines that a current data transmission to a network entity is complete. As an example of block <NUM>, UE <NUM> may execute, under control of controller <NUM>, DRX control logic <NUM> stored in memory <NUM>. The execution environment of DRX control logic <NUM> provides the functionality to determine that a current data transmission to a network entity is complete. In some implementations, this determination may be based on determining that buffer <NUM> is empty.

At block <NUM>, UE <NUM> transmits, to the network entity and based on the determination, an indication to terminate a DRX active time assigned to UE <NUM>. To illustrate, UE <NUM> may transmit the indication using wireless radios 601a-r and antennas 252a-r. To further illustrate, UE <NUM> may execute, under control of controller <NUM>, transmit logic <NUM> stored in memory <NUM>. The execution environment of transmit logic <NUM> provides the functionality to transmit an indication to terminate a DRX active time assigned to UE <NUM> to the network entity. Terminating the DRX active time may include terminating DRX active timer <NUM>.

In some implementations, the indication includes a one-byte MAC-CE. In some such implementations, the one-byte MAC-CE is included as padding in a PUSCH transmission to the network entity. Additionally or alternatively, the one-byte MAC-CE may include a logical channel ID associated with the one-byte MAC-CE.

In some implementations, a determination that the current data transmission is complete is based on detecting that a buffer configured to store data for transmission to the network entity is empty. For example, the determination may be based on detecting that buffer <NUM> is empty (e.g., contains no data for transmission to the network entity).

In some implementations, process <NUM> also includes receiving, from the network entity, a downlink communication based on transmitting the indication and terminating the DRX active time based on receiving the downlink communication. In some such implementations, the downlink communication includes or corresponds to a DRX MAC-CE. Additionally, or alternatively, process <NUM> may further include transitioning into a low power operating mode based on terminating the DRX active time.

In some implementations, process <NUM> further includes maintaining an active operating mode at the UE if a downlink communication is not received from the network entity. In some such implementations, the downlink communication is a DRX MAC-CE.

In some implementations, process <NUM> also includes initiating a timer based on transmitting the indication. In some such implementations, a duration of the timer is based on a processing time of the network entity associated with the indication and a reception time of a downlink communication from the network entity at the UE. Additionally or alternatively, process <NUM> also includes terminating the DRX active time based on expiration of the timer without receipt of a downlink communication from the network entity. In some such implementations, process <NUM> further includes transitioning into a low power operating mode based on terminating the DRX active time. Alternatively, process <NUM> may further include receiving, prior to expiration of the timer, a downlink communication from the network entity and maintaining an active operating mode at the UE based on receipt of the downlink communication. Alternatively, process <NUM> may further include receiving, prior to expiration of the timer, a HARQ retransmission grant from the network entity and restarting the timer based on receipt of the HARQ retransmission gran. The HARQ retransmission grant may be associated with a transport block that includes the indication.

As described with reference to <FIG>, process <NUM> enables UE-initiated DRX MAC-CE transmission. Because a UE performing the operations of process <NUM> may transition into a low power operating mode prior to expiration of a DRX active timer, power consumption at the UE may be reduced, as compared to UEs that wait until expiration of the DRX active timer or until receipt of a network entity-initiated DRX MAC-CE.

<FIG> is a flow diagram illustrating an example process <NUM> performed by a network entity for receiving a DRX MAC-CE according to one or more aspects. Example blocks of process <NUM> will also be described with respect to a network entity <NUM> as illustrated in <FIG> is a block diagram illustrating an example of network entity <NUM> configured to receive a DRX MAC-CE according to one or more aspects. Network entity <NUM> may include base station <NUM>, network entity <NUM>, a network, or a core network, as illustrative, non-limiting examples. Network entity <NUM> includes the structure, hardware, and components as illustrated for base station <NUM> of <FIG> and <FIG>, network entity <NUM> of <FIG>, or a combination thereof. For example, network entity <NUM> may include controller <NUM>, which operates to execute logic or computer instructions stored in memory <NUM>, as well as controlling the components of network entity <NUM> that provide the features and functionality of network entity <NUM>. Network entity <NUM>, under control of controller <NUM>, transmits and receives signals via wireless radios 701a-t and antennas 234a-t. Wireless radios 701a-t include various components and hardware, as illustrated in <FIG> for network entity <NUM> (such as base station <NUM>), including modulator or demodulators 232a-t, transmit processor <NUM>, TX MIMO processor <NUM>, MIMO detector <NUM>, and receive processor <NUM>.

As shown, memory <NUM> may include receive logic <NUM>, DRX control logic <NUM>, and buffer <NUM>. Receive logic <NUM> may be configured to receive a DRX MAC-CE from a UE. DRX control logic <NUM> may be configured to determine whether to terminate a DRX active time at the UE based on buffer <NUM>. Buffer <NUM> may be configured to store data for transmission to the UE. Network entity <NUM> may receive signals from or transmit signals to one or more UEs, such as UE <NUM> of <FIG> or UE <NUM> of <FIG>.

Returning to <FIG>, a flow diagram illustrating process <NUM> is shown. In some implementations, process <NUM> may be performed by network entity <NUM> of <FIG> or network entity <NUM> of <FIG>. In some other implementations, process <NUM> may be performed by an apparatus configured for wireless communication. For example, the apparatus may include at least one processor, and a memory coupled to the processor. The processor may be configured to perform operations of process <NUM>. In some other implementations, process <NUM> may be performed or executed using a non-transitory computer-readable medium having program code recorded thereon. The program code may be program code executable by a computer for causing the computer to perform operations of process <NUM>.

As illustrated at block <NUM>, network entity <NUM> receives, at a network entity from a UE, an indication to terminate a DRX active time assigned to the UE. To illustrate, network entity <NUM> may receive the indication using wireless radios 701a-t and antennas 234a-t. To further illustrate, network entity <NUM> may execute, under control of controller <NUM>, receive logic <NUM> stored in memory <NUM>. The execution environment of receive logic <NUM> provides the functionality to receive, from a UE, an indication to terminate a DRX active time assigned to the UE.

At block <NUM>, network entity <NUM> determines whether to terminate the DRX active time based on whether a current data transmission to the UE is complete. As an example of block <NUM>, network entity <NUM> may execute, under control of controller <NUM>, DRX control logic <NUM> stored in memory <NUM>. The execution environment of DRX control logic <NUM> provides the functionality to determine whether to terminate the DRX active time based on whether a current data transmission to a UE is complete. In some implementations, the determination may be based on a status of buffer <NUM>. The status of buffer <NUM> may indicate whether or not data is stored in buffer <NUM> for transmission to the UE.

In some implementations, a determination that the current data transmission is complete is based on detecting that a buffer configured to store data for transmission to the UE is empty. For example, the determination may be based on detecting that buffer <NUM> is empty.

In some implementations, process <NUM> further includes transmitting, to the UE, a downlink communication based on a determination that the current data transmission is complete. In some such implementations, receipt of the downlink communication at the UE enables termination of the DRX active time at the UE.

In some implementations, process <NUM> also includes transmitting a downlink communication to the UE based on a determination that the current data transmission is not complete. In some such implementations, the downlink communication is configured to schedule transmission of at least a portion of the data or includes the at least a portion of the data. Additionally or alternatively, process <NUM> may further include transmitting a HARQ retransmission grant to the UE based on a determination that a transport block associated with the indication is not successfully received at the network entity.

As described with reference to <FIG>, process <NUM> enables UE-initiated DRX MAC-CE transmission. Because a network entity performing the operations of process <NUM> may enable a UE to transition into a low power operating mode prior to expiration of a DRX active timer, power consumption at the UE may be reduced, as compared to UEs that wait until expiration of the DRX active timer or until receipt of a network entity-initiated DRX MAC-CE.

It is noted that one or more blocks (or operations) described with reference to <FIG> may be combined with one or more blocks (or operations) of another figure. For example, one or more blocks (or operations) of <FIG> may be combined with one or more blocks (or operations) <FIG>. As another example, one or more blocks of <FIG> may be combined with one or more blocks (or operations) of another of <FIG> or <FIG>. Additionally, or alternatively, one or more operations described above with reference to <FIG> may be combined with one or more operations described with reference to <FIG>.

In some aspects, techniques for enabling UE-initiated DRX MAC CEs may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes or devices described elsewhere herein. In some aspects, enabling UE-initiated DRX MAC CEs may include an apparatus determining, at a UE, that a current data transmission to a network entity is complete. The apparatus may also transmit, to the network entity and based on the determination, an indication to terminate a DRX active time assigned to the UE. In some implementations, the apparatus includes a wireless device, such as a UE. In some implementations, the apparatus may include at least one processor, and a memory coupled to the processor. The processor may be configured to perform operations described herein with respect to the wireless device. In some other implementations, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon and the program code may be executable by a computer for causing the computer to perform operations described herein with reference to the wireless device. In some implementations, the apparatus may include one or more means configured to perform operations described herein.

In a first aspect, the indication includes a one-byte MAC-CE.

In a second aspect, in combination with the first aspect, the one-byte MAC-CE is included as padding in a PUSCH transmission to the network entity.

In a third aspect, in combination with one or more of the first through second aspects, the one-byte MAC-CE includes a logical channel ID associated with the one-byte MAC-CE.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, a determination that the current data transmission is complete is based on detecting that a buffer configured to store data for transmission to the network entity is empty.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the apparatus receives, from the network entity, a downlink communication based on transmitting the indication and terminates the DRX active time based on receiving the downlink communication.

In a sixth aspect, in combination with the fifth aspect, the downlink communication includes a DRX MAC-CE.

In a seventh aspect, in combination with the fifth aspect, the apparatus transitions into a low power operating mode based on terminating the DRX active time.

In an eighth aspect, alone or in combination with one or more of the first through fourth aspects, the apparatus maintains an active operating mode at the UE if a downlink communication is not received from the network entity.

In a ninth aspect, alone or in combination with one or more of the first through fourth aspects, the apparatus initiates a timer based on transmitting the indication.

In a tenth aspect, in combination with the ninth aspect, a duration of the timer is based on a processing time of the network entity associated with the indication and a reception time of a downlink communication from the network entity at the UE.

In an eleventh aspect, alone or in combination with one or more of the ninth through tenth aspects, the apparatus terminates the DRX active time based on expiration of the timer without receipt of a downlink communication from the network entity.

In a twelfth aspect, in combination with the eleventh aspect, the apparatus transitions into a low power operating mode based on terminating the DRX active time.

In a thirteenth aspect, alone or in combination with one or more of the ninth through tenth aspects, the apparatus receives, prior to expiration of the timer, a downlink communication from the network entity and maintains an active operating mode at the UE based on receipt of the downlink communication.

In a fourteenth aspect, alone or in combination with one or more of the ninth through tenth aspects, the apparatus receives, prior to expiration of the timer, a HARQ retransmission grant from the network entity and restarts the timer based on receipt of the HARQ retransmission grant. The HARQ retransmission grant is associated with a transport block that includes the indication.

In some aspects, an apparatus configured for wireless communication, such as a network entity, is configured to receive, from a UE, an indication to terminate a DRX active time assigned to the UE. The apparatus is also configured to determine whether to terminate the DRX active time based on whether a current data transmission to the UE is complete. In some implementations, the apparatus includes a wireless device, such as a network entity. In some implementations, the apparatus may include at least one processor, and a memory coupled to the processor. The processor may be configured to perform operations described herein with respect to the wireless device. In some other implementations, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon and the program code may be executable by a computer for causing the computer to perform operations described herein with reference to the wireless device. In some implementations, the apparatus may include one or more means configured to perform operations described herein.

In a fifteenth aspect, the indication includes a one-byte MAC-CE.

In a sixteenth aspect, in combination with the fifteenth aspect, the one-byte MAC-CE is included as padding in a PUSCH transmission to the network entity.

In a seventeenth aspect, alone or in combination with one or more of the fifteenth through sixteenth aspects, the one-byte MAC-CE includes a logical channel ID associated with the one-byte MAC-CE.

In an eighteenth aspect, alone or in combination with one or more of the fifteenth through seventeenth aspects, a determination that the current data transmission is complete is based on detecting that a buffer configured to store data for transmission to the UE is empty.

In a nineteenth aspect, alone or in combination with one or more of the fifteenth through eighteenth aspects, the apparatus transmits, to the UE, a downlink communication based on a determination that the current data transmission is complete.

In a twentieth aspect, in combination with the nineteenth aspect, the downlink communication includes a MAC-CE.

In a twenty-first aspect, in combination with the nineteenth aspect, receipt of the downlink communication at the UE enables termination of the DRX active time at the UE.

In a twenty-second aspect, alone or in combination with one or more of the fifteenth through eighteenth aspects, the apparatus transmits a downlink communication to the UE based on a determination that the current data transmission is not complete.

In a twenty-third aspect, in combination with the twenty-second aspect, the downlink communication is configured to schedule transmission of at least a portion of the data or includes the at least a portion of the data.

In a twenty-fourth aspect, alone or in combination with one or more of the fifteenth through eighteenth aspects, the apparatus transmits a HARQ retransmission grant to the UE based on a determination that a transport block associated with the indication is not successfully received at the network entity.

Components, the functional blocks and modules described herein with respect to <FIG> may comprise processors, electronics devices, hardware devices, electronics components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof. In addition, features discussed herein relating to <FIG> may be implemented via specialized processor circuitry, via executable instructions, or combinations thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps (e.g., the logical blocks in <FIG>) described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.

The steps of a method or algorithm described in connection with the disclosure herein may be implemented directly in hardware, in a software module executed by a processor, or in a combination of the two.

Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), hard disk, solid state disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

As used herein, including in the claims, the term "or," when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing components A, B, or C, the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.

Claim 1:
A method of wireless communication at a user equipment, UE (<NUM>), the method comprising:
determining (<NUM>) that a current data transmission to a network entity (<NUM>) is complete; and
transmitting (<NUM>), to the network entity (<NUM>) and based on the determination, an indication to terminate a discontinuous reception, DRX, active time assigned to the UE (<NUM>).