WO2017200541A1

WO2017200541A1 - Improved signaling for battery efficient state transition in pch states

Info

Publication number: WO2017200541A1
Application number: PCT/US2016/033152
Authority: WO
Inventors: Roy S. BIRDI; Kulwinder SAINI; Vijayant Kumar
Original assignee: Intel IP Corporation
Priority date: 2016-05-18
Filing date: 2016-05-18
Publication date: 2017-11-23
Also published as: CN109076623A

Abstract

A user equipment (UE) may include a memory device and a processing device operatively coupled to the memory device. The processing device may encode a CELL UPDATE message indicating an attempt to release a signaling connection and decode a confirmation message from the network. The processing device may cause the UE to transition from a first connection state to a second connection state in response to receiving confirmation message. The second connection state may be associated with a second power consumption level which is less than a first power consumption level associated with the first connection state.

Description

IMPROVED SIGNALING FOR BATTERY EFFICIENT STATE

TRANSITION IN PCH STATES

BACKGROUND

[0001] The disclosure relates to the field of wireless communications, including control of network connections by user equipment.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Various embodiments of the present disclosure will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the disclosure.

[0003] FIG. 1 is a block diagram illustrating components of an electronic device implementing aspects of the disclosure, according to an embodiment.

[0004] FIG. 2 is a block diagram illustrating components of a network, according to an embodiment.

[0005] FIG. 3 illustrates a state diagram of connections states of user equipment, according to an embodiment

[0006] FIG. 4 illustrates a flowchart of an example method of performing a cell update procedure, according to an embodiment.

[0007] FIG. 5 illustrates a flowchart of an example method of performing a cell update procedure, according to an embodiment.

[0008] FIG. 6 illustrates a communication timing diagram that illustrates an example of application specific congestion control for data communication, according to an embodiment.

DESCRIPTION OF EMBODIMENTS

[0009] User equipment (UE) accessing a network over universal mobile

telecommunication system (UMTS) technologies may operate in one of several power states. The power states represent a tradeoff between the speed at which a UE can transmit and receive data over a network, the power consumed by the UE, the utilization of network resources by the UE, and the allocation of network resources to the UE by the network. The UE may switch between various power states by sending a request to the network to place the UE in a different power state. In addition, the network may place the UE into a certain power state without a request from the UE in order to reduce utilization of network resources based on the activity of the UE.

[0010] In a UMTS system, a UE may operate in an idle mode or in a connected mode. In a connected mode, the network may maintain a logical connection with the UE. For example, the network may establish and maintain a radio resource control (RRC) connection with a UE while the UE is in a connected state. In an idle mode, the UE may monitor a paging line and the network may not maintain a logical connection to the UE. A UE in a connected mode may be in a URA-PCH state, a CELL-PCH state, a CELL-DCH state, or a CELL-FACH state. The connection state for a UE may indicate whether the UE is in an idle or connected mode, and if in connected mode, what RRC state the UE is in.

[0011] In idle mode, the UE does not have a transmission connection to the network. The lack of logical connection minimizes the use and allocation of network resources by the network and power consumption by the UE. A UE in idle mode may perform processes of public land mobile network (PLMN) selection, cell selection, cell reselection, location area updating, routing area updating, receiving pages, or receiving system information broadcasts (SIB). The UE may listen to a page indicator channel (PICH) at predetermined times to reduce the power consumption. The predetermined time may be set by the network and referred to as a discontinuous reception (DRX) cycle. A separate DRX cycle may be set for packet switched (PS) communications and circuit switched (CS) communications. The DRX cycle set for a UE in idle mode may be a longer time interval than a DRX cycle for the UE in connected mode.

[0012] The states for a UE in connected mode may include URA-PCH, CELL-PCH,

CELL-DCH, and CELL-FACH. In the CELL-DCH state, the UE has a dedicated transport channel allocated by the network. In the CELL-DCH state, the UE may also utilize shared uplink and downlink channels that are available in combination with a dedicated transport channel. A network may transition a UE into CELL-DCH state in response to an indication that the UE has a large amount of data to transmit or receive. A UE in the CELL-DCH state may consume a large amount of power to maintain a dedicated connection to the network. In addition the network may dedicate a large number of resources to the UE when the UE is transitioned to the CELL-DCH state. Thus, the network or UE may cause the UE to transition to another state when an uplink or downlink communication is completed.

[0013] In the CELL-FACH state, the UE may not have a dedicated physical channel as it does in the CELL-DCH state. The UE may continuously monitor a forward access channel

(FACH) for downlink communications. The network may also allocate a default common or shared transport channel for uplink communications. For example, the UE may transmit uplink communications on a random access channel (RACH). The network may track the UE on the cell level based on where the UE made a last cell update. Continuous monitoring of an

FACH downlink may increase the battery usage for the UE. In addition, the network may have allocated some resources to the UE to establish RACH and FACH communication.

Thus, the network or UE may cause the UE to transition to another state if the UE is not utilizing the connection.

[0014] In the CELL-PCH state, the UE may not have a dedicated physical channel. The UE or the network may select a paging channel (PCH) for the UE. The UE may then receive pages on the PCH using DRX by monitoring an associated page indicator channel (PICH). In the CELL-PCH state, the UE may not transmit uplink communications to the network. The network may maintain an indication of the UE's location based on the last cell update performed by the UE. The URA-PCH state may have the same characteristics as the CELL- PCH state except that the network may maintain an indication of the UE's location based on the last user registration area (URA) update performed by the UE. A UE may be in a URA- PCH state instead of a CELL-PCH state to reduce the number of cell updates performed by the UE. For example, a moving UE may perform fewer URA updates in a URA-PCH state instead of performing many cell updates within a URA if the UE was in a CELL-PCH state.

[0015] In a CELL-PCH or URA-PCH state (referred to collectively as a PCH state), the UE may consume more power than in an idle state. Thus, the UE or the network may cause the UE to transition from a PCH state to the idle state if the UE has not utilized the paging channel or transitioned to a CELL-DCH or CELL-FACH state to transmit uplink data within a threshold amount of time.

[0016] The process of transitioning to a lower power state based on a request from the UE may be performed by first establishing a transmission connection with the network. The UE may initiate a process of establishing a transmission connection with the network by sending a CELL UPDATE message to the network. CELL UPDATE messages may be sent to the network for a variety of reasons. For example, a UE may generate a CELL UPDATE message to change states, to responds to pages, to report errors, to update the location of the UE, or for other reasons. In order to inform the network of the purpose of a CELL UPDATE message, the UE may send the message with a "cause" indicating the purpose. For example, in some embodiments causes may include "Uplink data transmission," "Paging response," "Radio link failure," "MBMS ptp RB request," "Re-entering service area," "RLC unrecoverable error," "Cell reselection," "Periodic cell update," "MBMS reception," or the like.

[0017] In order to establish a connection to send data to the network, a UE may generate a CELL UPDATE message that includes a cause of "Uplink Data Transmission." The network may then allocate resources to the UE so that the UE may transmit the data. After the transmission connection is established, the UE may transmit a signaling connection release indication (SCRI). The SCRI informs the network that the UE is seeking to release the signaling connection. The network may then release the signaling connection for the UE and transition the UE into a lower power state. For example, the UE may transition into an idle state.

[0018] This process of establishing a transmission connection to request to release a signaling connection has several disadvantages. For example, in order to send the SCRI, the UE and network must establish a transmission connection. Establishing the connection requires several communications between the UE and the network that may cost battery life to the UE and utilize network resources. Establishing the transmission connection also increases the network signaling load. Furthermore, after the connection is established, the network must allocate network resources to maintaining the connection and communicate with the UE. In addition, sending the SCRI through the network connection, acknowledging the SCRI, and confirming whether the UE is to transition into a lower power state causes the exchange of additional signaling messages.

[0019] In order to improve the process of transitioning to lower power states, a UE may request the transition without establishing a signaling connection with the network. In some embodiments, a UE may provide a cause in a CELL UPDATE message that indicates to the network that the CELL UPDATE message was sent to transition to a different power state.

For example, the UE may set the cause to "UE-Requested PS Data session end." The network may receive the CELL UPDATE message with a "UE-Requested PS Data Session End" cause and transition the UE to a lower power state without additional communications to establish a signaling connection for the UE. In some embodiments, a message may convey the same information using different language. For example, instead of "UE-Requested PS Data

Session End," a UE may send a cause with different language that is understood by the network as an indication that the UE is attempting to release a signaling connection.

[0020] In response to receiving a CELL UPDATE message with a "UE-Requested PS

Data Session End" cause, the network may determine whether to transition the UE into a lower power state. In some embodiments, the network may transition the UE into an idle state in response to such a message. However, in some embodiments, the network may make a determination not to transition the UE into a lower power state based on the available network resources and network utilization by the UE. For example, a network may have a policy that prevents a UE from transitioning from a connected state to and idle state within a threshold amount of time. Thus, if a UE transitions to an idle state and back to a connected state, then the network may not allow the UE to transition to an idle state again until a predetermined amount of time has passed.

[0021] The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of the disclosure. However, various aspects of the disclosed embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the present disclosure with unnecessary detail.

[0022] As used herein, the term "circuitry" may refer to, be part of, or include

an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor

(shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be

implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[0023] Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. Figure 1 illustrates, for one embodiment, example components of a UE device 100. In some embodiments, the UE device 100 may include application circuitry 102, baseband circuitry 104, Radio Frequency (RF) circuitry 106, front-end module (FEM) circuitry 108 and one or more antennas 110, coupled together at least as shown.

[0024] The application circuitry 102 may include one or more application processors.

For example, the application circuitry 102 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[0025] The baseband circuitry 104 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 104 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 106 and to generate baseband signals for a transmit signal path of the RF circuitry 106. Baseband processing circuity 104 may interface with the application circuitry 102 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 106. For example, in some embodiments, the baseband circuitry 104 may include a second generation (2G) baseband processor 104a, third generation (3G) baseband processor 104b, fourth generation (4G) baseband processor 104c, and/or other baseband processor(s) 104d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 104 (e.g., one or more of baseband processors 104a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 106. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 104 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 104 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of

modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0026] In some embodiments, the baseband circuitry 104 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control

(MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 104e of the baseband circuitry 104 may be configured to run elements of the protocol stack for signaling of the

PHY, MAC, RLC, PDCP, NAS and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 104f. The audio

DSP(s) 104f may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 104 and the application circuitry 102 may be implemented together such as, for example, on a system on a chip (SoC). [0027] In some embodiments, the baseband circuitry 104 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 104 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 104 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0028] RF circuitry 106 may enable communication with wireless networks

using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 106 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 106 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 108 and provide baseband signals to the baseband circuitry 104. RF circuitry 106 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 104 and provide RF output signals to the FEM circuitry 108 for transmission.

[0029] In some embodiments, the RF circuitry 106 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 106 may include mixer circuitry 106a, amplifier circuitry 106b and filter circuitry 106c. The transmit signal path of the RF circuitry 106 may include filter circuitry 106c and mixer circuitry 106a. RF circuitry 106 may also include synthesizer circuitry 106d for synthesizing a frequency for use by the mixer circuitry 106a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 106a of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 108 based on the synthesized frequency provided by synthesizer circuitry 106d. The amplifier circuitry 106b may be configured to amplify the down-converted signals and the filter circuitry 106c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down- converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 104 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 106a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect. [0030] In some embodiments, the mixer circuitry 106a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 106d to generate RF output signals for the FEM circuitry 108. The baseband signals may be provided by the baseband circuitry 104 and may be filtered by filter circuitry 106c. The filter circuitry 106c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0031] In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a may be arranged for direct

downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 106a of the receive signal path and the mixer circuitry 106a of the transmit signal path may be configured for super-heterodyne operation.

[0032] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 106 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 104 may include a digital baseband interface to communicate with the RF circuitry 106.

[0033] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0034] In some embodiments, the synthesizer circuitry 106d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 106d may be a delta- sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0035] The synthesizer circuitry 106d may be configured to synthesize an output frequency for use by the mixer circuitry 106a of the RF circuitry 106 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 106d may be a fractional N/N+l synthesizer.

[0036] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 104 or the applications processor 102 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 102.

[0037] Synthesizer circuitry 106d of the RF circuitry 106 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0038] In some embodiments, synthesizer circuitry 106d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (f_Lo)- In some embodiments, the RF circuitry 106 may include an IQ/polar converter.

[0039] FEM circuitry 108 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 110, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 106 for further processing. FEM circuitry 108 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 106 for transmission by one or more of the one or more antennas 110.

[0040] In some embodiments, the FEM circuitry 108 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 106). The transmit signal path of the FEM circuitry 108 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 106), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 110).

[0041] In some embodiments, the UE device 100 may include additional elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

[0042] Figure 2 illustrates an example network environment 200, according to an embodiment. The network environment 200 may include a radio network controller (RNC) 210, a NodeB 220, and a plurality of user equipment (UE) units 230. In other network environments, other network components may perform operations similar to those discussed with reference to RNC 210 in Figure 2. In some embodiments, network environment 200 includes other elements. For example, the RNC 210 may communicate with a network operator, such as a core network element in a UMTS system, or other systems to provide additional control or services to UEs 230.

[0043] The RNC 210 may determine connection states for the UEs 230 connected to the RNC through a NodeB 220. In some embodiments, the RNC 210 may communicate with UEs 230 through wireless uplink and downlink transmissions through NodeB 220. The RNC 210 may communicate with NodeB 220 through one or more hardwired or wireless communications .

[0044] The NodeB 220 may include RF circuitry 217 to enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.

The RF circuitry 217 may transmit and receive RF transmissions. The RF circuitry 217 may include similar components to those discussed with reference to RF circuitry 106 in Figure 1.

For example, the RF circuitry may include mixer circuitry, amplifier circuitry, filter circuitry, or synthesize circuitry. The NodeB may also include a front end module and antennae for transmitting and receiving RF signals over a non-solid medium. For example, for

transmitting and receiving signals to and from one or more UEs 230.

[0045] The RNC 210 establishes network communications with the UEs 230. For example, the communications may be established based on a UMTS network standard. The

RNC 210 may enable UE 230 to connect to packet switched network components or circuit switched network components. As shown in Figure 2, the RNC 210 may include a network monitor 212, a processing device 213, a memory device 215, and a UE state control system

216. The RNC 210 may receive access requests from UE 230, periodically provide system information over a broadcast, and maintain connection state information between the RNC 210 and various UEs 230. In some embodiments, the RNC 210 may include application circuitry to execute one or more applications operating on the RNC 210, baseband circuitry to process baseband signals received from a receive signal path of RF circuitry 217 and to generate baseband signals for a transmit signal path of RF circuitry 217.

[0046] In some embodiments, the RNC 210 may be may include components of the NodeB 220. For example, the RNC 210 may include one or more antennas for transmitting and receiving RF transmissions and a front end module circuitry having a receive signal path to operate on RF signals received from one or more antennas. The front end module circuitry may also include a transmit signal path to amplify signals for transmission provided by the RF circuitry for transmission by one or more of the one or more antennas. In some embodiments, a RNC 210 may provide communications to a NodeB having RF circuitry and a front end module to send and receive transmissions from UE 230. For example, as shown in Figure 2, the RNC 210 may include processing devices 213 and memory devices 215. In some embodiments, the RNC 210 may also include additional or alternative RF circuitry to the RF circuitry 217 included in NodeB 220. The processing devices 213 may include one or more central processing units and may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP, NAS and/or RRC layers. The processing devices 213 may execute one or more applications on the RNC 210, perform operations as part of baseband circuitry of the RNC 210 as described with reference to Figure 1, or perform other operations. The processing devices 213 may be coupled with and/or may include memory device 215, and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system. The memory device 215 may also store data for use by applications such as parameters used by UE state control system 216, network monitor 212, or parameters provided to UE 230.

[0047] In some embodiments, the network monitor 212 may monitor a variety of network performance parameters. The parameters may be based on access to the network by user equipment 230, the NodeB 220, or overall network performance. Some example performance statistics may include the percentage of random access channel resources occupied by access attempts from UEs 230, the ratio of access attempts that are unserved based on collisions, packet queuing delays, receiver noise ratios, or other performance measurements that may indicate the level of congestion and performance of the network. The network monitor 212 may provide statistics to other components of the RNC 210 and/or to other network elements. For example, the network monitor 212 may provide information indicative of the network's operation to the UE state control system 216.

[0048] The UE state control system 216 may implement processes to monitor the state of UEs 230 connected to the network. For example, the UE state control system 216 may track the location of UEs 230, the connection state of UEs 230, and monitor communications by UEs 220. The UE state control system 216 may determine whether to transition a UE 230 into a different connection state based on data regarding the UE and/or data provided by the network monitor 212. The UE state control system 216 may make such a determination periodically, in response to a CELL UPDATE message received from a UE 230, or in response to other stimulus. For example, if a CELL UPDATE message from a UE 230 includes a cause indication of "UE-Requested PS Data Session End," then the UE state control system 216 may make a determination whether to transition the UE to a different connection state.

[0049] The UE 230 may include circuitry as described with reference to Figure 1 above. The UE 230 may execute various application that request network services to communicate with a network. In addition, the UE 230 may provide information to the RNC 210 including the identity and capability of the UE 230. In some embodiments, one or more UEs 230 may be capable of performing operations to transition to a different connection state as describe herein.

[0050] Figure 3 depicts a state diagram 300 illustrating various connection states of a UE operating according to UMTS protocol. As discussed above, the UE may operate in idle mode 310 or connected mode 320. The connected mode may include four states: URA-PCH

330, CELL-PCH 340, CELL-FACH 360, and CELL-DCH 350. A UE may transition between the states according to the arrows shown in Figure 3. In some systems, a UE in a

PCH state 330, 340 may transition directly to idle mode 310 after receiving an information element from the network indicating that the UE is to transition to the idle mode. For example, in the event of congestion, the network may transition one or more UEs from a PCH state to an idle state. The UE may also request to transition to idle mode 310 in response to one or more conditions. For example, the UE may request to transition to idle mode if there is no uplink or downlink transmission expected or there hasn't been a transmission in a set period of time. In some embodiments, the UE may request a transition to idle mode if the

DRX cycle length used by the network in idle mode is longer than the cycle length of the

DRX cycle length for a UE in a PCH state. Thus, the UE may request a transition into a state that utilizes less power due to a longer DRX cycle length. In some embodiments, the UE may request to transition to a state other than the idle mode. For example, the UE may determine that the DRX cycle length in a URA-PCH state is longer than the DRX cycle length in a CELL-PCH state. In such cases, the UE may request to transition to a URA-PCH state instead of to an idle state. In some embodiments, the UE may send a request to transition to or from other states.

[0051] In order to transition to an idle mode 310 from a PCH state 330, 340, the UE may send a CELL UPDATE message to the network. In the CELL UPDATE message, the UE may include an information element indicating that the cause is "UE-Requested PS Data Session End." The network may determine based on the message to transition the UE into an idle mode. Because the UE indicates that it is attempting to end the RRC connection in the CELL UPDATE message, the network may transition the UE to an idle state 320 without establishing a dedicated or shared communication channel for the UE. Based on a CELL UPDATE CONFIRM message from the network, the UE may then release the RRC connection to transition into idle mode.

[0052] Figure 4 depicts a flowchart of an example method performed by a UE to transition to a battery efficient state. Beginning in block 410, the UE determines that it is to transition into a battery efficient state. For example, the UE may determine that it is to transition from a PCH state to an idle state as discussed with reference to Figure 3. The determination to transition to a battery efficient state may be made by a hardware or software component of the UE. For example, baseband circuitry or application circuitry as discussed with reference to Figure 1 may make the determination to transition to a battery efficient state. The UE may make the determination based on the current connection state of the UE, the DRX cycle length of the UE in a current state and in other states, the uplink or downlink transmissions by the UE over a period of time, expected uplink or downlink transmissions by the UE, network statistics, or other information that indicates transitioning to an idle state would reduce the power usage of the UE or the network utilization of the UE. In some embodiments, the UE may determine that it is to transition into a battery efficient state after a threshold amount of time has passed since the last uplink or downlink transmission. In some embodiments, the threshold amount of time may be different for uplink and downlink transmissions.

[0053] Moving on to block 420, the UE may generate a CELL UPDATE message with a cause indication of "UE-Requested PS Data Session End." The CELL UPDATE message may include other information as well. In some embodiments, the UE may provide a cause having language other than "UE-Requested PS Data Session End" to convey the same or similar information. For example, the cause may be listed as any indication that the network interprets as requesting a release of an RRC connection. Thus, the UE may generate a CELL UDPATE with any cause indicating an attempt to release a signaling connection. In some embodiments, instead of a CELL UPDATE message, the UE may send a URA UPDATE message or another type of message with the cause set to "UE-Requested PS Data Session End." In some embodiments, the CELL UPDATE message may be a RRC message. Then, generating the CELL UPDATE message may comprise encoding the CELL UPDATE message by baseband circuitry of the UE.

[0054] In block 430, the UE transmits the CELL UPDATE message to the network. In order to transmit the message, the UE may send a message over a RACH or may transition into a CELL-FACH state in order to send the message. For example, the UE may transmit the CELL UPDATE message in a time division allocated to the UE in CELL-FACH instead of over a random connection. However, the UE may not establish a dedicated channel with the network when sending the CELL UPDATE message.

[0055] In block 440, the UE receives a CELL UPDATE CONFIRM message from the network with an indication to transition to the battery efficient state. The UE may receive the CELL UPDATE CONFIRM message while in a CELL-FACH state or while in a CELL-PCH state. For example, the network may send the message to the UE over a FACH or send the message over a paging channel. The CELL UPDATE CONFIRM message may include an information element that indicates a state for the UE. For example, the CELL UPDATE CONFIRM message may include an information element that indicates to the UE to transition into an idle mode. In some embodiments, the CELL UPDATE CONFIRM message may be a RRC message. Then, receiving the CELL UPDATE CONFIRM message may comprise decoding the CELL UPDATE CONFIRM message by baseband circuitry of the UE. In response to the CELL UPDATE CONFIRM message, in block 450, the UE may transition to the battery efficient state indicated by the message. For example, the UE may transition from a PCH or CELL-FACH state to an idle state if an idle state is indicated in an information element of the CELL UPDATE CONFIRM message.

[0056] Figure 5 depicts an example method 500 performed by a network to transition a

UE to a battery efficient state. Beginning in block 510, the network receives a CELL

UPDATE message from a UE with a cause indication of "UE-Requested PS Data Session

End." In some embodiments, the network may receive the message over a wireless medium at an antenna of a NodeB. A RNC or other network element may then receive the CELL

UPDATE message from the NodeB or another intermediary component. In some embodiments, the CELL UPDATE message received by the network is an RRC message. Then, the RNC or another network element may decode the CELL UPDATE message in block 510 of method 500.

[0057] Moving on to block 520, the network determines to transition the UE to a battery efficient state. For example, an RNC may have a UE state control system that determines a state for the UE. In some embodiments, the network may determine that the UE may transition to another connection state unless there is a reason not to. For example, a network may have a set of policies or rules that indicate available states for a UE. For example, the network may have a rule that prevents a UE from transitioning to an idle state from a PCH state if the UE has transitioned to an idle state previously within a certain period of time. Such a rule may reduce unnecessary traffic on the network due to establishing connections for UEs that are transitioning to and from an idle state frequently. In some embodiments, the network may apply different or additional rules or policies to determine whether to transition the UE to a battery efficient state.

[0058] In block 530, the network generates a CELL UPDATE CONFIRM message with an information element indicating a battery efficient state for the UE. For example, the network may generate a CELL UPDATE CONFIRM message with an information element indicating an idle state for the UE. In some embodiments, an RNC may generate the CELL UPDATE CONFRIM message. In some embodiments another network element generates the CELL UPDATE CONFIRM message. The network may transmit the CELL UPDATE CONFIRM message to the UE through a wireless signal. For example, the network may generate the signal in an RNC and transmit the signal through RF circuitry, front-end circuitry, and an antenna of a NodeB. In some embodiments, the CELL UPDATE

CONFIRM message may be generated or transmit by other components of a network. In some embodiments, the CELL UPDATE CONFIRM message is an RRC message. Then, generating the CELL UPDATE CONFIRM message may comprise encoding the CELL UPDATE CONFIRM message for transmission to the UE.

[0059] If the cause of the CELL UPDATE message was different than "UE-Requested

PS Data Session End," the network may allocate resources to the UE and configure a communication channel to enable the UE to transmit uplink data. For example, in a system that does not have a cause of "UE-Requested PS Data Session End" available for a CELL

UPDATE message the UE may send a CELL UPDATE message with a cause of "UL Data

Transmission." Thus, the network may allocate resources to enable the UE to transmit uplink data. Then the UE may transmit a SCRI with a cause of "UE-Requested PS Data Session End" after the network and UE have allocated resources to establishing a connection for sending uplink data. Thus, if a UE sends a CELL UPDATE message with a cause of "UE- Requested PS Data Session End," and the network recognizes the cause, then the network and UE may reduce time and resources used to end a signaling connection.

[0060] In addition to generating the CELL UPDATE CONFIRM message in block 530, the network may transition the UE to a battery efficient state on the network side in block 540. For example, the network may release network resources reserved for the UE, change a paging schedule for the UE, update a data structure that describes location or logical address information for the UE, and/or the like. In some embodiments, the network may wait for a confirmation message such as an UPLINK RESPONSE message from the UE prior to transitioning the UE to an idle state on the network side of a connection.

[0061] Figure 6 is a communication timing diagram that illustrates an example of communication between a UE and a network to transition to a battery efficient state, according to an embodiment. The timing diagram shows communications between a UE 610 and a network 615. The network may include a NodeB, an RNC, a core network element, or other elements of a UMTS network. In some embodiments, the network may include other backend elements such as an evolved packet core (EPC) that communicates with an RNC or NodeB to perform functions of the network. For example, the EPC may determine network settings or generate responses to communications received from a UE. In some embodiments, the mobility management entity (MME) of an EPC may handle signaling related to the CELL UPDATE procedure. Various communications illustrated in the timing diagram may be processed by one or more elements of the UMTS network. In some embodiments, the network 615 may include other elements associated with other network configurations.

[0062] At a first time 620, the UE 610 is in a CELL-PCH/URA-PCH state. Then at time 625, the UE determines that it is to transition to a battery efficient state. For example, the UE may determine that it has not performed an uplink or downlink transmission within a set period of time and that it would be more efficient to be in an idle mode. Thus, the UE may attempt to transition to the battery efficient state.

[0063] In order to send a message to the network indicating that the UE is requesting to transition to a battery efficient state, the UE may transition to a CELL-FACH state at time

630. From the CELL_FACH state, the UE may transmit a message to the network. For example, the UE may transmit a message to the network over a RACH. At time 630 the UE sends a CELL UPDATE message to the network. The CELL UPDATE message may include a cause of "UE-Requested PS Data Session End." The "UE-Requested PS Data Session End" cause may indicate to the network that the reason for the CELL UPDATE is to request a transition to an idle state from a connected state.

[0064] The network may receive the CELL UPDATE message with the cause set to "UE- Requested PS Data Session End" and make a determination how to respond. The network may either determine to transition the UE to an idle state or determine to leave the UE in a connected state. For example, the network may leave the UE in a connected state if the UE has transitioned from an idle state within a threshold period. If the network determines that it is not going to transition the UE into an idle state it may send no response to the UE, or may send a response indicating that the network is not accepting the UEs request to transition into an idle state. If the network determines to transition the UE into an idle state, then the network may send a CELL UPDATE CONFIRM message to the UE at time 640 with an information element indicating the battery efficient state. For example, the CELL UPDATE CONFIRM message may include a state indicator of an idle state.

[0065] At time 645 the UE may send a response message indicating that it received the CELL UPDATE CONFIRM message from the network and that it will proceed to transition into an idle mode. In some embodiments, the network may also send an acknowledgement of the uplink response message at time 650. The UE may then transition into the idle state at 655. In some embodiments, transitioning to the idle state may comprise changing the monitoring of paging channels or other channels by the UE. The UE may also stop certain operations or update when CELL UPDATE messages or other messages are sent to the network. The network may release the RRC connection with the UE to transition the UE to idle mode. The network may also send a reconfiguration message to the UE. The

reconfiguration message may indicate additional parameters for use by the UE while the UE is in idle mode or another connection state. For example, the parameters may include measurement control information that indicates measurements that the UE is to perform in the new connection state. After the transition, the UE may then perform measurement according to the measurement control information for the new state.

[0066] While the present disclosure describes a number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present disclosure.

[0067] The following examples pertain to further embodiments of the disclosure. [0068] Example 1 is an apparatus of a UE comprising: a memory device; and a processing device, operatively coupled to the memory device, the processing device to:

encode a CELL UPDATE message indicating an attempt to release a signaling connection; decode, from a network, a confirmation message responsive to the CELL UPDATE message; and cause the UE to transition from a first connection state to a second connection state in response to receiving the confirmation message, wherein the second connection state is associated with a second power consumption level which is less than a first power consumption level associated with the first connection state.

[0069] In Example 2, in the apparatus of Example 1 or any of the Examples described herein the processing device is to encode the CELL UPDATE message in response to determining that the first connection state consumes more power than the second connection state.

[0070] In Example 3, in the apparatus of Example 2 or any of the Examples described herein the first connection state is a CELL-PCH or URA-PCH state, wherein the processing device is further to cause UE to monitor a paging channel in the CELL-PCH or URA-PCH state.

[0071] In Example 4, in the apparatus of Example 2 or any of the Examples described herein the second connection state is an idle mode, wherein the UE does not have a logical connection to the network in the idle mode.

[0072] In Example 5, in the apparatus of Example 2 or any of the Examples described herein the processing device determines that the first connection state consumes more power than a second memory state based on a first discontinuous reception period in the first connection state and a second discontinuous reception period in the second connection state.

[0073] In Example 6, in the apparatus of Example 1 or any of the Examples described herein the UE further comprises: radio frequency circuity coupled to the processing device; front-end module circuitry coupled to the radio frequency circuitry; and an antenna coupled to the front-end module circuitry.

[0074] In Example 7, in the apparatus of Example 6 or any of the Examples described herein The UE of Example 6, the processing device is further to: determine that the UE is to transition to an idle connection state; cause the UE to transition to a CELL-FACH connection state; and cause the antenna to transmit the CELL UPDATE message to the network. [0075] In Example 8, in the apparatus of Example 1 or any of the Examples described herein the UE further comprises radio frequency circuitry to transmit the encoded CELL UPDATE message.

[0076] In Example 9, in the apparatus of Example 1 or any of the Examples described herein to cause the UE to transition from a first connection state to a second connection state the processing device does not cause the UE to establish a signaling connection with the network.

[0077] Example 10 is a component of a Radio Network Controller (RNC) comprising: a memory device; a processing device operatively coupled to the memory device, the processing device to: decode a CELL UPDATE message sent by a user equipment (UE) in a connected mode to a network associated with the RNC; determine that the CELL UPDATE message indicates an attempt to release a signaling connection; determine to transition the UE to a battery efficient state; and generate a confirmation message with an information element indicating the battery efficient state.

[0078] In Example 11, in the component of the RNC of Example 10 or any of the Examples described herein the processing device is further to cause the confirmation message to be transmitted to the UE.

[0079] In Example 12, in the component of the RNC of Example 10 or any of the Examples described herein to determine to transition the UE to a battery efficient state, the processing device is to determine that a length of time since a last uplink transmission or CELL UPDATE message from the UE is greater than a threshold length of time.

[0080] In Example 13, in the component of the RNC of Example 10 or any of the Examples described herein the processing device is further to generate a reconfiguration message to configure the UE for the battery efficient state.

[0081] In Example 14, in the component of the RNC of Example 10 or any of the Examples described herein the processing devices does not cause the RNC to establish a connection with the UE in response to the CELL UPDATE message.

[0082] In Example 15, in the component of the RNC of Example 10 or any of the

Examples described herein the processing device is further to: decode a second CELL

UPDATE message from a second UE; determine that the CELL UPDATE message includes a cause indicating an attempt to release a signaling connection; determine not to transition the

UE to an battery efficient state; and generate a confirmation message with an information element indicating a CELL-PCH or a URA-PCH state for the UE. [0083] In Example 16, in the component of the RNC of Example 10 or any of the Examples described herein the component of the RNC is operatively coupled to a NodeB to transmit radio frequency signals to the UE and receive radio frequency signals from the UE.

[0084] Example 17 is one or more computer-readable media having instructions that, when executed, cause a user equipment (UE) to: determine that the UE is to transition to a battery efficient state; encode a CELL UPDATE message having a cause element indicating an attempt to release a signaling connection; and transmit the CELL UPDATE message having the cause element indicating an attempt to release a signaling connection.

[0085] In Example 18, the instructions in Example 17 or any of the other Examples described herein further cause the UE to decode a confirmation message having an indication of the battery efficient state; and transition to the battery efficient state in response to receiving confirmation message.

[0086] In Example 19, the instructions in Example 17 or any of the other Examples described herein to determine that the UE is to transition to the battery efficient state, the instructions further cause the UE to: determine a current connection state for the UE; and determine that the battery efficient state consumes less power than the current connection state.

[0087] In Example 20, the instructions in Example 19 or any of the other Examples described herein to determine that the battery efficient state consumes less power than the first connection state, the instructions further cause the UE to determine that a first discontinuous reception cycle for the current connection state is longer than a second discontinuous reception cycle for the battery efficient state.

[0088] Example 21 is a method comprising: determining that a user equipment (UE) is to transition to a battery efficient state; generating a CELL UPDATE message having a cause element indication an attempt to release a signaling connection; and transmitting the CELL update message having the cause element indicating an attempt to release a signaling connection.

[0089] In Example 22, the method of Example 21 or any of the Examples described herein, further comprises: receiving a confirmation message having an indication of the battery efficient state; and transitioning to the battery efficient state in response to receiving the confirmation message. [0090] In Example 23, in the method of Example 21 or any of the Examples described herein transitioning to battery efficient state does not cause the UE to establish a signaling connection with the network.

[0091] In Example 24, in the method of Example 21 or any of the Examples described herein, determining that the UE is to transition to the battery efficient state comprises:

determining a current connection state for the UE; and determine that the battery efficient state consumes less power than the current connection state.

[0092] In Example 25, in the method of Example 24 or any of the Examples described herein, determining that the battery efficient state consumes less power than the current connection state comprises determining that a first discontinuous reception cycle for the current connection state is longer than a second discontinuous reception cycle for the battery efficient state.

[0093] In Example 26, in the method of Example 24 or any of the Examples described herein, the current connection state is a CELL-PCH or URA-PCH state and wherein the battery efficient state is an idle mode, wherein the UE does not have a logical connection to the network in the idle mode.

[0094] Example 27 is a machine readable medium including code, when executed, to cause a machine to perform the method of any one of Examples 21 to 26 or any of the Examples described herein.

[0095] Example 28 is an apparatus comprising means for performing the method of any one of Examples 21 to 26 or any of the Examples described herein.

[0096] Example 29 is an apparatus comprising a processor configured to perform the method of any one of Examples 21 to 26 or any of the Examples described herein.

[0097] Example 30 is a method comprising: receiving a CELL UPDATE message sent by a user equipment (UE) in a connected mode to a network associated with the RNC;

determining that the CELL UPDATE message indicates an attempt to release a signaling connection; determining to transition the UE to a battery efficient state; and generating a confirmation message with an information element indicating the battery efficient state.

[0098] In Example 31, the method of Example 30 or any of the Examples described herein further comprises causing the confirmation message to be transmitted to the UE.

[0099] In Example 32 in, the method of Example 30 or any of the Examples described herein determining to transition the UE to a battery efficient state comprises determining that a length of time since a last uplink transmission or CELL UPDATE message from the UE is greater than a threshold length of time.

[0100] In Example 33, the method of Example 30 or any of the Examples described herein further comprises generating a reconfiguration message to configure the UE for the battery efficient state.

[0101] In Example 34, the method of Example 30 or any of the Examples described herein further comprises: receiving a second CELL UPDATE message from a second UE; determining that the CELL UPDATE message includes a cause indicating an attempt to release a signaling connection; determining not to transition the UE to an battery efficient state; and generating a confirmation message with an information element indicating a CELL- PCH or a URA-PCH state for the UE.

[0102] Example 35 is an apparatus comprising means to perform a method of Examples 30 to 34 or any of the Examples described herein.

[0103] Example 36 is One or more non-transitory computer-readable media having instructions that, when executed, cause a user equipment (UE) to: determine that the UE is to transition to a battery efficient state; encode a CELL UPDATE message having a cause element indicating an attempt to release a signaling connection; and transmit the CELL

UPDATE message having the cause element indicating an attempt to release a signaling connection.

[0104] In Example 37, the one or more non-transitory computer-readable media of Example 36 or any of the Examples described herein, the instructions further cause the UE to: decode a confirmation message having an indication of the battery efficient state; and transition to the battery efficient state in response to receiving the confirmation message.

[0105] In Example 38, in the one or more non-transitory computer-readable media of Example 36 or any of the Examples described herein, to determine that the UE is to transition to the battery efficient state, the instructions further cause the UE to: determine a current connection state for the UE; and determine that the battery efficient state consumes less power than the current connection state.

[0106] Example 39 is an apparatus of a UE comprising: means for generating a CELL

UPDATE message indicating an attempt to release a signaling connection; means for receiving, from a network, a confirmation message responsive to the CELL UPDATE message; and means for causing the UE to transition from a first connection state to a second connection state in response to receiving the confirmation message, wherein the second connection state is associated with a second power consumption level which is less than a first power consumption level associated with the first connection state.

[0107] In Example 40, the apparatus of the UE of Example 39 or any of the Examples described herein further comprises means for generating the CELL UPDATE message in response to determining that the first connection state consumes more power than the second connection state.

[0108] In Example 41, the apparatus of the UE of Example 39 or 40 or any of the Examples described herein further comprises means for causing the UE to transmit the encoded CELL UPDATE message.

[0109] In the description herein, numerous specific details are set forth, such as examples of specific types of processors and system configurations, specific hardware structures, specific architectural and micro architectural details, specific register configurations, specific instruction types, specific system components, specific measurements/heights, specific processor pipeline stages and operation etc. in order to provide a thorough understanding of the present disclosure. It will be apparent, however, that these specific details need not be employed to practice aspects of the present disclosure. In other instances, well known components or methods, such as specific and alternative processor architectures, specific logic circuits/code for described algorithms, specific firmware code, specific interconnect operation, specific logic configurations, specific manufacturing techniques and materials, specific compiler implementations, specific expression of algorithms in code, specific power down and gating techniques/logic and other specific operational details of computer system have not been described in detail in order to avoid unnecessarily obscuring the present disclosure.

[0110] Instructions used to program logic to perform embodiments of the disclosure can be stored within a memory in the system, such as DRAM, cache, flash memory, or other storage. Furthermore, the instructions can be distributed via a network or by way of other computer readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, Compact Disc, Read-Only Memory (CD- ROMs), and magneto-optical disks, Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the computer-readable medium includes any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0111] A module as used herein refers to any combination of hardware, software, and/or firmware. As an example, a module includes hardware, such as a micro-controller, associated with a non-transitory medium to store code adapted to be executed by the micro-controller. Therefore, reference to a module, in one embodiment, refers to the hardware, which is specifically configured to recognize and/or execute the code to be held on a non-transitory medium. Furthermore, in another embodiment, use of a module refers to the non-transitory medium including the code, which is specifically adapted to be executed by the

microcontroller to perform predetermined operations. And as can be inferred, in yet another embodiment, the term module (in this example) may refer to the combination of the microcontroller and the non-transitory medium. Often module boundaries that are illustrated as separate commonly vary and potentially overlap. For example, a first and a second module may share hardware, software, firmware, or a combination thereof, while potentially retaining some independent hardware, software, or firmware. In one embodiment, use of the term logic includes hardware, such as transistors, registers, or other hardware, such as programmable logic devices.

[0112] Use of the phrase 'configured to,' in one embodiment, refers to arranging, putting together, manufacturing, offering to sell, importing and/or designing an apparatus, hardware, logic, or element to perform a designated or determined task. In this example, an apparatus or element thereof that is not operating is still 'configured to' perform a designated task if it is designed, coupled, and/or interconnected to perform said designated task. As a purely illustrative example, a logic gate may provide a 0 or a 1 during operation. But a logic gate 'configured to' provide an enable signal to a clock does not include every potential logic gate that may provide a 1 or 0. Instead, the logic gate is one coupled in some manner that during operation the 1 or 0 output is to enable the clock. Note once again that use of the term

'configured to' does not require operation, but instead focuses on the latent state of an apparatus, hardware, and/or element, where in the latent state the apparatus, hardware, and/or element is designed to perform a particular task when the apparatus, hardware, and/or element is operating.

[0113] Furthermore, use of the phrases 'to,' 'capable of/to,' and or 'operable to,' in one embodiment, refers to some apparatus, logic, hardware, and/or element designed in such a way to enable use of the apparatus, logic, hardware, and/or element in a specified manner. Note as above that use of to, capable to, or operable to, in one embodiment, refers to the latent state of an apparatus, logic, hardware, and/or element, where the apparatus, logic, hardware, and/or element is not operating but is designed in such a manner to enable use of an apparatus in a specified manner.

[0114] The embodiments of methods, hardware, software, firmware or code set forth above may be implemented via instructions or code stored on a machine-accessible, machine readable, computer accessible, or computer readable medium which are executable by a processing element. A non-transitory machine-accessible/readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine, such as a computer or electronic system. For example, a non-transitory machine- accessible medium includes random-access memory (RAM), such as static RAM (SRAM) or dynamic RAM (DRAM); ROM; magnetic or optical storage medium; flash memory devices; electrical storage devices; optical storage devices; acoustical storage devices; other form of storage devices for holding information received from transitory (propagated) signals (e.g., carrier waves, infrared signals, digital signals); etc., which are to be distinguished from the non-transitory mediums that may receive information there from.

[0115] Instructions used to program logic to perform embodiments of the disclosure may be stored within a memory in the system, such as DRAM, cache, flash memory, or other storage. Furthermore, the instructions can be distributed via a network or by way of other computer readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, Compact Disc, Read-Only Memory (CD- ROMs), and magneto-optical disks, Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the computer-readable medium includes any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0116] Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" on "in some embodiments" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0117] In the foregoing specification, a detailed description has been given with reference to specific exemplary embodiments. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the disclosure as set forth in the appended claims. The specification and drawings are,

accordingly, to be regarded in an illustrative sense rather than a restrictive sense. Furthermore, the foregoing use of embodiment and other exemplarily language does not necessarily refer to the same embodiment or the same example, but may refer to different and distinct

embodiments, as well as potentially the same embodiment.

[0118] Some portions of the detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical

manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers or the like. The blocks described herein can be hardware, software, firmware or a combination thereof.

[0119] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as "defining," "receiving," "determining," "issuing," "linking," "associating," "obtaining," "authenticating," "prohibiting," "executing," "requesting," "communicating," or the like, refer to the actions and processes of a computing system, or similar electronic computing device, that

manipulates and transforms data represented as physical (e.g., electronic) quantities within the computing system's registers and memories into other data similarly represented as physical quantities within the computing system memories or registers or other such information storage, transmission or display devices.

[0120] The words "example" or "exemplary" are used herein to mean serving as an example, instance or illustration. Any aspect or design described herein as "example' or "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the words "example" or "exemplary" is intended to present concepts in a concrete fashion. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless specified otherwise, or clear from context, "X includes A or B" is intended to mean any of the natural inclusive permutations. That is, if X includes A; X includes B; or X includes both A and B, then "X includes A or B" is satisfied under any of the foregoing instances. In addition, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from context to be directed to a singular form. Moreover, use of the term "an embodiment" or "one embodiment" or "an implementation" or "one implementation" throughout is not intended to mean the same embodiment or implementation unless described as such. Also, the terms "first," "second," "third," "fourth," etc. as used herein are meant as labels to distinguish among different elements and may not necessarily have an ordinal meaning according to their numerical designation.

Claims

CLAIMS What is claimed is:

1. An apparatus of a user equipment (UE) comprising:

a memory device; and

a processing device, operatively coupled to the memory device, the processing device to: encode a CELL UPDATE message indicating an attempt to release a signaling connection;

decode, from a network, a confirmation message responsive to the CELL

UPDATE message; and

cause the UE to transition from a first connection state to a second connection state in response to receiving the confirmation message, wherein the second connection state is associated with a second power consumption level which is less than a first power consumption level associated with the first connection state, and wherein the first connection state is a radio resource control (RRC) state.

2. The apparatus of claim 1, wherein the processing device is to encode the CELL UPDATE message in response to determining that the first connection state consumes more power than the second connection state.

3. The apparatus of claim 1 or 2, wherein the first connection state is a CELL-PCH or URA- PCH state, wherein the processing device is further to cause UE to monitor a paging channel in the CELL-PCH or URA-PCH state.

4. The apparatus of claim 1 or 2, wherein the second connection state is an idle mode, wherein the UE does not have a RRC connection to the network in the idle mode.

5. The apparatus of claim 2, wherein the processing device determines that the first connection state consumes more power than the second connection state based on a first discontinuous reception period in the first connection state and a second discontinuous reception period in the second connection state, wherein the first discontinuous reception period is shorter than the second discontinuous reception period.

6. The apparatus of claim 1, further comprising:

radio frequency circuity coupled to the processing device;

front-end module circuitry coupled to the radio frequency circuitry; and

an antenna coupled to the front-end module circuitry

7. The apparatus of claim 6, wherein the processing device is further to:

determine that the UE is to transition to an idle connection state;

cause the UE to transition to a CELL-FACH connection state; and

cause the antenna to transmit the CELL UPDATE message to the network.

8. The apparatus of claim 1, further comprising radio frequency circuitry to transmit the encoded CELL UPDATE message.

9. The apparatus of claim 1, wherein to cause the UE to transition from a first connection state to a second connection state the processing device is to signal radio frequency circuitry to monitor a paging channel at a discontinuous reception period that is associated with the second connection state, perform measurements according to measurement control information of the second connection state, or release an RRC connection.

10. An apparatus of a Radio Network Controller (RNC) comprising:

a memory device;

a processing device operatively coupled to the memory device, the processing device to: process a CELL UPDATE message sent by a user equipment (UE) in a connected mode to a network associated with the RNC;

determine that the CELL UPDATE message indicates an attempt to release a signaling connection;

determine to transition the UE to a battery efficient state; and

encode a confirmation message with an information element indicating the battery efficient state.

11. The apparatus of the RNC of claim 10, wherein the processing device is further to cause the confirmation message to be transmitted to the UE.

12. The apparatus of the RNC of claim 10, wherein to determine to transition the UE to a battery efficient state, the processing device is to determine that a length of time since a last uplink transmission or CELL UPDATE message from the UE is greater than a threshold length of time.

13. The apparatus of the RNC of claim 10, wherein the processing device is further to generate a reconfiguration message to configure the UE for the battery efficient state.

14. The apparatus of the RNC of claim 10, wherein the processing device does not cause the RNC to establish a connection with the UE in response to the CELL UPDATE message.

15. The apparatus of the RNC of claim 10, wherein the processing device is further to:

decode a second CELL UPDATE message from a second UE;

determine that the CELL UPDATE message includes a cause indicating an attempt to release a signaling connection;

determine not to transition the UE to a battery efficient state; and

generate a confirmation message with an information element indicating a CELL-PCH or a URA-PCH state for the UE.

16. The apparatus of the RNC of claim 10, wherein the component of the RNC is operatively coupled to a NodeB to transmit radio frequency signals to the UE and receive radio frequency signals from the UE.

17. One or more computer-readable media having instructions that, when executed, cause a user equipment (UE) to:

determine that the UE is to transition to a battery efficient state;

encode a CELL UPDATE message having a cause element indicating an attempt to release a signaling connection; and

transmit the CELL UPDATE message having the cause element indicating an attempt to release a signaling connection.

18. The one or more computer-readable media of claim 16, wherein the instructions further cause the UE to:

decode a confirmation message having an indication of the battery efficient state; and transition to the battery efficient state in response to receiving confirmation message.

19. The one or more computer-readable media of claim 16, wherein to determine that the UE is to transition to the battery efficient state, the instructions further cause the UE to:

determine a current connection state for the UE; and

determine that the battery efficient state consumes less power than the current connection state.

20. An apparatus comprising:

means for decoding a CELL UPDATE message sent by a user equipment (UE) in a connected mode to a network associated with a radio network controller (RNC);

means for determining that the CELL UPDATE message indicates an attempt to release a signaling connection;

means for determining to transition the UE to a battery efficient state; and

means for encoding a confirmation message with an information element indicating the battery efficient state.

21. The apparatus of claim 20, wherein the means for determining to transition the UE to a battery efficient state is further to determine that a length of time since a last uplink transmission or CELL UPDATE message from the UE is greater than a threshold length of time.

22. The apparatus of claim 20 or 21 further comprising means for generating a

reconfiguration message to configure the UE for the battery efficient state.

23. An apparatus of a UE comprising:

means for encoding a CELL UPDATE message indicating an attempt to release a signaling connection;

means for decoding, from a network, a confirmation message responsive to the CELL UPDATE message; and

means for causing the UE to transition from a first connection state to a second connection state in response to receiving the confirmation message, wherein the second connection state is associated with a second power consumption level which is less than a first power consumption level associated with the first connection state, and wherein the first connection state is a radio resource control (RRC) state.

24. The apparatus of the UE of claim 23, further comprising means for encoding the CELL UPDATE message in response to determining that the first connection state consumes more power than the second connection state.

25. The apparatus of the UE of claim 23 or 24, further comprising means for causing the UE to transmit the encoded CELL UPDATE message.