Source: http://www.google.es/patents/US8682372
Timestamp: 2017-11-24 06:11:38
Document Index: 753918710

Matched Legal Cases: ['Application No. 2010202720', 'Application No. 2009313191', 'Application No. 2010202720', 'Application No. 2010321205', 'Application No. 2006252042', 'Application No. 2007202206', 'Application No. 2007202206', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 2', 'Application No. 200880124457', 'Application No. 200880124414', 'Application No. 200880124114', 'Application No. 200610064329', 'Application No. 200710137906', 'Application No. 2007101379068', 'Application No. 200880124457', 'Application No. 200880124414', 'Application No. 200610064329', 'Application No. 200710137906', 'Application No. 200610064329', 'Application No. 06118909', 'Application No. 06118909', 'Application No. 08154976', 'Application No. 05112183', 'Application No. 05112183', 'Application No. 07121138', 'Application No. 08849731', 'Application No. 07121138', 'Application No. 10', 'Application No. 05112183', 'Application No. 06119590', 'Application No. 05112183', 'Application No. 10771051', 'Application No. 10768896', 'Application No. 10798525', 'Application No. 10790529', 'Application No. 08154976', 'Application No. 08154976', 'Application No. 08849315', 'Application No. 08849731', 'Application No. 10184515', 'Application No. 07121138', 'Application No. 11177172', 'Application No. 11177171', 'Application No. 05112183', 'Application No. 10170815', 'Application No. 10174218', 'Application No. 06118909', 'Application No. 11160318', 'Application No. 13152938', 'Application No. 13152942', 'Application No. 13159334', 'Application No. 08154976', 'Application No. 06118909', 'Application No. 07121138', 'Application No. 08849315', 'Application No. 08849731', 'Application No. 10184515', 'Application No. 11160318', 'Application No. 2672', 'Application No. 2006', 'Application No. 2010', 'Application No. 2011', 'Application No. 2010', 'Application No. 2010', 'Application No. 2010', 'Application No. 2011', 'Application No. 2006', 'Application No. 2007', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 200610064329', 'Application No. 200710137906', 'Application No. 096131703', 'Application No. 095146891', 'Application No. 096131703']

Patente US8682372 - Method and apparatus for user equipment directed radio resource control in a ... - Google Patentes
A method and apparatus for improved battery performance of user equipment in a wireless network having multiple radio resource control (RRC) states, the method comprising the steps of: monitoring, at the user equipment, application data exchange; determining when no application on the user equipment...http://www.google.es/patents/US8682372?utm_source=gb-gplus-sharePatente US8682372 - Method and apparatus for user equipment directed radio resource control in a UMTS network
Número de publicación US8682372 B2
Número de solicitud US 12/844,302
También publicado como CA2571101A1, CA2571101C, CN101005659A, CN101005659B, CN102740502A, CN102740502B, EP1798998A1, EP1798998B1, EP2247146A2, EP2247146A3, EP2247146B1, EP2262328A1, EP2262328B1, US7949377, US9661611, US20070135080, US20110007682, US20140206369, US20170290085
Número de publicación 12844302, 844302, US 8682372 B2, US 8682372B2, US-B2-8682372, US8682372 B2, US8682372B2
Inventores Muhammad Khaledul Islam, Jeffery Wirtanen
Citas de patentes (168), Otras citas (246), Citada por (12), Clasificaciones (11), Eventos legales (3)
US 8682372 B2
A method and apparatus for improved battery performance of user equipment in a wireless network having multiple radio resource control (RRC) states, the method comprising the steps of: monitoring, at the user equipment, application data exchange; determining when no application on the user equipment is expected to exchange data; and initiating, from the user equipment, a transition to a less battery-demanding radio resource control state or mode.
1. A method performed by a user equipment (UE) operable in a plurality of radio resource control (RRC) connected states including a CELL_DCH state, a CELL_FACH state, a CELL_PCH state and a URA_PCH state, the method comprising:
determining, at a layer above a RRC layer of the UE, that no more data is expected;
determining that the UE is not in one of the PCH states; and
if no more data is expected, and if the UE is not in one of the PCH states, sending to a wireless network a message which requests the wireless network to initiate a network-controlled state transition of the UE to a battery-efficient RRC connected state or to an idle mode.
2. A method according to claim 1, wherein the message comprises a signaling connection release indication (SCRI) message.
3. A method according to claim 1, wherein the wireless network comprises a Universal Terrestrial Radio Access Network (UTRAN).
4. A method according to claim 1, wherein the wireless network comprises a Universal Mobile Telecommunications System (UMTS) network.
5. A method according to claim 1, wherein the battery-efficient RRC connected state is one of the CELL_FACH state, the CELL_PCH state or the URA_PCH state.
6. A method according to claim 1, wherein the message is a request for release of a signaling connection for a core network domain.
7. A method according to claim 6, wherein the core network domain is a packet switched domain.
8. A method according to claim 1, wherein the message causes the wireless network to release a signaling connection between the UE and the wireless network.
9. A method according to claim 1, wherein the step of determining that no more data is expected comprises a determination that no application at the UE is expected to exchange data.
10. A method according to claim 1, wherein the determination that no more data is expected is based on a composite status of data exchange completion indications received from a set of applications that exchanged data in a first RRC connected state.
11. A method according to claim 1, wherein the determining that the UE is not in one of the PCH states comprises determining that the UE is in the CELL_DCH state.
12. A method according to claim 1, wherein the determining that the UE is not in one of the PCH states comprises determining that the UE is in the CELL_FACH state.
13. A method of transitioning a user equipment (UE) between radio resource control (RRC) states or modes in a wireless network, the method comprising:
determining, at a layer above a RRC layer of the UE, that no more data is expected; and
when no more data is expected, sending to a wireless network a message which requests the wireless network to initiate a network-controlled state transition of the UE from a first RRC connected state to a battery-efficient RRC connected state or to an idle mode;
wherein sending to the wireless network the message which requests the wireless network to initiate the network-controlled state transition is performed if the first RRC connected state is not a URA_PCH state.
14. A user equipment (UE) for use in a wireless network and operable in a plurality of radio resource control (RRC) connected states including a CELL_DCH state, a CELL_FACH state, a CELL_PCH state and a URA_PCH state, the UE configured:
to determine, at a layer above a RRC layer, that no further more data is expected;
to determine that the UE is not in one of the PCH states; and
if no more data is expected, and if the UE is not in one of the PCH states, to send to the wireless network a message which requests the wireless network to initiate a network-controlled state transition of the UE to a battery-efficient RRC connected state or to an idle mode.
15. The user equipment according to claim 14, wherein the message comprises a signaling connection release indication (SCRI) message.
16. The user equipment according to claim 14, wherein the wireless network comprises a Universal Terrestrial Radio Access Network (UTRAN).
17. The user equipment according to claim 14, wherein the wireless network comprises a Universal Mobile Telecommunications System (UMTS) network.
18. The user equipment according to claim 14, wherein the battery-efficient RRC connected state is one of the CELL_FACH state, the CELL_PCH state or the URA_PCH state.
19. The user equipment according to claim 14, wherein the message is a request for release of a signaling connection for a core network domain.
20. The user equipment according to claim 19, wherein the core network domain is a packet switched domain.
21. The user equipment according to claim 14, wherein the message causes the wireless network to release a signaling connection between the UE and the wireless network.
22. The user equipment according to claim 14, further configured to determine that no application at the UE is expected to exchange data.
23. The user equipment according to claim 14, wherein the determination that no more data is expected is based on a composite status of data exchange completion indications received from a set of applications of the user equipment that exchanged data in a first RRC connected state.
24. A method according to claim 13, wherein the first RRC connected state is one of a CELL_DCH state, a CELL_FACH state or a CELL—PCH state.
25. A method according to claim 13, wherein the battery-efficient RRC connected state is one of a CELL_FACH state, a CELL_PCH state or the URA_PCH state.
26. The user equipment according to claim 14, wherein the UE configured to determine that the UE is not in one of the PCH states comprises the UE configured to determine that the UE is in the CELL_DCH state.
27. The user equipment according to claim 14, wherein the UE configured to determine that the UE is not in one of the PCH states comprises the UE configured to determine that the UE is in the CELL_FACH state.
28. A user equipment (UE) for use in a wireless network, the user equipment comprising a radio resource control (RRC) connection manager adapted to:
determine, at a layer above a RRC layer of the UE, that no more data is expected; and
when no more data is expected, send to the wireless network a message which requests the wireless network to initiate a network-controlled state transition of the UE from a first RRC connected state to a battery-efficient RRC connected state or to an idle mode;
wherein the RRC connection manager is further adapted to send the message to the wireless network for a network-controlled state transition if the first RRC connected state is not a URA_PCH state.
29. The user equipment according to claim 28, wherein the first RRC connected state is one of a CELL_DCH state, a CELL_FACH state or a CELL_PCH state.
30. The user equipment according to claim 28, wherein the battery-efficient RRC connected state is one of a CELL_FACH state, a CELL_PCH state or the URA_PCH state.
This application is a continuation of U.S. patent application Ser. No. 11/302,263, filed Dec. 14, 2005, the content of which is incorporated herein by reference.
In a UMTS network, a Radio Resource Control (RRC) part of the protocol stack is responsible for the assignment, configuration and release of radio resources between the UE and the UTRAN. This RRC protocol is described in detail in the 3GPP TS 25.331 specifications. Two basic modes that the UE can be in are defined as “idle mode” and “UTRA connected mode”. UTRA stands for UMTS Terrestrial Radio Access. In idle mode, the UE is required to request an RRC connection whenever it wants to send any user data or in response to a page whenever the UTRAN or the Serving GPRS Support Node (SGSN) pages it to receive data from an external data network such as a push server. Idle and Connected mode behaviors are described in details in 3GPP specifications TS 25.304 and TS 25.331.
The present system and method overcome certain deficiencies of the prior art by providing the transitioning from an RRC-connected mode to a more battery efficient state or mode. In particular, the present method and apparatus preferably provide for transitioning based on either the UE initiating termination of a signaling connection for a specified core network domain or indicating to the UTRAN that a transition should occur from one connected state to another.
In particular, if an application on the UE determines that it is done with the exchange of data, it can send a “done” indication to the “RRC connection manager” component of the UE software. The RRC connection manager keeps track of all existing applications (including those providing a service over one or multiple protocols), associated Packet Data Protocol (PD) contexts, associated packet switched (PS) radio bearers and associated circuit switched (CS) radio bearers. A PDP Context is a logical association between a UE and PDN (Public Data Network) running across a UMTS core network. One or multiple applications (e.g. an e-mail application and a browser application) on the UE may be associated with one PDP context. In some cases, one application on the UE is associated with one primary PDP context and multiple applications may be tied with secondary PDP contexts. The RRC Connection Manager receives “done” indications from different applications on the UE that are simultaneously active. For example, a user may receive an e-mail from a push server while browsing the web. After the e-mail application has sent an acknowledgement, it may indicate that it has completed its data transaction; however, the browser application may not send such indication. Based on a composite status of such indications from active applications, the UE software can decide how long it should wait before it can initiate a signaling connection release of the core network packet service domain. A delay in this case can be introduced to ensure that the application is truly finished with data exchange and does not require an RRC connection. The delay can be dynamic based on traffic history and/or application profiles. Whenever the RRC connection manager determines with some probability that no application is expected to exchange any data, it can send a signaling connection release indication procedure for the appropriate domain (e.g. PS domain). Alternatively it can send a request for state transition within connected mode to the UTRAN.
The above decision may also take into account whether the network supports the URA_PCH state and the transition behavior to this state.
The present application further preferably provides user equipment adapted for reduced battery consumption in a UMTS network, the user equipment having a radio subsystem including a radio adapted to communicate with the UMTS network; a radio processor having a digital signal processor and adapted to interact with said radio subsystem; memory; a user interface; a processor adapted to run user applications and interact with the memory, the radio, and the user interface, and adapted to run applications, the user equipment characterized by having means for: monitoring, at the user equipment, application data exchange; determining when no application on the user equipment is expected to exchange data; and initiating, from the user equipment, a transition to a less battery-demanding radio resource control state or mode.
In idle mode 110, the UE must request an RRC connection to set up the radio resource whenever data needs to be exchanged between the UE and the network. This can be as a result of either an application on the UE requiring a connection to send data, or as a result of the UE monitoring a paging channel to indicate whether the UTRAN or SGSN has paged the UE to receive data from an external data network such as a push server. In addition, the UE also requests RRC connection whenever it needs to send a Mobility Management signaling message such as Location Area Update.
Within the RRC connected mode 120, the RRC state can be changed at the discretion of the UTRAN. Specifically, if the data inactivity is detected for a specific amount of time or data throughput below a certain threshold is detected, the UTRAN may move the RRC state from CELL_DCH state 122 to the CELL_FACH state 124, CELL_PCH state 126 or URA_PCH state 128. Similarly, if the payload is detected to be above a certain threshold then the RRC state can be moved from CELL_FACH state 124 to CELL_DCH state 122.
The difference between CELL_PCH state 126 and URA_PCH state 128 is that the URA_PCH state 128 only triggers a URA Update procedure if the UE's current UTRAN registration area (URA) is not among the list of URA identities present in the current cell. Specifically, reference is made to FIG. 2. FIG. 2 shows an illustration of various UMTS cells 210, 212 and 214. All of these cells require a cell update procedure if reselected to a CELL_PCH State 128. However, in a UTRAN registration area, each will be within the same UTRAN registration area 220, and thus a URA update procedure is not triggered when moving between 210, 212 and 214 when in a URA_PCH mode.
In a first exemplary infrastructure, the RRC moves between an idle mode and a CELL_DCH state 122 directly. In the CELL_DCH state 122, if two seconds of inactivity are detected, the RRC state changes to a CELL_FACH state 124. If in CELL_FACH state 124, ten seconds of inactivity are detected then the
RRC state changes to CELL_PCH state 126. Forty five minutes of inactivity in CELL_PCH state 126 will result in the RRC state moving back to idle mode 110.
The URA_PCH state 128 with a DRX cycle similar to that of the idle state is likely the optimal trade up between battery life and latency for connection. However, URA_PCH is currently not supported in the UTRAN. It is therefore desirable to quickly transition to the idle mode as quickly as possible after an application is finished with the data exchange from a batter life perspective.
Reference is now made to FIG. 3. When transitioning from an idle mode to a connected mode various signaling and data connections need to be made. Referring to FIG. 3, the first item needing to be performed is an RRC connection setup 310. As indicated above, this RRC connection setup 310 can only be torn down by the UTRAN.
The above UE initiated transition to idle mode can happen in any stage of the RRC connected mode 120 as illustrated in FIG. 1 and ends up having the network release the RRC connection and moving to an idle mode 110 as illustrated in FIG. 1. This is also applicable when the UE is performing any packet data services during a voice call. In this case only the PS domain is released, but the CS domain remains connected.
As will be appreciated by those skilled in the art, in some cases it may be more desirable to be in the connected mode state URA_PCH than in idle mode 110.
For example, if the latency for connection to the CELL_DCH or the CELL_FACH connected mode states is required to be lower, it is preferable to be in a connected mode PCH state. There are two ways of accomplishing this. First is by changing the 3GPP specifications to allow for the UE to request the UTRAN to move it to a specific state, in this case the URA_PCH state 128.
Alternatively, the RRC connection manager may take into account other factors such as what the RRC connection is currently in. If, for example, the RRC connection is in the URA_PCH state 128 it may decide that it is unnecessary to move to idle mode 110 and thus no signaling connection release procedure is initiated.
Reference is now made to FIG. 4B. FIG. 4B utilizes the same exemplary infrastructure “four” from above, only now implementing the signalling connection release.
The UE in the example of FIG. 4B has an application specific inactivity timeout, which in the example of FIG. 4B is two seconds and is illustrated by step 440. After the RRC connection manager has determined that there is inactivity for the specific amount of time, the UE releases the signaling connection setup 312 in step 442 and the RRC connection is released by the network in step 428.
As illustrated in FIG. 4B, the current consumption curing the CELL_DCH step 122 is still about 200 to 300 milliamps. However, the connection time is only about eight seconds. As will be appreciated by those skilled in the art, the considerably shorter amount of time that the mobile device stays in the CELL_DCH state 122 results in significant battery savings for a UE device that is always on.
As can be seen further in FIG. 5B, the RRC starts in an idle mode 110, and moves to a CELL_DCH state 122 without proceeding into the CELLFACH state 124.
When required network registration or activation procedures have been completed, UE 1100 may send and receive communication signals over the network 1119. Signals received by antenna 1116 through communication network 1119 are input to receiver 1112, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection and the like, and in the example system shown in FIG. 7, analog to digital (ND) conversion. ND conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in the DSP 1120. In a similar manner, signals to be transmitted are processed, including modulation and encoding for example, by DSP 1120 and input to transmitter 1114 for digital to analog conversion, frequency up conversion, filtering, amplification and transmission over the communication network 1119 via antenna 1118. DSP 1120 not only processes communication signals, but also provides for receiver and transmitter control. For example, the gains applied to communication signals in receiver 1112 and transmitter 1114 may be adaptively controlled through automatic gain control algorithms implemented in DSP 1120.
Packet data is routed through Service GPRS Support Node (SGSN) 850. SGSN 850 is the gateway between the RNC and the core network in a GPRS/UMTS network and is responsible for the delivery of data packets from and to the UEs 802 within its geographical service area. IuPS interface 848 is used between the RNC 810 and SGSN 850, and is the packet-switched connection for carrying (typically) data traffic and signaling between the UTRAN 820 and the core data network. The main signaling protocol used is RANAP (described above).
The SGSN 850 communicates with the Gateway GPRS Support Node (GGSN) 860. GGSN 860 is the interface between the UMT/GPRS network and other networks such as the Internet or private networks. GGSN 860 is connected to a public data network PDN 870 over a Gi interface.
US20020022455 * 20 Ago 2001 21 Feb 2002 Juha Salokannel Method for reducing the power consumption of a wireless terminal, a communication system and a wireless terminal
US20040203971 * 21 Jun 2002 14 Oct 2004 Kuo Richard Lee-Chee Method for determining RLC entity re-establishment during SRNS relocation
US20050032555 * 7 Ago 2003 10 Feb 2005 Iqbal Jami Method of intermittent activation of receiving circuitry of a mobile user terminal
US20050245267 * 30 Abr 2004 3 Nov 2005 Guethaus Roland J Methods of allocating a channel to baseband processing units in a communication system
US20060223564 * 31 Mar 2005 5 Oct 2006 Rosen Eric C System and method for efficiently providing high-performance dispatch services in a wireless system
EP1858209A1 14 Ago 2006 21 Nov 2007 Research In Motion Limited Method and system for signaling release cause indication in a UMTS network
EP1981224B1 31 Mar 2008 27 Jul 2011 Samsung Electronics Co., Ltd. Transitioning radio resource control state of user equipment to idle state
WO2000/62435A1 Título no disponible
WO2001/52574A1 Título no disponible
WO2005050917A3 19 Nov 2004 14 Jul 2005 Nokia Corp Controlling network resources after determination of a flow termination
WO2007052098A3 27 Sep 2006 12 Jul 2007 Luis Barreto Hsupa harq process flushing
4 "3rd Generation Partnership Project 2; Data Service Options for Spread Spectrum Systems: Service Options 33 and 66," 3GPP2 C.S0017-012-A, Version 1.0, Jun. 11, 2004 (70 pgs.).
5 "3rd Generation Partnership Project 2; Data Service Options for Spread Spectrum Systems: Service Options 33 and 66," 3GPP2 C.S0017-012-A, Version 2.0, May 2006 (70 pgs.).
6 "3rd Generation Partnership Project 2; Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems Release D," 3GPP2 C.S0005-D, Version 1.0, Feb. 2004 (2247 pgs.).
7 "3rd Generation Partnership Project 2; Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems Release D," 3GPP2 C.S0005-D, Version 2.0, Sep. 6, 2005 (2367 pgs.).
8 "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-URTRA); Overall description; Stage 2 (Release 8)," 3GPP TS 36.300 V8.9.0 (Jun. 2009) (159 pgs.).
9 "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) protocol specification (Release 8)," 3GPP TS 36.321 V8.7.0 (Sep. 2009) (47 pgs.).
10 "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol specification (Release 8)," 3GPP TS 36.331 V8.6.0 (Jun. 2009) (207 pgs.).
11 "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode (Release 8)," 3GPP TS 36.304 V8.6.0 (Jun. 2009) (30 pgs.).
12 "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 8)"; 3GPP TS 25.331 V8.8.0 (Sep. 2009) (1697 pages).
13 "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode (Release 7)," 3GPP TS 25.304 V7.1.0 (Dec. 2006) (38 pgs.).
14 "3rd Generation partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access (Release 8)," 3GPP TS 23.401 V8.0.0 (Dec. 2007) (167 pgs.).
15 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal terrestrial Radio Access Network (E-UTRAN) access (Release 8)," 3GPP TS 23.401 V8.7.0 (Sep. 2009) (234 pgs.).
16 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 8)," 3GPP TS 23.203 V8.1.1 (Mar. 2008) (87 pgs.).
17 "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 8)," 3GPP TS 23.203 V8.7.0 (Sep. 2009) (114 pgs.).
18 "Digital Cellular Telecommunications System (Phase 2+)"; ETSI Standards European Telecommunications Standards Institute, Sophia-Antipo, FR, vol. 3-SA2, No. V6110, Dec. 2005, XP014032437.
19 3GPP 25.331 Radio Resource Control (RRC); Protocol Specification, V5.18.0 (Sep. 2006), pp. 12-13.
20 3GPP Organizational Partners, 3GPP TS 25.331 v8.7.0, Sections 6.3. 8.1.14.2, 8.3.1.2, 13.2, http://www.3gpp.org/ftp/Specs/archive/25—series/25.331/25331-870.zip (4 pages), Jan. 2009.
21 3GPP Radio Resource Control Protocal for the UE-UTRAN Radio Interface, 3GPP TS 25.331 V6.8.0 (Dec. 2005) (1,174 pgs.).
22 3GPP Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 9); 3GPP TS 25.331 v9.0.0 (Sep. 2009) Section 8.1.14 (pp. 142-144) and Sections 13.1 and 13.2 (pp. 1437-1439).
23 3GPP TS 25.331 V5.16.0 (Mar. 2006) (1045 pgs.).
24 3GPP TSG RAN WG#2 Meeting #67; R2-094437; Shenzhen, People's Republic of China, Aug. 24-28, 2009 (57 pages).
25 3GPP TSG-RAN WG2 Meeting #60 R2-075251, Jeju, South Korea, Nov. 5-9, 2007 (13 pages).
26 3GPP TSG-RAN WG2 Meeting #63 R2-084647, Aug. 18-22, 2008 (14 pages).
27 3GPP TSG-RAN WG2 Meeting #68, R2-097173, Jeju, South Korea, Nov. 9-13, 2009 (5 pages).
28 3GPP TSG-RAN WG2 Meeting #68, R2-097174, Jeju, South Korea, Nov. 9-13, 2009 (8 pages).
29 3GPP TSG-RAN WG2 Meeting #69, R2-101710, San Francisco, California, Feb. 22-26, 2010 (6 pages).
30 3GPP TSG-RAN WG2 Meeting #69, R2-101726, San Francisco, California, Feb. 22-26, 2010 (6 pages).
31 3GPP TSG-RAN WG2 Meeting #69; R2101726; San Francisco, CA Feb. 22-26, 2010 (6 pages).
32 3GPP TSG-RAN WG2#67bis; R2-096027; Miyazaki, Japan, Oct. 12-16, 2009 (4 pages).
33 3GPP TSG-RAN WG2#68; R2096624; Jeju, South Korea, Nov. 9-13, 2009 (8 pages).
34 3GPP TSG-RAN2 Meeting #64 R2-086557, Prague, Czech, Nov. 10-14, 2008 (13 pages).
35 3GPP TSG-RAN2 Meeting #67; R2-094792; Shenzhen, China, Aug. 24-28, 2009 (10 pages).
36 3GPP TSG-RAN2 Meeting #69; R2101440; San Francisco, CA, Feb. 22-26, 2010 (18 pages).
37 3GPP TSG-RAN2 Meeting #69; R2101441; San Francisco, CA, Feb. 22-26, 2010 (20 pages).
38 3GPP: "Radio resource control (RRC) protocol specification V7.0.0," 3GPP TS 25.331 V7.0.0, (1,249 pgs.), Mar. 2006.
39 3rd Generation Partnership Project 2 "3GPP2", Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems, Release 0, 3GPP2 C.S0005-0, Version 3.0, Jun. 15, 2000 (1168 pgs.).
40 3rd Generation Partnership Project 2"3GPP2", "Data Service Options for Spread Spectrum Systems: Service Options 33 and 66," 3GPP@ C.S0017-012-A, Version 1.0, Jun. 11, 2004 (70 pgs.).
41 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 8); 3GPP TS 25.331 V8.8.0 (Sep. 2009) (1697 pages).
42 Australian Examiners Report for AU Application No. 2010202720 dated Feb. 3, 2012 (16 pages).
43 Australian First Examination Report dated Feb. 13, 2013, issued in Australian Application No. 2009313191 (3 pages).
44 Australian First Examination Report dated Feb. 3, 2012, issued in Australian Application No. 2010202720 (16 pages).
45 Australian First Examination Report dated Jul. 30, 2013, issued in Australian Application No. 2010321205, (2 pages).
46 Australian First Report for AU Application No. 2006252042, dated Apr. 9, 2008, (this reference relates to U.S. Appl. No. 11/302,263) (2 pgs.).
47 Australian First Report for AU Application No. 2007202206, dated Sep. 2, 2008, (this reference relates to U.S. Appl. No. 11/464,380) (7 pgs.).
48 Australian Second Report for AU Application No. 2007202206, dated Sep. 30, 2009, (this reference relates to U.S. Appl. No. 11/464,380) (1 pg.).
49 Canadian Office Action dated Jul. 20, 2012, issued in Canadian Patent Application No. 2,705,477 (4 pages).
50 Canadian Office Action dated Jun. 21, 2012, issued in Canadian Application No. 2,705,476 (3 pages).
51 Canadian Office Action dated Jun. 21, 2012, issued in Canadian Patent Application No. 2,705,478 (4 pages).
52 Canadian Office Action for Application No. 2,661,592 dated Nov. 14, 2011 (3 pages).
53 Canadian Office Action for CA Application 2,571,101, dated Mar. 16, 2010, (this reference relates to U.S. Appl. No. 11/302,263) (4 pgs.).
54 Canadian Office Action for CA Application No. 2,571,101 dated Apr. 30, 2012 (4 pages).
55 Canadian Office Action for Canadian Application 2,589,373 dated Feb. 22, 2011 (5 pages).
56 Canadian Office Action for Canadian Patent Application No. 2,589,373, dated May 31, 2012 (3 pages).
57 Canadian Office Action for Canadian Patent Application No. 2,661,592, dated Jun. 18, 2012 (5 pages).
58 Chairman: Title LTE CP Session Report; 3GPP TSG RAN WG2 #63bis; R2-085921; Prague, Czech Republic; Sep. 29-Oct. 3, 2008 (38 pgs.).
59 Chinese First Office Action dated Aug. 2, 2012, issued in Chinese Application No. 200880124457.6 (24 pages).
60 Chinese First Office Action dated Aug. 3, 2012, issued in Chinese Application No. 200880124414.8 (10 pages).
61 Chinese First Office Action dated Oct. 31, 2012, issued in Chinese Application No. 200880124114.X (10 pages).
62 Chinese First Office Action for Chinese Application No. 200610064329.X, dated Feb. 6, 2009, (including translation) (this reference relates to U.S. Appl. No. 11/302,263) (18 pgs.).
63 Chinese Fourth Office Action dated Mar. 18, 2013, issued in Chinese Application No. 200710137906.8 (7 pages).
64 Chinese Office Action for Application No. 2007101379068, dated Apr. 25, 2011 (with translation) (13 pages).
65 Chinese Second Office Action dated Jan. 30, 2013, issued in Chinese Application No. 200880124457.6 (25 pages).
66 Chinese Second Office Action dated Jun. 5, 2013, issued in Chinese Application No. 200880124414.8, (8 pages).
67 Chinese Second Office Action for Chinese Application No. 200610064329.X, dated Feb. 24, 2010, (including translation) (this reference relates to U.S. Appl. No. 11/302,263) (18 pgs.).
68 Chinese Third Office Action dated Aug. 27, 2012, issued in Chinese Application No. 200710137906.8 (12 pages).
69 Chinese Third Office Action dated Oct. 8, 2011, issued in Chinese Application No. 200610064329.X (7 pages).
70 Communication from EPO regarding EP Application P44025EP1/GVR dated Dec. 15, 2011 (7 pages).
71 Communication from the EP Patent Office for EP Application No. 06118909.8, dated Jun. 25, 2008 (this reference relates to U.S. Appl. No. 11/464,380) (3 pgs.).
72 Communication from the EP Patent Office for EP Application No. 06118909.8, dated Nov. 12, 2007 (this reference relates to U.S. Appl. No. 11/464,380) (4 pgs.).
73 Communication from the EPO for related European Application 07121138.7-2412 dated Aug. 8, 2011.
74 Communication from the EPO regarding related European Application 10184515.4-2412 dated Aug. 8, 2011.
75 EP Application No. 08154976.8, Communication pursuant to Article 94(3) EPC, dated Oct. 8, 2009.
76 EP Communication for EP Application 07121138.7 dated Oct. 19, 2010.
77 EP Communication for EP Application 08849315.0 dated Apr. 19, 2012 (5 pages).
78 EP Communication for EP Application No. 05112183.8, dated Jan. 24, 2008 (2 pgs.).
79 EP Communication for EP Application No. 05112183.8, dated Sep. 7, 2009 (3 pgs.).
80 EP Examination Report for EP Application No. 07121138.7-2412 dated Sep. 7, 2009 (1 page).
81 EP Examination Report for EP Application No. 08849731.8 dated Apr. 19, 2012 (5 pages).
82 EP Extended Search Report for EP Application 06119590.5 dated Mar. 20, 2007.
83 EP Extended Search Report for EP Application 10184515.4 dated Nov. 19, 2010.
84 EP Intention to Grant EP Application 10183886.0 dated Apr. 13, 2012 (5 pages).
85 EP Intention to Grant EP Application No. 07121138.7 dated Jan. 26, 2012 (66 pages).
86 EP Office Action for EP Application No. 10 184 515.4 dated Dec. 15, 2011 (7 pages).
87 EP Search Report for EP Application 10183886.0 dated Nov. 15, 2010.
88 EP Search Report for EP Application No. 05112183.8, dated May 3, 2007 (7 pgs.).
89 EP Search Report for EP Application No. 06119590.5 dated Oct. 25, 2007.
90 European Communication dated Jan. 24, 2008, issued in European Application No. 05112183.8 (2 pages).
91 European Communication dated Jul. 18, 2012, issued in European Application No. 10771051.9 (2 pages).
92 European Communication dated Jul. 19, 2012, issued in European Application No. 10768896.2 (2 pages).
93 European Communication dated Jul. 19, 2012, issued in European Application No. 10798525.1 (2 pages).
94 European Communication dated Jul. 25, 2012, issued in European Application No. 10790529.1 (2 pages).
95 European Examination Report dated Aug. 10, 2009, issued in European Application No. 08154976.8 (4 pages).
96 European Examination Report dated Dec. 28, 2011, issued in European Application No. 08154976.8 (3 pages).
97 European Examination Report dated Feb. 14, 2013, issued in European Application No. 08849315.0 (6 pages).
98 European Examination Report dated Feb. 21, 2013, issued in European Application No. 08849731.8 (5 pages).
99 European Examination Report dated May 22, 2012, issued in European Application No. 10184515.4 (9 pages).
100 European Examination Report dated Sep. 7, 2009, issued in European Application No. 07121138.7 (1 page).
101 European Extended Search Report dated Nov. 22, 2012, issued in European Application No. 11177172.1 (6 pages).
102 European Extended Search Report dated Nov. 29, 2012, issued in European Application No. 11177171.3 (7 pages).
103 European Intent to Grant dated Dec. 17, 2010, issued in European Application No. 05112183.8 (41 pages).
104 European Intent to Grant dated Oct. 20, 2011, issued in European Application No. 10170815.4 (1 page).
105 European Search Report for Application No. 10174218.7 dated Jun. 21, 2011 (7 pages).
106 European Search Report for EP Application No. 06118909.8, dated Jul. 30, 2009 (this reference relates to U.S. Appl. No. 11/464,380) (3 pgs.).
107 Examination Report regarding EP Application No. 11160318.9 dated Nov. 15, 2011.
108 Extended European Search Report dated Apr. 12, 2013, issued in European Application No. 13152938.0 (10 pages).
109 Extended European Search Report dated Apr. 12, 2013, issued in European Application No. 13152942.2 (10 pages).
110 Extended European Search Report dated Apr. 16, 2013, issued in European Application No. 13159334.5 (10 pages).
111 Extended European Search Report for Application No. 08154976.8, dated Sep. 3, 2008.
112 Extended European Search Report for EP 09180936.8, dated May 20, 2010 (9 pgs.).
113 Extended European Search Report for EP 10170815.4, dated Nov. 2, 2010 (5 pgs.).
114 Extended European Search Report for EP Application 08154976.8 dated Sep. 3, 2008.
115 Extended European Search Report for EP Application No. 06118909.8, dated Nov. 24, 2006 (this reference relates to U.S. Appl. No. 11/464,380) (8 pgs.).
116 Extended European Search Report for EP Application No. 07121138.7, dated May 16, 2008 (this reference relates to U.S. Appl. No. 11/464,380) (10 pgs.).
117 Extended European Search Report for EP Application No. 08849315.0 dated Jan. 18, 2011 (8 pages).
118 Extended European Search Report for EP Application No. 08849731.8 dated Jan. 18, 2011 (7 pages).
119 Extended European Search Report for EP Application No. 10184515, dated Nov. 19, 2010, (this reference relates to U.S. Appl. No. 11/464,380) (7 pages).
120 Extended Search Report for EP Application No. 11160318.9 dated Jun. 24, 2011 (5 pages).
121 Final Office Action dated Aug. 15, 2013, issued in U.S. Appl. No. 13/244,761, (21 pages).
122 Final Office Action dated Aug. 30, 2013, issued in U.S. Appl. No. 12/953,049, (19 pages).
123 Final Office Action dated Dec. 24, 2012, issued in U.S. Appl. No. 12/616,024 (56 pages).
124 Final Office Action dated Feb. 26, 2013, issued in U.S. Appl. No. 12/897,945 (13 pages).
125 Final Office Action dated Feb. 27, 2013, issued in U.S. Appl. No. 12/953,144 (8 pages).
126 Final Office Action dated Jul. 12, 2012, issued in U.S. Appl. No. 13/244,761 (26 pages).
127 Final Office Action dated Jun. 26, 2013, issued in U.S. Appl. No. 13/532,353 (15 pages).
128 Final Office Action dated Mar. 25, 2013, issued in U.S. Appl. No. 12/897,959 (22 pages).
129 Final Office Action dated May 23, 2013, issued in U.S. Appl. No. 11/464,380 (22 pages).
130 Final Office Action dated Oct. 11, 2012, issued in U.S. Appl. No. 12/649,461 (19 pages).
131 Final Office Action dated Sep. 13, 2012, issued in U.S. Appl. No. 12/953,049 (18 pages).
132 Indian Office Action dated Apr. 7, 2011, issued in Indian Application No. 2672/DEL/2006 (2 pages).
133 International Application No. PCT/US2009/063912, Communication Relating to the Results of the Partial International Search dated Feb. 17, 2010.
134 International Preliminary Report on Patentability, for International Application No. PCT/CA2010/002031, dated Mar. 9, 2012 (8 pages).
135 International Search Report and Written Opinion dated Jan. 21, 2013, issued in International Application No. PCT/US2012/064499 (11 pages).
136 Japanese Final Office Action for JP Application No. 2006-335943, dated Dec. 3, 2009 (including translation), (this reference relates to U.S. Appl. No. 11/302,263) (6 pgs.).
137 Japanese Office Action dated Jun. 20, 2012, issued in Japanese Application No. 2010-533398 (9 pages).
138 Japanese Office Action dated Nov. 12, 2012, issued in Japanese Application No. 2011-535770 (7 pages).
139 Japanese Office Action dated Oct. 29, 2012, issued in Japanese Application No. 2010-085595 (6 pages).
140 Japanese Office Action for Japanese Patent Application No. 2010-533396, dated May 29, 2012 (5 pages).
141 Japanese Office Action for Japanese Patent Application No. 2010-533397, dated Apr. 23, 2012 (8 pages).
142 Japanese Office Action for Japanese Patent Application No. 2011-083176, dated May 30, 2012 (6 pages).
143 Japanese Office Action for JP Application No. 2006-335943, dated Jun. 19, 2009 (including translation), (this reference relates to U.S. Appl. No. 11/302,263) (10 pgs.).
144 JP Office Action for JP Application No. 2007-131146, dated Sep. 30, 2010 (7 pgs.)
145 KIPO Notice of Decision for Patent Application No. 10-2010-7012925 dated Nov. 30, 2011 with translation (4 pages).
146 Korean Application No. 10-2008-0092802, filed on Oct. 16, 2008, including English equivalent EP 1981224 (31 total pages).
147 Korean Notice Requesting Submission of Opinion for Korean Application No. 10-2006-0128027 (including translation), dated Aug. 28, 2008 (this reference relates to U.S. Appl. No. 11/302,263) (4 pgs.).
148 Korean Notice Requesting Submission of Opinion for Korean Application No. 10-2006-0128027 (including translation), dated Nov. 26, 2007 (this reference relates to U.S. Appl. No. 11/302,263) (8 pgs.).
149 Korean Office Action dated Aug. 13, 2012, issued in Korean Application No. 10-2011-7012708 (6 pages).
150 Korean Office Action dated Feb. 26, 2013, issued in Korean Application No. 10-2011-7012708 (9 pages).
151 Korean Office Action dated Jan. 17, 2013, issued in Korean Application No. 10-2012-7026886 (8 pages).
152 Korean Office Action for Korean Application No. 10-2010-7012701 dated Jul. 11, 2011 (11 pages including translation).
153 Korean Office Action for Korean Application No. 10-2010-7012925 dated Jul. 11, 2011 (6 pages including translation).
154 Mexican Office Action dated Jan. 11, 2013, issued in Mexican Application No. MX/a/2010/005249 (4 pages).
155 Mexican Office Action dated Jan. 11, 2013, issued in Mexican Application No. MX/a/2010/005251 (4 pages).
156 Mexican Office Action dated Jul. 13, 2012, issued in Mexican Application No. MX/a/2011/004888 (7 pages).
157 MX Office Action for Mexican Application No. MX/a/2010/005255, dated Feb. 13, 2012 (9 pages).
158 Nokia Corporatio et al.: "Fast Dormancy: A way forward", 3GPP Draft; R2-084647, 3rd Generation Partnership Project (3GPP) TSG-RAN WG2 Meeting #63, Jeju, South Korea, Aug. 18-22, 2008.
159 Notice of Allowance for U.S. Appl. No. 11/302,263 dated Feb. 28, 2011 (15 pages).
160 Notice of Allowance for U.S. Appl. No. 12/195,018, dated May 2, 2012 (4 pages).
161 Notice of Allowance for U.S. Appl. No. 12/270,522 dated Mar. 10, 2011 (34 pages).
162 Notice of Allowance for U.S. Appl. No. 12/270,562, dated Apr. 5, 2012 (27 pages).
163 Notice of Allowance for U.S. Appl. No. 13/244,749, dated Jun. 25, 2012 (13 pages).
164 Notice of Allowance for U.S. Appl. No. 13/244,765, dated Jun. 28, 2012 (8 pages).
165 Notice of Allowance for U.S. Appl. No. 13/244,792 dated Nov. 28, 2011 (19 pages).
166 Notice of Decision for Patent, for Korean Patent Application No. 10-2010-7012701, dated Mar. 8, 2012 (3 pages).
167 Notice of Decision for Patent, for Korean Patent Application No. 10-2010-7012778, dated Mar. 26, 2012 (7 pages).
168 Notification of Grant of Rights for Invention Patent, in Chinese Patent Application No. 200610064329.X, dated Apr. 9, 2012.
169 Office Action dated Apr. 19, 2013, issued in U.S. Appl. No. 13/157,724 (46 pages).
170 Office Action dated Feb. 7, 2013, issued in U.S. Appl. No. 12/953,049 (8 pages).
171 Office Action dated Jan. 16, 2013, issued in U.S. Appl. No. 13/532,353 (23 pages).
172 Office Action dated Jan. 22, 2013, issued in U.S. Appl. No. 13/244,761 (10 pages).
173 Office Action dated Jan. 7, 2013, issued in U.S. Appl. No. 11/464,380 (12 pages).
174 Office Action dated Jul. 31, 2012, issued in U.S. Appl. No. 12/953,144 (30 pages).
175 Office Action dated Jun. 26, 2013, issued in U.S. Appl. No. 12/844,302 (19 pages).
176 Office Action dated Nov. 20, 2012, issued in U.S. Appl. No. 12/897,959 (42 pages).
177 Office Action dated Oct. 18, 2012, issued in U.S. Appl. No. 12/897,945 (34 pages).
178 Office Action dated Sep. 17, 2013, issued in U.S. Appl. No. 13/921,728, (25 pages).
179 Office Action dated Sep. 18, 2013, issued in U.S. Appl. No. 12/616,024, (19 pages).
180 Office Action for U.S. Appl. 12/195,018 dated Feb. 10, 2012 (14 pages).
181 Office Action for U.S. Appl. 12/270,562 dated Nov. 18, 2010 (21 pages).
182 Office Action for U.S. Appl. 13/244,765 dated Apr. 17, 2012 (12 pgs.).
183 Office Action for U.S. Appl. No. 11/464,380 dated Dec. 22, 2010 (19 pages).
184 Office Action for U.S. Appl. No. 11/464,380 dated Dec. 22, 2010.
185 Office Action for U.S. Appl. No. 11/464,380, dated Jul. 20, 2012 (15 pages).
186 Office Action for U.S. Appl. No. 11/467,309 dated Jan. 21, 2010 (25 pages).
187 Office Action for U.S. Appl. No. 11/467,309 dated Jul. 20, 2010 (25 pages).
188 Office Action for U.S. Appl. No. 11/467,309 dated Jun. 12, 2009 (25 pages).
189 Office Action for U.S. Appl. No. 11/467,309 dated Jun. 3, 2011 (21 pages).
190 Office Action for U.S. Appl. No. 11/467,309 dated Nov. 14, 2011 (26 pages).
191 Office Action for U.S. Appl. No. 11/467,309 dated Nov. 14, 2011 (28 pages).
192 Office Action for U.S. Appl. No. 12/107,514 dated Apr. 14, 2011 (38 pages).
193 Office Action for U.S. Appl. No. 12/107,514 dated Nov. 10, 2011 (13 pages).
194 Office Action for U.S. Appl. No. 12/195,018 dated Apr. 20, 2011 (33 pages).
195 Office Action for U.S. Appl. No. 12/195,018 dated Jan. 5, 2011.
196 Office Action for U.S. Appl. No. 12/195,018 dated Oct. 6, 2011 (21 pages).
197 Office Action for U.S. Appl. No. 12/270,562 dated Apr. 7, 2011 (19 pages).
198 Office Action for U.S. Appl. No. 12/270,562 dated Mar. 10, 2011 (19 pages).
199 Office Action for U.S. Appl. No. 12/270,562 dated Nov. 18, 2010.
200 Office Action for U.S. Appl. No. 12/953,049 dated Dec. 22, 2011 (19 pages).
201 Office Action for U.S. Appl. No. 13/244,749 dated Dec. 21, 2011 (29 pages).
202 Office Action for U.S. Appl. No. 13/244,761 dated Dec. 15, 2011 (35 pages).
203 Office Action for U.S. Appl. No. 13/244,765 dated Feb. 15, 2012 (22 pages).
204 Office Action for U.S. Appl. No. 13/244,849 dated Dec. 15, 2011 (26 pages).
205 Office Action for U.S. Appl. No. 13/244,849 dated Mar. 22, 2012 (18 pages).
206 PCT International Search Report and Written Opinion dated Feb. 11, 2011, issued in International Application No. PCT/EP2010/068064 (16 pages).
207 PCT International Search Report and Written Opinion dated Jan. 28, 2011, issued in International Application No. PCT/EP2010/064860 (12 pages).
208 PCT International Search Report for Application PCT/US2009/063912 dated May 3, 2010 (6 pages).
209 PCT Search Report and Written Opinion for International Application No. PCT/CA2008/002000, dated Feb. 13, 2009.
210 PCT Search Report and Written Opinion for International Application No. PCT/CA2008/002001, dated Feb. 2, 2009.
211 PCT Search Report and Written Opinion for International Application No. PCT/CA2008/002002, dated Jan. 15, 2009.
212 PCT Search Report and Written Opinion for International Application No. PCT/EP2010/068063, dated Mar. 25, 2011 (23 pages).
213 PCT Search Report and Written Opinion for PCT Application No. PCT/CA2010/002031 dated Apr. 12, 2011 (8 pages).
214 PCT Search Report and Written Opinion for PCT Application No. PCT/EP2010/064859 dated Feb. 9, 2011 (17 pages).
215 PCT Search Report and Written Opinion for PCT Application No. PCT/EP2010/068065 dated Feb. 11, 2011 (17 pages).
216 PCT Search Report for Application PCT/CA2007/001497 dated Dec. 18, 2008.
217 PCT Search Report for Application PCT/US2009/063912 dated Feb. 17, 2010.
218 PCT Written Opinion and Search Report for Application PCT/US2009/063912 dated Apr. 13, 2010.
219 PCT Written Opinion for Application PCT/CA2007/001497 dated Dec. 12, 2007.
220 PCT Written Opinion for PCT Application PCT/US2009/063912 dated May 3, 2010 (22 pages).
221 PCT/CA2008/002000 International Search Report and Written Opinion dated Feb. 13, 2009.
222 PCT/CA2008/002001 International Search Report and Written Opinion dated Feb. 2, 2009.
223 PCT/CA2008/002002 International Search Report and Written Opinion dated Jan. 15, 2009.
224 Qualcomm Europe; Title: Introduction of Signaling Connection Release Indication; 3GPP TSG-RAN WG2 meeting #63bis; R2-085584; Prague, Czech Republic; Sep. 29-Oct. 3, 2008 (5 pgs.).
225 Research in Motion Limited, AT&T; Title: Fast Dormancy; A way forward; 3GPP TSG-RAN2 Meeting #63bis; R2-085134; Prague, Czech Republic; Sep. 29-Oct. 3, 2008 (13 pgs.).
226 Research in Motion Limited: "Fast dormancy alternatives", 3GPP Draft; R2-083626, 3rd Generation Partnership Project (3GPP) TSG-RAN WG2 Meeting #62bis, Warsaw, Poland, Jun. 30-Jul.4, 2008.
227 SDO Review Comment Form, SP-3-4617, 12-UGR (TIA-707-B.12) C.P0017.12-A (5 pgs.), Apr. 2004.
228 Second Chinese Office Action for Chinese Application No. 200710137906.8 dated Feb. 2, 2012 with translation (7 pages).
229 Summons to Attend Oral Proceedings for EP Application 08154976.8 dated Jan. 28, 2011 (10 pages).
230 Taiwan Office Action dated Aug. 30, 2012, issued in Taiwan Patent Application No. 096131703 (8 pages).
231 Taiwan Office Action dated Jul. 29, 2011, issued in Taiwan Application No. 095146891 (5 pages).
232 Taiwan Office Action dated May 20, 2013, issued in Taiwan Application No. 096131703 (19 pages).
233 U.S. Appl. No. 12/649,4612, filed Dec. 3, 2009, (87 pages).
234 U.S. Appl. No. 12/844,302, filed Jul. 27, 2010 (35 pages).
235 U.S. Appl. No. 12/897,945, filed Oct. 5, 2010 (144 pages).
236 U.S. Appl. No. 12/897,959, filed Oct. 5, 2010 (144 pages).
237 U.S. Appl. No. 12/953,049, filed Nov. 23, 2010 (146 pages).
238 U.S. Appl. No. 12/953,144, filed Nov. 23, 2010 (178 pages).
239 U.S. Appl. No. 12/953,223, filed Nov. 23, 2010 (146 pages).
240 U.S. Appl. No. 13/546,926, filed Jul. 11, 2012 (54 pages).
241 U.S. Appl. No. 13/673,398, filed Nov. 9, 2012 (42 pages).
242 U.S. Appl. No. 13/751,369, filed Jan. 28, 2013 (142 pages).
243 Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol specification (3GPP TS 25.331 version 10.5.0 Release 10), ETSI TS 125 331 (Nov. 2011), Sections 8.1.14.1 (p. 152), 8.1.14.2 (pp. 152-154), 8.2.2.2 (pp. 166-168), 8.2.2.3 (pp. 168-185), and 8.3.1.7 (pp. 235-239).
244 Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol Specification, 3GPP TS 25.331 V8.8.0 (Release 8) (Oct. 2009) Section 8.1.14 (pp. 141-143) and Sections 13.1 and 13.2 (pp. 1430-1432).
245 Vodafone, Rim; Huawei; Title: UE "Fast Dormancy" Behaviour; 3GPP TSG-RAN WG2 Meeting #60; R2-074848; Nov. 5-9, 2007, Jeju, South Korea (9 pgs.).
246 Vodafone, Rim; Huawei; Title: UE "Fast Dormancy" Behaviour; 3GPP TSG-RAN WG2 Meeting #60; R2-075251; Nov. 5-9, 2007, Jeju, South Korea (12 pgs.).
US9026153 25 Jun 2012 5 May 2015 Blackberry Limited Method and apparatus for state/mode transitioning
US9037167 19 Jun 2013 19 May 2015 Blackberry Limited Method and apparatus for state/mode transitioning
US9125208 10 Nov 2009 1 Sep 2015 Blackberry Limited Method and apparatus of transition to a battery efficient state or configuration by indicating end of data transmission in long term evolution
US9198132 17 Nov 2011 24 Nov 2015 Nec Corporation Mobile phone terminal and communication state transition method thereof
US20150201411 * 18 Jun 2014 16 Jul 2015 Qualcomm Incorporated Handling invalid configurations for enhanced uplink in cell_fach state
Clasificación de EE.UU. 455/509, 455/127.5
Clasificación internacional H04W52/02, H04B7/00
Clasificación cooperativa Y02B60/50, H04W76/046, H04W72/04, H04W84/042, H04W88/02, H04W52/0251, H04W76/048
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ISLAM, MUHAMMAD KHALEDUL;WIRTANEN, JEFFREY;REEL/FRAME:024747/0293