Source: http://www.google.com/patents/US7949377?dq=6,332,126
Timestamp: 2015-03-07 02:24:12
Document Index: 774114371

Matched Legal Cases: ['Application No. 2006252042', 'Application No. 2007202206', 'Application No. 2007202206', 'Application No. 200610064329', 'Application No. 200610064329', 'Application No. 06118909', 'Application No. 06118909', 'Application No. 08154976', 'Application No. 05112183', 'Application No. 05112183', 'Application No. 07121138', 'Application No. 05112183', 'Application No. 06118909', 'Application No. 08154976', 'Application No. 06118909', 'Application No. 07121138', 'Application No. 08154976', 'Application No. 08849315', 'Application No. 08849731', 'Application No. 10184515', 'Application No. 2006', 'Application No. 2006', 'Application No. 2007', 'Application No. 10', 'Application No. 10']

Patent US7949377 - Method and apparatus for user equipment directed radio resource control in a ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA 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.com/patents/US7949377?utm_source=gb-gplus-sharePatent US7949377 - Method and apparatus for user equipment directed radio resource control in a UMTS networkAdvanced Patent SearchPublication numberUS7949377 B2Publication typeGrantApplication numberUS 11/302,263Publication dateMay 24, 2011Filing dateDec 14, 2005Priority dateDec 14, 2005Fee statusPaidAlso published asCA2571101A1, CN101005659A, CN101005659B, CN102740502A, EP1798998A1, EP1798998B1, EP2247146A2, EP2247146A3, EP2247146B1, EP2262328A1, EP2262328B1, US8682372, US20070135080, US20110007682, US20140206369Publication number11302263, 302263, US 7949377 B2, US 7949377B2, US-B2-7949377, US7949377 B2, US7949377B2InventorsMuhammad Khaledul Islam, Jeffery WirtanenOriginal AssigneeResearch In Motion LimitedExport CitationBiBTeX, EndNote, RefManPatent Citations (87), Non-Patent Citations (87), Referenced by (6), Classifications (10), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetMethod and apparatus for user equipment directed radio resource control in a UMTS network
US 7949377 B2Abstract
1. A method for improving battery performance of a mobile user equipment used in a wireless network having multiple radio resource control (RRC) states, the user equipment capable of running a plurality of different applications, each of which is capable of exchanging data with the wireless network, the method comprising, at the user equipment:
receiving an indication of data exchange completion from each application, at the mobile user equipment, that exchanged data with the wireless network while in an RRC state or mode;
based on the data exchange completion indications received from each application that exchanged data in the RRC state or mode, determining when no application on the user equipment is expected to exchange data; and
initiating a transition from the RRC state or mode to another, less battery demanding RRC state or mode if a determination is made that no application on the user equipment is expected to exchange data.
2. The method of claim 1, wherein said initiating comprises tearing down a signaling connection setup between the user equipment and the wireless network.
3. The method of claim 2, wherein said tearing down causes the network to release a signaling connection between the user equipment and the wireless network.
4. The method of claim 1, wherein the wireless network is a UMTS network.
5. The method of claim 4, wherein the RRC state is a CELL_DCH state or a CELL_FACH state.
6. The method of claim 4, wherein the RRC state is a CELL_PCH state qr a URA_PCH state.
7. The method of claim 4, wherein said initiating includes sending a message to the wireless network requesting transition to the other, less battery demanding RRC state or mode.
8. The method of claim 1, wherein the other less battery demanding state or mode is a state selected from the group consisting of one of a CELL_FACH state, a CELL_PCH state, a URA_PCH state, or an idle mode.
9. The method of claim 1, wherein the user equipment includes an RRC connection manager, which performs said receiving, said determining and said initiating.
10. The method of claim 9, wherein said determining includes determining when no application on the user equipment is expected to exchange data based on a composite status of the data exchange completion indications received from any application that exchanged data in the RRC state or mode.
11. The method of claim 1 further comprising tracking each application of the plurality of different applications that exchanged data with the wireless network while in an RRC state or mode.
12. A user equipment adapted for reducing battery consumption in a wireless network, the user equipment having a radio subsystem including a radio adapted to communicate with the wireless 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 a plurality of applications each of which is capable of exchanging data with the wireless network, the user equipment comprising:
an RRC connection manager that is adapted and configured to: receive an indication of data exchange completion from each application, at the mobile user equipment, that exchanged data with the wireless network while in an RRC state or mode, and, based on the data exchange completion indications received from each application that exchanged data in the RRC state or mode, determine when no application on the user equipment is expected to exchange data; and initiate a transition from the RRC state or mode to another, less battery demanding state or mode if a determination is made that no application on the user equipment is expected to exchange data.
13. The user equipment of claim 12, wherein the RRC connection manager is adapted to tear down a signaling connection setup between the user equipment and the wireless network.
14. The user equipment of claim 13, wherein said RRC connection manager is adapted to determine when no application on the user equipment is expected to exchange data based on a composite status of the data exchange completion indications received from the applications that exchanged data in the RRC state or mode.
15. The user equipment of claim 13, wherein said RRC connection manager is adapted to determine when no application on the user equipment is expected to exchange data based on a delay to ensure that the applications that exchanged data in the RRC state or mode no longer require an RRC connection.
16. The user equipment of claim 13, wherein the RRC connection manager is adapted to cause the network to release a signaling connection between the user equipment and the wireless network by the tearing down of a signaling connection setup.
17. The user equipment of claim 12, wherein the RRC state or mode is a CELL_PCH state or a URA_PCH state.
18. The user equipment of claim 12, wherein the RRC connection manager is configured and arranged to send a message to the wireless network that requests a transition to the other, less battery-demanding RRC state or mode.
19. The user equipment of claim 18, wherein said other, less battery-demanding state or mode is one of a CELL_FACH state, a CELL_PCH state, a URA_PCH state, or an idle mode.
20. The user equipment of claim 19, wherein each of the plurality of different applications that exchanged data with the wireless network while in a RRC state or mode is an active application.
21. A method for improving battery performance of a mobile user equipment used in a wireless network having multiple radio resource control (RRC) states, the user equipment capable of running a plurality of different applications, each of which is capable of exchanging data with the wireless network, the method characterized by the steps of, at the user equipment:
receiving an indication of data exchange completion from each of the plurality of different applications that exchanged data with the wireless network while in an RRC state;
based on the data exchange completion indications received from the applications that exchanged data in the RRC state, determining when no application on the user equipment is expected to exchange data; and
initiating a transition from the RRC state to another, less battery demanding RRC state or mode if a determination is made that no application on the user equipment is expected to exchange data;
said user equipment including an RRC connection manager, which performs said receiving, determining and initiating steps,
wherein said determining step includes determining when no application on the user equipment is expected to exchange data based on a composite status of the data exchange completion indications received from the applications that exchanged data in the RRC state and, tracking associated Packet Data Protocol �PDP� contexts, packet switched �PS� radio access bearers, and PS radio bearers for said user equipment.
22. The method of claim 21, further comprising the step of blocking said initiating step if said RRC state is a URA_PCH state.
23. A method for improving battery performance of a mobile user equipment used in a wireless network having multiple radio resource control (RRC) states, the user equipment capable of running a plurality of different applications, each of which is capable of exchanging data with the wireless network, the method characterized by the steps of, at the user equipment:
initiating a transition from the RRC state to another, less battery demanding RRC state or mode if a determination is made that no application on the user equipment is expected to exchange data and upon a delay to ensure that the applications that exchanged data in the RRC state no longer require an RRC connection.
24. The method of claim 23, wherein the delay is a composite of a plurality of inactivity timeout periods, each inactivity timeout period corresponding to a respective application that exchanged data with the wireless network while in the RRC state or mode.
25. The method of claim 24, wherein said delay is dynamic based on traffic pattern history and/or application profiles.
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 detail in 3GPP specifications TS 25.304 and TS 25.331.
CELL DCH: A dedicated channel is allocated to the UE in uplink and downlink in this state to exchange data. The UE must perform actions as outlined in 3GPP 25.331. CELL_FACH: no dedicated channel is allocated to the user equipment in this state. Instead, common channels are used to exchange a small amount of bursty data. The UE must perform actions as outlined in 3GPP 25.331 which includes the cell selection process as defined in 3GPP TS 25.304. CELL_PCH: the UE uses Discontinuous Reception (DRX) to monitor broadcast messages and pages via a Paging Indicator Channel (PICH). No uplink activity. is possible. The UE must perform actions as outlined in 3GPP 25.331 which includes the cell selection process as defined in 3GPP TS 25.304. The UE must perform the CELL UPDATE procedure after cell reselection. URA_PCH: the UE uses Discontinuous Reception (DRX) to monitor broadcast messages and pages via a Paging Indicator Channel (PICH). No uplink activity is possible. The UE must perform actions as outlined in 3GPP 25.331 including the cell selection process as defined in 3GPP TS 25.304. This state is similar to CELL_PCH, except that the URA UPDATE procedure is only triggered via UTRAN Registration Area (URA) reselection. The transition from an idle to the connected mode and vise-versa is controlled by the UTRAN. When an idle mode UE requests an RRC connection, the network decides whether to move the UE to the CELL_DCH or CELL_FACH state. When the UE is in an RRC connected mode, again it is the network that decides when to release the RRC connection. The network may also move the UE from one RRC state to another prior to releasing the connection. The state transitions are typically triggered by data activity or inactivity between the UE and the network. Since the network may not know when the UE has completed data exchange, it typically keeps the RRC connection for some time in anticipation of more data to/from the UE. This is typically done to reduce the latency of call setup and radio bearer setup. The RRC connection release message can only be sent by the UTRAN. This message releases the signal link connection and all radio bearers between the UE and the UTRAN.
The problem with the above is that even if an application on the UE has completed its data transaction and is not expecting any further data exchange, it still waits for the network to move it to the correct state. The network may not be even aware of the fact that the application on the UE has completed its data exchange. For example, an application on the UE may use its own acknowledgement-based protocol to exchange data with its application server which is connected to the UMTS core network. Examples are applications that run over UDP/IP implementing-their own guaranteed delivery. In such a case, the UE knows whether the application server has sent or received all the data packets or not and is in a better position to determine if any further data exchange is to take place and hence decide when to terminate the RRC connection. Since the UTRAN controls when the RRC connected state is changed to a different, less battery-intensive state or into an idle mode, and the fact that UTRAN is not aware of the status of data delivery between the UE and external server, the UE is forced to stay in a higher data rate and intensive battery state than the required state or mode, thereby draining battery life and wasting network resources.
FIG. 5A is a block diagram of an exemplary transition between a CELL_DCH inactivity to a CELL_FACH inactivity to an idle mode initiated by the UTRAN according to the current method;
The present system and method overcome the deficiencies of the prior art by providing for the transitioning from an RRC connected mode to a more battery-efficient state or mode. In particular, the present method and apparatus 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 (PDP) 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 acknowledgment, 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 that 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 behaviour to this state.
The UE-initiated transition to idle mode can happen from any state of the RRC connected mode and ends up having the network release the RRC connection and moving to idle mode. The UE being in idle mode, as will be appreciated by those skilled in the art, is much less battery intensive than the UE being in a connected state.
The present application therefore provides a method for improved battery performance of user equipment in a wireless network having multiple radio resource control (RRC) states, 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.
The present application further 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.
As will be appreciated by those skilled in the art, a UMTS network consists of two land-based network segments. These are the Core Network (CN) and the Universal Terrestrial Radio-Access Network (UTRAN) (as illustrated in FIG. 8). The Core Network is responsible for the switching and routing of data calls and data connections to the external networks while the UTRAN handles all radio-related functionalities.
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 a Location Area Update.
Alternatively, the UTRAN can move from idle mode 110 to a CELL_FACH state 124. In a CELL_FACH 124, state no dedicated channel is allocated to the UE. Instead, common channels are used to send signaling in a small amount of bursty data. However, the UE still has to continuously monitor the FACH, and therefore it consumes battery power.
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 126. 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 states 126 will result in the RRC state moving back to idle mode 110.
In a second exemplary infrastructure, RRC transition can occur between an idle mode 110 and connected mode 120 depending on a payload threshold. In the second infrastructure, if the payload is below a certain threshold then the UTRAN moves the RRC state to CELL_FACH state 124. Conversely, if the data is above a certain payload threshold then the UTRAN moves the RRC state to CELL_DCH state 122. In the second infrastructure, if two minutes of inactivity are detected in CELL_DCH state 122, the UTRAN moves the RRC state to CELL_FACH state 124. After five minutes of inactivity in the CELL_FACH state 124, the UTRAN moves the RRC stage to CELL_PCH state 126. In CELL_PCH state 126, two hours of inactivity are required before moving back to idle mode 110.
In a third exemplary infrastructure, movement between idle mode 110 and connected mode 120 is always to CELL_DCH state 122. After five seconds of inactivity in CELL_DCH state 122 the UTRAN moves the RRC state to CELL_FACH state 124. Thirty seconds of inactivity in CELL_FACH state 124 result in the movement back to idle mode 110.
In a fourth exemplary infrastructure the RRC transitions from an idle mode 110 to a connected mode 120 directly into a CELL_DCH state 122. In the fourth exemplary infrastructure, CELL_DCH state 122 includes two sub-states. The first includes a sub-state which has a high data rate and a second sub-state includes a lower data rate, but still within the CELL_DCH state 122. In the fourth exemplary infrastructure, the RRC transitions from idle mode 110 directly into the high data rate CELL_DCH sub-state. After 10 seconds of inactivity the RRC state transitions to a low data rate CELL_DCH state 122. Seventeen seconds of inactivity from the low data CELL_DCH state 122 result in the RRC state changing it to idle mode 110.
The above four exemplary infrastructures show how various UMTS infrastructure vendors are implementing the states. As will be appreciated by those skilled in the art, in each case, if the time spent on exchanging actual data (such as an email) is significantly short compared to the time that is required to stay in the CELL_DCH or the CELL_FACH states 122, 124, this causes unnecessary current drain which makes user experience in newer generation networks such as UMTS worse than in prior generation networks such as GPRS.
Further, although the CELL_PCH state 126 is more optimal than the CELL_FACH state 124 from a battery life perspective, the DRX cycle in a CELL_PCH state 126 is typically set to a lower value than the idle mode 110. As a result, the UE is required to wake up more frequently in the CELL_PCH state 126 than in an idle mode.
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 battery life perspective.
Reference is now made to FIG. 3. When transitioning from an idle mode 110 to a connected mode 120, 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.
Although the current 3GPP specification does not allow the UE to release the RRC connection or indicate its preference for the RRC state, the UE can still indicate termination of a signaling connection for a specified core network domain such as the Packet Switched (PS) domain used by packet-switched applications. According to section 8.1.14.1 of 3GPP TS 25.33:
The signaling connection release indication procedure is used by the UE to indicate to the UTRAN that one of its signaling connections has been released. This procedure may in turn initiate the RRC connection release procedure. Thus staying within the current 3GPP specifications, signaling connection release may be initiated upon the tearing down of the signaling connection setup 312. It is within the ability of the UE to tear down signaling connection setup 312, and this in turn according to the specification �may� initiate the RRC connection release.
As will be appreciated by those skilled in the art, if signaling connection setup 312 is torn down, the UTRAN will also need to clean up ciphering and integrity setup 314 and radio bearer setup 316 after the signaling connection setup 312 has been torn down.
If signaling connection setup 312 is torn down, the RRC connection 310 setup is typically brought down by the network for current vendor infrastructures.
Using the above, if the UE determines that it is done with the exchange of data, for example if an �RRC connection manager� component of the UE software is provided with an indication that the exchange of data is complete, then the RRC connection manager may determine whether or not to tear down the signaling connection setup 312. For example, an email application on the device sends an indication that it has received an acknowledgement from the push email server that the email was indeed received by the push server. The RRC manager can keep track of all existing applications, associated PDP contexts, associated PS radio bearers and associated circuit switched (CS) radio bearers. A delay in this case can be introduced to ensure that the application is truly finished with data exchange and no longer requires an RRC connection even after it has sent the �done� indication. This delay is equivalent to inactivity timeout associated with the application. Each application can have its own inactivity timeout. For example, an email application can have an inactivity timeout of five seconds, whereas an active browser application can have a timeout of sixty seconds. Based on a composite status of all such indications from active applications, the UE software decides how long it should wait before it can initiate a signaling connection release of the appropriate core network (e.g. PS Domain).
The above UE-initiated transition to idle mode 110 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 that UTRAN 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 state 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 made to FIG. 4. FIG. 4A shows a current UMTS implementation according to the infrastructure �four� example above. As illustrated in FIG. 4, time is across the horizontal axes.
Next, signaling connection setup 312, ciphering and integrity setup 314, and radio bearer setup 316 occur. The RRC state is CELL_DCH state 122 during this. As illustrated in FIG. 4A, the time for moving from RRC idle to the time that the radio bearer is set up is approximately two seconds in this example.
Once the RRC connection is initiated in step 428, the RRC state proceeds to a disconnecting state 430 for approximately forty milliseconds, after which the UE is in an RRC idle state 110.
Reference is now made to FIG. 4B. FIG. 4B utilizes the same exemplary infrastructure �four� from above, only now implementing the signaling 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 during 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.
Reference is now made to FIG. 5. FIG. 5 shows a second example using the infrastructure indicated above as infrastructure �three�. As with FIGS. 4A and 4B, a connection setup occurs which takes approximately two seconds. This requires the RRC connection setup 310, the signaling connection setup 312, the ciphering and integrity setup 314 and the radio bearer setup 316.
During this setup, the UE moves from RRC idle mode 110 to a CELL_DCH state 122 with an RRC state connecting step 410 in between.
According to the infrastructure three, RLC signaling PDU exchange receives no data and thus is idle for a period of five seconds in step 422, except for intermittent RLC signaling PDU as required, at which point the radio bearer reconfigures the network to move into a CELL_FACH state 124 from CELL_DCH state 122. This is done in step 450.
In the CELL_FACH state 124, the RLC signaling PDU exchange finds that there is no data except for intermittent RLC signaling PDU as required for a predetermined amount of time, in this case thirty seconds, at which point an RRC connection release by the network is performed in step 428.
Reference is now made to FIG. 5B. FIG. 5B illustrates the same infrastructure �three� as FIG. 5A with the same connection time of about two seconds to get the RRC connection setup 310, signaling connection setup 312, ciphering and integrity setup 314 and radio bearer setup 316. Further, RLC data PDU exchange 420 takes approximately two to four seconds.
Network access requirements will also vary depending upon the type of network 1119. For example, In UMTS and GPRS networks, network access is associated with a subscriber or user of UE 1100. For example, a GPRS mobile device therefore requires a subscriber identity module (SIM) card in order to operate on a GPRS network. In UMTS a USIM or SIM module is required. In CDMA a RUIM card or module is required. These will be referred to as a UIM interface herein. Without a valid UIM interface, a mobile device may not be fully functional. Local or non-network communication functions, as well as legally required functions (if any) such as emergency calling, may be available, but mobile device 1100 will be unable to carry out any other functions involving communications over the network 1100. The UIM interface 1144 is normally similar to a card-slot into which a card can be inserted and ejected like a diskette or PCMCIA card. The UIM card can have approximately 64K of memory and hold many key configurations 1151, and other information 1153 such as identification, and subscriber-related information.
For voice communications, overall operation of UE 1100 is similar, except that received signals would preferably be output to a speaker 1134 and signals for transmission would be generated by a microphone 1136. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on UE 1100. Although voice or audio signal output is preferably accomplished primarily through the speaker 1134, display 1122 may also be used to provide an indication of the identity of a calling party, the duration of a voice call, or other voice call-related information for example.
Alternatively, serial port 1130 could be used for other communications, and could include a universal serial bus (USB) port. An interface is associated with serial port 1130.
Traffic between RNC 810 and MSC 830 uses the lu-CS interface 828. Iu-CS interface 828 is the circuit-switched connection for carrying (typically) voice traffic and signaling between UTRAN 820 and the core voice network. The main signaling protocol used is RANAP (Radio Access Network Application Part). The RANAP protocol is used in UMTS signaling between the Core Network 821, which can be a MSC 830 or SGSN 850 (defined in more detail below) and UTRAN 820. RANAP protocol is defined in 3GPP TS 25.413 V3.11.1 (2002-09) and TS 25.413 V5.7.0 (2004-01).
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. lu-PS 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).
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5812636Sep 6, 1996Sep 22, 1998Northern Telecom LimitedSystem and method for faulty mobile unit isolationUS6064340Jul 2, 1998May 16, 2000Intersil CorporationElectrostatic discharge locating apparatus and methodUS6229989 *Jul 7, 1998May 8, 2001Samsung Electronics Co., Ltd.Method of controlling power supplied to RF receiver and paging receiver employing the sameUS6243579Mar 27, 1997Jun 5, 2001Nokia Telecommunications OyControlling operating states of a mobile station in a packet radio systemUS6377790Mar 8, 1999Apr 23, 2002Sharp Laboratories Of America, Inc.Mobile-initiated, packet switched communications methodUS6654360Jan 10, 2000Nov 25, 2003Qualcomm IncorporatedMethod and system for providing dormant mode wireless packet data servicesUS6657984Oct 29, 1999Dec 2, 2003Samsung Electronics, Co., Ltd.System and method providing backward compatibility of radio link protocols in a wireless networkUS6661777Mar 29, 1999Dec 9, 2003AlcatelProcess for controlling uplink packet transmission in a wireless communication systemUS6668175Jul 14, 2000Dec 23, 2003Telefonaktiebolaget Lm Ericsson (Publ)Method and apparatus for providing radio access bearer servicesUS6845236Apr 19, 2001Jan 18, 2005Lg Electronics Inc.Method for concurrent multiple services in a mobile communication systemUS6847610Aug 28, 2000Jan 25, 2005Nokia Mobile Phones Ltd.Method for optimizing data transmission in a packet switched wireless data transmission systemUS6961570Jul 17, 2002Nov 1, 2005Asustek Computer Inc.Handling of a wireless device re-entering a service areaUS7130668 *Jun 30, 2004Oct 31, 2006Samsung Electronics Co., Ltd.Method and system for controlling sleep mode in broadband wireless access communication systemUS7155261May 1, 2003Dec 26, 2006Asustek Computer Inc.Method and apparatus for saving battery power in a mobile device using recovery mechanism for cell update procedure in CELL�DCH stateUS7353120Jan 24, 2006Apr 1, 2008Research In Motion LimitedElectrostatic discharge monitoring and manufacturing process control systemUS20010018342Feb 22, 2001Aug 30, 2001Jukka VialenMethod and arrangement for optimizing the re-establishment of connections in a cellular radio system supporting real time and non-real time communicationsUS20020077105Apr 19, 2001Jun 20, 2002Chang Woon SukMethod for concurrent multiple services in a mobile communication systemUS20020082020Jun 22, 2001Jun 27, 2002Samsung Electronics Co., Ltd.Apparatus and method for gating dedicated physical control 5 channel in a mobile communication systemUS20020141331Feb 16, 2001Oct 3, 2002Nokia Mobile Phones Ltd.Method and device for downlink packet switchingUS20030003895 *Apr 2, 2002Jan 2, 2003Telefonaktiebolaget Lm Ericsson (Publ).Authentication of termination messages in telecommunications systemUS20030014145May 1, 2002Jan 16, 2003Applied Materials, Inc.Integration of fault detection with run-to-run controlUS20030157927Feb 13, 2003Aug 21, 2003Lg Electronics Inc.Method for relocating SRNS in a mobile communication systemUS20030211846May 13, 2002Nov 13, 2003Vikas NagpalSelective processing of the common control channelUS20040120253Oct 31, 2003Jun 24, 2004Mika ForssellMethod and arrangement for transferring information in a packet radio serviceUS20040179490Mar 8, 2004Sep 16, 2004Nortel Networks LimitedMethod for mobile station request release of multiple packet data service sessions simultaneously using resource release request messagesUS20040203778Jul 17, 2002Oct 14, 2004Kuo Richard Lee-CheeHandling of a wireless device re-entering a service areaUS20040224688May 6, 2004Nov 11, 2004Evolium S.A.S.Method of setting up connections in a mobile radio systemUS20050026597Aug 2, 2004Feb 3, 2005Samsung Electronics Co., Ltd.Method for retransmitting a radio resource control connection request message in mobile communication system capable of providing a multimedia broadcast/multicast serviceUS20050141471Apr 20, 2004Jun 30, 2005Virtanen Terhi T.Method and system for controlling access bearer in a real-time data serviceUS20050143056Dec 2, 2004Jun 30, 2005Iyer Prakash R.Method and apparatus for providing push-to-talk services in a cellular communication systemUS20050153700Jan 9, 2004Jul 14, 2005Farnsworth Andrew J.Apparatus and method for implementing detection of system information changes in universal mobile telecommunications systemsUS20050185613Feb 1, 2005Aug 25, 2005Sharp Laboratories Of America, Inc.Method to negotiate consumed power versus medium occupancy time in MIMO based WLAN systems using admission controlUS20050237935Apr 19, 2005Oct 27, 2005Samsung Electronics Co., Ltd.System and method of efficiently providing packet data service in a UMTS systemUS20050266846Feb 25, 2005Dec 1, 2005Lg Electronics Inc.Method and apparatus for providing enhanced messages on common control channel in wireless communication systemUS20050281269Jun 17, 2005Dec 22, 2005Lg Electronics Inc.Mobile telecommunication system and method for session terminationUS20060036741Nov 5, 2004Feb 16, 2006Nokia CorporationMethod of managing a connection release, corresponding system and deviceUS20060089137Oct 27, 2004Apr 27, 2006Howell Stephen AMethod for reducing wireless communication procedure failureUS20060094478Nov 2, 2005May 4, 2006Lg Electronics Inc.Mobile power handling method and apparatusUS20060109846May 23, 2005May 25, 2006Marcello LioyMethod and apparatus for mitigating the impact of receiving unsolicited IP packets at a wireless deviceUS20060176167Jan 25, 2005Aug 10, 2006Laser Shield Systems, Inc.Apparatus, system, and method for alarm systemsUS20060182022Oct 1, 2004Aug 17, 2006Saied AbediVirtually centralized uplink schedulingUS20060223537Mar 9, 2006Oct 5, 2006Nec CorporationMobile communication system, relief method of competition between downlink RRC message and inter-cell movement of user equipment, and radio network controllerUS20060240823Apr 25, 2005Oct 26, 2006Research In Motion LimitedMethod and apparatus for CDMA timer-based registration on a mobile deviceUS20060293067 *Jun 27, 2005Dec 28, 2006Leung Kin KMethod and apparatus for controlling sleep intervals of a mobile unitUS20070135080Dec 14, 2005Jun 14, 2007Research In Motion LimitedMethod and apparatus for user equipment directed radio resource control in a UMTS networkUS20070270140Aug 14, 2006Nov 22, 2007Research In Motion LimitedMethod and system for signaling release cause indication in a umts networkUS20080039087Jul 14, 2007Feb 14, 2008Gallagher Michael DGeneric Access to the Iu InterfaceUS20080049662Aug 25, 2006Feb 28, 2008Research In Motion LimitedApparatus, and associated method, for releasing a data-service radio resource allocated to a data-service-capable mobile nodeUS20080123658Nov 28, 2006May 29, 2008Simo HyytiaMethod for the delivery of messages in a communication systemUS20080126554Nov 9, 2007May 29, 2008Koji SakaiCommunications device, communications method, communications circuit, communications system, computer program, and computer-readable storage medium containing the computer programUS20080212542Aug 6, 2007Sep 4, 2008Hsiang Tsung KungCommunication methods and devices for dual-mode communication systemsUS20080253312Apr 10, 2008Oct 16, 2008Samsung Electronics Co., Ltd.Method for transitioning radio resource control state of user equipment to idle state, system therefor, and the same user equipmentUS20080304510Jun 8, 2007Dec 11, 2008Hai QuMethod and apparatus for controlling radio connection based on inputs from applicationsUS20090042560Aug 20, 2008Feb 12, 2009Research In Motion LimitedMethod and system for a signaling connection release indicationUS20090124212Apr 22, 2008May 14, 2009Research In Motion LimitedMethod and apparatus for state/mode transitioningUS20090124249Nov 13, 2008May 14, 2009Research In Motion LimitedMethod and apparatus for state/mode transitioningUS20090129339Nov 13, 2008May 21, 2009Research In Motion LimitedMethod and apparatus for state/mode transitioningUS20100118752Nov 10, 2009May 13, 2010Research In Motion LimitedMethod and Apparatus of Transition to a Battery Efficient State or Configuration by Indicating End of Data Transmission in Long Term EvolutionEP0695069A2Jul 25, 1995Jan 31, 1996Sharp Kabushiki KaishaCommunication apparatus automatically selecting one of two operation modesEP1453286A1Dec 5, 2002Sep 1, 2004NTT DoCoMo, Inc.MOBILE COMMUNICATION TERMINAL&comma; METHOD FOR CONTROLLING EXECUTION STATE OF APPLICATION PROGRAM&comma; APPLICATION PROGRAM&comma; AND RECORDING MEDIUM WHEREIN APPLICATION PROGRAM HAS BEEN RECORDEDEP1511337A1Jul 23, 2004Mar 2, 2005Lucent Technologies Inc.A network for mobile communications, and a method of intermittent activation of receiving circuitry of a mobile user terminalEP1596616A1May 14, 2004Nov 16, 2005Research In Motion LimitedMethod and apparatus for expeditiously releasing network resources for a mobile station based on low battery and lost signal conditionsEP1608113A1Jun 16, 2005Dec 21, 2005LG Electronics Inc.Message transmission during packet service terminationEP1798998A1Dec 14, 2005Jun 20, 2007Research In Motion LimitedMethod and apparatus for user equipment directed radio resource control in a UMTS networkEP1858209A1Aug 14, 2006Nov 21, 2007Research In Motion LimitedMethod and system for signaling release cause indication in a UMTS networkEP1892895A1Aug 25, 2006Feb 27, 2008Research In Motion LimitedApparatus, and associated method, for releasing a data service radio resource allocated to a data service capable mobile nodeEP1981224A1Mar 31, 2008Oct 15, 2008Samsung Electronics Co., Ltd.Transitioning radio resource control state of user equipment to idle stateEP2061192A1Apr 22, 2008May 20, 2009Research In Motion LimitedMethod and apparatus for state/mode transitioningEP2244499A2Apr 21, 2010Oct 27, 2010HTC CorporationRelay for handling data forwarding in a wireless communication system and related method for controlling the sameEP2271168A1Nov 20, 2007Jan 5, 2011Research In Motion LimitedMethod and system for a signaling connection release indicationJP2000261372A Title not availableJPH0955764A Title not availableWO2000062435A1Apr 12, 2000Oct 19, 2000Samsung Electronics Co LtdMethod for controlling gated transmission of dedicated channel in w-cdma communication systemWO2000062449A1Apr 3, 2000Oct 19, 2000Tantivy Comm IncSystem and method for efficient data transmission on wireless access to a networkWO2001052574A1Jan 9, 2001Jul 19, 2001Qualcomm IncMethod and wireless system for terminating a dormant mode in a packet data sessionWO2002033853A1Oct 9, 2001Apr 25, 2002Motorola IncLow-powered communication system and method of operationWO2004032391A1Sep 23, 2003Apr 15, 2004Motorola IncMethod and apparatus for managing the usage of data link resourcesWO2004056142A1Mar 24, 2003Jul 1, 2004Research In Motion LtdMethods and apparatus for reducing power consumption in cdma communication deviceWO2004179542A2 Title not availableWO2005029813A1Sep 16, 2004Mar 31, 2005Cisco Tech IndTtl exploration technique for determining capabilities and configuration of a peer routerWO2005050917A2Nov 19, 2004Jun 2, 2005Nokia CorpControlling network resources after determination of a flow terminationWO2005064962A1Dec 22, 2004Jul 14, 2005Nokia CorpMethod and system for controlling a real-time communications serviceWO2005120104A1Apr 25, 2005Dec 15, 2005Motorola IncConcurrent packet data session set-up for push-to-talk over cellularWO2007073118A1Dec 22, 2006Jun 28, 2007Korea Electronics TelecommMethod and apparatus for discontinuous transmission/reception operation for reducing power consumption in cellular systemWO2007097670A1Feb 27, 2006Aug 30, 2007Hannes EkstroemMethod and apparatus for communicationWO2009062302A1Nov 13, 2008May 22, 2009Research In Motion LtdMethod and apparatus for state/mode transitioningWO2009104086A1Feb 20, 2009Aug 27, 2009Nokia CorporationMobile equipment autonomous quick release detection* Cited by examinerNon-Patent CitationsReference1"3rd Generation Partnership Project 2; Data Service Options for Spread Spectrum Systems," 3GPP2 C.S0017-0, Version 5.0, Feb. 17, 2003 (70 pgs.).2"3rd Generation Partnership Project 2; Data Service Options for Spread Spectrum Systems: Introduction and Service Guide," 3GPP2 C.S0017-001-A, Version 1.0, Jun. 11, 2004 (22 pgs.).3"3rd Generation Partnership Project 2; Data Service Options for Spread Spectrum Systems: Radio Link Protocol Type 3," 3GPP2 C.S0017-010-A, Version 2.0, Sep. 2005 (56 pgs.).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; 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.).13"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.).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.7.0 (Sep. 2009) (234 pgs.).15"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.).16"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.).17"Digital Cellular Telecommunications System (Phase 2+)"; ETSI Standards European Telecommunications Standards Institute, Sophia-Antipo, FR, vol. 3-SA2, No. V6110, Dec. 2005, XP014032437.183GPP Radio Resource Control Protocal for the UE-UTRAN Radio Interface, 3GPP TS 25.331 V6.8.0 (Dec. 2005) (1,174 pgs.).193GPP TS 25.331 V5.16.0 (Mar. 2006) (1045 pgs.).203GPP TSG-RAN WG2 Meeting #69; R2101726; San Francisco, CA, Feb. 22-26, 2010 (6 pages).213GPP TSG-RAN WG2#67bis; R2-096027; Miyazaki, Japan, Oct. 12-16, 2009 (4 pages).223GPP TSG-RAN WG2#68; R2096624; Jeju, South Korea, Nov. 9-13, 2009 (8 pages).233GPP TSG-RAN2 Meeting #67; R2-094792; Shenzhen, China, Aug. 24-28, 2009 (10 pages).243GPP TSG-RAN2 Meeting #69; r2101440; San Francisco, CA, Feb. 22-26, 2010 (18 pages).253GPP TSG-RAN2 Meeting #69; R2101441; San Francisco, CA, Feb. 22-26, 2010 (20 pages).263GPP: "Radio resource control (RRC) protocol specification V7.0.0," 3GPP TS 25.331 V7.0.0, (1,249 pgs.).273rd Generation Partnership Project 2 "3GPP2", "Data Service Options for Spread Spectrum Systems: Service Options 33 and 66", 3GPP2 C.S0017-012-A, version 1.0, Jun. 11, 2004.283rd 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.29Australian First Report for AU Application No. 2006252042, dated Apr. 9, 2008, (this reference relates to U.S. Appl. No. 11/302,263) (2 pgs.).30Australian First Report for AU Application No. 2007202206, dated Sep. 2, 2008, (this reference relates to U.S. Appl. No. 11/464,380) (7 pgs.).31Australian Second Report for AU Application No. 2007202206, dated Sep. 30, 2009, (this reference relates to U.S. Appl. No. 11/464,380) (1 pg.).32Canadian 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.).33Canadian Office Action for Canadian Application 2,589,373 dated Feb. 22, 2011 (5 pages).34Chairman: Title LTE CP Session Report; 3GPP TSG RAN WG2 #63bis; R2-085921; Prague, Czech Republic; Sep. 29-Oct. 3, 2008 (38 pgs.).35Chinese 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.).36Chinese 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.).37Communication 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.).38Communication 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.).39EP Application No. 08154976.8, Communication pursuant to Article 94(3) EPC, dated Oct. 8, 2009.40EP Communication for EP Application 07121138.7 dated Oct. 19, 2010.41EP Communication for EP Application No. 05112183.8, dated Jan. 24, 2008 (2 pgs.).42EP Communication for EP Application No. 05112183.8, dated Sep. 7, 2009 (3 pgs.).43EP Examination Report for EP Application No. 07121138.7-2412 dated Sep. 7, 2009 (1 page).44EP Extended Search Report for EP Application 06119590.5 dated Mar. 20, 2007.45EP Extended Search Report for EP Application 10184515.4 dated Nov. 19, 2010.46EP Search Report for EP Application 06119590.5 dated Oct. 25, 2007.47EP Search Report for EP Application 10183886.0 dated Nov. 15, 2010.48EP Search Report for EP Application No. 05112183.8, dated May 3, 2007 (7 pgs.).49European 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.).50Extended European Search Report for Application No. 08154976.8, dated Sep. 3, 2008.51Extended European Search Report for EP 09180936.8, dated May 20, 2010 (9 pgs.).52Extended European Search Report for EP 10170815.4 dated Nov. 2, 2010.53Extended 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.).54Extended 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.).55Extended European Search Report for EP Application No. 08154976.8 dated Sep. 3, 2008.56Extended European Search Report for EP Application No. 08849315.0 dated Jan. 18, 2011 (8 pages).57Extended European Search Report for EP Application No. 08849731.8 dated Jan. 18, 2011 (7 pages).58Extended 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).59International Application No. PCT/US2009/063912, Communication Relating to the Results of the Partial International Search dated Feb 17, 2010.60Japanese 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.).61Japanese 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.).62JP Office Action for JP Application No. 2007-131146, dated Sep. 30, 2010 (7 pgs.).63Korean 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) (4pgs.).64Korean 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. 11/302,263) (8 pgs.).65Nokia 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, 18th-22nd Aug. 2008.66Office Action for U.S. Appl. No. 11/464,380 dated Dec. 22, 2010.67Office Action for U.S. Appl. No. 12/270,562 dated Nov. 18, 2010.68Office Action for. U.S. Appl. No. 12/196,018 dated Jan. 5, 2011.69PCT International Search Report for Application PCT/US2009/063912 dated May 3, 2010 (6 pages).70PCT Search Report and Written Opinion for PCT Application No. PCT/EP2010/064859 dated Feb. 9, 2011 (17 pages).71PCT Search Report and Written Opinion for PCT Application No. PCT/EP2010/068065 dated Feb. 11, 2011 (17 pages).72PCT Search Report for Application No. PCT/US2009/063912 dated Feb. 17, 2010.73PCT Search Report for PCT/CA2007/001497 dated Dec. 18, 2008.74PCT Written Opinion and Search Report for PCT/US2009/063912 dated Apr. 13, 2010.75PCT Written Opinion for PCT Application PCT/US2009/063912 dated May 3, 2010 (22 page).76PCT Written Opinion for PCT/CA2007/001497 dated Dec. 12, 2007.77PCT/CA2008/002000 International Search Report and Written Opinion dated Feb. 13, 2009.78PCT/CA2008/002001 International Search Report and Written Opinion dated Feb. 2, 2009.79PCT/CA2008/002002 International Search Report and Written Opinion dated Jan. 15, 2009.80Qualcomm 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.).81Research 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.).82Research 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.83SDO Review Comment Form, SP-3-4617, 12-UGR (TIA-707-B.12) C.P0017.12-A (5 pgs.).84U.S. Appl. No. 12/649,461 filed Dec. 3, 2009 (87 pages).85U.S. Appl. No. 12/844,302, filed Jul. 27, 2010 (35 pgs.).86Vodafone, Rim; Huawei; Title: UE "Fast Dormancy" Behaviour; 3GPP TSG-RAN WG2 Meeting #60; R2-074848; Nov. 5-9, 2007, Jeju, South Korea (9 pgs.).87Vodafone, Rim; Huawei; Title: UE "Fast Dormancy" Behaviour; 3GPP TSG-RAN WG2 Meeting #60; R2-075251; Nov. 5-9, 2007, Jeju, South Korea (12 pgs.).Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8644829Aug 14, 2006Feb 4, 2014Blackberry LimitedMethod and system for signaling release cause indication in a UMTS networkUS8682372Jul 27, 2010Mar 25, 2014Blackberry LimitedMethod and apparatus for user equipment directed radio resource control in a UMTS networkUS8885607Aug 13, 2012Nov 11, 2014Blackberry LimitedMethod and apparatus for state/mode transitioningUS8909306Aug 6, 2012Dec 9, 2014Qualcomm Innovation Center, Inc.Method to conserve power on a wireless mobile device using web browser state knowledgeUS20100118752 *Nov 10, 2009May 13, 2010Research In Motion LimitedMethod and Apparatus of Transition to a Battery Efficient State or Configuration by Indicating End of Data Transmission in Long Term EvolutionUS20140199979 *Jan 11, 2013Jul 17, 2014Qualcomm IncorporatedApplication driven fast dormancy* Cited by examinerClassifications U.S. Classification455/574, 455/154.1International ClassificationH04B1/00, H04W52/02Cooperative ClassificationH04W72/04, H04W76/048, H04W52/0251, H04W76/046European ClassificationH04W52/02T6, H04W76/04RLegal EventsDateCodeEventDescriptionNov 24, 2014FPAYFee paymentYear of fee payment: 4Oct 14, 2014ASAssignmentOwner name: BLACKBERRY LIMITED, ONTARIOEffective date: 20130709Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:033987/0576Mar 6, 2012CCCertificate of correctionDec 14, 2005ASAssignmentOwner name: RESEARCH IN MOTION LIMITED, CANADAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ISLAM, MUHAMMAD KHALEDUL;WIRTANEN, JEFFERY;REEL/FRAME:017363/0454Effective date: 20051214RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services