Techniques for cell activity time extension

By extending the activity duration of the cell DRX cycle, the latency problem when the UE sends latency-sensitive data was solved, improving communication efficiency and user experience.

CN121713644APending Publication Date: 2026-03-20QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480054198.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-08-29
Filing Date
2024-08-12
Publication Date
2026-03-20

AI Technical Summary

Technical Problem

In existing wireless communication systems, user equipment (UE) may experience delays when transmitting delay-sensitive data due to the inactivity duration of discontinuous reception (DRX) cycles, which can negatively impact user experience.

Method used

Based on the UE's data delay tolerance and uplink transmission characteristics, the cell dynamically or semi-statically extends the activity duration of the DRX cycle to enable the UE to transmit via the low-latency uplink.

Benefits of technology

It improves the communication efficiency of UE when sending latency-sensitive data, reduces latency, and enhances the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121713644A_ABST
    Figure CN121713644A_ABST
Patent Text Reader

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive control signaling indicating a cell discontinuous reception (DRX) cycle for a cell for communicating with the UE. In some examples, a cell DRX cycle may alternate between an active duration during which a cell may monitor communications and an inactive duration during which a cell may refrain from monitoring communications. In some examples, a UE may send a request to extend an activity duration of a cell DRX cycle during one or more cycles of the cell DRX cycle based on a performance parameter associated with an uplink transmission satisfying a threshold. Thus, the UE may transmit an uplink transmission during an active duration of a cycle that is extended based on the transmission request.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 457,991, filed August 29, 2023, entitled “TECHNIQUESFOR CELL ACTIVE TIME EXTENSION”, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The following text relates to wireless communications, including technologies for extending cell activity time. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for cell active time extension. For example, the described techniques allow a cell of a network entity to extend an active duration of a cell discontinuous reception (DRX) cycle by one or more time units. In some cases, the cell can extend the active duration based on a delay tolerance of data for a user equipment (UE) to transmit. For example, if the UE is scheduled to transmit a low latency uplink transmission (e.g., data associated with a latency parameter that satisfies a latency threshold), the UE can transmit a request for the cell to extend the active duration of the cell DRX cycle. Accordingly, the cell can extend a current active duration or generate an additional active duration during which the UE can transmit the low latency uplink transmission. In some examples, the cell can semi-statically configure the extended duration. In some examples, the UE can dynamically indicate the extended duration based on one or more characteristics of the uplink transmission (e.g., a packet size of the uplink transmission, a quality of an uplink channel, or both).

[0006] A method for wireless communication by a UE is described. The method can include receiving control signaling indicating a cell discontinuous reception (DRX) cycle of a cell for communicating with a user equipment (UE), the cell DRX cycle alternating between an active duration during which the cell monitors for communications and an inactive duration during which the cell refrains from monitoring for communications; transmitting a request to extend the active duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, where transmitting the request is based on a performance parameter associated with an uplink transmission satisfying a threshold; and transmitting the uplink transmission during the active duration of the cycle extended based on transmitting the request.

[0007] A UE for wireless communication is described. The UE can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories. The one or more processors can be individually or collectively capable of operating to execute the code to cause the UE to receive control signaling indicating a cell DRX cycle of a cell for communicating with the UE, the cell DRX cycle alternating between an active duration during which the cell monitors for communications and an inactive duration during which the cell refrains from monitoring for communications; transmit a request to extend the active duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, where transmitting the request is based on a performance parameter associated with an uplink transmission satisfying a threshold; and transmit the uplink transmission during the active duration of the cycle extended based on transmitting the request.

[0008] Another UE for wireless communication is described. The UE can include means for receiving control signaling indicating a cell DRX cycle for a cell in which the UE communicates, the cell DRX cycle alternating between an active duration and an inactive duration, the cell monitoring for communications during the active duration, the cell refraining from monitoring for communications during the inactive duration; means for transmitting a request to extend the active duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, where transmitting the request is based on a performance parameter associated with an uplink transmission satisfying a threshold; and means for transmitting the uplink transmission during the active duration of the cycle that is extended based on transmitting the request.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code can include instructions executable by a processor to receive control signaling indicating a cell DRX cycle for a cell in which the UE communicates, the cell DRX cycle alternating between an active duration and an inactive duration, the cell monitoring for communications during the active duration, the cell refraining from monitoring for communications during the inactive duration; transmit a request to extend the active duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, where transmitting the request is based on a performance parameter associated with an uplink transmission satisfying a threshold; and transmit the uplink transmission during the active duration of the cycle that is extended based on transmitting the request.

[0010] Some examples of the method, UE, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving second control signaling indicating a set of multiple cell DRX patterns associated with the cell, where receiving the control signaling includes receiving an indication to activate a first cell DRX pattern of the set of multiple cell DRX patterns, where the first cell DRX pattern includes a DRX cycle.

[0011] In some examples of the method, UE, and non-transitory computer-readable medium described herein, transmitting the request can include operations, features, means, or instructions for transmitting the request at or before a time that is a duration before an end time of a current active duration of the cell DRX cycle.

[0012] In some examples of the method, UE, and non-transitory computer- readable medium described herein, the request can be a buffer status report (BSR) that includes a non-zero number of values, and transmitting the request can be based on the non-zero number of values satisfying a quantity threshold.

[0013] In some examples of the method, UE, and non-transitory computer- readable medium described herein, the method, apparatuses, and non-transitory computer- readable medium can also include operations, features, means, or instructions for indicating a first value that the cell can be maintaining a cell DRX cycle or a second value that the cell can be extending an active time.

[0014] Some examples of the method, UE, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for identifying, based on transmitting the request, a duration for which the active time can be extended.

[0015] In some examples of the method, UE, and non-transitory computer-readable medium described herein, transmitting the request can include operations, features, means, or instructions for transmitting, as part of the request, an indication of the duration for which the active time is to be extended.

[0016] In some examples of the method, UE, and non-transitory computer-readable medium described herein, the duration can be based on a packet size of the uplink transmission, a reference signal received power condition of a channel associated with the uplink transmission, or both.

[0017] In some examples of the method, UE, and non-transitory computer-readable medium described herein, the duration for which the active time can be extended can be semi-statically configured by the cell.

[0018] Some examples of the method, UE, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving second control signaling that enables the UE to request extending an active time of a cell DRX cycle based on a type of data traffic associated with the UE.

[0019] In some examples of the method, UE, and non-transitory computer-readable medium described herein, the uplink transmission can be a low latency uplink transmission including ultra-reliable low latency communication (URLLC) data or extended reality (XR) data, and the performance parameter can be a latency parameter, and the threshold can be a latency threshold.

[0020] Some examples of the method, UE, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for receiving an acknowledgement message indicating that a request to extend the active time can be successfully received, where transmitting the uplink transmission can be based on receiving the acknowledgement message.

[0021] In some examples of the method, the UE, and the non-transitory computer- readable medium described herein, the request can be one of a scheduling request (SR) message, a BSR message, uplink control information (UCI), a medium access control- control element (MAC-CE), or a physical uplink control channel (PUCCH) including a negative acknowledgement (NACK).

[0022] A method for wireless communication by a cell of a network entity is described. The method can include transmitting control signaling indicating a cell DRX cycle of the cell for communicating with a UE, the cell DRX cycle alternating between an active duration and an inactive duration, the cell monitoring for communications during the active duration, the cell refraining from monitoring for communications during the inactive duration; receiving a request to extend the active duration of the cell DRX cycle for one or more cycles of the cell DRX cycle, where transmitting the request is based on a performance parameter associated with an uplink transmission satisfying a threshold; and receiving the uplink transmission during the active duration of the cycle based on the request being extended.

[0023] A cell of a network entity for wireless communication is described. The cell of the network entity can include one or more memories storing processor-executable code and one or more processors coupled with the one or more memories. The one or more processors can individually or collectively be capable of operating to execute the code to cause the cell of the network entity to: transmit control signaling indicating a cell DRX cycle of the cell for communicating with a UE, the cell DRX cycle alternating between an active duration and an inactive duration, the cell monitoring for communications during the active duration, the cell refraining from monitoring for communications during the inactive duration; receive a request to extend the active duration of the cell DRX cycle for one or more cycles of the cell DRX cycle, where transmitting the request is based on a performance parameter associated with an uplink transmission satisfying a threshold; and receive the uplink transmission during the active duration of the cycle based on the request being extended.

[0024] Another cell of a network entity for wireless communication is described. The cell of the network entity can include: means for transmitting control signaling indicating a cell DRX cycle of the cell for communicating with a UE, the cell DRX cycle alternating between an active duration and an inactive duration, the cell monitoring for communications during the active duration, the cell refraining from monitoring for communications during the inactive duration; means for receiving a request to extend the active duration of the cell DRX cycle for one or more cycles of the cell DRX cycle, where transmitting the request is based on a performance parameter associated with an uplink transmission satisfying a threshold; and means for receiving the uplink transmission during the active duration of the cycle based on the request being extended.

[0025] A non-transitory computer-readable medium storing code for wireless communication is described. The code can include instructions executable by a processor to transmit control signaling indicating a cell DRX cycle of a cell for communicating with a UE, the cell DRX cycle alternating between an active duration and an inactive duration, the cell monitoring for communications during the active duration, the cell refraining from monitoring for communications during the inactive duration, receive a request to extend the active duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, where transmitting the request is based on a performance parameter associated with an uplink transmission satisfying a threshold, and receive the uplink transmission during the active duration of the cycle that is extended based on transmitting the request.

[0026] Some examples of the method, cell of the network entity, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for transmitting second control signaling indicating a set of multiple cell DRX patterns associated with the cell, where transmitting the control signaling includes transmitting an indication to activate a first cell DRX pattern of the set of multiple cell DRX patterns, where the first cell DRX pattern includes a cell DRX cycle.

[0027] In some examples of the method, cell of the network entity, and non-transitory computer-readable medium described herein, receiving the request can include operations, features, means, or instructions for receiving the request at or before a time that is a duration before an end time of a current active duration of the cell DRX cycle.

[0028] In some examples of the method, cell of the network entity, and non-transitory computer-readable medium described herein, the request can be a BSR including a non-zero amount of values, and receiving the request can be based on the non-zero amount of values satisfying an amount threshold.

[0029] Some examples of the method, cell of the network entity, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for indicating a first value that the cell can maintain the cell DRX cycle, or a second value that the cell can extend the active duration.

[0030] Some examples of the method, cell of the network entity, and non-transitory computer-readable medium described herein can further include operations, features, means, or instructions for identifying a duration for which the active duration can be extended based on receiving the request.

[0031] In some examples of the methods described herein, the cell of the network entity, and the non-transitory computer-readable medium, receiving a request may include an operation, feature, component, or instruction for receiving, as part of the request, an indication of the duration for which the activity is extended.

[0032] In some examples of the methods described herein, the cell of the network entity, and non-transitory computer-readable media, the duration may be based on the packet size transmitted on the uplink, the reference signal received power condition of the channel associated with the uplink transmission, or both.

[0033] In the methods described herein, and in some examples of cell and non-transitory computer-readable media of network entities, the duration for which the activity duration may be extended can be configured semi-statically by the cell.

[0034] The methods described herein, some examples of cell and nontransitory computer-readable media of network entities may also include operations, features, components or instructions for sending a second control signaling that enables the UE to request an extension of the activity duration of the cell DRX cycle based on the type of data service associated with the UE.

[0035] In some examples of the methods described herein, the cell of the network entity, and the non-transitory computer-readable medium, the uplink transmission can be a low-latency uplink transmission including URLLC data or XR data, and the performance parameter can be a latency parameter, and the threshold can be a latency threshold.

[0036] The methods described herein, some examples of cell and nontransitory computer-readable medium of network entities may also include operations, features, components or instructions for sending an acknowledgment message indicating that a request for extended activity duration can be accepted, wherein receiving uplink transmissions may be based on receiving the acknowledgment message.

[0037] In some examples of the methods described herein, the cell of the network entity, and the non-transitory computer-readable medium, the request may be one of an SR message, a BSR message, a UCI, a MAC-CE, or a PUCCH including NACK.

[0038] The methods described herein, some examples of cell and nontransitory computer-readable media of network entities may also include operations, features, components or instructions for extending the duration of cell DRX cycle activity for a certain duration for one or more cycles.

[0039] The methods described herein, some examples of cell and nontransitory computer-readable media of network entities may also include operations, features, components or instructions for generating additional activity durations relative to the current activity duration for one or more cycles, wherein the start of the additional activity duration may be relative to the end of the current activity duration. Attached Figure Description

[0040] Figure 1 Examples of wireless communication systems supporting techniques for extended cell activity time according to one or more aspects of this disclosure are shown.

[0041] Figure 2 Examples of wireless communication systems supporting techniques for extended cell activity time according to one or more aspects of this disclosure are shown.

[0042] Figure 3A and Figure 3B Each of the following examples illustrates a cell discontinuous reception extension process that supports a technique for extending cell activity time according to one or more aspects of this disclosure.

[0043] Figure 4 An example of a process flow supporting a technology for extended cell activity time according to one or more aspects of this disclosure is shown.

[0044] Figure 5 and Figure 6 A block diagram of an apparatus supporting a technology for extending cell activity time, according to one or more aspects of this disclosure, is shown.

[0045] Figure 7 A block diagram of a communication manager supporting a technology for extended cell activity time, according to one or more aspects of this disclosure, is shown.

[0046] Figure 8 A diagram of a system including an apparatus supporting technology for extended cell activity time is shown, according to one or more aspects of this disclosure.

[0047] Figure 9 and Figure 10 A block diagram of an apparatus supporting a technology for extending cell activity time, according to one or more aspects of this disclosure, is shown.

[0048] Figure 11 A block diagram of a communication manager supporting a technology for extended cell activity time, according to one or more aspects of this disclosure, is shown.

[0049] Figure 12 A diagram of a system including an apparatus supporting technology for extended cell activity time is shown, according to one or more aspects of this disclosure.

[0050] Figures 13 to 16 A flowchart illustrating a method for supporting technologies for extended cell activity time according to one or more aspects of this disclosure is shown. Detailed Implementation

[0051] In some examples of wireless communication, network entities can reduce power consumption by operating according to one or more discontinuous communication modes. For example, a cell of a network entity can operate according to a discontinuous reception (DRX) cycle, where the cell can alternate between an active duration and an inactive duration, during which the cell can monitor communication and during which the cell suppresses monitoring of communication. Additionally or alternatively, a cell can operate according to a discontinuous transmission (DTX) cycle, where calls can alternate between an active duration and an inactive duration, during which the cell can transmit signaling and during which the cell suppresses transmitting signaling. Additionally or alternatively, a cell can operate according to a cycle that includes both a DTX cycle and a DRX cycle. In some cases of such a cycle, the DTX cycle and the DRX cycle can at least partially overlap in the time domain. In other cases of such a cycle, the DTX cycle and the DRX cycle can be mutually exclusive in the time domain. Throughout this specification, the descriptions and features described in the context of a DRX cycle can be applied to a DTX cycle or a cycle combining a DRX cycle and a DTX cycle.

[0052] Therefore, one or more radio devices communicating with the cell can operate according to one or more power-saving modes of the cell. For example, a user equipment (UE) can transmit one or more data packets during the active duration of a cell DRX cycle and suppress transmission during the inactive duration of the cell DRX cycle. In some cases, the UE can be scheduled to transmit data packets near the end of the active duration of the cell DRX cycle. In such cases, if the UE transmits data packets, the cell can receive at least a portion of the data packets during the inactive duration of the cell DRX cycle. Therefore, the UE can wait until the subsequent active duration of the cell DRX cycle before transmitting data packets. However, if the data packets are associated with latency-sensitive data (e.g., Ultra-Reliable Low-Latency Communication (URLLC) data or Extended Reality (XR) data), delaying the transmission of data packets may degrade the user experience at the UE.

[0053] According to the techniques described herein, a cell can determine the duration of an extended cell DRX cycle based on the latency tolerance of the data at the UE. For example, if the UE is scheduled to transmit low-latency uplink transmissions (e.g., data associated with latency parameters that meet a latency threshold), the UE can send a request to extend the duration of the cell DRX cycle. Therefore, the cell can extend the current duration or generate an additional duration during which the UE can transmit low-latency uplink transmissions. In some examples, the cell can semi-statically configure the extended duration. In some examples, the UE can dynamically indicate the extended duration based on one or more characteristics of the uplink transmission (e.g., uplink transmission packet size, uplink channel quality, or both).

[0054] The various aspects of this disclosure are first described in the context of wireless communication systems, cell DRX extension processes, and process flows. These aspects are further illustrated and described by way of apparatus diagrams, system diagrams, and flowcharts related to the technology used for cell activity time extension.

[0055] Figure 1 Examples of wireless communication systems 100 supporting technologies for extended cell activity time according to one or more aspects of this disclosure are shown. Wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies including future systems and radio technologies not explicitly mentioned herein.

[0056] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0057] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0058] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0059] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0060] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0061] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0062] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0063] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0064] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support techniques for extending cell activity time as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0065] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0066] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0067] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0068] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0069] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0070] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0071] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0072] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0073] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the extent of such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping coverage areas 110, etc.

[0074] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0075] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0076] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0077] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0078] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0079] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0080] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be transferred through user plane entities, which provide IP address allocation and other functions. User plane entities may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0081] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0082] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed bands may be combined with component carriers operating with licensed bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0083] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0084] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0085] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0086] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0087] In some examples, one or more wireless devices may communicate with the cell based on one or more power-saving modes of the cell of network entity 105. For example, UE 115 may transmit one or more data packets during the active duration of the cell DRX cycle and suppress transmission during the inactive duration of the cell DRX cycle. In some cases, UE 115 may be scheduled to transmit data packets near the end of the active duration of the cell DRX cycle. In such cases, if UE 115 transmits data packets, the cell may receive at least a portion of the data packets during the inactive duration of the cell DRX cycle. Therefore, UE 115 may wait until the subsequent active duration of the cell DRX cycle before transmitting data packets. However, if the data packets are associated with latency-sensitive data (e.g., URLLC data or XR data), delaying the transmission of data packets may degrade the user experience at UE 115.

[0088] According to the techniques described herein, a cell can determine to extend the activity duration of the cell DRX cycle by one or more time units based on the latency tolerance of the data at UE 115. For example, if UE 115 is scheduled to transmit low-latency uplink transmissions (e.g., data associated with latency parameters that meet a latency threshold), UE 115 can send a request to extend the activity duration of the cell DRX cycle. Therefore, the cell can extend the current activity duration or generate an additional activity duration during which UE 115 can transmit low-latency uplink transmissions. In some examples, the cell can semi-statically configure the extended duration. In some examples, UE 115 can dynamically indicate the extended duration based on one or more characteristics of the uplink transmission (e.g., uplink transmission packet size, uplink channel quality, or both).

[0089] Figure 2 Examples of a wireless communication system 200 supporting techniques for extended cell activity time according to one or more aspects of this disclosure are shown. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network entity 105-a and UE 115-a, which may be references Figure 1 Examples of the corresponding devices described.

[0090] like Figure 2 As illustrated, network entity 105-a may include one or more cells 260 (e.g., cell 260-a and cell 260-b) or be associated with one or more such cells. Cells 260 of network entity 105-a may include macro cells (e.g., primary cells for wide-area coverage of a geographic region), small cells (e.g., microcells, picocells, or femtocells for enhancing capacity and coverage in high-density areas, indoor spaces, or where macro cell coverage is below a threshold), multiple-input multiple-output (MIMO) cells (e.g., to improve spectral efficiency and increase capacity in high-traffic areas), beamforming cells (e.g., using beamforming technology to direct focused radio signals toward specific user equipment, thereby enhancing signal strength and reliability), and so on. Figure 2 The example illustrates network entity 105-a associated with two cells 260, but it should be understood that a wireless network may include any number of network entities 105, each associated with any number of cells 260.

[0091] In some examples of the wireless communication system 200, network entity 105-a may operate according to one or more power-saving modes. For example, a cell DRX mode could be a technique used in a wireless network to enhance energy efficiency and reduce the energy consumption of one or more cells 260 of network entity 105-a (e.g., when data traffic is low or below a configured data threshold). Figure 2As illustrated, cell 260-a can operate according to a cell DRX cycle that alternates between an active duration 215 and an inactive duration 220. During the active duration 215 (e.g., cell DRX on 205), cell 260-a can monitor communications from one or more radio devices (e.g., UE115-a) serving cell 260-a. During the inactive duration 220 (e.g., cell DRX off 210), cell 260-a can suppress monitoring of communications from one or more radio devices. Therefore, cell DRX can be a power-saving mechanism that allows cell 260 to periodically enter a sleep mode, thereby saving energy during idle periods. Additionally, during the inactive duration 220 of cell DRX, one or more radio devices can suppress the transmission of data to cell 260-a, which can reduce power consumption at one or more radio devices.

[0092] In some examples, the cell DRX mode can be cell-specific (e.g., a first cell DRX mode for cell 260-a and a second DRX mode for cell 260-b). Additionally, each radio device served by a given cell 260 can share a common DRX configuration, such that transmissions scheduled at one or more radio devices can be aligned with the active duration 215 of the cell DRX mode, which allows cell 260-a to suppress signal monitoring during the inactive duration 220. Additionally or alternatively, each radio device in the radio network can be configured with a corresponding DRX mode (e.g., UE 115-a can be configured with a UE DRX mode). In such examples, cell 260-a can be configured such that the corresponding DRX modes are staggered according to multi-user scheduling. In some cases, if UE 115-a operates in the UE DRX inactive state, UE 115-a may transmit periodic signals via Configuration Grant (CG) Physical Uplink Shared Channel (PUSCH), Probe Reference Signal (e.g., Periodic or Semi-Persistent Scheduling (SPS)), or both.

[0093] Additionally or alternatively, one or more cells 260 of network entity 105-a may operate according to a cell DTX mode. In an example of cell DTX, cell 260-a may be configured to cycle through a cell DTX, similar to a cell DRX cycle, alternating between an active duration 215 and an inactive duration 220. During the active duration 215 of cell DTX, cell 260-a may transmit data to one or more served radio devices. During the inactive duration 220 of cell DTX, cell 260-a may transition to an idle period, during which cell 260-a may enter a sleep mode and suppress data transmission. Therefore, cell DTX can be a power-saving mechanism that allows cell 260 to periodically enter a sleep mode, thereby saving energy during idle periods. Additionally, during the inactive duration 220 of cell DRX, one or more radio devices may suppress monitoring of data from cell 260-a, which may reduce power consumption at one or more radio devices. While the techniques described herein are discussed in relation to cell DRX mode, it should be understood that these techniques can be applied to cell DTX mode in addition to or as an alternative to cell DRX mode. For example, cell DRX mode and cell DTX mode can be configured and operated separately (e.g., a first RRC configuration set for downlink and a second RRC configuration set for uplink), or cell DRX and cell DTX can be configured jointly (e.g., an RRC configuration set for both uplink and downlink).

[0094] UE 115-a can communicate with network entity 105-a according to one or more power-saving modes of network entity 105-a. For example, UE 115-a can send uplink data or control signaling to cell 260-a during the active duration 215 of the cell DRX cycle. However, in some cases, UE 115-a may have data packets scheduled for transmission within a threshold duration until the end of the active duration 215 (e.g., scheduled by cell 260-a or not requested). In such cases, the reception of data packets by cell 260-a may at least partially overlap with the inactive duration 220. Therefore, UE 115-a may suppress the transmission of data packets until the subsequent active duration 215 of the cell DRX mode. However, in some cases, data packets at UE 115-a may be associated with low latency tolerance. For example, data packets may include ultra-reliable low-latency (URLLC) data, or extended reality (XR) data. Therefore, delaying the transmission of data packets with low data tolerance may degrade performance at UE 115-a.

[0095] According to the techniques described herein, cell 260-a can determine the active duration 215 of extending the cell DRX cycle based on the delay tolerance of the data at UE 115-a. For example, cell 260-a can send a cell DRX cycle indication 235, which may be an example of control signaling indicating the cell DRX cycle of cell 260-a (e.g., the length of the active duration 215, the length of the inactive duration 220, periodicity, and other parameters).

[0096] In some examples, the cell DRX cycle indication 235 may be associated with the cell DRX mode indication 225. For example, prior to the cell DRX cycle indication 235, network entity 105-a may send the cell DRX mode indication 225, which includes the cell DRX mode settings that cell 260-a can operate according to (e.g., corresponding cell DRX modes each associated with a corresponding cell DRX cycle including a corresponding length of active duration 215, a corresponding length of inactive duration 220, and a corresponding periodicity). If UE 115-a receives the cell DRX mode indication 225, the cell DRX cycle indication 235 may indicate cell DRX modes from a set of cell DRX modes. In such examples, each cell DRX mode may be indicated by a bit string, wherein the cell DRX cycle indication 235 includes a bit string associated with the cell DRX mode for cell 260-a. In some examples, the cell DRX mode indication 225 can be used to indicate the cell DRX mode associated with multiple cells 260 of network entity 105-a (e.g., in some cases, all cells 260 of the network entity). In some examples, the cell DRX mode indication 225 can be used to indicate the cell DRX mode for each cell 260 of network entity 105-a. In some examples, network entity 105-a can utilize the set of cell DRX modes to configure UE 115-a as part of RRC configuration (e.g., RRC signaling). A given cell 260 can then select a cell DRX mode from the set of cell DRX modes to operate using, and can communicate the selected cell DRX mode to UE 115-a via other control signaling (e.g., downlink control information (DCI) or media access control-control element (MAC-CE)).

[0097] Based on the cell DRX mode of cell 260-a, UE 115-a can transmit one or more uplink messages during the active duration 215 of the cell DRX mode. In some cases, UE 115-a can determine that uplink transmission 255 may overlap with at least the inactive duration 220 following the current active duration 215. Therefore, UE 115-a can operate according to the extension identification procedure 240 to determine whether UE 115-a can request an extension of the current active duration 215. As part of the extension identification procedure 240, UE 115-a can determine the latency tolerance associated with uplink transmission 255. For example, if uplink transmission 255 includes latency-sensitive data (e.g., URLLC data, XR data, etc.), UE 115-a can compare the latency value associated with the data with a latency threshold. Therefore, if the uplink transmission of data 255 meets the delay threshold, UE 115-a can send an extension request message 245, which can instruct cell 260-a to extend the current activity duration 215.

[0098] In some examples, cell 260-a can enable and disable the ability of UE 115-a to send extension request message 245. For example, cell 260-a can send a cell DRX extension request configuration 230, which can enable or disable UE 115-a from sending extension request message 245. Therefore, UE 115-a can use extension identification procedure 240 depending on whether or not it is enabled to send extension request message 245.

[0099] In some examples, UE 115-a may send an extension request message 245 at a duration offset (e.g., a time increment) before the end time of the current activity duration 215. The duration offset may be defined at UE 115-a (e.g., pre-configured) or indicated by network entity 105-a via control signaling (e.g., via cell DRX extension request configuration 230).

[0100] In some examples, UE 115-a may include an extension request message 245 in its Buffer Status Report (BSR) message. In some cases, a BSR message may be sent without being requested (e.g., claimed) by network entity 105-a. For example, UE 115-a may send an unclaimed BSR at a time that satisfies the duration offset. In some examples, the BSR may include the number of non-zero values ​​that satisfy a quantity threshold (e.g., the number of non-zero values ​​is less than the quantity threshold). Therefore, the number of non-zero values ​​that satisfy the quantity threshold can indicate the extension request message 245.

[0101] In some examples, UE 115-a may include an extension request message 245 in a scheduling request (SR) message. For example, the SR message may be associated with an SR codebook, which distinguishes whether UE 115-a is requesting an extension of the current activity duration 215. For example, the first bit value in the SR message (e.g., bit value 0 or 1) may indicate that the current activity duration should not be extended, and the second bit value in the SR message (e.g., a bit value opposite to the first bit value) may indicate the extension request message 245.

[0102] As described herein, UE 115-a may include extension request messages 245 of various message types. For example, UE 115-a extension request message 245 may be included in SR messages, BSR messages (e.g., requested or unrequested), uplink control information (UCI) messages, MAC-CE, or physical uplink control channel (PUCCH) including negative acknowledgment (NACK).

[0103] If network entity 105-a receives extension request message 245, network entity 105-a and UE 115-a may assume that the activity duration 215 has been extended by a value X. The value of X may indicate the duration, number of time slots, sub-time slots, or any other type of TTI value or any combination thereof. In some examples, cell 260-a may indicate the value of X in cell DRX extension request configuration 230. In some examples, the cell may configure the value of X semi-statically (e.g., in an RRC message, DCI, Media Access Control-Control message, or in the Physical Downlink Control Channel (PDCCH)). In some examples, UE 115-a may indicate the value of X dynamically (e.g., as part of extension request message 245, or in a separate control message). In some examples, UE 115-a may determine the value of X based on the packet size of uplink transmission 255, such that the value of X increases as the packet size increases. Alternatively, UE 115-a may determine the value of X based on the reference signal received power (RSRP) condition of the channel with cell 260-a, such that the value of X may increase as the RSRP value of the channel decreases (e.g., channel quality deteriorates).

[0104] In some examples, cell 260-a can respond to the extension request message (e.g., cell 260-a can send a response 250 to the request). If the response 250 to the request indicates an acknowledgment (ACK), then cell 260-a has extended the current activity duration 215, and UE 115-a can continue to send uplink transmissions 255 during the extended activity duration. If the response 250 to the request indicates a NACK, then cell 260-a has rejected the extension request message 245, and UE 115-a can wait until a subsequent activity duration 215 before sending uplink transmissions 255. If cell 260-a suppresses the transmission of the response 250 to the request, then UE 115-a can assume that the current activity duration 215 has been extended and send uplink transmissions 255 during the extended activity duration 215.

[0105] In some examples, cell 260-a can include an extension directly after the current activity duration of 215 ends, as shown in the reference. Figure 3A As described. In some examples, cell 260-a may include an extension after the current activity duration 215 ends and before the subsequent activity duration 215, as referenced. Figure 3B As described.

[0106] Figure 3A and Figure 3B Examples of cell DRX extension procedures 300-a and 300-b supporting techniques for extending cell activity time according to one or more aspects of this disclosure are shown. In some examples, cell DRX extension procedure 300 can implement aspects of wireless communication systems 100 and 200. For example, cell DRX activation 305, cell DRX deactivation 310, activity duration 315, and inactivity duration 320 can be corresponding examples of cell DRX activation 205, cell DRX deactivation 210, activity duration 215, and inactivity duration 220. In some examples, the cell of a network entity can be adjusted according to... Figure 3A or Figure 3B The technology will extend the duration of the activity by 325 to 315.

[0107] like Figure 3A and Figure 3B As illustrated in both examples, the cells of a network entity can operate according to cell DRX modes that include active duration 315-a and inactive duration 320-a. (See reference...) Figure 2As described, a cell DRX mode can correspond to a cell DRX cycle, wherein the cell periodically alternates between an active duration of 315 and an inactive duration of 320. Therefore, a single cycle of the cell DRX mode can include an active duration of 315-a and an inactive duration of 320-a. Additionally, for a given cell DRX cycle, the cell can operate for a first duration during the active duration of 315-a and for a second duration during the inactive duration of 320-a, wherein the first and second durations can be the same or different values ​​configured by the cell.

[0108] like Figure 3A As illustrated, a cell can apply extension 325 to activity duration 315-a. For example, the cell can apply extension 325-a directly after the end time of activity duration 315-a. Therefore, the cell can remain in cell DRX enabled 305 and monitor data from one or more wireless devices during extension 325-a. In some examples, extension 325-a can occur during at least a portion of inactivity duration 320-a. In such examples, the cell can reconfigure inactivity duration 320-a to inactivity duration 320-b, where inactivity duration 320-b is the difference between inactivity duration 320-a and extension 325-a. Alternatively, the cell can include extension 325-a and cause cell DRX cyclic shift. That is, the cell can maintain inactivity duration 320-a directly after the end of extension 325-a.

[0109] A cell can configure extension 325-a for the current activity duration 315-a or for multiple subsequent activity durations 315. For example, a cell can indicate which activity duration 315 extension 325-a has been applied to by the cell via a control message (e.g., cell DRX extension request configuration 230 or response to the request 250).

[0110] like Figure 3B As illustrated, a cell can apply extension 325-b after the end time of active duration 315-a. In some examples, a cell can reconfigure a portion of inactive duration 320-a for use as extension 325-b. For example, a cell can reconfigure inactive duration 320-a to include extension 325-b, where inactive duration 320-c precedes extension 325-b and inactive duration 320-d follows extension 325-b. Therefore, the cell can switch back to cell DRX enabled 305 and monitor data from one or more radio devices during extension 325-b.

[0111] A cell can configure an extension 325-b during the current inactive period 320-a or for multiple subsequent inactive periods 320. For example, a cell can indicate via a control message (e.g., cell DRX extension request configuration 230 or response 250 to the request) which inactive period 320 the cell has applied extension 325-b to. Additionally, the control message can indicate the duration between the end of the active period 315-a and the start of the extension 325-b (e.g., inactive period 320-c).

[0112] For reference Figure 2 As described, the duration of the extension of 325-a or 325-b can be a value X, where the value is predetermined, semi-statically configured by the cell, or dynamically indicated by the UE requesting the extension of 325.

[0113] Figure 4 An example of a process flow 400 supporting a technique for extending cell activity time according to one or more aspects of this disclosure is shown. In some examples, process flow 400 may implement aspects of wireless communication systems 100 and 200 and cell DRX extension processes 300-a and 300-b. Process flow 400 includes UE 115-b and network entity 105-b, which may be as described in reference Figure 1 The corresponding examples of UE 115 and network entity 105 described in Figure 3 are shown below. Alternative examples may be implemented, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added. Furthermore, while process flow 400 illustrates the process between a single UE 115 and a single network entity 105, these processes can occur between any number of network devices and network device types.

[0114] In some examples, at 405, UE 115-b may receive control signaling indicating a set of cell DRX modes associated with the cell of network entity 105-b (e.g., cell DRX mode indication 225).

[0115] In some examples, at 410, UE 115-b may receive control signaling that enables UE 115-b to request an extension of the activity duration of the cell DRX cycle based on the type of data service associated with UE 115-b (e.g., cell DRX extension request configuration 230).

[0116] At 415, UE 115-b can receive control signaling indicating the DRX cycle of the cell used to communicate with UE 115-b. In some cases, cell DRX cycling can alternate between an active duration and an inactive duration, during which the cell monitors communication and during the inactive duration it suppresses communication monitoring. If UE 115-b receives a cell DRX mode indication (at 405), the control signaling indicating the cell DRX cycle can indicate that the cell is operating according to a first cell DRX mode in the set of cell DRX modes (e.g., the first cell DRX mode includes cell DRX cycling).

[0117] In some examples, UE 115-b can determine that an uplink transmission can at least partially overlap with the inactive duration of a cell DRX cycle. In such examples, at 420, UE 115-b can perform an extension identification procedure to determine whether to request an extension of the active duration of the cell DRX cycle. In some examples, the extension identification procedure can analyze performance parameters associated with the uplink transmission. For example, the uplink transmission can be a low-latency transmission including URLLC communication data or XR data, where the performance parameter can be a latency parameter. Therefore, UE 115-b can compare the latency parameter of the uplink transmission with a latency threshold. If the latency parameter of the uplink transmission meets the latency threshold, UE 115-b can determine to request an extension of the active duration of the cell DRX cycle. In some examples, UE 115-b can perform the extension identification procedure based on a cell DRX extension request configuration (at 410) that enables the UE to request an extension of the active duration.

[0118] At 425, UE 115-b can send a request to extend the activity duration of a cell DRX cycle during one or more cycles of the cell DRX cycle. In some examples, the request can be sent based on performance parameters associated with uplink transmission satisfying an associated threshold. In some examples, UE 115-b can send the request at or before the duration preceding the end time of the current activity duration of the cell DRX cycle. In some examples, the request can be a BFR including a number of non-zero values, where the request can be sent based on a number threshold satisfied by the number of non-zero values. In some examples, the request can include values ​​associated with the SR codebook, where a first value indicates that the cell wants to maintain the cell DRX cycle and a second value indicates that the cell wants to extend the activity duration. In some examples, the request can be one of an SR message, a BFR message, a UCI, MAC-CE, or a PUCCH including NACK.

[0119] In some examples, UE 115-b may identify the duration for which the activity duration should be extended (e.g., value X) based on a transmission request. In some examples, UE 115-b may send an indication of the duration for which the activity duration should be extended as part of a request. For example, this duration may be based on the uplink transmission packet size, the RSRP conditions of the channel associated with the uplink transmission, or both. In some examples, the cell of network entity 105-b may semi-statically configure the duration for which the activity duration should be extended.

[0120] In some examples, at 430, UE 115-b can receive a response to a request to extend the activity duration. For example, UE 115-b can receive an ACK message indicating that the request to extend the activity duration was successfully received. In some examples, uplink transmission can be based on receiving an acknowledgment message.

[0121] At 435, UE 115-b can send uplink transmissions during the activity duration of a cycle based on an extended transmission request. In some examples, this can be based on... Figure 3A Techniques (e.g., extending the DRX cycle directly after the current activity duration) can be used. In some examples, this can be done based on... Figure 3B Techniques (such as extending the DRX cycle during subsequent inactive periods) can be used to extend the cycle.

[0122] Figure 5 A block diagram 500 illustrates an apparatus 505 supporting techniques for extended cell activity time according to one or more aspects of this disclosure. Apparatus 505 may be an example of various aspects of a UE 115 as described herein. Apparatus 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Apparatus 505, or one or more components of apparatus 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that can be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0123] Receiver 510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for extending cell activity time). The information may be passed to other components of device 505. Receiver 510 may utilize a single antenna or a collection of antennas.

[0124] Transmitter 515 may provide components for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to techniques for extending cell activity time), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0125] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of the techniques for extending cell activity time as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0126] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0127] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0128] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0129] The communication manager 520 may support wireless communication according to examples disclosed herein. For example, the communication manager 520 may be capable of, configured to, or operable to support components for receiving control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration during which the cell monitors communication and suppresses monitoring of communication during the inactive duration. The communication manager 520 may be capable of, configured to, or operable to support components for sending a request to extend the active duration of a cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the transmission request is based on performance parameters associated with uplink transmission meeting a threshold. The communication manager 520 may be capable of, configured to, or operable to support components for sending uplink transmissions during the active duration of a cycle whose transmission request is extended.

[0130] By including or configuring a communication manager 520 according to an example as described herein, device 505 (e.g., controlling receiver 510, transmitter 515, communication manager 520 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing latency, lowering power consumption, and utilizing communication resources more efficiently.

[0131] Figure 6 A block diagram 600 illustrates an apparatus 605 supporting techniques for extended cell activity time according to one or more aspects of this disclosure. Apparatus 605 may be an example of aspects of apparatus 505 or UE 115 as described herein. Apparatus 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Apparatus 605, or one or more components of apparatus 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that can be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0132] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to technologies for extending cell activity time). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0133] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels related to techniques for extending cell activity time), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0134] Device 605 or its various components may be examples of parts used to perform various aspects of the techniques for extending cell activity time as described herein. For example, communication manager 620 may include control signal monitoring component 625, request message sending and receiving component 630, uplink sending component 635, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0135] The communication manager 620 may support wireless communication according to examples disclosed herein. The control signal monitoring component 625 is capable of, configured to, or operable to support components for receiving control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration during which the cell monitors communication and suppresses monitoring communication during the inactive duration. The request message sending component 630 is capable of, configured to, or operable to support components for sending a request to extend the active duration of a cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the sending request is based on performance parameters associated with uplink transmission meeting a threshold. The uplink transmission component 635 is capable of, configured to, or operable to support components for sending uplink transmissions during the active duration of a cycle whose transmission request is extended.

[0136] Figure 7 A block diagram 700 illustrates a communication manager 720 supporting techniques for extending cell activity time according to one or more aspects of this disclosure. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of the techniques for extending cell activity time as described herein. For example, the communication manager 720 may include a control signal monitoring component 725, a request message sending and receiving component 730, an uplink sending component 735, a time-of-flight identification component 740, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0137] The communication manager 720 may support wireless communication according to examples disclosed herein. The control signal monitoring component 725 is capable of, configured to, or operable to support components for receiving control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration during which the cell monitors communication and suppresses monitoring of communication during the inactive duration. The request message sending component 730 is capable of, configured to, or operable to support components for sending a request to extend the active duration of a cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the sending request is based on performance parameters associated with uplink transmission meeting a threshold. The uplink transmission component 735 is capable of, configured to, or operable to support components for sending uplink transmissions during the active duration of a cycle whose transmission request is extended.

[0138] In some examples, the control signal monitoring component 725 is capable of, configured to, or operable to support components for receiving a second control signaling indicating a set of multiple cell DRX modes associated with a cell, wherein receiving the control signaling includes receiving an indication for activating a first cell DRX mode in the set of multiple cell DRX modes, wherein the first cell DRX mode includes DRX cycling.

[0139] In some examples, in order to support sending requests, the request message sending component 730 can be configured or operated to support components for sending requests at or before the end of the current active duration that serves as the cell DRX cycle.

[0140] In some examples, the request is a BSR that includes a number of non-zero values. In other examples, the request is sent based on a number of non-zero values ​​that meet a quantity threshold.

[0141] In some examples, the duration identification component 740 is capable of being configured or operated to support components for identifying the duration by which an activity duration should be extended based on a sending request.

[0142] In some examples, in order to support sending requests, the request message sending component 730 can be configured or operated to support the following component: as part of the request, sending an indication of the duration for extending the activity duration.

[0143] In some examples, the duration is based on the uplink transmission packet size, the reference signal received power condition of the channel associated with the uplink transmission, or both.

[0144] In some examples, the duration for which the activity duration is extended is configured semi-statically by the cell.

[0145] In some examples, the control signal monitoring component 725 is capable of, configured to, or able to operate to support components for receiving a second control signaling that enables the UE to request an extension of the activity duration of the cell DRX cycle based on the type of data service associated with the UE.

[0146] In some examples, uplink transmissions are low-latency uplink transmissions that include URLLC data or extended reality data. In some examples, the performance parameter is a latency parameter, and the threshold is a latency threshold.

[0147] In some examples, the control signal monitoring component 725 is capable of, configured to, or able to operate to support components for receiving an acknowledgment message indicating that a request for extended activity duration has been successfully received, wherein uplink transmission is based on the receipt of the acknowledgment message.

[0148] In some examples, the request is one of the following: SR message, BSR message, UCI, MAC-CE, or PUCCH including NACK.

[0149] Figure 8A diagram of a system 800 including device 805 supporting technology for extended cell activity time, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

[0150] I / O controller 810 can manage the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 can utilize an operating system, such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0151] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0152] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 830 may contain a basic I / O system (BIOS), etc., which controls basic hardware or software operations such as interaction with peripheral components or devices.

[0153] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting technologies for extended cell activity time). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein.

[0154] The communication manager 820 may support wireless communication according to examples disclosed herein. For example, the communication manager 820 may be capable of, configured to, or operable to support components for receiving control signaling indicating a cell DRX cycle for communicating with a UE, the cell DRX cycle alternating between an active duration and an inactive duration during which the cell monitors communication and suppresses monitoring of communication during the inactive duration. The communication manager 820 may be capable of, configured to, or operable to support components for sending a request to extend the active duration of a cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the transmission request is based on performance parameters associated with uplink transmission meeting a threshold. The communication manager 820 may be capable of, configured to, or operable to support components for sending uplink transmissions during the active duration of a cycle whose transmission request is extended.

[0155] By including or configuring a communication manager 820 according to an example as described herein, device 805 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0156] In some examples, the communication manager 820 may be configured to use or otherwise cooperate with transceiver 815, one or more antennas 825, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or executed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions that can be executed by at least one processor 840 to cause device 805 to perform various aspects of the techniques for extending cell activity time as described herein, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0157] Figure 9 A block diagram 900 illustrates an apparatus 905 supporting a technology for extended cell activity time according to one or more aspects of this disclosure. Apparatus 905 may be an example of aspects of network entity 105 as described herein. Apparatus 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Apparatus 905, or one or more components of apparatus 905 (e.g., receiver 910, transmitter 915, and communication manager 920), may include at least one processor that can be coupled to at least one memory to individually or jointly support or implement the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0158] Receiver 910 may provide components for acquiring (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 905. In some examples, receiver 910 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 910 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0159] Transmitter 915 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 905. For example, transmitter 915 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 915 and receiver 910 may be co-located in a transceiver, which may include or be coupled to a modem.

[0160] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of parts for performing various aspects of the techniques for extending cell activity time as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0161] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0162] Additionally or alternatively, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured, either individually or collectively, as components for performing the functions described in this disclosure).

[0163] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 920 may receive information from the receiver 910, transmit information to the transmitter 915, or be integrated with the receiver 910, transmitter 915, or both to acquire information, output information, or perform various other operations as described herein.

[0164] The communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for transmitting control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration during which the cell monitors communication and suppresses monitoring of communication during the inactive duration. The communication manager 920 may be capable of, configured to, or operable to support components for receiving requests to extend the active duration of a cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the transmission request is based on performance parameters associated with uplink transmissions meeting a threshold. The communication manager 920 may be capable of, configured to, or operable to support components for receiving uplink transmissions during the active duration of a cycle whose transmission request is extended.

[0165] By including or configuring a communication manager 920 according to an example as described herein, device 905 (e.g., controlling receiver 910, transmitter 915, communication manager 920 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing latency, lowering power consumption, and utilizing communication resources more efficiently.

[0166] Figure 10A block diagram 1000 of an apparatus 1005 supporting a technology for extended cell activity time according to one or more aspects of this disclosure is shown. Apparatus 1005 may be an example of aspects of apparatus 905 or network entity 105 as described herein. Apparatus 1005 may include receiver 1010, transmitter 1015, and communication manager 1020. Apparatus 1005, or one or more components of apparatus 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that can be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0167] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0168] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0169] Device 1005 or its various components may be examples of parts used to perform various aspects of the techniques for extending cell activity time as described herein. For example, communication manager 1020 may include control signaling component 1025, request monitoring component 1030, uplink monitoring component 1035, or any combination thereof. Communication manager 1020 may be examples of aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1020 may receive information from receiver 1010, transmit information to transmitter 1015, or be integrated in combination with receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0170] The communication manager 1020 may support wireless communication according to examples disclosed herein. The control signaling component 1025 is capable of, configured to, or operable to support components for transmitting control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration during which the cell monitors communication and suppresses monitoring of communication during the inactive duration. The request monitoring component 1030 is capable of, configured to, or operable to support components for receiving requests to extend the active duration of a cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the transmission request is based on performance parameters associated with uplink transmission meeting a threshold. The uplink monitoring component 1035 is capable of, configured to, or operable to support components for receiving uplink transmissions during the active duration of a cycle whose transmission request is extended.

[0171] Figure 11A block diagram 1100 of a communication manager 1120 supporting techniques for extended cell activity time according to one or more aspects of this disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of parts for performing various aspects of the techniques for extended cell activity time as described herein. For example, the communication manager 1120 may include a control signaling component 1125, a request monitoring component 1130, an uplink monitoring component 1135, a duration identification component 1140, a power saving configuration component 1145, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0172] Communication manager 1120 may support wireless communication according to examples disclosed herein. Control signaling component 1125 is capable of, configured to, or operable to support components for transmitting control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration during which the cell monitors communication and suppresses monitoring of communication during the inactive duration. Request monitoring component 1130 is capable of, configured to, or operable to support components for receiving requests to extend the active duration of a cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the transmission request is based on performance parameters associated with uplink transmission meeting a threshold. Uplink monitoring component 1135 is capable of, configured to, or operable to support components for receiving uplink transmissions during the active duration of a cycle whose transmission request is extended.

[0173] In some examples, control signaling component 1125 is capable of, configured to, or operable to support components for transmitting a second control signaling for indicative of a set of multiple cell DRX modes associated with a cell, wherein transmitting the control signaling includes transmitting an indication for activating a first cell DRX mode in the set of multiple cell DRX modes, wherein the first cell DRX mode includes cell DRX cycling.

[0174] In some examples, in order to support receiving requests, the request monitoring component 1130 is able to be configured or operated to support components for receiving requests at or before the end of the current activity duration that serves as the cell DRX cycle.

[0175] In some examples, the request is a BSR that includes a number of non-zero values. In other examples, the request is received based on a number of non-zero values ​​that meet a quantity threshold.

[0176] In some examples, the duration identification component 1140 is capable of being configured or operated to support a component for identifying the duration by which the activity duration should be extended based on a received request.

[0177] In some examples, in order to support receiving requests, the request monitoring component 1130 is able to be configured or operated to support the following component: as part of the request, receiving an indication of the duration for which the activity duration is extended.

[0178] In some examples, the duration is based on the uplink transmission packet size, the reference signal received power condition of the channel associated with the uplink transmission, or both.

[0179] In some examples, the duration for which the activity duration is extended is configured semi-statically by the cell.

[0180] In some examples, control signaling component 1125 is capable of, configured to, or able to operate to support components for sending a second control signaling that enables the UE to request an extension of the activity duration of the cell DRX cycle based on the type of data service associated with the UE.

[0181] In some examples, uplink transmissions are low-latency uplink transmissions that include URLLC data or extended reality data. In some examples, the performance parameter is a latency parameter, and the threshold is a latency threshold.

[0182] In some examples, control signaling component 1125 is capable of, configured to, or able to operate to support components for sending an acknowledgment message indicating that a request for extended activity duration has been accepted, wherein receiving uplink transmission is based on receiving the acknowledgment message.

[0183] In some examples, the request is one of the following: SR message, BSR message, UCI, MAC-CE, or PUCCH including NACK.

[0184] In some examples, the power saving configuration component 1145 is capable of being configured or operated to support components for extending the activity duration of a cell DRX cycle for a certain duration for one or more cycles.

[0185] In some examples, the power saving configuration component 1145 is capable of being configured to operate to support components for generating additional activity durations relative to the current activity duration for one or more cycles, wherein the start of the additional activity duration is relative to the end of the current activity duration.

[0186] Figure 12 A diagram of a system 1200 including device 1205 supporting technologies for extended cell activity time, according to one or more aspects of this disclosure, is shown. Device 1205 may be an example of device 905, device 1005, or network entity 105 as described herein, or a component including such devices. Device 1205 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1205 may include components supporting output and acquisition of communication, such as a communication manager 1220, a transceiver 1210, an antenna 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components may communicate electronically or otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1240).

[0187] Transceiver 1210 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1210 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, device 1205 may include one or more antennas 1215 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1210 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1215, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1215, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1215 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1215 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1210 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1210, or transceiver 1210 and one or more antennas 1215, or transceiver 1210 and one or more antennas 1215 and one or more processors or one or more memory components (e.g., at least one processor 1235, at least one memory 1225, or both) may be included in a chip or chip assembly mounted in device 1205. In some examples, transceiver 1210 may be operable to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0188] At least one memory 1225 may include RAM, ROM, or any combination thereof. At least one memory 1225 may store computer-readable, computer-executable code 1230 including instructions that, when executed by one or more of the at least one processor 1235, cause the device 1205 to perform the various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by one of the at least one processor 1235, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1225 may contain a BIOS, etc., which controls basic hardware or software operations such as interaction with peripheral components or devices. In some examples, at least one processor 1235 may include multiple processors, and at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0189] At least one processor 1235 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more of the at least one processor 1235. At least one processor 1235 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1225) to cause device 1205 to perform various functions (e.g., functions or tasks supporting technologies for extended cell activity time). For example, device 1205 or components of device 1205 may include at least one processor 1235 and at least one memory 1225 coupled to one or more of the at least one processor 1235, wherein at least one processor 1235 and at least one memory 1225 are configured to perform the various functions described herein. At least one processor 1235 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 1230) to perform the functions of device 1205. At least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1205 (such as within one or more memories of at least one memory 1225). In some implementations, at least one processor 1235 may be a component of a processing system. A processing system generally refers to a system or series of machines or components that receive input and process that input to produce a set of outputs (which may be passed to other systems or components, such as device 1205). For example, the processing system of device 1205 may refer to a system that includes various other components or sub-components of device 1205 (such as at least one processor 1235, transceiver 1210, communication manager 1220, or other components or combinations of components of device 1205). The processing system of device 1205 can interface with other components of device 1205 and can process information (such as inputs or signals) received from other components or output information to other components. For example, the chip or modem of device 1205 may include a processing system and one or more interfaces for outputting information or for acquiring information, or both. These one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to acquire information, or the same interface configured to both output and acquire information, and other specific implementations.In some embodiments, one or more interfaces may refer to the interface between the processing system of the chip or modem and the transmitter, enabling device 1205 to transmit information output from the chip or modem. Additionally or alternatively, in some embodiments, one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1205 to receive information or signal input, and such information can be transmitted to the processing system. Those skilled in the art will readily recognize that a first interface may also receive information or signal input, and a second interface may also output information or signal output.

[0190] In some examples, bus 1240 may support communication at protocol layers (e.g., within a protocol layer) in a protocol stack. In some examples, bus 1240 may support communication associated with logical channels of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communication performed within components of device 1205, or communication performed between different components of device 1205 that are co-addressable or may be located in different locations (e.g., where device 1205 may refer to a system in which one or more of communication manager 1220, transceiver 1210, at least one memory 1225, code 1230 and at least one processor 1235 may be located in one of the different components or partitioned between the different components).

[0191] In some examples, the communication manager 1220 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1220 can manage the transfer of data communication between client devices such as one or more UEs 115. In some examples, the communication manager 1220 can manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1220 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0192] The communication manager 1220 may support wireless communication according to examples disclosed herein. For example, the communication manager 1220 may be capable of, configured to, or operable to support components for transmitting control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration during which the cell monitors communication and suppresses monitoring of communication during the inactive duration. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving requests to extend the active duration of a cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the transmission request is based on performance parameters associated with uplink transmissions meeting a threshold. The communication manager 1220 may be capable of, configured to, or operable to support components for receiving uplink transmissions during the active duration of a cycle whose transmission request is extended.

[0193] By including or configuring a communication manager 1220 according to an example as described herein, device 1205 can support techniques for improving communication reliability, reducing latency, improving and reducing user experience related to processing, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, and improving the utilization of processing power.

[0194] In some examples, the communication manager 1220 may be configured to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting) using or in cooperation with transceiver 1210, one or more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communication manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by transceiver 1210, one or more processors in at least one processor 1235, one or more memories in at least one memory 1225, code 1230, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1235, at least one memory 1225, code 1230, or any combination thereof). For example, code 1230 may include instructions that can be executed by one or more processors in at least one processor 1235 to cause device 1205 to perform various aspects of the techniques for extending cell activity time as described herein, or at least one processor 1235 and at least one memory 1225 may be otherwise configured to perform or support such operations individually or jointly.

[0195] Figure 13A flowchart illustrating a method 1300 for supporting technologies for extended cell activity time according to various aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0196] At 1305, the method may include receiving control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration, during which the cell monitors communication and during which the cell suppresses monitoring of communication. The operation of block 1305 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1305 may be provided by reference to [reference needed]. Figure 7 The control signal monitoring component 725 described herein performs this function.

[0197] At 1310, the method may include sending a request to extend the activity duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the sending request is based on a performance parameter associated with uplink transmission satisfying a threshold. The operation of block 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be provided by reference to [reference needed]. Figure 7 The request message sending and receiving component 730 described is used to execute this.

[0198] At 1315, the method may include sending an uplink transmission during the activity duration of a cycle based on an extended transmission request. The operation of block 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1315 may be derived from references... Figure 7 The described uplink transmitting component 735 is used to perform this.

[0199] Figure 14 A flowchart illustrating a method 1400 for supporting technologies for extended cell activity time according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be implemented by, as referenced... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0200] At 1405, the method may include receiving control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration, during which the cell monitors communication and during which the cell suppresses monitoring of communication. Operation of block 1405 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1405 may be provided by reference to [reference needed]. Figure 7 The control signal monitoring component 725 described herein performs this function.

[0201] At 1410, the method may include sending a request to extend the activity duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, wherein the sending request is based on performance parameters associated with uplink transmissions meeting a threshold. The operation of block 1410 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be provided by reference to [reference needed]. Figure 7 The request message sending and receiving component 730 described is used to execute this.

[0202] At 1415, the method may include identifying the duration by which the activity duration is to be extended based on the sending request. The operation of block 1415 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1415 may be derived from references... Figure 7 The described historical identifier component 740 is used to perform this.

[0203] At 1420, the method may include sending an uplink transmission during the activity duration of a cycle based on an extended transmission request. The operation of block 1420 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1420 may be derived from references... Figure 7 The described uplink transmitting component 735 is used to perform this.

[0204] Figure 15 A flowchart illustrating a method 1500 for extending cell activity time according to various aspects of this disclosure is shown. Operation of method 1500 may be implemented by a network entity or its components as described herein. For example, operation of method 1500 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0205] At 1505, the method may include sending control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration, during which the cell monitors communication and during which the cell suppresses monitoring of communication. The operation of block 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1505 may be provided by reference to [reference needed]. Figure 11 The control signaling component 1125 described herein is used to execute this.

[0206] At 1510, the method may include receiving a request to extend the activity duration of a cell DRX cycle during one or more cycles of a cell DRX cycle, wherein the transmission request is based on performance parameters associated with uplink transmissions meeting a threshold. Operation of block 1510 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be provided by reference to [reference needed]. Figure 11 The described request monitoring component 1130 is used to perform this.

[0207] At 1515, the method may include receiving uplink transmissions during the activity duration of a cycle based on an extended transmission request. The operation of block 1515 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1515 may be derived from references... Figure 11 The uplink monitoring component 1135 described herein is used to perform this function.

[0208] Figure 16 A flowchart illustrating a method 1600 for extending cell activity time according to various aspects of this disclosure is shown. Operation of method 1600 may be implemented by a network entity or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 4 as well as Figures 9 to 12 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0209] At 1605, the method may include sending control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration, during which the cell monitors communication and during which the cell suppresses monitoring of communication. The operation of block 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to [reference needed]. Figure 11 The control signaling component 1125 described herein is used to execute this.

[0210] At 1610, the method may include receiving a request to extend the activity duration of a cell DRX cycle during one or more cycles of a cell DRX cycle, wherein the transmission request is based on performance parameters associated with uplink transmissions meeting a threshold. Operation of block 1610 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1610 may be provided by reference to [reference needed]. Figure 11 The described request monitoring component 1130 is used to perform this.

[0211] At 1615, the method may include identifying the duration by which the activity duration is to be extended based on the received request. The operation of box 1615 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1615 may be derived from references... Figure 11 The described time signature component 1140 is used to perform this.

[0212] At 1620, the method may include receiving uplink transmissions during the activity duration of a cycle based on an extended transmission request. The operation of block 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1620 may be derived from references... Figure 11 The uplink monitoring component 1135 described herein is used to perform this function.

[0213] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving control signaling indicating a cell DRX cycle for communicating with the UE, the cell DRX cycle alternating between an active duration and an inactive duration, the cell monitoring communication during the active duration and the cell suppressing monitoring communication during the inactive duration; sending a request to extend the active duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, wherein sending the request is at least partially based on a performance parameter associated with uplink transmission satisfying a threshold; and sending the uplink transmission during the active duration of the cycle in which the request is extended.

[0214] Aspect 2: According to the method of aspect 1, the method further includes: receiving a second control signaling indicating a plurality of cell DRX modes associated with the cell, wherein receiving the control signaling includes receiving an indication for activating a first cell DRX mode among the plurality of cell DRX modes, wherein the first cell DRX mode includes the DRX cycle.

[0215] Aspect 3: The method according to any one of Aspects 1 to 2, wherein sending the request comprises: sending the request at or before the time preceding the end time of the current activity duration of the cell DRX cycle.

[0216] Aspect 4: According to the method of aspect 3, the request is a BSR that includes a number of non-zero values, and the request is sent at least in part based on the number of non-zero values ​​satisfying a quantity threshold.

[0217] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the request includes a value associated with the SR codebook, the value being one of: a first value indicating that the cell should maintain the cell DRX cycle, or a second value indicating that the cell should extend the duration of the activity.

[0218] Aspect 6: The method according to any one of aspects 1 to 5, the method further comprising: identifying the duration for which the activity duration is to be extended, at least in part based on sending the request.

[0219] Aspect 7: The method according to any one of Aspects 1 to 6, wherein sending the request comprises: as part of the request, sending an indication of the duration for extending the duration of the activity.

[0220] Aspect 8: The method according to aspect 7, wherein the duration is based at least in part on the packet size of the uplink transmission, the reference signal reception power condition of the channel associated with the uplink transmission, or both.

[0221] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the duration for which the activity duration is extended is configured semi-statically by the cell.

[0222] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: receiving a second control signaling, the second control signaling enabling the UE to request an extension of the activity duration of the cell DRX cycle based at least in part on the type of data service associated with the UE.

[0223] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the uplink transmission is a low-latency uplink transmission including URLLC data or XR data, the performance parameter is a latency parameter, and the threshold is a latency threshold.

[0224] Aspect 12: The method according to any one of aspects 1 to 11, the method further comprising: receiving an acknowledgment message indicating that the request to extend the duration of the activity has been successfully received, wherein the uplink transmission is at least partially based on the receipt of the acknowledgment message.

[0225] Aspect 13: The method according to any one of Aspects 1 to 12, wherein the request is one of an SR message, a BSR message, a UCI, a MAC-CE, or a PUCCH including NACK.

[0226] Aspect 14: A method for wireless communication at a cell of a network entity, the method comprising: transmitting control signaling indicating a cell DRX cycle for communicating with a UE, the cell DRX cycle alternating between an active duration and an inactive duration, the cell monitoring communication during the active duration, and the cell suppressing monitoring communication during the inactive duration; receiving a request to extend the active duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, wherein transmitting the request is based at least in part on a performance parameter associated with uplink transmission satisfying a threshold; and receiving the uplink transmission during the active duration of the cycle in which the request is extended.

[0227] Aspect 15: The method according to aspect 14, the method further comprising: sending a second control signaling indicating a plurality of cell DRX modes associated with the cell, wherein sending the control signaling includes sending an indication for activating a first cell DRX mode among the plurality of cell DRX modes, wherein the first cell DRX mode includes the cell DRX cycle.

[0228] Aspect 16: The method according to any one of Aspects 14 to 15, wherein receiving the request comprises: receiving the request at or before the time preceding the end time of the current activity duration of the cell DRX cycle.

[0229] Aspect 17: The method according to aspect 16, wherein the request is a BSR comprising a number of non-zero values, and the request is received at least in part based on the number of non-zero values ​​satisfying a quantity threshold.

[0230] Aspect 18: The method according to any one of Aspects 14 to 17, wherein the request includes a value associated with the SR codebook, the value being one of: a first value indicating that the cell should maintain the cell DRX cycle, or a second value indicating that the cell should extend the duration of the activity.

[0231] Aspect 19: The method according to any one of aspects 14 to 18, the method further comprising: identifying, at least in part, the duration for which the activity duration is to be extended based on receiving the request.

[0232] Aspect 20: The method according to any one of aspects 14 to 19, wherein receiving the request comprises: as part of the request, receiving an indication for the duration of the activity.

[0233] Aspect 21: The method according to aspect 20, wherein the duration is based at least in part on the packet size of the uplink transmission, the reference signal reception power condition of the channel associated with the uplink transmission, or both.

[0234] Aspect 22: The method according to any one of aspects 14 to 21, wherein the duration for which the activity duration is extended is configured semi-statically by the cell.

[0235] Aspect 23: The method according to any one of Aspects 14 to 22, the method further comprising: sending a second control signaling, the second control signaling enabling the UE to request an extension of the activity duration of the cell DRX cycle based at least in part on the type of data service associated with the UE.

[0236] Aspect 24: The method according to any one of Aspects 14 to 23, wherein the uplink transmission is a low-latency uplink transmission including URLLC data or XR data, the performance parameter is a latency parameter, and the threshold is a latency threshold.

[0237] Aspect 25: The method according to any one of aspects 14 to 24, the method further comprising: sending an acknowledgment message indicating that the request to extend the duration of the activity is accepted, wherein receiving the uplink transmission is at least in part based on receiving the acknowledgment message.

[0238] Aspect 26: The method according to any one of Aspects 14 to 25, wherein the request is one of an SR message, a BSR message, a UCI, a MAC-CE, or a PUCCH including NACK.

[0239] Aspect 27: The method according to any one of aspects 14 to 26, the method further comprising: extending the activity duration of the cell DRX cycle for a certain duration for the one or more cycles.

[0240] Aspect 28: The method according to any one of aspects 14 to 27, the method further comprising: generating an additional activity duration for the current activity duration relative to the cell DRX cycle for the one or more cycles, wherein the start of the additional activity duration is relative to the end of the current activity duration.

[0241] Aspect 29: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 13.

[0242] Aspect 30: A UE for wireless communication, the UE comprising at least one component for performing the method according to any one of aspects 1 to 13.

[0243] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of aspects 1 to 13.

[0244] Aspect 32: A cell of a network entity for wireless communication, the cell comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the cell of the network entity to perform a method according to any one of aspects 14 to 28.

[0245] Aspect 33: A cell of a network entity for wireless communication, the cell comprising at least one component for performing a method according to any one of aspects 14 to 28.

[0246] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform a method according to any one of aspects 14 to 28.

[0247] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0248] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0249] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0250] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

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

[0252] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0253] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0254] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0255] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, acquiring, selecting, choosing, building, and other similar actions.

[0256] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate between similar components. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second reference numeral or other subsequent reference numerals.

[0257] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0258] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this 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 scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the UE: The system receives control signaling indicating a cell discontinuous reception (DRX) cycle for communicating with the UE, the cell DRX cycle alternating between an active period and an inactive period, the cell monitoring communication during the active period, and the cell suppressing monitoring communication during the inactive period. Send a request to extend the activity duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, wherein sending the request is based at least in part on a performance parameter associated with uplink transmission satisfying a threshold; as well as The uplink transmission is sent during the activity duration, which is at least in part based on a cycle in which the request is sent.

2. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: Receive a second control signaling indicating a plurality of cell DRX modes associated with the cell, wherein receiving the control signaling includes receiving an indication for activating a first cell DRX mode among the plurality of cell DRX modes, wherein the first cell DRX mode includes the DRX cycle.

3. The UE of claim 1, wherein, in order to send the request, the one or more processors are individually or jointly operable to execute the code to cause the UE to: The request is sent at or before the end time of the current activity duration that is the DRX cycle of the cell.

4. The UE of claim 3, wherein the request is a buffer status report comprising a number of non-zero values, and wherein sending the request is based at least in part on the number of non-zero values ​​satisfying a quantity threshold.

5. The UE of claim 1, wherein the request includes a value associated with a scheduling request codebook, the value being one of the following: The instruction is given to the cell to maintain the first value of the cell's DRX cycle, or A second value indicating that the cell should extend the duration of the activity.

6. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The duration for which the activity should be extended is identified, at least in part, based on sending the request.

7. The UE of claim 1, wherein, in order to send the request, the one or more processors are individually or jointly operable to execute the code to cause the UE to: As part of the request, an instruction is sent for the duration of the activity to be extended.

8. The UE of claim 7, wherein the duration is based at least in part on the packet size of the uplink transmission, the reference signal reception power condition of the channel associated with the uplink transmission, or both.

9. The UE of claim 1, wherein the duration for which the activity duration is extended is configured semi-statically by the cell.

10. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The UE receives a second control signaling message that enables it to request an extension of the activity duration of the cell DRX cycle, at least in part, based on the type of data service associated with the UE.

11. The UE of claim 1, wherein the uplink transmission is a low-latency uplink transmission including ultra-reliable low-latency communication data or extended reality data, the performance parameter is a latency parameter, and the threshold is a latency threshold.

12. The UE of claim 1, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the UE to: The uplink transmission receives an acknowledgment message indicating that the request to extend the duration of the activity has been successfully received, wherein the uplink transmission is based at least in part on the receipt of the acknowledgment message.

13. The UE of claim 1, wherein the request is one of a scheduling request message, a buffer status report message, uplink control information, a media access control-control element, or a physical uplink control channel including negative acknowledgment.

14. A cell of a network entity, the cell comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the cell: Control signaling is sent to indicate a cell discontinuous reception (DRX) cycle for communicating with user equipment (UE), the cell DRX cycle alternating between an active period and an inactive period, the cell monitoring communication during the active period, and the cell suppressing monitoring communication during the inactive period; Receive a request to extend the activity duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, wherein sending the request is based at least in part on a performance parameter associated with uplink transmission satisfying a threshold; as well as The uplink transmission is received during the activity duration, which is at least in part based on a cycle in which the transmission of the request is extended.

15. The cell of claim 14, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the cell to: Sending a second control signaling instruction indicating multiple cell DRX modes associated with the cell, wherein sending the control signaling includes sending an instruction to activate a first cell DRX mode among the multiple cell DRX modes, wherein the first cell DRX mode includes the cell DRX cycle.

16. The cell of claim 14, wherein, in order to receive the request, the one or more processors are individually or jointly operable to execute the code to cause the cell to: The request is received at or before the end time of the current activity duration that is the DRX cycle of the cell.

17. The cell of claim 16, wherein the request is a buffer status report comprising a number of non-zero values, and wherein receiving the request is at least in part based on a number threshold being met based on the number of non-zero values.

18. The cell of claim 14, wherein the request includes a value associated with a scheduling request codebook, the value being one of the following: The instruction is given to the cell to maintain the first value of the cell's DRX cycle, or A second value indicating that the cell should extend the duration of the activity.

19. The cell of claim 14, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the cell to: The duration for which the activity should be extended is identified, at least in part, based on the receipt of the request.

20. The cell of claim 14, wherein, in order to receive the request, the one or more processors are individually or jointly operable to execute the code to cause the cell to: As part of the request, an instruction is received regarding the duration for extending the duration of the activity.

21. The cell of claim 20, wherein the duration is based at least in part on the packet size of the uplink transmission, the reference signal received power condition of the channel associated with the uplink transmission, or both.

22. The cell of claim 14, wherein the duration for which the activity duration is extended is configured semi-statically by the cell.

23. The cell of claim 14, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the cell to: A second control signaling is sent, which enables the UE to request an extension of the activity duration of the cell DRX cycle, at least in part, based on the type of data service associated with the UE.

24. The cell of claim 14, wherein the uplink transmission is a low-latency uplink transmission including ultra-reliable low-latency communication data or extended reality data, wherein the performance parameter is a latency parameter, and the threshold is a latency threshold.

25. The cell of claim 14, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the cell to: Send an acknowledgment message indicating that the request to extend the duration of the activity is accepted, wherein receiving the uplink transmission is at least in part based on receiving the acknowledgment message.

26. The cell of claim 14, wherein the request is one of a scheduling request message, a buffer status report message, uplink control information, a media access control-control element, or a physical uplink control channel including negative acknowledgment.

27. The cell of claim 14, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the cell to: For the one or more cycles, the activity duration of the cell DRX cycle is extended for a certain period of time.

28. The cell of claim 14, wherein the one or more processors are individually or jointly capable of further operating to execute the code to cause the cell to: For the one or more cycles, generate additional activity durations relative to the current activity duration of the cell DRX cycle, wherein the start of the additional activity duration is relative to the end of the current activity duration.

29. A method for conducting wireless communication at a user equipment (UE), the method comprising: The system receives control signaling indicating a cell discontinuous reception (DRX) cycle for communicating with the UE, the cell DRX cycle alternating between an active period and an inactive period, the cell monitoring communication during the active period, and the cell suppressing monitoring communication during the inactive period. Send a request to extend the activity duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, wherein sending the request is based at least in part on a performance parameter associated with uplink transmission satisfying a threshold; as well as The uplink transmission is sent during the activity duration, which is at least in part based on a cycle in which the request is sent.

30. A method for conducting wireless communication at a cell of a network entity, the method comprising: Control signaling is sent to indicate a cell discontinuous reception (DRX) cycle for communicating with user equipment (UE), the cell DRX cycle alternating between an active period and an inactive period, the cell monitoring communication during the active period, and the cell suppressing monitoring communication during the inactive period; Receive a request to extend the activity duration of the cell DRX cycle during one or more cycles of the cell DRX cycle, wherein sending the request is based at least in part on a performance parameter associated with uplink transmission satisfying a threshold; as well as The uplink transmission is received during the activity duration, which is at least in part based on a cycle in which the transmission of the request is extended.