Patent Grant
9456436
The present disclosure relates to radio resource control between User Equipment (UE) or other wireless or mobile device and a wireless network, and in particular to transitioning between states and modes of operation in a wireless network such as for example, a Universal Mobile Telecommunication System (UMTS) network.
A Universal Mobile Telecommunication System (UMTS) is a broadband, packet-based system for the transmission of text, digitized voice, video and multi-media. It is a highly subscribed to standard for third generation and is generally based on Wideband Coded Division Multiple Access (W-CDMA).
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 RRC connected mode” (or simply “connected mode,” as used herein). UTRA stands for UMTS Terrestrial Radio Access. In idle mode, the UE or other mobile device 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 General Packet Radio Service (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 the Third Generation Partnership Project (3GPP) specifications TS 25.304 and TS 25.331.
When in a UTRA RRC connected mode, the device can be in one of four states. These are:
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 mode to the connected mode and vice-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 or in some cases instead of releasing the connection. The state transitions are typically triggered by data activity or inactivity between the UE and network. Since the network may not know when the UE has completed the data exchange for a given application, 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 subsequent radio resource setup. The RRC connection release message can only be sent by the UTRAN. This message releases the signal link connection and all radio resources between the UE and the UTRAN. Generally, the term “radio bearer” refers to radio resources assigned between the UE and the UTRAN. And, the term “radio access bearer” generally refers to radio resources assigned between the UE and, e.g., an SGSN (Serving GPRS Service Node). The present disclosure shall, at times, refer to the term radio resource, and such term shall refer, as appropriate, to either or both the radio bearer and/or the radio access bearer.
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 accessed through the UMTS core network. Examples are applications that run over User Datagram Protocol/Internet Protocol (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 associated with Packet Service (PS) domain. Since the UTRAN controls when the RRC connected state is changed to a different state or into an idle mode and the UTRAN is not aware of the status of data delivery between the UE and external server, the UE may be forced to stay in a higher data rate state or mode than what is required, possibly resulting in decreased battery life for the mobile station and also possibly resulting in wasted network resources due to the fact that the radio resources are unnecessarily being kept occupied and are thus not available for another user.
One solution to the above is to have the UE send a signaling release indication to the UTRAN when the UE realizes that it is finished with a data transaction. Pursuant to Section 8.1.14.3 of the 3GPP TS 25.331 specification, the UTRAN may release the signaling connection upon receipt of the signaling release indication from the UE, causing the UE to transition to an idle mode or some other RRC state. A problem with the above solution is that the UTRAN might become inundated with signaling release indication messages from the UE and other UEs
The present disclosure will be better understood with reference to the drawings in which:
The examples and embodiments provided below describe various methods and systems for transitioning a User Equipment (UE) or other mobile device between various states/modes of operation in a wireless network such as, for example, a UMTS network. It is to be understood that other implementations in other types of networks are also possible. For example, the same teachings could also be applied to a Code-Division-Multiple-Access (CDMA) network (e.g. 3GPP2 IS-2000), Wideband-CDMA (W-CDMA) network (e.g. 3GPP UMTS/High-Speed Packet Access (HSPA)) network, an Evolved UTRAN network (e.g. LTE), or by way of generalization, to any network based on radio access technologies that utilize network-controlled radio resources or that does not maintain any knowledge of the status of device application level data exchanges. The specific examples and implementations described below although presented for simplicity in relation to UMTS networks are also applicable to these other network environments. Further, the network element is sometimes described below as the UTRAN. However, if other network types besides UMTS are utilized, the network element can be selected appropriately based on the network type. Further, the network element can be the core network in a UMTS system or any other appropriate network system, where the network element is the entity that makes transition decisions.
In a particular example, the present system and method provide for the transitioning from an RRC connected mode to a more battery efficient or radio resource efficient state or mode while providing for decision making capabilities at the network. In particular, the present method and apparatus provide for transitioning based on receipt of an indication from a UE indicating, either implicitly or explicitly, that a transition of the RRC state or mode associated with a particular signaling connection with radio resources to another state or mode should occur. As will be appreciated, such a transition indication or request could utilize an existing communication under current standards, for example a SIGNALING CONNECTION RELEASE INDICATION message, or could be a new dedicated message to change the state of the UE, such as a “preferred RRC state request” or a “data transfer complete indication message.” A data transfer complete indication message is a message which indicates the completion of higher layer data transfer. As used herein, an indication could refer to either scenario, and could incorporate a request.
The transition indication originated by the UE can be sent in some situations when one or more applications on the UE have completed an exchange of data and/or when a determination is made that the UE application(s) are not expected to exchange any further data. The network element can then use the indication and any information provided therein, as well as other information related to the radio resource, such a quality of service, Access Point Name (APN), Packet Data Protocol (PDP) context, historical information, among others, defined herein as a radio resource profile, to make a network specific decision about whether to transition the mobile device to another mode or state, or do nothing. The transition indication provided by the UE or mobile device can take several forms and can be sent under different conditions. In a first example, the transition indication can be sent based on a composite status of all of the applications residing on the UE. Specifically, in a UMTS environment, if an application on the UE determines that it is done with the exchange of data, it can send a “done” indication to a “connection manager” component of UE software. The connection manager can, in one embodiment, keep 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 resources and associated circuit switched (CS) radio resources. 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 (for 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 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. The browser application may behave differently and instead make a predictive determination (e.g. using an inactivity timer) of when to send a “done” indication to the connection manager.
Based on a composite status of such indications from active applications, UE software can decide to send a transition indication to indicate or request of the network that a transition from one state or mode to another should occur. Alternatively, the UE software can instead wait before it sends the transition indication and introduce a delay to ensure that the application is truly finished with data exchange and does not require to be maintained in a battery or radio resource intensive state or mode. The delay can be dynamic based on traffic history and/or application profiles. Whenever the connection manager determines with some probability that no application is expected to exchange data, it can send a transition indication to the network to indicate that a transition should occur. In a specific example, the transition indication can be a signaling connection release indication for the appropriate domain (e.g. PS domain) to request a transition to an idle mode. Alternatively, the transition indication could be a request for state transition within connected mode to the UTRAN.
As described below in further detail, based on the receipt of a transition indication and optionally a radio resource profile, a network element such as the UTRAN in a UMTS environment can decide to transition the UE from one state or mode to another.
Other transition indications are possible. For example, instead of relying on a composite status of all active applications on the UE, the UE software can, in an alternative embodiment, send a transition indication every time a UE application has completed an exchange of data and/or the application is not expected to exchange further data. In this case, the network element (e.g. the UTRAN), based on an optional radio resource profile for the UE as described with reference to
In yet another example, the transition indication could simply indicate that one or more applications on the UE completed a data exchange and/or that the UE application(s) are not expected to exchange any further data. Based on that indication and an optional radio resource profile for the UE, the network (e.g. UTRAN), can decide whether or not to transition the UE to a more appropriate state or mode or operation.
In a further example, the transition indication could be implicit rather than explicit. For example, the indication may be part of a status report sent periodically. Such a status report could include information such as whether a radio link buffer has data or could include information on outbound traffic.
When the UE sends a transition indication it may include additional information in order to assist the network element in making a decision to act on the indication. This additional information would include the reason or cause for the UE to send the message. This cause or reason (explained below in greater detail) would be based on the UE determining a need for “fast dormancy” like behavior. Such additional information may be by way of a new information element or a new parameter within the transition indication message.
In a further embodiment, a timer could exist on the UE to ensure that a transition indication may not be sent until a time duration has elapsed (inhibit duration) since a previous transition indication was sent. This inhibit timer restricts the UE from sending the transition indication message too frequently and further allows the network to make a determination by relying on messages that are triggered only with a given maximum frequency. The time duration could be determined by a timer whose value is preconfigured, or set by a network (indicated or signaled). If the value is set by a network, it could be conveyed in new or existing messages such as RRC Connection Request, RRC Connection release, Radio Bearer Setup, UTRAN Mobility Information or a System Information Block, among others, and could be an information element in those messages. The value could alternatively be conveyed in an inhibit transition indication portion of an RRC connection setup message sent by the UTRAN in response to an RRC connection request message received from the UE, for example.
In an alternative embodiment, the value could be conveyed to a UE in a message whose type depends on a state of the UE. For example, the network could send the value to all the UEs in a cell as a portion of a system information message which is read by the UE when it is in an IDLE, URA_PCH, CELL_PCH or CELL_FACH state.
In yet another embodiment, the value could be sent as a portion of an RRC connection setup message.
Network generated messages may also convey an implied inhibit timer value through non-inclusion of an inhibit timer in the message or in an information element within the message. For example, upon determining that an inhibit timer is omitted from a received message, a UE applies a pre-determined value for use as an inhibit timer value. One exemplary use of inhibit timer value omission is to prohibit the UE from sending a transition indication message. In such a situation, when a UE detects the omission of an expected inhibit timer value in a received message, the UE may, based on the omission, be prohibited from sending any transition indication messages. One way to achieve this is for the UE to adopt an inhibit timer value of infinity.
In another embodiment when the UE detects the omission of an inhibit timer value (and for example, adopts an inhibit timer value of infinity), it may send transition indications but without including any additional information, specifically it may omit the cause for triggering the sending of the transition indication (further described below in greater detail). The omission of a cause element in a transition indication message may ensure backward-compatibility by allowing UEs to use an existing transition indication message (e.g. SIGNALING CONNECTION RELEASE INDICATION) to request or indicate a transition.
Non-inclusion of an inhibit timer in the received message is further detailed with reference to an exemplary embodiment wherein a System Information Block is broadcast in a cell, or sent to a UE and the System Information Block is configured to convey an inhibit timer value. In this embodiment, if the UE receives a System Information Block which does not contain an inhibit timer, known as T3xx, in the message or an information element within the message, in which case the UE may determine to not enable the UE to send the transition indication message, for example by setting the inhibit timer, T3xx, to infinity.
Non-inclusion of an inhibit timer is further detailed with reference to another exemplary embodiment wherein an inhibit timer, T3xx, is omitted from a UTRAN Mobility Information message. In such a situation a recipient UE may continue to apply a previous stored inhibit timer value. Alternatively, the UE, on detecting the omission of the inhibit timer T3xx, may determine to not enable the UE to send the transition indication message, for example by setting the inhibit timer, T3xx, to infinity.
In yet another exemplary embodiment, a UE, on detecting the omission of an inhibit timer in the received message or in an information element within the message, sets the inhibit timer value to another preset value (e.g. one of 0 seconds, 5 seconds, 10 seconds, 15 seconds, 20 seconds, 30 seconds, 1 minute, 1 minute 30 seconds, 2 minutes). Alternatively or in addition, these examples may apply to other network generated messages.
In other embodiments, if the inhibit timer (value) is not sent or signaled to the UE in a message or information element, or the inhibit timer is not read from broadcast system information or received from other dedicated UTRAN messages on transitioning from one cell to another, the sending of a transition indication may or may not occur.
Specifically in one embodiment the UE on detecting that there is no inhibit timer present, does not initiate a transition indication based on a higher layer determining that it has no more PS data to transmit.
In an alternative embodiment the UE on detecting that there is no inhibit timer present, may initiate a transition indication based on the higher layer determining that it has no more PS data to transmit.
In yet another embodiment, if no timer value is received from the UTRAN within a message, or within an information element in a message (via broadcasting or otherwise), rather than setting the timer value at the UE to infinity the UE may set the inhibit timer to zero or alternatively delete any configuration for the timer, and instead be permitted to send a transition indication. In this case, the UE could omit or be prohibited from attaching a cause in the transition indication message. In one embodiment a SIGNALING CONNECTION RELEASE INDICATION message is used as one example of a transition indication.
In an embodiment the transition indication is conveyed using the signaling connection release indication procedure. 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.
Specifically in accordance with TS 25.331 Section 8.1.14.2 the UE shall, on receiving a request to release the signaling connection from the upper layers for a specific CN domain, check if the signaling connection in the variable “ESTABLISHED_SIGNALLING_CONNECTIONS” for the specific CN domain identified in the information element “CN domain identity” exists. If it does, the UE may initiate the signaling connection release indication procedure.
In the case of the inhibit timer value not being signaled or otherwise conveyed to the UE, no signaling connection release indication cause is specified in the SIGNALING CONNECTION RELEASE INDICATION message. Those skilled in the art will appreciate that in this alternative embodiment the lack of a timer value does not result in the timer value being set to infinity.
On the UTRAN side, upon receipt of a SIGNALING CONNECTION RELEASE INDICATION message without a cause, the UTRAN indicates the release of the signaling connection for the identified CN domain identity to the upper layers. This may then initiate the release of the established radio resource control connection.
Under another alternative embodiment, when the UTRAN signals or conveys a timer value to the UE, for example, inhibit timer T3xx in information element “UE timers and constants in connected mode” (or using system information, such as SIB1, SIB3 or SIB4, or with a dedicated UTRAN mobility information message), the release procedure occurs in accordance with the following. First, the UE can check whether there are any circuit switched domain connections indicated. Such connections may be indicated in the variable “ESTABLISHED_SIGNALLING_CONNECTIONS.” If there are no circuit switched domain connections, a second check to determine whether an upper layer indicates that there will be no packet switched domain data for a prolonged period could occur.
If there are no circuit switched domain connections and no packet switched domain data is expected for a prolonged period, the UE may next check whether the timer T3xx is running.
If the timer T3xx is not running, the UE sets information element “CN Domain Identity” to the packet switched (PS) domain. Further, the information element “Signaling Connection Release Indication Cause” is set to “UE requested PS data session end.” The SIGNALING CONNECTION RELEASE INDICATION message is transmitted on the DCCH using AM RLC. Further, after the transmission the timer T3xx is started.
The procedure above ends on successful delivery of the SIGNALING CONNECTION RELEASE INDICATION message, as confirmed by the RLC in the above procedure. In this embodiment, the UE is inhibited from sending the SIGNALING CONNECTION RELEASE INDICATION message with a signaling connection release indication cause set to “UE Requested PS data session end” while the timer T3xx is running or until the timer T3xx has expired.
When the T3xx timer is running, if the signaling connection release indication procedure is initiated due to no further packet switched domain data for a prolonged duration, the UE is responsible for implementing whether to initiate the procedure on the expiry of the T3xx timer. The UE decision may be based on determining whether it has any subsequent signaling connection release indication or request messages to send and if so, the UE decision may include re-checking some or all of the same checks for initiating the procedure as outlined herein.
On the UTRAN side, if the SIGNALING CONNECTION RELEASE INDICATION message received does not include a signaling connection release indication cause, the UTRAN may request the release of the signaling connection from an upper layer and the upper layer may then initiate the release of the signaling connection. If on the other hand the SIGNALING CONNECTION RELEASE INDICATION message received includes a cause, the UTRAN may either release the signaling connection or initiate a state transition to a more battery efficient state (e.g. CELL_FACH, CELL_PCH, URA_PCH or IDLE_MODE).
The inhibit duration above may be based on the state the UE would like to transition to. For example the inhibit duration may be different, whether the mobile indicated its last preference for some RRC States/modes versus others. For example, it could be different if the mobile indicated a preference for idle mode, versus CELL_FACH, or versus CELL_PCH/URA_PCH states. In the case where the Inhibit Duration is set by the network, this may be achieved by the network indicating/sending two (or more) sets of values to the mobile, to be used depending on the scenario. Alternatively, the indication could be done in such a way that the appropriate Inhibit duration value only is indicated/signaled to the mobile: for example, if the UE wants to transition to CELL_PCH, a different elapsed time duration could be set than if the UE wants to transition to Idle.
The inhibit duration from above may be different, depending on which RRC State/mode the mobile currently is in (e.g. CELL_DCH/CELL_FACH versus CELL_PCH/URA_PCH, or in CELL_DCH versus CELL_FACH, or CELL_PCH/URA_PCH).
The inhibit duration from above may be different, depending if the network has already acted on preference RRC State information from the mobile. Such recognition may happen on the network, or on the mobile side. In the first case, this may affect the inhibit values indicated/signaled by the network to the mobile. In this second case, different sets of inhibit duration values may be preconfigured or indicated/signaled by the network. As a particular case, the inhibit duration/functionality may be reduced or cancelled if the network has acted on preference RRC State information from the mobile, e.g. has initiated a state transition to a state indicated by the UE.
The inhibit duration from above may be different, depending on, for example, preferences, features, capabilities, loads or capacities of the network. A network may indicate a short Inhibit duration if it is able to receive frequent transition indication messages. A network may indicate a long Inhibit duration if it is unable or does not want to receive frequent transition indication messages. A network may indicate a specific period of time during which a UE cannot send transition indication messages. The specific period of time can be indicated numerically (i.e. 0 seconds, 30 seconds, 1 minute, 1 minute 30 seconds, 2 minutes or infinity) for example. A UE which receives an inhibit duration of 0 seconds is able to send transition indications without delay. A UE which receives an inhibit duration of infinity is unable to send transition indications.
A maximum number of messages per time-window (e.g. “no more than 15 messages every 10 minutes”) may be used/specified instead of, or in addition to, the Inhibit duration.
Combinations of the above inhibition durations/maximum messages per time-window are possible.
By way of example, the present disclosure generally describes the reception of an RRC CONNECTION REQUEST message by a UTRAN from a UE. Upon receiving an RRC CONNECTION REQUEST message, the UTRAN should, for example, accept the request and send an RRC CONNECTION SETUP message to the UE. The RRC CONNECTION SETUP message may include an Inhibit Transition Indication, which is known as Timer T3xx. Upon reception of the RRC CONNECTION SETUP message by the UE, the UE should, for example, store the value of the Timer T3xx, replacing any previously stored value, or, if the Timer T3xx is not in the RRC CONNECTION SETUP message, set the value of the timer to infinity. In some embodiments, the RRC CONNECTION SETUP message must include an Inhibit Transition Indication to ensure that the UE knows that the UTRAN supports the Inhibit Transition Indication signaling.
In an embodiment it is assumed that during mobility in a DCH state, the UE will maintain its currently stored value for the inhibit timer. In some cases where the inhibit timer is set to infinity this may mean that the UE must wait for network data inactivity timers to expire and for the network to move the UE to an RRC state where it can receive or determine a new value for the inhibit timer. In other cases where the inhibit timer is some value other than infinity before the handover, this other value is continued to be used until the UE is able to update the timer value to that indicated in the new cell.
In some instances the inhibit timer and the transition indication (e.g. SIGNALING CONNECTION RELEASE INDICATION) message may not be implemented in some networks or in some cells within a network. For mobility purposes, if there is no support available for the feature of sending a transition indication or request message (particularly in the case where a cause is used), the UE should default to not sending the message. This avoids unnecessary transmissions and the associated waste of network resources and battery resources.
In addition, for mobility purposes, different vendor's network equipment used within a network may lead to adjacent cells using different inhibit timers which need to be updated on the UE when the UE moves between cells.
In one alternative embodiment this is handled by providing that all handover and related bearer control messages include a value for an inhibit timer T3xx. Such messages are referred to herein as mobility messages. This allows the UE to receive new inhibit timer values when moving between cells. It also allows the UE to set a default timer value for the inhibit timer if one of these mobility messages does not contain an inhibit timer value. As will be appreciated, if no inhibit timer value is received in the mobility messages, this indicates that the cell is not enabled for fast dormancy.
As another example of a transition indication procedure, a Data Transfer Complete Indication procedure may be used by the UE to indicate to the UTRAN that it has determined that it does not need to transfer any more PS domain data. In connection with the example described above, the UE would not send the Data Transfer Complete Indication message before the timer T3xx has expired, if the timer T3xx was running.
The Data Transfer Complete Indication procedure commences with an indication that the RRC or upper layers will have no more PS domain data for a prolonged duration. If a CS domain connection is indicated in the variable ESTABLISHED_SIGNALLING_CONNECTIONS or if timer T3xx is set to infinity the procedure ends. Otherwise if timer T3xx is not running (i.e. has expired) or is set to 0 seconds, a DATA TRANSFER COMPLETE INDICATION message is submitted to the lower layers for transmission using AM RLC on DCCH after which the timer T3xx is started or reset when the message has been delivered to the lower layers.
The UTRAN on receipt of the DATA TRANSFER COMPLETE INDICATION may decide to initiate a UE transition to a more battery efficient RRC state or idle mode.
The UE shall not send the Data Transfer Complete Indication message while timer T3xx is running.
The present disclosure therefore provides a method for sending a transition indication to transition a user equipment to a different state or mode, the method comprising: receiving a configuration message from a network; and transmitting a transition indication from the user equipment, the transition indication only includes a cause if the configuration message contains an inhibit transition indication.
The present disclosure also provides a user equipment configured to send a transition indication to transition to a different state or mode, the user equipment configured to: receive a configuration message from a network; and transmit a transition indication from the user equipment, the transition indication only includes a cause if the configuration message contains an inhibit transition indication.
The present disclosure further provides a method for processing a transitioning indication from a user equipment indicating the user equipment desires a transition to a different state or mode, the method comprising: receiving the transition indication from the user equipment; if the transition indication contains a cause: releasing a signaling connection of the user equipment or transitioning the user equipment to a different state or mode; and if the transition indication does not contain the cause: releasing the signaling connection.
The present disclosure further provides a network element configured to transition a state or mode of a user equipment, the network equipment configured to: receive the transition indication from the user equipment; if the transition indication contains a cause: release a signaling connection of the user equipment or transitioning the user equipment to a different state or mode; and if the transition indication does not contain the cause: release the signaling connection.
Reference is now made to
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
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 an RRC connection whenever it needs to send Mobility Management signaling messages such as Location Area Update.
Once the UE has sent a request to the UTRAN to establish a radio connection, the UTRAN chooses a state for the RRC connection to be in. Specifically, the RRC connected mode 120 includes four separate states. These are CELL_DCH state 122, CELL_FACH state 124, CELL_PCH state 126 and URA_PCH state 128.
From idle mode 110 the UE autonomously transitions to the CELL_FACH state 124, in which it makes its initial data transfer, subsequent to which the network determines which RRC connected state to use for continued data transfer. This may include the network either moving the UE into the Cell Dedicated Channel (CELL_DCH) state 122 or keeping the UE in the Cell Forward Access Channel (CELL_FACH) state 124.
In CELL_DCH state 122, a dedicated channel is allocated to the UE for both uplink and downlink to exchange data. This state, since it has a dedicated physical channel allocated to the UE, typically requires the most battery power from the UE.
Alternatively, the UTRAN can maintain the UE in a CELL_FACH state 124. In a CELL_FACH state 124, 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 more battery power than in a CELL_PCH state 126, a URA_PCH state 128, and in idle mode 110.
Within the RRC connected mode 120, the RRC state can be changed at the discretion of the UTRAN. Specifically, if 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.
From CELL_FACH state 124, if data inactivity is detected for a predetermined time in some networks, the UTRAN can move the RRC state from CELL_FACH state 124 to a paging channel (PCH) state. This can be either the CELL_PCH state 126 or URA_PCH state 128.
From CELL_PCH state 126 or URA_PCH state 128 the UE must move to CELL_FACH state 124 in order to initiate an update procedure to request a dedicated channel. This is the only state transition that the UE controls.
Idle mode 110 and CELL_PCH state 126 and URA_PCH state 128 use a discontinuous reception cycle (DRX) to monitor broadcast messages and pages by a Paging Indicator Channel (PICH). No uplink activity is possible.
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
As seen in
As will be appreciated by those skilled in the art, from a battery life perspective the idle state provides the lowest battery usage compared with the states above. Specifically, because the UE is required to monitor the paging channel only at intervals, the radio does not need to continuously be on, but will instead wake up periodically. The trade-off for this is the latency to send data. However, if this latency is not too great, the advantages of being in the idle mode and saving battery power outweigh the disadvantages of the connection latency.
Reference is again made to
In a first exemplary infrastructure, the RRC moves between an idle mode 110 and a CELL_DCH state 122 directly after initiating access in a CELL_FACH state 124. 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.
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 payload is above a certain payload threshold then the UTRAN moves the RRC state to a 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 state 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 results 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 configurations. The first includes a configuration which has a high data rate and a second configuration 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 sub-state. Seventeen seconds of inactivity from the low data sub-state of CELL_DCH state 122 results 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 or 124. This causes unnecessary current drain, making the 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 110.
The URA_PCH state 128 with a DRX cycle similar to that of the idle state 110 is likely the optimal trade up between battery life and latency for connection. However, URA_PCH state 128 is currently not implemented in the UTRAN. In some cases, 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
Once RRC connection setup 310 is accomplished, a signaling connection setup 312 is started.
Once signaling connection setup 312 is finished, a ciphering and integrity setup 314 is started. Upon completion of this, a radio bearer setup 316 is accomplished. At this point, data can be exchanged between the UE and UTRAN.
Tearing down a connection is similarly accomplished in the reverse order, in general. The radio bearer setup 316 is taken down and then the RRC connection setup 310 is taken down. At this point, the RRC moves into idle mode 110 as illustrated in
Although the current 3GPP specification does not allow the UE to release the RRC connection or indicate its preference for 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.331, 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 deciphering 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 setup 310 is typically brought down by the network for current vendor infrastructures if no CS connection is active.
Using this for one of the specific transition indication examples mentioned above, if the UE determines that it is done with the exchange of data, for example if a “connection manager” component of the UE software is provided with an indication that the exchange of data is complete, then the connection manager may determine whether or not to tear down the signaling connection setup 312. For example, an e-mail application on the device sends an indication that it has received an acknowledgement from the push e-mail server that the e-mail was indeed received by the push server. The connection manager can, in one embodiment, keep track of all existing applications, associated PDP contexts, associated PS radio resources and associated circuit switched (CS) radio bearers. In other embodiments a network element (e.g. the UTRAN) can keep track of existing applications, associated PDP contexts, QoS, associated PS radio resources and associated CS radio bearers. A delay can be introduced at either the UE or network element to ensure that the application(s) is (are) truly finished with data exchange and no longer requires an RRC connection even after the “done” indication(s) have been sent. This delay can be made equivalent to an inactivity timeout associated with the application(s) or the UE. Each application can have its own inactivity timeout and thus the delay can be a composite of all of the application timeouts. 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. An inhibit duration timer can further delay sending of a transition indication. Based on a composite status of all such indications from active applications, as well as a radio resource profile and/or inhibit duration timer delay in some embodiments, the UE software decides how long it should or must wait before it sends a transition indication (for e.g. a signaling connection release indication or state change request) for the appropriate core network (e.g. PS Domain). If the delay is implemented at the network element, the element makes a determination of whether to and how to transition the UE, but only operates the transition after the delay has run its course.
The inactivity timeout can be made dynamic based on a traffic pattern history and/or application profile.
If the network element transitions the UE to idle mode 110, which can happen in any stage of the RRC connected mode 120 as illustrated in
In a further embodiment, a cause could be added to the transition indication indicating to the UTRAN the reason for the indication. In a preferred embodiment, the cause could be an indication that an abnormal state caused the indication or that the indication was initiated by the UE as a result of a requested transition. Other normal (i.e. non-abnormal) transactions could also result in the sending of the transition indication.
In a further preferred embodiment, various timeouts can cause a transition indication to be sent for an abnormal condition. The examples of timers below are not exhaustive, and other timers or abnormal conditions are possible. For example, 10.2.47 3GPP TS 24.008 specifies timer T3310 as:
This timer is used to indicate an attachment failure. The failure to attach could be a result of the network or could be a radio frequency (RF) problem such as a collision or bad RF.
The attachment attempt could occur multiple times, and an attachment failure results from either a predetermined number of failures or an explicit rejection.
A second timer of 10.2.47 of 3GPP is timer T3330, which is specified as:
This timer is used to indicate a routing area update failure. Upon expiry of the timer, a further routing area update could be requested multiple times and a routing area update failure results from either a predetermined number of failures or an explicit rejection.
A third timer of 10.2.47 of 3GPP is timer T3340, which is specified as:
This timer is used to indicate a GMM service request failure. Upon expiry of the timer, a further GMM service request could be initiated multiple times and a GMM service request failure results from either a predetermined number of failures or an explicit rejection.
Thus, instead of a transition indication cause limited to an abnormal condition and a release by the UE, the transition indication cause could further include information about which timer failed for an abnormal condition. In a specific example where a signaling connection release indication is used as a transition indication, the indication could be structured as:
This message is used by the UE to indicate to the UTRAN a request to release an existing signaling connection. The addition of the signaling connection release indication cause allows the UTRAN or other network element to receive the cause of the signaling connection release indication, whether it was due to an abnormal condition, and what the abnormal condition was. Based on the receipt of the SIGNALING CONNECTION RELEASE INDICATION, an RRC connection release procedure is, in turn, permitted to be initiated at the UTRAN.
In one implementation of this example, the UE, upon receiving a request to release, or abort, a signaling connection from upper layers for a specific CN (core network) domain, initiates the signaling connection release indication procedure if a signaling connection is identified in a variable. For example, a variable ESTABLISHED_SIGNALING_CONNECTIONS, for the specific CN domain identified with the IE (information element) “CN domain identity” exists. If the variable does not identify any existing signaling connection, any ongoing establishment of a signaling connection for that specific CN domain is aborted in another manner. Upon initiation of the signaling connection release indication procedures in the CELL_PCH or URA_PCH states 126 or 128, the UE performs a cell update procedure using a cause “uplink data transmission”. When a cell update procedure is completed successfully, the UE continues with the signaling connection release indication procedures that follow.
Namely, the UE sets the information element (IE) “CN domain identity” to the value indicated by upper logical layers. The value of the IE indicates the CN domain whose associated signaling connection the upper layers are marking to be released. If the CN domain identity is set to the PS domain, and if the upper layer indicates the cause to initiate this request, then the IE “SIGNALING RELEASE INDICATION CAUSE” is accordingly set. The UE further removes the signaling connection with the identity indicated by upper layers from the variable “ESTABLISHED_SIGNALING_CONNECTIONS”. The UE transmits a SIGNALING CONNECTION RELEASE INDICATION message on, e.g., the Dedicated Control Channel (DCCH) using acknowledged mode radio link control (AM RLC). Upon confirmation of successful delivery of the release indication message by the RLC, the procedure ends.
An IE “Signaling Connection Release Indication Cause” is also used pursuant to an embodiment of the present disclosure. The release cause is aligned, for instance, with existing message definitions. The upper layer release cause message is structured, e.g., as:
In this example, the T3310, T3330, and T3340 expiries correspond to expiration of correspondingly-numbered timers, identified previously. A cause value is settable, in one implementation, as a “UE Requested PS Data session end” rather than a “UE Requested idle transition” to remove the UE indication of a preference for an idle transition and provide for the UTRAN to decide upon the state transition, although the expected result corresponds to that identified by the cause value. The extension to the signaling connection release indication is preferably, but not necessarily, a non-critical extension.
Reference is now made to
The UE transitions to step 912 in which it checks to see whether an abnormal condition exists. Such an abnormal condition can include, for example, timer T3310, timer T3320, or timer T3340 expiring as described above. If these timers expire a certain predetermined number of times or if an explicit rejection is received based on the expiry of any of these timers, the UE proceeds to step 914 in which it sends a signaling connection release indication. The SIGNALING CONNECTION RELEASE INDICATION message is appended with a signaling release indication cause field. The signaling release indication cause field includes at least that the signaling release indication is based on an abnormal condition or state and one embodiment includes the specific timer that timed out to result in the abnormal condition.
Conversely, if in step 912 the UE finds that no abnormal condition exists, the UE proceeds to step 920 in which it checks whether further data is expected at the UE. This can, as described above, include when an email is sent and confirmation of the sending of the email is received back at the UE. Other examples of where the UE will determine that no further data is expected would be known to those skilled in the art.
If in step 920 the UE determines that the data transfer is finished (or in the case of a circuit switched domain that a call is finished) the UE proceeds to step 922 in which it sends a signaling connection release indication in which the signaling release indication cause field has been added and includes the fact that the UE requested an idle transition or simply indicated an end to the PS session.
From step 920, if the data is not finished the UE loops back and continues to check whether an abnormal condition exists in step 912 and whether the data is finished in step 920.
Once the signaling connection release indication is sent in step 914 or step 922, the process proceeds to step 930 and ends.
The UE includes functional elements, implementable, for instance, by applications or algorithms carried out through operation of a UE microprocessor or by hardware implementation, that form a checker and a transition indication sender. The checker is configured to check whether a transition indication should be sent. And, a transition indication sender is configured to send a transition indication responsive to an indication by the checker that the transition indication should be sent. The transition indication may include a transition indication cause field.
In one implementation, the network is, instead, implicitly made aware of timing out of a timer, and the UE need not send a cause value indicating the timing out of the timer. That is to say, the timer starts timing upon authorization of the network. Cause codes are defined, and the cause codes are provided by the network to the UE. Such cause codes are used by the UE to initiate the timer. The network is implicitly aware of the reason for subsequent timing out of the timer as the cause code sent earlier by the network causes the timer to start timing. As a result, the UE need not send a cause value indicating the timing out of the timer.
As suggested by
Referring to
Conversely, if in step 1016 the cause of the transition indication (e.g. signaling connection release indication) is not a result of an abnormal condition, or in other words is a result of the UE requesting a PS data session end or idle transition, the network node proceeds to step 1030 in which no alarm is raised and the indication can be filtered from the performance statistics, thereby preventing the performance statistics from being skewed. From step 1020 or step 1030 the network node proceeds to step 1040 in which the process ends.
The reception and examination of the transition indication may result in the initiation by the network element of packet switched data connection termination or alternatively to a transition into another more suitable state, for example CELL_FACH, CELL_PCH, URA_PCH or IDLE_MODE.
As suggested above, in some implementations, the absence of a cause in a transition indication may also be used to determine whether the transition indication is a result of a normal or an abnormal condition and whether an alarm must be raised. For example, if a cause is added only to denote normal conditions (i.e. non-abnormal such as for e.g. a request for PS data session end and/or transition to idle mode), and the network element receives a transition indication with no cause added, the network element may infer from the absence of a cause that the transition indication is a result of an abnormal condition and optionally raise an alarm. Conversely, in another example, if a cause is added only to denote abnormal conditions, and the network element receives a transition indication with no cause, the network element may infer from the absence of a cause that the transition indication is a result of a normal condition (e.g. request for PS data session end and/or transition to idle mode) and not raise an alarm.
As will be appreciated by those skilled in the art, step 1020 can be used to further distinguish between various alarm conditions. For example, a T3310 time out could be used to keep a first set of statistics and a T3330 time out could be used to keep a second set of statistics. Step 1020 can distinguish between the causes of the abnormal condition, thereby allowing the network operator to track performance more efficiently.
The network includes functional elements, implementable, for instance, by applications or algorithms carried out through operation of a processor or by hardware implementation, that form an examiner and an alarm generator. The examiner is configured to examine a transition indication cause field of the transition indication. The examiner checks whether the transition indication cause field indicates an abnormal condition. The alarm generator is configured to selectably generate an alarm if examination by the examiner determines the signaling connection release indication cause field indicates the abnormal condition.
In one implementation, upon reception of a signaling connection release indication, the UTRAN forwards the cause that is received and requests, from upper layers, for the release of the signaling connection. The upper layers then are able to initiate the release of the signaling connection. The IE signaling release indication cause indicates the UE's upper layer cause to trigger the RRC of the UE to send the message. The cause is possibly the result of an abnormal upper layer procedure. Differentiation of the cause of the message is assured through successful reception of the IE.
A possible scenario includes a scenario in which, prior to confirmation by the RLC of successful delivery of the SIGNALING CONNECTION RELEASE INDICATION message, reestablishment of the transmitting side of the RLC entity on the signaling radio bearer RB2 occurs. In the event of such an occurrence, the UE retransmits the SIGNALING CONNECTION RELEASE INDICATION message, e.g., on the uplink DCCH using AM RLC on signaling radio bearer RB2. In the event that an inter-RAT (radio access technology) handover from UTRAN procedure occurs prior to confirmation by the RLC of the successful delivery of the SIGNALING CONNECTION RELEASE INDICATION or request message, the UE aborts the signaling connection when in the new RAT.
In a further embodiment, instead of a “signaling connection release indication” or request, a “data transfer complete indication” could be utilized. Functionality similar to that described in
In one embodiment, the data transfer complete indication is used by the UE to inform the UTRAN that the UE has determined that there is no on-going CS domain data transfer, and it has completed its PS data transfer. Such a message is sent from the UE to UTRAN on the DCCH using AM RLC, for example. An exemplary message is shown below.
Reference is now made to
In a further and alternative embodiment, the conditions may include precluding the sending of the transition indication if timer T3xx is set to infinity. As will be appreciated, T3xx could include a number of discrete values, one of which represents an infinity value.
If, in step 2012, the conditions are not appropriate to send the transition indication or request message, the process loops on itself and continues to monitor until conditions are appropriate to send the transition indication or request message.
Once the conditions are appropriate the process proceeds to step 2020 in which a transition indication is sent to the UTRAN. Exemplary indications are shown in the tables above.
The process then proceeds to step 2022 in which a check is made to determine whether the transition indication was successful. As would be appreciated by those skilled in the art this could mean that the UTRAN has successfully received the transition indication and has initiated a state transition. If yes, the process proceeds to step 2030 and ends.
Conversely, if it is determined in step 2022 that the transition indication was not successful the process proceeds to step 2024 and waits for a time period. Such a wait could be implemented using an “inhibit duration”, e.g. T3xx, that would not allow the mobile to send another transition indication message before a given duration has elapsed. Alternatively, the process could limit the number of transition indication messages within a given time period (e.g. no more than 15 messages in 10 minutes). A combination of the inhibition duration and limiting the number of messages within a given time period is also possible.
The duration could be predetermined, such as a value defined in the standards, could be set by a network element, for example, as part of an RRC connection request, an RRC connection setup message, an RRC connection release, a radio bearer setup, a system information broadcast message, a system information block message, an ACTIVE SET UPDATE, a CELL UPDATE CONFIRM, UTRAN Mobility Information Message, a Handover to UTRAN Command, a Physical Channel Reconfiguration Message, a Radio Bearer Reconfiguration Message, a Radio Bearer Release Message, a Transport Channel Reconfiguration Message, or any request, configuration or reconfiguration message. Further, the duration could be set based on a parameter within the transition indication message. Thus, the duration could be longer if the UE is requesting a transition to CELL_PCH rather than Idle.
The signaling or sending of the duration by a network element could take the form of an information element. As used herein, signaling or sending could include directly sending the information to a UE, or broadcasting the information. Similarly, receiving at the UE could include direct reception or reading of a broadcast channel. One exemplary information element includes:
The values of T3xx, in one embodiment are defined as:
In one embodiment T3xx can be included in the existing UMTS Information Element “UE Timers and Constants in connected mode”. This can therefore be broadcast in a cell by inclusion in System Information Block Type 1. In an alternative embodiment the timer value could also be signaled using other system information messages, such as SIB3 or SIB4, or either alternatively or additionally could be signaled with a dedicated UTRAN mobility information message.
As indicated in the Table above, the T3xx value can vary between set values and include a zero value or an infinity value. The zero value is used to indicate that no inhibition needs to occur. The infinity value indicates that a Transition Indication Message should never be sent.
In one mobility embodiment, the UE resets the T3xx value whenever a new network or cell is transitioned to. In this example, the value is set to infinity. This ensures that if a transitioning message or Radio Bearer Messages does not contain an inhibit timer value, then by default the UE is not to send the Transition Indication Message. Thus, for example, if the transitioning or Radio Bearer Message does not contain an “Inhibit Transition Indication”, the value of the timer is set to infinity and otherwise the value of the timer received in the indication replaces any previously stored value.
In another alternative embodiment the values of T3xx, are defined as follows. The inclusion of the timer T3xx is optional thereby ensuring that if not included the UE need not have to support configuring or using this timer:
The reception of the inhibit timer in a cell is thus an indication to the UE that the cell recognizes the use of the transition indication message. The UE may determine, if initiated by the RRC or higher layers due to a determination of no more PS domain data for a prolonged duration, to signal a transition indication using a cause value. When the network receives a transition indication message (of whatever form, as captured in this document) with this cause value it may determine to signal to the UE a state transition change to a more battery efficient RRC State.
Whereas in an alternative embodiment when the inhibit timer is not received or read in a cell the UE can determine that the cause for sending the transition indication message, is not supported by the UTRAN. In this case the UE can determine to not configure a value for T3xx and also not to use the T3xx in relation to sending or inhibiting the sending of the transition indication message.
If the UE determines that the inhibit timer is omitted then it may omit to include the cause value from the transition indication message and just send the transition indication message, based on higher layer determining that it has no more PS data to transmit.
In an alternative embodiment the UE on determining that the inhibit timer is omitted the UE shall not initiate a transition indication based on higher layer determining that it has no more PS data to transmit.
In one embodiment of this described behavior, the transition indication message is the SIGNALING CONNECTION RELEASE INDICATION message.
In a first alternative embodiment, the reception of the inhibit timer in a cell is thus an indication that the cell recognizes the use of the transition indication messages. Where the sending of this message is permitted when the T3xx is not set to infinity value, then when the network receives a transition indication it may determine to signal to the UE a state transition to a more battery efficient RRC State (e.g. CELL_FACH, CELL_PCH, URA_PCH or IDLE_MODE).
In a particular example utilizing the 3GPP TSG-RAN2 25.331 standard, the following is added to the sections identified below:
This is added to sections:
The messages described above, besides messages 10.2.48.8.6 System Information Block Type 3 and 10.2.48.8.7 System Information Block Type 4, are all examples of mobility information messages.
The above covers connections and system operations, as well as transitions between various cells, ensuring that a UE has an inhibit timer value if that cell supports the transition indication message. For example, the Handover to UTRAN Command ensures that a transition from another Radio Access Technology such as a second generation network to a third generation network will provide an inhibit timer value if supported by the third generation network's target cell.
In particular referring to
If not, the process proceeds to block 2120 in which the inhibit timer value is set to infinity. Conversely, from block 2114 the process proceeds to block 2130 if it is determined that the configuration message does include an inhibit timer value. In block 2130 the inhibit timer value is stored on the UE, replacing the previous value for the inhibit timer. The process then proceeds to block 2140 and ends. As will be appreciated, in one embodiment the process of
Once the process has waited for a predetermined time in step 2024 the process proceeds back to step 2012 to determine whether the conditions for sending a transition indication still exist. If yes, the process loops back to step 2020 and 2022.
Based on the above, the inhibit timer value may be provided in various embodiments. In a first embodiment it can be provided only using an RRC Connection Setup Message to convey an inhibit timer value.
In a second embodiment, system information can be used to convey the inhibit timer value.
In a third embodiment the RRC Connection Setup and System Information Messages can both be utilized to send the inhibit timer value to ensure that UEs in idle mode and CELL_PCH/CELL_FACH and DCH states have the latest information.
In a fourth embodiment the inhibit timer value can be sent as in the third embodiment, with the addition of sending an inhibit timer value in a Radio Bearer Setup so that when a PDP context is established having no Radio Bearer, when a Radio Bearer is subsequently established to send a data message the inhibit timer value can be conveyed at that time.
In a fifth embodiment the fourth embodiment can be combined with all mobility-related messages as described above and including reconfiguration, cell update confirmation and a Handover to UTRAN command to convey the inhibit timer value.
In the first to fourth embodiments, during mobility the UE maintains its currently stored inhibit timer value. As indicated above, in some cases where the inhibit timer is set to infinity this may mean that the UE must wait for network timers to expire and for the network to move the UE to an RRC state where it can receive or determine a new value for the inhibit timer. In other cases where the inhibit timer is some value other than infinity before the handover, this other value is continued to be used until the UE is able to update the timer value to that indicated in the new cell.
For the fifth embodiment, the process of
An exception may occur on RLC re-establishment or inter-RAT change. If a re-establishment of the transmitting side of the RLC entity occurs before the successful delivery of the transition indication message has been confirmed by the RLC, in one embodiment the UE retransmits the transition indication message on the uplink DCCH using AM RLC.
In one embodiment, if an inter-RAT handover from UTRAN procedure occurs before the successful delivery of the transition indication message has been confirmed by the RLC the UE aborts the signaling connection while in the new RAT.
On the network side, the process is handled similarly to that described with reference to
Referring again to
Alternatively, the 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.
In a further alternative, the network element (e.g. the UTRAN) may itself take into account other factors such as what state the RRC connection is currently in and 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 instead simply transition the UE into a more suitable state instead of releasing the connection.
Reference is made to
The UE starts in RRC idle state 110 and based on local or mobile generated data needing to be transmitted or a page received from the UTRAN, starts to establish an RRC connection.
As illustrated in
Next, signaling connection setup 312, ciphering and integrity setup 314, and radio bearer setup 316 occurs. The RRC state is CELL_DCH state 122 during these procedures. As illustrated in
Data is next exchanged. In the example of
After data is exchanged in step 420, no data is being exchanged except for intermittent RLC signaling PDU as required and thus the radio resource is reconfigured by the network to move into a lower data rate DCH configuration after approximately ten seconds. This is illustrated in steps 422 and 424.
In the lower data rate DCH configuration, nothing is received for seventeen seconds, at which point the RRC connection is released by the network in step 428.
Once the RRC connection release is initiated in step 428, the RRC state proceeds to a disconnecting state 430 for approximately forty milliseconds, after which the UE is in a RRC idle state 110.
Also illustrated in
Reference is now made to
As illustrated in
Further, the RRC data PDU exchange for the exemplary e-mail at step 420 of
The UE in the example of
As illustrated in
Reference is now made to
During this setup, the UE moves from RRC idle mode 110 to a CELL_DCH state 122 with a RRC state connecting step 410 in between.
As with
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 resource reconfigures the UE 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 a RRC connection release by network is performed in step 428.
As seen in
As further seen in
The UTRA RRC Connected Mode state being CELL_DCH state 122 or CELL_FACH state 124 lasts for approximately forty seconds in the example of
Reference is now made to
As with
As can be seen further in
As will be seen further in
Therefore, a comparison between
Reference is now made to
As seen in
Within these three planes, a non-access stratum (NAS) portion 614 and an access stratum portion 616 exist.
NAS portion 614 in CS control plane 610 includes a call control (CC) 618, supplementary services (SS) 620, and short message service (SMS) 622.
NAS portion 614 in PS control plane 611 includes both mobility management (MM) and GPRS mobility management (GMM) 626. It further includes session management/radio access bearer management SM/RABM 624 and GSMS 628.
CC 618 provides for call management signaling for circuit switched services. The session management portion of SM/RABM 624 provides for PDP context activation, deactivation and modification. SM/RABM 624 also provides for quality of service negotiation.
The main function of the RABM portion of the SM/RABM 624 is to connect a PDP context to a Radio Access Bearer. Thus SM/RABM 624 is responsible for the setup, modification and release of radio resources.
CS control plane 610 and PS control plane 611, in the access stratum 616 sit on radio resource control (RRC) 617.
NAS portion 614 in PS user plane 630 includes an application layer 638, TCP/UDP layer 636, and PDP layer 634. PDP layer 634 can, for example, include Internet Protocol (IP).
Access Stratum 616, in PS user plane 630 includes packet data convergence protocol (PDCP) 632. PDCP 632 is designed to make the WCDMA protocol suitable to carry TCP/IP protocol between UE and RNC (as seen in
The UMTS Radio Link Control (RLC) 640 and Medium Access Control (MAC) layers 650 form the data link sub-layers of the UMTS radio interface and reside on the RNC node and the User Equipment.
The Layer 1 (L1) UMTS layer (physical layer 660) is below the RLC/MAC layers 640 and 650. This layer is the physical layer for communications.
While the above can be implemented on a variety of mobile or wireless devices, an example of one mobile device is outlined below with respect to
UE 700 is preferably a two-way wireless communication device having at least voice and data communication capabilities. UE 700 preferably has the capability to communicate with other computer systems on the Internet. Depending on the exact functionality provided, the wireless device may be referred to as a data messaging device, a two-way pager, a wireless e-mail device, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device, as examples.
Where UE 700 is enabled for two-way communication, it will incorporate a communication subsystem 711, including both a receiver 712 and a transmitter 714, as well as associated components such as one or more, preferably embedded or internal, antenna elements 716 and 718, local oscillators (LOs) 713, and a processing module such as a digital signal processor (DSP) 720. As will be apparent to those skilled in the field of communications, the particular design of the communication subsystem 711 will be dependent upon the communication network in which the device is intended to operate. For example, UE 700 may include a communication subsystem 711 designed to operate within the GPRS network or UMTS network.
Network access requirements will also vary depending upon the type of network 719. For example, in UMTS and GPRS networks, network access is associated with a subscriber or user of UE 700. 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 700 will be unable to carry out any other functions involving communications over the network 700. The UIM interface 744 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 751, and other information 753 such as identification, and subscriber-related information.
When required network registration or activation procedures have been completed, UE 700 may send and receive communication signals over the network 719. Signals received by antenna 716 through communication network 719 are input to receiver 712, 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
Network 719 may further communicate with multiple systems, including a server 760 and other elements (not shown). For example, network 719 may communicate with both an enterprise system and a web client system in order to accommodate various clients with various service levels.
UE 700 preferably includes a microprocessor 738, which controls the overall operation of the device. Communication functions, including at least data communications, are performed through communication subsystem 711. Microprocessor 738 also interacts with further device subsystems such as the display 722, flash memory 724, random access memory (RAM) 726, auxiliary input/output (I/O) subsystems 728, serial port 730, keyboard 732, speaker 734, microphone 736, a short-range communications subsystem 740 and any other device subsystems generally designated as 742.
Some of the subsystems shown in
Operating system software used by the microprocessor 738 is preferably stored in a persistent store such as flash memory 724, which may instead be a read-only memory (ROM) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile memory such as RAM 726. Received communication signals may also be stored in RAM 726. Further, a unique identifier is also preferably stored in read-only memory.
As shown, flash memory 724 can be segregated into different areas for both computer programs 758 and program data storage 750, 752, 754 and 756. These different storage types indicate that each program can allocate a portion of flash memory 724 for their own data storage requirements. Microprocessor 738, in addition to its operating system functions, preferably enables execution of software applications on the mobile device. A predetermined set of applications that control basic operations, including at least data and voice communication applications for example, will normally be installed on UE 700 during manufacturing. A preferred software application may be a personal information manager (PIM) application having the ability to organize and manage data items relating to the user of the mobile device such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items. Naturally, one or more memory stores would be available on the mobile device to facilitate storage of PIM data items. Such PIM application would preferably have the ability to send and receive data items, via the wireless network 719. In a preferred embodiment, the PIM data items are seamlessly integrated, synchronized and updated, via the wireless network 719, with the mobile device user's corresponding data items stored or associated with a host computer system. Further applications may also be loaded onto the mobile device 700 through the network 719, an auxiliary I/O subsystem 728, serial port 730, short-range communications subsystem 740 or any other suitable subsystem 742, and installed by a user in the RAM 726 or preferably a non-volatile store (not shown) for execution by the microprocessor 738. Such flexibility in application installation increases the functionality of the device and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using the UE 700. These applications will however, according to the above, in many cases need to be approved by a carrier.
In a data communication mode, a received signal such as a text message or web page download will be processed by the communication subsystem 711 and input to the microprocessor 738, which preferably further processes the received signal for output to the display 722, or alternatively to an auxiliary I/O device 728. A user of UE 700 may also compose data items such as email messages for example, using the keyboard 732, which is preferably a complete alphanumeric keyboard or telephone-type keypad, in conjunction with the display 722 and possibly an auxiliary I/O device 728. Such composed items may then be transmitted over a communication network through the communication subsystem 711.
For voice communications, overall operation of UE 700 is similar, except that received signals would preferably be output to a speaker 734 and signals for transmission would be generated by a microphone 736. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on UE 700. Although voice or audio signal output is preferably accomplished primarily through the speaker 734, display 722 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.
Serial port 730 in
Alternatively, serial port 730 could be used for other communications, and could include a universal serial bus (USB) port. An interface is associated with serial port 730.
Other communications subsystems 740, such as a short-range communications subsystem, is a further optional component which may provide for communication between UE 700 and different systems or devices, which need not necessarily be similar devices. For example, the subsystem 740 may include an infrared device and associated circuits and components or a Bluetooth™ communication module to provide for communication with similarly enabled systems and devices.
Reference is now made to
UE 802 communicates wirelessly with one or multiple Node Bs 806. Each Node B 806 is responsible for air interface processing and some radio resource management functions. Node B 806 provides functionality similar to a Base Transceiver Station in a GSM/GPRS network.
The wireless link shown in communication system 800 of
An RF channel is a limited resource that must be conserved, typically due to limits in overall bandwidth and a limited battery power of UE 802. Those skilled in the art will appreciate that a wireless network in actual practice may include hundreds of cells depending upon desired overall expanse of network coverage. All pertinent components may be connected by multiple switches and routers (not shown), controlled by multiple network controllers.
Each Node B 806 communicates with a radio network controller (RNC) 810. The RNC 810 is responsible for control of the radio resources in its area. One RNC 810 controls multiple Node Bs 806.
The RNC 810 in UMTS networks provides functions equivalent to the Base Station Controller (BSC) functions in GSM/GPRS networks. However, an RNC 810 includes more intelligence, including, for example, autonomous handovers management without involving MSCs and SGSNs.
The interface used between Node B 806 and RNC 810 is a lub interface 808. An NBAP (Node B application part) signaling protocol is primarily used, as defined in 3GPP TS 25.433 V3.11.0 (2002-09) and 3GPP TS 25.433 V5.7.0 (2004-01).
Universal Terrestrial Radio Access Network (UTRAN) 820 comprises the RNC 810, Node B 806 and the Uu air interface 804.
Circuit switched traffic is routed to Mobile Switching Centre (MSC) 830. MSC 830 is the computer that places the calls, and takes and receives data from the subscriber or from PSTN (not shown).
Traffic between RNC 810 and MSC 830 uses the Iu-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).
For all UEs 802 registered with a network operator, permanent data (such as UE 802 user's profile) as well as temporary data (such as UE's 802 current location) are stored in a home location registry (HLR) 838. In case of a voice call to UE 802, HLR 838 is queried to determine the current location of UE 802. A Visitor Location Register (VLR) 836 of MSC 830 is responsible for a group of location areas and stores the data of those mobile stations that are currently in its area of responsibility. This includes parts of the permanent mobile station data that have been transmitted from HLR 838 to the VLR 836 for faster access. However, the VLR 836 of MSC 830 may also assign and store local data, such as temporary identifications. UE 802 is also authenticated on system access by HLR 838.
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 within its geographical service area. Iu-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).
The SGSN 850 communicates with the Gateway GPRS Support Node (GGSN) 860. GGSN 860 is the interface between the UMTS/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.
Those skilled in the art will appreciate that the wireless network may be connected to other systems, possibly including other networks, not explicitly shown in
Responsive to a radio resource release request, or other decision to release the radio resource, the network selectably tears down the radio resource associated with the packet data service. Radio release requests are made on a radio access bearer-by-radio access bearer basis and not on an entire signaling connection basis, thereby permitting improved granularity control of resource allocation.
In the exemplary implementation, a single packet data service is further formable as a primary service and one or more secondary services, such as indicated by the designations 1118 and 1122. The radio resource release is further permitting of identifying which of one or more primary and secondary services whose radio resource allocations are no longer needed, or otherwise are desired to be released. Efficient radio resource allocation is thereby provided. In addition, optimal utilization of the processor on the UE is provided since the processor power that would have been allocated to unnecessary processing can now be better utilized for other purposes.
The apparatus 1126 includes a detector 1132 and a transition indication sender 1134. In one exemplary implementation, the elements 1132 and 1134 are embodied at a session management layer, e.g., the Non-Access Stratum (NAS) layer defined in UMTS, of the UE.
In another exemplary implementation, the elements are embodied at an Access Stratum (AS) sublayer. When implemented at the AS sublayer, the elements are implemented as part of a connection manager, shown at 1136. When implemented in this manner, the elements need not be aware of the PDP context behavior or of the application layer behavior.
The detector detects when a determination is made to send a transition indication associated with a packet communication service. The determination is made, e.g., at an application layer, or other logical layer, and provided to the session management layer and the detector embodied thereat. Indications of detections made by the detector are provided to the radio resource release indication sender. The sender generates and causes the UE to send a transition indication that forms the service release request 1116, shown in
In a further implementation, the transition indication includes a cause field containing a cause, such as any of the aforementioned causes described here and above, as appropriate or the cause field identifies a preferred state into which the UE prefers the network to cause the UE to be transitioned.
The apparatus 1128 embodied at the network includes an examiner 1142 and a grantor 1144. The examiner 1142 examines the transition indication, when received thereat. And, the transition grantor 1144 operates selectably to transition the UE as requested in the transition indication.
In an implementation in which the signaling is performed at a radio resource control (RRC) layer, the radio network controller (RNC), rather than the SGSN performs the examination and transitioning of the UE. And, correspondingly, the apparatus embodied at the UE is formed at the RRC layer, or the apparatus otherwise causes the generated indication to be sent at the RRC level.
In an exemplary control flow, a higher layer informs the NAS/RRC layer, as appropriate, that the radio resource that is allocated to a particular PDP context is no longer required. An RRC-layer indication message is sent to the network. The message includes an RAB ID or RB ID that, e.g., identifies the packet data service, to the radio network controller. And, in response, operation of the radio network controller triggers a procedure to resolve to end the radio resource release, radio resource reconfiguration, or radio resource control (RRC) connection release message to be returned to the UE. The RNC procedure is, e.g., similar, or equivalent to, the procedure set forth in 3GPP document TS 23.060, Section 9.2.5. The RAB ID is, e.g., advantageously utilized as the ID is the same as the Network Service Access Point Identifier (NSAPI) which identifies the associated PDP context, and application layers are generally aware of the NSAPI.
In a specific example, a radio resource release indication formed at, or otherwise provided to the RRC layer, and sent at the RRC layer is represented, together with associated information, below. The indication when embodied at the RRC layer is also referred to as, e.g., a radio resource release indication.
Upon initiation, a radio access bearer (RAB) release request is generated, and sent, indicated by the segment 1138 by the RNC/UTRAN and delivered to the SGSN. In response, an RAB assignment request is returned, indicated by the segment 1140, to the RNC/UTRAN. And, then, as indicated by the segment 1142, the radio resources extending between the UE 802 and the UTRAN are released. A response is then sent, as indicated by segment 1144.
After start of the process, indicated by the block 1164, a determination is made, indicated by the decision block 1166 as to whether a radio resource release indication has been received. If not, the no branch is taken to the end block 1168.
If, conversely, a radio access bearer release has been requested, the yes branch is taken to the decision block 1172. At the decision block 1172, a determination is made as to whether the radio access bearer that is to be released is the final radio access bearer to be released. If not, the no branch is taken to the block 1178, and the preferred state is set. Then radio access bearer release procedures are performed, such as that shown in
Conversely, if a determination is made at the decision block 1172 that the RAB is the last to be released, the yes branch is taken to the block 1186, an lu release procedure, such as that shown in
After start of the process, indicated by the block 1194, a determination is made, indicated by the decision block 1196 as to whether there is an RAB (Radio Access Bearer) to release. If not, the no branch is taken to the end block 1198.
If, conversely, a radio access bearer release has been requested, the yes branch is taken to the decision block 1202. At the decision block 1202, a determination is made as to whether the radio access bearer that is to be released is the final radio access bearer to be released. If not, the no branch is taken to the block 1204, where the RAB list is set, block 1206 where the preferred state is set, and block 1208 where radio access bearer release procedures are performed, such as that shown in
Conversely, if a determination is made at the decision block 1202 that the RAB is the last to be released, the yes branch is taken to the block 1212, and the domain is set to PS (Packet Switched). Then, as indicated by block 1214, a release cause is set. And, as indicated by the block 1216, a SIGNALING CONNECTION RELEASE INDICATION is sent on a DCCH. An lu release procedure, such as that shown in
Then, at block 1212 the radio resource release indication is examined and then at block 1214 the grant of the release of the radio bearer is selectably granted.
In a further embodiment, the network may initiate a transition based on both the receipt of an indication from the user equipment or another network element and on a radio resource profile for the user equipment.
An indication as received from the user equipment or other network element could be any of the different transition indications described above. The indication can be passive and thus be merely a blank indication that a less battery intensive radio state should be entered. Alternatively the indication could be part of the regular indications sent from the UE which the network determines, possibly over time or a number of received indications, and the UE's radio resource profile that a less battery or radio resource intensive radio state should be entered. Alternatively, the indication could be dynamic and provide information to the network element about a preferred state or mode in which to transition. As with the above, the indication could contain a cause for the indication (e.g. normal or abnormal). In a further embodiment, the indication could provide other information about a radio resource profile, such as a probability that the user equipment is correct about the ability to transition to a different state or mode, or information about the application(s) that triggered the indication.
An indication from another network element could include, for example, an indication from a media or push-to-talk network entity. In this example, the indication is sent to the network entity responsible for transitioning (e.g. the UTRAN) when traffic conditions allow. This second network entity could look at traffic at an Internet protocol (IP) level to determine whether and when to send a transition indication.
In a further embodiment, the indication from the UE or second network element could be implicit rather than explicit. For example, a transition indication may be implied by the network element responsible for transitioning (e.g. the UTRAN) from device status reports on outbound traffic measurements. Specifically, status reporting could include a radio link buffer status where, if no outbound data exists, could be interpreted as an implicit indication. Such status reporting could be a measurement that can be repetitively sent from the UE that does not, by itself, request or indicate anything.
The indication could thus be any signal and could be application based, radio resource based, or a composite indication providing information concerning all of the user equipment's application and radio resources. The above is not meant to be limiting to any particular indication, and one skilled in the art would appreciate that any indication could be used with the present method and disclosure.
Reference is now made to
Once the network receives the indication in step 1810, the process proceeds to step 1820 in which a radio resource profile for the user equipment is optionally checked.
The term “radio resource profile,” as used herein, is meant to be a broad term that could apply to a variety of situations, depending on the requirements of a network element. In broad terms, the radio resource profile includes information about radio resources utilized by the user equipment.
The radio resource profile could include either or both static profile elements and dynamic or negotiated profile elements. Such elements could include an “inhibit duration and/or maximum indication/request messages per time-window” value, which could be part of the radio resource profile, either within or apart from the transition profile, and could be negotiated or static.
Static profile elements may include one or more of the quality of service for a radio resource (e.g. RAB or RB), a PDP context, an APN that the network has knowledge of and a subscriber profile.
As will be appreciated by those skilled in the art, various levels of quality service could exist for a radio resource and the level of the quality of service could provide information to a network on whether to transition to a different state or mode. Thus if the quality of service is background, the network element may consider transitioning to idle more readily than if the quality of service is set to interactive. Further, if multiple radio resources have the same quality of service, this could provide an indication to the network on whether to transition the mobile device to a more suitable state or mode or to tear down the radio resources. In some embodiments, a primary and secondary PDP context could have a different quality of service, which could also affect the decision on whether to perform a state/mode transition.
Further, the APN could provide the network with information about the typical services that the PDP context utilizes. For example, if the APN is xyz.com, where xyz.com is typically used for the provision of data services such as email, this could provide an indication to the network about whether or not to transition to a different state or mode. This could further indicate routing characteristics.
In particular, the present method and apparatus can utilize the Access Point Name (APN) specified by the UE to set the transition profile between various states. This may be another way of describing the subscription of the UE. As will be appreciated, the Home Location Register (HLR) may store relevant information about subscribers, and could provide the radio network controller (RNC) with the subscription of the UE. Other network entities could also be used to store subscription information centrally. Whether using the HLR or other network entity, information is preferably pushed to other network components such as the RNC and SGSN, which map subscription information to relevant physical parameters used during data exchange.
The UTRAN could include or have access to a database or table in which various APNs or QoS parameters could be linked to a specific transition profile. Thus, if the UE is an always on device, this will be apparent from the APN and an appropriate transition profile for that APN could be stored at the UTRAN as part of the radio resource profile or be remotely accessible by the UTRAN. Similarly, if the QoS or a portion of the QoS parameter is used, or a dedicated message sent with a profile, this could signify to the UTRAN that a particular transition profile is desired based on a database query or a lookup in a table. Additionally, a multiplicity of behaviors beyond the RRC connected state transition profile can be specified by this means. These include, but are not limited to:
Further, if there are multiple PDP contexts that have different QoS requirements, but share the same APN IP address, such as a primary context, secondary context, and so forth, a different transition profile can be used for each context. This could be signaled to the UTRAN through QoS or dedicated messages.
If multiple active PDP contexts are concurrently utilized, the lowest common denominator between the contexts can be used. For RRC state transition, if one application has a first PDP context that is associated with a transition profile in which the system moves from CELL_DCH state to a CELL_PCH or Idle state quickly, and a second PDP context is associated with a transition profile in which the system is to stay in the CELL_DCH state longer, the second profile in which the CELL_DCH state is maintained longer will override the first profile.
As will be appreciated by those skilled in the art, the lowest common denominator can be considered in two different ways. Lowest common denominator, as used herein, implies a longest time required before transitioning to a different state. In a first embodiment, the lowest common denominator may be the lowest of the activated PDPs. In an alternative embodiment, the lowest common denominator may be the lowest of the PDPs that actually have active radio resources. The radio resources could be multiplexed in a number of different fashions but the end result is the same.
An exemplary case for such methods can be drawn for always on devices. As described, various APNs or QoS parameters can be linked to a specific behavior for always on. Consider initially granted radio resources that may be desirable based on an ‘always on’ profile. The network now has a means to ‘know’ that data bursts are short and bursty for always-on applications, such as email. For those skilled in the art, it is clearly seen that given this information, there is no incentive to save code space for trunking efficiency on the network. Thus a maximum rate may be allocated to an always-on device with little risk of not reserving enough code space for other users. Additionally the UE benefits in receiving data more rapidly and also saves on battery life due to shorter ‘on time’. Again, to those skilled in the art, high data rates have very little effect on current draw since power amplifiers are fully biased regardless of data rate.
In the above embodiment, a lookup table can be used by the UTRAN to determine the resource control profile for radio resources(s) to be assigned for different applications for a given RRC connection for the UE. The profile can be based on user subscription and stored on the network side at a network entity such as HLR or alternatively at the RNC since the RNC will have more up to date traffic resources available (i.e. data rates that can be granted). If higher data rates can be achieved shorter timeouts may be possible.
Instead of APN, other alternatives such as the Quality of Service (QoS) parameters set in a Packet Data Protocol (PDP) Context activation or Modified PDP Context can be used. The QoS field can further include the QoS “allocation retention priority (Service data unit could be used to infer traffic data volumes)” in case of multiple PDP contexts sharing the same APN address or a subscription profile to set the transition profile. Further alternatives include dedicated messages such as the indication message above to signal a resource control profile and information such as inhibit duration and/or maximum indication/request messages per time-window value.
The transition profile included in the radio resource profile could further include whether the state of the UE should be transitioned at all based on the type of application. Specifically, if the user equipment is being used as a data modem, a preference may be set either on the user equipment so transition indications are not sent or if knowledge of the preference is maintained at the network, that any transition indication received from the UE while being used as a data modem should be ignored. Thus the nature of the applications that are being run on the user equipment could be used as part of the radio resource profile.
A further parameter of a transition profile could involve the type of transition. Specifically, in a UMTS network, the user equipment may prefer to enter a CELL_PCH state rather than entering an idle state for various reasons. One reason could be that the UE needs to connect to a CELL_DCH state more quickly if data needs to be sent or received, and thus moving to a CELL_PCH state will save some network signaling and battery resources while still providing for a quick transition to the CELL_DCH state. The above is equally applicable in non-UMTS networks and may provide for a transition profile between various connected and idle states.
The transition profile may also include various timers including, but not limited to, inhibit duration and/or maximum indication/request messages per time-window, delay timers and inactivity timers. Delay timers provide a period which the network element will wait prior to transitioning to a new state or mode. As will be appreciated, even if the application has been inactive for a particular time period, a delay may be beneficial in order to ensure that no further data is received or transmitted from the application. An inactivity timer could measure a predetermined time period in which no data is received or sent by an application. If data is received prior to the inactivity timer expiring, typically the inactivity timer will be reset. Once the inactivity timer expires, the user equipment may then send the indication of step 1810 to the network. Alternatively, the user equipment may wait for a certain period, such as that defined for the delay timer, before sending the indication of step 1810.
Further, the delay timer or inhibit duration and/or maximum indication/request messages per time-window could vary based on a profile that is provided to the network element. Thus, if the application that has requested a transition to a different mode or state is a first type of application, such as an email application, the delay timer on the network element can be set to a first delay time, while if the application is of a second type such as an instant messaging application, the delay timer can be set to a second value. The values of the inhibit duration and/or maximum indication/request messages per time-window, delay timer or inactivity timer could also be derived by the network based on the APN utilized for a particular PDP.
As will be appreciated by those skilled in the art, the inactivity timer could similarly vary based on the application utilized. Thus, an email application may have a shorter inactivity timer than a browser application since the email application is expecting a discrete message after which it may not receive data. Conversely the browser application may utilize data even after a longer delay and thus require a longer inactivity timer.
The transition profile may further include a probability that a user equipment is correct requesting a transition. This could be based on compiled statistics on the rate of accuracy of a particular user equipment or application on the user equipment.
The transition profile may further include various discontinuous reception (DRX) time values. Further, a progression profile for DRX times could be provided in a transition profile.
The transition profile could be defined on an application by application basis or be a composite of the various applications on the user equipment.
As will be appreciated by those skilled in the art the transition profile could be created or modified dynamically when a radio resource is allocated and could be done on subscription, PS registration, PDP activation, RAB or RB activation or changed on the fly for the PDP or RAB/RB. The transition profile could also be part of the indication of step 1810. In this case, the network may consider the preferred RRC state indication to determine whether to allow the transition and to what state/mode. Modification could occur based on available network resources, traffic patterns, among others.
The radio resource profile is therefore comprised of static and/or dynamic fields. The radio resource profile used by a particular network may vary from other networks and the description above is not meant to limit the present method and system. In particular, the radio resources profile could include and exclude various elements described above. For example, in some cases the radio resource profile will merely include the quality of service for a particular radio resource and include no other information. In other cases, the radio resource profile will include only the transition profile. Still in other cases, the radio resource profile will include all of the quality of service, APN, PDP context, transition profile, among others.
Optionally, in addition to a radio resource profile, the network element could also utilize safeguards to avoid unnecessary transitions. Such safeguards could include, but are not limited to, the number of indications received in a predetermined time period, the total number of indications received, traffic patterns and historical data.
The number of indications received in a predetermined time period could indicate to the network that a transition should not occur. Thus, if the user equipment has sent, for example, five indications within a thirty second time period, the network may consider that it should ignore the indications and not perform any transitions. Alternatively the network may determine to indicate to the UE that it should not send any further indications either indefinitely or for some configured or predefined time period. This could be independent of any “inhibit duration and/or maximum indication/request messages per time-window” on the UE.
Further, the UE could be configured not to send further indications for a configured, predefined or negotiated time period. The UE configuration could be exclusive of the safeguards on the network side described above.
The traffic patterns and historical data could provide an indication to the network that a transition should not occur. For example, if the user has received a significant amount of data in the past between 8:30 and 8:35 a.m. from Monday to Friday, if the indication is received at 8:32 a.m. on Thursday, the network may decide that it should not transition the user equipment since more data is likely before 8:35 a.m.
If multiple radio resources are allocated for the user equipment, the network may need to consider the complete radio resource profile for the user equipment. In this case, the radio resource profiles for each radio resource can be examined and a composite transition decision made. Based on the radio resource profile of one or multiple radio resources, the network can then decide whether or not a transition should be made.
In one embodiment, the network has a plurality of choices on how to proceed when it has received an indication in step 1810 and optionally examined the radio resource profile or profiles in step 1820.
A first option is to do nothing. The network may decide that a transition is not warranted and thus not accept the user equipment indication to transition. As will be appreciated by those skilled in the art, doing nothing saves network signaling since the state is not changed and in particular since a transition is not triggered.
A second option is to change the state of the device. For example, in a UMTS network, the state of the device may change from CELL_DCH to CELL_PCH. In non-UMTS networks the state transition may occur between connected states. As will be appreciated by those skilled in the art, changing states reduces the amount of core network signaling when compared with a transition to idle mode. Changing the state can also save radio resources since the CELL_PCH state does not require a dedicated channel. Also, CELL_PCH is a less battery intensive state enabling the UE to preserve battery power.
A third option for the network is to keep the UE in the same state but release the radio resources associated with a particular APN or PDP context. This approach saves radio resources and signaling as the connection is maintained in its current state and does not need to be re-established. However, it may be less suitable for situations where UE battery life is a concern.
A fourth option for the network is to transition the UE to an Idle mode. In particular, in both UMTS and non-UMTS, the network may move from a connected mode to an Idle mode. As will be appreciated, this saves radio resources since no connection at all is maintained. It further saves the battery life on the user equipment. However, a greater amount of core network signaling is required to reestablish the connection.
A fifth option for the network is to change a data rate allocation, which will save radio resources, typically allowing more users to use the network.
Other options would be evident to those skilled in the art.
The decision of the network on which of the five or more options to utilize will vary from network to network. Some overloaded networks may prefer to preserve radio resources and thus would choose the third, fourth or fifth options above. Other networks prefer to minimize signaling and thus may choose the first or second options above.
The decision is shown in
Reference is now made to
Network element 1910 further includes a processor 1930 and a storage 1940. Storage 1940 is adapted to store preconfigured or static radio resource profiles for each user equipment being serviced by network element 1910. Processor 1930 is adapted to, upon receipt of an indication by communications subsystem 1920, consider the radio resource profile for the user equipment and to decide on a network action regarding transitioning the user equipment. As will be appreciated by those skilled in the art, the indication received by communications subsystem 1920 could further include a portion of or all of the radio resource profile for the user equipment that would then be utilized by processor 1930 to make the network decision concerning any transition.
Based on the above, a network element therefore receives an indication from the user equipment that a transition might be in order (such as for example when a data exchange is complete and/or that no further data is expected at the UE). Based on this indication, the network element optionally checks the radio resource profile of the user equipment, which could include both static and dynamic profile elements. The network element may further check safeguards to ensure that unnecessary transitions are not occurring. The network element could then decide to do nothing or to transition to a different mode or state, or to tear down a radio resource. As will be appreciated, this provides the network more control of its radio resources and allows the network to configure transition decisions based on network preferences rather than merely user equipment preferences. Further, in some cases the network has more information than the device concerning whether to transition. For example, the user equipment has knowledge of upstream communications and based on this may decide that the connection may be torn down. However, the network may have received downstream communications for the user equipment and thus realized that it cannot tear down the connection. In this case, a delay can also be introduced using the delay timer to provide the network with more certainty that no data will be received for user equipment in the near future.
The embodiments described herein are examples of structures, systems or methods having elements corresponding to elements of the techniques of this disclosure. This written description may enable those skilled in the art to make and use embodiments having alternative elements that likewise correspond to the elements of the techniques of this disclosure. The intended scope of the techniques of this disclosure thus includes other structures, systems or methods that do not differ from the techniques of this disclosure as described herein, and further includes other structures, systems or methods with insubstantial differences from the techniques of this disclosure as described herein.
| Number | Date | Country | Kind |
|---|---|---|---|
| 08154976 | Apr 2008 | EP | regional |
The present application is a continuation of and claims priority from U.S. patent application Ser. No. 13/157,724, filed Jun. 10, 2011, which is a continuation of U.S. patent application Ser. No. 12/270,522, filed Nov. 13, 2008, now U.S. Pat. No. 7,969,924, which claims priority from U.S. Provisional Application No. 60/987,672 filed Nov. 13, 2007; U.S. Provisional Application No. 61/061,359 filed Jun. 13, 2008; U.S. Provisional Application No. 61/074,856 filed Jun. 23, 2008; U.S. Provisional Application No. 61/086,955 filed Aug. 7, 2008; U.S. Provisional Application No. 61/089,731 filed Aug. 18, 2008; and European Patent Application No. EP 08154976 filed Apr. 22, 2008, claiming priority from U.S. Provisional Application No. 60/987,672 filed Nov. 13, 2007, the contents of all of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5812636 | Tseng et al. | Sep 1998 | A |
| 6064340 | Croft et al. | May 2000 | A |
| 6181683 | Chevillat et al. | Jan 2001 | B1 |
| 6223044 | Schultz | Apr 2001 | B1 |
| 6229989 | Kwon | May 2001 | B1 |
| 6243579 | Kari | Jun 2001 | B1 |
| 6275712 | Gray et al. | Aug 2001 | B1 |
| 6345185 | Yoon et al. | Feb 2002 | B1 |
| 6377790 | Ishii | Apr 2002 | B1 |
| 6593850 | Addy | Jul 2003 | B1 |
| 6654360 | Abrol | Nov 2003 | B1 |
| 6657984 | Semper | Dec 2003 | B1 |
| 6661777 | Blanc et al. | Dec 2003 | B1 |
| 6668175 | Almgren | Dec 2003 | B1 |
| 6748246 | Khullar | Jun 2004 | B1 |
| 6845236 | Chang | Jan 2005 | B2 |
| 6847610 | Suumaki | Jan 2005 | B1 |
| 6961570 | Kuo et al. | Nov 2005 | B2 |
| 7130668 | Chang et al. | Oct 2006 | B2 |
| 7155261 | Chen | Dec 2006 | B2 |
| 7164673 | Jang | Jan 2007 | B2 |
| 7280506 | Lin et al. | Oct 2007 | B2 |
| 7313408 | Choi | Dec 2007 | B2 |
| 7353120 | Enta | Apr 2008 | B2 |
| 7437172 | Chen et al. | Oct 2008 | B2 |
| 7480267 | Funnell et al. | Jan 2009 | B2 |
| 7539160 | Virtanen et al. | May 2009 | B2 |
| 7609673 | Bergenlid et al. | Oct 2009 | B2 |
| 7623869 | Lee et al. | Nov 2009 | B2 |
| 7672673 | Kojima | Mar 2010 | B2 |
| 7720482 | Chaudry et al. | May 2010 | B2 |
| 7761097 | Chaudry et al. | Jul 2010 | B2 |
| 7894375 | Chaudry et al. | Feb 2011 | B2 |
| 7949377 | Islam et al. | May 2011 | B2 |
| 7969924 | Young et al. | Jun 2011 | B2 |
| 8014772 | Beming et al. | Sep 2011 | B2 |
| 8208950 | Islam et al. | Jun 2012 | B2 |
| 8223697 | Dwyer et al. | Jul 2012 | B2 |
| 8243683 | Young et al. | Aug 2012 | B2 |
| 8265034 | Islam et al. | Sep 2012 | B2 |
| 8270932 | Kim et al. | Sep 2012 | B2 |
| 8305924 | Dwyer et al. | Nov 2012 | B2 |
| 8310970 | Dwyer et al. | Nov 2012 | B2 |
| 8644829 | Islam et al. | Feb 2014 | B2 |
| 9019877 | Young et al. | Apr 2015 | B2 |
| 9026153 | Islam et al. | May 2015 | B2 |
| 9049657 | Boley et al. | Jun 2015 | B2 |
| 9119208 | Dwyer et al. | Aug 2015 | B2 |
| 20010018342 | Vialen et al. | Aug 2001 | A1 |
| 20020022455 | Salokannel et al. | Feb 2002 | A1 |
| 20020064140 | Numminen | May 2002 | A1 |
| 20020077105 | Chang | Jun 2002 | A1 |
| 20020082020 | Lee et al. | Jun 2002 | A1 |
| 20020141331 | Mate et al. | Oct 2002 | A1 |
| 20020159444 | Vialen et al. | Oct 2002 | A1 |
| 20030003895 | Wallentin et al. | Jan 2003 | A1 |
| 20030014145 | Reiss et al. | Jan 2003 | A1 |
| 20030031159 | Sayeedi et al. | Feb 2003 | A1 |
| 20030156578 | Bergenlid et al. | Aug 2003 | A1 |
| 20030157927 | Yi et al. | Aug 2003 | A1 |
| 20030211846 | Nagpal et al. | Nov 2003 | A1 |
| 20040044771 | Allred et al. | Mar 2004 | A1 |
| 20040062262 | Venteicher et al. | Apr 2004 | A1 |
| 20040120253 | Forssell et al. | Jun 2004 | A1 |
| 20040156338 | Pasanen | Aug 2004 | A1 |
| 20040179490 | Jang | Sep 2004 | A1 |
| 20040192312 | Li et al. | Sep 2004 | A1 |
| 20040203778 | Kuo et al. | Oct 2004 | A1 |
| 20040203971 | Kuo | Oct 2004 | A1 |
| 20040216144 | Mitsui | Oct 2004 | A1 |
| 20040224669 | Pedlar | Nov 2004 | A1 |
| 20040224688 | Fischer | Nov 2004 | A1 |
| 20050009527 | Sharma | Jan 2005 | A1 |
| 20050026597 | Kim et al. | Feb 2005 | A1 |
| 20050032555 | Jami et al. | Feb 2005 | A1 |
| 20050105696 | Ramsden | May 2005 | A1 |
| 20050141471 | Virtanen et al. | Jun 2005 | A1 |
| 20050143056 | Iyer et al. | Jun 2005 | A1 |
| 20050153700 | Farnsworth et al. | Jul 2005 | A1 |
| 20050185613 | Kowalski et al. | Aug 2005 | A1 |
| 20050192021 | Lee et al. | Sep 2005 | A1 |
| 20050232176 | Van Lieshout et al. | Oct 2005 | A1 |
| 20050237935 | Chae et al. | Oct 2005 | A1 |
| 20050245267 | Guethaus | Nov 2005 | A1 |
| 20050265294 | Hu et al. | Dec 2005 | A1 |
| 20050266846 | Kim | Dec 2005 | A1 |
| 20050272422 | Asadi | Dec 2005 | A1 |
| 20050281269 | Choi | Dec 2005 | A1 |
| 20050286461 | Zhang et al. | Dec 2005 | A1 |
| 20060009202 | Gallagher et al. | Jan 2006 | A1 |
| 20060025122 | Harris et al. | Feb 2006 | A1 |
| 20060034204 | Lee | Feb 2006 | A1 |
| 20060036741 | Kiss et al. | Feb 2006 | A1 |
| 20060040645 | Grilli et al. | Feb 2006 | A1 |
| 20060089137 | Howell | Apr 2006 | A1 |
| 20060094478 | Kim et al. | May 2006 | A1 |
| 20060109846 | Lioy et al. | May 2006 | A1 |
| 20060111110 | Schwarz et al. | May 2006 | A1 |
| 20060176167 | Dohrmann | Aug 2006 | A1 |
| 20060182022 | Abedi | Aug 2006 | A1 |
| 20060223537 | Kojima | Oct 2006 | A1 |
| 20060223564 | Rosen et al. | Oct 2006 | A1 |
| 20060240823 | Jiao et al. | Oct 2006 | A1 |
| 20060293067 | Leung et al. | Dec 2006 | A1 |
| 20070072635 | Zhao et al. | Mar 2007 | A1 |
| 20070121540 | Sharp et al. | May 2007 | A1 |
| 20070135080 | Islam et al. | Jun 2007 | A1 |
| 20070270140 | Islam et al. | Nov 2007 | A1 |
| 20080039087 | Gallagher et al. | Feb 2008 | A1 |
| 20080049662 | Islam et al. | Feb 2008 | A1 |
| 20080123658 | Hyytia et al. | May 2008 | A1 |
| 20080126554 | Sakai et al. | May 2008 | A1 |
| 20080212542 | Kung et al. | Sep 2008 | A1 |
| 20080253312 | Park | Oct 2008 | A1 |
| 20080304510 | Qlu | Dec 2008 | A1 |
| 20080310313 | Maheshwari et al. | Dec 2008 | A1 |
| 20090016278 | Wakabayashi | Jan 2009 | A1 |
| 20090028084 | Ping | Jan 2009 | A1 |
| 20090042560 | Islam et al. | Feb 2009 | A1 |
| 20090088134 | Ishii et al. | Apr 2009 | A1 |
| 20090093262 | Gao et al. | Apr 2009 | A1 |
| 20090124212 | Islam et al. | May 2009 | A1 |
| 20090124249 | Young et al. | May 2009 | A1 |
| 20090129339 | Young et al. | May 2009 | A1 |
| 20090149189 | Sammour et al. | Jun 2009 | A1 |
| 20090161571 | Terry et al. | Jun 2009 | A1 |
| 20090221277 | Fomin et al. | Sep 2009 | A1 |
| 20090225709 | Wager et al. | Sep 2009 | A1 |
| 20090253422 | Fischer | Oct 2009 | A1 |
| 20090318199 | Barreto et al. | Dec 2009 | A1 |
| 20100046533 | Kuramoto et al. | Feb 2010 | A1 |
| 20100061361 | Wu | Mar 2010 | A1 |
| 20100075679 | Tenny et al. | Mar 2010 | A1 |
| 20100118752 | Suzuki et al. | May 2010 | A1 |
| 20100142457 | Chun et al. | Jun 2010 | A1 |
| 20100208696 | Lee et al. | Aug 2010 | A1 |
| 20100226325 | Chun et al. | Sep 2010 | A1 |
| 20100265896 | Park et al. | Oct 2010 | A1 |
| 20100323703 | Pirskanen | Dec 2010 | A1 |
| 20110007682 | Islam et al. | Jan 2011 | A1 |
| 20110038347 | Patil et al. | Feb 2011 | A1 |
| 20110122818 | Dwyer et al. | May 2011 | A1 |
| 20110124294 | Dwyer et al. | May 2011 | A1 |
| 20110159895 | Arzelier et al. | Jun 2011 | A1 |
| 20110182193 | Dwyer et al. | Jul 2011 | A1 |
| 20110207465 | Dwyer et al. | Aug 2011 | A1 |
| 20110249575 | Dwyer et al. | Oct 2011 | A1 |
| 20110267959 | Yi et al. | Nov 2011 | A1 |
| 20110306352 | Young et al. | Dec 2011 | A1 |
| 20120008585 | Kwon et al. | Jan 2012 | A1 |
| 20120014325 | Dwyer et al. | Jan 2012 | A1 |
| 20120014326 | Dwyer et al. | Jan 2012 | A1 |
| 20120033626 | Dwyer et al. | Feb 2012 | A1 |
| 20120051288 | Dwyer et al. | Mar 2012 | A1 |
| 20120051289 | Dwyer et al. | Mar 2012 | A1 |
| 20120281561 | Shukla et al. | Nov 2012 | A1 |
| 20120307703 | Young et al. | Dec 2012 | A1 |
| 20120320811 | Islam et al. | Dec 2012 | A1 |
| 20130021919 | Islam et al. | Jan 2013 | A1 |
| 20130122918 | Boley et al. | May 2013 | A1 |
| 20130188543 | Dwyer et al. | Jul 2013 | A1 |
| 20130295905 | Islam et al. | Nov 2013 | A1 |
| 20130308578 | Dwyer et al. | Nov 2013 | A1 |
| 20130316720 | Dwyer et al. | Nov 2013 | A1 |
| 20130336258 | Young et al. | Dec 2013 | A1 |
| 20140194131 | Islam et al. | Jul 2014 | A1 |
| 20140206369 | Islam et al. | Jul 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2007202206 | Dec 2007 | AU |
| 2781497 | May 2011 | CA |
| 2661592 | Oct 2013 | CA |
| 1328756 | Dec 2001 | CN |
| 1934802 | Mar 2007 | CN |
| 101005659 | Jul 2007 | CN |
| 101080102 | Nov 2007 | CN |
| 101114988 | Jan 2008 | CN |
| 101351041 | Jan 2009 | CN |
| 101409606 | Apr 2009 | CN |
| 101426278 | May 2009 | CN |
| 101453742 | Jun 2009 | CN |
| 103619071 | Mar 2014 | CN |
| 0695069 | Jan 1996 | EP |
| 1006695 | Jun 2000 | EP |
| 1453286 | Jan 2004 | EP |
| 1511337 | Mar 2005 | EP |
| 1560381 | Aug 2005 | EP |
| 1596616 | Nov 2005 | EP |
| 1608113 | Dec 2005 | EP |
| 1798998 | Jun 2007 | EP |
| 1807944 | Jul 2007 | EP |
| 1858209 | Nov 2007 | EP |
| 2019512 | Dec 2007 | EP |
| 1892895 | Feb 2008 | EP |
| 1981224 | Oct 2008 | EP |
| 2028909 | Feb 2009 | EP |
| 2061192 | May 2009 | EP |
| 2244499 | Oct 2010 | EP |
| 2271168 | Jan 2011 | EP |
| 2654369 | Oct 2013 | EP |
| 2667679 | Nov 2013 | EP |
| 2592895 | Jul 2014 | EP |
| 1105132 | Dec 2011 | HK |
| 09-055764 | Feb 1997 | JP |
| H0955764 | Feb 1997 | JP |
| 11-313370 | Nov 1999 | JP |
| 11-331947 | Nov 1999 | JP |
| 2000-174820 | Jun 2000 | JP |
| 2000-261372 | Sep 2000 | JP |
| 2001074820 | Mar 2001 | JP |
| 2001-275168 | Oct 2001 | JP |
| 2002061372 | Feb 2002 | JP |
| 2003-037874 | Feb 2003 | JP |
| 2004-032391 | Jan 2004 | JP |
| 2005-175831 | Jun 2005 | JP |
| 2005-525760 | Aug 2005 | JP |
| 2006-510244 | Mar 2006 | JP |
| 2006-518125 | Aug 2006 | JP |
| 2007-166627 | Jun 2007 | JP |
| 2007312393 | Nov 2007 | JP |
| 2008-509627 | Mar 2008 | JP |
| 2009-504047 | Jan 2009 | JP |
| 2009-508372 | Feb 2009 | JP |
| 2009-534980 | Sep 2009 | JP |
| 2011-504020 | Jan 2011 | JP |
| 2011504021 | Jan 2011 | JP |
| 2011504022 | Jan 2011 | JP |
| 2012257314 | Dec 2012 | JP |
| 10-1116549 | Feb 2012 | KR |
| 476205 | Feb 2002 | TW |
| WO0062435 | Oct 2000 | WO |
| WO0062449 | Oct 2000 | WO |
| WO0152574 | Jul 2001 | WO |
| WO0233853 | Apr 2002 | WO |
| 03105519 | Dec 2003 | WO |
| WO2004032391 | Apr 2004 | WO |
| WO2004056142 | Jul 2004 | WO |
| WO2004079542 | Sep 2004 | WO |
| 2005013515 | Feb 2005 | WO |
| WO2005029813 | Mar 2005 | WO |
| WO2005050917 | Jun 2005 | WO |
| WO2005064962 | Jul 2005 | WO |
| 2005012010 | Dec 2005 | WO |
| WO2005120104 | Dec 2005 | WO |
| 2006009714 | Jan 2006 | WO |
| 2006009714 | Jan 2006 | WO |
| WO2006016784 | Feb 2006 | WO |
| WO2006029054 | Mar 2006 | WO |
| WO2007023366 | Mar 2007 | WO |
| WO2007023812 | Mar 2007 | WO |
| WO2007025138 | Mar 2007 | WO |
| 2007052753 | May 2007 | WO |
| WO2007052098 | May 2007 | WO |
| WO2007073118 | Jun 2007 | WO |
| WO2007097670 | Aug 2007 | WO |
| WO2007123351 | Nov 2007 | WO |
| WO2007125462 | Nov 2007 | WO |
| 2008076991 | Jun 2008 | WO |
| WO2008108143 | Sep 2008 | WO |
| 2009062303 | May 2009 | WO |
| WO2009062302 | May 2009 | WO |
| WO2009104086 | Aug 2009 | WO |
| WO2010006204 | Jan 2010 | WO |
| 2011079379 | Jul 2011 | WO |
| Entry |
|---|
| 3GPP ETSI TS 123 034, v3.3.0, Digital Cellular Telecommunications System (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); High Speed Circuit Switched Data (HSCSD)—Stage 2, Dec. 2000 (21 pages). |
| 3GPP TS 25.331, v6.7.0 (Sep. 2005), (9 pages). |
| 3GPP TSG RAN WG2, #46bis, Tdoc R2-051493, Siemens, “Stored Configurations in UTRAN—Principles and Mechanism”, Athens, Greece, May 8-13, 2005 (7 pages). |
| 3GPP TSG RAN-WG#2 Meeting #17, Tdoc R2-002255, Sophia Antipolis, France, Nov. 13-17, 2000 (19 pages). |
| 3GPP TSG SA WG 3 (Security) Meeting #11, S3-000131, Mainz, Germany, Feb. 22-24, 2000 (11 pages). |
| 3GPP TSG-RAN WG2 #63 bis, R2-085726, Prague, CZ, Sep. 29-Oct. 3, 2008 (6 pages). |
| 3GPP TSG-RAN WG2 Meeting #11, R2-000660, Turin, Italy, Feb. 28-Mar. 3, 2000 (9 pages). |
| 3GPP TSG-RAN WG2, #59, R2-073707, Motorola, “DRX for NRT and RT services”, Athens, Greece, Aug. 20-24, 2007 (1 page). |
| Australian Examination Report dated Jul. 8, 2013, issued in Australian Application No. 2010320843, (3 pages). |
| Australian Examination Report dated Nov. 18, 2013, issued in Australian Application No. 2010323195, (4 pages). |
| Australian Examination Report dated Nov. 18, 2013, issued in Australian Application No. 2012207044, (4 pages). |
| Australian First Examination Report dated Jul. 30, 2013, issued in Australian Application No. 2010321205, (2 pages). |
| Australian First Examination Report dated Sep. 26, 2013, issued in Australian Application No. 2010321204, (4 pages). |
| Australian Second Examination Report dated Jul. 9, 2014, issued in Australian Application No. 2010321205, (3 pages). |
| Canadian Office Action dated Aug. 21, 2014, issued in Canadian Application No. 2,743,128, (3 pages). |
| Canadian Office Action dated Aug. 9, 2013, issued in Canadian Application No. 2,743,128, (3 pages). |
| Canadian Office Action dated Feb. 27, 2014, issued in Canadian Application No. 2,589,373, (3 pages). |
| Canadian Office Action dated May 13, 2014, issued in Canadian Application No. 2,781,630, (3 pages). |
| Canadian Office Action dated May 20, 2014, issued in Canadian Application No. 2,781,558, (2 pages). |
| Canadian Office Action dated May 8, 2014, issued in Canadian Application No. 2,781,509, (2 pages). |
| Canadian Office Action dated May 8, 2014, issued in Canadian Application No. 2,785,826, (2 pages). |
| Canadian Office Action dated May 9, 2014, issued in Canadian Application No. 2,781,562, (3 pages). |
| Canadian Office Action dated Oct. 11, 2013, issued in Canadian Application No. 2,571,101, (7 pages). |
| Chinese First Office Action dated Aug. 15, 2014, issued in Chinese Application No. 201080062007.6, (7 pages). |
| Chinese First Office Action dated Jul. 15, 2014, issued in Chinese Application No. 201080062010.8, (16 pages). |
| Chinese First Office Action dated Jul. 2, 2014, issued in Chinese Application No. 201080062345.X, (9 pages). |
| Chinese First Office Action dated Jul. 25, 2014, issued in Chinese Application No. 201080062001.9, (3 pages). |
| Chinese First Office Action dated Jul. 25, 2014, issued in Chinese Application No. 201080062006.1, (6 pages). |
| Chinese First Office Action dated Jun. 5, 2014, issued in Chinese Application No. 201210213644.X, (13 pages). |
| Chinese Fourth Office Action dated Oct. 11, 2013, issued in Chinese Application No. 200880124457.6, (3 pages). |
| Chinese Second Office Action dated Jun. 5, 2013, issued in Chinese Application No. 200880124414.8, (8 pages). |
| Chinese Second Office Action dated Nov. 5, 2013, issued in Chinese Application No. 200980144537.2, (10 pages). |
| Chinese Third Office Action dated Dec. 25, 2013, issued in Chinese Application No. 200880124414.8, (7 pages). |
| Chinese Third Office Action dated Jul. 11, 2013, issued in Chinese Application No. 200880124457.6, (29 pages). |
| European Communication—Invitation Pursuant to Article 94(3) and Rule 71(1) EPC dated Apr. 14, 2014, issued in European Application No. 08849315.0, (4 pages). |
| European Examination Report dated Apr. 30, 2014, issued in European Application No. 08849731.8, (5 pages). |
| European Examination Report dated Jan. 3, 2014, issued in European Application No. 09752972.1, (8 pages). |
| European Examination Report dated Oct. 30, 2013, issued in European Application No. 09180936.8, (7 pages). |
| Extended European Search Report dated Jul. 16, 2014, issued in European Application No. 13181054.1, (8 pages). |
| Final Office Action dated Apr. 8, 2014, issued in U.S. Appl. No. 13/673,398, (10 pages). |
| Final Office Action dated Aug. 30, 2013, issued in U.S. Appl. No. 12/953,049, (19 pages). |
| Final Office Action dated Feb. 10, 2014, issued in U.S. Appl. No. 13/921,728, (16 pages). |
| Final Office Action dated Feb. 13, 2014, issued in U.S. Appl. No. 13/532,353, (14 pages). |
| Final Office Action dated Jul. 22, 2014, issued in U.S. Appl. No. 12/953,223, (12 pages). |
| Final Office Action dated May 13, 2014, issued in U.S. Appl. No. 11/467,309, (19 pages). |
| Final Office Action dated May 8, 2014, issued in U.S. Appl. No. 12/616,024, (26 pages). |
| Final Office Action dated Sep. 27, 2013, issued in U.S. Appl. No. 13/157,724, (9 pages). |
| Indonesian Office Action dated Dec. 23, 2013, issued in Indonesian Application No. W00201202454, (6 pages). |
| Indonesian Office Action dated Feb. 27, 2014, issued in Indonesian Appl. No. W00201102002, (4 pages). |
| Indonesian Office Action dated Feb. 27, 2014, issued in Indonesian Appl. No. W00201202452, (4 pages). |
| Indonesian Office Action dated Nov. 15, 2013, issued in Indonesian Application No. W00201202451, (4 pages). |
| Japanese Office Action dated Apr. 2, 2014, issued in Japanese Application No. 2012-539362, (13 pages). |
| Japanese Office Action dated Aug. 2, 2013, issued in Japanese Application No. 2012-539362, (9 pages). |
| Japanese Office Action dated Aug. 27, 2013, issued in Japanese Application No. 2010-085595, (9 pages). |
| Japanese Office Action dated Aug. 7, 2013, issued in Japanese Application No. 2012-539244, (5 pages). |
| Japanese Office Action dated Aug. 7, 2013, issued in Japanese Application No. 2012-539245, (5 pages). |
| Japanese Office Action dated Dec. 6, 2013, issued in Japanese Application No. 2013-023208, (4 pages). |
| Japanese Office Action dated Jul. 25, 2013, issued in Japanese Application No. 2012-539363, (5 pages). |
| Japanese Office Action dated Nov. 25, 2013, issued in Japanese Application No. 2012-185846, (8 pages). |
| Japanese Office Action dated Nov. 25, 2013, issued in Japanese Application No. 2012-539363, (8 pages). |
| Japanese Office Action dated Nov. 26, 2013, issued in Japanese Application No. 2012-241734, (7 pages). |
| Japanese Office Action dated Nov. 28, 2013, issued in Japanese Application No. 2012-241739, (8 pages). |
| Japanese Office Action dated Sep. 3, 2013, issued in Japanese Application No. 2012-549266, (7 pages). |
| Korean Final Office Action dated Aug. 4, 2014, issued in Korean Application No. 10-2012-7016425, (4 pages). |
| Korean Final Office Action dated Feb. 3, 2014, issued in Korean Application No. 10-2012-7016427, w/English translation outlining Office Action and of Argument Brief, (7 pages). |
| Korean Final Office Action dated Mar. 31, 2014, issued in Korean Application No. 10-2012-7016424, (3 pages). |
| Korean Final Office Action dated Mar. 31, 2014, issued in Korean Application No. 10-2012-7016425, (3 pages). |
| Korean Notice of Allowance dated Feb. 5, 2014, issued in Korean Application No. 10-2011-7021074, (5 pages). |
| Korean Notice of Allowance dated Feb. 7, 2014, issued in Korean Application No. 10-2011-7021393, (7 pages). |
| Korean Notice of Allowance dated Mar. 31, 2014, issued in Korean Application No. 10-2012-7016426, (3 pages). |
| Korean Office Action dated Apr. 15, 2014, issued in Korean Application No. 10-2012-7016423, (3 pages). |
| Korean Office Action dated Aug. 6, 2014, issued in Korean Application No. 10-2014-7012197, (4 pages). |
| Korean Office Action dated Jan. 24, 2014, issued in Korean Application No. KR-10-2011-7021391, with English translation outlining Office Action and of Argument Brief, (5 pages). |
| Korean Office Action dated Oct. 18, 2013, issued in Korean Application No. 10-2011-7021074, (6 pages). |
| Korean Office Action dated Oct. 18, 2013, issued in Korean Application No. 10-2011-7021393, (6 pages). |
| Korean Office Action dated Oct. 25, 2013, issued in Korean Application No. 10-2012-7016424, (9 pages). |
| Korean Office Action dated Oct. 28, 2013, issued in Korean Application No. 10-2012-7016425, (9 pages). |
| Korean Office Action dated Oct. 29, 2013, issued in Korean Application No. KR-10-2012-7016426, (8 pages). |
| Korean Office Action dated Oct. 29, 2013, issued in Korean Application No. KR-10-2012-7016427, (7 pages). |
| Mexican Notice of Allowance dated Aug. 27, 2014, issued in Mexican Application No. MX/a/2012/005871, (9 pages). |
| Mexican Notice of Allowance dated Nov. 8, 2013, issued in Mexican Application No. MX/a/2013/003651, (6 pages). |
| Mexican Notice of Allowance dated Sep. 6, 2013, issued in Mexican Application No. MX/a/2012/009440, (8 pages). |
| Mexican Office Action dated Mar. 24, 2014, issued in Mexican Application No. MX/a/2012/005871, (8 pages). |
| Mexican Office Action dated Mar. 24, 2014, issued in Mexican Application No. MX/a/2012/005874, (4 pages). |
| Mexican Office Action dated May 12, 2014, issued in Mexican Application No. MX/a/2012/005875, (6 pages). |
| Mexican Third Office Action dated May 30, 2012, issued in Mexican Application No. MX/a/2010/005255, (7 pages). |
| Notice of Allowance dated Aug. 12, 2014, issued in U.S. Appl. No. 13/157,724, (11 pages). |
| Notice of Allowance dated Aug. 15, 2014, issued in U.S. Appl. No. 12/616,024, (5 pages). |
| Notice of Allowance dated Jul. 8, 2014, issued in U.S. Appl. No. 13/584,381, (19 pages). |
| Notice of Allowance dated Nov. 5, 2013, issued in U.S. Appl. No. 12/844,302, (26 pages). |
| Notice of Allowance dated Sep. 12, 2014, issued in U.S. Appl. No. 13/673,398, (8 pages). |
| Notice of Allowance dated Sep. 30, 2013, issued in U.S. Appl. No. 11/464,380, (20 pages). |
| Notice of Allowance dated Sep. 8, 2014, issued in U.S. Appl. No. 13/244,849, (9 pages). |
| Office Action dated Apr. 25, 2014, issued in U.S. Appl. No. 13/244,849, (32 pages). |
| Office Action dated Apr. 28, 2014, issued in U.S. Appl. No. 12/649,461, (27 pages). |
| Office Action dated Dec. 20, 2013, issued in U.S. Appl. No. 13/584,381, (36 pages). |
| Office Action dated Feb. 10, 2014, issued in U.S. Appl. No. 12/953,223, (53 pages). |
| Office Action dated Jan. 2, 2014, issued in U.S. Appl. No. 13/673,398, (33 pages). |
| Office Action dated Jan. 30, 2014, issued in U.S. Appl. No. 11/467,309, (57 pages). |
| Office Action dated Jul. 14, 2014, issued in U.S. Appl. No. 13/587,073, (34 pages). |
| Office Action dated Jun. 18, 2014, issued in U.S. Appl. No. 12/897,945, (33 pages). |
| Office Action dated Jun. 18, 2014, issued in U.S. Appl. No. 12/897,959, (26 pages). |
| Office Action dated Jun. 18, 2014, issued in U.S. Appl. No. 12/953,049, (18 pages). |
| Office Action dated Jun. 19, 2014, issued in U.S. Appl. No. 13/244,761, (17 pages). |
| Office Action dated Jun. 9, 2014, issued in U.S. Appl. No. 13/532,353, (5 pages). |
| Office Action dated Jun. 9, 2014, issued in U.S. Appl. No. 13/921,728, (5 pages). |
| Office Action dated Mar. 6, 2014, issued in U.S. Appl. No. 12/953,049, (9 pages). |
| Office Action dated Mar. 6, 2014, issued in U.S. Appl. No. 13/244,761, (8 pages). |
| Office Action dated Oct. 15, 2013, issued in U.S. Appl. No. 13/532,353, (12 pages). |
| Office Action dated Sep. 17, 2013, issued in U.S. Appl. No. 13/921,728, (25 pages). |
| Office Action dated Sep. 18, 2013, issued in U.S. Appl. No. 12/616,024, (19 pages). |
| Partial European Search Report dated Jun. 13, 2014, issued in European Application No. 13177318.6, (5 pages). |
| Taiwan Office Action dated Jun. 3, 2014, issued in Taiwanese Application No. 096131703, (9 pages). |
| Taiwan Office Action dated Mar. 7, 2014, issued in Taiwan Application No. 096117599, (7 pages). |
| Taiwan Office Action dated Mar. 7, 2014, issued in Taiwan Application No. 100110649, (9 pages). |
| Talukdar et al., IEEE Xplore Digital Library, “Radio Resource Control Protocol Configuration for Optimum Web Browsing”, published in Vehicular Technology Conference, 2002. Proceedings VTC 2002-Fall, IEEE 56th, vol. 3 (3 pages). |
| TSG-RAN Working Group 2 (Radio layer 2 and Radio layer 3), R2-002259, Ericsson, “Handling of “out of service” area”, Sophia Antipolis, France, Nov. 13-17, 2000 (3 pages). |
| “3rd Generation Partnership Project 2; Data Service Options for Spread Spectrum Systems,” 3GPP2 C.S0017-0, Version 5.0, Feb. 17, 2003 (70 pgs.). |
| “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.). |
| “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.). |
| “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.). |
| “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.). |
| “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),” 3GPPTS 36.300 V8.9.0 (Jun. 2009) (159 pages). |
| “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.). |
| “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.). |
| “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.). |
| “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). |
| “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.). |
| “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 pages). |
| “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 pages). |
| “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.). |
| “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.). |
| “3rd Generation Partnership Project2; 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.). |
| “Digital Cellular Telecommunications System (Phase 2+)”; ETSI Standards European Telecommunications Standards Institute, Sophia-Antipo, FR, vol. 3-SA2, No. V6110, Dec. 2005, XP014032437 (17 pgs.). |
| 3GPP 25.331 Radio Resource Control (RRC); Protocol Specification, V5.18.0 (Sep. 2006), pp. 12-13. |
| 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). |
| 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). |
| 3GPP TS 25.331 Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol Specification, V8.8.0 (Release 8) (Oct. 2009) Section 8.1.14 (pp. 141-143) and Sections 13.1 and 13.2 (pp. 1430-1432). |
| 3GPP TS 25.331 V5.16.0 (Mar. 2006) (1045 pgs.). |
| 3GPP TSG RAN WG#2 Meeting #67, R2-094437, Shenzhen, People's Republic of China, Aug. 24-28, 2009 (57 pages). |
| 3GPP TSG RAN WG2 #63bis; R2-085921; Prague, Czech Republic; Sep. 29-Oct. 3, 2008 (38 pgs). |
| 3GPP TSG-RAN WG2 Meeting #60, R2-074848, Vodafone, Rim, Huawei, Title: UE “Fast Dormancy” Behaviour, Nov. 5-9, 2007, Jeju, South Korea, (9 pages). |
| 3GPP TSG-RAN WG2 Meeting #60, R2-075251, Jeju, South Korea, Nov. 5-9, 2007 (13 pages). |
| 3GPP TSG-RAN WG2 Meeting #62bis, R2-083626, Warsaw, Poland, Jun. 30-Jul. 4, 2008 (11 pages). |
| 3GPP TSG-RAN WG2 Meeting #63, R2-084647, Jeju, South Korea, Aug. 18-22, 2008 (14 pages). |
| 3GPP TSG-RAN WG2 Meeting #63bis, R2-085584, Prague, Czech Republic, Sep. 29-Oct. 3, 2008 (5 pgs). |
| 3GPP TSG-RAN WG2 Meeting #68, R2-097173, Jeju, South Korea, Nov. 9-13, 2009 (5 pages). |
| 3GPP TSG-RAN WG2 Meeting #68, R2-097174, Jeju, South Korea, Nov. 9-13, 2009 (8 pages). |
| 3GPP TSG-RAN WG2 Meeting #69, R2-101710, San Francisco, California, Feb. 22-26, 2010 (6 pages). |
| 3GPP TSG-RAN WG2 Meeting #69, R2-101726, San Francisco, California, Feb. 22-26, 2010 (6 pages). |
| 3GPP TSG-RAN WG2#67bis; R2-096027; Miyazaki, Japan, Oct. 12-16, 2009 (4 pages). |
| 3GPP TSG-RAN WG2#68, R2-096624, Jeju, South Korea, Nov. 9-13, 2009 (8 pages). |
| 3GPP TSG-RAN2 Meeting #63bis, R2-085134, Prague, Czech, Sep. 29-Oct. 3, 2008 (13 pgs). |
| 3GPP TSG-RAN2 Meeting #64 R2-086557, Prague, Czech, Nov. 10-14, 2008 (13 pages). |
| 3GPP TSG-RAN2 Meeting #67; R2-094792; Shenzhen, China, Aug. 24-28, 2009 (10 pages). |
| 3GPP TSG-RAN2 Meeting #69, R2-101440, San Francisco, CA, Feb. 22-26, 2010 (18 pages). |
| 3GPP TSG-RAN2 Meeting #69, R2-101441, San Francisco, CA, Feb. 22-26, 2010 (20 pages). |
| 3GPP: “Radio resource control (RRC) protocol specification V7.0.0,” 3GPP TS25.331 V7.0.0, (Mar. 2006), (1,249 pgs.). |
| 3GPP: Radio Resource Control Protocol Specification for UE-UTRAN radio interface, 3GPP TS 25.331 V6.8.0 (Dec. 2005) (1,174 pgs.). |
| 3rd 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 (70 pgs.). |
| 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.). |
| Australian First Examination Report dated Apr. 9, 2008, issued in Australian Appplication No. 2006252042 (this reference relates to U.S. Appl. No. 11/302,263) (2 pgs.). |
| Australian First Examination Report dated Feb. 13, 2013, issued in Australian Application No. 2009313191 (3 pages). |
| Australian First Examination Report dated Feb. 3, 2012, issued in Australian Application No. 2010202720 (16 pages). |
| Australian First Examination Report dated Sep. 2, 2008, issued in Australian Application No. 2007202206 (this reference relates to U.S. Appl. No. 11/464,380) (7 pgs.). |
| Australian Second Examination Report dated Sep. 30, 2009, issued in Australian Application No. 2007202206 (this reference relates to U.S. Appl. No. 11/464,380) (1 pg.). |
| Canadian Office Action dated Apr. 30, 2012, issued in Canadian Patent Application No. 2,571,101 (4 pages). |
| Canadian Office Action dated Feb. 22, 2011, issued in Canadian Application 2,589,373 (5 pages). |
| Canadian Office Action dated Jul. 20, 2012, issued in Canadian Patent Application No. 2,705,477 (4 pages). |
| Canadian Office Action dated Jun. 18, 2012, issued in Canadian Patent Application No. 2,661,592 (5 pages). |
| Canadian Office Action dated Jun. 21, 2012, issued in Canadian Application No. 2,705,476 (3 pages). |
| Canadian Office Action dated Jun. 21, 2012, issued in Canadian Patent Application No. 2,705,478 (4 pages). |
| Canadian Office Action dated Mar. 16, 2010, issued in Canadian Patent Application No. 2,571,101 (5 pages). |
| Canadian Office Action dated May 31, 2012, issued in Canadian Patent Application No. 2,589,373 (3 pages). |
| Canadian Office Action dated Nov. 14, 2011, issued in Canadian Application No. 2,661,592 (3 pages). |
| Chinese First Office Action dated Apr. 25, 2011, issued in Chinese Application No. 2007101379068 (13 pages). |
| Chinese First Office Action dated Aug. 2, 2012, issued in Chinese Application No. 200880124457.6 (26 pages). |
| Chinese First Office Action dated Aug. 3, 2012, issued in Chinese Application No. 200880124414.8 (10 pages). |
| Chinese First Office Action dated Feb. 6, 2009, issued in Chinese Application No. 200610064329.X (18 pages). |
| Chinese First Office Action dated Oct. 31, 2012, issued in Chinese Application No. 200880124114.X (10 pages). |
| Chinese Fourth Office Action dated Mar. 18, 2013, issued in Chinese Application No. 200710137906.8 (7 pages). |
| Chinese Notification of Grant of Rights for Invention Patent dated Apr. 9, 2012, issued in Chinese Patent Application No. 200610064329.X (2 pages). |
| Chinese Second Office Action dated Feb. 2, 2012, issued in Chinese Application No. 200710137906.8 (7 pages). |
| Chinese Second Office Action dated Feb. 24, 2010, issued in Chinese Application No. 200610064329.X (including translation) (this reference relates to U.S. Appl. No. 11/302,263) (18 pgs.). |
| Chinese Second Office Action dated Jan. 30, 2013, issued in Chinese Application No. 200880124457.6 (25 pages). |
| Chinese Third Office Action dated Aug. 27, 2012, issued in Chinese Application No. 200710137906.8 (12 pages). |
| Chinese Third Office Action dated Oct. 8, 2011, issued in Chinese Application No. 200610064329.X (7 pages). |
| European Communication dated Jul. 18, 2012, issued in European Application No. 10771051.9 (2 pages). |
| European Communication dated Jul. 19, 2012, issued in European Application No. 10768896.2 (2 pages). |
| European Communication dated Jul. 19, 2012, issued in European Application No. 10798525.1 (2 pages). |
| European Communication dated Jul. 25, 2012, issued in European Application No. 10790529.1 (2 pages). |
| European Examination Report dated Apr. 19, 2012, issued in European Application No. 08849315.0 (5 pages). |
| European Examination Report dated Apr. 19, 2012, issued in European Application No. 08849731.8 (5 pages). |
| European Examination Report dated Aug. 10, 2009, issued in European Application No. 08154976.8 (4 pages). |
| European Examination Report dated Aug. 8, 2011, issued in European Application No. 07121138.7 (5 pages). |
| European Examination Report dated Aug. 8, 2011, issued in European Application No. 10184515.4 (7 pages). |
| European Examination Report dated Dec. 15, 2011, issued in European Application No. 10 184 515.4 (7 pages). |
| European Examination Report dated Dec. 28, 2011, issued in European Application No. 08154976.8 (3 pages). |
| European Examination Report dated Feb. 14, 2013, issued in European Application No. 08849315.0 (6 pages). |
| European Examination Report dated Feb. 21, 2013, issued in European Application No. 08849731.8 (5 pages). |
| European Examination Report dated Jan. 24, 2008, issued in European Application No. 05112183.8 (2 pages). |
| European Examination Report dated Jul. 30, 2009, issued in European Application No. 06118909.8 (this reference relates to U.S. Appl. No. 11/464,380) (3 pgs.). |
| European Examination Report dated Jun. 25, 2008, issued in European Application No. 06118909.8 (this reference relates to U.S. Appl. No. 11/464,380) (3 pgs.). |
| European Examination Report dated May 22, 2012, issued in European Application No. 10184515.4 (9 pages). |
| European Examination Report dated Nov. 12, 2007, issued in European Application No. 06118909.8 (this reference relates to U.S. Appl. No. 11/464,380) (4 pgs.). |
| European Examination Report dated Nov. 15, 2011, issued in European Application No. 11160318.9 (4 pages). |
| European Examination Report dated Oct. 25, 2007, issued in European Application No. 06119590.5 (7 pages). |
| European Examination Report dated Sep. 7, 2009, issued in European Application No. 05112183.8 (3 pages). |
| European Examination Report dated Sep. 7, 2009, issued in European Application No. 07121138.7 (1 page). |
| European Examinaton Report dated Oct. 19, 2010, issued in European Application No. 07121138.7 (8 pages). |
| European Intent to Grant dated Apr. 13, 2012, issued in European Application No. 10183886.0 (5 pages). |
| European Intent to Grant dated Dec. 17, 2010, issued in European Application No. 05112183.8 (41 pages). |
| European Intent to Grant dated Jan. 26, 2012, issued in European Application No. 07121138.7 (66 pages). |
| European Intent to Grant dated Oct. 20, 2011, issued in European Application No. 10170815.4 (1 page). |
| European Summons to Attend Oral Proceedings dated Jan. 28, 2011, issued in European Application No. 08154976.8 (10 pages). |
| Extended European Search Report dated Apr. 12, 2013, issued in European Application No. 13152938.0 (10 pages). |
| Extended European Search Report dated Apr. 12, 2013, issued in European Application No. 13152942.2 (10 pages). |
| Extended European Search Report dated Apr. 16, 2013, issued in European Application No. 13159334.5 (10 pages). |
| Extended European Search Report dated Jan. 18, 2011, issued in European Application No. 08849315.0 (8 pages). |
| Extended European Search Report dated Jan. 18, 2011, issued in European Application No. 08849731.8 (7 pages). |
| Extended European Search Report dated Jun. 21, 2011, issued in European Application No. 10174218.7 (7 pages). |
| Extended European Search Report dated Jun. 24, 2011, issued in European Application No. 11160318.9 (5 pages). |
| Extended European Search Report dated Mar. 20, 2007, issued in European Application No. 06119590.5 (11 pages). |
| Extended European Search Report dated May 16, 2008, issued in European Application No. 07121138.7 (this reference relates to U.S. Appl. No. 11/454,380) (10 pages). |
| Extended European Search Report dated May 20, 2010, issued in European Application No. 09180936.8 (9 pages). |
| Extended European Search Report dated May 3, 2007, issued in European Application No. 05112183.8 (7 pages). |
| Extended European Search Report dated Nov. 15, 2010, issued in European Application No. 10183886.0 (3 pages). |
| Extended European Search Report dated Nov. 19, 2010, issued in European Application No. 10184515.4 (this refrence relates to U.S. Appl. No. 11/454,380) (7 pages). |
| Extended European Search Report dated Nov. 2, 2010, issued in European Application No. 10170815.4 (5 pages). |
| Extended European Search Report dated Nov. 22, 2012, issued in European Application No. 11177172.1 (6 pages). |
| Extended European Search Report dated Nov. 24, 2006, issued in European Application No. 06118909.8 (this reference relates to U.S. Appl. No. 11/464,380) (8 pages). |
| Extended European Search Report dated Nov. 29, 2012, issued in European Application No. 11177171.3 (7 pages). |
| Extended European Search Report dated Sep. 3, 2008, issued in European Application 08154976.8 (7 pages). |
| Final Office Action dated Aug. 15, 2013, issued in U.S. Appl. No. 13/244,761, (21 pages). |
| Final Office Action dated Apr. 20, 2011, issued in U.S. Appl. No. 12/195,018 (33 pages). |
| Final Office Action dated Dec. 22, 2010, issued in U.S. Appl. No. 11/464,380 (21 pages). |
| Final Office Action dated Dec. 24, 2012, issued in U.S. Appl. No. 12/616,024 (56 pages). |
| Final Office Action dated Feb. 10, 2012, issued in U.S. Appl. No. 12/195,018 (14 pages). |
| Final Office Action dated Feb. 15, 2012, issued in U.S. Appl. No. 12/844,302 (9 pages). |
| Final Office Action dated Feb. 26, 2013, issued in U.S. Appl. No. 12/897,945 (13 pages). |
| Final Office Action dated Feb. 27, 2013, issued in U.S. Appl. No. 12/953,144 (8 pages). |
| Final Office Action dated Jan. 21, 2010, issued in U.S. Appl. No. 11/467,309 (25 pages). |
| Final Office Action dated Jul. 12, 2012, issued in U.S. Appl. No. 13/244,761 (26 pages). |
| Final Office Action dated Jul. 20, 2010, issued in U.S. Appl. No. 11/467,309 (30 pages). |
| Final Office Action dated Jun. 26, 2013, issued in U.S. Appl. No. 13/532,353 (15 pages). |
| Final Office Action dated Mar. 22, 2012, issued in U.S. Appl. No. 13/244,849 (18 pages). |
| Final Office Action dated Mar. 25, 2013, issued in U.S. Appl. No. 12/897,959 (22 pages). |
| Final Office Action dated May 23, 2013, issued in U.S. Appl. No. 11/464,380 (22 pages). |
| Final Office Action dated Nov. 10, 2011, issued in U.S. Appl. No. 12/107,514 (13 pages). |
| Final Office Action dated Nov. 14, 2011, issued in U.S. Appl. No. 11/467,309 (29 pages). |
| Final Office Action dated Nov. 23, 2011, issued in U.S. Appl. No. 12/844,302 (16 pages). |
| Final Office Action dated Oct. 11, 2012, issued in U.S. Appl. No. 12/649,461 (19 pages). |
| Final Office Action dated Sep. 13, 2012, issued in U.S. Appl. No. 12/953,049 (18 pages). |
| Indian Office Action dated Apr. 7, 2011, issued in Indian Application No. 2672/DEL/2006 (2 pages). |
| Japanese Office Action dated Apr. 26, 2012, issued in Japanese Application No. 2010-533397 (8 pages). |
| Japanese Office Action dated Dec. 3, 2009, issued in Japanese Application No. 2006-335943 (this reference relates to U.S. Appl. No. 11/302,263) (6 pgs.). |
| Japanese Office Action dated Jun. 20, 2012, issued in Japanese Application No. 2010-533398 (9 pages). |
| Japanese Office Action dated Jun. 23, 2009, issued in Japanese Application No. 2006-335943 (this reference relates to U.S. Appl. No. 11/302,263) (10 pgs.). |
| Japanese Office Action dated Jun. 4, 2012, issued in Japanese Application No. 2011-083176 (7 pages). |
| Japanese Office Action dated May 31, 2012, issued in Japanese Application No. 2010-533396 (5 pages). |
| Japanese Office Action dated Nov. 12, 2012, issued in Japanese Application No. 2011-535770 (7 pages). |
| Japanese Office Action dated Oct. 29, 2012, issued in Japanese Application No. 2010-085595 (6 pages). |
| Japanese Office Action dated Sep. 30, 2010, issued in Japanese Application No. 2007-131146 (7 pages). |
| KIPO Notice of Decision for Patent Application No. 10-2010-7012925 dated Nov. 30, 2011 with translation (4 pages). |
| Korean Application No. 10-2008-0092802, filed on Oct. 16, 2008, including English equivalent EP 1981224 (31 total pages). |
| Korean Notice of Decision for Patent, for Korean Patent Application No. 10-2010-7012701, dated Mar. 8, 2012 (3 pages). |
| Korean Notice of Decision for Patent, for Korean Patent Application No. 10-2010-7012778, dated Mar. 26, 2012 (7 pages). |
| Korean Notice Requesting Submission of Opinion dated Aug. 28, 2008, issued in Korean Application No. 10-2006-0128027 (this reference relates to U.S. Appl. No. 11/302,263) (6 pgs). |
| Korean Notice Requesting Submission of Opinion dated Nov. 26, 2007, issued in Korean Application No. 10-2006-0128027 (this reference relates to U.S. Appl. No. 11/302,263) (8 pgs.). |
| Korean Office Action dated Aug. 13, 2012, issued in Korean Application No. 10-2011-7012708 (6 pages). |
| Korean Office Action dated Feb. 26, 2013, issued in Korean Application No. 10-2011-7012708 (9 pages). |
| Korean Office Action dated Jan. 17, 2013, issued in Korean Application No. 10-2012-7026886 (8 pages). |
| Korean Office Action dated Jul. 11, 2011, issued in Korean Application No. 10-2010-7012701 (11 pages, including translation). |
| Korean Office Action dated Jul. 11, 2011, issued in Korean Application No. 10-2010-7012925 (6 pages, including translation). |
| Mexican Office Action dated Feb. 13, 2012, issued in Mexican Application No. MX/a/2010/005255 (9 pages). |
| Mexican Office Action dated Jan. 11, 2013, issued in Mexican Application No. MX/a/2010/005249 (4 pages). |
| Mexican Office Action dated Jan. 11, 2013, issued in Mexican Application No. MX/a/2010/005251 (4 pages). |
| Mexican Office Action dated Jul. 13, 2012, issued in Mexican Application No. MX/a/2011/004888 (7 pages). |
| Notice of Allowance dated Apr. 5, 2012, issued in U.S. Appl. No. 12/270,562 (27 pages). |
| Notice of Allowance dated Feb. 28, 2011, issued in U.S. Appl. No. 11/302,263 (15 pages). |
| Notice of Allowance dated Jun. 25, 2012, issued U.S. Appl. No. 13/244,749 (13 pages). |
| Notice of Allowance dated Jun. 28, 2012, issued in U.S. Appl. No. 13/244,765 (8 pages). |
| Notice of Allowance dated Mar. 10, 2011, issued in U.S. Appl. No. 12/270,522 (34 pages). |
| Notice of Allowance dated May 2, 2012, issued in U.S. Appl. No. 12/195,018 (4 pages). |
| Notice of Allowance dated Nov. 28, 2011, issued in U.S. Appl. No. 13/244,792 (19 pages). |
| Office Action dated Apr. 14, 2011, issued in U.S. Appl. No. 12/107,514 (38 pages). |
| Office Action dated Apr. 17, 2012, issued in U.S. Appl. No. 13/244,765 (12 pages). |
| Office Action dated Apr. 19, 2013, issued in U.S. Appl. No. 13/157,724 (44 pages). |
| Office Action dated Apr. 7, 2011, issued in U.S. Appl. No. 12/270,562 (19 pages). |
| Office Action dated Dec. 15, 2011, issued in U.S. Appl. No. 13/244,761 (35 pages). |
| Office Action dated Dec. 15, 2011, issued in U.S. Appl. No. 13/244,849 (26 pages). |
| Office Action dated Dec. 21, 2011, issued in U.S. Appl. No. 13/244,749 (29 pages). |
| Office Action dated Dec. 22, 2011, issued in U.S. Appl. No. 12/953,049 (19 pages). |
| Office Action dated Feb. 15, 2012, issued in U.S. Appl. No. 13/244,765 (22 pages). |
| Office Action dated Feb. 7, 2013, issued in U.S. Appl. No. 12/953,049 (8 pages). |
| Office Action dated Jan. 16, 2013, issued in U.S. Appl. No. 13/532,353 (23 pages). |
| Office Action dated Jan. 22, 2013, issued in U.S. Appl. No. 13/244,761 (10 pages). |
| Office Action dated Jan. 5, 2011, issued in U.S. Appl. No. 12/195,018 (14 pages). |
| Office Action dated Jan. 7, 2013, issued in U.S. Appl. No. 11/464,380 (12 pages). |
| Office Action dated Jul. 20, 2012, issued in U.S. Appl. No. 11/464,380 (15 pages). |
| Office Action dated Jul. 31, 2012, issued in U.S. Appl. No. 12/953,144 (30 pages). |
| Office Action dated Jun. 12, 2009, issued in U.S. Appl. No. 11/467,309 (21 pages). |
| Office Action dated Jun. 26, 2013, issued in U.S. Appl. No. 12/844,302 (19 pages). |
| Office Action dated Jun. 3, 2011, issued in U.S. Appl. No. 11/467,309 (22 pages). |
| Office Action dated Mar. 10, 2011, issued in U.S. Appl. No. 12/270,562 (36 pages). |
| Office Action dated Mar. 25, 2011, issued in U.S. Appl. No. 12/844,302 (27 pages). |
| Office Action dated Nov. 18, 2010, issued in U.S. Appl. No. 12/270,562 (19 pages). |
| Office Action dated Nov. 20, 2012, issued in U.S. Appl. No. 12/897,959 (42 pages). |
| Office Action dated Oct. 18, 2012, issued in U.S. Appl. No. 12/897,945 (34 pages). |
| Office Action dated Oct. 6, 2011, issued in U.S. Appl. No. 12/195,018 (21 pages). |
| PCT Communication dated Feb. 17, 2010, issued in International Application No. PCT/US2009/063912 (9 pages). |
| PCT International Preliminary Report on Patentability dated Dec. 18, 2008, issued in International Application PCT/CA2007/001497 (9 pages). |
| PCT International Search Report and Written Opinion dated Apr. 12, 2011, issued in International Application No. PCT/CA2010/002031 (8 pages). |
| PCT International Search Report and Written Opinion dated Dec. 12, 2007, issued in International Application PCT/CA2007/001497 (12 pages). |
| PCT International Search Report and Written Opinion dated Feb. 11, 2011, issued in International Application No. PCT/EP2010/068064 (16 pages). |
| PCT International Search Report and Written Opinion dated Feb. 11, 2011, issued in International Application No. PCT/EP2010/068065 (17 pages). |
| PCT International Search Report and Written Opinion dated Feb. 13, 2009, issued in International Application No. PCT/CA2008/002000 (10 pages). |
| PCT International Search Report and Written Opinion dated Feb. 2, 2009, issued in International Application No. PCT/CA2008/002001 (10 pages). |
| PCT International Search Report and Written Opinion dated Feb. 9, 2011, issued in International Application No. PCT/EP2010/064859 (17 pages). |
| PCT International Search Report and Written Opinion dated Jan. 15, 2009, issued in International Application No. PCT/CA2008/002002 (10 pages). |
| PCT International Search Report and Written Opinion dated Jan. 21, 2013, issued in International Application No. PCT/US2012/064499 (11 pages). |
| PCT International Search Report and Written Opinion dated Jan. 28, 2011, issued in International Application No. PCT/EP2010/064860 (12 pages). |
| PCT International Search Report and Written Opinion dated Mar. 25, 2011, issued in International Application No. PCT/EP2010/068063 (15 pages). |
| PCT International Search Report and Written Opinion dated May 3, 2010, issued in International Application PCT/US2009/063912 (22 pages). |
| PCT Preliminary Report on Patentability dated Mar. 9, 2012, issued in International Application No. PCT/CA2010/002031 (8 pages). |
| SDO Review Comment Form, SP-3-4617.12-UGR (TIA-707-B.12) C.P0017.12-A (5 pgs.). |
| Taiwan Office Action dated Aug. 30, 2012, issued in Taiwan Application No. 096131703 (8 pages). |
| Taiwan Office Action dated Jul. 29, 2011, issued in Taiwan Application No. 095146891 (5 pages). |
| Taiwan Office Action dated May 20, 2013, issued in Taiwan Application No. 096131703 (19 pages). |
| U.S. Appl. No. 12/649,461, filed Dec. 30, 2009 (87 pages). |
| U.S. Appl. No. 12/844,302, filed Jul. 27, 2010 (35 pages). |
| U.S. Appl. No. 12/897,945, filed Oct. 5, 2010 (144 pages). |
| U.S. Appl. No. 12/897,959, filed Oct. 5, 2010 (144 pages). |
| U.S. Appl. No. 12/953,049, filed Nov. 23, 2010 (146 pages). |
| U.S. Appl. No. 12/953,144, filed Nov. 23, 2010 (178 pages). |
| U.S. Appl. No. 12/953,223, filed Nov. 23, 2010 (146 pages). |
| U.S. Appl. No. 13/546,926, filed Jul. 11, 2012 (54 pages). |
| U.S. Appl. No. 13/673,398, filed Nov. 9, 2012 (42 pages). |
| U.S. Appl. No. 13/751,369, filed Jan. 28, 2013 (142 pages). |
| 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). |
| 3GPP R2-096625, “Clarification on the UE State after Fast Dormancy Request,” Jeju, Korea, Nov. 2009, 6 pages. |
| 3GPP2 specification A.S0013-0v1.0; “Interoperability Specification (IOS) for CDMA 2000 Access Network Interfaces—Part 3 Features”; Revision 0 (3G IOSv4.2); (SDO Ballot Version); Nov. 16, 2001; 281 pages. |
| 3GPP TS 25.331 v8.7.0 R.8, Universal Mobile Telecommunications System (UMTS), Radio Resource Control (RRC), Protocol specification, Jul. 2009, p. 1424. |
| 3GPP TSG RAN WG2 25.331 v3.1.0 Meeting #11, R2-000660, “Proposed Enhancements to RRC Connection Re-Establishment Procedure,” Mar. 3, 2000, 10 pages. |
| 3GPP TSG RAN WG2 25.331 Meeting #8, R2-99e50, “Proposed CR 008 to 25.331 on a Parameter for RRC Connection Re-Establishment,” Oct. 5, 1999, 7 pages. |
| 3GPP TSG RAN2 Meeting #68 R2-096818, “Clarification on Enhanced SCRI Approach for Fast Dormancy,” Jeju, Korea, Nov. 9-13, 2009, 10 pages. |
| 3GPP2 R2-002479, “Revised: Use of ‘new’ BA—RANGE for improved RPLMN selection,” Nov. 17, 2000, 12 pages. |
| Implementation aspects of the pan-European digital mobile radio system, by Vary, CompEuro '89., ‘VLSI and Computer Peripherals. VLSI and Microelectronic Applications in Intelligent Peripherals and their Interconnection Networks’, Proceedings, May 8-12, 1989; 6 pages. |
| European Search Report in European Application No. 05112183.8, dated May 3, 2007, 7 pages. |
| European Search Report in European Application No. 06118909.8, dated Jul. 30, 2009, 3 pages. |
| European Search Report in European Application No. 06118909.8, dated Nov. 24, 2006, 8 pages. |
| European Search Report in European Application No. 06119590.5, dated Oct. 25, 2007, 7 pages. |
| European Search Report in European Application No. 08154976.8, dated Sep. 3, 2008, 7 pages. |
| European Search Report in European Application No. 10174218.7, dated Jun. 21, 2011, 7 pages. |
| European Search Report in European Application No. 10183886.0, dated Nov. 15, 2010, 3 pages. |
| Extended European Search Report in European Application No. 13177318.6, dated Oct. 27, 2014, 11 pages. |
| International Communication in International Application No. PCT/US2009/063912, dated Feb. 17, 2010, 9 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/CA2008/002000, dated Aug. 4, 2009, 5 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/CA2008/002000, dated Nov. 12, 2009, 4 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/CA2008/002001, dated Dec. 3, 2009, 8 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/CA2008/002002, dated May 18, 2010, 5 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/CA2010/002031, dated Mar. 9, 2012 (8 pages). |
| International Preliminary Report on Patentability in International Application No. PCT/EP2010/064859, dated Jun. 7, 2012, 11 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/EP2010/064860, dated Jun. 7, 2012, 9 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/EP2010/068063, dated Jun. 7, 2012, 10 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/EP2010/068063, dated May 30, 2012, 9 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/EP2010/068064, dated Aug. 14, 2012, 10 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/US2009/063912, dated May 10, 2011, 17 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/US2012/064499, dated May 22, 2014, 8 pages. |
| International Search Report and Written Opinion in International Application No. PCT/CA2007/001497, dated Dec. 18, 2008, 9 pages. |
| International Search Report and Written Opinion in International Application No. PCT/CA2008/002001, dated Jan. 28, 2009, 6 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2009/063912, dated Apr. 13, 2010, 22 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2009/063912, dated Feb. 17, 2010, 9 pages. |
| International Search Report in International Application No. PCT/CA2007/001497, dated Dec. 18, 2008, 9 pages. |
| International Search Report in International Application No. PCT/US2009/063912, dated Feb. 17, 2010, 9 pages. |
| International Search Report in International Application No. PCT/US2009/063912, dated May 3, 2010, 6 pages. |
| International Written Opinion in International Application No. PCT/CA2007/001497, dated Dec. 12, 2007, 12 pages. |
| International Written Opinion in International Application No. PCT/US2009/063912, dated May 3, 2010, 22 pages. |
| Office Action issued in related Canadian Application No. 2,781,558 on Apr. 8, 2016. |
| Office Action issued in related Canadian Application No. 2,781,630 on Apr. 8, 2016. |
| Office Action issued in related Chinese Application No. 201280004597.6 on Apr. 21, 2016. |
| Communication Pursuant to Article 94(3) EPC issued in European Application No. 10798525.1, dated Jul. 14, 2016. |
| Office Action issued in Indian Application No. 2949/CHENP/2010, dated Jul. 9, 2016. |
| Office Action issued in related Chinese Application No. 20130329228.0 on Jul. 28, 2016. |
| Communication Pursuant to Article 94(3) EPC issued in related European Application No. 10174218.7 on May 19, 2016. |
| Number | Date | Country | |
|---|---|---|---|
| 20130336258 A1 | Dec 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61089731 | Aug 2008 | US | |
| 61086955 | Aug 2008 | US | |
| 61074856 | Jun 2008 | US | |
| 61061359 | Jun 2008 | US | |
| 60987672 | Nov 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13157724 | Jun 2011 | US |
| Child | 13956862 | US | |
| Parent | 12270522 | Nov 2008 | US |
| Child | 13157724 | US |
