Wireless communication with power state transition

Abstract

Apparatuses and methods for enabling power state transitions are described. An apparatus is configured to receive a DL EOC indication of a trigger status indication from a network node. The apparatus is configured to transmit a status indication to the network node and based on the DL EOC indication, the status indication indicating a status of a buffer or delay of the UE and an estimated time at which the UE estimates arrival of a next UL packet. Another apparatus is configured to transmit a DL EOC indication that triggers a status indication to a UE. The apparatus is configured to receive a status indication from the UE and based on the DL EOC indication, the status indication indicating a status of a buffer or delay of the UE and an estimated time at which the UE estimates arrival of a next UL packet.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Non-Provisional Patent Application Serial No. 18 / 447,060, entitled “WIRELESS COMMUNICATION WITH POWER STATE TRANSITIONS”, filed August 9, 2023, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to wireless communication utilizing different power states. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be associated with, or may be a, user equipment (UE). The apparatus is configured to receive a downlink (DL) communication end (EOC) indication that triggers a status indication from a network node. The apparatus is also configured to send a status indication to the network node and based on the DL EOC indication, the status indication indicating the status of: (i) the UE's buffer or UE delay, and (ii) an estimated time indicating to the UE the estimated arrival time of the next UL packet.

[0008] In this respect, the method includes receiving a DL EOC indication that triggers a state indication from a network node. The method also includes sending a state indication to the network node and based on the DL EOC indication, the state indication indicating the state of: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating to the UE the estimated time of arrival of the next UL packet.

[0009] In another aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus is configured to send a DL EOC indication triggering a state indication to a UE. The apparatus is also configured to receive a state indication from the UE and based on the DL EOC indication, the state indication indicating the state of: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating to the UE the estimated time of arrival of the next UL packet.

[0010] In this respect, the method includes sending a DL EOC indication that triggers a state indication to the UE. The method also includes receiving a state indication from the UE and based on the DL EOC indication, the state indication indicating the state of: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating to the UE the estimated time of arrival of the next UL packet.

[0011] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0012] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0013] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0014] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0015] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0016] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0017] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0018] Figure 4 This is a diagram illustrating examples of scheduling request (SR) overwriting with physical downlink control channel (PDCCH) skipping and search space set (SSS) group (SSSG) switching according to various aspects of this disclosure.

[0019] Figure 5 These are illustrations of example XR services based on various aspects of this disclosure.

[0020] Figure 6 This is a call flow diagram for wireless communication based on various aspects of this disclosure.

[0021] Figure 7 This is a diagram illustrating example power states and associated code points according to various aspects of this disclosure, as well as a call flow diagram for wireless communication.

[0022] Figure 8 This is a diagram illustrating example uplink control information (UCI) code points and conditional downlink control information (DCI) for power states according to various aspects of this disclosure.

[0023] Figure 9 This is a diagram illustrating examples of UL and DL transmissions associated with power status and estimated time according to various aspects of this disclosure.

[0024] Figure 10 This is an illustration of example UL-approved actions following status indication and wake-up signal monitoring for autonomous power state transitions, according to various aspects of this disclosure.

[0025] Figure 11 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0026] Figure 12 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0027] Figure 13 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0028] Figure 14 This is a flowchart of a wireless communication method according to various aspects of this disclosure.

[0029] Figure 15 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities.

[0030] Figure 16 This is a diagram illustrating an example of a hardware implementation used for an example network entity. Detailed Implementation

[0031] Wireless communication networks can implement service flows with specific characteristics that utilize communication and sensing for applications. Service flows in wireless communication networks can have various characteristics, such as layer attributes, time frames for latency, power-saving configurations, etc. As an example, Extended Reality (XR) services for UL and DL can have characteristics such as application layer attributes, short time frames for switching (where longer latency for the service flow may degrade the user experience of XR applications or devices), and unbalanced service flows. In scenarios where unbalanced services may exist, for example, services may be dominated by UL packets for a certain amount of time, while in other scenarios, DL packets may exist for a certain amount of time. Power-saving configurations for XR can include UL states triggered by inactivity or rapid triggering (e.g., via DCI) (e.g., no DL communication). Other configurations, such as those for PDCCH skipping, can save power by allowing the UE to skip monitoring of DL PDCCH data / information.

[0032] The aspects presented in this paper provide mechanisms for transitioning between power states. For example, in the context of XR, the aspects presented in this paper implement increased granularity and faster transitions compared to discontinuous reception (DRX) or connected mode DRX (C-DRX) active-inactive states and C-DRX transitions based on inactivity timers designed for eMBB / voice services. The aspects presented in this paper implement SSSG state / PDCCH skipping in a quasi-periodic structure and additional granularity of power states (e.g., UL power state without DL monitoring). Further regarding PDCCH skipping, since no communication may occur when the UE is not monitoring the PDCCH (in both UL and DL), it may introduce latency into UL scheduling. To reduce UL scheduling latency, if the UE has urgent UL data to send, the UE can indicate the cessation of PDCCH skipping or overwrite the SSSG handover via the transmission of a scheduling request (SR) (e.g., the UE can switch back to regular PDCCH monitoring to monitor uplink permission after transmitting the SR). Related to latency reduction, the UE can terminate PDCCH skipping if a pending negative acknowledgment (NACK) is present. However, such configurations do not consider scenarios without urgent UL data. For example, if the UE cancels PDCCH skipping, the base station (e.g., gNB, etc.) may have already transmitted redundant PDCCH skipping indications for the UE to enter sleep mode (whether this is a scheduled DCI or an unscheduled DCI—an unscheduled DCI could be in the form of a dummy grant with zero resource block allocation and used to indicate PDCCH skipping (e.g., not used for any other operation)). Furthermore, the base station (e.g., gNB, etc.) may not know / be aware that the UE is about to transmit a positive SR so close to a PDCCH skipping indication, which could also guarantee that the base station transmits redundant indications. Similarly, transmitting a DCI uses PDCCH resources and can be considered an overhead in terms of power and resources. Therefore, the aspects presented in this paper provide improvements that enable the base station to make better decisions about whether to transmit skipping indications. The aspects presented in this paper provide solutions covering transitions between entering and exiting power states.

[0033] The various aspects collectively involve wireless communication systems utilizing different power states. Some aspects more specifically relate to “on” power state transitions. In one example, the UE may receive a DL EOC indication from a network node that triggers a state indication. The UE also sends a state indication to the network node and based on the DL EOC indication, which indicates the state of: (i) the UE’s buffer or UE’s delay, and (ii) an estimated time indicating the time of arrival of the next UL packet. The UE may receive a power state switching indication from the network node that indicates an operating mode for the UE based on at least one of the states of the UE’s buffer, UE’s delay, or estimated time. The UE may switch to an operating mode for the UE based on the power state switching indication. The UE may send a UCI to the network node including code points for the UE, wherein the code points for the UE indicate at least one of: a first indication of delaying operation in a second mode, which consumes less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operating in the second mode based on the elapsed first time period; or a fourth indication of returning to the first mode or transitioning to the third mode based on the second time period. The UE can receive UL permission from the network node for UL services associated with data in the UE's buffer during a period after sending the status indication and before the estimated time. The UE can send UL services to the network node based on the UL permission during the period after sending the status indication and before the estimated time. The UE can send to the network node a capability indication of at least one of the UE's first capability to estimate service status or the UE's second capability to provide estimated time. The UE can autonomously switch to an operating mode for the UE after sending the status indication, wherein the operating mode for the UE is: a first mode, wherein the UE is configured to operate in UL mode and DL mode; a second mode, wherein the UE is configured to operate in UL mode instead of DL mode; a third mode, wherein the UE is configured to operate with the modem off; or a fourth mode, wherein the UE is configured to skip monitoring of the PDCCH. The UE can monitor wake-up signals (WUS) of sequence type from the network node while in operating mode. The UE can receive WUS of sequence type from the network node. The UE can switch to another mode among the first, second, third, or fourth modes based on the sequence type. In another example, a network node (or base station, etc.) may send a DL EOC indication that triggers a status indication to the UE. The network node may also receive a status indication from the UE and based on the DL EOC indication, which indicates the status of (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating to the UE the estimated time of arrival of the next UL packet.A network node may send a power state switching indication to the UE, which indicates an operating mode for the UE based on at least one of the UE's buffer state, the UE's delay state, or an estimated time state. The network node may receive from the UE a UCI including code points for the UE, wherein the code points for the UE indicate at least one of the following: a first indication of delayed operation in a second mode, which consumes less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operation in the second mode based on the elapsed first time period; or a fourth indication of returning to the first mode or transitioning to the third mode for wake-up based on the second time period. The network node may send a UL grant to the UE for UL services associated with data in the UE's buffer during a time period after sending the state indication and before the estimated time. The network node may receive UL services from the UE based on the UL grant during the time period after sending the state indication and before the estimated time. The network node may receive from the UE a capability indication of at least one of the UE's first capability to estimate service conditions or the UE's second capability to provide estimated time. The network node can receive from the UE an operation instruction for autonomous handover, instructing the UE to operate in a third mode or a second mode, wherein the operation instruction includes at least one of a UCI, a Media Access Control (MAC) Control Element (MAC-CE), or a UE Assistance Information (UAI). The network node can send a WUS to the UE including a sequence type, wherein the sequence type is associated with the UE handover to another mode for the UE, namely a first mode, a second mode, a third mode, or a fourth mode.

[0034] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In one example, by enhancing status reporting to include estimated time and / or delay reporting of UL data, the described techniques can be used to improve communication efficiency and reduce power consumption of devices associated with the wireless network. In another example, by utilizing a new MAC-CE introduced to include estimated arrival time or preferred permission configuration (e.g., for time, frequency (such as the number of RBs, the number of OFDM symbols, repetition, etc.)) instead of enhanced status reporting, the described techniques can be used to improve communication efficiency and reduce power consumption of devices associated with the wireless network. In an additional example, by utilizing a DL EOC indication that triggers status reporting, the described techniques can be used to further improve communication efficiency and reduce power consumption of wireless devices, as well as to quickly provide UE information to the base station without additional signaling. In another example, by monitoring various wake-up signals, the described techniques can be used to allow the UE to autonomously transition to different power states after providing status indication to the base station.

[0035] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0036] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0037] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0038] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium accessible to a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible to a computer.

[0039] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0040] Communication systems, such as 5G NR systems, can be deployed in various ways with a variety of components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0041] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0042] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0043] Figure 1Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0044] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media and / or transmit signals to one or more other units.

[0045] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0046] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0047] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that at least partially hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.) based on functional decomposition such as lower-layer functional decomposition, or both. In this architecture, the RU 140 can be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration allows the DU 130 and CU 110 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0048] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 111, via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0049] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0050] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and can be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0051] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each direction, the total number of carriers used for transmission can be up to [number missing]. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number] carriers. YA spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0052] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0053] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0054] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0055] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, and thus can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0056] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0057] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0058] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0059] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following systems / signals / sensors: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other position / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0060] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0061] Refer again Figure 1In some respects, UE 104 may have a power state transition component 198 (“Component 198”) configured to receive a downlink DL EOC indication triggering a state indication from a network node. Component 198 may also be configured to send a state indication to the network node and based on the DL EOC indication, the state indication indicating the state of: (i) the UE’s buffer or UE’s delay, and (ii) an estimated time indicating the time of arrival of the next UL packet for the UE. Component 198 may be configured to receive a power state transition indication from the network node, the power state transition indication indicating an operating mode for the UE based on at least one of the states of the UE’s buffer, UE’s delay, or estimated time. Component 198 may be configured to switch to an operating mode for the UE based on the power state transition indication. Component 198 can be configured to send a UCI to a network node including code points for the UE, wherein the code points for the UE indicate at least one of the following: a first indication of delayed operation in a second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication based on the elapsed first time period for operation in the second mode; or a fourth indication based on the second time period for returning to the first mode or transitioning to the third mode. Component 198 can be configured to receive UL permission from the network node for UL services associated with data in the UE's buffer during a time period after sending the status indication and before the estimated time. Component 198 can be configured to send UL services to the network node based on UL permission during a time period after sending the status indication and before the estimated time. Component 198 can be configured to send to the network node a capability indication of the UE, either a first capability of the UE to estimate the service status or a second capability of the UE to provide an estimated time. Component 198 can be configured to autonomously switch to an operating mode for the UE after sending a status indication, wherein the operating mode for the UE is: a first mode, wherein the UE is configured to operate in UL mode and DL mode; a second mode, wherein the UE is configured to operate in UL mode instead of DL mode; a third mode, wherein the UE is configured to operate with the modem off; or a fourth mode, wherein the UE is configured to skip monitoring of the PDCCH. Component 198 can be configured to monitor WUS, including sequence type, from network nodes while in the operating mode. Component 198 can be configured to receive WUS, including sequence type, from network nodes. Component 198 can be configured to switch to another mode among the first, second, third, or fourth modes for the UE based on the sequence type. In some aspects, base station 102 may have a power state transition component 199 (“Component 199”), which can be configured to send a DL EOC indication that triggers a status indication to the UE.Component 199 may also be configured to receive a status indication from the UE and based on a DL EOC indication, the status indication indicating the status of: (i) the UE's buffer or UE's delay, and (ii) an estimated time indicating the time of arrival of the next UL packet for the UE. Component 199 may be configured to send a power state switching indication to the UE, the power state switching indication indicating an operating mode for the UE based on at least one of the status of the UE's buffer, the UE's delay, or the estimated time. Component 199 may be configured to receive a UCI from the UE including code points for the UE, wherein the code points for the UE indicate at least one of: a first indication of delayed operation in a second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operation in the second mode based on the elapsed first time period; or a fourth indication of returning to the first mode or transitioning to the third mode for wake-up based on the second time period. Component 199 may be configured to send UL permission for UL services associated with data in the UE's buffer for a period after sending the status indication and before the estimated time. Component 199 can be configured to grant UL service access from the UE based on UL during a time period following the transmission of a status indication and preceding the estimated time. Component 199 can be configured to receive from the UE a capability indication from the UE of at least one of a first capability indicating that the UE estimates the service status or a second capability indicating that the UE provides an estimated time. Component 199 can be configured to receive from the UE an operation indication for autonomous handover to a third or second mode, wherein the operation indication includes at least one of UCI, MAC-CE, or UAI. Component 199 can be configured to transmit a WUS to the UE including a sequence type, wherein the sequence type is associated with a handover from the UE to another mode for the UE, either the first, second, third, or fourth mode. That is, the aspects used to enable power state transitions in this paper improve communication efficiency and reduce the power consumption of devices associated with the wireless network by enhancing state reports to include estimated time and / or delay reports of UL data, further improve communication efficiency and reduce the power consumption of wireless devices by utilizing DL EOC indications that trigger state reports, and quickly provide UE information to the base station without additional signaling, and also allow the UE to autonomously transition to different power states after providing state indications to the base station by monitoring various wake-up signals.

[0062] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2DFigure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0063] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled by 1 / SCS.

[0064]

[0065] Table 1: Parameter Set, SCS, and CP

[0066] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0067] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0068] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0069] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of Restricted Frames (RBs) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0070] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0071] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0072] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0073] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine the decoding and modulation scheme, as well as for spatial processing. Channel estimates can be derived from reference signals transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to different antennas 320 via a separate transmitter 318Tx. Each transmitter 318Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0074] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. Subsequently, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0075] The controller / processor 359 may be associated with at least one memory 360 storing program code and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0076] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0077] The TX processor 368 can use the channel estimate derived from the reference signal or feedback transmitted by the channel estimator 358 from the base station 310 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0078] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0079] The controller / processor 375 may be associated with at least one memory 376 storing program code and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0080] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform coupling. Figure 1 Various aspects of component 198. At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform combined Figure 1 The components of 199 are all aspects.

[0081] Traffic flows in wireless communication networks can exhibit various characteristics inherent to the network, including layer attributes, time frames for latency, power-saving configurations, etc. As an example, XR services for UL and DL may possess characteristics such as application layer attributes, short time frames for switching (where longer latency for traffic flows can degrade the user experience of XR applications or devices), and unbalanced traffic flows. Power-saving configurations for XR may include UL states triggered by inactivity or rapid triggering (e.g., via DCI) (e.g., no DL communication). Other configurations, such as those for PDCCH skipping, can save power by allowing the UE to skip monitoring of DL PDCCH data / information. PDCCH skipping refers to the UE skipping monitoring of the PDCCH for a period of time. The aspects presented in this paper provide improved granularity under DRX or C-DRX active-inactive states and C-DRX transitions designed for eMBB / voice services compared to inactive timers, and enable faster transitions between different power states. The aspects presented in this paper provide flexible SSSG state / PDCCH skipping that take into account quasi-periodic structures and provide additional granularity for power states (e.g., UL power states without DL monitoring). Further regarding PDCCH skipping, since no communication may occur when the UE is not monitoring the PDCCH (in both UL and DL), it can introduce latency into UL scheduling. To reduce UL scheduling latency, if the UE has urgent UL data to transmit, the UE can indicate the cessation of PDCCH skipping or overwrite the SSSG handover via the transmission of an SR (e.g., the UE can switch back to regular PDCCH monitoring to monitor uplink permission after transmitting the SR). The aspects presented in this paper provide transitions between power states, such as PDCCH skipping states, even without urgent UL data. In some aspects, the UE can cancel PDCCH skipping, and the base station (e.g., gNB, etc.) may have already transmitted redundant PDCCH skipping indications for the UE to put to sleep (whether this is a scheduled DCI or an unscheduled DCI—an unscheduled DCI could be in the form of a dummy permission with zero resource block allocation and used to indicate PDCCH skipping (e.g., not used for any other operation)). Furthermore, the base station (e.g., gNB, etc.) may not know / understand that the UE is about to transmit a positive SR so close to the PDCCH skip indication, which may also guarantee that the base station transmits redundant indications. Therefore, the aspects proposed in this paper provide improvements by which the base station (e.g., gNB, etc.) knows / understands the existence of UL data arriving sufficiently quickly, allowing the base station to make a better decision on whether to transmit the skip indication. The aspects proposed in this paper provide solutions covering transitions between entering and exiting power states.

[0082] The various aspects of power state transitions described in this paper improve communication efficiency and reduce power consumption of devices associated with the wireless network by enhancing state reporting to include estimated time of arrival (also known as estimated time of arrival (ETA)) and / or delay reporting of UL data. These aspects further improve communication efficiency and reduce power consumption of wireless devices by utilizing DL EOC indications that trigger state reporting, and by rapidly providing UE information to the base station without additional signaling. These aspects reduce communication latency while avoiding additional overhead. Some aspects also enable the UE to autonomously transition to different power states after providing state indications to the base station by monitoring various wake-up signals.

[0083] This paper presents various enhancements to enable rapid power state transitions for devices such as XR. The service model illustrates rapid handover between states for UL service (without DL service), DL service (without UL service), and UL and DL services. Therefore, new PHY / MAC signaling considering estimated arrival times in BSR and UL is proposed for each aspect of this paper to improve power performance. Furthermore, new signaling in DL is provided to enable rapid transitions from specific power states for the UE. Each aspect includes several specific design schemes proposed in this paper. Therefore, each aspect of this paper addresses state transitions and their design. Each aspect includes new BSR triggering based on receiving the DL EOC / its indication. Each aspect also provides enhanced BSRs to include new information to assist power state transitions. For example, this new information could be the estimated arrival time sent by the UL. Each aspect further allows the UE to autonomously transition to certain power states or make recommendations to be in certain power states, and utilizes wake-up signals (e.g., WUS (generally), low-power WUS (LP-WUS), etc.) for various state transitions.

[0084] Figure 4Figure 400 illustrates an example of an SR that overwrites (e.g., indicates or requests cancellation) a PDCCH skip and an SSSG handover. Figure 400 shows configuration 410 associated with PDCCH skipping and the UE transmitting an SR to overwrite, cancel, or request cancellation of PDCCH skipping. Figure 400 shows configuration 420 associated with an SSSG handover. PDCCH skipping can save power at the UE when it is not monitoring the PDCCH. Skipped PDCCH monitoring can increase latency, for example, because no communication may occur (in both UL and DL) when the UE is not monitoring the PDCCH. To reduce UL scheduling latency, the UE can indicate or request to stop PDCCH skipping and resume PDCCH monitoring via the transmission of an SR (as shown for configuration 410), or similarly stop or change the SSSG handover. As an example, if the UE has urgent UL data, the UE can transmit an SR as shown for configuration 420. The UE can switch back to regular PDCCH monitoring after transmitting the SR to monitor uplink permission in order to transmit UL data.

[0085] As shown for configuration 410, when the PDCCH monitoring adaptation field indicates to the UE that PDCCH monitoring should be skipped on the active DL BWP of the serving cell for a certain duration, the UE begins skipping PDCCH monitoring at the beginning of a first time slot, which is after the last symbol of a PDCCH reception with the DCI format having the PDCCH monitoring adaptation field. If, after the UE detects that the DCI format of the PDCCH monitoring adaptation field indicates to the UE that PDCCH monitoring should be skipped on the active DL BWP of the serving cell for that duration has been provided, the UE sends a PUCCH providing a positive SR, then the UE resumes PDCCH monitoring starting at the beginning of the first time slot, which is after the last symbol of a PUCCH transmission in all serving cells of the corresponding cell group. Similarly, as shown for configuration 420, when an SSSG handover indication is received via PDCCH, the UE can override the SSSG handover.

[0086] Figure 5This is an illustration 500 illustrating example XR services in various aspects. XR services can refer to wireless communications used in technologies such as Virtual Reality (VR), Mixed Reality (MR), and / or Augmented Reality (AR). VR can refer to a technology that immerses a user in a simulated experience similar to or different from the real world. Users can interact with a VR system through VR headsets or multi-projection environments that generate realistic images, sounds, and other sensations simulating the user's physical presence in the virtual environment. MR can refer to a technology in which aspects of virtual and real environments are mixed. AR can refer to a technology in which computer-generated perceptual information is used to enhance objects residing in the real world (sometimes across multiple sensory modalities such as vision, hearing, touch, somatosensory, and / or olfaction). AR systems can combine the real and virtual worlds, real-time interaction, and accurate 3D registration of virtual and real objects. In the example, an AR system can overlay sensory information (e.g., images) onto and / or mask real objects from a natural environment. XR services may include video and / or audio data. XR services can be sent by the base station and received by the UE, or XR services can be sent by the UE and received by the base station.

[0087] XR services can arrive periodically in bursts (“XR bursts”). XR bursts can vary in the number of packets in each burst and / or the size of each packet within a burst. Figure 500 illustrates a first XR stream 502 including a first XR burst 504 and a second XR burst 506. As illustrated in Figure 500, bursts can include different numbers of packets; for example, the first XR burst 504 is shown as having three packets (represented as rectangles in Figure 500), and the second XR burst 506 is shown as having two packets. Furthermore, as illustrated in Figure 500, the three packets in the first XR burst 504 and the two packets in the second XR burst 506 can differ in size; that is, the packets within the first XR burst 504 and the second XR burst 506 can include different amounts of data.

[0088] XR bursts can arrive in non-integer periods (i.e., within non-integer cycles). The period can differ from an integer number of symbols, time slots, etc. In the example, for 60 frames per second (FPS) video data, an XR burst can arrive in a period of 1 / 60 = 16.67 ms. In another example, for 120 FPS video data, an XR burst can arrive in a period of 1 / 120 = 8.33 ms.

[0089] The arrival time of XR services can vary. For example, an XR service burst may arrive earlier or later than the time the UE (or base station) expects the XR service burst to arrive and be available for transmission. The variability of packet arrival relative to the period (e.g., 16.76ms period, 8.33ms period, etc.) can be referred to as "jitter". In the example, the XR service jitter can range from -4ms (arriving earlier than expected) to +4ms (arriving later than expected). For example, as shown in the figure, referring to the first XR stream 502, the UE can expect the first packet of the first XR service burst 504 to arrive at time t0, but the first packet of the first XR service burst 504 arrives at time t1.

[0090] XR services may include multiple streams arriving at the UE (or base station) concurrently with each other (or within a threshold time period). For example, Figure 500 includes a second XR stream 508. The second XR stream 508 may have different characteristics than the first XR stream 502. For example, the second XR stream 508 may have XR service bursts with different numbers of packets, different packet sizes, etc. In one example, the first XR stream 502 may include video data, and the second XR stream 508 may include audio data for the video data. In another example, the first XR stream 502 may include internally decoded picture frames (I-frames) containing the complete image, and the second XR stream 508 may include predicted picture frames (P-frames) containing changes from previous images.

[0091] As noted herein, XR services may have an associated e2e PDB. If a packet does not arrive within the e2e PDB, the UE (or base station) may discard the packet. In the example, if a packet corresponding to a video frame of a video does not arrive at the UE within the e2e PDB, the UE may discard the packet because the video has progressed beyond that frame. However, considering the discarding of packets, the RDB at the UE may not be taken into account. Example time diagram 550 shows the time length corresponding to PDB 554. At a specific time point 556, the residual delay budget 552 is the remainder of PDB 554.

[0092] The overall PDB for XR services may include a portion for communication delays (e2e PDB) that allow data to be exchanged between the UE and a computing device (e.g., a server) hosting an application (e.g., for XR), and a portion for additional time after the communication delays but before the data is discarded (e.g., residual delay (e.g., RDB)). For example, Figure 500 includes a packet delay budget flow 510. The packet delay budget flow 510 illustrates a UE 512, a network entity 514 (e.g., a base station or a portion thereof), and a server 516 hosting an application 518. In the illustrated aspect, communication delay 520 is shown as including the RAN portion between the UE 512 and the network entity 514, and the CN portion between the network entity 514 and the server 516. Communication delay 520 can apply to both UL communication and DL communication. Additionally, residual delay 522 for DL ​​communication is shown at the UE 512, and residual delay 524 for UL communication is shown at the server 516. Communication delay 520 and residual delay 522 can constitute the overall PDB for DL ​​XR communication, for example, DL PDB 526. Similarly, communication delay 520 and residual delay 524 can constitute the overall PDB for UL XR communication (not shown for clarity).

[0093] Generally speaking, XR services are characterized by relatively high data rates and relatively low latency. Latency in XR services can affect user experience. For example, XR services can be applied to eMBB and URLLC services.

[0094] Figure 6 Call flowchart 600 illustrates various aspects of wireless communication. Call flowchart 600 illustrates the configuration of power state transitions performed by a UE (e.g., UE 602) capable of communicating with a network node (base station 604, such as a gNB or other type of base station, as an example, as shown). The aspects described for base station 604 can be performed by the base station in an aggregated manner and / or by one or more components of base station 604 in a decomposed manner. Additionally or alternatively, these aspects can be performed autonomously by UE 602, in addition to and / or as a substitute for the operation of base station 604.

[0095] In an illustrative aspect, UE 602 may be configured to provide capability indication 606 to base station 604. Capability indication 606 may be associated with at least one of the UE's first capabilities for providing information to base station 604 to enable power state transitions. In various aspects, capability indication 606 may indicate such capabilities of the UE as a first capability for the UE to estimate service conditions and / or a second capability for the UE to provide estimated time. The UE may optionally provide the granted estimated time and / or the granted magnitude.

[0096] UE 602 may be configured to receive DL EOC indication 608, and base station 604 may be configured to provide / transmit DL EOC indication 608. DL EOC indication 608 may be used as an indication / signaling for UE 602 to transition to another power state. DL EOC indication 608 may be included in or may be part of DL communication, such as data provided / transmitted from base station 604 via the DL channel. DL EOC indication 608 may be at least one of the following: End of Burst (EOB) indication, PDCCH skip indication, DRX MAC-CE, DL retransmission end indication, DL feedback indication (DFI) indicating an ACK for UL packets (e.g., an ACK indicating that all UL packets from the base station / gNB have been successfully decoded), and / or any equivalent DL signaling indicating that UE 602 has completed DL communication. As another example, EOC indication 608 may be L1 / L2 signaling indicating the end of cell DRX / DRX activity time. In various aspects, the DL EOC indication 608 can trigger the UE 602 to provide / transmit a status indication 610 of the UE 602 to the base station 604. The status indication 610 may include / indicate, but is not limited to, the status of the UE's buffer (e.g., a BSR, such as a BSR included in the MAC-CE), delay status or delay status report (DSR), an estimated time indicating the time of arrival of the next UL packet for the UE 602, etc. In various aspects, the DSR may be transmitted together with the BSR or as part of the BSR.

[0097] UE 602 can be configured to autonomously switch (at 612) to an operating mode for UE 602 based on Power State Switching Indication 614 and / or after Transmission State Indication 610. In each respect, UE 602 can switch (at 612) its power state based on Power State Switching Indication 614, or UE 602 can autonomously switch its power state (at 612) after Transmission State Indication 610: (i) a first mode in which UE 602 is configured to operate in both UL and DL modes; (ii) a second mode in which UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode in which UE 602 is configured to operate with the modem off; (iv) a fourth mode in which UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); or (v) a fifth mode in which UE 602 is configured to operate in DL mode instead of UL mode.

[0098] In aspects of the handover (at 612) based on the power state handover indication 614, the power state handover indication 614 may be based on or associated with the DL EOC indication 608. The power state handover indication 614 may be included in the DCI and may indicate that UE 602 operates in a third mode based on (i) the amount of data in UE 602's buffer is zero or (ii) UE 602's ability to delay the transmission of data packets, and / or indicate that UE 602 operates in a second mode based on the amount of data in UE 602's buffer being non-zero. In such aspects, UE 602 may be configured to provide / transmit a state indication 610 for the state of the indication buffer to base station 604 based on an estimated time. The estimated time may indicate that UE 602 estimates the arrival time of the next UL packet to be shorter than the sleep time used by UE 602 to enter sleep mode. Furthermore, in various aspects, the power state handover indication 614 provided / transmitted from base station 604 may indicate the operating mode for UE 602 as the second mode. Additionally, UE 602 may send a UCI (User Code Indicator) to base station 604, including code points for UE 602. The code points for UE 602 may indicate: a first indication of delayed operation in a second mode, where the second mode consumes less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operation in the second mode based on the elapsed first time period; a fourth indication of returning to the first mode or transitioning to the third mode based on the second time period; and so on. In various respects, the UCI may be based on and / or in response to a received DL EOC indication 608 from base station 604.

[0099] In aspects where the UE 602 autonomously performs the handover (at 612), the UE 602 can be configured to autonomously switch to (at 612) various operating modes. The operating modes can be: (i) a first mode, wherein the UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, wherein the UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, wherein the UE 602 is configured to operate with the modem off; (iv) a fourth mode, wherein the UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); (v) a fifth mode, wherein the UE 602 is configured to operate in DL mode instead of UL mode; and so on. In each aspect, the UE 602 can be configured to send an operation instruction to base station 604 instructing the UE 602 to operate in either the third or second mode. In each aspect, the operation instruction can include at least one of UCI, MAC-CE, or UAI. UE 602 can be configured to monitor WUS (e.g., WUS (generally), LP-WUS, etc.) from base station 604 when in an operating mode (e.g., an operating mode that UE 602 autonomously switches to). For example, in some aspects, when UE 602 monitors DL DCI, UE 602 can autonomously transition to a specific power state (e.g., to avoid UE 602 losing any DL grants that have arrived at UE 602). As another example, in some aspects, if UE 602 is allowed to switch to a power state that does not force UE 602 to monitor DL ​​DCI, UE 602 can be configured to monitor WUS from base station 604 when in an operating mode. UE 602 can also be configured to receive WUS including sequence types from base station 604 and switch to another mode, a first mode, a second mode, a third mode, or a fourth mode, based on the sequence type. In various respects, the sequence type can be: (i) a first sequence type that instructs UE 602 to wake up and operate in a fifth mode, in which UE 602 is configured to operate in DL mode instead of UL mode; (ii) a second sequence type that instructs UE 602 to restart the retransmission time for retransmission monitoring; (iii) a third sequence type that instructs UE 602 to wake up and operate in a second mode; (iv) a fourth sequence type that includes a bit payload in WUS, wherein the bit payload corresponds to the first sequence type, the second sequence type, or the third sequence type; (iv) a fifth mode, wherein UE 602 is configured to operate in DL mode instead of UL mode; and so on.

[0100] Figure 7This is illustrated in Figure 700, which shows the configuration 750 of example power states and associated code points for various aspects of power state transitions and the call flowchart 760 for wireless communication.

[0101] Configuration 750 illustrates, but is not limited to, power states and corresponding example characteristics, as well as associated code points and their corresponding operations. As a first example, a UL power state (e.g., no DL) for configuration grant (CG) is shown, which includes monitoring UL attitude instead of PDCCH, i.e., no retransmissions, no PDSCH monitoring, and a sleeping SCell BWP. As a second example, a UL power state (e.g., no DL) for dynamic grant (DG) is shown, which excludes monitoring of DL services, excludes monitoring of DL DCI, and includes monitoring of PDCCH for UL but not DL. As a third example, a DL power state (e.g., no DL) is shown, which includes monitoring of DL services but excludes monitoring of UL DCI or SR (or conditional SR). As a fourth example, DL and UL power states are shown, which include monitoring of both UL and DL DCI services. As a fifth example, a modem power-off state is shown, which includes one or more sleep states of the UE. As a sixth example, a DL SPS power state is shown, which includes monitoring of DL SPS but excludes monitoring of other signals.

[0102] Associated with the aforementioned power states are code points and operations for the UE. For example, code point "00" may be associated with the UE's DL and UL power states, code point "01" may be associated with the UE's UL power state (e.g., no DL monitoring), code point "10" may be associated with the UE's modem off power state, and code point "11" may be associated with the UE's PDCCH skip power state / mode. Therefore, code points indicate to the UE and / or the base station that the UE is about to switch to, is in, or expects to be in a given power state. It should be noted that the code points are shown and described in configuration 750 by way of example and not limitation, and other power states / operations may be associated with and / or substituted for the power states / operations used for the code points shown.

[0103] Call flowchart 760 is shown for wireless communication between UE 702 and base station 704, and may be as described above for... Figure 6 Another aspect of the described call flowchart 600.

[0104] UE 702 may be configured to receive DL EOC indication 706, and base station 704 may be configured to provide / transmit DL EOC indication 706. DL EOC indication 706 may be included in / may be part of DL communication, such as data provided / transmitted from base station 704 via the DL channel. In various respects, DL EOC indication 706 may trigger UE 702 to generate and / or provide / transmit UE 702 status indication 710 to base station 704. DL EOC indication 706 may be at least one of the following: EOB indication, PDCCH skip indication, DRX MAC-CE, DL retransmission end indication, DFI indicating ACK for UL packets (e.g., ACK indicating that all UL packets from base station / gNB have been successfully decoded), and / or any equivalent DL signaling indicating that UE 702 has completed DL communication. As another example, EOC indication 706 may be L1 / L2 signaling indicating the end of cell DRX / DRX activity time. The UE may generate (at 708) a status indication 710 based on and / or in response to the received DL EOC indication 706. The status indication 710 may include / indicate, but is not limited to, the status of the UE's buffer (e.g., a BSR, such as a BSR included in the MAC-CE), delay status or delay status report (DSR), an estimated time indicating the time of arrival of the next UL packet for UE 702, etc. UE 702 may be configured to provide / transmit the status indication 710 of UE 702, which can be received by base station 704, based on a trigger caused by the DL EOC indication 706.

[0105] UE 702 can be configured to switch to (as described above) an operating mode for UE 702 based on a power state switching indication 712 provided / transmitted by base station 704. The power state switching indication 712 may be included in the DCI and may indicate UE 702 to operate in a third mode based on (i) the amount of data in UE 702's buffer being zero or (ii) UE 702's ability to delay the transmission of data packets, and / or indicate UE 702 to operate in a second mode based on the amount of data in UE 702's buffer being non-zero.

[0106] Figure 8 This is an example diagram 800 illustrating various aspects of power state-specific UCI code points and conditional DCI. Diagram 800 shows call flowcharts 850 and 860 for wireless communication between UE 802 and base station 804. Call flowcharts 850 and / or 860 can be as described above for... Figure 6 Another aspect of the described call flowchart 600.

[0107] In call flowchart 850, UE 802 can be configured to receive DL EOC indication 806, and base station 804 can be configured to provide / transmit DL EOC indication 806. DL EOC indication 806 may be included in / may be a part of DL communication, such as data provided / transmitted from base station 804 via DL channel, and may be... Figure 6 DL EOC indicates 608 and / or Figure 6 The DL EOC in the text indicates another aspect of 706.

[0108] UE 802 can be configured to provide / transmit UCI 808, and base station 804 can be configured to receive the UCI. UCI 808 can be provided / transmitted by UE 802 based on or in response to a received DL EOC indication 806. UCI 808 may include code points for UE 802 indicating: (i) a first indication of delayed operation in a second mode, which consumes less power than the first mode; (ii) a second indication that operation in the second mode is acceptable; (iii) a third indication of operation in the second mode based on the elapsed first time period; (iv) a fourth indication of returning to the first mode or transitioning to the third mode based on the second time period; and so on. Therefore, in various respects, base station 804 can be configured to provide / transmit a power state switching indication 810 based on the UCI 808 with code points, which UE 802 can receive.

[0109] In the first example, via power state switching indication 810, base station 804 may trigger a state indication (e.g., BSR, delay state, and / or estimated time), or DL ​​EOC indication 806 may trigger a state indication as described herein if the state indication indicates that UE 802's buffer is non-zero and / or UE 802 is delay-intolerant. UE 802 may be transferred to a UL power state (e.g., not monitoring DL traffic) without via power state switching indication 810, which has a lower power than both DL and UL power states. In the second example, via power state switching indication 810, if the state indication indicates that UE 802's buffer is zero and the estimated arrival time of the next UL data packet is insufficient to enter sleep mode (e.g., for UE 802 entering sleep, microsleep, deep sleep, ultra-deep sleep, etc.), and subsequently transitioning from sleep to an on state (e.g., ... Figure 7If the power state configuration 750 (non-sleep state) is inefficient (e.g., in terms of DCI bits), then base station 804 can trigger a state indication (e.g., BSR, delay state, and / or estimated time). A configurable threshold for the estimated time is configurable, such that if the estimated time is less than or equal to the threshold, UE 802 is not transferred to sleep. In the third example, via power state switching indication 810, if the state indication indicates that UE 802's buffer is zero and the estimated time is long enough for UE 802 to enter a sleep state, then base station 804 can trigger a state indication (e.g., BSR, delay state, and / or estimated time), UE 802 can be transferred to sleep until the estimated time, and UE 802 can sleep based on the available time. In various aspects, the time for transitioning to another power state can also be considered to determine which sleep state UE 802 should enter.

[0110] In some respects, even if the base station / network node does not have a status indication, as described herein, the base station / network node can transmit a conditional DCI indication for power state transition to the UE.

[0111] In call flowchart 860, UE 802 can be configured to receive DL EOC indication 812, and base station 804 can be configured to provide / transmit DL EOC indication 812. DL EOC indication 812 may be included in / may be a part of DL communication, such as data provided / transmitted from base station 804 via DL channel, and may be... Figure 6 DL EOC indicates 608 and / or Figure 6 Another aspect of the DL EOC indication 706. In the illustrative aspect, base station 804 may not receive a status indication as described herein from UE 802. However, base station 804 may be configured to provide / transmit a power state switching indication 814 to UE 802 (e.g., as a conditional DCI) in the absence of a status indication.

[0112] UE 802 can be configured to switch to (as described above) an operating mode for UE 802 based on a power state switching indication 814 provided / transmitted by base station 804. The power state switching indication 814 can be included in a conditional DCI and, as a first option, can indicate to UE 802 that: (i) if the amount of data waiting in UE 802's buffer is zero, it will transition to a sleep state, or (ii) UE 802 can safely wait for the next cycle to transmit packets because UE 802 is configured to be latency-tolerant. As a second option, if the amount of data waiting in UE 802's buffer is non-zero, UE 802 can transition to a UL power state / mode (e.g., no DL service monitoring). In various respects, UE 802 can be configured to report (e.g., provide / transmit) back (e.g., receive) to base station 804 via UCI, MAC-CE, or UAI which of the two states / modes it will be in (e.g., operating state 818 of UE 802). In various aspects, RRC signaling (such as UAI) may include periodic recommendations from UE 802 for preferred power states (e.g., when there is cross-layer optimization between the application and the modem of UE 802, UE 802 may know its UL services better than base station 804).

[0113] Figure 9 Figure 900 illustrates examples of DL and UL transmissions associated with power state and estimated time (or ETA) in various aspects. Figure 900 shows configurations 910, 920, and 930 in the context of transmission of DL dataset 902 (e.g., DL burst) and UL dataset 904 (e.g., UL burst) with respect to estimated time 906 (“ETA”). In various aspects, DL dataset 902 may include DL EOC indication 905, as described herein.

[0114] In the example of configuration 910, the UE initially operates in a power state for DL ​​service monitoring (e.g., no UL service monitoring). DL data set 902 ends, and DL EOC indication 905 is received by the UE. In the example of configuration 910, the UE estimates the arrival time 906 of the next UL packet to be no less than (e.g., longer than) the sleep time the UE uses to enter a sleep mode (such as microsleep, deep sleep, hyper-deep sleep, etc.). Therefore, the UE is transmitted to sleep while waiting for UL data set 904 (e.g., the next UL packet). In all respects, when UL data set 904 arrives, the UE can wake up and enter a UL power state to transmit UL data set 904 (e.g., the second mode described above, where the UE is configured to operate in UL mode instead of DL mode). As noted herein, the UE may provide / transmit the estimated time 906, along with buffer states and / or delay states, to the base station / network node.

[0115] In the example of configuration 920, the UE initially operates in a power state used for DL ​​service monitoring (e.g., no UL service monitoring). DL dataset 902 ends, and DL EOC indication 905 is received by the UE. In the example of configuration 920, the estimated time 906 for the arrival of the next UL packet is shorter than the sleep time the UE uses to enter a sleep mode (such as microsleep, deep sleep, hyper-deep sleep, etc.). That is, the ETA estimated time in the example of configuration 920 may indicate that there is not enough time for the UE to enter a sleep mode before the arrival of UL dataset 904. Therefore, the UE may not be transmitted to sleep while it waits for UL dataset 904 (e.g., the next UL packet), but may enter / transition to a UL power state to transmit UL dataset 904 (e.g., the second mode mentioned above, where the UE is configured to operate in UL mode instead of DL mode). As noted herein, the UE may provide / transmit the estimated time 906, along with buffer states (such as BSR) and / or delay states, to the base station / network node. In all aspects, if the UE does not want to sleep, for example because the estimated time 906 is too short to allow sleep, the UE can transmit a BSR, which avoids the UE transmitting unnecessary BSRs.

[0116] In the example of configuration 930, the UE initially operates in a power state for DL ​​service monitoring (e.g., no UL service monitoring). In configurations 910 / 920, when DL dataset 902 ends, the UE receives a DL EOC indication 905 to trigger an estimation of the estimated time 906 (and the buffer / delay state in each aspect). In the example of configuration 930, the estimated time 906 may or may not be estimated in each aspect because UL dataset 904 has arrived and there is a DL / UL overlap 908 with DL dataset 902. Therefore, the UE may not be transferred to sleep, but may instead enter / transition to a DL and UL power state to send UL dataset 904 when DL dataset 902 is received (e.g., the first mode described above, where the UE is configured to operate simultaneously in UL and DL modes—in each aspect, this may be based on the received PUCCH indicating a positive SR). When DL dataset 902 ends, the UE's buffer is non-zero because UL dataset 904 has arrived. Therefore, the UE can be entered / transitioned to UL power state instead of being sent to sleep to continue transmitting UL dataset 904.

[0117] Figure 10Figure 1000 illustrates example UL-approved actions following state indication and wake-up signal monitoring for autonomous power state transitions in various aspects. Figure 1000 shows call flowcharts 1050 and 1060 for wireless communication between UE 1002 and base station 1004. Call flowcharts 1050 and / or 1060 can be as described above for... Figure 6 Another aspect of the described call flowchart 600.

[0118] As described herein, the UE can enter various operating modes / power states associated with receiving a DL EOC indication. However, aspects also provide for the UE to process and transmit UL data packets for services in the UE buffer, as reported by a status indication (e.g., via a BSR).

[0119] In call flow diagram 1050, upon receiving the DL EOC indication, as noted herein, UE 1002 may be configured to provide / transmit a status indication 1006 that can be received by base station 1004. Status indication 1006 may include, but is not limited to, buffer status (e.g., BSR), delay status, estimated time, etc. In a scenario where UE 1002's buffer is non-zero and there are data packets to be transmitted via the UL channel, UE 1002 may be configured to receive at least one UL grant 1008 from base station 1004 and, in response, provide the associated UL data service 1010 to base station 1004.

[0120] Call flowchart 1060 illustrates an example wireless communication for a power state transition proposed by the UE. For example, after transmitting a UL EOC indication or a zero-buffer state report, the UE 1002 can be configured to autonomously transition to any state it prefers (e.g., as described above for...). Figure 6 As described (at 612)). However, this leads to a misunderstanding with base station 1004, which may not be aware of the autonomous transition (e.g., base station 1004 may believe that UE 1002 is still monitoring DCI, while UE 1002 has entered a low-power state / mode, such as a low-power mode for UL services instead of DL services, a low-power mode for modem shutdown, a low-power mode for a specific sleep state, etc.). Therefore, UE 1002 may miss UL retransmissions, may miss DL grants, etc.

[0121] In this scenario, UE 1002 can be configured to provide / transmit an operation indication 1012 to base station 1004. The operation indication 1012 can indicate to base station 1004 which power state / operation mode (e.g., the first mode, second mode, third mode, fourth mode, fifth mode, etc., described below) UE 1002 has autonomously entered. This makes base station 1004 aware of UE 1002's autonomous transition. When in the desired power state / operation mode that UE 1002 has autonomously entered, UE 1002 can be configured to monitor (at 1014) a WUS 1016 with a sequence type (e.g., WUS (generally), low-power WUS (LP-WUS), etc.) from base station 1004. WUS 1016 may include sequence type 1020.

[0122] UE 1002 can be configured to receive WUS 1016 with sequence type 1020 from base station 1004. The sequence type 1020 included / included in the WUS along with the WUS can be: a first sequence type that instructs the UE to wake up and operate in a fifth mode, in which the UE is configured to operate in DL mode instead of UL mode (e.g., if UE 1002 autonomously decides to be in DL power state, then UE 1002 can remain in DL power state after this type of WUS; if UE 1002 autonomously decides to be in UL power state, then UE 1002 can move to DL power state, and if UE 1002 autonomously decides to be in DL power state, then UE 1002 can remain in DL power state after this type of WUS); a second sequence type that instructs the UE to restart the retransmission time for retransmission monitoring; and a third sequence type that instructs the UE to wake up and operate in a second mode (e.g., if UE 1002 autonomously decides to be in UL power state, then UE 1002 can remain in UL power state after this type of WUS; ... If UE 1002 autonomously decides to be in the DL power state, then UE 1002 can move to the UL power state, and if UE 1002 autonomously decides to be in the UL power state, then UE 1002 can remain in the UL power state after this type of WUS; a fourth sequence type, which includes the payload of bits in the WUS, wherein the payload of bits corresponds to the first sequence type, the second sequence type, or the third sequence type; a fifth mode, wherein the UE is configured to operate in DL mode instead of UL mode; and so on. Based on WUS 1016 and sequence type 1020, UE 1002 can be configured to switch (at 1018) to another mode among the first, second, third, or fourth modes for the UE based on sequence type 1020.

[0123] Therefore, UE 1002 is allowed to autonomously transition from higher power states (e.g., from DL and UL states) to lower power states (e.g., UL power state, modem off power state, DL power state), and to achieve this efficiently, UE 1002 is configured to monitor (at 1018) WUS, LP-WUS, etc., to transition to different power states, which can be indicated by base station 1004 in WUS 1016. In all respects, when UE 1002 is allowed to autonomously move to a certain power state, base station 1004 can configure LP-WUS for UE 1002 for this purpose.

[0124] Figure 11This is a flowchart 1100 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, 602, 702, 802, 1002; device 1504). In some aspects, the method may include combining... Figure 6 The communication process described in the document covers various aspects and / or Figures 7 to 10 The method provides enabling power state transitions, which improves communication efficiency and reduces power consumption of devices associated with the wireless network by enhancing state reporting to include estimated time and / or delay reports of UL data, further improves communication efficiency and reduces power consumption of wireless devices by utilizing DL EOC indications that trigger state reporting, and rapidly provides UE information to the base station without additional signaling, and also allows the UE to autonomously transition to different power states after providing state indications to the base station by monitoring various wake-up signals.

[0125] At 1102, the UE receives a DL EOC indication from the network node. As an example, this reception may be performed at least in part by component 198. Figures 6 to 10 An example is shown where UE 602 receives such a DLEOC indication from a network node (e.g., base station 604).

[0126] UE 602 can be configured to provide capability indication 606 to base station 604. Capability indication 606 may be associated with at least one of the UE's first capabilities for providing information to base station 604 to enable power state transitions. In various aspects, capability indication 606 may indicate such capabilities of the UE as a first capability for the UE to estimate service conditions and / or provide the UE with an estimated time (e.g., Figure 9 The second capability (906, 908 in the original text). UE 602 can be configured to receive DL EOC indication 608 (e.g., ...). Figure 7 706 in the middle; Figure 8 (e.g., 806, 812), and base station 604 can be configured to provide / transmit DL EOC indication 608 (e.g., Figure 7 706 in the middle; Figure 8 (806, 812 in the text). DL EOC indicates 608 (e.g., Figure 7 706 in the middle; Figure 8806, 812) may be included in / may be part of DL communication, such as data provided / transmitted from base station 604 via DL channel. DLEOC indication 608 may be at least one of the following: EOB indication, PDCCH skip indication, DRX MAC-CE, DL retransmission end indication, DFI indicating ACK for UL packets (e.g., ACK for all UL packets from base station / gNB successfully decoded), and / or any equivalent DL signaling indicating that UE 602 has completed DL communication. As another example, EOC indication 608 may be L1 / L2 signaling indicating the end of cell DRX / DRX activity time.

[0127] At 1104, the UE sends a status indication to the network node based on the DL EOC indication, which indicates the status of: (i) the UE's buffer or UE delay, and (ii) an estimated time indicating the time when the UE estimates the arrival of the next UL packet. As an example, this transmission may be performed at least in part by component 198. Figures 6 to 10 An example of UE 602 sending such a status indication to a network node (e.g., base station 604) is shown.

[0128] In all respects, DL EOC indicates 608 (e.g., Figure 7 706 in the middle; Figure 8 (806, 812) can trigger UE 602 to provide / send UE 602 status indication 610 to base station 604 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the middle). Status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the table may include / indicate, but is not limited to, the state of the UE's buffer (e.g., BSR, such as the BSR included in MAC-CE), delay status or delay status report (DSR), and an estimated time indicating to the UE 602 the arrival time of the next UL packet (e.g., Figure 9 (e.g., 906, 908). UE 602 can be configured to switch based on power state indication 614 (e.g., ...). Figure 7 712 in the middle; Figure 8 810, 814) and / or by UE 602 in the transmission status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, autonomously (e.g., Figure 10 In 1060) switch (at 612) to the operating mode for UE 602. In various aspects, UE 602 can switch based on power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 UE 602 can switch the power state (at 612) using 810, 814 in the transmission status indication 610, or ... Figure 7 710 in the middle; Figure 10 After 1006 in the middle, it autonomously switches the power state (at 612) (e.g., Figure 10 1060 in the above): (i) a first mode, wherein UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, wherein UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, wherein UE 602 is configured to operate with the modem off; (iv) a fourth mode, wherein UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); or (v) a fifth mode, wherein the UE is configured to operate in DL mode instead of UL mode (e.g., ... Figure 7 750 in the middle; Figure 8 816 in the middle; Figure 10 (1018 in the middle).

[0129] Figure 12 This is a flowchart 1200 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, 602, 702, 802, 1002; device 1504). In some aspects, the method may include combining... Figure 6 The communication process described in the document covers various aspects and / or Figures 7 to 10 The method provides enabling power state transitions, which improves communication efficiency and reduces power consumption of devices associated with the wireless network by enhancing state reporting to include estimated time and / or delay reports of UL data, further improves communication efficiency and reduces power consumption of wireless devices by utilizing DL EOC indications that trigger state reporting, and rapidly provides UE information to the base station without additional signaling, and also allows the UE to autonomously transition to different power states after providing state indications to the base station by monitoring various wake-up signals.

[0130] At 1202, the UE transmits to the network node a capability indication of at least one of the UE's first capability to estimate service conditions or the UE's second capability to provide estimated time. As an example, this transmission may be performed at least in part by component 198. Figures 6 to 10 An example is shown where UE 602 sends such a capability indication to a network node (e.g., base station 604).

[0131] UE 602 can be configured to provide capability indication 606 to base station 604. Capability indication 606 may be associated with at least one of the UE's first capabilities for providing information to base station 604 to enable power state transitions. In various aspects, capability indication 606 may indicate such capabilities of the UE as a first capability for the UE to estimate service conditions and / or provide the UE with an estimated time (e.g., Figure 9 The second ability of 906 and 908 in the middle.

[0132] At 1204, the UE receives a DL EOC indication from the network node. As an example, this reception may be performed at least in part by component 198. Figures 6 to 10 An example is shown where UE 602 receives such a DLEOC indication from a network node (e.g., base station 604).

[0133] UE 602 can be configured to receive DL EOC indication 608 (e.g., Figure 7 706 in the middle; Figure 8 (e.g., 806, 812), and base station 604 can be configured to provide / transmit DL EOC indication 608 (e.g., Figure 7 706 in the middle; Figure 8 806, 812 (in the DLEOC instruction 608, e.g., ) Figure 7 706 in the middle; Figure 8 806, 812) may be included in / may be part of DL communication, such as data provided / transmitted from base station 604 via DL channel. DL EOC indication 608 may be at least one of the following: EOB indication, PDCCH skip indication, DRX MAC-CE, DL retransmission end indication, DFI indicating ACK for UL packets (e.g., ACK for all UL packets from base station / gNB successfully decoded), and / or any equivalent DL signaling indicating that UE 602 has completed DL communication. As another example, EOC indication 608 may be L1 / L2 signaling indicating the end of cell DRX / DRX activity time.

[0134] At 1206, the UE sends a status indication to the network node based on the DL EOC indication, which indicates the status of: (i) the UE's buffer or UE delay, and (ii) an estimated time indicating the time when the UE estimates the arrival of the next UL packet. As an example, this transmission may be performed at least in part by component 198. Figures 6 to 10 An example of UE 602 sending such a status indication to a network node (e.g., base station 604) is shown.

[0135] In all respects, DL EOC indicates 608 (e.g., Figure 7706 in the middle; Figure 8 (806, 812) can trigger UE 602 to provide / send UE 602 status indication 610 to base station 604 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the middle). Status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the table may include / indicate, but is not limited to, the state of the UE's buffer (e.g., BSR, such as the BSR included in MAC-CE), delay status or delay status report (DSR), and an estimated time indicating to the UE 602 the arrival time of the next UL packet (e.g., Figure 9 (e.g., 906, 908).

[0136] At 1208, the UE determines whether it is waiting for UL permission for data to be sent from the UE's buffer. As an example, this determination may be performed at least in part by component 198. If yes, flowchart 1200 proceeds to 1210; if no, flowchart 1200 proceeds to 1212.

[0137] At 1210, during the time period following the transmission status indication and preceding the estimated time, the UE receives from the network node a UL grant for UL services associated with data in the UE's buffer, and transmits UL services to the network node based on the UL grant. As an example, this reception and transmission can be performed at least partially by component 198. Figure 6 and Figure 10 An example of UE 602 receiving UL permission and transmitting UL data for a network node (e.g., base station 604) is illustrated.

[0138] As described herein, the UE can enter various operating modes / power states associated with receiving the DL EOC indication. However, aspects also provide for the UE to process and transmit UL data packets for services in the UE buffer, as reported by a status indication (e.g., via BSR). In call flow diagram 1050, after receiving the DL EOC indication, as noted herein, UE 1002 (e.g., Figure 6 602 in the middle can be configured to provide / transmit information that can be provided by base station 1004 (e.g., Figure 6 The status indication 1006 received by (604) may include, but is not limited to, buffer status (e.g., BSR), delay status, estimated time (e.g., ...). Figure 9(e.g., 906, 908). In a scenario where the buffer of UE 1002 is non-zero and there are data packets to be transmitted via the UL channel, UE 1002 can be configured to receive at least one UL grant 1008 from base station 1004 and, in response, provide the associated UL data service 1010 to base station 1004.

[0139] At 1212, the UE determines whether it will perform an autonomous power state switch. As an example, this determination may be performed at least partially by component 198. If yes, flowchart 1200 proceeds to 1222; if no, flowchart 1200 proceeds to 1214.

[0140] At 1214, the UE determines whether it will provide / transmit a UCI with the UE's code points to the network node. As an example, this determination may be performed at least in part by component 198. If yes, flowchart 1200 proceeds to 1216; if no, flowchart 1200 proceeds to 1218.

[0141] At 1216, the UE transmits a UCI to the network node including code points for the UE, wherein the code points for the UE indicate at least one of the following: a first indication of delayed operation in a second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operation in the second mode based on the elapsed first time period; or a fourth indication of returning to the first mode or transitioning to the third mode based on the second time period. As an example, this transmission may be performed at least in part by component 198. Figure 6 and Figure 8 An example of UE 602 sending such a UCI to a network node (e.g., base station 604) is illustrated.

[0142] UE 602 can be configured to send code points (e.g., for UE 602) to base station 604. Figure 7 The UCI (e.g., 750) in the middle) Figure 8 808 in the middle). UCI 808 may be based on or in response to the received DL EOC instruction 608 (e.g., Figure 7 706 in the middle; Figure 8 The code points (806, 812) used in UE 602 are provided / transmitted. Figure 7 The 750 in the text can indicate: a first indication of delaying operation in a second mode, where the second mode consumes less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication based on the elapsed first time period for operation in the second mode; a fourth indication based on the second time period for returning to the first mode or transitioning to the third mode; and so on. In various respects, UCI (e.g., Figure 8808 in the middle) may be based on and / or in response to the received DL EOC indication 608 from base station 604 (e.g., Figure 7 706 in the middle; Figure 8 (806, 812).

[0143] At 1218, the UE receives a power state switching indication from the network node, which indicates the operating mode for the UE based on at least one of the UE's buffer, the UE's delay, or the state of an estimated time. As an example, this reception may be performed at least partially by component 198. Figures 6 to 10 An example is shown where UE 602 receives such a power state switching indication from a network node (e.g., base station 604).

[0144] UE 602 may receive a power state switching indication 614 provided / transmitted from base station 604 (e.g., Figure 7 712 in the middle; Figure 8 (810, 814 in the middle). Figure 7 In the context of the DCI, the power state switching indication 712 provided / transmitted by base station 704 may be included in the DCI and may indicate that UE 702 operates in a third mode based on (i) the amount of data in UE 702's buffer is zero or (ii) UE 702's ability to delay the transmission of data packets, and / or indicate that UE 702 operates in a second mode based on the amount of data in UE 702's buffer being non-zero. Figure 8 In the context (850), base station 804 can be configured to provide / transmit power state switching indication 810 based on UCI 808 with code points, which UE 802 can receive. Through power state switching indication 810, in the first example, base station 804 can trigger state indications (e.g., BSR, delay state, and / or estimated time) (e.g., ...). Figure 9 (906, 908 in the document), or if the status indication indicates that the buffer of UE 802 is non-zero and / or UE 802 is latency-intolerant, then the DL EOC indication 806 may trigger the status indication as described herein. UE 802 may be transferred to a UL power state (e.g., not monitoring DL traffic) instead of via the power state switching indication 810, which has a lower power than the DL and UL power states. In the second example, via the power state switching indication 810, if the status indication indicates that the buffer of UE 802 is zero and the estimated arrival time of the next UL data packet (e.g., ...) is... Figure 9 906 and 908 in the code are insufficient to enter sleep mode (e.g., for UE 802, entering sleep, microsleep, deep sleep, ultra-deep sleep, etc., and subsequently transitioning from sleep to on state (e.g., Figure 7 If the power state of configuration 750 (non-sleep state) is inefficient (e.g., in terms of DCI bits), then base station 804 can trigger a state indication (e.g., BSR, delay state, and / or estimated time). Configurable for estimated time (e.g., Figure 9 The configurable thresholds (906, 908) in the data allow for estimation of time (e.g., ...) Figure 9 If 906 and 908 in the above values ​​are less than or equal to the threshold, then UE 802 will not be transferred to sleep mode. In the third example, via power state switching indication 810, if the state indication indicates that UE 802's buffer is zero and the estimated time (e.g., ...) is... Figure 9 If 906 and 908 in the timeline are long enough to put UE 802 into a sleep state, then base station 804 can trigger a status indication (e.g., BSR, delay status, and / or estimated time) (e.g., ...). Figure 9 (906, 908 in the original text), UE 802 can be sent to sleep until the estimated time (e.g., Figure 9 (906, 908 in the document), and UE 802 can sleep based on available time. In various aspects, the time for transitioning to another power state can also be considered to determine which sleep state UE 802 should enter. In some aspects, even if the base station / network node does not provide a state indication, as described herein, the base station / network node can transmit a conditional DCI indication for power state transition to the UE. Figure 8 In the context of (860), the power state switching indication 814 may be included in the conditional DCI and, as a first option, may indicate to UE 802 that: (i) if the amount of data waiting in UE 802's buffer is zero, then it will transition to a sleep state, or (ii) UE 802 may safely wait for the next cycle to send packets because UE 802 is configured to be latency tolerant. As a second option, if the amount of data waiting in UE 802's buffer is non-zero, then UE 802 may transition to a UL power state / mode (e.g., no DL service monitoring). In all respects, UE 802 may be configured to report (e.g., provide / send) back (e.g., receive) to base station 804 via UCI, MAC-CE, or UAI which of the two states / modes it will be in (e.g., UE 802's operating state 818). In various aspects, RRC signaling (such as UAI) may include periodic recommendations from UE 802 for preferred power states (e.g., when there is cross-layer optimization between the application and the modem of UE 802, UE 802 may know its UL services better than base station 804).

[0145] At 1220, the UE switches to an operating mode for the UE based on a power state switching indication. As an example, this switching may be performed at least partially by component 198. Figures 6 to 10 An example is shown where UE 602 switches such a power state based on a power state switching indication from a network node (e.g., base station 604).

[0146] UE 602 can be configured to switch based on power state indication 614 (e.g., Figure 7 712 in the middle; Figure 8 810, 814) and / or by UE 602 in the transmission status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, autonomously (e.g., Figure 10 In 1060) switch (at 612) to the operating mode for UE 602. In various aspects, UE 602 can switch based on power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 UE602 can switch the power state (at 612) using 810, 814, or UE602 can do so at transmit status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, it autonomously switches the power state (at 612) (e.g., Figure 10 (1060 in the above): (i) a first mode, wherein UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, wherein UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, wherein UE 602 is configured to operate with the modem off; (iv) a fourth mode, wherein UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); or (v) a fifth mode, wherein UE 602 is configured to operate in DL mode instead of UL mode.

[0147] The switching (at 612) is based on the power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 In terms of aspects of 810, 814), power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 810, 814 in the above) may be based on or associated with DL EOC indication 608. Power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8810, 814) may be included in the DCI and may instruct UE 602 to operate in a third mode based on (i) the amount of data in UE 602's buffer being zero or (ii) UE 602's ability to delay the transmission of data packets, and / or instruct UE 602 to operate in a second mode based on the amount of data in UE 602's buffer being non-zero. In such respect, UE 602 may be configured to operate based on estimated time (e.g., Figure 9 (906, 908) to provide / transmit status indication 610 for the status of the indication buffer of base station 604 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the middle). Estimated time (e.g., Figure 9 (906, 908) can instruct UE 602 to estimate that the arrival time of the next UL packet is shorter than the sleep time used by UE 602 to enter sleep mode. Furthermore, in various aspects, the power state switching indication 614 provided / transmitted by base station 604 can indicate the operating mode for UE 602 as a second mode. Additionally, UE 602 can send a UCI including code points for UE 602 to base station 604. The code points for UE 602 can indicate: a first indication of delayed operation in the second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operation in the second mode based on the elapsed first time period; a fourth indication of returning to the first mode or transitioning to the third mode based on the second time period; and so on. In various aspects, the UCI can be based on and / or in response to a received DL EOC indication 608 from base station 604.

[0148] At 1222, after sending a status indication, the UE autonomously switches to the operating mode for the UE. As an example, this switch can be performed at least partially by component 198. Figures 6 to 10 An example of UE 602 autonomously switching such power states is shown.

[0149] UE 602 can be configured to switch based on power state indication 614 (e.g., Figure 7 712 in the middle; Figure 8 810, 814) and / or by UE 602 in the transmission status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, autonomously (e.g., Figure 10 In 1060) switch (at 612) to the operating mode for UE 602. In various aspects, UE 602 can switch based on power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8UE602 can switch the power state (at 612) using 810, 814, or UE602 can do so at transmit status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, it autonomously switches the power state (at 612) (e.g., Figure 10 (1060 in the above): (i) a first mode, wherein UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, wherein UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, wherein UE 602 is configured to operate with the modem off; (iv) a fourth mode, wherein UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); or (v) a fifth mode, wherein UE 602 is configured to operate in DL mode instead of UL mode.

[0150] When executed autonomously by UE 602 (e.g., Figure 10 In terms of various aspects of the handover (at 612) (at 1060), UE 602 can be configured to autonomously (e.g., Figure 10 (1060) Switches to (at 612) various operating modes. The operating modes can be: (i) a first mode, in which UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, in which UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, in which UE 602 is configured to operate with the modem off; (iv) a fourth mode, in which UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); (v) a fifth mode, in which UE 602 is configured to operate in DL mode instead of UL mode; and so on.

[0151] At 1224, the UE transmits an operation instruction to the network node instructing the UE to operate in either the third mode or the second mode, wherein the operation instruction includes at least one of UCI, MAC-CE, or UAI. As an example, this transmission may be performed at least partially by component 198. Figures 6 to 10 An example of UE 602 sending such an operational instruction to a network node (e.g., base station 604) is illustrated.

[0152] In all respects, UE 602 can be configured to send an operation instruction to base station 604 instructing UE 602 to operate in the third mode or the second mode (e.g., Figure 8 818 in the middle; Figure 10 1012 in the middle). In all aspects, operating instructions (e.g., Figure 8 818 in the middle; Figure 101012) may be included in at least one of UCI, MAC-CE, or UAI. Figure 10 In the context of UE 1002 (e.g., Figure 6 602 in the configuration can be configured to provide / transmit an operation instruction 1012 to base station 1004 (e.g., 1004). The operation instruction 1012 can indicate to base station 1004 which power state / operation mode (e.g., the first mode, second mode, third mode, fourth mode, fifth mode, etc., described below) UE 1002 has autonomously entered. This makes base station 1004 aware of the autonomous transition of UE 1002. This occurs when UE 1002 is in the desired power state / operation mode that it has autonomously entered.

[0153] At 1226, when the UE is in operating mode, it monitors WUS (Warranty Information) including sequence type from the network node, receives WUS including sequence type from the network node, and switches to another mode among the first, second, third, or fourth modes for the UE based on the sequence type. As an example, this monitoring, receiving, and / or switching may be performed at least in part by component 198. Figures 6 to 10 An example is shown of UE 602 performing this monitoring, receiving, and handover transmission in association with a network node (e.g., base station 604).

[0154] UE 602 can be configured to monitor (e.g., in) when in an operating mode (e.g., an operating mode that UE 602 autonomously switches to). Figure 10 (at position 1014 in the text) comes from base station 604, including sequence types (e.g., Figure 10 WUS (e.g., WUS (generally), LP-WUS, etc.) (e.g., 1020) Figure 10 (1016 in the original text). UE 602 can also be configured to receive from base station 604 a sequence type (e.g., ...). Figure 10 WUS (e.g., 1020) Figure 10 (1016 in the sequence), and based on the sequence type (e.g., Figure 10 Switching from 1020 in (e.g., in) Figure 10 (at position 1018 in the original text) is used for another mode in the first, second, third, or fourth mode of UE 602. In each respect, the sequence type (e.g., Figure 101020 in the WUS can be: (i) a first sequence type that instructs UE 602 to wake up and operate in a fifth mode, in which UE 602 is configured to operate in DL mode instead of UL mode; (ii) a second sequence type that instructs UE 602 to restart the retransmission time for retransmission monitoring; (iii) a third sequence type that instructs UE 602 to wake up and operate in a second mode; (iv) a fourth sequence type that includes a bit payload in WUS, wherein the bit payload corresponds to the first sequence type, the second sequence type, or the third sequence type; (iv) a fifth mode, wherein UE 602 is configured to operate in DL mode instead of UL mode; and so on.

[0155] Figure 13 This is a flowchart 1300 of a wireless communication method. The method can be performed by a base station / gNB (e.g., base stations 102, 604, 704, 804, 1004; network entities 1502, 1602, 1260). In some aspects, the method may include combining... Figure 6 The communication process described in the document covers various aspects and / or Figures 7 to 10 The method provides enabling power state transitions, which improves communication efficiency and reduces power consumption of devices associated with the wireless network by enhancing state reporting to include estimated time and / or delay reports of UL data, further improves communication efficiency and reduces power consumption of wireless devices by utilizing DL EOC indications that trigger state reporting, and rapidly provides UE information to the base station without additional signaling, and also allows the UE to autonomously transition to different power states after providing state indications to the base station by monitoring various wake-up signals.

[0156] At 1302, the base station sends a DL EOC indication to the UE, triggering a state indication. As an example, this transmission may be performed at least in part by component 199. Figures 6 to 10 An example of base station 604 sending such a DL EOC indication to a UE (e.g., UE 602) is illustrated.

[0157] UE 602 can be configured to provide capability indication 606 to base station 604. Capability indication 606 may be associated with at least one of the UE's first capabilities for providing information to base station 604 to enable power state transitions. In various aspects, capability indication 606 may indicate such capabilities of the UE as a first capability for the UE to estimate service conditions and / or provide the UE with an estimated time (e.g., Figure 9 The second capability (906, 908 in the original text). UE 602 can be configured to receive DL EOC indication 608 (e.g., ...). Figure 7706 in the middle; Figure 8 (e.g., 806, 812), and base station 604 can be configured to provide / transmit DL EOC indication 608 (e.g., Figure 7 706 in the middle; Figure 8 (806, 812 in the text). DL EOC indicates 608 (e.g., Figure 7 706 in the middle; Figure 8 806, 812) may be included in / may be part of DL communication, such as data provided / transmitted from base station 604 via DL channel. DLEOC indication 608 may be at least one of the following: EOB indication, PDCCH skip indication, DRX MAC-CE, DL retransmission end indication, DFI indicating ACK for UL packets (e.g., ACK for all UL packets from base station / gNB successfully decoded), and / or any equivalent DL signaling indicating that UE 602 has completed DL communication. As another example, EOC indication 608 may be L1 / L2 signaling indicating the end of cell DRX / DRX activity time.

[0158] At 1304, the base station receives a status indication from the UE and based on a DL EOC indication, which indicates the status of (i) the UE's buffer or UE delay, and (ii) an estimated time indicating the time when the UE estimates the arrival of the next UL packet. As an example, this reception may be performed at least in part by component 199. Figures 6 to 10 An example is shown where base station 604 receives such a status indication from UE (e.g., UE 602).

[0159] In all respects, DL EOC indicates 608 (e.g., Figure 7 706 in the middle; Figure 8 (806, 812) can trigger UE 602 to provide / send UE 602 status indication 610 to base station 604 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the middle). Status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the table may include / indicate, but is not limited to, the state of the UE's buffer (e.g., BSR, such as the BSR included in MAC-CE), delay status or delay status report (DSR), and an estimated time indicating to the UE 602 the arrival time of the next UL packet (e.g., Figure 9 (e.g., 906, 908). UE 602 can be configured to switch based on power state indication 614 (e.g., ...). Figure 7 712 in the middle; Figure 8 810, 814) and / or by UE 602 in the transmission status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, autonomously (e.g., Figure 10 In 1060) switch (at 612) to the operating mode for UE 602. In various aspects, UE 602 can switch based on power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 UE 602 can switch the power state (at 612) using 810, 814 in the transmission status indication 610, or ... Figure 7 710 in the middle; Figure 10 After 1006 in the middle, it autonomously switches the power state (at 612) (e.g., Figure 10 1060 in the above): (i) a first mode, wherein UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, wherein UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, wherein UE 602 is configured to operate with the modem off; (iv) a fourth mode, wherein UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); or (v) a fifth mode, wherein the UE is configured to operate in DL mode instead of UL mode (e.g., ... Figure 7 750 in the middle; Figure 8 816 in the middle; Figure 10 (1018 in the middle).

[0160] Figure 14 This is a flowchart 1400 of a wireless communication method. The method can be performed by a base station / gNB (e.g., base stations 102, 604, 704, 804, 1004; network entities 1502, 1602, 1260). In some aspects, the method may include combining... Figure 6 The communication process described in the document covers various aspects and / or Figures 7 to 10 The method provides enabling power state transitions, which improves communication efficiency and reduces power consumption of devices associated with the wireless network by enhancing state reporting to include estimated time and / or delay reports of UL data, further improves communication efficiency and reduces power consumption of wireless devices by utilizing DL EOC indications that trigger state reporting, and rapidly provides UE information to the base station without additional signaling, and also allows the UE to autonomously transition to different power states after providing state indications to the base station by monitoring various wake-up signals.

[0161] At 1402, the base station receives from the UE a capability indication of at least one of the UE's first capability to estimate service conditions or the UE's second capability to provide estimated time. As an example, this reception may be performed at least in part by component 199. Figures 6 to 10 An example is shown where base station 604 receives such a capability indication from UE (e.g., UE 602).

[0162] UE 602 can be configured to provide capability indication 606 to base station 604. Capability indication 606 may be associated with at least one of the UE's first capabilities for providing information to base station 604 to enable power state transitions. In various aspects, capability indication 606 may indicate such capabilities of the UE as a first capability for the UE to estimate service conditions and / or provide the UE with an estimated time (e.g., Figure 9 The second ability of 906 and 908 in the middle.

[0163] At 1404, the base station sends a DL EOC indication to the UE, triggering a state indication. As an example, this transmission may be performed at least in part by component 199. Figures 6 to 10 An example of base station 604 sending such a DL EOC indication to a UE (e.g., UE 602) is illustrated.

[0164] UE 602 can be configured to receive DL EOC indication 608 (e.g., Figure 7 706 in the middle; Figure 8 (e.g., 806, 812), and base station 604 can be configured to provide / transmit DL EOC indication 608 (e.g., Figure 7 706 in the middle; Figure 8 806, 812 (in the DLEOC instruction 608, e.g., ) Figure 7 706 in the middle; Figure 8 806, 812) may be included in / may be part of DL communication, such as data provided / transmitted from base station 604 via DL channel. DL EOC indication 608 may be at least one of the following: EOB indication, PDCCH skip indication, DRX MAC-CE, DL retransmission end indication, DFI indicating ACK for UL packets (e.g., ACK for all UL packets from base station / gNB successfully decoded), and / or any equivalent DL signaling indicating that UE 602 has completed DL communication. As another example, EOC indication 608 may be L1 / L2 signaling indicating the end of cell DRX / DRX activity time.

[0165] At 1406, the base station receives a status indication from the UE and based on a DL EOC indication, which indicates the status of (i) the UE's buffer or UE delay, and (ii) an estimated time indicating the time when the UE estimates the arrival of the next UL packet. As an example, this reception may be performed at least in part by component 199. Figures 6 to 10 An example is shown where base station 604 receives such a status indication from UE (e.g., UE 602).

[0166] In all respects, DL EOC indicates 608 (e.g., Figure 7 706 in the middle; Figure 8 (806, 812) can trigger UE 602 to provide / send UE 602 status indication 610 to base station 604 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the middle). Status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the table may include / indicate, but is not limited to, the state of the UE's buffer (e.g., BSR, such as the BSR included in MAC-CE), delay status or delay status report (DSR), and an estimated time indicating to the UE 602 the arrival time of the next UL packet (e.g., Figure 9 (e.g., 906, 908).

[0167] At 1408, the base station determines whether it will grant UL permission for data to be transmitted from the UE's buffer. As an example, this determination may be performed at least in part by component 199. If yes, flowchart 1400 proceeds to 1410; if no, flowchart 1400 proceeds to 1412.

[0168] At 1410, during the time period following the receipt of the status indication and prior to the estimated time, the base station transmits a UL grant to the UE for UL services associated with data in the UE's buffer, and receives UL services from the UE based on the UL grant. As an example, this transmission and reception may be performed at least in part by component 199. Figure 6 and Figure 10 An example of base station 604 sending UL grant and receiving UL data with respect to UE (e.g., UE 602) is illustrated.

[0169] As described herein, the UE can enter various operating modes / power states associated with receiving the DL EOC indication. However, aspects also provide for the UE to process and transmit UL data packets for services in the UE buffer, as reported by a status indication (e.g., via BSR). In call flow diagram 1050, after receiving the DL EOC indication, as noted herein, UE 1002 (e.g., Figure 6 602 in the middle can be configured to provide / transmit information that can be provided by base station 1004 (e.g., Figure 6 The status indication 1006 received by (604) may include, but is not limited to, buffer status (e.g., BSR), delay status, estimated time (e.g., ...). Figure 9 (e.g., 906, 908). In a scenario where the buffer of UE 1002 is non-zero and there are data packets to be transmitted via the UL channel, UE 1002 can be configured to receive at least one UL grant 1008 from base station 1004 and, in response, provide the associated UL data service 1010 to base station 1004.

[0170] At 1412, the base station determines whether the UE should perform an autonomous power state handover. As an example, this determination may be performed at least partially by component 199. If yes, flowchart 1400 proceeds to 1420; if no, flowchart 1400 proceeds to 1414.

[0171] At 1414, the base station determines whether the UE provides / transmits a UCI with the UE's code points. As an example, this determination may be performed at least in part by component 199. If yes, flowchart 1400 proceeds to 1416; if no, flowchart 1400 proceeds to 1418.

[0172] At 1416, the base station receives from the UE a UCI including code points for the UE, wherein the code points for the UE indicate at least one of the following: a first indication of delayed operation in a second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operation in the second mode based on the elapsed first time period; or a fourth indication of returning to the first mode or transitioning to the third mode for wake-up based on the second time period. As an example, this reception may be performed at least in part by component 199. Figure 6 and Figure 8 An example of base station 604 receiving such UCI from UE (e.g., UE 602) is illustrated.

[0173] UE 602 can be configured to send code points (e.g., for UE 602) to base station 604. Figure 7 The UCI (e.g., 750) in the middle) Figure 8 808 in the middle). UCI 808 may be based on or in response to the received DL EOC instruction 608 (e.g., Figure 7 706 in the middle; Figure 8 The code points (806, 812) used in UE 602 are provided / transmitted. Figure 7The 750 in the text can indicate: a first indication of delaying operation in a second mode, where the second mode consumes less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication based on the elapsed first time period for operation in the second mode; a fourth indication based on the second time period for returning to the first mode or transitioning to the third mode; and so on. In various respects, UCI (e.g., Figure 8 808 in the middle) may be based on and / or in response to the received DL EOC indication 608 from base station 604 (e.g., Figure 7 706 in the middle; Figure 8 (806, 812).

[0174] At 1418, the base station sends a power state switching indication to the UE, which indicates the operating mode for the UE based on at least one of the UE's buffer, the UE's delay, or the state of estimated time. As an example, this transmission may be performed at least in part by component 199. Figures 6 to 10 An example of base station 604 sending such a power state switching indication to a UE (e.g., UE 602) is illustrated.

[0175] UE 602 may receive a power state switching indication 614 provided / transmitted from base station 604 (e.g., Figure 7 712 in the middle; Figure 8 (810, 814 in the middle). Figure 7 In the context of the DCI, the power state switching indication 712 provided / transmitted by base station 704 may be included in the DCI and may indicate that UE 702 operates in a third mode based on (i) the amount of data in UE 702's buffer is zero or (ii) UE 702's ability to delay the transmission of data packets, and / or indicate that UE 702 operates in a second mode based on the amount of data in UE 702's buffer being non-zero. Figure 8 In the context (850), base station 804 can be configured to provide / transmit power state switching indication 810 based on UCI 808 with code points, which UE 802 can receive. Through power state switching indication 810, in the first example, base station 804 can trigger state indications (e.g., BSR, delay state, and / or estimated time) (e.g., ...). Figure 9(906, 908 in the document), or if the status indication indicates that the buffer of UE 802 is non-zero and / or UE 802 is latency-intolerant, then the DL EOC indication 806 may trigger the status indication as described herein. UE 802 may be transferred to a UL power state (e.g., not monitoring DL traffic) instead of via the power state switching indication 810, which has a lower power than the DL and UL power states. In the second example, via the power state switching indication 810, if the status indication indicates that the buffer of UE 802 is zero and the estimated arrival time of the next UL data packet (e.g., ...) is... Figure 9 906 and 908 in the code are insufficient to enter sleep mode (e.g., for UE 802, entering sleep, microsleep, deep sleep, ultra-deep sleep, etc., and subsequently transitioning from sleep to on state (e.g., Figure 7 If the power state of configuration 750 (non-sleep state) is inefficient (e.g., in terms of DCI bits), then base station 804 can trigger a state indication (e.g., BSR, delay state, and / or estimated time). Configurable for estimated time (e.g., Figure 9 The configurable thresholds (906, 908) in the data allow for estimation of time (e.g., ...) Figure 9 If 906 and 908 in the above values ​​are less than or equal to the threshold, then UE 802 will not be transferred to sleep mode. In the third example, via power state switching indication 810, if the state indication indicates that UE 802's buffer is zero and the estimated time (e.g., ...) is... Figure 9 If 906 and 908 in the timeline are long enough to put UE 802 into a sleep state, then base station 804 can trigger a status indication (e.g., BSR, delay status, and / or estimated time) (e.g., ...). Figure 9 (906, 908 in the original text), UE 802 can be sent to sleep until the estimated time (e.g., Figure 9 (906, 908 in the document), and UE 802 can sleep based on available time. In various aspects, the time for transitioning to another power state can also be considered to determine which sleep state UE 802 should enter. In some aspects, even if the base station / network node does not provide a state indication, as described herein, the base station / network node can transmit a conditional DCI indication for power state transition to the UE. Figure 8In the context of (860), the power state switching indication 814 may be included in the conditional DCI and, as a first option, may indicate to UE 802 that: (i) if the amount of data waiting in UE 802's buffer is zero, then it will transition to a sleep state, or (ii) UE 802 may safely wait for the next cycle to send packets because UE 802 is configured to be latency tolerant. As a second option, if the amount of data waiting in UE 802's buffer is non-zero, then UE 802 may transition to a UL power state / mode (e.g., no DL service monitoring). In all respects, UE 802 may be configured to report (e.g., provide / send) back (e.g., receive) to base station 804 via UCI, MAC-CE, or UAI which of the two states / modes it will be in (e.g., UE 802's operating state 818). In various aspects, RRC signaling (such as UAI) may include periodic recommendations from UE 802 for preferred power states (e.g., when there is cross-layer optimization between the application and the modem of UE 802, UE 802 may know its UL services better than base station 804).

[0176] UE 602 can be configured to switch based on power state indication 614 (e.g., Figure 7 712 in the middle; Figure 8 810, 814) and / or by UE 602 in the transmission status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, autonomously (e.g., Figure 10 In 1060) switch (at 612) to the operating mode for UE 602. In various aspects, UE 602 can switch based on power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 UE602 can switch the power state (at 612) using 810, 814, or UE602 can do so at transmit status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, it autonomously switches the power state (at 612) (e.g., Figure 10 (1060 in the above): (i) a first mode, wherein UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, wherein UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, wherein UE 602 is configured to operate with the modem off; (iv) a fourth mode, wherein UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); or (v) a fifth mode, wherein UE 602 is configured to operate in DL mode instead of UL mode.

[0177] The switching (at 612) is based on the power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 In terms of aspects of 810, 814), power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 810, 814 in the above) may be based on or associated with DL EOC indication 608. Power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 810, 814) may be included in the DCI and may instruct UE 602 to operate in a third mode based on (i) the amount of data in UE 602's buffer being zero or (ii) UE 602's ability to delay the transmission of data packets, and / or instruct UE 602 to operate in a second mode based on the amount of data in UE 602's buffer being non-zero. In such respect, UE 602 may be configured to operate based on estimated time (e.g., Figure 9 (906, 908) to provide / transmit status indication 610 for the status of the indication buffer of base station 604 (e.g., Figure 7 710 in the middle; Figure 10 1006 in the middle). Estimated time (e.g., Figure 9 (906, 908) can instruct UE 602 to estimate that the arrival time of the next UL packet is shorter than the sleep time used by UE 602 to enter sleep mode. Furthermore, in various aspects, the power state switching indication 614 provided / transmitted by base station 604 can indicate the operating mode for UE 602 as a second mode. Additionally, UE 602 can send a UCI including code points for UE 602 to base station 604. The code points for UE 602 can indicate: a first indication of delayed operation in the second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operation in the second mode based on the elapsed first time period; a fourth indication of returning to the first mode or transitioning to the third mode based on the second time period; and so on. In various aspects, the UCI can be based on and / or in response to a received DL EOC indication 608 from base station 604.

[0178] At 1420, the base station receives from the UE an operation instruction for autonomous handover, instructing the UE to operate in a third mode or a second mode, wherein the operation instruction includes at least one of UCI, MAC-CE, or UAI. As an example, the handover may be performed at least partially by component 199. Figures 6 to 10 An example is shown where base station 604 receives such an operation instruction from UE (e.g., UE 602).

[0179] UE 602 can be configured to switch based on power state indication 614 (e.g., Figure 7 712 in the middle; Figure 8 810, 814) and / or by UE 602 in the transmission status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, autonomously (e.g., Figure 10 In 1060) switch (at 612) to the operating mode for UE 602. In various aspects, UE 602 can switch based on power state switching indication 614 (e.g., Figure 7 712 in the middle; Figure 8 UE602 can switch the power state (at 612) using 810, 814, or UE602 can do so at transmit status indication 610 (e.g., Figure 7 710 in the middle; Figure 10 After 1006 in the middle, it autonomously switches the power state (at 612) (e.g., Figure 10 (1060 in the above): (i) a first mode, wherein UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, wherein UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, wherein UE 602 is configured to operate with the modem off; (iv) a fourth mode, wherein UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); or (v) a fifth mode, wherein UE 602 is configured to operate in DL mode instead of UL mode.

[0180] When executed autonomously by UE 602 (e.g., Figure 10 In terms of various aspects of the handover (at 612) (at 1060), UE 602 can be configured to autonomously (e.g., Figure 10 (1060) Switches to (at 612) various operating modes. The operating modes can be: (i) a first mode, in which UE 602 is configured to operate in both UL and DL modes; (ii) a second mode, in which UE 602 is configured to operate in UL mode instead of DL mode; (iii) a third mode, in which UE 602 is configured to operate with the modem off; (iv) a fourth mode, in which UE 602 is configured to skip monitoring of the PDCCH (e.g., PDCCH skipping); (v) a fifth mode, in which UE 602 is configured to operate in DL mode instead of UL mode; and so on.

[0181] In all respects, UE 602 can be configured to send an operation instruction to base station 604 instructing UE 602 to operate in the third mode or the second mode (e.g., Figure 8818 in the middle; Figure 10 1012 in the middle). In all aspects, operating instructions (e.g., Figure 8 818 in the middle; Figure 10 1012) may be included in at least one of UCI, MAC-CE, or UAI. Figure 10 In the context of UE 1002 (e.g., Figure 6 602 in the configuration can be configured to provide / transmit an operation instruction 1012 to base station 1004 (e.g., 1004). The operation instruction 1012 can indicate to base station 1004 which power state / operation mode (e.g., the first mode, second mode, third mode, fourth mode, fifth mode, etc., described below) UE 1002 has autonomously entered. This makes base station 1004 aware of the autonomous transition of UE 1002. This occurs when UE 1002 is in the desired power state / operation mode that it has autonomously entered.

[0182] At 1422, the base station sends a WUS to the UE, including a sequence type, where the sequence type is associated with a handover of the UE to another mode among a first mode, a second mode, a third mode, or a fourth mode for the UE. As an example, this transmission may be performed at least in part by component 199. Figures 6 to 10 An example of base station 604 sending such WUS to UE (e.g., UE 602) is shown.

[0183] UE 602 can be configured to monitor (e.g., in) when in an operating mode (e.g., an operating mode that UE 602 autonomously switches to). Figure 10 (at position 1014 in the text) comes from base station 604, including sequence types (e.g., Figure 10 WUS (e.g., WUS (generally), LP-WUS, etc.) (e.g., 1020) Figure 10 (1016 in the original text). UE 602 can also be configured to receive from base station 604 a sequence type (e.g., ...). Figure 10 WUS (e.g., 1020) Figure 10 (1016 in the sequence), and based on the sequence type (e.g., Figure 10 Switching from 1020 in (e.g., in) Figure 10 (at position 1018 in the original text) is used for another mode in the first, second, third, or fourth mode of UE 602. In each respect, the sequence type (e.g., Figure 101020 in the WUS can be: (i) a first sequence type that instructs UE 602 to wake up and operate in a fifth mode, in which UE 602 is configured to operate in DL mode instead of UL mode; (ii) a second sequence type that instructs UE 602 to restart the retransmission time for retransmission monitoring; (iii) a third sequence type that instructs UE 602 to wake up and operate in a second mode; (iv) a fourth sequence type that includes a bit payload in WUS, wherein the bit payload corresponds to the first sequence type, the second sequence type, or the third sequence type; (iv) a fifth mode, wherein UE 602 is configured to operate in DL mode instead of UL mode; and so on.

[0184] Figure 15Figure 1500 illustrates an example of a hardware implementation for device 1504. Device 1504 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1504 may include at least one cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., cellular RF transceivers). Cellular baseband processor 1524 may include at least one on-chip memory 1524'. In some aspects, device 1504 may also include one or more Subscriber Identity Module (SIM) cards 1520 and at least one application processor 1506 coupled to a Secure Digital Card (SD) card 1508 and a screen 1510. Application processor 1506 may include on-chip memory 1506'. In some aspects, device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power supply 1530, and / or a camera 1532. Bluetooth module 1512, WLAN module 1514, and SPS module 1516 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 1512, WLAN module 1514, and SPS module 1516 may include their own dedicated antennas and / or communicate using antenna 1580. Cellular baseband processor 1524 communicates with UE 104 and / or RU associated with network entity 1502 via transceiver 1522 through one or more antennas 1580. Cellular baseband processor 1524 and application processor 1506 may each include computer-readable media / memory 1524', 1506'. Additional memory module 1526 may also be considered computer-readable media / memory. Each computer-readable media / memory 1524', 1506', 1526 may be non-transitory. Cellular baseband processor 1524 and application processor 1506 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1524 / application processor 1506, the software causes cellular baseband processor 1524 / application processor 1506 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by cellular baseband processor 1524 / application processor 1506 during software execution.Cellular baseband processor 1524 / application processor 1506 may be a component of UE 350 and may include at least one of memory 360 and / or TX processor 368, RX processor 356 and controller / processor 359. In one configuration, device 1504 may be at least one processor chip (modem and / or application) and may include only cellular baseband processor 1524 and / or application processor 1506, while in another configuration, device 1504 may be the entire UE (see, for example). Figure 3 The UE 350 includes an additional module of the device 1504.

[0185] As discussed above, component 198 can be configured to receive a downlink DLEOC indication triggering a state indication from a network node. Component 198 can also be configured to send a state indication to the network node based on the DLEOC indication, the state indication indicating the state of: (i) the UE's buffer or UE delay, and (ii) an estimated time indicating the time of arrival of the next UL packet for the UE. Component 198 can be configured to receive a power state switching indication from the network node, the power state switching indication indicating an operating mode for the UE based on at least one of the states of the UE's buffer, UE delay, or estimated time. Component 198 can be configured to switch to an operating mode for the UE based on the power state switching indication. Component 198 can be configured to send a UCI to the network node including code points for the UE, wherein the code points for the UE indicate at least one of: a first indication of delaying operation in a second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operating in the second mode based on the elapsed first time period; or a fourth indication of returning to the first mode or transitioning to the third mode based on the second time period. Component 198 can be configured to receive UL permission from the network node for UL services associated with data in the UE's buffer during a time period after the transmission status indication and before the estimated time. Component 198 can be configured to transmit UL services to the network node based on UL permission during the time period after the transmission status indication and before the estimated time. Component 198 can be configured to transmit to the network node a capability indication of at least one of the UE's ability to estimate service status or the UE's ability to provide a second time estimate. Component 198 can be configured to allow the UE to autonomously switch to an operating mode for the UE after the transmission status indication, wherein the operating mode for the UE is: a first mode, wherein the UE is configured to operate in UL mode and DL mode; a second mode, wherein the UE is configured to operate in UL mode instead of DL mode; a third mode, wherein the UE is configured to operate with the modem off; or a fourth mode, wherein the UE is configured to skip monitoring of the PDCCH. Component 198 can be configured to monitor WUS, including sequence type, from the network node while in operating mode. Component 198 can be configured to receive WUS, including sequence type, from the network node. Component 198 can be configured to switch to another mode among the first, second, third, or fourth modes for the UE based on the sequence type. Component 198 can also be configured to perform combination. Figures 11 to 14 Any aspect described in the flowchart of any of the above, and / or by the sensing node for any aspect Figures 6 to 10Any aspect of the process / algorithm executed by any of the processors. Component 198 may be within cellular baseband processor 1524, application processor 1506, or both cellular baseband processor 1524 and application processor 1506. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, device 1504 may include a variety of components configured for various functions. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for receiving a downlink DL EOC indication from a network node. In this configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for transmitting a status indication to the network node based on a DL EOC indication, the status indication indicating the state of: (i) the UE's buffer or UE delay, and (ii) an estimated time indicating the time of arrival of the next UL packet for the UE. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for receiving a power state switching indication from the network node, the power state switching indication indicating an operating mode for the UE based on at least one of the states of the UE's buffer, UE delay, or estimated time. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for switching to an operating mode for the UE based on the power state switching indication. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for transmitting to a network node a UCI including code points for the UE, wherein the code points for the UE include at least one of: a first indication of delayed operation in a second mode, the second mode consuming less power than a first mode; a second indication that operation in the second mode is acceptable; a third indication based on the elapsed first time period of operation in the second mode; or a fourth indication based on the second time period of returning to the first mode or transitioning to a third mode. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for receiving from the network node UL authorization for UL services associated with data in the UE's buffer during a time period after the transmission of a status indication and before an estimated time.In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for granting permission to transmit UL services to a network node based on UL during a time period following a transmission status indication and preceding an estimated time. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for transmitting to a network node an indication of at least one of a first capability of the UE to estimate service conditions or a second capability of the UE to provide an estimated time. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for allowing the UE to autonomously switch to an operating mode for the UE after a transmission status indication, wherein the operating modes for the UE are: a first mode in which the UE is configured to operate in both UL and DL modes; a second mode in which the UE is configured to operate in UL mode instead of DL mode; a third mode in which the UE is configured to operate with the modem off; or a fourth mode in which the UE is configured to skip monitoring of the PDCCH. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for monitoring WUS of sequence type from a network node when in an operating mode. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for receiving WUS of sequence type from a network node. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for switching to another mode among a first mode, a second mode, a third mode, or a fourth mode for the UE based on the sequence type. These components may be components 198 of device 1504 configured to perform the functions described therein. As described above, device 1504 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, these components may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions described therein.

[0186] Figure 16Figure 1600 illustrates an example of a hardware implementation for network entity 1602. Network entity 1602 may be a BS, a component of a BS, or implement BS functionality. Network entity 1602 may include at least one of CU 1610, DU 1630, or RU 1640. For example, depending on the layer functionality handled by component 199, network entity 1602 may include: CU 1610; both CU 1610 and DU 1630; each of CU 1610, DU 1630, and RU 1640; DU 1630; both DU 1630 and RU 1640; or RU 1640. CU 1610 may include at least one CU processor 1612. CU processor 1612 may include on-chip memory 1612'. In some aspects, CU 1610 may also include an additional memory module 1614 and a communication interface 1618. CU1610 communicates with DU 1630 via a midhaul link, such as an F1 interface. DU 1630 may include at least one DU processor 1632. DU processor 1632 may include on-chip memory 1632'. In some aspects, DU 1630 may also include an additional memory module 1634 and a communication interface 1638. DU 1630 communicates with RU 1640 via a fronthaul link. RU 1640 may include at least one RU processor 1642. RU processor 1642 may include on-chip memory 1642'. In some aspects, RU 1640 may also include an additional memory module 1644, one or more transceivers 1646, an antenna 1680, and a communication interface 1648. RU 1640 communicates with UE 104. On-chip memories 1612', 1632', 1642' and additional memory modules 1614, 1634, 1644 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1612, 1632, and 1642 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0187] As discussed above, component 199 can be configured to send a DL EOC indication triggering a state indication to the UE. Component 199 can also be configured to receive a state indication from the UE and based on the DL EOC indication, the state indication indicating the state of: (i) the UE's buffer or UE's delay, and (ii) an estimated time indicating the time of arrival of the next UL packet for the UE. Component 199 can be configured to send a power state switching indication to the UE, the power state switching indication indicating an operating mode for the UE based on at least one of the states of the UE's buffer, UE's delay, or estimated time. Component 199 can be configured to receive a UCI from the UE including code points for the UE, wherein the code points for the UE indicate at least one of: a first indication of delayed operation in a second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication of operation in the second mode based on the elapsed first time period; or a fourth indication of returning to the first mode or transitioning to the third mode for wake-up based on the second time period. Component 199 can be configured to send UL permission to the UE for UL services associated with data in the UE's buffer during a time period after the transmission status indication and before the estimated time. Component 199 can be configured to receive UL services from the UE based on UL permission during the time period after the transmission status indication and before the estimated time. Component 199 can be configured to receive from the UE a capability indication from the UE of at least one of a first capability indicating that the UE estimates the service status or a second capability that the UE provides an estimated time. Component 199 can be configured to receive from the UE an operation indication for autonomous handover of the UE for operation in a third mode or a second mode, wherein the operation indication includes at least one of UCI, MAC-CE, or UAI. Component 199 can be configured to send to the UE a WUS including a sequence type, wherein the sequence type is associated with a handover of the UE to another mode for the UE, namely a first mode, a second mode, a third mode, or a fourth mode. Component 199 can also be configured to perform a combination. Figures 11 to 14 Any aspect described in the flowchart of any of the above, and / or by the sensing node for any aspect Figures 6 to 10Any aspect of the process / algorithm executed by any of the components. Component 199 may be located within one or more processors of one or more of CU 1610, DU 1630, and RU 1640. Component 199 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1602 may include a variety of components configured for various functions. In one configuration, network entity 1602 may include components for sending a DL EOC indication to the UE to trigger a status indication. In this configuration, network entity 1602 may include components for receiving a status indication from the UE and based on the DL EOC indication, the status indication indicating the status of (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating to the UE the estimated time of arrival of the next UL packet. In one configuration, network entity 1602 may include components for sending a power state switching indication to the UE, the power state switching indication indicating an operating mode for the UE based on at least one of the UE's buffer state, the UE's delay state, or an estimated time state. In one configuration, network entity 1602 may include components for receiving from the UE a UCI including code points for the UE, wherein the code points for the UE indicate at least one of the following: a first indication of delayed operation in a second mode, the second mode consuming less power than the first mode; a second indication that operation in the second mode is acceptable; a third indication based on the elapsed first time period of operation in the second mode; or a fourth indication based on the second time period of wake-up to return to the first mode or transition to the third mode. In one configuration, network entity 1602 may include components for sending UL permission for UL services associated with data in the UE's buffer to the UE during a time period after sending the state indication and before the estimated time. In one configuration, network entity 1602 may include components for receiving UL services from the UE based on UL permission during a time period after sending the state indication and before the estimated time. In one configuration, network entity 1602 may include components for receiving from the UE a capability indication of at least one of a first capability of the UE to estimate service conditions or a second capability of the UE to provide estimated time. In one configuration, network entity 1602 may include components for receiving from the UE an operation indication of an autonomous handover for operation in a third mode or a second mode, wherein the operation indication includes at least one of UCI, MAC-CE, or UAI.In one configuration, network entity 1602 may include components for sending a WUS to the UE, including a sequence type, wherein the sequence type is associated with a UE switching to another mode among a first mode, a second mode, a third mode, or a fourth mode for the UE. These components may be components 199 of network entity 1602 configured to perform the functions described therein. As described above, network entity 1602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, these components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described therein.

[0188] Traffic flows in wireless communication networks can have various characteristics inherent to wireless communication networks, including layer attributes, time frames for latency, power-saving configurations, etc. As an example, XR services for UL and DL may have characteristics such as application layer attributes, short time frames for switching (where longer latency for traffic flows may degrade the user experience of XR applications or devices), unbalanced traffic flows, etc. Power-saving configurations for XR may include UL states triggered by inactivity or rapid triggering (e.g., via DCI) (e.g., no DL communication). Other configurations, such as those for PDCCH skipping, can save power by allowing the UE to skip monitoring of DL PDCCH data / information. However, existing power-saving configurations for 5G NR may not be suitable for advanced networks such as 6G networks. For example, in the context of XR, 5G implementations may have insufficient granularity in DRX or C-DRX active-inactive states, and C-DRX transitions designed for eMBB / voice services may have inactivity timers that cannot ensure rapid transitions. SSSG state / PDCCH skipping offers greater flexibility but does not account for quasi-periodic structures and does not provide sufficient granularity for power states (e.g., UL power states without DL monitoring). Further regarding PDCCH skipping, since communication may not occur when the UE is not monitoring the PDCCH (in both UL and DL), it can introduce latency into UL scheduling. To reduce UL scheduling latency, if the UE has urgent UL data to send, the UE can indicate the cessation of PDCCH skipping or override the SSSG handover via the transmission of an SR (e.g., the UE can switch back to regular PDCCH monitoring to monitor uplink permission after transmitting the SR). However, such a configuration does not account for scenarios without urgent UL data. For example, while 5G NR may allow the UE to cancel PDCCH skipping, the base station (e.g., gNB, etc.) may have already transmitted redundant PDCCH skipping indications for the UE to put to sleep (whether this is a scheduled DCI or an unscheduled DCI—an unscheduled DCI could be in the form of a dummy permission with zero resource block allocation and used to indicate PDCCH skipping (e.g., not used for any other operation)). Furthermore, the base station (e.g., gNB, etc.) may not know / understand that the UE is about to transmit a positive SR so close to the PDCCH skip indication, which could also guarantee that the base station transmits an unnecessary indication. Therefore, previous solutions lacked optimization, by which the base station (e.g., gNB, etc.) knows / understands the existence of UL data arriving sufficiently quickly, allowing the base station to make a better decision on whether to transmit the skip indication. This paper provides solutions covering transitions between entering and exiting power states.

[0189] This document describes various aspects for enabling power state transitions to improve communication efficiency and reduce power consumption of devices associated with the wireless network by enhancing state reporting to include estimated timing and / or delay reporting of UL data. These aspects further enhance communication efficiency and reduce power consumption of wireless devices by utilizing DL EOC indications that trigger state reporting, and by rapidly providing UE information to the base station without additional signaling. Furthermore, these aspects allow the UE to autonomously transition to different power states after providing state indications to the base station by monitoring various wake-up signals.

[0190] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0191] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when…”, do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements with a number of one or more elements. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to perform a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. A device configured to “output” data (such as transmission, signaling, or a message) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to “receive” data (such as transmission, signaling, or a message) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data.Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to or will later be known to a person skilled in the art are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., cannot replace the word “component.” Therefore, no claim element will be construed as a functional component unless the element is expressly recited using the phrase “component for…”.

[0192] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0193] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0194] Aspect 1 is a method for wireless communication at a user equipment (UE), the method comprising: receiving a downlink (DL) communication end (EOC) indication that triggers a state indication from a network node; and sending the state indication to the network node and based on the DL EOC indication, the state indication indicating the state of: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating the UE to estimate the arrival time of the next UL packet.

[0195] Aspect 2 is the method according to aspect 1, the method further comprising: receiving a power state switching indication from the network node, the power state switching indication indicating an operating mode for the UE based on at least one of the state of the UE's buffer, the UE's delay, or the estimated time.

[0196] Aspect 3 is the method according to aspect 2, wherein the operating mode for the UE is: a first mode, wherein the UE is configured to operate in UL mode and DL mode; a second mode, wherein the UE is configured to operate in UL mode but not in DL mode; a third mode, wherein the UE is configured to operate with the modem off; a fourth mode, wherein the UE is configured to skip monitoring of the physical downlink control channel (PDCCH); or a fifth mode, wherein the UE is configured to operate in DL mode but not in UL mode.

[0197] Aspect 4 is the method according to aspect 3, wherein the power state switching indication is based on the DL EOC indication and included in the downlink control information (DCI), wherein the power state switching indication indicates at least one of the following: operating in the third mode based on (i) the amount of data in the buffer of the UE is zero or (ii) the UE's ability to delay the transmission of data packets; or operating in the second mode based on the amount of data in the buffer of the UE being non-zero.

[0198] Aspect 5 is the method according to aspect 3, wherein the state indication of the state of the buffer is transmitted based on the estimated time, wherein the estimated time indicates that the UE estimates the arrival time of the next UL packet to be shorter than the sleep time used by the UE to enter sleep mode, and wherein the power state switching indication indicates the operating mode for the UE to be the second mode.

[0199] Aspect 6 is the method according to aspect 2, the method further comprising: switching to the operating mode for the UE based on the power state switching indication.

[0200] Aspect 7 is a method according to any one of Aspects 1 to 6, the method further comprising: sending uplink control information (UCI) to the network node including code points for the UE, wherein the code points for the UE indicate at least one of the following: a first indication of delaying operation in a second mode, the second mode consuming less power than a first mode; a second indication that operation in the second mode is acceptable; a third indication of operating in the second mode based on a first time period; or a fourth indication of returning to the first mode or switching to a third mode based on a second time period.

[0201] Aspect 8 is the method according to aspect 7, wherein the UCI is sent based on the received DL EOC indication from the network node.

[0202] Aspect 9 is a method according to any one of Aspects 1 to 8, wherein the status indication includes at least one of the following: a buffer status report (BSR) included in a medium access control (MAC) control element (MAC-CE); or a delay status report (DSR) indicating the status of the delay of the UE; and wherein the EOC is at least one of the following: an end-of-burst (EOB) indication, a physical downlink control channel (PDCCH) skip indication, a discontinuous reception (DRX) MAC-CE, a DL retransmission end indication, a DL feedback indication (DFI) indicating an acknowledgment (ACK) for a UL packet, or a Layer 1 (L1) or Layer 2 (L2) signaling indicating the end of cell DRX or the end of DRX activity time.

[0203] Aspect 10 is a method according to any one of aspects 1 to 9, the method further comprising: during a time period after the status indication is sent and before the estimated time: receiving from the network node a UL grant for UL services associated with data in the buffer of the UE; and sending the UL services to the network node based on the UL grant.

[0204] Aspect 11 is a method according to any one of aspects 1 to 10, the method further comprising: transmitting to the network node a capability indication of at least one of a first capability of the UE to estimate service conditions or a second capability of the UE to provide the estimated time.

[0205] Aspect 12 is a method according to aspect 1 and any one of aspects 7 to 11, the method further comprising: after sending the status indication, the UE autonomously switching to an operating mode for the UE, wherein the operating mode for the UE is: a first mode, wherein the UE is configured to operate in UL mode and DL mode; a second mode, wherein the UE is configured to operate in UL mode but not in DL mode; a third mode, wherein the UE is configured to operate with the modem off; or a fourth mode, wherein the UE is configured to skip monitoring of the physical downlink control channel (PDCCH).

[0206] Aspect 13 is the method according to aspect 12, the method further comprising: sending an operation indication to the network node instructing the UE to operate in the third mode or the second mode, wherein the operation indication includes at least one of uplink control information (UCI), media access control (MAC) control element (MAC-CE), or UE assistance information (UAI).

[0207] Aspect 14 is the method according to aspect 13, the method further comprising: monitoring a wake-up signal (WUS) including a sequence type from the network node while in the operating mode; receiving the WUS including the sequence type from the network node; and switching to another mode for the UE based on the sequence type, namely the first mode, the second mode, the third mode, or the fourth mode.

[0208] Aspect 15 is the method according to aspect 14, wherein the sequence type is at least one of the following: a first sequence type, the first sequence type indicating that the UE is woken up and operates in a fifth mode, wherein the UE is configured to operate in the DL mode instead of the UL mode; a second sequence type, the second sequence type indicating that the UE restarts the retransmission time for retransmission monitoring; a third sequence type, the third sequence type indicating that the UE is woken up and operates in the second mode; or a fourth sequence type, the fourth sequence type including a payload of bits in the WUS, wherein the payload of bits corresponds to the first sequence type, the second sequence type, or the third sequence type.

[0209] Aspect 16 is a method for wireless communication at a network node, the method comprising: sending a downlink (DL) communication end (EOC) indication that triggers a state indication to a user equipment (UE); and receiving the state indication from the UE and based on the DL EOC indication, the state indication indicating the state of: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating to the UE the estimated time of arrival of the next UL packet.

[0210] Aspect 17 is the method according to aspect 16, the method further comprising: sending a power state switching indication to the UE, the power state switching indication indicating an operating mode for the UE based on at least one of the state of the UE's buffer, the UE's delay, or the estimated time.

[0211] Aspect 18 is the method according to aspect 17, wherein the operating mode for the UE is: a first mode, wherein the UE is configured to operate in UL mode and DL mode; a second mode, wherein the UE is configured to operate in UL mode but not in DL mode; a third mode, wherein the UE is configured to operate with the modem off; or a fourth mode, wherein the UE is configured to skip monitoring of the physical downlink control channel (PDCCH).

[0212] Aspect 19 is the method according to aspect 18, wherein the power state switching indication is based on the UL EOC indication and included in the downlink control information (DCI), wherein the power state switching indication indicates at least one of the following: operating in the third mode based on (i) the amount of data in the buffer of the UE is zero or (ii) the UE's ability to delay the transmission of data packets; or operating in the second mode based on the amount of data in the buffer of the UE being non-zero.

[0213] Aspect 20 is the method according to aspect 18, wherein receiving a state indication indicating the state of the buffer is based on the estimated time, wherein the estimated time indicates that the UE estimates the arrival time of the next UL packet to be shorter than the sleep time used by the UE to enter sleep mode, and wherein the power state switching indication indicates the operating mode for the UE to be the second mode.

[0214] Aspect 21 is a method according to any one of aspects 16 to 20, the method further comprising: receiving from the UE uplink control information (UCI) including code points for the UE, wherein the code points for the UE indicate at least one of the following: a first indication of delaying operation in a second mode, the second mode consuming less power than a first mode; a second indication that operation in the second mode is acceptable; a third indication of operating in the second mode based on the elapsed first time period; or a fourth indication of returning to the first mode or transitioning to a third mode for wake-up based on a second time period.

[0215] Aspect 22 is the method according to aspect 21, wherein the UCI responds to the DL EOC indication from the network node.

[0216] Aspect 23 is a method according to any one of Aspects 16 to 22, wherein the status indication includes at least one of the following: a buffer status report (BSR) included in a medium access control (MAC) control element (MAC-CE); or a delay status report (DSR) indicating the status of the delay of the UE; and wherein the EOC is at least one of the following: an end-of-burst (EOB) indication, a physical downlink control channel (PDCCH) skip indication, a discontinuous reception (DRX) MAC-CE, a DL retransmission end indication, a DL feedback indication (DFI) indicating an acknowledgment (ACK) for a UL packet, or a Layer 1 (L1) or Layer 2 (L2) signaling indicating the end of cell DRX or the end of DRX activity time.

[0217] Aspect 24 is a method according to any one of aspects 16 to 23, the method further comprising: during a time period after the status indication is sent and before the estimated time: sending a UL grant to the UE for UL services associated with data in the buffer of the UE; and receiving the UL services from the UE based on the UL grant.

[0218] Aspect 25 is a method according to any one of aspects 16 to 24, the method further comprising: receiving from the UE a capability indication of at least one of a first capability of the UE to estimate service conditions or a second capability of the UE to provide the estimated time.

[0219] Aspect 26 is a method according to any one of Aspects 16 and 21 to 24, wherein the operating mode for the UE is: a first mode, wherein the UE is configured to operate in UL mode and DL mode; a second mode, wherein the UE is configured to operate in UL mode but not in DL mode; a third mode, wherein the UE is configured to operate with the modem off; or a fourth mode, wherein the UE is configured to skip monitoring of the physical downlink control channel (PDCCH); the method further includes: receiving from the UE an operation indication of autonomous switching of the UE for operation of the third mode or the second mode, wherein the operation indication includes at least one of uplink control information (UCI), media access control (MAC) control element (MAC-CE), or UE assistance information (UAI); and sending to the UE a wake-up signal (WUS) including a sequence type, wherein the sequence type is associated with a switch of the UE to another mode for the UE, the first mode, the second mode, the third mode, or the fourth mode.

[0220] Aspect 27 is the method according to aspect 26, wherein the sequence type is at least one of the following: a first sequence type, the first sequence type indicating that the UE is woken up and operates in a fifth mode, wherein the UE is configured to operate in the DL mode instead of the UL mode; a second sequence type, the second sequence type indicating that the UE restarts the retransmission time for retransmission monitoring; a third sequence type, the third sequence type indicating that the UE is woken up and operates in the second mode; or a fourth sequence type, the fourth sequence type including a payload of bits in the WUS, wherein the payload of bits corresponds to the first sequence type, the second sequence type or the third sequence type.

[0221] Aspect 28 is a device for wireless communication, the device including components for implementing any one of aspects 1 to 15.

[0222] Aspect 29 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code that, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 15.

[0223] Aspect 30 is an apparatus for wireless communication at a network node. The apparatus includes: a memory; and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to implement any one of aspects 1 to 15.

[0224] Aspect 31 is the apparatus according to aspect 30, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0225] Aspect 32 is an apparatus for wireless communication, the apparatus including components for implementing any one of aspects 16 to 27.

[0226] Aspect 33 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code that, when executed by at least one processor, causes the at least one processor to implement any one of aspects 16 to 27.

[0227] Aspect 34 is an apparatus for wireless communication at a network node. The apparatus includes: a memory; and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to implement any one of aspects 16 to 27.

[0228] Aspect 35 is the apparatus according to aspect 34, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to: Receive a downlink (DL) communication termination (EOC) indication triggered by a status indicator from the network node; and The status indication is sent to the network node based on the DL EOC indication, the status indication indicating the status of the following: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating the time when the UE estimates the arrival time of the next UL packet.

2. The apparatus of claim 1, wherein the at least one processor is further configured, alone or in any combination, to: The power state switching indication is received from the network node, the power state switching indication indicating the operating mode for the UE based on at least one of the state of the UE's buffer, the UE's delay, or the estimated time.

3. The apparatus according to claim 2, wherein the operating mode for the UE is: The first mode, wherein the UE is configured to operate in UL mode and DL mode; The second mode, wherein the UE is configured to operate in the UL mode instead of the DL mode; The third mode, wherein the UE is configured to operate with the modem off; The fourth mode, wherein the UE is configured to skip monitoring of the Physical Downlink Control Channel (PDCCH); or The fifth mode, wherein the UE is configured to operate in the DL mode but not in the UL mode.

4. The apparatus of claim 3, wherein the power state switching indication is based on the DL EOC indication and included in the downlink control information (DCI), wherein the power state switching indication indicates at least one of the following: The third mode is operated based on (i) the amount of data in the buffer of the UE being zero or (ii) the UE's ability to delay the transmission of data packets; or The second mode is operated based on the fact that the amount of data in the buffer of the UE is non-zero.

5. The apparatus of claim 3, wherein the state indication of sending the state indication of the buffer is based on the estimated time, wherein the estimated time indicates that the UE estimates the arrival time of the next UL packet to be shorter than the sleep time used by the UE to enter sleep mode, and wherein the power state switching indication indicates the operating mode for the UE as the second mode.

6. The apparatus of claim 2, further wherein the at least one processor is configured individually or in any combination to: The UE is switched to the operating mode based on the power state switching indication.

7. The apparatus of claim 1, wherein the at least one processor is further configured, alone or in any combination, to: The network node is sent uplink control information (UCI) including code points for the UE, wherein the code points for the UE indicate at least one of the following: The first indication of operation in the second mode is delayed, and the second mode consumes less power than the first mode. The second instruction is that operation in the second mode is acceptable. Based on a third instruction given after operating in the second mode for a first time period; or A fourth instruction to return to the first mode or switch to the third mode based on the second time period.

8. The apparatus of claim 7, wherein the UCI is transmitted based on a received DLEOC indication from the network node.

9. The apparatus of claim 1, wherein the status indication comprises at least one of the following: Includes the Buffer Status Report (BSR) in the Media Access Control (MAC) Control Element (MAC-CE); or A Delay Status Report (DSR) indicating the state of the delay of the UE; and The EOC is at least one of the following: End of Burst (EOB) indication, Physical Downlink Control Channel (PDCCH) skip indication, Discontinuous Receive (DRX) MAC-CE, DL Retransmission End Indication, DL Feedback Indication (DFI) indicating acknowledgment (ACK) for UL packets, or Layer 1 (L1) or Layer 2 (L2) signaling indicating the end of DRX for a cell or the end of DRX activity time.

10. The apparatus according to claim 1, further comprising: During the time period after the status indication is sent and before the estimated time: Receive from the network node UL approval for UL services associated with data in the buffer of the UE; and Based on the UL, permission is granted to send the UL service to the network node.

11. The apparatus of claim 1, wherein the at least one processor is further configured, alone or in any combination, to: The network node sends an indication to the UE of at least one of a first capability to estimate service conditions or a second capability to provide the estimated time.

12. The apparatus of claim 1, wherein the at least one processor is further configured, alone or in any combination, to: After sending the status indication, the UE autonomously switches to an operating mode for the UE, wherein the operating mode for the UE is: The first mode, wherein the UE is configured to operate in UL mode and DL mode; The second mode, wherein the UE is configured to operate in the UL mode instead of the DL mode; The third mode, wherein the UE is configured to operate with the modem off; The fourth mode, wherein the UE is configured to skip monitoring of the Physical Downlink Control Channel (PDCCH); or The fifth mode, wherein the UE is configured to operate in the DL mode but not in the UL mode.

13. The apparatus of claim 12, wherein the at least one processor is further configured, alone or in any combination, to: The network node sends an operation instruction to the UE for operation in the third mode or the second mode, wherein the operation instruction includes at least one of uplink control information (UCI), media access control (MAC) control element (MAC-CE), or UE assistance information (UAI).

14. The apparatus of claim 13, wherein the at least one processor is further configured, alone or in any combination, to: When in the operating mode, monitor wake-up signals (WUS) from the network node, including those of sequence type. Receive the WUS including the sequence type from the network node; and Based on the sequence type, the system switches to another mode among the first mode, the second mode, the third mode, or the fourth mode for the UE.

15. The apparatus of claim 14, wherein the sequence type is at least one of the following: A first sequence type indicates that the UE is woken up and operates in the fifth mode, in which the UE is configured to operate in the DL mode but not in the UL mode; The second sequence type indicates that the UE restarts the retransmission time for retransmission monitoring; A third sequence type, the third sequence type indicating that the UE is woken up and operates in the second mode; or A fourth sequence type, the fourth sequence type including the payload of bits in the WUS, wherein the payload of bits corresponds to the first sequence type, the second sequence type or the third sequence type.

16. An apparatus for wireless communication at a network node, the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to: Send a downlink (DL) communication termination (EOC) indication with a triggered status indication to the user equipment (UE); and The status indication is received from the UE and based on the DL EOC indication, the status indication indicating the status of the following: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating the time when the UE estimates the arrival time of the next UL packet.

17. The apparatus of claim 16, wherein the at least one processor is further configured, alone or in any combination, to: A power state switching indication is sent to the UE, the power state switching indication indicating an operating mode for the UE based on at least one of the UE's buffer, the UE's delay, or the state of the estimated time.

18. The apparatus of claim 17, wherein the operating mode for the UE is: The first mode, wherein the UE is configured to operate in UL mode and DL mode; The second mode, wherein the UE is configured to operate in the UL mode instead of the DL mode; The third mode, wherein the UE is configured to operate with the modem off; or The fourth mode, wherein the UE is configured to skip monitoring of the physical downlink control channel (PDCCH).

19. The apparatus of claim 18, wherein the power state switching indication is based on the UL EOC indication and included in the downlink control information (DCI), wherein the power state switching indication indicates at least one of the following: The third mode is operated based on (i) the amount of data in the buffer of the UE being zero or (ii) the UE's ability to delay the transmission of data packets; or The second mode is operated based on the fact that the amount of data in the buffer of the UE is non-zero.

20. The apparatus of claim 18, wherein receiving a state indication indicating the state of the buffer is based on the estimated time, wherein the estimated time indicates that the UE estimates the arrival time of the next UL packet to be shorter than the sleep time used by the UE to enter sleep mode, and wherein the power state switching indication indicates the operating mode for the UE as the second mode.

21. The apparatus of claim 16, wherein the at least one processor, alone or in any combination, is further configured to: The UE receives uplink control information (UCI) including code points for the UE, wherein the code points for the UE indicate at least one of the following: The first indication of operation in the second mode is delayed, and the second mode consumes less power than the first mode. The second instruction is that operation in the second mode is acceptable. Based on a third instruction given after operating in the second mode for a first time period; or A fourth instruction to return to the first mode or switch to the third mode based on the second time period.

22. The apparatus of claim 21, wherein the UCI responds to the DL EOC indication from the network node.

23. The apparatus of claim 16, wherein the status indication comprises at least one of the following: Includes the Buffer Status Report (BSR) in the Media Access Control (MAC) Control Element (MAC-CE); or A Delay Status Report (DSR) indicating the state of the delay of the UE; and The EOC is at least one of the following: End of Burst (EOB) indication, Physical Downlink Control Channel (PDCCH) skip indication, Discontinuous Receive (DRX) MAC-CE, DL Retransmission End Indication, DL Feedback Indication (DFI) indicating acknowledgment (ACK) for UL packets, or Layer 1 (L1) or Layer 2 (L2) signaling indicating the end of DRX for a cell or the end of DRX activity time.

24. The apparatus of claim 16, wherein the at least one processor is further configured, alone or in any combination, to: During the time period after receiving the status indication and before the estimated time: UL permission is granted to the UE for transmitting UL services associated with data in the buffer of the UE; and Based on the UL, the UE is authorized to receive the UL service.

25. The apparatus of claim 16, wherein the at least one processor is further configured, alone or in any combination, to: The UE receives at least one of the following: a first capability of the UE to estimate service conditions or a second capability of the UE to provide the estimated time.

26. The apparatus of claim 16, wherein the operating mode for the UE is: The first mode, wherein the UE is configured to operate in UL mode and DL mode; The second mode, wherein the UE is configured to operate in the UL mode instead of the DL mode; The third mode, wherein the UE is configured to operate with the modem off; The fourth mode, wherein the UE is configured to skip monitoring of the Physical Downlink Control Channel (PDCCH); or The fifth mode, wherein the UE is configured to operate in the DL mode but not in the UL mode; The at least one processor is further configured, individually or in any combination, to: The UE receives an operation instruction for autonomous handover, instructing the UE to operate in the third mode or the second mode, wherein the operation instruction includes at least one of uplink control information (UCI), media access control (MAC) control element (MAC-CE), or UE assistance information (UAI), and Send a wake-up signal (WUS) of a sequence type to the UE, wherein the sequence type is associated with the UE switching to another mode among the first mode, the second mode, the third mode, or the fourth mode for the UE.

27. The apparatus of claim 26, wherein the sequence type is at least one of the following: A first sequence type indicates that the UE is woken up and operates in the fifth mode, in which the UE is configured to operate in the DL mode but not in the UL mode; The second sequence type indicates that the UE restarts the retransmission time for retransmission monitoring; A third sequence type, the third sequence type indicating that the UE is woken up and operates in the second mode; or A fourth sequence type, the fourth sequence type including the payload of bits in the WUS, wherein the payload of bits corresponds to the first sequence type, the second sequence type or the third sequence type.

28. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive a downlink (DL) communication termination (EOC) indication triggered by a status indicator from the network node; as well as The status indication is sent to the network node based on the DL EOC indication, the status indication indicating the status of the following: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating the time when the UE estimates the arrival time of the next UL packet.

29. The method according to claim 28, further comprising: The power state switching indication is received from the network node, the power state switching indication indicating the operating mode for the UE based on at least one of the state of the UE's buffer, the UE's delay, or the estimated time.

30. A method for wireless communication at a network node, the method comprising: Send a downlink (DL) communication end (EOC) indication with a trigger status indication to the user equipment (UE); as well as The status indication is received from the UE and based on the DL EOC indication, the status indication indicating the status of the following: (i) the UE's buffer or the UE's delay, and (ii) an estimated time indicating the time when the UE estimates the arrival time of the next UL packet.

Images