Apparatus for wireless communication

Abstract

An apparatus configured for wireless communication is provided. The apparatus comprises: at least one processor; and a memory coupled to the at least one processor, where, when executing instructions stored in the memory, the at least one processor is configured to cause the apparatus to: obtain an indication to terminate a discontinuous reception (DRX) activity time allocated to a user equipment (UE); and in response to the indication, initiating a transmission of a hybrid automatic repeat request (HARQ) retransmission grant to the UE to maintain the DRX activity time based on a current data transmission to the UE being not complete, the HARQ retransmission grant being associated with a transport block including the indication.

Description

[0001] This application is a divisional application of the invention patent application with the application date of April 13, 2021, application number 202180032444.1, and invention name "Discontinuous Reception (DRX) Media Access Control (MAC) Control Element (MAC-CE) Initiated by User Equipment (UE)".

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Patent Application No. 17 / 228,296, filed on April 12, 2021, entitled “User Equipment (UE) Initiated Discontinuous Reception (DRX) Medium Access Control (MAC) Control Element (MAC-CE)” and U.S. Provisional Patent Application No. 63 / 021,796, filed on May 8, 2020, entitled “User Equipment (UE) Initiated Discontinuous Reception (DRX) Medium Access Control (MAC-CE) Control Element (MAC-CE)”, both of which are expressly incorporated herein by reference. Technical Field

[0004] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to a user equipment (UE) initiated discontinuous reception (DRX) medium access control (MAC) control element (MAC-CE). Background Art

[0005] Wireless communication networks are widely deployed to provide various communication services, such as voice, video, packet data, messaging, broadcast, etc. These wireless networks can be multiple access networks capable of supporting multiple users by sharing available network resources. Such networks are typically multiple access networks that support communication for multiple users by sharing available network resources. An example of such a network is the Universal Terrestrial Radio Access Network (UTRAN). UTRAN is a radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), which is a third generation (3G) mobile phone technology supported by the Third Generation Partnership Project (3GPP). Examples of multiple access network formats include code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, and single carrier FDMA (SC-FDMA) networks.

[0006] A wireless communication network may include multiple base stations or Node Bs that can support communication for multiple user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to the communication link from a base station to a UE, and an uplink (or reverse link) refers to the communication link from a UE to a base station.

[0007] A base station may send data and control information to a UE on the downlink, or may receive data and control information from a UE on the uplink. On the downlink, transmissions from a base station may encounter interference due to transmissions from neighboring base stations or other radio frequency (RF) transmitters. On the uplink, transmissions from a UE may encounter interference from uplink transmissions of other UEs communicating with neighboring base stations or from other wireless RF transmitters. This interference can degrade the performance of both the downlink and uplink.

[0008] As the demand for mobile broadband access continues to increase, the likelihood of interference and congested networks increases as more UEs access long-range wireless communication networks and more short-range wireless systems are deployed in communities. Research and development continues to advance wireless technologies, not only to meet the growing demand for mobile broadband access, but also to improve and enhance the user's mobile communication experience.

[0009] In a fifth generation (5G) new radio (NR) wireless communication system, when a discontinuous reception (DRX) timer expires or when the UE receives a DRX media access control (MAC) control element (MAC-CE) from a base station, the UE may be configured to save power by entering a low power operation mode (e.g., a "sleep" mode). The base station may send a DRX MAC-CE to the UE based on a determination that there is no more data to be sent by the base station to the UE, so the UE may enter the low power operation mode. However, for at least some applications, data transmitted between the UE and the base station may be primarily sent by the UE to the base station in an uplink (UL) data session. The base station may not know when the UE has completed the UL data session, which may result in the base station being unable to send a DRX MAC-CE to the UE, thereby preventing the UE from entering a low power operation mode before the DRX timer expires and reducing power consumption, even if there is no more data to be transmitted between the UE and the base station. Summary of the invention

[0010] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an extensive review of all expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in an overview form as a preface to a more detailed description presented later.

[0011] In one aspect of the present 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 also includes sending an indication to the network entity to terminate a discontinuous reception (DRX) activity time allocated to the UE based on the determination.

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

[0013] In an additional aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes equipment for determining at a UE that a current data transmission to a network entity is complete. The apparatus also includes equipment for initiating, based on the determination, sending an indication to the network entity to terminate the DRX active time.

[0014] In an additional aspect of the present 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 also include initiating, based on the determination, sending an indication to the network entity to terminate a discontinuous reception (DRX) activity time.

[0015] In an additional aspect of the present 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 also includes determining whether to terminate the DRX active time based on whether a current data transmission to the UE is completed.

[0016] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes at least one processor and a memory coupled to the at least one processor. When executing instructions stored in the memory, the at least one processor is configured to cause the device to receive an indication from a UE to terminate a DRX active time assigned to the UE. The at least one processor is also configured to determine whether to terminate the DRX active time based on whether a current data transmission to the UE is completed.

[0017] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes a device for receiving an indication from a UE at a network entity to terminate a DRX active time assigned to the UE. The device also includes a device for determining whether to terminate the DRX active time based on whether a current data transmission to the UE is completed.

[0018] In an additional aspect of the present 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 also include determining whether to terminate the DRX active time based on whether a current data transmission to the UE is completed.

[0019] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed, the device comprising: at least one processor; and a memory coupled to the at least one processor, wherein, when executing instructions stored in the memory, the at least one processor is configured to cause the device to: obtain an indication to terminate a discontinuous reception (DRX) active time allocated to a user equipment (UE); and in response to the indication, initiate transmission of a hybrid automatic repeat request (HARQ) retransmission grant to the UE to maintain the DRX active time based on the incompleteness of current data transmission to the UE, the HARQ retransmission grant being associated with a transmission block including the indication.

[0020] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed, the device comprising: at least one processor; and a memory coupled to the at least one processor, wherein, when executing instructions stored in the memory, the at least one processor is configured to cause the device to: obtain an indication to terminate a discontinuous reception (DRX) activity time assigned to a user equipment (UE); and in response to the indication, initiate transmission of downlink communication to the UE or abandon transmission of downlink communication to the UE before a timer initiated by the UE and associated with the UE sending the indication expires, so as to maintain the DRX activity time or terminate the DRX activity time based on whether a current data transmission to the UE is completed, wherein the duration of the timer is based on a processing time associated with the indication and a time when the UE receives the downlink communication.

[0021] In an additional aspect of the present disclosure, a device configured for wireless communication is disclosed, the device comprising: at least one processor; and a memory coupled to the at least one processor, wherein, when executing instructions stored in the memory, the at least one processor is configured to cause the device to: obtain an indication to terminate a discontinuous reception (DRX) active time assigned to a user equipment (UE); and in response to the indication, abandon the transmission of downlink communications to the UE to terminate the DRX active time, the foregoing being completed based on current data transmission to the UE; and allow the UE to terminate the DRX active time.

[0022] By reading the following description of specific exemplary aspects in conjunction with the accompanying drawings, those of ordinary skill in the art will understand other aspects, features and implementations. Although features can be discussed relative to certain aspects and accompanying drawings below, all aspects can include one or more advantageous features discussed herein. In other words, although one or more aspects can be discussed as having certain advantageous features, one or more such features can also be used according to various aspects. In a similar manner, although exemplary aspects can be discussed below as equipment, systems or methods, exemplary aspects can be implemented in various devices, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar parts or features may have the same reference numerals. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral to distinguish similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral.

[0024] Figure 1 is a block diagram showing details of a wireless communication system.

[0025] Figure 2 is a block diagram illustrating an example of a base station and a UE configured according to one or more aspects of the present disclosure.

[0026] Figure 3 is a block diagram illustrating an example wireless communication system supporting user equipment (UE) initiated discontinuous reception (DRX) medium access control (MAC) control element (MAC-CE) according to one or more aspects.

[0027] Figure 4 is a flow chart illustrating an example process of UE operation for sending a DRX MAC-CE according to one or more aspects.

[0028] Figure 5 is a flow chart illustrating an example process of network entity operation for receiving a DRX MAC-CE according to one or more aspects.

[0029] Figure 6 is a block diagram illustrating an example of a UE configured to transmit a DRX MAC-CE according to one or more aspects.

[0030] Figure 7 is a block diagram illustrating an example network entity configured to receive a DRX MAC-CE according to one or more aspects. DETAILED DESCRIPTION

[0031] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Instead, the detailed description includes specific details in order to provide a thorough understanding of the subject matter of the present disclosure. It is apparent to those skilled in the art that these specific details are not required in every case, and in some cases, for clarity of presentation, known structures and components are shown in block diagram form.

[0032] The present disclosure provides systems, apparatuses, methods, and computer-readable media for implementing a discontinuous reception (DRX) media access control (MAC) control element (MAC-CE) initiated by a user equipment (UE). For example, the UE described herein may be configured to determine that a current data transmission (e.g., a transmission of one or more data packets, such as during an uplink (UL) data session or 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 optional schemes, the determination may be based on an indication from an application executed by the UE. Based on the determination, the UE may send a DRX MAC-CE to the network entity. The DRX MAC-CE may indicate that the DRX active time will terminate 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 includes a logical channel identifier (ID) associated with the UE.

[0033] In some implementations, the network entity may authorize the UE to terminate the DRX active time based on a DRX MAC-CE from the UE. For example, the network entity may send a downlink communication to the UE based on a determination that a current downlink (DL) transmission (e.g., a 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 no data is stored at the network entity for transmission to the UE (e.g., 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 to a low power operating mode (e.g., a "sleep" mode) to save power. If the UE does not receive a downlink communication from the network entity, the UE may remain in the active operating mode.

[0034] In some other implementations, the UE may determine whether to terminate the DRX active time, rather than relying on a grant from the network entity. For illustration, the UE may start a transmission timer based on sending a DRX MAC-CE to the network entity. If the transmission timer expires and the UE does not receive DL communication from the network entity, the UE may enter a low power operation mode. If the UE receives DL communication from the network entity, such as a message scheduling or including DL data or a hybrid automatic request (HARQ) retransmission grant, the UE may maintain the active operation mode to receive or send additional data.

[0035] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. In some aspects, the present disclosure provides techniques for implementing a UE-initiated DRX MAC-CE. For example, based on a determination that the UE has completed a current UL data transmission (e.g., a UL data session or a UL data burst), the UE may send a DRX MAC-CE to a network entity. Sending a DRX MAC-CE may enable the UE to enter a low-power operation mode faster than waiting for the network entity to determine that the data session is complete or waiting for the DRX activity timer to expire. Entering a low-power operation mode enables the UE to save power compared to remaining in an active operation mode. The techniques described herein may reduce power consumption of certain types of UEs that would otherwise not be able to use DRX to reduce power consumption. As an example, a UE configured to perform an extended reality (XR) application (or an augmented reality (AR) or virtual reality (VR) application) or a battery-powered camera may send a frame approximately every 33.3 milliseconds (ms). It may take approximately 10-15 ms to send each frame. If such a UE is allocated a typical 100 ms DRX Active Time, the UE may not be able to enter a low power mode of operation because a new frame needs to be sent before the DRX Active Time expires. For another example, a wearable UE such as a smart watch, fitness device, etc. may benefit from entering a low power mode of operation after a traffic burst is completed. However, the traffic burst may be driven by the UE, and the network entity may not be aware that the traffic burst has been completed and thus instruct the UE to terminate the DRX Active Timer before the DRX Active Timer expires, which may limit the amount of power savings at the UE.

[0036] The present disclosure generally relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various implementations, these techniques and apparatuses can be used in 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, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems or devices), and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0037] For example, a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0038] A TDMA network may, for example, implement a radio technology such as Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standard for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN), also known as GERAN. GERAN is the radio component of GSM / EDGE, and the network that connects base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents the component of the GSM network through which telephone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to and from subscriber handsets, which are also known as user terminals or user equipment (UE). A mobile phone operator's network may include one or more GERANs, which in the case of UMTS / GSM networks may be coupled to a Universal Terrestrial Radio Access Network (UTRAN). In addition, an operator network may also include one or more Long Term Evolution (LTE) networks, or one or more other networks. Various different network types may use different radio access technologies (RATs) and radio access networks (RANs).

[0039] OFDMA networks may implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and Global System for Mobile Communications (GSM) are part of the Universal Mobile Telecommunications System (UMTS). In particular, LTE is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents provided by an organization named "3rd Generation Partnership Project 2" (3GPP 2). These different radio technologies and standards are either known or under development. For example, 3GPP is a collaboration between groups of telecommunications associations to define globally applicable third generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP project to improve the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure may describe certain aspects with reference to LTE, 4G, or 5G NR technologies; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. In fact, one or more aspects of the present disclosure relate to wireless spectrum shared access between networks using different radio access technologies or radio air interfaces.

[0040] 5G networks take into account different deployments, different spectrums, and different services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new air interface technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage (1) with ultra-high density (e.g., about 1 M nodes / km 2 ), ultra-low complexity (e.g., ~10 s bit / s), ultra-low energy (e.g., ~10+ years battery life), and deep coverage to reach challenging locations; (2) mission-critical control including strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1 millisecond (ms)), and users with wide-area mobility or lack of mobility; and (3) enhanced mobile broadband, including extremely high capacity (e.g., ~10 Tbps / km 2 ), extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experienced rates), and deep awareness for advanced discovery and optimization.

[0041] 3G NR devices, networks, and systems can be implemented to use optimized OFDM-based waveform features. These features can include scalable parametrics and transmission time intervals (TTIs); a general, flexible framework for efficient multiplexing of services and features through dynamic, low-latency time division duplex (TDD) or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility. The scalability of parametrics in 5G NR, as well as the extension of subcarrier spacing, can effectively address the problem of operating different services on different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of FDD or TDD implementations less than 3 GHz, the subcarrier spacing may appear as 15 kHz, such as on bandwidths of 1, 5, 10, 20 MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3 GHz, the subcarrier spacing may be 30 kHz on 80 or 100 MHz bandwidths. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, the subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments sending the mmWave component with 28 GHz TDD, the subcarrier spacing may be 120 kHz over a 500 MHz bandwidth.

[0042] 5G NR's scalable parameter science facilitates scalable TTI to meet different latency and quality of service (QoS) requirements. For example, shorter TTI can be used for low latency and high reliability, while longer TTI can be used for higher spectral efficiency. Efficient multiplexing of long TTI and short TTI allows transmission to start on symbol boundaries. 5G NR also considers a self-contained integrated subframe design with uplink or downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink or downlink, which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0043] For clarity, certain aspects of the apparatus and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as an illustrative example in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0044] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate with any combination of licensed or unlicensed spectrum depending on load and availability. Therefore, it will be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications besides the specific examples provided.

[0045] Although various aspects and implementations are described in this application by way of illustration of some examples, it will be understood by those skilled in the art that additional implementations and use cases may occur in many different arrangements and scenarios. The innovations described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementation or use may be implemented by integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail devices, purchasing devices, medical devices, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically targeted at use cases or applications, a variety of applicability of the described innovations may occur. The scope of implementation 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 that integrate one or more of the described aspects. In some practical settings, the device incorporating the described aspects and features may also have to include additional components and features for implementing and practicing the claimed and described aspects. The innovations described herein may be implemented in a wide variety of implementations, including both large and small devices of varying sizes, shapes, and configurations, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, and the like.

[0046] Figure 1 1 is a block diagram illustrating details of an example wireless communication system. The wireless communication system may include a wireless network 100. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 The components appearing in may have related counterparts in other network arrangements, including, for example, cellular network arrangements and non-cellular network arrangements (eg, device-to-device or peer-to-peer or ad hoc network arrangements, etc.).

[0047] Figure 1The wireless network 100 shown includes multiple base stations 105 and other network entities. A base station may be a station that communicates with a UE and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a specific 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 the implementation of the wireless network 100 herein, the base station 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). In addition, in the implementation of the wireless network 100 herein, the base station 105 may provide wireless communication using one or more frequencies (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof) that are the same as those of an adjacent cell. In some examples, a single base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0048] 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 cells. A macro cell typically covers a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access to UEs that subscribe to services from a network provider. A small cell, such as a pico cell, typically covers a relatively small geographic area and may allow unrestricted access to UEs that subscribe to services from a network provider. A small cell, such as a femto cell, also typically covers a relatively small geographic area (e.g., a home), and in addition to unrestricted access, may also provide restricted access to UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). 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 Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations that support one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to increase coverage and capacity by utilizing 3D beamforming in both elevation and azimuth beamforming. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0049] The wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some scenarios, the network may be enabled or configured to handle dynamic switching between synchronous or asynchronous operation.

[0050] UE 115 is dispersed throughout the wireless network 100, and each UE may be fixed or mobile. It should be understood that although mobile devices are generally referred to as user equipment (UE) in the standards and specifications issued by 3GPP, those skilled in the art may additionally or otherwise refer to such devices as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, mobile phones, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle component devices or modules, or some other suitable terms. In this document, a "mobile" device or UE does not necessarily need to have the ability to move and may be stationary. Some non-limiting examples of mobile devices, such as implementations that may include one or more UE 115, include mobile phones, cellular (mobile) phones, smart phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet computers, and personal digital assistants (PDAs). The mobile device may also be an "Internet of Things" (IoT) or "Internet of Everything" (IoE) device, such as a car or other vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multicopter, a quadcopter, smart energy or security equipment, a solar panel or solar array, municipal lighting, water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammal implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, 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, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UEs 115a-115d of the illustrated implementation are examples of mobile smartphone-type devices accessing the wireless network 100. A UE may also be a machine specifically configured for connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), and the like. Figure 1 The UEs 115 e - 115 k shown in FIG. 1 are examples of various machines configured for communications accessing the wireless network 100 .

[0051] A mobile device such as UE 115 is able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the figure, the communication link (represented as a lightning) indicates the wireless transmission between the UE and the serving base station, which is the base station designated to serve the UE on the downlink or uplink, or the desired transmission between the base stations, and the backhaul transmission between the base stations. In some scenarios, the UE can operate as a base station or other network node. The backhaul communication between the base stations of the wireless network 100 can be carried out using wired or wireless communication links.

[0052] In operation of the wireless network 100, base stations 105a-105c use 3D beamforming and cooperative spatial techniques (such as coordinated multi-point (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as yellow alerts or gray alerts.

[0053] The implemented wireless network 100 supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which is a drone. The redundant communication links with UE 115e include links from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices, such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device), can communicate directly with base stations such as small cell base station 105f and macro base station 105e through the wireless network 100, or communicate in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f transmitting temperature measurement information to smart meter UE 115g, which then reports the information to the network through small cell base station 105f. The wireless network 100 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 - 115k communicating with a macro base station 105e .

[0054] Figure 2 A block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects is shown, and the base station 105 and the UE 115 may be Figure 1 For a restricted association scenario (as described above), the base station 105 may be any base station and UE in Figure 1 The small cell base station 105f in the example, and the UE 115 may be a UE 115c or 115d operating in the service area of ​​the base station 105f, which will be included in the accessible UE list of the small cell base station 105f in order to access the small cell base station 105f. The base station 105 may also be some other type of base station. Figure 2 As shown, the base station 105 may be equipped with antennas 234a through 234t, and the UE 115 may be equipped with antennas 252a through 252r, to facilitate wireless communications.

[0055] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller 240 (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. In addition, the transmit processor 220 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, or reference symbols (if applicable), and may provide output symbol streams to modulators (MODs) 232a to 232t. For example, the spatial processing performed on data symbols, control symbols, or reference symbols may include precoding. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0056] At the UE 115, antennas 252a to 252r may receive downlink signals from the base station 105 and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to a data sink 260, and provide decoded control information to a controller 280 (e.g., a processor).

[0057] On the uplink, at the UE 115, the transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from the controller 280 (e.g., for a physical uplink control channel (PUCCH)). In addition, the transmit processor 264 may generate reference symbols for a reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266 (if applicable), further processed by the modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 115. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller 240.

[0058] The controllers 240 and 280 may direct the operations at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105 or the controller 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes of the techniques described herein, such as performing or directing Figure 4 and Figure 5 The operations shown in , or other processes of the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0059] In some cases, the UE 115 and the base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 105 may traditionally perform a media sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-transmitting (LBT) process such as a clear channel assessment (CCA) before communication to determine whether the shared channel is available. In some implementations, the CCA may include an energy detection process to determine whether there are any other active transmissions. For example, the device may infer that a change in the received signal strength indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, a signal power concentrated in a specific bandwidth and exceeding a predetermined noise floor may indicate other wireless transmitters. CCA may also include detection of a specific sequence indicating channel usage. For example, other devices may send a specific preamble before sending a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback of its own transmitted packets as a proxy for collisions.

[0060] The present disclosure provides systems, devices, methods, and computer-readable media for implementing a UE-initiated discontinuous reception (DRX) media access control (MAC) control element (MAC-CE). For example, the UE described herein may be configured to determine that a current data transmission (e.g., a transmission of one or more data packets, such as during an uplink (UL) data session or 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 the determination, the UE may send a DRX MAC-CE to the network entity. The DRX MAC-CE may indicate that the DRX active time will terminate 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 includes a logical channel identifier (ID) associated with the UE.

[0061] In some implementations, the network entity may authorize the UE to terminate the DRX active time based on a DRX MAC-CE from the UE. For example, the network entity may send a downlink communication to the UE based on a determination that a current downlink (DL) transmission (e.g., a 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 no data is stored at the network entity for transmission to the UE (e.g., 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 to a low power operating mode (e.g., a "sleep" mode) to save power. If the UE does not receive a downlink communication from the network entity, the UE may remain in the active operating mode.

[0062] In some other implementations, the UE may determine whether to terminate the DRX active time, rather than relying on a grant from the network entity. For illustration, the UE may start a transmission timer based on sending a DRX MAC-CE to the network entity. If the transmission timer expires and the UE does not receive DL communication from the network entity, the UE may enter a low power operation mode. If the UE receives DL communication from the network entity, such as a message scheduling or including DL data or a hybrid automatic request (HARQ) retransmission grant, the UE may maintain the active operation mode to receive or send additional data.

[0063] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. In some aspects, the present disclosure provides techniques for implementing a UE-initiated DRX MAC-CE. For example, based on a determination that the UE has completed a current UL data transmission (e.g., a UL data session or a UL data burst), the UE may send a DRX MAC-CE to a network entity. Sending a DRX MAC-CE may enable the UE to enter a low-power operation mode faster than waiting for the network entity to determine that the data session is complete or waiting for the DRX activity timer to expire. Entering a low-power operation mode enables the UE to save power compared to remaining in an active operation mode. The techniques described herein may reduce power consumption of certain types of UEs that would otherwise not be able to use DRX to reduce power consumption. As an example, a UE configured to perform an extended reality (XR) application (or an augmented reality (AR) or virtual reality (VR) application) or a battery-powered camera may send a frame approximately every 33.3 milliseconds (ms). It may take approximately 10-15 ms to send each frame. If such a UE is allocated a typical 100 ms DRX Active Time, the UE may not be able to enter a low power mode of operation because a new frame needs to be sent before the DRX Active Time expires. As another example, wearable UEs such as smart watches, fitness devices, etc. may benefit from entering a low power mode of operation after a traffic burst is completed. However, the traffic burst may be driven by the UE, and the network entity may not be aware that the traffic burst has been completed in order to instruct the UE to terminate the DRX Active Timer before the DRX Active Timer expires, which may limit the amount of power savings at the UE.

[0064] Figure 3 is a block diagram of an example wireless communication system 300 that supports UE-initiated DRX MAC-CE according to one or more aspects. In some implementations, the wireless communication system 300 can implement aspects of the wireless network 100. The wireless communication system 300 includes a UE 115 and a network entity 350. As an illustrative and non-limiting example, the network entity 350 may include or correspond to a base station, such as a base station 105, a network, a network core, or other network equipment. Although one UE 115 and one network entity 350 are shown, in some other implementations, the wireless communication system 300 may generally include multiple UEs 115 and may include more than one network entity 350.

[0065] The UE 115 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include a processor 302, a memory 304, a buffer 306, an optional DRX activity timer 308, an optional transmission timer 310, a transmitter 312, and a receiver 314. The processor 302 may be configured to execute instructions stored in the memory 304 to perform the operations described herein. In some implementations, the processor 302 includes or corresponds to the controller 280, and the memory 304 includes or corresponds to the memory 282.

[0066] The buffer 306 may be configured to store data for transmission to the network entity 350. For example, the buffer 306 may be configured to store one or more data packets scheduled to be sent to the network entity 350 as part of a UL data session or data burst. The DRX activity timer 308 may be configured to signal the duration of the DRX active time at the UE 115. In some implementations, the DRX activity timer 308 has a duration of 100 ms. In other implementations, the DRX activity timer 308 has a different duration, such as 80 ms, 60 ms, or 40 ms, as non-limiting examples. The transmission timer 310 may be configured to signal the duration of the time period between the UE 115 sending the DRX MAC CE and the UE 115 terminating the DRX active time at the UE 115. In some implementations, the transmission timer 310 has a duration of approximately 4 ms.

[0067] The transmitter 312 is configured to send reference signals, control information, and data to one or more other devices, and the receiver 314 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, the transmitter 312 can send signaling, control information, and data, and the receiver 314 can receive signaling, control information, and data via a network, such as a wired network, a wireless network, or a combination thereof. For example, the UE 115 can be configured to send 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, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed that allows two or more electronic devices to communicate therein. In some implementations, the transmitter 312 and the receiver 314 can be integrated in a transceiver. Additionally or alternatively, the transmitter 312, the receiver 314, or both can include and correspond to the reference Figure 2 One or more components of UE 115 are described.

[0068] The network entity 350 may include various components (such as structures, hardware components) for performing one or more functions described herein. For example, these components may include a processor 352, a memory 354, a transmitter 356, a receiver 358, and a buffer 360. The processor 352 may be configured to execute instructions stored in the memory 354 to perform the operations described herein. In some implementations, the processor 352 includes or corresponds to the controller 240, and the memory 354 includes or corresponds to the memory 242.

[0069] The transmitter 356 is configured to send reference signals, synchronization signals, control information, and data to one or more other devices, and the receiver 358 is configured to receive reference signals, control information, and data from one or more other devices. For example, the transmitter 356 can send signaling, control information, and data, and the receiver 358 can receive signaling, control information, and data via a network, such as a wired network, a wireless network, or a combination thereof. For example, the network entity 350 can be configured to send or receive data via a direct device-to-device connection, a LAN, a WAN, a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed that allows two or more electronic devices to communicate therein. In some implementations, the transmitter 356 and the receiver 358 can be integrated into a transceiver. Additionally or alternatively, the transmitter 356, the receiver 358, or both can include and correspond to a reference Figure 2 One or more components of base station 105 are described.

[0070] Buffer 360 may be configured to store data for transmission to UE 115. For example, buffer 360 may be configured to store one or more data packets scheduled to be sent to UE 115 as part of a DL data session or data burst.

[0071] In some implementations, the wireless communication system 300 implements a 5G New Radio (NR) network. For example, the wireless communication system 300 may include a plurality of 5G-capable UEs 115 and a plurality of 5G-capable network entities 350, such as UEs and network entities configured to operate according to a 5G NR network protocol, such as defined by 3GPP.

[0072] During operation of the wireless communication system 300, the UE 115 and the network entity 350 may communicate control information and data via one or more wireless networks. For example, the UE 115 may send one or more UL data packets to the network entity 350 and may receive one or more DL data packets from the network entity 350. The control information or data may be communicated as part of a data session between the UE 115 and the network entity 350.

[0073] In addition, at the initiation of a data session, or at a scheduled time to send UL data or receive DL data at the UE 115, the UE 115 may start a DRX active timer 308. The DRX active timer 308 may track the duration of the DRX active time at the UE 115. During the DRX active time, the UE 115 may be configured to maintain (e.g., remain) in an active operating mode. For example, the UE 115 may maintain power to the processor 302, the transmitter 312, the receiver 314, 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 other channels. By remaining in the active operating mode and monitoring the PDCCH, PDSCH, or other channels, the UE 115 is able to receive control information or data from the network entity 350.

[0074] At some time before the DRX activity timer 308 expires, the UE 115 may determine that the current data transmission to the network entity 350 has been completed. For example, if the UE 115 determines that there is no more data to be sent to the network entity 350 in the near future (e.g., within a certain time period), the data session or UL data burst may be completed. The determination may be based on the state of the buffer 306. For example, the UE 115 may determine that the current data transmission (e.g., data session or UL data burst) is completed based on determining that the buffer 306 is empty (e.g., no data is stored in the buffer 306 for transmission to the network entity 350). Alternatively, the UE 115 may determine that the current data transmission is not completed based on determining that the buffer 306 stores at least one data packet to be transmitted to the network entity 350. Although described as being based on the state of the buffer 306, in some other implementations, the UE 115 may determine that the current data transmission is complete based on other information, such as an indication from an application layer of an application executed by the UE 115. For example, an application requesting data to be transmitted to the network entity 350 may signal to the UE 115 that there is no more data to be transmitted, at least for a certain period of time.

[0075] Based on the determination, the UE 115 may generate an indication to terminate the DRX active time assigned to the UE 115. In some implementations, the indication includes or corresponds to a DRX MAC-CE 372. For example, the UE 115 may generate a MAC structure including control information indicating that the UE 115 requests to terminate the DRX active time. In some implementations, the DRX MAC-CE 372 may be a one-byte MAC-CE. In other implementations, the DRX MAC-CE 372 may have a different size, such as greater than one byte or less than one byte. In some implementations, the DRX MAC-CE 372 includes only a logical channel identifier (ID) 374 associated with the DRX MAC-CE 372 (e.g., without any information other than the logical channel ID 374). For example, a header of the DRX MAC-CE 372 may include the logical channel ID 374. In some other implementations, the DRX MAC-CE 372 includes additional information as well as the logical channel ID 374.

[0076] The UE 115 may send the DRX MAC-CE 372 to the network entity 350. For example, the UE 115 may send the DRX MAC-CE 372 to the network entity 350 alone or as part of a message. In some implementations, the DRX MAC-CE 372 is included in a physical uplink shared channel (PUSCH) transmission 370 to the network entity 350. In some such implementations, the DRX MAC-CE 372 may be included in the PUSCH transmission 370 as padding. For example, the DRX MAC-CE 372 may replace one or more bits reserved as padding within the PUSCH transmission 370. The reservation of the padding may be based on a wireless communication standard specification, such as a 3GPP wireless communication standard specification.

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

[0078] Based on the determination to terminate the DRX active time at the UE 115, the network entity 350 may generate a downlink communication 376 and send it to the UE 115. In some implementations, the downlink communication 376 includes or corresponds to a DRX MAC-CE. In some such implementations, the downlink communication 376 is a one-byte MAC-CE that includes only a logical channel ID associated with the downlink communication 376. In some other implementations, the downlink communication 376 has a different size or includes other information. The network entity 350 may send the downlink communication 376 to the UE 115 individually or in a message. For example, the downlink communication 376 may be included in a PDCCH transmission to the UE 115. In some implementations, the downlink communication 376 may be included in bits reserved as padding for the PDCCH transmission.

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

[0080] Based on the determination that the DRX active time is not terminated at the UE 115, the network entity 350 may not send any DRX MAC-CE to the UE 115. In contrast, the network entity 350 may send a DL communication 378 to the UE 115 based on a determination that the current DL transmission is not completed (e.g., as a non-limiting example, determining that data is stored in the buffer 360 or an indication has been received from the application). The DL communication 378 may be configured to schedule the transmission of at least a portion of the data, or may include at least a portion of the data. If a DRX MAC-CE is not received from the network entity 350, such as a downlink communication 376, the UE 115 may maintain (e.g., remain) in an active operating mode. Therefore, the UE 115 may monitor the PDCCH or PDSCH for the DL communication 378 from the network entity 350. In some implementations, the UE 115 may restart the DRX active timer 308 based on receiving the DL communication 378 from the network entity 350.

[0081] In some other implementations, the UE 115 is configured to terminate the DRX active period without an explicit authorization from the network entity 350, such as receiving a DRX MAC-CE 372. In some such implementations, the UE 115 may start a transmission timer 310 based on sending the DRX MAC-CE 372 to the network entity 350. The duration of the transmission timer 310 may be based on a processing timer of the network entity 350 associated with the DRX MAC-CE 372 and a reception time of DL communications from the network entity 350 at the UE 115. For example, the duration of the transmission timer 310 may be at least a combination of the amount of time it takes the network entity 350 to process the DRX MAC-CE 372 and the amount of time required for the UE 115 to receive a DL allocation of additional data from the network entity 350. In some implementations, the duration of the transmission timer 310 is approximately 4 ms. For example, the amount of time it takes the network entity 350 to process the DRX MAC-CE 372 is approximately 3 ms and the amount of time it takes to receive DL communications from the network entity 350 is approximately 1 ms. In other implementations, the duration of the transmission timer 310 is less than 4 ms or greater than 4 ms.

[0082] The UE 115 may terminate the DRX active time based on the expiration of the transmission timer 310 without receiving DL communications from the network entity 350. For example, if the UE 115 does not receive a DL allocation of additional data from the network entity 350 before the transmission timer 310 expires, the UE 115 may terminate the DRX active time. In some implementations, terminating the DRX active time includes terminating (e.g., stopping) the DRX active timer 308. Based on terminating the DRX active time, the UE 115 may transition to a low power operating mode. The UE 115 may remain in the low power operating mode for the remainder of the current DRX cycle. During operation in the low power operating mode, the UE 115 may not monitor one or more channels of DL communications from the network entity 350, such as the PDCCH or the PDSCH.

[0083] If the network entity 350 determines that the UE 115 should not terminate the DRX active time, the network entity 350 may generate a DL communication 378 and send the DL communication 378 to the UE 115. For example, the network entity 350 may send the DL communication 378 based on the buffer 360 being not empty (e.g., storing data), or based on an indication from the application layer. The DL communication 378 may be configured to schedule the transmission of at least a portion of the data, or may include at least a portion of the data. The UE 115 may receive the DL communication 378 from the network entity 350, and may maintain (e.g., remain) in an active operating mode based on the receipt of the DL communication 378. The UE 115 may then monitor the PDCCH or PDSCH for additional DL communications from the network entity 350. In some implementations, the UE 115 may restart the DRX active timer 308 based on receiving the DL communication 378 from the network entity 350.

[0084] Additionally or alternatively, the network entity 350 may determine that a transport block (TB) associated with the DRX MAC-CE 372 was not successfully received at the network entity 350. For example, the TB may have too many errors to be decoded or may not be received by the network entity 350. Based on the determination, the network entity 350 may generate a hybrid automatic repeat request (HARQ) retransmission grant 380 and send it to the UE 115. The HARQ retransmission grant 380 may indicate the TB associated with the DRX MAC-CE 372 and may request a retransmission of the TB. The UE 115 may receive the HARQ retransmission grant 380, and based on receiving the HARQ retransmission grant 380 before the transmission timer 310 expires, the UE 115 may restart the transmission timer 310. For example, the UE 115 may retransmit the TB and the DRX MAC-CE 372 to the network entity 350, and may restart the transmission timer 310 when retransmitting the DRX MAC-CE 372.

[0085] As reference Figure 3As described, the present disclosure provides a technique for implementing a UE-initiated DRX MAC-CE. For example, the UE 115 may send a DRX MAC-CE 372 to the network entity 350 based on a determination that the UE 115 has no more data to send to the network entity 350 at least within a certain period of time. Because the DRX MAC-CE 372 may be a one-byte MAC-CE that includes only a logical channel ID 374, the DRX MAC-CE 372 may be sent quickly and has a lower overhead relative to the wireless communication system 300. In addition, because the UE 115 may transition to a low power operation mode based on the expiration of a reception or transmission timer 310 of the DRX MAC-CE 372, the UE 115 may transition to a low power operation mode before the DRX activity timer 308 expires, which reduces power consumption at the UE 115. Enabling UE-initiated requests to terminate DRX active time can reduce power consumption for certain types of UEs, such as UEs configured to execute XR, AR, or VR applications, battery-powered cameras, or wearable devices (e.g., smart watches, fitness devices, etc.), which would otherwise incur greater power consumption using typical DRX techniques.

[0086] Reference Figure 4 , a flow chart of an example process 400 for sending a DRX MAC-CE performed by a UE according to one or more aspects is shown. Figure 6 UE 600 is shown to describe example operations (also referred to as “blocks”) of process 400 . Figure 6 is a block diagram illustrating an example UE 600 configured to send a DRX MAC-CE according to one or more aspects. The UE 600 includes Figure 2 or Figure 3 115 of the present invention. For example, the UE 600 includes a controller 280 for executing logic or computer instructions stored in a memory 282 and controlling components of the UE 600 that provide the features and functions of the UE 600. Under the control of the controller 280, the UE 600 sends and receives signals via wireless radios 601a-r and antennas 252a-r. The wireless radios 601a-r include various components and hardware, such as Figure 2 As shown for UE 115, modulators or demodulators 254a-r, a MIMO detector 256, a receive processor 258, a transmit processor 264, and a TX MIMO processor 266 are included.

[0087] As shown, the memory 282 may include a buffer 602, a DRX control logic 603, a transmission logic 604, and a DRX activity timer 605. The buffer 602 may be configured to store data for transmission to a network entity. The DRX control logic 603 may be configured to control the DRX activity time at the UE 600, such as by terminating the DRX activity time. The transmission logic 604 may be configured to enable transmission of signaling or messages to a base station. The DRX activity timer 605 may be configured to track the DRX activity time at the UE 600. The UE 600 may receive signals from or send signals to one or more network entities, such as Figure 1-Figure 2 Base station 105, Figure 3 The network entity 350, core network, core network equipment or Figure 7 The network entities shown.

[0088] Reference Figure 4 , a flow chart illustrating process 400 is shown. In some implementations, process 400 may be performed by UE 115 or UE 600. In some other implementations, process 400 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 the operations of process 400. In some other implementations, process 400 may be performed or run using a non-transitory computer-readable medium having program code recorded thereon. The program code may be a program code executable by a computer for causing the computer to perform the operations of process 400.

[0089] As shown in block 402, UE 600 determines that the current data transmission to the network entity is completed. As an example of block 402, UE 600 can execute DRX control logic 603 stored in memory 282 under the control of controller 280. The operating environment of DRX control logic 603 provides the function of determining that the current data transmission to the network entity is completed. In some implementations, this determination can be based on determining that buffer 602 is empty.

[0090] At block 404, the UE 600 sends an indication to the network entity to terminate the DRX active time assigned to the UE based on the determination. For illustration, the UE 600 may use the wireless radio 601a-r and the antenna 252a-r to send the indication. For further illustration, the UE 600 may execute a transmission logic 604 stored in the memory 282 under the control of the controller 280. The operating environment of the transmission logic 604 provides the functionality of sending an indication to the network entity to terminate the DRX active time assigned to the UE 600. Terminating the DRX active time may include terminating the DRX active timer 605.

[0091] 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 a network entity. Additionally or alternatively, the one-byte MAC-CE may include a logical channel ID associated with the one-byte MAC-CE.

[0092] In some implementations, the determination that the current data transmission is complete is based on detecting that a buffer configured to store data to be transmitted to the network entity is empty. For example, the determination can be based on detecting that the buffer 602 is empty (eg, does not contain data to be transmitted to the network entity).

[0093] In some implementations, process 400 also includes receiving a downlink communication from a network entity based on sending 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 400 may also include transitioning to a low power operating mode based on terminating the DRX active time.

[0094] In some implementations, process 400 further includes maintaining an active mode of operation at the UE if no downlink communication is received from the network entity. In some such implementations, the downlink communication is a DRX MAC-CE.

[0095] In some implementations, process 400 also includes starting a timer based on sending the indication. In some such implementations, the 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 optionally, process 400 also includes terminating the DRX active time based on the expiration of the timer in the absence of receiving the downlink communication from the network entity. In some such implementations, process 400 also includes switching to a low power operation mode based on terminating the DRX active time. Alternatively, process 400 may also include receiving a downlink communication from the network entity before the expiration of the timer, and maintaining the active operation mode at the UE based on the reception of the downlink communication. Alternatively, process 400 may also include receiving a HARQ retransmission grant from the network entity before the expiration of the timer, and restarting the timer based on the reception of the HARQ retransmission grant. The HARQ retransmission grant may be associated with a transport block including the indication.

[0096] As reference Figure 4As described above, process 400 implements UE-initiated DRX MAC-CE transmission. Because the UE performing the operations of process 400 can transition to a low power operation mode before the DRX activity timer expires, power consumption at the UE can be reduced compared to a UE that waits until the DRX activity timer expires or until a DRX MAC-CE initiated by a network entity is received.

[0097] Figure 5 1 is a flow chart illustrating an example process 500 performed by a network entity for receiving a DRX MAC-CE according to one or more aspects. Figure 7 Network entity 700 is shown to describe example blocks of process 500 . Figure 7 1 is a block diagram illustrating an example of a network entity 700 configured to receive a DRX MAC-CE according to one or more aspects. As illustrative and non-limiting examples, the network entity 700 may include a base station 105, a network entity 350, a network, or a core network. The network entity 700 includes Figure 1 and Figure 2 Base station 105, Figure 3 The structure, hardware, and components of the network entity 350 or a combination thereof are shown. For example, the network entity 700 may include a controller 240 for executing logic or computer instructions stored in a memory 242 and controlling components of the network entity 700 that provide the features and functions of the network entity 700. Under the control of the controller 240, the network entity 700 sends and receives signals via wireless radios 701a-t and antennas 234a-t. The wireless radios 701a-t include various components and hardware, such as Figure 2 1 , shown for a network entity 350 , such as a base station 105 , including modulators or demodulators 232 a - t , a transmit processor 220 , a TX MIMO processor 230 , a MIMO detector 236 , and a receive processor 238 .

[0098] As shown, the memory 242 may include a receiving logic 702, a DRX control logic 703, and a buffer 704. The receiving logic 702 may be configured to receive a DRX MAC-CE from a UE. The DRX control logic 703 may be configured to determine whether to terminate the DRX active time at the UE based on the buffer 704. The buffer 704 may be configured to store data for transmission to the UE. The network entity 700 may receive data from one or more UEs (e.g., Figure 1-Figure 3 UE 115 or Figure 6 UE 600) receives signals or sends signals to it.

[0099] Back to Figure 5 , a flow chart illustrating process 500 is shown. In some implementations, process 500 can be performed by Figure 3 Network entity 350 or Figure 7 The process 500 may be performed by a network entity 700 of the present invention. In some other implementations, the process 500 may be performed by a device configured for wireless communication. For example, the device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations of the process 500. In some other implementations, a non-transitory computer-readable medium having program code recorded thereon may be used to perform or run the process 500. The program code may be a program code executable by a computer for causing the computer to perform the operations of the process 500.

[0100] As shown in block 502, the network entity 700 receives an indication at the network entity from the UE to terminate the DRX active time assigned to the UE. For illustration, the network entity 700 may receive the indication using the wireless radio devices 701a-t and the antennas 234a-t. For further illustration, the network entity 700 may execute the receiving logic 702 stored in the memory 242 under the control of the controller 240. The operating environment of the receiving logic 702 provides the functionality of receiving from the UE an indication to terminate the DRX active time assigned to the UE.

[0101] In block 504, the network entity 700 determines whether to terminate the DRX active time based on whether the current data transmission to the UE is completed. As an example of block 504, the network entity 700 may execute the DRX control logic 703 stored in the memory 242 under the control of the controller 240. The operating environment of the DRX control logic 703 provides a function of determining whether to terminate the DRX active time based on whether the current data transmission to the UE is completed. In some implementations, the determination may be based on the state of the buffer 704. The state of the buffer 704 may indicate whether data is stored in the buffer 704 for transmission to the UE.

[0102] 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 a network entity. Additionally or alternatively, the one-byte MAC-CE may include a logical channel ID associated with the one-byte MAC-CE.

[0103] In some implementations, the determination that the current data transmission is complete is based on detecting that a buffer configured to store data to be transmitted to the UE is empty. For example, the determination can be based on detecting that the buffer 704 is empty.

[0104] In some implementations, process 500 also includes sending a downlink communication to the UE based on the determination that the current data transmission is complete. In some such implementations, receiving the downlink communication at the UE enables termination of the DRX active time at the UE.

[0105] In some implementations, process 500 further includes sending 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 at least a portion of the data. Additionally or alternatively, process 500 may further include sending a HARQ retransmission grant to the UE based on a determination that a transport block associated with the indication was not successfully received at the network entity.

[0106] As reference Figure 5 As described above, process 500 implements UE-initiated DRX MAC-CE transmission. Because the network entity performing the operations of process 500 can enable the UE to transition to a low power operation mode before the DRX activity timer expires, power consumption at the UE can be reduced compared to the UE waiting until the DRX activity timer expires or until a DRX MAC-CE initiated by the network entity is received.

[0107] Note, refer to Figure 4 and Figure 5 One or more blocks (or operations) described herein may be combined with one or more blocks (or operations) of another figure. Figure 4 One or more boxes (or operations) can be combined with Figure 5 As another example, Figure 4 or Figure 5 One or more boxes can be connected with Figure 2 or Figure 3 Additionally or alternatively, the above reference Figure 1-Figure 6 One or more of the operations described may be combined with reference to Figure 7 Describes a combination of one or more operations.

[0108] In some aspects, the technology for implementing the UE-initiated DRX MAC CE may include additional aspects, such as any single aspect described below or any combination of these aspects, or in combination with one or more other processes or devices described elsewhere herein. In some aspects, enabling the UE-initiated DRX MAC CE may include a device: determining at the UE that the current data transmission to the network entity is completed. The device may also send an indication to the network entity to terminate the DRX activity time assigned to the UE based on the determination. In some implementations, the device includes a wireless device, such as a UE. In some implementations, the device may include at least one processor and a memory coupled to the processor. The processor may be configured to perform the operations described herein for the wireless device. In some other implementations, the device may include a non-transitory computer-readable medium having a program code recorded thereon, and the program code may be executed by a computer to cause the computer to perform the operations described herein with reference to the wireless device. In some implementations, the device may include one or more equipment configured to perform the operations described herein.

[0109] In a first aspect, the indication comprises a one-byte MAC-CE.

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

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

[0112] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the current data transmission is determined to be complete based on detecting that a buffer configured to store data to be transmitted to the network entity is empty.

[0113] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the apparatus receives downlink communications from a network entity based on sending an indication, and terminates the DRX active time based on receiving the downlink communications.

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

[0115] In a seventh aspect, in combination with the fifth aspect, the apparatus switches to a low power operation mode based on terminating the DRX activity time.

[0116] In an eighth aspect, alone or in combination with one or more of the first to fourth aspects, the apparatus maintains an active mode of operation at the UE if no downlink communication is received from the network entity.

[0117] In a ninth aspect, alone or in combination with one or more of the first to fourth aspects, the apparatus starts a timer based on sending an indication.

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

[0119] In an eleventh aspect, alone or in combination with one or more of the ninth to tenth aspects, the apparatus terminates the DRX active time based on expiration of a timer when no downlink communication is received from the network entity.

[0120] In a twelfth aspect, in combination with the eleventh aspect, the apparatus transitions to a low power operation mode based on terminating the DRX active time.

[0121] In a thirteenth aspect, alone or in combination with one or more of the ninth to tenth aspects, the apparatus receives downlink communications from a network entity before expiration of a timer, and maintains an active operating mode at the UE based on reception of the downlink communications.

[0122] In a fourteenth aspect, alone or in combination with one or more of the ninth to tenth aspects, the apparatus receives a HARQ retransmission grant from a network entity before the timer expires, and restarts the timer based on the receipt of the HARQ retransmission grant. The HARQ retransmission grant is associated with a transport block including the indication.

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

[0124] In a fifteenth aspect, the indication comprises a one-byte MAC-CE.

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

[0126] In a seventeenth aspect, alone or in combination with one or more of the fifteenth to sixteenth aspects, the one-byte MAC-CE comprises a logical channel ID associated with the one-byte MAC-CE.

[0127] In an eighteenth aspect, alone or in combination with one or more of the fifteenth to seventeenth aspects, the current data transmission is determined to be completed based on detecting that a buffer configured to store data to be transmitted to the UE is empty.

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

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

[0130] In a twenty-first aspect, in combination with the nineteenth aspect, receiving downlink communications at the UE enables termination of the DRX active time at the UE.

[0131] In a twenty-second aspect, either alone or in combination with one or more of the fifteenth to eighteenth aspects, the apparatus sends a downlink communication to a UE based on a determination that a current data transmission is incomplete.

[0132] 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 include at least a portion of the data.

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

[0134] Those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0135] This article refers to Figure 4 and Figure 5 The components, functional blocks and modules described may include processors, electronic devices, hardware devices, electronic components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof. Figure 1-Figure 7 The related features may be implemented by dedicated processor circuits, by executable instructions, or a combination thereof.

[0136] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps (e.g., Figure 5 to Figure 6 The logic blocks in the system (such as the logic blocks in the system) can be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above according to their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints on the entire system. A skilled person can implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein are merely examples, and the components, methods, or interactions of various aspects of the present disclosure may be combined or performed in a manner different from that shown and described herein.

[0137] The various illustrative logical blocks, modules, and circuits described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0138] The steps of the method or algorithm described in conjunction with the disclosure herein can be implemented directly in hardware, a software module executed by a processor, or a combination of the two. The software module can reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium can be integrated into the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. Alternatively, the processor and the storage medium can reside in a user terminal as discrete components.

[0139] In one or more exemplary designs, the functions described may be implemented with hardware, software, firmware, or any combination thereof. If implemented with software, these functions may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Computer-readable storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. As an example and not a limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to carry or store a desired program code device in the form of an instruction or data structure and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. In addition, a connection may be appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL) is used to transmit software from a website, server, or other remote source, the coaxial cable, fiber optic cable, twisted pair, or DSL are all included in the definition of the medium. Disc and disk, as used herein, include laser discs (CDs), laser disks, optical disks, digital versatile disks (DVDs), hard disks, solid-state disks and Blu-ray discs, where discs usually reproduce data magnetically, while disks reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0140] 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 may be used alone, or any combination of two or more of the listed items may be used. For example, if a composition is described as comprising ingredients A, B, or C, the composition may comprise only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Furthermore, as used herein, including in the claims, "or" used in a list of items beginning with "at least one of" means a disjunctive list, such that, for example, a list of "at least one of A, B, or C" means any one of A or B or C or AB or AC or BC or ABC (i.e., A and B and C), or any combination thereof.

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

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: at least one processor; and a memory coupled to the at least one processor, Wherein, when executing the instructions stored in the memory, the at least one processor is configured to cause the apparatus to: Obtaining an indication of terminating a discontinuous reception (DRX) activity time allocated to a user equipment (UE); as well as In response to the indication, initiating transmission of a hybrid automatic repeat request (HARQ) retransmission grant to the UE to maintain the DRX active time based on the current data transmission to the UE being incomplete, the HARQ retransmission grant being associated with the transport block including the indication.

2. The device according to claim 1, wherein: The indication comprises a Medium Access Control MAC Control Element MAC-CE, the MAC-CE being included as padding in a Physical Uplink Shared Channel PUSCH transmission, or a Logical Channel Identifier ID associated with the MAC-CE.

3. The device according to claim 1, wherein: The sending of the HARQ retransmission grant to the UE is initiated before expiration of a timer initiated by the UE and associated with the UE sending the indication.

4. The device according to claim 1, wherein: The HARQ retransmission grant is initiated for transmission based on a transport block associated with the indication being unsuccessfully received.

5. The apparatus of claim 1 , further comprising a buffer configured to store data for transmission to the UE, wherein: The HARQ retransmission grant is initiated for transmission based on the buffer being empty.

6. The apparatus of claim 1, further comprising a transceiver configured to receive the indication, wherein: The HARQ retransmission grant is initiated for transmission via the transceiver, and further wherein the apparatus is configured as a network entity.

7. An apparatus configured for wireless communication, the apparatus comprising: at least one processor; and a memory coupled to the at least one processor, Wherein, when executing the instructions stored in the memory, the at least one processor is configured to cause the apparatus to: Obtaining an indication of terminating a discontinuous reception (DRX) activity time allocated to a user equipment (UE); and In response to the indication, before the expiration of a timer initiated by the UE and associated with the UE sending the indication, initiate the transmission of downlink communication to the UE or abandon the transmission of downlink communication to the UE, so as to maintain the DRX active time or terminate the DRX active time based on whether the current data transmission to the UE is completed, wherein the duration of the timer is based on the processing time associated with the indication and the time when the UE receives the downlink communication.

8. The device according to claim 7, wherein: The indication comprises a Medium Access Control MAC Control Element MAC-CE.

9. The device according to claim 7, wherein: When executing the instructions, the at least one processor is configured to: When the current data transmission is completed, the UE is authorized to terminate the DRX active time.

10. The device according to claim 7, wherein: When executing the instructions, the at least one processor is further configured to cause the apparatus to: Based on expiration of the timer and no downlink communication to the UE, the UE is allowed to terminate the DRX active time.

11. The device according to claim 7, wherein: When executing the instructions, the at least one processor is further configured to cause the apparatus to: An active mode of operation with respect to the UE is terminated.

12. The device according to claim 7, wherein: When executing the instructions, the at least one processor is configured to: When the current data transmission is not completed, transmission of the downlink communication to the UE is initiated to maintain the DRX active time.

13. The device according to claim 12, wherein: The downlink communication includes a hybrid automatic repeat request (HARQ) retransmission grant to the UE because a transport block associated with the indication was not successfully received at the device.

14. The apparatus of claim 7, further comprising a transceiver configured to receive the indication, wherein: The device is configured as a network entity.

15. An apparatus configured for wireless communication, the apparatus comprising: at least one processor; and a memory coupled to at least one processor, Wherein, when executing the instructions stored in the memory, the at least one processor is configured to cause the apparatus to: Obtaining an indication of terminating a discontinuous reception (DRX) activity time allocated to a user equipment (UE); and In response to the indication, abandoning transmission of downlink communications to the UE to terminate the DRX active time, the foregoing being completed based on current data transmission to the UE; and The UE is allowed to terminate the DRX active time.

16. The device according to claim 15, wherein: The indication comprises a Medium Access Control MAC Control Element MAC-CE.

17. The device according to claim 15, wherein: The foregoing is also based on a buffer configured to store data for transmission to the UE being empty.

18. The apparatus according to claim 15, wherein: When executing the instructions, the at least one processor is further configured to cause the apparatus to: An active mode of operation with respect to the UE is terminated.

19. The device according to claim 15, wherein: Terminating, by the UE, the DRX active time is based on expiration of a timer initiated by the UE and associated with sending the indication by the UE.

20. The apparatus of claim 15, further comprising a transceiver configured to receive the indication, wherein: The apparatus is configured as a network entity.

Images