CN111149392B

CN111149392B - Enhanced power saving through mobile-initiated dormancy

Info

Publication number: CN111149392B
Application number: CN201880063844.7A
Authority: CN
Inventors: S·K·拉古纳坦; S·巴拉苏布拉马尼安; P·克里希纳穆尔蒂; Y·基达内; C·查克拉瓦蒂; K·辛格; A·库马尔; K·R·曼达达普
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2017-10-04
Filing date: 2018-10-03
Publication date: 2023-07-18
Anticipated expiration: 2038-10-03
Also published as: US20190104474A1; WO2019070808A1; US11382042B2; EP3692749A1; CN111149392A; US20220295410A1

Abstract

Methods, systems, and devices are described for enhancing power savings in a wireless device through a mobile-initiated sleep procedure. A User Equipment (UE) may establish a Radio Resource Control (RRC) connection with a base station of a network and send and receive one or more different signaling messages for sleep state initialization and suspension at the UE. Sleep state implementation at the UE may save available power resources at the UE during periods of inactive data transactions. The one or more signaling messages may contain a single bit or multi-bit indication for the receiving device and may be sent via direct signaling on an upper layer protocol of the data network or mapped to allocated resources for data transmission. The signaling message may maintain synchronization between a functional mode of the UE interpreted at the base station and a mode implemented at the UE.

Description

Enhanced power saving through mobile-initiated dormancy

Cross reference

This patent application claims the benefit of the following applications: U.S. provisional patent application Ser. No.62/567,897 entitled "Enhanced Power Savings Through Mobile Initiated Dormancy," filed by Raghunathatn et al at 10/4 of 2017; and U.S. patent application Ser. No.16/149,534, entitled "Enhanced Power Savings Through Mobile Initiated Dormancy," filed by Raghunathatn et al at 10/2 of 2018; each of the above applications is assigned to the assignee of the present application.

Technical Field

The following relates generally to wireless communications, and more particularly to power saving techniques.

Background

Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems are able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (e.g., long Term Evolution (LTE) systems or LTE-advanced (LTE-a) systems) and fifth generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ techniques such as: code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), frequency Division Multiple Access (FDMA), orthogonal Frequency Division Multiple Access (OFDMA), or discrete fourier transform spread spectrum OFDM (DFT-S-OFDM). A wireless multiple-access communication system may include multiple base stations or network access nodes, each supporting communication for multiple communication devices, which may be otherwise referred to as User Equipment (UE), simultaneously.

The UE may be configured to communicate with one or more base stations of the established network connection. In some cases, to conserve at least battery resources, the UE may identify that it is to be in a period of persistent communication inactivity and initiate a procedure for entering a dormant state (e.g., based on expiration of an inactivity timer). Thus, the UE may enable data connection release from the base station. As a result, in case the persistent resource overhead between the base station and the serving MME of the UE is dedicated, synchronization between the UE and the base station may be prevented or lost. Furthermore, the UE may experience excessive latency due to repeated performance of association and authentication procedures (e.g., due to synchronization having been lost) when attempting connection reestablishment.

Disclosure of Invention

The described technology relates to improved methods, systems, devices or apparatus supporting power saving techniques, e.g., through a User Equipment (UE) initiated sleep procedure. In general, the described techniques provide for signaling to a base station over established Radio Resource Control (RRC), medium Access Control (MAC), and/or Physical (PHY) layer resources. The signaling from the UE may include a single or multi-bit indication for sleep state initialization at the UE. For example, the UE may determine one or more parameters for initiating a sleep state at the UE via an interface indication (e.g., a command-based binary protocol interface, such as a Mobile Station Modem (MSM) interface). The UE may evaluate service operation and determine that there is no data activity on the established network connection. The UE may then send a request to the coupled base station of the network connection to suspend the data transaction at the UE while maintaining the established RRC connection (e.g., a dormant state, which may be referred to as a fast dormant state).

The connection suspension request may correspond to different bit maps within the signaled resources of the transmission and may include additional priority (e.g., indicating urgency of the request) and duration indicators. The base station may respond with a response to the connection suspension request (connection suspension response) and based on the scheduled resources of the connection, the response may include an acknowledgement (acknowledgement) and/or a rejection (confirmation) of the initialization of the sleep state at the UE. The transmission and reception of connection suspension request and response messages may maintain synchronization between the base station and the UE within the network environment. In the case of a received sleep state acknowledgement, the UE may cache configuration parameters (including security context) of the connection with the base station and the extra layer protocol of the data network, and then enter a configured sleep state. The resources used for the caching process may correspond to locally or remotely stored static or modular memory resources configured for the UE. Additionally or alternatively, remote storage corresponding to a base station or established core network of the communication system may be implemented for caching context associated with the UE.

The triggering indication from an application processor coupled to the UE and/or a request for an upper layer of service (e.g., a non-access stratum (NAS)) may cause a connection re-establishment or restoration procedure to occur at the UE. In such a case, the UE may send a request for data service continuity to the base station within a previous connection environment of the RRC connection with the base station. In some cases, the base station may respond to the UE with a connection recovery acknowledgement based on cached security contexts and parameters (e.g., access Stratum (AS) security contexts and dedicated parameters) for previous connections with the UE or parameters for new configurations of the UE within the network environment. Alternatively, the base station may provide an indication to the UE for a connection release procedure to establish an idle camping state of the UE on the connected network cell. As a result, the UE may achieve RRC connection re-establishment or RRC connection release while maintaining connection synchronization with the base station and additional network elements of the communication system.

A method of wireless communication is described. The method may include: identifying that the power level of the UE is below a power threshold; transmitting a connection suspension request to a base station based at least in part on the identification, the connection suspension request to transition the UE from a connected state to a dormant state; and receiving a response to the connection suspension request from the base station, the response indicating whether the UE is to transition to the sleep state.

An apparatus for wireless communication is described. The apparatus may include: means for identifying that a power level of the UE is below a power threshold; means for sending a connection suspension request to a base station based at least in part on the identifying, the connection suspension request for transitioning the UE from a connected state to a dormant state; and means for receiving a response to the connection suspension request from the base station, the response indicating whether the UE is to transition to the sleep state.

Another apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be operable to cause the processor to: identifying that the power level of the UE is below a power threshold; transmitting a connection suspension request to a base station based at least in part on the identification, the connection suspension request to transition the UE from a connected state to a dormant state; and receiving a response to the connection suspension request from the base station, the response indicating whether the UE is to transition to the sleep state.

A non-transitory computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include instructions operable to cause a processor to: identifying that the power level of the UE is below a power threshold; transmitting a connection suspension request to a base station based at least in part on the identification, the connection suspension request to transition the UE from a connected state to a dormant state; and receiving a response to the connection suspension request from the base station, the response indicating whether the UE is to transition to the sleep state.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: a determination is made whether to transition to the dormant state based at least in part on the received response to the connection suspension request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: transition from the connected state to the dormant state is based at least in part on the response to the connection suspension request, wherein the response includes an acknowledgement of the connection suspension request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: the connection state is maintained based at least in part on the response to the connection suspension request, wherein the response includes a rejection of the connection suspension request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: transition to an idle state is based at least in part on the response to the connection suspension request, wherein the response includes a rejection of the connection suspension request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: and causing a modem of the UE to enter the dormant state, wherein the response includes an acknowledgement of the connection suspension request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: transition from the connected state to the dormant state is based at least in part on the response to the connection suspension request. Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: while in the dormant state, determining to resume communication with the base station. Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: and sending a connection recovery request for switching from the dormant state to the connection state to the base station.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: a response to the connection restoration request is received from the base station, the response to the connection restoration request acknowledging the connection restoration request. Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: transition from the dormant state to the connected state is based at least in part on the acknowledgement.

In some examples of the above methods, apparatus, and non-transitory computer-readable medium, the connection suspension request, or the response to the connection suspension request, or a connection resume request, or a response to the connection resume request may be sent using a Radio Resource Control (RRC) message, or layer 1 signaling, or a combination thereof.

In some examples of the above methods, apparatus, and non-transitory computer-readable medium, the layer 1 signaling comprises: uplink control information within a Physical Uplink Control Channel (PUCCH), or the uplink control information within a Physical Uplink Shared Channel (PUSCH), or an uplink Medium Access Control (MAC) Control Element (CE), or a combination thereof.

In some examples of the above method, apparatus, and non-transitory computer-readable medium, the connection suspension request includes an indication of: a duration for the dormant state, or a priority for the transition to the dormant state, or a request to store a security context for the UE, or a request to store one or more connection parameters for the UE, or a combination thereof.

In some examples of the above methods, apparatus, and non-transitory computer-readable medium, the connection suspension request includes an uplink Dedicated Control Channel (DCCH) message. In some examples of the above methods, apparatus, and non-transitory computer-readable medium, the response to the connection suspension request includes a downlink DCCH message.

A method of wireless communication is described. The method may include: receiving a connection suspension request from a User Equipment (UE), the connection suspension request for transitioning the UE from a connected state to a dormant state; determining whether to allow the UE to transition to the dormant state based at least in part on the connection suspension request; and sending a response to the connection suspension request to the UE, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based at least in part on the determination.

An apparatus for wireless communication is described. The apparatus may include: means for receiving a connection suspension request from a User Equipment (UE), the connection suspension request for transitioning the UE from a connected state to a dormant state; determining whether to allow the UE to transition to the dormant state based at least in part on the connection suspension request; and means for sending a response to the connection suspension request to the UE, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based at least in part on the determination.

Another apparatus for wireless communication is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be operable to cause the processor to: receiving a connection suspension request from a User Equipment (UE), the connection suspension request for transitioning the UE from a connected state to a dormant state; determining whether to allow the UE to transition to the dormant state based at least in part on the connection suspension request; and sending a response to the connection suspension request to the UE, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based at least in part on the determination.

A non-transitory computer-readable medium for wireless communication is described. The non-transitory computer-readable medium may include instructions operable to cause a processor to: receiving a connection suspension request from a User Equipment (UE), the connection suspension request for transitioning the UE from a connected state to a dormant state; determining whether to allow the UE to transition to the dormant state based at least in part on the connection suspension request; and sending a response to the connection suspension request to the UE, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based at least in part on the determination.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: determining to allow the UE to transition to the dormant state, wherein the response to the connection suspension request includes the acknowledgement of the connection suspension request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: a connection resume request is received from the UE for transitioning the UE from the dormant state to the connected state. Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: and sending a response to the connection recovery request to the UE, and confirming the connection recovery request according to the response to the connection recovery request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: determining to reject the UE to transition to the dormant state, wherein the response to the connection suspension request includes the rejection of the connection suspension request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: a command for the UE to transition to an idle state is sent based at least in part on receiving the connection suspension request.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: one or more communication parameter values for the UE are stored by the base station based at least in part on receiving the connection suspension request.

In some examples of the above method, apparatus, and non-transitory computer-readable medium, storing the one or more communication parameter values includes: and storing the security context of the UE.

Some examples of the above-described methods, apparatus, and non-transitory computer-readable media may further include processes, features, units, or instructions to: based at least in part on the received connection suspension request, identifying an indication of: the UE will be in the dormant state for a duration of time, or a priority associated with the transition to the dormant state, or a request to cache a UE security context, or a request to cache one or more UE connection parameters, or a combination thereof.

Drawings

Fig. 1 illustrates an example of a system for wireless communication that supports power saving in accordance with aspects of the present disclosure.

Fig. 2 illustrates an example of a wireless communication system supporting power conservation in accordance with aspects of the present disclosure.

Fig. 3 illustrates an example of a process flow in a system supporting power saving in accordance with aspects of the present disclosure.

Fig. 4-6 illustrate block diagrams of devices supporting power saving in accordance with aspects of the present disclosure.

Fig. 7 illustrates a block diagram of a system including a UE supporting power saving in accordance with aspects of the disclosure.

Fig. 8-10 illustrate block diagrams of devices supporting power saving in accordance with aspects of the present disclosure.

Fig. 11 illustrates a block diagram of a system including a base station supporting power saving in accordance with aspects of the disclosure.

Fig. 12-18 illustrate methods for power saving in accordance with aspects of the present disclosure.

Detailed Description

In a wireless communication system, a User Equipment (UE) may analyze resources of an established network connection and initiate a procedure for implementing a sleep state at the UE as a means for conserving power (e.g., available power of a battery). The application processor may evaluate the power state of the UE and associate the indicated state with a pre-configured threshold. In the event that the operable power capacity is below the threshold, the application processor may send an indication of the power state to a modem of the UE. The modem may receive the indication through a binary protocol interface of the UE (e.g., a Mobile Station Modem (MSM) interface) and formulate a command instruction associated with the protocol. The modem may analyze resources of one or more channels configured for data transmission and reception and scheduling operations at the UE and determine that there is no signaling associated with the UE.

Upon determining that signaling at the processor is inactive, the UE may send a different connection suspension request message to the base station for at least acknowledging (acknowledgement) and acknowledging (confirm) the sleep state at the UE. The request may correspond to a single bit or multi-bit command indication requesting a switch to a power save mode (e.g., sleep state) at the UE. In some cases, the UE may signal a connection suspension request via a UL Dedicated Control Channel (DCCH) transmission on a configured Signaling Radio Bearer (SRB) 1. In other cases, the UE may implement a different bit string (e.g., a Medium Access Control (MAC) Control Element (CE)) to carry the control indication of the request. The MAC CE may be implemented in one or more subheaders of a submitted MAC Protocol Data Unit (PDU). Alternatively, in other cases, the UE may map one or more bits of the connection suspension request within an Uplink Control Information (UCI) indication on physical layer (PHY) resources. The request may be mapped to one or more configured resource elements of an allocated resource block within a Physical Uplink Control Channel (PUCCH) and/or Physical Uplink Shared Channel (PUSCH) resource. In each of the above cases, the request indication for causing the sleep procedure to occur at the UE may at least implement a method for maintaining synchronization between the base station and the UE and preserving available power.

The base station may receive the transmitted signaling and/or an indication of the submission of the UE and generate a response to the connection suspension request. In some cases, the generated response may include a positive acknowledgement of the sleep state request of the UE, as well as an acknowledgement of the subsequent enablement of the power saving mode at the UE. In other cases, the generated response may include a connection suspension rejection, and a command indication to maintain an RRC connected state at the UE. The UE may receive the transmitted response to the connection suspension request from the base station and determine an operation mode of the UE. In the event of connection suspension acknowledgement and acknowledgement, the UE may cache security context and configuration parameters of the connection established with the base station and the extra layer protocol of the data network and enter a configured dormant state of the UE. The sleep state of the UE may allow the UE to operate with limited power consumption by avoiding data traffic on PHY layer resources while maintaining an RRC connection established with the base station.

A trigger indication from an application process and/or an upper layer (e.g., NAS) of an Evolved Packet Core (EPC) entity coupled to the UE requesting service may initiate a connection re-establishment process at the UE. The UE may signal a connection suspension request via a UL Dedicated Control Channel (DCCH) transmission on SRB 1. The base station may receive the transmitted signaling of the UE and process command information including the included bit request for reestablishing the data connection in the RRC connected state. In some cases, the base station may then respond with a connection recovery acknowledgement message on the DL DCCH resource. The UE may then implement a procedure for re-establishing (re-establishing) the previously established RRC connection state of the UE according to the cached or indicated security context of the connection. In other cases, the base station may initiate an RRC connection release procedure at the UE. As a result, the UE may transition to RRC idle mode on the camped cell of the network. The connection request and response of the UE and the base station may maintain synchronization between the functional mode of the UE interpreted at the base station and the mode implemented at the UE.

Aspects of the present disclosure are first described in the context of a wireless communication system. Aspects are also described in the context of signaling transmissions over configured network cells and in the process flow. Aspects of the present disclosure are further illustrated by, and described with reference to, apparatus diagrams, system diagrams, and flowcharts relating to power saving techniques for sleep initiated by a mobile device.

Fig. 1 illustrates an example of a wireless communication system 100 in accordance with various aspects of the present disclosure. The wireless communication system 100 includes a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an LTE-advanced (LTE-a) network, or a New Radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low cost and low complexity devices. The wireless communication system 100 may support signaling between the UE 115 and the base station that enables the UE 115 to enter a sleep state for efficient power saving.

Base station 105 may communicate wirelessly with UE 115 via one or more base station antennas. The base stations 105 described herein may include or may be referred to by those skilled in the art as base station transceivers, radio base stations, access points, radio transceivers, node bs, evolved node bs (enbs), next generation node bs or giganode bs (any of which may be referred to as a gNB), home node bs, home evolved node bs, or some other suitable terminology. The wireless communication system 100 may include different types of base stations 105 (e.g., macrocell base stations or small cell base stations). The UEs 115 described herein are capable of communicating with various types of base stations 105 and network devices (including macro enbs, small cell enbs, gnbs, relay base stations, etc.).

Each base station 105 may be associated with a particular geographic coverage area 110 in which communications with the respective UE 115 are supported. Each base station 105 may provide communication coverage for a respective geographic coverage area 110 via a communication link 125, and the communication link 125 between the base station 105 and the UE 115 may utilize one or more carriers. The communication links 125 shown in the wireless communication system 100 may include: uplink transmissions from UE 115 to base station 105, or downlink transmissions from base station 105 to UE 115. The downlink transmission may also be referred to as a forward link transmission, while the uplink transmission may also be referred to as a reverse link transmission.

The geographic coverage area 110 for a base station 105 may be divided into sectors that form only a portion of the geographic coverage area 110 and each sector may be associated with a cell. For example, each base station 105 may provide communication coverage for a macrocell, a small cell, a hotspot, or other type of cell, or various combinations thereof. In some examples, the base station 105 may be mobile and, thus, provide communication coverage for a mobile geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, and the overlapping geographic coverage areas 110 associated with different technologies may be supported by the same base station 105 or different base stations 105. The wireless communication system 100 may include, for example, heterogeneous LTE/LTE-a or NR networks, wherein different types of base stations 105 provide coverage for respective geographic coverage areas 110.

The term "cell" refers to a logical communication entity for communication (e.g., on a carrier) with the base station 105 and may be associated with an identifier (e.g., physical Cell Identifier (PCID), virtual Cell Identifier (VCID)) for distinguishing between neighboring cells operating via the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine Type Communication (MTC), narrowband internet of things (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types), which may provide access for different types of devices. In some cases, the term "cell" may refer to a portion (e.g., a sector) of the geographic coverage area 110 over which the logical entity operates.

The UEs 115 may be dispersed throughout the wireless communication system 100, and each UE 115 may be stationary or mobile. UE 115 may also be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, station, terminal, or client. The UE 115 may also be a personal electronic device such as a cellular telephone, a Personal Digital Assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 may also refer to a Wireless Local Loop (WLL) station, an internet of things (IoT) device, a internet of things (IoE) device, or an MTC device, etc., which may be implemented in various items such as appliances, vehicles, meters, etc.

Some UEs 115 (e.g., MTC or IoT devices) may be low cost or low complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication techniques that allow devices to communicate with each other or base station 105 without human intervention. In some examples, M2M communications or MTC may include communications from devices integrated with sensors or meters to measure or capture information and relay the information to a central server or application that may utilize or present the information to humans interacting with the program or application. Some UEs 115 may be designed to collect information or to implement automated behavior of the machine. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business billing.

Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communications (e.g., a mode that supports unidirectional communications via transmission or reception rather than simultaneous transmission and reception). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power saving techniques for UE115 include: when not engaged in active communications or operating on limited bandwidth (e.g., according to narrowband communications), a "deep sleep" mode of power saving is entered. In some cases, the UE115 may be designed to support critical functions (e.g., mission critical functions), and the wireless communication system 100 may be configured to provide ultra-reliable communications for these functions.

In some cases, the UE115 may also be capable of communicating directly with other UEs 115 (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). One or more of a group of UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside of the geographic coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some cases, multiple groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE115 transmits to each other UE115 in the group. In some cases, the base station 105 facilitates scheduling of resources for D2D communications. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

The base stations 105 may communicate with the core network 130 and with each other. For example, the base station 105 may interface with the core network 130 (e.g., via S1 or another interface) through a backhaul link 132. The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130) over the backhaul link 134 (e.g., via an X2 or other interface).

The core network 130 may provide user authentication, access authorization, tracking, internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an Evolved Packet Core (EPC) that may include at least one Mobility Management Entity (MME), at least one serving gateway (S-GW), and at least one Packet Data Network (PDN) gateway (P-GW). The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. The user IP packets may be transmitted through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address assignment as well as other functions. The P-GW may connect to network operator IP services. The operator IP services may include access to the internet, intranets, IP Multimedia Subsystem (IMS) or Packet Switched (PS) streaming services.

At least some of the network devices (e.g., base stations 105) may include a subcomponent such as an access network entity, which may be an example of an Access Node Controller (ANC). Each access network entity may communicate with UE 115 through a plurality of other access network transmission entities, which may be referred to as radio heads, intelligent radio heads, or transmission/reception points (TRPs). In some configurations, the various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or incorporated into a single network device (e.g., base station 105).

The wireless communication system 100 may operate using one or more frequency bands (typically in the range of 300MHz to 300 GHz). Typically, the region from 300MHz to 3GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band, because wavelengths range in length from approximately one decimeter to one meter. UHF waves may be blocked or redirected by building and environmental features. However, the waves may be sufficient to penetrate the structure for the macro cell to serve the UE 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 km) than transmission of smaller and longer waves using the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz.

The wireless communication system 100 may also operate in an ultra-high frequency (SHF) region using a frequency band from 3GHz to 30GHz (also referred to as a centimeter frequency band). The SHF region includes frequency bands such as the 5GHz industrial, scientific, and medical (ISM) band, which can be opportunistically used by devices that can tolerate interference from other users.

The wireless communication system 100 may also operate in the Extremely High Frequency (EHF) region of the spectrum (e.g., from 30GHz to 300 GHz), also referred to as the millimeter-frequency band. In some examples, wireless communication system 100 may support millimeter wave (mmW) communication between UE 115 and base station 105, and EHF antennas of respective devices may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate the use of antenna arrays within UE 115. However, the propagation of EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein may be employed on transmissions using one or more different frequency regions, and the designated use of the frequency bands spanning these frequency regions may vary depending on the country or regulatory agency.

In some cases, the wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed frequency band (e.g., 5GHz ISM band). When operating in the unlicensed radio frequency spectrum band, wireless devices (e.g., base station 105 and UE 115) may employ Listen Before Talk (LBT) procedures to ensure that frequency channels are idle before transmitting data. In some cases, operation in the unlicensed band may be based on a CA configuration of CCs operating in conjunction with the licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer transmissions, or a combination of these. The duplexing in the unlicensed spectrum may be based on Frequency Division Duplexing (FDD), time Division Duplexing (TDD), or a combination of both.

In some examples, base station 105 or UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, the wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., base station 105) and a receiving device (e.g., UE 115), where the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication may employ multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers (which may be referred to as spatial multiplexing). For example, the transmitting device may transmit multiple signals via different antennas or different combinations of antennas. Also, the receiving device may receive multiple signals via different antennas or different combinations of antennas. Each of the plurality of signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or a different data stream. Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (in which multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (in which multiple spatial layers are transmitted to multiple devices).

Beamforming (which may also be referred to as spatial filtering, directional transmission or directional reception) is a signal processing technique as follows: the techniques may be used at a transmitting device or a receiving device (e.g., base station 105 or UE 115) to form or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by: signals transmitted via antenna elements of the antenna array are combined such that signals propagating in a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. The adjusting of the signal transmitted via the antenna element may include: the transmitting device or the receiving device applies certain amplitude and phase offsets to the signals carried via each of the antenna elements associated with the device. The adjustment associated with each of the antenna elements may be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to an antenna array of the transmitting device or the receiving device, or relative to some other orientation).

In one example, the base station 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with the UE 115. For example, the base station 105 may transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions, which may include signals transmitted according to different sets of beamforming weights associated with different transmission directions. The transmissions in the different beam directions may be used (e.g., by the base station 105 or a receiving device (e.g., UE 115)) to identify the beam direction for subsequent transmission and/or reception by the base station 105. The base station 105 may transmit some signals (e.g., data signals associated with a particular receiving device) in a single beam direction (e.g., a direction associated with the receiving device (e.g., UE 115)). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based at least in part on signals transmitted in different beam directions. For example, the UE 115 may receive one or more of the signals transmitted by the base station 105 in different directions, and the UE 115 may report an indication to the base station 105 of the signal it received with the highest signal quality or otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted by the base station 105 in one or more directions, the UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by the UE 115) or in a single direction (e.g., to transmit data to a receiving device).

When receiving various signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) from the base station 105, a receiving device (e.g., UE 115, which may be an example of a mmW receiving device) may attempt multiple receive beams. For example, the receiving device may attempt multiple directions of reception by receiving via different antenna sub-arrays, by processing received signals according to different antenna sub-arrays, by receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array (any of the above operations may be referred to as "listening" according to different receive beams or directions of reception). In some examples, a receiving device may use a single receive beam to receive along a single beam direction (e.g., when receiving a data signal). A single receive beam may be aligned on a beam direction determined based at least in part on listening according to different receive beam directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality based at least in part on listening according to multiple beam directions).

In some cases, the antennas of base station 105 or UE 115 may be located within one or more antenna arrays, which may support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with the base station 105 may be located in different geographic locations. The base station 105 may have an antenna array with multiple rows and columns of antenna ports that the base station 105 may use to support beamforming for communication with the UE 115. Also, UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations.

In some cases, the wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. In some cases, a Radio Link Control (RLC) layer may perform packet segmentation and reassembly for transmission over logical channels. The Medium Access Control (MAC) layer may perform priority processing and multiplexing of logical channels to transport channels. The MAC layer may also use hybrid automatic repeat request (HARQ) to provide retransmissions at the MAC layer to improve link efficiency. In the control plane, a Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between the UE 115 and the base station 105 or core network 130, which supports radio bearers for user plane data. At the Physical (PHY) layer, transport channels may be mapped to physical channels.

In some cases, the UE 115 and the base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is a technique that increases the likelihood that data is properly received over the communication link 125. HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward Error Correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer under poor radio conditions (e.g., signal and noise conditions). In some cases, a wireless device may support the same slot HARQ feedback, where the device may provide HARQ feedback in a particular slot for data received in a previous symbol in the slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

May be in basic time units (which may for example refer to T _s Sample period=1/30,720,000 seconds) to represent a time interval in LTE or NR. The time intervals of the communication resources may be organized according to radio frames each having a duration of 10 milliseconds (ms), where a frame period may be denoted as T _f ＝307,200T _s . The radio frames may be identified by a System Frame Number (SFN) ranging from 0 to 1023. Each frame may include 10 subframes numbered from 0 to 9, and each subframe may have a duration of 1 ms. The subframe may be further divided into 2 slots, each slot having a duration of 0.5ms, and each slot may contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix added before each symbol period). Excluding the cyclic prefix, each symbol period may contain 2048 sampling periods. In some cases, a subframe may be the smallest scheduling unit of the wireless communication system 100 and may be referred to as a Transmission Time Interval (TTI). In other cases, the smallest schedule element of the wireless communication system 100 may be less than The frame is short or may be dynamically selected (e.g., in bursts of shortened TTIs (sTTI) or in selected component carriers using sTTI).

In some wireless communication systems, a time slot may be further divided into a plurality of minislots containing one or more symbols. In some examples, the symbols of the minislots or the minislots may be the smallest scheduling units. Each symbol may vary in duration depending on, for example, subcarrier spacing or frequency band of operation. Further, some wireless communication systems may implement slot aggregation, in which multiple slots or micro-slots are aggregated together and used for communication between the UE 115 and the base station 105.

The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications over the communication link 125. For example, the carrier of the communication link 125 may include portions of the radio frequency spectrum band that operate in accordance with the physical layer channel for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling. Carriers may be associated with predefined frequency channels, e.g., E-UTRA absolute radio frequency channel numbers (EARFCNs), and may be placed according to a channel grid for discovery by UEs 115. The carrier may be downlink or uplink (e.g., in FDD mode), or may be configured to carry downlink and uplink communications (e.g., in TDD mode). In some examples, the signal waveform transmitted on the carrier may be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as OFDM or DFT-s-OFDM).

The organization of carriers may be different for different radio access technologies (e.g., LTE-A, NR, etc.). For example, communications on carriers may be organized according to TTIs or time slots, each of which may include user data and control information or signaling to support decoding of the user data. The carrier may also include dedicated acquisition signaling (e.g., synchronization signals or system information, etc.) and control signaling to coordinate operation for the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers.

The physical channels may be multiplexed on the carrier according to various techniques. For example, the physical control channels and physical data channels may be multiplexed on the downlink carrier using Time Division Multiplexing (TDM), frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques. In some examples, control information transmitted in the physical control channel may be distributed among different control regions in a cascaded manner (e.g., between a common control region or common search space and one or more UE-specific control regions or UE-specific search spaces).

The carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a plurality of predetermined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) for a carrier of a particular radio access technology. In some examples, each served UE 115 may be configured to operate over part or all of the carrier bandwidth. In other examples, some UEs 115 may be configured for operation using narrowband protocol types associated with predefined portions or ranges (e.g., sets of subcarriers or RBs) within a carrier (e.g., an "in-band" deployment of narrowband protocol types).

In a system employing MCM techniques, a resource element may be composed of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme). Thus, the more resource elements received by the UE 115 and the higher the order of the modulation scheme, the higher the data rate for the UE 115 may be. In a MIMO system, wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers), and the use of multiple spatial layers may further increase the data rate for communication with UE 115.

Devices in the wireless communication system 100 (e.g., the base station 105 or the UE 115) may have a hardware configuration that supports communication over a particular carrier bandwidth or may be configurable to support communication over one of a set of carrier bandwidths. In some examples, wireless communication system 100 may include a base station 105 and/or a UE capable of supporting simultaneous communications via carriers associated with more than one different carrier bandwidth.

The wireless communication system 100 may support communication with UEs 115 over multiple cells or carriers (a feature that may be referred to as Carrier Aggregation (CA) or multi-carrier operation). According to a carrier aggregation configuration, UE 115 may be configured with multiple downlink CCs and one or more uplink CCs. Carrier aggregation may be used with both FDD and TDD component carriers.

In some cases, the wireless communication system 100 may utilize an enhanced component carrier (eCC). An eCC may be characterized by one or more features including: a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have sub-optimal or non-ideal backhaul links). An eCC may also be configured for use in unlicensed spectrum or shared spectrum (e.g., where more than one operator is allowed to use the spectrum). An eCC characterized by a wide carrier bandwidth may include one or more segments that may be used by UEs 115 that are unable to monitor the entire carrier bandwidth or are otherwise configured to use a limited carrier bandwidth (e.g., to save power).

In some cases, an eCC may utilize a different symbol duration than other CCs, which may include using a reduced symbol duration compared to the symbol durations of other CCs. A shorter symbol duration may be associated with an increased spacing between adjacent subcarriers. A device utilizing an eCC (e.g., UE 115 or base station 105) may transmit a wideband signal (e.g., according to a frequency channel or carrier bandwidth of 20, 40, 60, 80MHz, etc.) with a reduced symbol duration (e.g., 16.67 microseconds). The TTIs in an eCC may consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) may be variable.

In addition, wireless communication systems (such as NR systems) may utilize any combination of licensed, shared, and unlicensed spectrum bands. The flexibility of eCC symbol duration and subcarrier spacing may allow eCC to be used across multiple spectrums. In some examples, NR sharing of spectrum may improve spectrum utilization and spectrum efficiency, especially through dynamic vertical (e.g., across frequency) and horizontal (e.g., across time) sharing of resources.

Each of the UEs 115 may initiate connection establishment and synchronization with a network cell of the wireless communication system. The UE 115 may receive a broadcasted network identification (e.g., public land mobile network identity (PLMN-ID), physical Cell ID (PCI), etc.) and network capability indication from the base station 105 associated with the network cell for at least time slot and frame synchronization. Based at least in part on the synchronization, the UE 115 may be enabled to interpret system information received on System Information Block (SIB) and Master Information Block (MIB) resources and establish Downlink (DL) synchronization. The UE 115 may initiate a Random Access Procedure (RAP) with a base station and establish Uplink (UL) synchronization for obtaining Network Access Stratum (NAS) services. Prior to establishing the NAS connection, the UE 115 may establish a Radio Resource Control (RRC) protocol connection with the base station 105 of the network via Common Control Channel (CCCH) transmissions on Signaling Radio Bearer (SRB) 0. The RRC connection setup may include SRB1 configuration for Direct Control Channel (DCCH) signaling. The UE 115 may send NAS attach requests and Public Data Network (PDN) connection requests for Internet Protocol (IP) establishment over RRC connections. The base station 105 may establish a logical connection associated with the corresponding UE 115 at a serving Mobility Management Entity (MME) and a serving gateway (S-GW) of the core network and perform authentication. The S-GW may establish a default bearer and additional dedicated assignments for UE 115 to establish a connection to the PDN and assign an IP address to the UE. The one or more bearers may include a radio bearer connection between the base station and the UE, an S1 bearer between the base station 105 and the S-GW, and an S5/S8 bearer between the S-GW and a PDN gateway (P-GW) of the network. Based on the bearer assignment, the base station 105 may establish security parameters with the UE and may establish an IP connection at the UE 115.

As a means for conserving at least battery resources at UE 115, wireless communication system 100 may support UE-initiated dormant state implementations at UE 115. In some contexts (e.g., in LTE), the UE 115 may provide a detach request (via NAS signaling) to a serving MME entity of the UE 115 and perform autonomous release of Evolved Packet System (EPS) connection management (ECM). The MME may then implement session termination protocols for both the S-GW and the P-GW of the PDN, and locally deactivate the EPS bearer context assigned for the UE 115 without peer-to-peer signaling. As a result, the base station 105 of the established RRC connection may not be aware of the connection release at the UE 115. In case the persistent resource overhead between the base station and the corresponding serving MME of the UE 115 is dedicated, synchronization between the UE 115 and the base station 105 may be prevented. The features provided by the present disclosure include additional methods and features for enabling different RRC signaling transmissions and receptions between the UE 115 and the base station 105. The signaling may request and acknowledge sleep state implementation at the UE 115 while maintaining synchronous interpretation at the base station 105 and avoiding autonomous connection release procedures at the UE 115. Advantages of these provided features may include providing a smooth transition to a dormant state for the UE 115 that reduces the overall signaling required between the UE 115 and the base station 105 when the connection between the UE 115 and the base station 105 is re-activated or restored.

One or more of the UEs 115 within the wireless communication system 100 may include a modem and one or more configured application processors. The application processor may be coupled to the UE 115 via a command-based binary protocol interface (e.g., MSM interface) and may provide indication parameters for enabling and suspending a sleep state at the UE 115, including power state indication (e.g., for battery power level). For example, an application processor of UE 115 may provide an indication of a power level state below a pre-configured threshold. The modem of UE 115 may evaluate one or more service operations and determine that there is no data activity on the established network connection. Based on the inactivity detection at the modem and the signaling indication of the coupled application, the UE 115 may request a procedure for causing sleep state implementation to occur at the UE 115 as a means for improving battery power savings.

In some examples, each of the UEs 115 may be coupled to a network database of EPS connections. The database may be established locally within the data hardware of each UE 115 or remotely via a link connection. The database may include static and/or dynamic memory allocations specified for each of UEs 115. In the case of a dormant state implementation, each of the UEs 115 may cache at least the security context and configuration parameterization of the PDN connection within the RRC connection state implementation at the UE 115. Additional data context and authentication information corresponding to the UE 115 may be maintained at the network database by the UE 115 or a coupled network entity (e.g., base station 105, serving MME, HSS, etc.) of the established EPS connection.

Each of the base stations 105 may be configured to process RRC signaling messages for the UE 115 with respect to sleep state initialization and suspension requests. The signaling message may contain a bit indication value for the operation mode implementation at the UE 115. The base station 105 may evaluate at least the context of the established RRC connection and generate a response acknowledgement or rejection through different RRC signaling. The acknowledgement or rejection of the base station's response may maintain synchronization between the functional mode of the UE 115 interpreted at the base station 105 and the mode implemented at the UE 115. In some examples, each of the base stations 105 may be configured to process layer 1 signaling messages for the UE 115 with respect to sleep state initialization and suspension requests. Advantages of utilizing layer 1 signaling compared to RRC signaling may include implementing a faster communication mechanism for requests and responses between the base station 105 and the UE 115.

Fig. 2 illustrates an example of a wireless communication system 200 supporting power saving (e.g., sleep initiated by a mobile device) in accordance with various aspects of the disclosure. The wireless communication system 200 may represent at least a subcontext of the established EPS. In some examples, wireless communication system 200 may implement aspects of wireless communication system 100. For example, wireless communication system 200 includes UE 115-a and base station 105-a, which may be examples of corresponding devices described with reference to fig. 1. The wireless communication system 200 may support efficient battery conservation at the UE 115 through coherent signaling for transitioning to and from the dormant state.

The UE 115-a may be synchronized with the base station 105-a and camp on a configured network cell of the EPS connection. The UE 115-a may have an RRC connection established with the base station 105-a and may be configured to receive and transmit information 205 on licensed and unlicensed (shared) radio frequency spectrum band resources. Additional bearer context may be allocated to UE 115-a as part of the PDN connection to establish an end-to-end connection between UE 115-a and the P-GW of the serving network.

As a means for detecting at least parameterized values associated with functional components and/or operational states at the UE 115-a, one or more application processors may be coupled to the UE 115-a. For example, the application processor may evaluate the battery power state of the UE 115-a and determine that the operable battery capacity is below a configured power threshold. The application may send an indication of the battery status to the modem of the UE 115-a via the configured MSM interface of the UE 115-a and formulate command instructions associated with one or more protocols of the interface. The modem may interpret the received indication of the application and analyze the configured channel of the established connection and the scheduling operation at UE 115-a. Based on the analysis, the modem may determine that there is no signaling communication at the UE 115-a from the established network connection. In some cases, the modem may implement a timing duration for determining that signaling is not present. The timing may be configured in accordance with an EPC Mobility Management Entity (MME) sublayer of a Network Access Stratum (NAS) protocol and may be based at least in part on a bearer assignment (e.g., EPS bearer) of a Packet Data Network (PDN) connection establishment and a configured protocol of an RRC connection establishment.

After the determination of the signaling inactivity of the modem, the UE 115-a may send a different connection suspension request 210 to the base station 105-a to at least acknowledge and confirm the dormant state implementation at the UE 115-a. The connection suspension request 210 may correspond to a single bit command indication requesting to switch to a power saving mode (e.g., sleep state) at the UE 115-a and may include one or more additional bit indicators corresponding to a priority indication and/or an occurrence duration of the sleep state. In some cases, UE 115-a may signal a connection suspension request via UL DCCH resources on SRB 1 configured between base station 105-a and UE 115-a. For example, UE 115-a may configure the bit indication within a field structure of a different UL DCCH message indication. The bit indication may have a specified value or boolean value representing the sleep state request. Additionally, as a means for indicating the priority and/or duration values associated with the sleep state request, the UE 115-a may include one or more additional bit value indicators within the request message. UE 115-a may include spare bits within the field structure of the DCCH map for the purpose of padding to the octet boundary (e.g., octet alignment) indicated by the message and for ensuring forwarding capability on DCCH resources.

In other cases, the UE 115-a may implement a different bit string (e.g., MAC CE) within the MAC PDU for control indications regarding requests for control command exchanges between the UE 115-a and the base station 105-a. For example, the UE 115-a may submit a DL MAC PDU to the base station 105-a to transmit control and data indications in one or more concatenated MAC inputs, including a request to cause a sleep state to occur at the UE 115-a. The MAC CE may span a fixed number of bits (e.g., the MAC CE may be a fixed size) and may be assigned a unique Logical Channel ID (LCID) bit string contained within the MAC subheader. The field structure of the indicated MAC CE may be constructed from CCs of the channel in association with CA implementations enabled at UE 115-a. In particular, UE 115-a may provide a bit indication within the MAC CE per CC of the channel. As a means for indicating the priority and/or duration values associated with the sleep state request (e.g., indicating how long the UE will need or will want to be in the sleep state), the payload of the MAC CE indicated by the UE 115-a may include additional reserved bit elements mapped within the field structure of the MAC CE. For example, the UE 115-a may configure a unique 8-bit MAC CE to request a sleep state implementation at the UE 115-a. The UE 115-a may allocate a MAC CE within a subheader of the DL MAC PDU and define a field structure of one or more contained bits of the MAC CE according to at least the CA attribute of the channel. In the case of 4 CCs spanning the CA bandwidth of the channel, UE 115-a may define a field mapping within the MAC CE for each of the 4 bits corresponding to the CCs. The UE 115-a may reserve an additional 4 bits of the MAC CE as a means for ensuring octet boundaries (e.g., octet alignment) within the field map populated to the MAC CE and thus ensure forwarding capability within the MAC PDU. In some cases, the additional reserved bits of the MAC CE may contain priority and/or duration indications regarding the requested sleep state implementation at the UE 115-a.

Alternatively, in additional cases, UE115-a may map one or more included bits associated with the connection suspension request within UCI resources of UL data transmission on PDCCH and/or PUSCH resources. In particular, UE115-a may configure a bit indication within the reserved UCI mapping on the allocated resource blocks scheduled for UL data transmission. The bit indication may have a specified value or boolean value that represents at least a request for sleep state initialization or suspension. For example, UE115-a may configure the bit indication of UCI to a bit value of 1 for a connection suspension request. As a means for indicating the priority and/or duration values associated with the sleep state request, UE115-a may include one or more additional allocated bits within the UCI mapping. In some cases, the UE115-a may time multiplex one or more demodulation reference signal (DMRS) symbols within an allocated resource block of a transmission and maintain continuous signaling despite frequency diversity. UE115-a may direct UCI (including a configured bit indication of a connection suspension request) to resource elements in the allocated resource block that are near the multiplexed DMRS symbols for at least channel indication reliability and data acknowledgement.

The base station 105-a may receive one or more of the above-described signaling indications of the connection suspension request 210 from the UE115-a, including a bit request included to cause a sleep state to be implemented at the UE 115-a. The base station 105-a may process and interpret the contained command indication of the message payload and evaluate the context of at least the RRC connection established with the UE 115-a. Based at least in part on the interpretation and evaluation, the base station 105-a may generate a response 215 to the connection suspension request. Base station 105-a may signal response 215 on SRB 1 via DCCH resources. In some cases, the base station 105-a may generate a response transmission that includes a positive acknowledgement of the sleep state request of the UE115-a and an acknowledgement of the subsequent implementation of the sleep state. Alternatively, the base station 105a may generate a response transmission that includes a connection suspension rejection associated with the RRC context of the UE 115-a. The suspension rejection may include additional command instructions for maintaining the RRC connected state at the UE 115-a. Corresponding to receipt of a different connection suspension request message by the UE115-a, the acknowledgement or rejection of the response by the base station 105-a may maintain synchronization between the functional mode of the UE115-a interpreted at the base station 105-a and the mode subsequently implemented at the UE 115-a.

The UE 115-a may receive the transmitted response 215 from the base station 105-a and determine the mode of operation according to the submitted command indication. In the case of a connection suspension acknowledgement and acknowledgement message, the UE 115-a may cache one or more security contexts and/or configuration parameters of the RRC connection established with the base station 105-a and the additional bearer connection of the data network. Additionally, based at least in part on the connection suspension acknowledgement of the base station 105-a, the UE 115-a may enter a configured sleep state. In some cases, the caching operation of UE 115-a may include: the above-described context parameters of the connection are stored in a data storage unit coupled to the static and/or dynamic allocation of the database of UE 115-a. The database may be located locally within the hardware of the UE 115-a or may be coupled to the UE 115-a remotely via an application processor and/or a device interface. Additionally or alternatively, additional storage resources can be deployed at a packet data network gateway (P-GW) and/or serving gateway (e.g., layer 2 cache) element of the PDN and associated with the UE 115-a, or within available resources at the base station 105-a (e.g., layer 1 cache). The sleep state implemented at the UE 115-a may allow the UE 115-a to operate with limited power consumption by avoiding data traffic on PHY layer resources while maintaining RRC connection establishment with the base station 105-a. Alternatively, in the case of a connection suspension rejection message, the UE 115-a may maintain the RRC connected state of the UE 115-a and allow continuous data transactions with the base station 105-a. In some cases, the connection suspension rejection message may include a timing offset indication within the message payload. Based at least in part on the offset parameter, the UE 115-a may ignore, for a specified duration, one or more data inactivity detections at the modem or device state indications of one or more configured application processors associated with the UE 115-a.

The UE 115-a may request service on the MSM interface and/or via an upper layer (NAS) of the EPS via one or more coupled application processors configured to the UE 115-a, receive the trigger indication. The trigger may include one or more indications for data connection re-establishment at the UE 115-a. The modem of UE 115-a may process the encapsulated Short Message Service (SMS) entity transmission of the application processor indication or upper layer request and configure a connection restoration request 220 to base station 105-a. UE 115-a may signal connection restoration request 220 via UL DCCH resources on SRB 1 configured between base station 105-a and UE 115-a. For example, UE 115-a may configure the bit indication within a field structure of a different UL DCCH message indication. The bit indication may have a specified value or boolean value representing a connection (e.g., RRC connection state) resume request. For example, UE 115-a may configure the bit indication for UCI to a bit value of 0 for the connection recovery request. In addition, UE 115-a may include one or more additional bit value indicators within the request message as a means for indicating the priority and/or duration values associated with the connection restoration request. UE 115-a may include spare bits within the field structure of the DCCH map for the purpose of padding to the octet boundary (e.g., octet alignment) indicated by the message and for ensuring forwarding capability on DCCH resources.

The base station 105-a may receive one or more of the aforementioned connection recovery request signaling indications of the connection recovery request 220, including a bit request included to reestablish the data connection via the RRC connection configuration at the UE 115-a. The base station 105-a can process and interpret the contained command indication of the message payload and evaluate the context of the established PDN connection. Based at least in part on the indication and the evaluation, the base station 105-a can transmit a response 225 to the connection recovery request on the DL DCCH resource.

In some cases, the base station 105-a may respond on SRB 1 via a different connection resume confirm message. Within the payload of the resume confirm message, the base station 105-a may provide command instructions for establishing the cached security context and dedicated parameters for the established network connection. Alternatively, the base station 105-a may give the new security context and the dedicated parameters of the connection within the payload of the connection resume confirm message. Each of the security context and dedicated connection parameters may be configured within a field structure indicated by the DCCH message. The UE 115-a may then implement a procedure for causing the UE 115-a's previously established RRC connection state to reoccur based on the cached parameters or the newly indicated parameters.

In other cases, the base station 105-a may initiate an RRC connection release procedure corresponding to the UE 115-a. Specifically, the base station 105-a may provide a context release request to a serving MME of the UE 115-a via an S1-MME interface. The MME may cause a procedure to occur for tearing down EPS bearers of a connection established at the UE 115-a via communication with the S-GW. Based at least in part on the bearer release, the RRC connection of UE 115-a may be terminated and base station 105-a may provide an RRC connection release indication to UE 115-a. As a result, UE 115-a may transition to RRC idle mode on the camped cell of the network. Corresponding to receipt of the different connection restoration request messages of the UE 115-a, the acknowledgement or rejection of the response by the base station 105-a may maintain synchronization between the functional mode of the UE 115-a interpreted at the base station 105-a and the mode implemented at the UE 115-a.

Fig. 3 illustrates an example of a process flow 300 in a system supporting power saving (e.g., sleep initiated by a mobile device) in accordance with various aspects of the disclosure. In some examples, process flow 300 may implement aspects of wireless communication system 100. For example, process flow 300 includes UE 115-b and base station 105-b, which may be examples of corresponding devices described with reference to fig. 1 and 2. Process flow 300 may support maintaining synchronization between UE 115-b and base station 105-b after UE 115-b transitions to a dormant state. In addition, a transition to the dormant state may be preemptively requested by the UE 115-b, where the base station 105-b may respond with an acknowledgement or rejection of the requested transition.

At 305, the modem of UE 115-b may process the received signaling indication and command instructions corresponding to the battery state of UE 115-b. The signaling may be directed from a coupled application processor of UE 115-b and may be received through an MSM interface environment of UE 115-b. The modem may interpret the command instructions of the received application and analyze the source of the configured channel of the established connection and the scheduling operation at UE 115-b. Based at least in part on the analysis, the modem may determine that no data transaction exists at the UE 115-b. In some examples, a modem of UE 115-b or another component of UE 115-b may process received signaling instructions and command instructions corresponding to aspects of UE 115-b (other than the battery state of UE 115-b) for determining to transition to the sleep state. For example, the UE 115-b may determine to transition to the dormant state based on processing resources and associated activities or applications of the UE 115-b that do not require an active connection to the base station 105-b (regardless of battery state).

After the determination at the modem, the UE 115-b may send a connection suspension request message 310 to the base station 105-b. The request message may correspond to a single bit command indication requesting a switch to a power save mode (e.g., sleep state) at UE 115-a and may include one or more additional bit indicators corresponding to a priority indication and/or an occurrence duration of the sleep state. In some cases, the UE 115-b may signal a connection suspension request to the base station 105-b via a UL Dedicated Control Channel (DCCH) transmission on a Signaling Radio Bearer (SRB) 1 configured during RRC connection establishment. In other cases, the UE 115-b may implement a different bit string (e.g., a Medium Access Control (MAC) Control Element (CE)) to carry a control indication for a request for a control command exchange between the UE 115-b and the base station 105-b over a MAC layer protocol. Alternatively, in other cases, the UE 115-b may map one or more included bits of the connection suspension request in alignment with an Uplink Control Information (UCI) indication on PHY resources. The request may be mapped to one or more configured resource elements of an allocated resource block within a Physical Uplink Control Channel (PUCCH) and/or Physical Uplink Shared Channel (PUSCH) resource.

The base station 105-b may receive signaling and/or commit indication of the transmitted connection suspension request message 310, including the bit value included corresponding to the request to cause the sleep state to occur at the UE 115-b. The base station 105-b can evaluate the context of at least the RRC connection established with the UE 115-b and send a response message 315 to the connection suspension request on the DL DCCH resource. The response message 315 may include a positive acknowledgement of the sleep state request of the UE 115-b and an acknowledgement of the subsequent enablement of the power saving mode at the UE 115-b. Thus, the base station 105-b may initiate a transition to the dormant state with the UE 115-b before the inactivity timer expires.

At 320, UE 115-b may receive the transmitted response message 315 from base station 105-b and enter a configured sleep state for UE 115-b. The UE 115-b may cause an operational state change to occur at the UE 115-b based on the submitted command indication of the response message 315, including an acknowledgement and confirmation of the sleep state implementation at the UE 115-b. The UE 115-b may cache the security context and configuration parameters of the RRC connection established with the base station 105-b and the additional layer protocol of the established network connection in a coupled database of the wireless system.

At 325, the UE 115-b may process a trigger indication from one or more coupled application processors of the UE 115-b and/or an upper layer (e.g., NAS) of the EPC entity to request service. The trigger indication may initiate a connection re-establishment procedure at UE 115-b. UE 115-b may send connection resume request message 330 on SRB 1 via DL DCCH resources. The connection recovery request message may be a single bit or a multi-bit indication within a bit field structure that includes DCCH transmissions.

The base station 105-b may receive the transmitted connection resume request message 330 and process command information contained within the connection resume request message 330, including a bit request contained for reestablishing the RRC connection state at the UE 115-b. The base station 105-b may then respond with a connection recovery response message 335. In some cases, the connection resume response message 335 may require an RRC connection state reestablishment acknowledgement. Within the message payload corresponding to the recovery acknowledgement, the base station 105-b may provide command instructions for establishing a cached security context and dedicated parameters for the established network connection, or give new security context and dedicated parameters for the connection. Alternatively, the base station 105-b may initiate an RRC connection release procedure at the UE 115-b and the connection resume response message 335 may require an RRC connection release indication for the UE 115-b.

Fig. 4 illustrates a block diagram 400 of a wireless device 405 supporting power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the disclosure. The wireless device 405 may be an example of aspects of the UE 115 as described herein. The wireless device 405 may include a receiver 410, a UE communication manager 415, and a transmitter 420. The wireless device 405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

The receiver 410 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to enhanced power savings through mobile-initiated dormancy, etc.). Information may be passed to other components of the device. Receiver 410 may be an example of aspects of transceiver 735 described with reference to fig. 7. The receiver 410 may utilize a single antenna or a group of antennas.

The UE communication manager 415 may be an example of aspects of the UE communication manager 715 described with reference to fig. 7. At least some of the UE communication manager 415 and/or its various subcomponents may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software that is executed by a processor, the functions of UE communication manager 415 and/or at least some of its various sub-components may be performed by a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

At least some of the UE communication manager 415 and/or its various subcomponents may be physically located at various locations, including being distributed such that some of the functionality is implemented by one or more physical devices at different physical locations. In some examples, at least some of the UE communication manager 415 and/or its various subcomponents may be separate and distinct components in accordance with aspects of the present disclosure. In other examples, according to various aspects of the present disclosure, UE communication manager 415 and/or at least some of its various subcomponents may be combined with one or more other hardware components (including, but not limited to, an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof).

The UE communication manager 415 may: identifying that the power level of UE 115 is below a power threshold (e.g., a predetermined power threshold); transmitting a connection suspension request to the base station based at least in part on the identification, the connection suspension request to transition the UE 115 from the connected state to the dormant state; and receiving a response to the connection suspension request from the base station, the response indicating whether the UE 115 is to transition to the sleep state.

Transmitter 420 may transmit signals generated by other components of the device. In some examples, the transmitter 420 may be co-located with the receiver 410 in a transceiver module. For example, transmitter 420 may be an example of aspects of transceiver 735 described with reference to fig. 7. Transmitter 420 may utilize a single antenna or a group of antennas.

Fig. 5 illustrates a block diagram 500 of a wireless device 505 supporting power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the disclosure. The wireless device 505 may be an example of aspects of the wireless device 405 or the UE 115 as described with reference to fig. 4. The wireless device 505 may include a receiver 510, a UE communication manager 515, and a transmitter 520. The wireless device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

The receiver 510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to enhanced power savings through mobile-initiated dormancy, etc.). Information may be passed to other components of the device. Receiver 510 may be an example of aspects of transceiver 735 described with reference to fig. 7. The receiver 510 may utilize a single antenna or a group of antennas.

The UE communication manager 515 may be an example of aspects of the UE communication manager 715 described with reference to fig. 7. The UE communication manager 515 may also include a UE power manager 525, a connection suspension request component 530, and a UE sleep manager 535.

The UE power manager 525 may identify that the power level of the UE 115 is below a power threshold (e.g., a predetermined power threshold). For example, the UE power manager 525 may identify that a battery level or other available power level for a power supply of the UE 115 is below a threshold power level. The connection suspension request component 530 may send a connection suspension request to the base station based on the identification, the connection suspension request to transition the UE 115 from the connected state to the dormant state. In some cases, the connection suspension request includes an indication of: a duration for the dormant state, or a priority for transitions to the dormant state, or a request to store a security context for UE 115, or a request to store one or more connection parameters for UE 115, or a combination thereof. In some cases, the connection suspension request includes an uplink DCCH message.

The UE sleep manager 535 may receive a response from the base station 105 to the connection suspension request indicating whether the UE 115 is to transition to the sleep state. In some examples, the UE sleep manager 535 may determine whether to transition to the sleep state based on the received response to the connection suspension request. In other examples, UE sleep manager 535 may put the modem of UE 115 into a sleep state (i.e., put the modem of UE 115 into a sleep state), where the response includes an acknowledgement of the connection suspension request. In some examples, the UE sleep manager 535 may determine to resume communication with the base station while in the sleep state and receive a response to the connection resume request from the base station, the response acknowledging the connection resume request. In some cases, the response to the connection suspension request includes a downlink DCCH message. In some cases, the connection suspension request, or the response to the connection suspension request, or the connection resume request, or the response to the connection resume request, is sent using an RRC message, or layer 1 signaling, or a combination thereof. In some cases, layer 1 signaling includes: uplink control information within PUCCH, UCI within PUSCH, or uplink MAC CE, or a combination thereof.

Transmitter 520 may transmit signals generated by other components of the device. In some examples, transmitter 520 may be co-located with receiver 510 in a transceiver module. For example, transmitter 520 may be an example of aspects of transceiver 735 described with reference to fig. 7. Transmitter 520 may utilize a single antenna or a group of antennas.

Fig. 6 illustrates a block diagram 600 of a UE communication manager 615 supporting power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the disclosure. The UE communication manager 615 may be an example of aspects of the UE communication manager 415, the UE communication manager 515, or the UE communication manager 715 described with reference to fig. 4, 5, and 7. The UE communication manager 615 may include a UE power manager 620, a connection suspension request component 625, a UE sleep manager 630, a UE status manager 635, and a connection resume request component 640. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

The UE power manager 620 may identify that the power level of the UE 115 is below a power threshold. The connection suspension request component 625 may send a connection suspension request to the base station for transitioning the UE 115 from the connected state to the dormant state based on the identification. In some cases, the connection suspension request includes an indication of: a duration for the dormant state, or a priority for transitions to the dormant state, or a request to store a security context for UE 115, or a request to store one or more connection parameters for UE 115, or a combination thereof. In some cases, the connection suspension request includes an uplink DCCH message.

The UE sleep manager 630 may receive a response from the base station 105 to the connection suspension request indicating whether the UE 115 is to transition to the sleep state. In some examples, UE sleep manager 630 may determine whether to transition to the sleep state based on the received response to the connection suspension request. In some cases, UE sleep manager 630 may cause the modem of UE 115 to enter a sleep state (i.e., cause the modem of UE 115 to enter a sleep state), where the response includes an acknowledgement of the connection suspension request. In some examples, UE sleep manager 630 may determine to resume communication with base station 105 while in a sleep state and receive a response to the connection resume request from base station 105, the response acknowledging the connection resume request. In some cases, the response to the connection suspension request includes a downlink DCCH message.

The UE state manager 635 may transition from the connected state to the dormant state based on a response to the connection suspension request, where the response includes an acknowledgement of the connection suspension request. Alternatively, the UE state manager 635 may maintain the connection state based on a response to the connection suspension request, where the response includes a rejection of the connection suspension request. In some examples, the UE state manager 635 may transition to the idle state based on a response to the connection suspension request, where the response includes a rejection of the connection suspension request. In some examples, the UE state manager 635 may transition from the connected state to the dormant state based on a response to the connection suspension request and transition from the dormant state to the connected state based on an acknowledgement of the connection resume request.

The connection resume request component 640 can send a connection resume request to the base station 105 for transitioning from the dormant state to the connected state. In some cases, the connection suspension request, or the response to the connection suspension request, or the connection resume request, or the response to the connection resume request, is sent using an RRC message, or layer 1 signaling, or a combination thereof. In some cases, layer 1 signaling includes: uplink control information in PUCCH, or uplink control information in PUSCH, or uplink MAC CE, or a combination thereof.

Fig. 7 illustrates a diagram of a system 700 including a device 705 that supports power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the disclosure. Device 705 may be an example of or include components of: wireless device 405, wireless device 505, or UE 115 as described above (e.g., with reference to fig. 4 and 5). Device 705 may include components for two-way voice and data communications, including components for sending and receiving communications, including: UE communication manager 715, processor 720, memory 725, software 730, transceiver 735, antenna 740, and I/O controller 745. These components may be in electronic communication via one or more buses (e.g., bus 710). Device 705 may communicate wirelessly with one or more base stations 105.

Processor 720 may include intelligent hardware devices (e.g., a general purpose processor, a DSP, a Central Processing Unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof). In some cases, processor 720 may be configured to operate the memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 720. Processor 720 may be configured to execute computer-readable instructions stored in memory to perform various functions (e.g., functions or tasks that support enhanced power savings through mobile-initiated dormancy).

Memory 725 may include Random Access Memory (RAM) and read-only memory (ROM). The memory 725 may store computer-readable, computer-executable software 730 comprising instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 725 may contain, among other things, a basic input/output (I/O) system (BIOS) that may control basic hardware or software operations (e.g., interactions with peripheral components or devices).

Software 730 may include code for implementing aspects of the present disclosure including code for supporting enhanced power saving through mobile-initiated dormancy. The software 730 may be stored in a non-transitory computer readable medium (e.g., system memory or other memory). In some cases, software 730 may not be directly executable by a processor, but may instead cause a computer (e.g., when compiled and executed) to perform the functions described herein.

The transceiver 735 may communicate bi-directionally via one or more antennas, wired or wireless links as described above. For example, transceiver 735 may represent a wireless transceiver and may bi-directionally communicate with another wireless transceiver. Transceiver 735 may also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, as well as demodulate packets received from the antenna.

In some cases, the wireless device may include a single antenna 740. However, in some cases, a device may have more than one antenna 740 that is capable of concurrently transmitting or receiving multiple wireless transmissions.

I/O controller 745 may manage input and output signals for device 705. I/O controller 745 may also manage peripherals not integrated into device 705. In some cases, I/O controller 745 may represent a physical connection or port to an external peripheral device. In some cases, I/O controller 745 may utilize a controller such as Such as an operating system or another known operating system. In other cases, I/O controller 745 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I/O controller 745 may be implemented as part of a processor. In some cases, a user may interact with device 705 via I/O controller 745 or via hardware components controlled by I/O controller 745.

Fig. 8 illustrates a block diagram 800 of a wireless device 805 supporting power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the disclosure. Wireless device 805 may be an example of aspects of base station 105 as described herein. Wireless device 805 may include a receiver 810, a base station communication manager 815, and a transmitter 820. The wireless device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

The receiver 810 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to enhanced power savings through mobile-initiated dormancy, etc.). Information may be passed to other components of the device. Receiver 810 may be an example of aspects of transceiver 1135 described with reference to fig. 11. The receiver 810 may utilize a single antenna or a set of antennas.

The base station communication manager 815 may be an example of aspects of the base station communication manager 1115 described with reference to fig. 11. The base station communication manager 815 and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the base station communication manager 815 and/or at least some of its various sub-components may be performed by general-purpose processors, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in this disclosure.

The base station communication manager 815 and/or at least some of its various sub-components may be physically located at various locations, including being distributed such that some of the functionality is implemented at different physical locations by one or more physical devices. In some examples, the base station communication manager 815 and/or at least some of its various sub-components may be separate and distinct components in accordance with various aspects of the present disclosure. In other examples, base station communication manager 815 and/or at least some of its various subcomponents may be combined with one or more other hardware components (including, but not limited to, an I/O component, a transceiver, a network server, another computing device, one or more other components described in this disclosure, or a combination thereof) in accordance with various aspects of this disclosure.

The base station communication manager 815 may perform the following operations: receiving a connection suspension request from the UE 115 for transitioning the UE 115 from the connected state to the dormant state; determining whether to allow the UE 115 to transition to the sleep state based on the connection suspension request; and sending a response to the connection suspension request to the UE 115, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based on the determination.

The transmitter 820 may transmit signals generated by other components of the device. In some examples, the transmitter 820 may be co-located with the receiver 810 in a transceiver module. For example, the transmitter 820 may be an example of aspects of the transceiver 1135 described with reference to fig. 11. Transmitter 820 may utilize a single antenna or a set of antennas.

Fig. 9 illustrates a block diagram 900 of a wireless device 905 supporting power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the disclosure. The wireless device 905 may be an example of aspects of the wireless device 805 or the base station 105 as described with reference to fig. 8. The wireless device 905 may include a receiver 910, a base station communication manager 915, and a transmitter 920. The wireless device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

The receiver 910 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to enhanced power savings through mobile-initiated dormancy, etc.). Information may be passed to other components of the device. Receiver 910 may be an example of aspects of transceiver 1135 described with reference to fig. 11. The receiver 910 may utilize a single antenna or a group of antennas.

The base station communication manager 915 may be an example of aspects of the base station communication manager 1115 described with reference to fig. 11. The base station communication manager 915 may also include a connection manager 925, a base station sleep manager 930, and a response manager 935.

The connection manager 925 may receive a connection suspension request from the UE 115 for transitioning the UE 115 from the connected state to the dormant state. In some examples, the connection manager 925 may determine to allow the UE 115 to transition to a dormant state, where the response to the connection suspension request includes an acknowledgement of the connection suspension request. In some cases, the connection manager 925 may receive a connection resume request from the UE 115 to transition the UE 115 from the dormant state to the connected state. The connection manager 925 may determine to reject the UE 115 to transition to the dormant state, wherein the response to the connection suspension request includes a rejection of the connection suspension request. In some examples, the connection manager 925 may send a command for the UE 115 to transition to the idle state based on receiving the connection suspension request. In some cases, the connection suspension request, or the response to the connection suspension request, or the connection resume request, or the response to the connection resume request, is sent using an RRC message, or layer 1 signaling, or a combination thereof. In some cases, layer 1 signaling includes: uplink control information in PUCCH, or uplink control information in PUSCH, or uplink MAC CE, or a combination thereof. In some cases, the connection suspension request includes an uplink DCCH message.

The base station sleep manager 930 may: identifying, based on the received connection suspension request, an indication of: the duration that the UE 115 will be in the dormant state, or a priority associated with a transition to the dormant state, or a request to cache a UE security context, or a request to cache one or more UE connection parameters, or a combination thereof; and determining whether to allow the UE 115 to transition to the sleep state based on the connection suspension request.

The response manager 935 may do the following: transmitting a response to the connection suspension request to the UE 115, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based on the determination; and sending a response to the connection restoration request to the UE, the response acknowledging the connection restoration request. In some cases, the response to the connection suspension request includes a downlink DCCH message.

Transmitter 920 may transmit signals generated by other components of the device. In some examples, the transmitter 920 may be co-located with the receiver 910 in a transceiver module. For example, the transmitter 920 may be an example of aspects of the transceiver 1135 described with reference to fig. 11. Transmitter 920 may utilize a single antenna or a group of antennas.

Fig. 10 illustrates a block diagram 1000 of a base station communication manager 1015 supporting power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the disclosure. The base station communication manager 1015 may be an example of aspects of the base station communication manager 1115 described with reference to fig. 8, 9, and 11. Base station communication manager 1015 may include a connection manager 1020, a base station sleep manager 1025, a response manager 1030, and a cache component 1035. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

The connection manager 1020 may receive a connection suspension request from the UE115 for transitioning the UE115 from the connected state to the dormant state. In some examples, connection manager 1020 may determine to allow UE115 to transition to a dormant state, where the response to the connection suspension request includes an acknowledgement of the connection suspension request. In some cases, connection manager 1020 may receive a connection resume request from UE115 to transition UE115 from the dormant state to the connected state. The connection manager 1020 may determine to reject the UE115 to transition to the dormant state, wherein the response to the connection suspension request includes a rejection of the connection suspension request. In some examples, connection manager 1020 may send a command for UE115 to transition to the idle state based on receiving the connection suspension request. In some cases, the connection suspension request, or the response to the connection suspension request, or the connection resume request, or the response to the connection resume request, is sent using an RRC message, or layer 1 signaling, or a combination thereof. In some cases, layer 1 signaling includes: uplink control information in PUCCH, or uplink control information in PUSCH, or uplink MAC CE, or a combination thereof. In some cases, the connection suspension request includes an uplink DCCH message.

The base station sleep manager 1025 may do the following: identifying, based on the received connection suspension request, an indication of: the duration that the UE 115 will be in the dormant state, or a priority associated with a transition to the dormant state, or a request to cache a UE security context, or a request to cache one or more UE connection parameters, or a combination thereof; and determining whether to allow the UE 115 to transition to the sleep state based on the connection suspension request.

Response manager 1030 may do the following: transmitting a response to the connection suspension request to the UE, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based on the determination; and transmitting a response to the connection restoration request to the UE 115, the response acknowledging the connection restoration request. In some cases, the response to the connection suspension request includes a downlink DCCH message.

The cache component 1035 may store, by the base station, one or more communication parameter values for the UE based on receiving the connection suspension request. In some cases, storing the one or more communication parameter values includes: the security context of UE 115 is stored.

Fig. 11 illustrates a diagram of a system 1100 including a device 1105 supporting power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the disclosure. The device 1105 may be an example of the base station 105 or a component comprising the base station 105 as described above (e.g., with reference to fig. 1). Device 1105 may include components for bi-directional voice and data communications including components for sending and receiving communications, including: base station communication manager 1115, processor 1120, memory 1125, software 1130, transceiver 1135, antenna 1140, network communication manager 1145, and inter-station communication manager 1150. These components may be in electronic communication via one or more buses (e.g., bus 1110). The device 1105 may communicate wirelessly with one or more UEs 115.

Processor 1120 may include intelligent hardware devices (e.g., a general purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1120 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1120. The processor 1120 may be configured to execute computer-readable instructions stored in memory to perform various functions (e.g., functions or tasks that support enhanced power savings through mobile-initiated dormancy).

The memory 1125 may include RAM and ROM. Memory 1125 may store computer-readable, computer-executable software 1130 comprising instructions that, when executed, cause a processor to perform the various functions described herein. In some cases, memory 1125 may contain, among other things, a BIOS that may control basic hardware or software operations (e.g., interactions with peripheral components or devices).

Software 1130 may include code for implementing aspects of the present disclosure including code for supporting power saving techniques such as mobile-initiated dormancy. Software 1130 may be stored in a non-transitory computer readable medium (e.g., system memory or other memory). In some cases, software 1130 may not be directly executable by a processor, but may instead cause a computer (e.g., when compiled and executed) to perform the functions described herein.

The transceiver 1135 may communicate bi-directionally via one or more antennas, wired or wireless links as described above. For example, transceiver 1135 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1135 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, as well as demodulate packets received from the antenna. In some cases, the wireless device may include a single antenna 1140. However, in some cases, a device may have more than one antenna 1140 that is capable of concurrently transmitting or receiving multiple wireless transmissions.

The network communication manager 1145 may manage communications with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1145 may manage the transmission of data communications for a client device (e.g., one or more UEs 115).

The inter-station communication manager 1150 may manage communications with other base stations 105 and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the inter-station communication manager 1150 may coordinate scheduling of transmissions to the UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communication manager 1150 may provide an X2 interface within Long Term Evolution (LTE)/LTE-a wireless communication network technology to provide communication between the base stations 105.

Fig. 12 shows a flow chart illustrating a method 1200 for power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the present disclosure. The operations of method 1200 may be implemented by UE 115 or components thereof as described herein. For example, the operations of method 1200 may be performed by a UE communication manager as described with reference to fig. 4-7. In some examples, UE 115 may execute a set of codes to control the functional units of the device to perform the functions described below. Additionally or alternatively, UE 115 may perform aspects of the functionality described below using dedicated hardware.

At 1205, the UE 115 may identify that the power level of the UE 115 is below a power threshold. Operations of 1205 may be performed in accordance with the methods described herein. In some examples, aspects of the operation of 1205 may be performed by a UE power manager as described with reference to fig. 4-7.

At 1210, the UE 115 may send a connection suspension request to the base station 105 for transitioning the UE from the connected state to the dormant state based at least in part on the identification. The operations of 1210 may be performed according to the methods described herein. In some examples, aspects of the operation of 1210 may be performed by a connection suspension request component as described with reference to fig. 4-7.

At 1215, the UE 115 may receive a response from the base station to the connection suspension request indicating whether the UE 115 is to transition to the dormant state. The operations of 1215 may be performed according to the methods described herein. In some examples, aspects of the operation of 1215 may be performed by a UE sleep manager as described with reference to fig. 4-7.

Fig. 13 shows a flow chart illustrating a method 1300 for power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the present disclosure. The operations of method 1300 may be implemented by UE 115 or components thereof as described herein. For example, the operations of method 1300 may be performed by a UE communication manager as described with reference to fig. 4-7. In some examples, UE 115 may execute a set of codes to control the functional units of the device to perform the functions described below. Additionally or alternatively, UE 115 may perform aspects of the functionality described below using dedicated hardware.

At 1305, the UE 115 may identify that the power level of the UE 115 is below a power threshold. 1305 may be performed according to the methods described herein. In some examples, aspects of the operation of 1305 may be performed by a UE power manager as described with reference to fig. 4-7.

At 1310, the UE 115 may send a connection suspension request to the base station 105 for transitioning the UE 115 from the connected state to the dormant state based at least in part on the identifying. Operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operation of 1310 may be performed by a connection suspension request component as described with reference to fig. 4-7.

At 1315, UE 115 may receive a response to the connection suspension request from base station 105 indicating whether UE 115 is to transition to a dormant state, where the response includes an acknowledgement of the connection suspension request. The operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operation of 1315 may be performed by a UE sleep manager as described with reference to fig. 4-7.

At 1320, UE 115 may transition from the connected state to the dormant state based at least in part on a response to the connection suspension request. Operations of 1320 may be performed according to the methods described herein. In some examples, aspects of the operation of 1320 may be performed by a UE state manager as described with reference to fig. 4-7.

At 1325, UE 115 may put the modem of UE 115 into a dormant state (i.e., put the modem of UE 115 into a dormant state). 1325 may be performed according to the methods described herein. In some examples, aspects of the operation of 1325 may be performed by a UE sleep manager as described with reference to fig. 4-7.

Fig. 14 shows a flow chart illustrating a method 1400 for power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the present disclosure. The operations of the method 1400 may be implemented by the UE 115 or components thereof as described herein. For example, the operations of method 1400 may be performed by a UE communication manager as described with reference to fig. 4-7. In some examples, UE 115 may execute a set of codes to control the functional units of the device to perform the functions described below. Additionally or alternatively, UE 115 may perform aspects of the functionality described below using dedicated hardware.

At 1405, UE 115 may identify that the power level of UE 115 is below a power threshold. 1405 may be performed according to the methods described herein. In some examples, aspects of the operation of 1405 may be performed by a UE power manager as described with reference to fig. 4-7.

At 1410, the UE 115 may send a connection suspension request to the base station 105 for transitioning the UE 115 from the connected state to the dormant state based at least in part on the identification. The operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operation of 1410 may be performed by a connection suspension request component as described with reference to fig. 4-7.

At 1415, the UE 115 may receive a response to the connection suspension request from the base station 105 indicating whether the UE 115 is to transition to the dormant state, wherein the response includes a rejection of the connection suspension request. 1415 may be performed according to the methods described herein. In some examples, aspects of the operation of 1415 may be performed by a UE sleep manager as described with reference to fig. 4-7.

At 1420, UE 115 may maintain the connection state based at least in part on the response to the connection suspension request. Operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operation of 1420 may be performed by a UE state manager as described with reference to fig. 4-7.

Fig. 15 shows a flow chart illustrating a method 1500 for power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the present disclosure. The operations of method 1500 may be implemented by UE 115 or components thereof as described herein. For example, the operations of method 1500 may be performed by a UE communication manager as described with reference to fig. 4-7. In some examples, UE 115 may execute a set of codes to control the functional units of the device to perform the functions described below. Additionally or alternatively, UE 115 may perform aspects of the functionality described below using dedicated hardware.

At 1505, UE 115 may identify that the power level of UE 115 is below a power threshold. The operations of 1505 may be performed according to the methods described herein. In some examples, aspects of the operation of 1505 may be performed by a UE power manager as described with reference to fig. 4-7.

At 1510, UE 115 may send a connection suspension request to base station 105 for transitioning UE 115 from a connected state to a dormant state based at least in part on the identification. 1510 may be performed according to the methods described herein. In some examples, aspects of the operation of 1510 may be performed by a connection suspension request component as described with reference to fig. 4-7.

At 1515, UE 115 may receive a response from base station 105 to the connection suspension request indicating whether UE 115 is to transition to the dormant state. The operations of 1515 may be performed according to methods described herein. In some examples, aspects of the operation of 1515 may be performed by a UE sleep manager as described with reference to fig. 4-7.

At 1520, UE 115 may transition from the connected state to the dormant state based at least in part on the response to the connection suspension request. Operations of 1520 may be performed according to the methods described herein. In some examples, aspects of the operation of 1520 may be performed by a UE state manager as described with reference to fig. 4-7.

At 1525, UE 115 may determine to resume communication with base station 105 while in a dormant state. Operations of 1525 may be performed according to the methods described herein. In some examples, aspects of the operation of 1525 may be performed by a UE sleep manager as described with reference to fig. 4-7.

At 1530, UE 115 may send a connection resume request to base station 105 for transitioning from the dormant state to the connected state. The operations of 1530 may be performed in accordance with the methods described herein. In some examples, aspects of the operation of 1530 may be performed by a connection recovery request component as described with reference to fig. 4-7.

Fig. 16 shows a flow chart illustrating a method 1600 for power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the present disclosure. The operations of method 1600 may be implemented by base station 105 or components thereof as described herein. For example, the operations of method 1600 may be performed by a base station communication manager as described with reference to fig. 8-11. In some examples, the base station 105 may execute a set of codes to control the functional units of the device to perform the functions described below. Additionally or alternatively, the base station 105 may use dedicated hardware to perform aspects of the functions described below.

At 1605, the base station 105 may receive a connection suspension request from the UE 115 for transitioning the UE 115 from a connected state to a dormant state. The operations of 1605 may be performed according to the methods described herein. In some examples, aspects of the operation of 1605 may be performed by a connection manager as described with reference to fig. 8-11.

At 1610, the base station 105 may determine whether to allow the UE 115 to transition to the sleep state based at least in part on the connection suspension request. The operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operation of 1610 may be performed by a base station dormancy manager as described with reference to fig. 8-11.

At 1615, the base station 105 may send a response to the connection suspension request to the UE 115, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based at least in part on the determination. 1615 may be performed according to the methods described herein. In some examples, aspects of the operation of 1615 may be performed by a response manager as described with reference to fig. 8-11.

Fig. 17 shows a flow chart illustrating a method 1700 for power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the present disclosure. The operations of method 1700 may be implemented by base station 105 or components thereof as described herein. For example, the operations of method 1700 may be performed by a base station communication manager as described with reference to fig. 8-11. In some examples, the base station 105 may execute a set of codes to control the functional units of the device to perform the functions described below. Additionally or alternatively, the base station 105 may use dedicated hardware to perform aspects of the functions described below.

At 1705, the base station 105 may receive a connection suspension request from the UE 115 for transitioning the UE 115 from the connected state to the dormant state. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operation of 1705 may be performed by a connection manager as described with reference to fig. 8-11.

At 1710, the base station 105 may determine to allow the UE to transition to the sleep state. Operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operation of 1710 may be performed by a connection manager as described with reference to fig. 8-11.

At 1715, the base station 105 may send a response to the connection suspension request to the UE 115, the response including an acknowledgement of the connection suspension request based at least in part on the determination. 1715 may be performed according to the methods described herein. In some examples, aspects of the operation of 1715 may be performed by a response manager as described with reference to fig. 8-11.

Fig. 18 shows a flow chart illustrating a method 1800 for power saving (e.g., sleep initiated by a mobile device) in accordance with aspects of the present disclosure. The operations of method 1800 may be implemented by base station 105 or components thereof as described herein. For example, the operations of method 1800 may be performed by a base station communication manager as described with reference to fig. 8-11. In some examples, the base station 105 may execute a set of codes to control the functional units of the device to perform the functions described below. Additionally or alternatively, the base station 105 may use dedicated hardware to perform aspects of the functions described below.

At 1805, the base station 105 may receive a connection suspension request from the UE 115 for transitioning the UE 115 from the connected state to the dormant state. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operation of 1805 may be performed by a connection manager as described with reference to fig. 8-11.

At 1810, the base station 105 may identify, based at least in part on the received connection suspension request, an indication of: the duration that the UE 115 will be in the dormant state, or a priority associated with a transition to the dormant state, or a request to cache a UE security context, or a request to cache one or more UE connection parameters, or a combination thereof. 1810 may be performed according to the methods described herein. In some examples, aspects of the operation of 1810 may be performed by a base station sleep manager as described with reference to fig. 8-11.

At 1815, the base station 105 may determine whether to allow the UE 115 to transition to the sleep state based at least in part on the connection suspension request. The operations of 1815 may be performed according to methods described herein. In some examples, aspects of the operation of 1815 may be performed by a base station sleep manager as described with reference to fig. 8-11.

At 1820, the base station 105 may transmit a response to the connection suspension request to the UE 115, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based at least in part on the determination. The operations of 1820 may be performed in accordance with the methods described herein. In some examples, aspects of the operation of 1820 may be performed by a response manager as described with reference to fig. 8-11.

It should be noted that the methods described above describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Further, aspects from two or more methods may be combined.

The techniques described herein may be used for various wireless communication systems such as Code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), frequency Division Multiple Access (FDMA), orthogonal Frequency Division Multiple Access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and other systems. A CDMA system may implement a radio technology such as CDMA2000, universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. The IS-2000 version may be generally referred to as CDMA2000 1X, etc. IS-856 (TIA-856) IS commonly referred to as CDMA2000 1xEV-DO, high Rate Packet Data (HRPD), or the like. UTRA includes wideband CDMA (W-CDMA) and other variations of CDMA. TDMA systems may implement radio technologies such as global system for mobile communications (GSM).

OFDMA systems may implement radio technologies such as Ultra Mobile Broadband (UMB), evolved UTRA (E-UTRA), institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, flash-OFDM, and the like. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). LTE and LTE-a are versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, NR and GSM are described in documents from an organization named "3 rd generation partnership project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "3 rd generation partnership project 2" (3 GPP 2). The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. Although aspects of an LTE or NR system may be described for purposes of example and LTE or NR terminology may be used in much of the description, the techniques described herein may be applicable to areas outside of LTE or NR applications.

A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs 115 with service subscription with the network provider. The small cell may be associated with a lower power base station 105 than the macro cell, and the small cell may operate in the same or a different (e.g., licensed, unlicensed, etc.) frequency band as the macro cell. According to various examples, small cells may include pico cells, femto cells, and micro cells. For example, a pico cell may cover a small geographic area and may allow unrestricted access by UEs 115 with service subscription with the network provider. A femto cell may also cover a small geographic area (e.g., a residence) and may provide limited access by UEs 115 having an association with the femto cell (e.g., UEs 115 in a Closed Subscriber Group (CSG), UEs 115 for users in the residence, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, pico eNB, femto eNB, or home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells and may also support communications using one or more component carriers.

The wireless communication system 100 or systems described herein may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timings, and transmissions from different base stations 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable Logic Device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software for execution by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwired or a combination of any of these items. Features that implement the functions may also be physically located at various locations including being distributed such that each portion of the functions is implemented at a different physical location.

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can comprise Random Access Memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact Disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code elements in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Further, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes CD, laser disc, optical disc, digital Versatile Disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

As used herein (including in the claims), an "or" as used in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of" indicates an inclusive list, such that, for example, a list of at least one of A, B or C means a or B or C or AB or AC or BC or ABC (i.e., a and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, exemplary steps described as "based on condition a" may be based on both condition a and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on" is interpreted.

In the drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type may be distinguished by following the reference label by a dash and a second label that is used to distinguish between similar components. If only a first reference label is used in the specification, the description applies to any one of the similar components having the same first reference label, irrespective of second or other subsequent reference labels.

The description set forth herein in connection with the appended drawings describes example configurations and is not intended to represent all examples that may be implemented or within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication at a User Equipment (UE), comprising:

determining that the UE enters an inactive period during which the UE is expected to not transmit or receive data;

determining to transition from a connected state to a dormant state based at least in part on determining that the UE entered the inactive period;

transmitting a connection suspension request to a network entity via an uplink Dedicated Control Channel (DCCH) for transitioning the UE from the connected state to the dormant state based at least in part on the determining to transition from the connected state, wherein the dormant state maintains synchronization of an established radio resource control connection and is associated with storage of a UE security context and UE connection parameters, and wherein the connection suspension request includes a request for storing one or both of the UE security context or the UE connection parameters; and

a response to the connection suspension request is received from the network entity via a downlink DCCH, the response to the connection suspension request indicating whether the UE is to transition to the dormant state.

2. The method of claim 1, further comprising:

A determination is made whether to transition to the dormant state based at least in part on the received response to the connection suspension request.

3. The method of claim 1, further comprising:

transition from the connected state to the dormant state is based at least in part on the response to the connection suspension request, wherein the response includes an acknowledgement of the connection suspension request.

4. The method of claim 1, further comprising:

the connection state is maintained based at least in part on the response to the connection suspension request, wherein the response includes a rejection of the connection suspension request.

5. The method of claim 1, further comprising:

transition to an idle state is based at least in part on the response to the connection suspension request, wherein the response includes a rejection of the connection suspension request.

6. The method of claim 1, further comprising:

and causing a modem of the UE to enter the dormant state, wherein the response includes an acknowledgement of the connection suspension request.

7. The method of claim 1, further comprising:

transitioning from the connected state to the dormant state based at least in part on the response to the connection suspension request;

Determining to resume communication with the network entity while in the dormant state; and

a connection resume request is sent to the network entity for transitioning from the dormant state to the connected state.

8. The method of claim 7, further comprising:

receiving a response to the connection restoration request from the network entity, the response to the connection restoration request acknowledging the connection restoration request; and

transition from the dormant state to the connected state is based at least in part on the acknowledgement.

9. The method of claim 1, wherein the connection suspension request, or the response to the connection suspension request, or a connection resume request, or a response to the connection resume request, is sent using a Radio Resource Control (RRC) message, or layer 1 signaling, or a combination thereof.

10. The method of claim 9, wherein the layer 1 signaling comprises: uplink control information within a Physical Uplink Control Channel (PUCCH), or the uplink control information within a Physical Uplink Shared Channel (PUSCH), or an uplink Medium Access Control (MAC) Control Element (CE), or a combination thereof.

11. The method of claim 1, wherein the connection suspension request includes an indication of: a duration for the dormant state, or a priority for the transition to the dormant state, or a combination thereof.

12. The method according to claim 1, wherein:

the connection suspension request includes an uplink DCCH message; and

the response to the connection suspension request includes a downlink DCCH message.

13. A method for wireless communication at a network entity, comprising:

receiving a connection suspension request from a User Equipment (UE) via an uplink Dedicated Control Channel (DCCH), the connection suspension request for transitioning the UE from a connected state to a dormant state, wherein the dormant state maintains synchronization of an established radio resource control connection and is associated with storage of a UE security context and UE connection parameters, and wherein the connection suspension request includes a request for storing one or both of the UE security context or the UE connection parameters;

determining whether to allow the UE to transition to the dormant state based at least in part on the connection suspension request; and

A response to the connection suspension request is sent to the UE via a downlink DCCH, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based at least in part on the determination of whether to allow the UE to transition to the dormant state.

14. The method of claim 13, further comprising:

determining to allow the UE to transition to the dormant state, wherein the response to the connection suspension request includes the acknowledgement of the connection suspension request.

15. The method of claim 14, further comprising:

receiving a connection resume request from the UE for transitioning the UE from the dormant state to the connected state; and

and sending a response to the connection recovery request to the UE, and confirming the connection recovery request according to the response to the connection recovery request.

16. The method of claim 13, further comprising:

determining to reject the UE to transition to the dormant state, wherein the response to the connection suspension request includes the rejection of the connection suspension request.

17. The method of claim 13, further comprising:

A command for the UE to transition to an idle state is sent based at least in part on receiving the connection suspension request.

18. The method of claim 13, further comprising:

one or more communication parameter values for the UE are stored by the network entity based at least in part on receiving the connection suspension request.

19. The method of claim 18, wherein the connection suspension request comprises a request to store at least the UE security context, and wherein storing the one or more communication parameter values comprises:

and storing the UE security context.

20. The method of claim 13, wherein the connection suspension request, or the response to the connection suspension request, or a connection resume request, or a response to the connection resume request, is sent using a Radio Resource Control (RRC) message, or layer 1 signaling, or a combination thereof.

21. The method of claim 20, wherein the layer 1 signaling comprises: uplink control information within a Physical Uplink Control Channel (PUCCH), or the uplink control information within a Physical Uplink Shared Channel (PUSCH), or an uplink Medium Access Control (MAC) Control Element (CE), or a combination thereof.

22. The method of claim 13, further comprising:

identifying, based at least in part on the connection suspension request, an indication of: the UE will be in the dormant state for a duration of time, or a priority associated with the transition to the dormant state, or a combination thereof.

23. The method according to claim 13, wherein:

the connection suspension request includes an uplink DCCH message; and

24. An apparatus for wireless communication at a User Equipment (UE), comprising:

means for determining that the UE enters an inactive period during which the UE is expected to not transmit or receive data;

means for transmitting a connection suspension request to a network entity via an uplink Dedicated Control Channel (DCCH) based at least in part on the determination to transition from the connected state to the dormant state, the connection suspension request for transitioning the UE from the connected state to the dormant state, wherein the dormant state maintains synchronization of an established radio resource control connection and is associated with storage of a UE security context and UE connection parameters, and wherein the connection suspension request includes a request for storing one or both of the UE security context or the UE connection parameters; and

Means for receiving a response to the connection suspension request from the network entity via a downlink DCCH, the response to the connection suspension request indicating whether the UE is to transition to the dormant state.

25. The apparatus of claim 24, further comprising:

determining whether to transition to the sleep state based at least in part on the received response to the connection suspension request.

26. The apparatus of claim 24, further comprising:

the apparatus may further include means for transitioning from the connected state to the dormant state based at least in part on the response to the connection suspension request, wherein the response includes an acknowledgement of the connection suspension request.

27. The apparatus of claim 24, further comprising:

means for maintaining the connection state based at least in part on the response to the connection suspension request, wherein the response includes a rejection of the connection suspension request.

28. The apparatus of claim 24, further comprising:

the apparatus may further include means for transitioning to an idle state based at least in part on the response to the connection suspension request, wherein the response includes a rejection of the connection suspension request.

29. The apparatus of claim 24, further comprising:

and means for causing a modem of the UE to enter the dormant state, wherein the response includes an acknowledgement of the connection suspension request.

30. The apparatus of claim 24, further comprising:

means for transitioning from the connected state to the dormant state based at least in part on the response to the connection suspension request;

determining that communication with the network entity is to be resumed while in the dormant state; and

and means for sending a connection resume request to the network entity for transitioning from the dormant state to the connected state.

31. The apparatus of claim 30, further comprising:

means for receiving a response to the connection restoration request from the network entity, the response to the connection restoration request acknowledging the connection restoration request; and

the apparatus also includes means for transitioning from the dormant state to the connected state based at least in part on the acknowledgement.

32. The apparatus of claim 24, wherein the connection suspension request, or the response to the connection suspension request, or a connection resume request, or a response to the connection resume request, is sent using a Radio Resource Control (RRC) message, or layer 1 signaling, or a combination thereof.

33. An apparatus for wireless communication at a network entity, comprising:

means for receiving a connection suspension request from a User Equipment (UE) via an uplink Dedicated Control Channel (DCCH), the connection suspension request for transitioning the UE from a connected state to a dormant state, wherein the dormant state maintains synchronization of an established radio resource control connection and is associated with storage of a UE security context and UE connection parameters, and wherein the connection suspension request includes a request for storing one or both of the UE security context or the UE connection parameters;

means for sending a response to the connection suspension request to the UE via a downlink DCCH, the response including an acknowledgement of the connection suspension request or a rejection of the connection suspension request based at least in part on the determining whether to allow the UE to transition to the dormant state.

34. The apparatus of claim 33, further comprising:

the apparatus may further include means for determining to allow the UE to transition to the dormant state, wherein the response to the connection suspension request includes the acknowledgement of the connection suspension request.

35. The apparatus of claim 34, further comprising:

means for receiving a connection resume request from the UE for transitioning the UE from the dormant state to the connected state; and

and means for sending a response to the connection restoration request to the UE, the response to the connection restoration request acknowledging the connection restoration request.

36. The apparatus of claim 33, further comprising:

the apparatus may further include means for determining to reject the UE from transitioning to the dormant state, wherein the response to the connection suspension request includes the rejection of the connection suspension request.

37. The apparatus of claim 33, further comprising:

means for sending a command for the UE to transition to an idle state based at least in part on receiving the connection suspension request.

38. The apparatus of claim 33, further comprising:

means for storing one or more communication parameter values for the UE based at least in part on receiving the connection suspension request.

39. The apparatus of claim 33, wherein the connection suspension request, or the response to the connection suspension request, or a connection resume request, or a response to the connection resume request, is sent using a Radio Resource Control (RRC) message, or layer 1 signaling, or a combination thereof.

40. An apparatus for wireless communication at a User Equipment (UE), comprising:

a processor;

a memory in electronic communication with the processor; and

instructions stored in the memory and executable by the processor to cause the apparatus to:

41. The apparatus of claim 40, wherein the instructions are further executable by the processor to cause the apparatus to:

42. The apparatus of claim 40, wherein the instructions are further executable by the processor to cause the apparatus to:

43. The apparatus of claim 40, wherein the instructions are further executable by the processor to cause the apparatus to:

44. The apparatus of claim 40, wherein the instructions are further executable by the processor to cause the apparatus to:

45. The apparatus of claim 40, wherein the instructions are further executable by the processor to cause the apparatus to:

46. The apparatus of claim 40, wherein the instructions are further executable by the processor to cause the apparatus to:

47. The apparatus of claim 46, wherein the instructions are further executable by the processor to cause the apparatus to:

48. The apparatus of claim 40, wherein the connection suspension request, or the response to the connection suspension request, or a connection resume request, or a response to the connection resume request, is sent using a Radio Resource Control (RRC) message, or layer 1 signaling, or a combination thereof.

49. The apparatus of claim 48, wherein the layer 1 signaling comprises: uplink control information within a Physical Uplink Control Channel (PUCCH), or the uplink control information within a Physical Uplink Shared Channel (PUSCH), or an uplink Medium Access Control (MAC) Control Element (CE), or a combination thereof.

50. The apparatus of claim 40, wherein the connection suspension request includes an indication of: a duration for the dormant state, or a priority for the transition to the dormant state, or a combination thereof.

51. The apparatus of claim 40, wherein:

the connection suspension request includes an uplink DCCH message; and

52. An apparatus for wireless communication at a network entity, comprising:

A processor;

a memory in electronic communication with the processor; and

53. The apparatus of claim 52, wherein the instructions are further executable by the processor to cause the apparatus to:

54. The apparatus of claim 53, wherein the instructions are further executable by the processor to cause the apparatus to:

55. The apparatus of claim 52, wherein the instructions are further executable by the processor to cause the apparatus to:

56. The apparatus of claim 52, wherein the instructions are further executable by the processor to cause the apparatus to:

57. The apparatus of claim 52, wherein the instructions are further executable by the processor to cause the apparatus to:

one or more communication parameter values for the UE are stored based at least in part on receiving the connection suspension request.

58. The apparatus of claim 57, wherein the connection suspension request comprises a request to store at least the UE security context, and wherein the instructions are further executable by the processor to cause the apparatus to:

and storing the UE security context.

59. The apparatus of claim 52, wherein the connection suspension request, or the response to the connection suspension request, or a connection resume request, or a response to the connection resume request, is sent using a Radio Resource Control (RRC) message, or layer 1 signaling, or a combination thereof.

60. The apparatus of claim 59, wherein the layer 1 signaling comprises: uplink control information within a Physical Uplink Control Channel (PUCCH), or the uplink control information within a Physical Uplink Shared Channel (PUSCH), or an uplink Medium Access Control (MAC) Control Element (CE), or a combination thereof.

61. The apparatus of claim 52, wherein the instructions are further executable by the processor to cause the apparatus to:

62. The apparatus of claim 52, wherein,

the connection suspension request includes an uplink DCCH message; and

63. A non-transitory computer-readable medium storing code for wireless communication at a User Equipment (UE), the code comprising instructions executable by a processor to:

64. A non-transitory computer-readable medium storing code for wireless communication at a network entity, the code comprising instructions executable by a processor to: