RELOCATION

BACKGROUND

[0001] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to call set up failures during serving radio network subsystem (SRNS) relocation.

[0002] Wireless communication networks are widely deployed to provide various communication services such as telephony, video, data, messaging, broadcasts, and so on. Such networks, which are usually multiple access networks, support communications for multiple users by sharing the available network resources. One example of such a network is the UMTS Terrestrial Radio Access Network (UTRAN). The UTRAN is the radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP). The UMTS, which is the successor to Global System for Mobile Communications (GSM) technologies, currently supports various air interface standards, such as Wideband-Code Division Multiple Access (W-CDMA), Time Division-Code Division Multiple Access (TD-CDMA), and Time Division-Synchronous Code Division Multiple Access (TD- SCDMA). The UMTS also supports enhanced 3G data communications protocols, such as High Speed Packet Access (HSPA), which provides higher data transfer speeds and capacity to associated UMTS networks.

[0003] For example, in TD-SCDMA, when a user equipment (UE) initiates a second circuit switched (CS) or packet switched (PS) call while a first CS/PS call in progress, and a serving radio network system (SRNS) relocation is triggered at a network entity prior to the setting up of radio bearer (RB)/radio access bearer (RAB) of the second CS/PS call, the setting up of the second CS/PS call may fail and/or the first CS/PS call may be dropped.

[0004] Therefore, there is a desire for a method and an apparatus for reducing call set up failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation. SUMMARY

[0005] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects not delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.

[0006] The present disclosure presents an example method and apparatus for reducing call set up or registration failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation. For example, the present disclosure presents an example method for identifying that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE, determining that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call, and terminating the SRNS relocation and sending a failure message to the network entity in response to the determination.

[0007] In an additional aspect, an apparatus for reducing call set up or registration failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation is disclosed. The apparatus may include means for identifying that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE, means for determining that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call, and means for terminating the SRNS relocation and sending a failure message to the network entity in response to the determination.

[0008] In a further aspect, a computer program product for reducing call set up or registration failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation is described. The computer program product may include a non- transitory computer-readable medium comprising code executable by a computer for identifying that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE, determining that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call, and terminating the SRNS relocation and sending a failure message to the network entity in response to the determination.

[0009] Moreover, the present disclosure presents an apparatus for reducing call set up or registration failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation. The apparatus may include a call identifying component to identify that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE, a SRNS relocation determining component to identify that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call, and a SRNS relocation terminating component to terminate the SRNS relocation and sending a failure message to the network entity in response to the determination.

[0010] Furthermore, the present disclosure presents an example method and apparatus for reducing registration failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation. For example, the present disclosure presents an example method for identifying that a registration message is transmitted from the UE, determining that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to completion of a registration procedure at the network entity, and terminating the SRNS relocation and sending a failure message to the network entity in response to the determination.

[0011] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Fig. 1 is a block diagram illustrating an example wireless system in aspects of the present disclosure; [0013] Fig. 2 is a flow diagram illustrating aspects of a method of reducing call set up or registration failures as contemplated by the present disclosure;

[0014] Fig. 3 is a block diagram illustrating aspects of a logical grouping of electrical components as contemplated by the present disclosure;

[0015] Fig. 4 is a block diagram illustrating aspects of a computer device according to the present disclosure;

[0016] Fig.5 is a conceptual diagram illustrating an example of an access network; and

[0017] Fig. 6 is a block diagram conceptually illustrating an example of a NodeB in communication with a UE in a telecommunications system.

DETAILED DESCRIPTION

[0018] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0019] The present disclosure presents an example method and apparatus for reducing call set up failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation. For example, the present disclosure presents an example method for reducing call set up failures at a UE during SRNS relocation that may include identifying that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE, determining that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call, and terminating the SRNS relocation and sending a failure message to the network entity in response to the determination.

[0020] Additionally, the present disclosure presents an example apparatus for reducing call set up failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation that may include means for identifying that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE, means for determining that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call, and means for terminating the SRNS relocation and sending a failure message to the network entity in response to the determination.

[0021] In a further aspect, the presents disclosure presents an example computer program product for reducing call set up failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation that may include a non-transitory computer-readable medium comprising code executable by a computer for identifying that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE, determining that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call, and terminating the SRNS relocation and sending a failure message to the network entity in response to the determination.

[0022] Furthermore, in an aspect, the present disclosure presents an example method for reducing call set up failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation that may include detecting that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for a circuit switched (CS) or packet switched (PS) call, and terminating the SRNS relocation and sending a failure message to the network entity in response to the detection.

[0023] Referring to Fig. 1, a wireless communication system 100 is illustrated that facilitates reducing call set up failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation. For example, system 100 includes user equipment (UE) 102 that may communicate with one or more network entities 120 (e.g., source network entity 130 and/or target network entity 140) via one or more over-the-air link 136 and/or 146. In an aspect, for example, source network entity 130 may include source radio network controller (RNC) 132 and cell 134, and/or target network entity 140 may include target radio network controller (RNC) 142 and cell 144. [0024] For example, in an aspect, UE 102 may be camped on cell 134 (e.g., cell 134 is serving cell of UE 102) which is supported by (or connected to) source RNC 132. When radio frequency (RF) conditions at cell 134 deteriorate, UE 102 may perform a cell reselection to cell 144. If UE 102 performs a cell reselection to cell 144, a serving radio network subsystem (SRNS) relocation may be triggered, transparent to UE 102, as cell 144 is supported by target RNC 142 (also referred to as the "target RNC") with the change in RNCs from RNC 132 (also referred to as "source RNC") to RNC 142. For example, a SRNS relocation procedure is used to move radio access network (RAN) to core network (CN) connection point at the RAN side from the source RNC (e.g., RNC 132) to the target RNC (e.g., 142). In such a procedure, the Iu links are relocated.

[0025] In an aspect, network entity 120, source network entity 130, and/or target network entity 140 may include, but not limited to, an access point, a base station (BS) or Node B or eNodeB, a macro cell, a small cell such as a femtocell or a pico cell, a relay, a peer-to-peer device, an authentication, authorization and accounting (AAA) server, a mobile switching center (MSC), etc. Additionally, network entity 120, source network entity 130, and/or target network entity 140 may include one or more of any type of network components that can enable UE 102 to communicate and/or establish and maintain linkl36 with source network entity 130 and/or link 146 with target network entity 140. In an example aspect, network entity 120 may operate according to Time Division Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE) or Global System for Mobile Communications (GSM) standard as defined in 3GPP Specifications.

[0026] In an aspect, UE 102 may be a mobile apparatus and may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.

[0027] In an aspect, UE 102 may be configured with a serving radio network subsystem

(SRNS) relocation manager 104. The SRNS relocation manager 104 facilitates reducing call set up failures at UE 102 during SRNS relocation, which includes for example, change of a SRNS (for example, controlling RNC) from source RNC 132 to target RNC 142. The SRNS relocation manager 104 may be configured to reduce call set up failures at UE 102 during SRNS relocation by identifying that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE, determining that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call, and terminating the SRNS relocation and sending a failure message to the network entity. For example, SRNS relocation manager 104 terminates or stops the SRNS relocation and sends a failure message to the network entity which may result in a reduction or elimination of call set up failures.

[0028] In an aspect, once SRNS relocation manager 104 terminates or stops SRNS relocation, the UE stays on the source RNC (e.g., UE still supported or connected to source RNC 132) until setting up of RB/RAB at the UE for the second CS or PS call is complete. In an additional or optional aspect, SRNS relocation may be successfully completed (e.g., SRNS relocation of UE 102 from the source RNC to the target RNC) if the SRNS relocation is triggered after the setting of the radio bearer for the second CS/PS call. In an additional aspect, the SRNS relocation may be delayed (e.g., instead of terminating) until the setup of the radio bearer for the second CS/PS call is completed.

[0029] In an aspect, SRNS Relocation Manager 104, for example, of UE 102 may be configured to include a Call Identifying Component 106, a SRNS relocation Determining Component 108, and/or a SRNS Relocation Terminating Component 110.

[0030] In an aspect, Call Identifying Component 106 may be configured to identify that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE. For example, in an aspect, a first CS or PS call may be in progress between UE 102 and cell 134/source RNC 132 via link 126. In an example aspect, when a first CS/PS is already in progress at the UE, and a second CS/PS call is initiated at UE 102, Call Identifying Component 106 may be configured to identify that a second CS/PS call is initiated at the UE when the first call at UE 102 is already in progress. For example, Call Identifying Component 106 may identify the origination of the second CS/PS call based on a non-access stratum (NAS) message received from the network entity (e.g., source network entity 130). In an additional aspect, the second CS/PS call initiated at UE 102 may be a mobile originated call (e.g., call originated at UE 102). [0031] In an aspect, SRNS Relocation Determining Component 108 may be configured to determine that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio bearer (RB) or radio access bearer (RAB) for the second CS or PS call. For example, in an aspect, when the initiation of the second CS/PS call is in progress and/or prior to the setting up RB/RAB of the second CS/PS call, SRNS relocation may be triggered at network entity 120. In an aspect, SRNS relocation may be triggered due to various reasons as described in 3GPP Specifications, examples of which are discussed below.

[0032] For example, the SRNS relocation procedure may include moving of radio access network (RAN) to carrier network (CN) connection point at the RAN side from a source radio network controller (RNC) to a target RNC. In an aspect, for example, UE 102 may be notified of SRNS relocation via a message from the network entity 120. For example, the message from the network entity 120 may be a reconfiguration message, e.g., a radio bearer reconfiguration message. In an additional aspects, the message may be received from target network entity 140/target RNC 142.

[0033] In an aspect, SRNS Relocation Terminating Component 110 may be configured to terminate the SRNS relocation and send a failure message to the network entity in response to the determination. For example, in an aspect, when SRNS Relocation Determining Component 108 determines that a SRNS relocation is triggered (e.g., at network entity 120) prior to setting up of RB/RAB for the second CS/PS call, SRNS Relocation Terminating Component 110 may be configured to respond by terminating the SRNS relocation procedure. In an aspect, the termination of SRNS relocation procedure which is triggered at network entity 120 may reduce/avoid dropping of the first CS/PS calls. In an additional aspect, the termination of SRNS relocation procedure which is triggered at network entity 120 may reduce/avoid failures associated with the setting up of the second CS/PS calls

[0034] In an additional aspect, SRNS Relocation Terminating Component 110 may be further configured to send a failure message to the network entity. For example, in an aspect, SRNS Relocation Terminating Component 110 may be configured to send a failure message that includes termination of the SRNS relocation to network entity 120. [0035] In an additional or optional aspect, SRNS Relocation Terminating Component

110 may be further configured to send a physical layer failure message to the network entity to indicate the termination of the SRNS relocation.

[0036] In an additional aspect, SRNS Relocation Terminating Component 110 may be further configured to retain (e.g., keep) the UE on the source RNC 132 until the setting up of RB/RAB for the second CS/PS is complete. For example, in an aspect, SRNS Relocation Terminating Component 110 may be configured to retain or hold UE 102 on source RNC 132 until the setting up of RB/RAB for the second CS/PS is complete. This may include the source RNC 132 continuing to support UE 102. This will help avoiding and/or eliminating dropped calls which may include the second CS/PS call and/or the first CS/PS call.

[0037] In an additional or optional aspect, the mechanism described above for reducing call set up failures associated with second CS/PS calls may also be used for reducing call set up failures during the set up of a first CS/PS call. For example, in an aspect, UE 102 and/or SRNS relocation manager may be configured to detect that SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for a CS/PS call and terminating the SRNS relocation and sending a failure message to the network entity in response to the detection. The mechanism described above in reference to a two call scenario (e.g., a first CS/PS and a second CS/PS call) may be used in a one call scenarios as well (e.g., a CS/PS call). This mechanism will minimize, avoid, and eliminate dropped calls at the UE when SRNS relocation is triggered prior to setting up of the RAB at the UE.

[0038] In an additional or optional aspect, the mechanism described above for reducing call set up failures associated with setting up CS/PS calls may also be used for reducing registrations failures. For example, in an aspect, when the UE is receiving a registration message (e.g., a location area update message) and a SRNS relocation is triggered at the network entity prior to setting up of a radio access bearer (RAB) at the UE, the update at the UE associated with the registration message may fail. In an aspect, the mechanism described above in reference to a two call and/or a one call scenario may be used. This mechanism will minimize, avoid, and eliminate dropped registration messages at the UE when SRNS relocation is triggered prior to setting up of the RAB at the UE. In an aspect, the UE is retained at the source network entity 130 and the registration message (e.g., location area update message) is processed at the UE.

[0039] Fig. 2 illustrates an example methodology 200 for reducing call set up failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation. In an aspect, at block 202, methodology 200 may include identifying that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE. For example, in an aspect, UE 102, SRNS Relocation Manager 104, and/or Call Identifying Component 106 may be configured to identify that a second circuit switched (CS) or packet switched (PS) call is initiated at UE 102 when a first CS or PS call is in progress at UE 102. For example, UE 102, SRNS Relocation Manager 104, and/or Call Identifying Component 106 may be configured to identify the second CS/PS calls based on a non-access stratum (NAS) message received from the network entity (e.g., target network entity 140 and/or target RNC 144).

[0040] Additionally, at block 204, methodology 200 may include determining that a

SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call. For example, in an aspect, UE 102, SRNS Relocation Manager 104, and/or SRNS Relocation Determining Component 108 may be configured to determine that a SRNS relocation is triggered at network entity 120 (e.g., SRNS relocation from source RNC 132 to target RNC 1402) that is in communication with UE 102 prior to setting up of a radio access bearer (RAB) for the second CS or PS call. For example, UE 102, SRNS Relocation Manager 104, and/or SRNS Relocation Determining Component 108 may be configured to determine triggering of SRNS relocation based on a reconfiguration message (e.g., radio bearer reconfiguration message) received from the network entity.

[0041] Further, at block 206, methodology 200 may include terminating the SRNS relocation and sending a failure message to the network entity in response to the determination. For example, in an aspect, UE 102, SRNS Relocation Manager 104, and/or SRNS Relocation Termination Component 110 may be configured to terminate the SRNS relocation (e.g., SRNS relocation to target RNC 142) in response to determining that the a SRNS relocation is triggered at network entity 120. In an additional aspect, UE 102, SRNS Relocation Manager 104, and/or SRNS Relocation Termination Component 110 may be configured to send a failure message to the network entity (e.g., target network entity 140 and/or target RNC 142) notifying the network entity that the SRNS relocation has been terminated to update the network entity that the UE is still on source RNC 132.

[0042] In an optional aspect, at block 210, methodology 200 may include retaining of the UE on the source RNC until setting up of the RAB for the second CS or PS call is complete at the UE. For example, in an aspect, UE 102, SRNS Relocation Manager 104, and/or SRNS Relocation Termination Component 110 may be configured for UE 102 to be retained on source RNC 132 until setting up of the RAB at UE 102 for the second CS or PS call is complete. For example, UE 102, SRNS Relocation Manager 104, and/or SRNS Relocation Termination Component 110 may be configured to retain (e.g., continue supporting the UE on the source RNC 132) until the RAB for the second CS/PS is complete at the UE.

[0043] Referring to Fig. 3, an example system 300 is displayed for reducing call set up or registration failures at a user equipment (UE) during serving radio network subsystem (SRNS) relocation. For example, system 300 can reside at least partially within a user equipment, for example, UE 102 (Fig. 1) and/or SRNS Relocation Manager 104 (Fig. 1). It is to be appreciated that system 300 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (for example, firmware). System 300 includes a logical grouping 302 of electrical components that can act in conjunction. For instance, logical grouping 302 may include an electrical component 304 configured to identify that a second circuit switched (CS) or packet switched (PS) call is initiated at the UE when a first CS or PS call is in progress at the UE. For example, in an aspect, electrical component 304 may comprise Call Identifying Component 106 (Fig. 1).

[0044] Additionally, logical grouping 302 may include an electrical component 306 configured to determine that a SRNS relocation is triggered at a network entity that is in communication with the UE prior to setting up of a radio access bearer (RAB) for the second CS or PS call. For example, in an aspect, electrical component 306 may comprise SRNS Relocation Determining Component 108 (Fig. 1).

[0045] Further, logical grouping 302 may include an electrical component 308 configured to terminate the SRNS relocation and sending a failure message to the network entity in response to the determination. For example, in an aspect, electrical component 308 may comprise SRNS Relocation Terminating Component 110 (Fig. 1).

[0046] Furthermore, in an optional aspect, logical grouping 302 may optionally include an electrical component 310 configured to remain on the first RNC until setting up of the RAB at the UE for the second CS or PS call is complete. In an aspect, electrical component 310 may comprise SRNS Relocation Terminating Component 110 (Fig. 1) further configured for UE 102 to remain on the source RNC.

[0047] Additionally, system 300 can include a memory 312 that retains instructions for executing functions associated with the electrical components 304, 306, 308, and 310, stores data used or obtained by the electrical components 304, 306, 308, and 310, etc. While shown as being external to memory 312, it is to be understood that one or more of the electrical components 304, 306, 308, and 310 can exist within memory 312. In one example, electrical components 304, 306, 308, and 310 can comprise at least one processor, or each electrical component 304, 306, 308, and 310 can be a corresponding module of at least one processor. Moreover, in an additional or alternative example, electrical components 304, 306, 308, and 310 can be a computer program product including a computer readable medium, where each electrical component 304, 306, 308, and 310 can be corresponding code.

[0048] Referring to Fig. 4, in an aspect, UE 102 and/or SRNS Relocation Manager 104 may be represented by a specially programmed or configured computer device 400. In one aspect of implementation, computer device 400 may include UE 102 and SRNS Relocation Manager 104 and its components, including Call Identifying Component 106, SRNS Relocation Determining Component 108, and/or SRBS Relocation Terminating Component 110 (Fig. 1), such as in specially programmed computer readable instructions or code, firmware, hardware, or some combination thereof. Computer device 400 includes a processor 402 for carrying out processing functions associated with one or more of components and functions described herein. Processor 402 can include a single or multiple set of processors or multi-core processors. Moreover, processor 402 can be implemented as an integrated processing system and/or a distributed processing system.

[0049] For example, in an aspect, SRNS Relocation Manager 104 may be implemented or executed using one or any combination of processor 402, memory 404, communications component 406, and/or data store 408. For example, SRNS Relocation Manager 104 may be defined or otherwise programmed as one or more processor modules of processor 402. Further, for example, SRNS Relocation Manager 104 may be defined as a computer-readable medium stored in memory 404 and/or data store 408 and executed by processor 402. Moreover, for example, inputs and outputs relating to operations of SRNS Relocation Manager 104 may be provided or supported by communications component 406, which may provide a bus between the components of computer device 400 or an interface to communication with external devices or components."

[0050] Computer device 400 further includes a memory 404, such as for storing data used herein and/or local versions of applications being executed by processor 402. Memory 404 can include any type of memory usable by a computer, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.

[0051] Further, computer device 400 includes a communications component 406 that provides for establishing and maintaining communications with one or more parties utilizing hardware, software, and services as described herein. Communications component 406 may carry communications between components on computer device 400, as well as between computer device 400 and external devices, such as devices located across a communications network and/or devices serially or locally connected to computer device 400. For example, communications component 406 may include one or more buses, and may further include transmit chain components and receive chain components associated with a transmitter and receiver, respectively, or a transceiver, operable for interfacing with external devices. In an additional aspect, communications component 406 may be configured to receive one or more pages from one or more subscriber networks. In a further aspect, such a page may correspond to the second subscription and may be received via the first technology type communication services.

[0052] Additionally, computer device 400 may further include a data store 408, which can be any suitable combination of hardware and/or software, that provides for mass storage of information, databases, and programs employed in connection with aspects described herein. For example, data store 408 may be a data repository for applications not currently being executed by processor 402 and/or any threshold values or finger position values.

[0053] Computer device 400 may additionally include a user interface component 410 operable to receive inputs from a user of computer device 400 and further operable to generate outputs for presentation to the user. User interface component 410 may include one or more input devices, including but not limited to a keyboard, a number pad, a mouse, a touch-sensitive display, a navigation key, a function key, a microphone, a voice recognition component, any other mechanism capable of receiving an input from a user, or any combination thereof. Further, user interface component 410 may include one or more output devices, including but not limited to a display, a speaker, a haptic feedback mechanism, a printer, any other mechanism capable of presenting an output to a user, or any combination thereof.

[0054] Referring to Fig. 5, an access network 500 in a UTRAN architecture is illustrated, and may include one or more user equipment (UE) configured to include a SRNS Relocation Manager 104 (Fig. 1). The multiple access wireless communication system includes multiple cellular regions (cells), including cells 502, 504, and 506, each of which may include one or more sectors and which may be network entity 120 of Fig. 1. The multiple sectors can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell. For example, in cell 502, antenna groups 512, 514, and 516 may each correspond to a different sector. In cell 504, antenna groups 518, 520, and 522 each correspond to a different sector. In cell 506, antenna groups 524, 526, and 528 each correspond to a different sector. The cells 502, 504 and 506 may include several wireless communication devices, e.g., User Equipment or UEs, for example, including UE 102 of Fig. 1, which may be in communication with one or more sectors of each cell 502, 504 or 506. For example, UEs 530 and 532 may be in communication with NodeB 542, UEs 534 and 536 may be in communication with NodeB 544, and UEs 536 and 540 can be in communication with NodeB 546. Here, each NodeB 542, 544, 546 is configured to provide an access point for all the UEs 530, 532, 534, 536, 538, 540 in the respective cells 502, 504, and 506. Additionally, each NodeB 542, 544, 546 may be network entity 120 of Fig. 1, and/or each UE 530, 532, 534, 536, 538, 540 may be UE 102 of Fig. 1, and may perform the methods outlined herein. [0055] As the UE 534 moves from the illustrated location in cell 504 into cell 506, a serving cell change (SCC) or handover may occur in which communication with the UE 534 transitions from the cell 504, which may be referred to as the source cell, to cell 506, which may be referred to as the target cell. Management of the handover procedure may take place at the UE 534, at the Node Bs corresponding to the respective cells, at an Enhanced Packet Core, or at another suitable node in the wireless network. For example, during a call with the source cell 504, or at any other time, the UE 534 may monitor various parameters of the source cell 504 as well as various parameters of neighboring cells such as cells 506 and 502. Further, depending on the quality of these parameters, the UE 534 may maintain communication with one or more of the neighboring cells. During this time, the UE 534 may maintain an Active Set, that is, a list of cells that the UE 534 is simultaneously connected to (i.e., the UTRA cells that are currently assigning a downlink dedicated physical channel DPCH or fractional downlink dedicated physical channel F-DPCH to the UE 534 may constitute the Active Set). In any case, UE 534 may execute IRAT Handover Manager 104 to perform the reselection operations described herein.

[0056] Further, the modulation and multiple access scheme employed by the access network 500 may vary depending on the particular telecommunications standard being deployed. By way of example, the standard may include Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB). EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations. The standard may alternately be Universal Terrestrial Radio Access (UTRA) employing Wideband-CDMA (W-CDMA) and other variants of CDMA, such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDM A. UTRA, E-UTRA, UMTS, LTE, LTE Advanced, and GSM are described in documents from the 3GPP organization. CDMA2000 and UMB are described in documents from the 3GPP2 organization. The actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system. [0057] Fig. 6 is a block diagram of a NodeB 610 in communication with UE 650, where the NodeB 610 may be network entity 120 and where UE 650 may be UE 102 that may include a SRNS Relocation Manager 104 (Fig 1). In the downlink communication, a transmit processor 620 may receive data from a data source 612 and control signals from a controller/processor 640. The transmit processor 620 provides various signal processing functions for the data and control signals, as well as reference signals (e.g., pilot signals). For example, the transmit processor 620 may provide cyclic redundancy check (CRC) codes for error detection, coding and interleaving to facilitate forward error correction (FEC), mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), and the like), spreading with orthogonal variable spreading factors (OVSF), and multiplying with scrambling codes to produce a series of symbols. Channel estimates from a channel processor 644 may be used by a controller/processor 640 to determine the coding, modulation, spreading, and/or scrambling schemes for the transmit processor 620. These channel estimates may be derived from a reference signal transmitted by the UE 650 or from feedback from the UE 650. The symbols generated by the transmit processor 620 are provided to a transmit frame processor 630 to create a frame structure. The transmit frame processor 630 creates this frame structure by multiplexing the symbols with information from the controller/processor 640, resulting in a series of frames. The frames are then provided to a transmitter 632, which provides various signal conditioning functions including amplifying, filtering, and modulating the frames onto a carrier for downlink transmission over the wireless medium through antenna 634. The antenna 634 may include one or more antennas, for example, including beam steering bidirectional adaptive antenna arrays or other similar beam technologies.

[0058] At the UE 650, a receiver 654 receives the downlink transmission through an antenna 652 and processes the transmission to recover the information modulated onto the carrier. The information recovered by the receiver 654 is provided to a receive frame processor 660, which parses each frame, and provides information from the frames to a channel processor 684 and the data, control, and reference signals to a receive processor 670. The receive processor 670 then performs the inverse of the processing performed by the transmit processor 620 in the NodeB 610. More specifically, the receive processor 670 descrambles and de-spreads the symbols, and then determines the most likely signal constellation points transmitted by the NodeB 610 based on the modulation scheme. These soft decisions may be based on channel estimates computed by the channel processor 684. The soft decisions are then decoded and de-interleaved to recover the data, control, and reference signals. The CRC codes are then checked to determine whether the frames were successfully decoded. The data carried by the successfully decoded frames will then be provided to a data sink 672, which represents applications running in the UE 650 and/or various user interfaces (e.g., display). Control signals carried by successfully decoded frames will be provided to a controller/processor 680. When frames are unsuccessfully decoded by the receiver processor 670, the controller/processor 680 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.

In the uplink, data from a data source 678 and control signals from the controller/processor 680 are provided to a transmit processor 679. The data source 678 may represent applications running in the UE 650 and various user interfaces (e.g., keyboard). Similar to the functionality described in connection with the downlink transmission by the NodeB 610, the transmit processor 679 provides various signal processing functions including CRC codes, coding and interleaving to facilitate FEC, mapping to signal constellations, spreading with OVSFs, and scrambling to produce a series of symbols. Channel estimates, derived by the channel processor 684 from a reference signal transmitted by the NodeB 610 or from feedback contained in the mid- amble transmitted by the NodeB 610, may be used to select the appropriate coding, modulation, spreading, and/or scrambling schemes. The symbols produced by the transmit processor 679 will be provided to a transmit frame processor 682 to create a frame structure. The transmit frame processor 682 creates this frame structure by multiplexing the symbols with information from the controller/processor 680, resulting in a series of frames. The frames are then provided to a transmitter 656, which provides various signal conditioning functions including amplification, filtering, and modulating the frames onto a carrier for uplink transmission over the wireless medium through the antenna 652. [0060] The uplink transmission is processed at the NodeB 610 in a manner similar to that described in connection with the receiver function at the UE 650. A receiver 635 receives the uplink transmission through the antenna 634 and processes the transmission to recover the information modulated onto the carrier. The information recovered by the receiver 635 is provided to a receive frame processor 636, which parses each frame, and provides information from the frames to the channel processor 644 and the data, control, and reference signals to a receive processor 637. The receive processor 637 performs the inverse of the processing performed by the transmit processor 679 in the UE 650. The data and control signals carried by the successfully decoded frames may then be provided to a data sink 638 and the controller/processor, respectively. If some of the frames were unsuccessfully decoded by the receive processor, the controller/processor 680 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.

[0061] The controller/processors 640 and 680 may be used to direct the operation at the

NodeB 610 and the UE 650, respectively. For example, the controller/processors 640 and 680 may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The computer readable media of memories 642 and 662 may store data and software for the NodeB 610 and the UE 650, respectively. A scheduler/processor 646 at the NodeB 610 may be used to allocate resources to the UEs and schedule downlink and/or uplink transmissions for the UEs.

[0062] Several aspects of a telecommunications system have been presented with reference to a W-CDMA system. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0063] By way of example, various aspects may be extended to other UMTS systems such as TD-SCDMA, High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+) and TD- CDMA. Various aspects may also be extended to systems employing Long Term Evolution (LTE) (in FDD, TDD, or both modes), LTE-Advanced (LTE-A) (in FDD, TDD, or both modes), CDMA2000, Evolution-Data Optimized (EV-DO), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra- Wideband (UWB), Bluetooth, and/or other suitable systems. The actual telecommunication standard, network architecture, and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0064] In accordance with various aspects of the disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a "processing system" that includes one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on a computer-readable medium. The computer-readable medium may be a non-transitory computer-readable medium. A non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disk (CD), digital versatile disk (DVD)), a smart card, a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer.

[0065] The computer-readable medium may also include, by way of example, a carrier wave, a transmission line, and any other suitable medium for transmitting software and/or instructions that may be accessed and read by a computer. The computer- readable medium may be resident in the processing system, external to the processing system, or distributed across multiple entities including the processing system. The computer-readable medium may be embodied in a computer-program product. By way of example, a computer-program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0066] It is to be understood that the specific order or hierarchy of steps in the methods disclosed is an illustration of exemplary processes. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented unless specifically recited therein.

[0067] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language of the claims, wherein reference to an element in the singular is not intended to mean "one and only one" unless specifically so stated, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. A phrase referring to "at least one of a list of items refers to any combination of those items, including single members. As an example, "at least one of: a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. No claim element is to be construed under the provisions of 35 U.S.C. § 112, sixth paragraph, unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the element is recited using the phrase "step for."