Method and apparatus for transfer of session reference network controller

Systems and methods of decoupling session management from connection management of a wireless network by enabling transfer of a session between session controllers. A session transfer component transfers ownership of a session from a source session controller to a target session controller, wherein the session transfer does not necessarily require moving the associated connections therewith. Such transfer employs a Unicast Access Terminal Identifier (UATI) that is updated to inform the related base stations regarding transfer of the session.

BACKGROUND

The following description relates generally to wireless communications, and more particularly to methods and apparatus for transfer of session ownership between network entities.

Wireless networking systems have become a prevalent means to communicate with others worldwide. Wireless communication devices, such as cellular telephones, personal digital assistants, and the like have become smaller and more powerful in order to meet consumer needs and to improve portability and convenience. Consumers have become dependent upon these devices, demanding reliable service, expanded areas of coverage, additional services (e.g., web browsing capabilities), and continued reduction in size and cost of such devices.

In particular, as the evolution of wireless technologies continues to advance, the progression of mobile services will continue to evolve into ever-richer, more compelling mobile and converged services. With end users demanding more and higher-quality multimedia content in all environments, the evolution of device technologies will continue to enhance the increasing consumption of data usage. For example, over the last several years, wireless communications technologies have evolved from analog-driven systems to digital systems. Typically in conventional analog systems, the analog signals are relayed on a forward link and a reverse link and require a significant amount of bandwidth to enable signals to be transmitted and received while being associated with suitable quality. As the analog signals are continuous in time and space, no status messages (e.g., messages indicating receipt or non-receipt of data) are generated. In contrast, packet-switched systems allow analog signals to be converted to data packets and transmitted by way of a physical channel between an access terminal and a base station, router, and the like. In addition, digital data can be relayed in its natural form (e.g., text, Internet data, and the like) via employing a packet switched network.

As such, digital wireless communication systems are widely deployed to provide various communication services such as telephony, video, data, messaging, broadcasts, and the like. Such systems commonly employ an access network that connects multiple access terminals to a wide area network (WAN) by sharing the available network resources. The access network is typically implemented with multiple access points dispersed throughout a geographic coverage region. Moreover, the geographic coverage region can be divided into cells with an access point in each cell. Likewise, the cell can be further divided into sectors. However, in such system architecture supplying session information and paging management to a moving AT becomes a challenging task.

SUMMARY

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

The described aspects provide for transfer of a communication session from a source session controller (e.g., a source Session Reference Network Controller—SRNC) to a target session controller (e.g., a target SRNC)—via a session transfer component, and enable decoupling of session management from connection management of wireless networks. Accordingly, session management becomes independent of connection management, wherein if a session is to be transferred, such does not necessarily require moving the associated connection therewith. Such is in contrast to conventional systems that require the connection to be moved if the session is moved, which can further induce interruptions. Hence, the described aspects provide for transfer of a session without interruption of the data stream between the AT and the wireless communication system.

In general, a connection represents an assignment of resources (e.g., dedicated resources) that allow an Access Terminal (AT) to communicate with an Access Network (AN). Likewise, a session represents a collection of configurations, attributes or parameters negotiated between the AT and the AN (e.g., Quality of Service configurations), wherein the session controller retains the authority on such configurations. Communications between base station and the AT is based on the configurations maintained in the session controller, wherein a base station needs to obtain such configuration from the session controller, before communicating with the AT. The connection is maintained independently of the session state, wherein the base stations (and not the session controller) control the connection.

The session and the AT can be identified to base stations based on a Unicast Access Terminal Identifier (UATI), wherein session signatures can further designate the version of the session for the AT. Such identification by session signatures can be based on a sequence of numbers that can be incremented, when the session is updated, e.g., a session can be modified upon initiation of a new application that requires additional resources.

Based on such updates, base station that receives the UATI can clearly and unambiguously locate the session controller (e.g., target SRNC), which now manages the session to retrieve session information. It is to be appreciated that a base station can re-negotiate the session if session information is not desirable.

In a related aspect, the transfer of the SRNC occurs without interruption to stream of data communicated between the AT and base stations, regardless of which SRNC is chosen. Moreover, the AT can recognize each base station and can communicate directly therewith, wherein the SRNC can act as the coordinator of negotiations that the AT has conducted with such base stations. The SRNC typically includes authentication functions and associated configurations—which are negotiated between base station(s) and access terminals(s), and functions as a reference for base stations to retrieve information (e.g., obtain session information to avoid conflicts during session change.) The source SRNC can also hold the reference copy of the session and perform paging controller function. SRNC can be located using the UATI of the AT. In a related aspect, the session transfer component can robustly transfer SRNC to another entity, while at the same time another AN is being added into the active set or session negotiation.

According to a methodology, initially a source SRNC and a target SRNC are positioned in a route set for exchange of messages (e.g., have been set up for communication). Subsequently, a message related to an SRNC transfer request can be sent to the source SRNC from the target SRNC. The source SRNC can then supply UATI sequence numbers (e.g., an increasing number associated with UATI) to signify for base stations the sequence numbers supplied for the target SRNC. Moreover, the target SRNC can supply the updated UATI to the AT. Upon receipt of such message by the AT, it subsequently responds with UATI complete message, to the target SRNC to indicate agreement with updated UATI and transfer to the assigned target SRNC. The target SRNC can then announce to members of route associated therewith (e.g., the source SRNC and the serving eBS) that the UATI has changed and the target SRNC has now taken ownership of the session. Likewise, base stations can change their associated UATI to that of the target SRNC.

To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative, however, of but a few of the various ways in which the principles of the disclosed subject matter may be employed and the claimed matter is intended to include all such aspects and their equivalents. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings.

DETAILED DESCRIPTION

FIG. 1illustrates a session transfer component125that transfers a session142from a source Session Reference Controller111(SRNC) to a target SRNC113. Typically, the source and target SRNC111,113are responsible for maintaining the session reference with the Access Terminal120(AT.) Moreover, such source SRNC111and target SRNC113can support idle state management of the AT120, and provide paging control functions when the AT120is idle. In one aspect, the SRNC111,113contains a Session Anchor route for each AT120it is supporting. Moreover, Access Gateway (AGW) selection can be performed by the SRNC111,113for the AT120. In addition, an SRNC can assume the Data Attachment Point SRNC function to establish a Signaling-Only binding with the AGW when the AT is idle. The SRNC can also function as the authenticator for access authentication.

As illustrated inFIG. 1, the session transfer component125transfers ownership of a session142from the source SRNC111to the target SRNC113, wherein associated Unicast Access Terminal Identifier (UATI) can then be updated to designate such transfer to the related base station(s). Accordingly, session management becomes independent of connection management, wherein if a session is to be moved, such does not necessarily require moving the associated connection therewith. Such is in contrast to conventional systems that require the connection to be moved if the session is moved, which can further induce interruptions. Communications between base station (not shown) and the AT120is based on the configurations maintained in the session controller, wherein a base station needs to obtain such configuration from the session controller, before communicating with the AT. The session and the AT120can be identified to base stations based on a Unicast AccessTerminal Identifier (UATI), wherein session signatures can further designate the version of the session for the AT. Such identification by session signatures can be based on a sequence of numbers that can be incremented, when the session is updated, e.g., a session can be modified upon initiation of a new application that requires additional resources.

Based on such updates, a base station that receives the UATI can clearly and unambiguously locate the target SRNC111, which now manages the session to retrieve session information. It is to be appreciated that a base station can re-negotiate the session if session information is not desirable. The UATI may include a subnet identifier segment (e.g., having a size of 8 bits) and an AT identifier portion having a predetermined size (e.g., 24 bits.). It may also include the IP address of the SRNC for the AT120. Accordingly, when the AT system moves (e.g., from a source subnet to a target subnet) a target SRNC can be identified from UATI, and a session is referred or located thereafter by updated or a new UATI. It is to be appreciated that even thoughFIG. 1illustrates the session transfer component as a single unit, such unit can be in a distributed from throughout the system. Moreover, the paging processes during session transfer can be performed by using both an old page ID (e.g., assigned by the source session controller to the AT) and a new Page ID (e.g., assigned to the AT by the target SRNC), and before the new UATI has been confirmed from the AT.

FIG. 2illustrates an exemplary system SRNC transfer that includes Access Networks in form of a functional entity that contains AN Route Instance (ANRI)211,213,215for logically communicating with the Access Terminal (AT)220. Communication by an ANRI that is not currently serving the AT220on a forward or reverse radio link is accomplished logically by tunneling UMB Route Protocol Packets through the Forward Link Serving eBS (FLSE) and Reverse-Link Serving eBS (RLSE). The SRNC230can have a route with the AT220, wherein the SRNC230can communicate transparently with other base stations. In one aspect transfer of a session occurs without interruption of the data stream between the AT and the wireless communication system. Moreover, the AT220can recognize each base station and can communicate directly therewith, wherein the SRNC can act as the coordinator of negotiations that the AT has conducted with such base stations.

As illustrated inFIG. 2, the Access Gateway (AGW)225provides the “point of IP attachment” to the Packet Data network for ATs. Accordingly, the AGW225is effectively the first-hop router for the AT220, wherein the AGW225can consist of Control-plane (C-plane) to handle signaling messages between eBS/SRNC and the AGW, and User-plan (U-plane) to handle bearer traffic. C-plane and U-plane may have different IP endpoint. The transfer component moves the SRNC from one entity to another entity.

The source SRNC can also hold the reference copy of the session and perform paging controller function. SRNC can be located using the UATI of the AT220. For example, IP address of the SRNC may be embedded as part of the UATI. The transfer component robustly transfers SRNC to another entity that can happen at the same time that another AN is being added. Accordingly, the transfer component transfers ownership of a session from a source SRNC to a target SRNC, wherein associated Unicast Access Terminal Identifier (UATI) can then be updated to designate such transfer to base stations.

The session and the AT can be identified to base stations based on a Unicast AccessTerminal Identifier (UATI), wherein session signatures can further designate the version of the session for the AT. Based on such updates, a bases station that receives the UATI can clearly and unambiguously locate the target SRNC, which now manages the session reference, to retrieve session information. It is to be appreciated that a base station can re-negotiate the session if session information is not desirable. As illustrated inFIG. 2, the U1reference point carries control and bearer information between the eBS and the AGW. Likewise, the U2reference point carries control information between the SRNC and eBS; and the U3reference point carries control and bearer information between two eBSs. Moreover, The U4reference point carries control information between SRNCs. Furthermore, the U6reference point carries control information between the SRNC and AGW.

FIG. 3illustrates an exemplary Unicast Access Terminal Identifier (UATI)319that is updatable to designate transfer of the AT from one base station to another base station, as part of a communication system300. The UATI serves as a temporary identifier to identify the AT and the associated SRNC serving the AT. For example, the UATI319can be employed in messages transmitted over the air interface between the mobile station326327, the AN, target SRNC340or source SRNC330. As illustrated inFIG. 3, the UATI319can include a predetermined number of bits (e.g., 24 bits that includes an 8-bit prefix for the AN, and a 16-bit SRNC identifier.) It is to be appreciated that such arrangement is exemplary in nature and other arrangements are well within the realm of the subject innovation.

Moreover, additional frame preambles can be employed followed by a series of frames. Further acquisition information such as timing and other information sufficient for an access terminal to communicate on one of the carriers and basic power control or offset information may also be included in the superframe preamble. In other cases, only some of the above and/or other information can be included in the frame preamble and or subframes. Moreover, each frame can further identify a number of subcarriers that can simultaneously utilized for transmission over some defined period.

In a related aspect, such transfer of the SRNC via updatable UATIs can occur without interruption of the data stream between the AT326,327and the wireless communication system. Moreover, the AT326,327can recognize each base station and can communicate directly therewith, wherein the SRNC can act as the coordinator of negotiations that the AT has conducted with such base stations.

FIG. 4illustrates a related methodology400of transferring a session from a source SRNC to a target SRNC according to an aspect. While the exemplary method is illustrated and described herein as a series of blocks representative of various events and/or acts, the various aspects is not limited by the illustrated ordering of such blocks. For instance, some acts or events may occur in different orders and/or concurrently with other acts or events, apart from the ordering illustrated herein, in accordance with the various aspects described herein. In addition, not all illustrated blocks, events or acts, may be required to implement a methodology in accordance with the subject innovation. Moreover, it will be appreciated that the exemplary method and other methods according to the innovation may be implemented in association with the method illustrated and described herein, as well as in association with other systems and apparatus not illustrated or described. Initially and at410, changes in the base station serving the AT can be detected, which prompt a change between a source SRNC and a target SRNC. Next and at420UATI associated with the source SRNC can be updated to designate the target SRNC. At430, a session can transfer ownership from the source SRNC to the target SRNC. Such transfer of ownership from the source SRNC to the target SRNC supplies decoupling of management of the session from connection management of the session at440. Accordingly, session management becomes independent of connection management, wherein if a session is to be moved, such does not necessarily require moving the associated connection therewith. Such is in contrast to conventional systems that require the connection to be moved if the session is moved, which can further induce interruptions.

FIG. 5illustrates a further methodology500of transferring ownership of a session from a source SRNC to a target SRNC according to an aspect. Initially and at510, a source SRNC and a target SRNC are positioned in a route set for exchange of messages. Subsequently and at520, a message related to an SRNC transfer request can be sent to the source SRNC from the target SRNC. At530, the source SRNC can then supply UATI sequence numbers (e.g., an increasing number associated with UATI) and signify for base stations the sequence numbers supplied for the target SRNC. Moreover, the target SRNC can supply the updated UATI to the AT. Upon receipt of such message by the AT, it subsequently responds with UATI complete message to the target SRNC to indicate agreement with updated UATI and transfer to the assigned target SRNC. At540, the target SRNC can then announce to members of route associated therewith (e.g., the source SRNC and the serving eBS) that the UATI has changed and the target SRNC has now taken ownership of the session. Likewise, base stations can change their associated UATI to that of the target SRNC.

FIG. 6illustrates an exemplary call flow600of SRNC transfer according to a further aspect, wherein it can be assumed that the source SRNC and the target SRNC are already in the Route Set (e.g., communicate with each other). As illustrated, initially and at610, the target SRNC sends an Inter-Access Network Signaling (IAS)-SRNC Transfer Request message to the source SRNC to request a session reference transfer and starts timer Tstr-ias. Such timers are employed to increase reliability of the message exchange procedures.

Subsequently, and at620, the source SRNC responds to the target SRNC with an IAS-SRNC Transfer Response message. Such message includes a new UATI_SeqNo (for the new UATI). Once the source SRNC sends the IAS-SRNC Transfer Response message, a session associated therewith can be locked. Such session locking can include rejects of any further session modification—and yet still acceptance request for a copy of the session and also request to page the AT. Upon receipt of the IAS-SRNC Transfer Response message, the target SRNC halts timer Tstr-ias. The target SRNC can also lock its session.

At630, the target SRNC sends UATIAssign message containing the new UATI to the AT. Subsequently and at640, upon receipt of the UATIAssign message, the AT sends UATIComplete messages to the target SRNC. Upon receipt of the UATIComplete message or signaling message addressed to the new UATI, the target SRNC unlocks its session, e.g., it allows session configuration, and sends IAS-UATI Update message to all ANRIs in the Route Set.

Next and at640, upon receipt of the IAS-UATI Update message with a new UATI_SeqNo, the source SRNC releases the old UATI and sends IAS-UATI Update Ack message back to the target SRNC. Upon receipt of the IAS-UATI Update Ack message, the target SRNC unlocks the session and stops timer Tuupd-ias.

FIG. 7illustrates a call flow700when Route Set Add occurs during a session reference transfer. Such call flow700assumes that the source SRNC and the target SRNC are already in the Route Set while eBS1is not in the Route Set yet. Initially and at710, the target SRNC sends an IAS-SRNC Transfer Request message to the source SRNC to request a session reference transfer and starts timer Tstr-ias.

Next and at720the source SRNC locks its session and responds to the target SRNC with an IAS-SRNC Transfer Response message. Such message includes the new UATI_SeqNo (for the new UATI). Upon receipt of the IAS-SRNC Transfer Response message, the target SRNC stops timer Tstr-ias.

Subsequently and at730the target SRNC sends a UATIAssign message containing the new UATI to the AT. However, before the message is received at the AT, the AT sends RouteOpenRequest message to the eBS1with old UATI to add the eBS1into the Route Set. At740, eBS1sends an IAS-Session Information Request message addressing the old UATI, to the source SRNC with a flag indicating this is for Route Set Add and starts timer Tsir-ias.

At750, the source SRNC accepts the request for session by sending an IAS-Session Information Response message with the session information. Upon receipt of the IAS-Session Information Response message, the eBS1stops timer Tsir-ias.

Subsequently, at760, the AT receives the UATIAssign message from the target SRNC. Next, at770, upon receipt of the UATIAssign message, the AT sends UATIComplete message to the target SRNC. As such and upon receipt of the UATIComplete message or a signaling message addressed to the new UATI, the target SRNC unlocks its session, wherein session configuration can be enabled, and sends IAS-UATI Update message to all ANRIs in the Route Set.

At780, the target SRNC sends an IAS-UATI Update message with the new UATI and the new UATI_SeqNo to the source SRNC and starts timer Tuupd-ias.

Moreover, at790, upon receipt of the IAS-UATI Update message, the source SRNC releases the old UATI and sends an IAS-UATI Update Ack message back to the target SRNC. Upon receipt of the IAS-UATI Update Ack message, the target SRNC stops timer Tuupd-ias. At792, the AT receives a RouteOpenAccept message from eBS1in response to the RouteOpenRequest message in act730. Subsequently, at794, the AT sends RouteMapStatus message to all ANRIs in the Route Set, including the target SRNC.

Next, at796, upon receipt of the RouteMapStatus message which contains the new eBS1in the Route Set, the target SRNC sends IAS-UATI Update message containing the new UATI and the new UATI_SeqNo to eBS1and starts timer Tuupd-ias.

Next, at799, upon receipt of the IAS-UATI Update message, eBS1sends an IAS-UATI Update Ack message to the target SRNC. Upon receipt of the IAS-UATI Update Ack message, the target SRNC stops timer Tuupd-ias.

FIG. 8illustrates a further flowchart in accordance with a further aspect. Such flowchart describes the call flow when session negotiation is attempted during a session reference transfer. The call flow800assumes that eBS1891, the source SRNC892and the target SRNC893are already in the Route Set. Initially, at801, the target SRNC893sends an IAS-SRNC Transfer Request message to the source SRNC892to request a session reference transfer and starts timer Tstr-ias.

Subsequently, at802, the source SRNC892locks its session and responds to the target SRNC893with an IAS-SRNC Transfer Response message. This message includes the new UATI_SeqNo (for the new UATI). Upon receipt of the IAS-Session Information Request message, the target SRNC893stops timer Tstr-ias. The target SRNC sends UATIAssign message containing the new UATI to the AT. However, before the message is received at the AT, the AT and eBS1initiate session negotiation at803.

Next, at804, in order to complete session negotiation, eBS1891sends IAS-Session Information Update Request message with the old UATI to the source SRNC892and starts timer Tstir-ias. At805, the source SRNC rejects the request by sending an IAS-Session Information Update Response message to eBS1891with the error cause value indicating that the session is locked. Upon receipt of the IAS-Session Information Update Response message, eBS1stops timer Tsir-iasand eBS1may retry updating the session at the SRNC after it receives an IAS-UATI Update message or may terminate session negotiation with the AT895. Next, at806, the AT receives UATIAssign message from the target SRNC.

Subsequently and upon receipt of the UATIAssign message, the AT sends UATIComplete message to the target SRNC at807. Upon receipt of the UATIComplete message or a signaling message addressed to the new UATI, the target SRNC unlocks its session, wherein, it can allow session configuration, and sends an IAS-UATI Update message to all ANRIs in the Route Set, including the source SRNC and eBS1.

Next, at808, the target SRNC sends an IAS-UATI Update message with the new UATI to the source SRNC and starts timer Tuupd-ias. At809, and upon receipt of the IAS-UATI Update message, the source SRNC releases the old UATI and sends an IAS-UATI Update Ack message back to the target SRNC. Upon receipt of the IAS-UATI Update Ack message, the target SRNC stops timer Tuupd-ias.

Subsequently, at810, the target SRNC sends an IAS-UATI Update message with the new UATI to eBS1and starts timer Tuupd-ias. At811, upon receipt of the IAS-UATI Update message, eBS1uses the new UATI and sends an IAS-UATI Update Ack message back to the target SRNC. Upon receipt of the IAS-UATI Update Ack message, the target SRNC stops timer Tuupd-ias. Next, at812, upon receipt of the IAS-UATI Update message, eBS1sends IAS-Session Update Request message with the new UATI to the target SRNC and starts timer Tsur-ias.

Subsequently, at813, the target SRNC accepts the request by sending an IAS-Session Update Response message to eBS1with the new session signature. Upon receipt of the IAS-Session Update Response message, eBS1stops timer Tstir-ias. Accordingly, at814, eBS1and the AT complete session negotiation using the new session signature.

FIG. 9illustrates a related call flow900that illustrates an exemplary session reference transfer where the AT999does not receive the UATIAssign message. Such call flow900assumes that the source SRNC991and the target SRNC993are already in the Route Set while eBS1997is not yet in the Route Set. Initially, at910, the target SRNC993sends an IAS-SRNC Transfer Request message to the source SRNC991to request a session reference transfer and starts timer Tstr-ias.

Next, at911, the source SRNC991responds to the target SRNC993with an IAS-SRNC Transfer Response message. This message includes the new UATI_SeqNo (for the new UATI). Upon receipt of the IAS-SRNC Transfer Response message, the target SRNC993stops timer Tstr-ias. Subsequently, at912, the target SRNC993sends UATIAssign message containing the new UATI to the AT999. However, the AT999does not receive the message, as it has lost its connection.

During this period, if the source SRNC991receives a Paging Request message, then the source SRNC991shall initiate a paging procedure for the AT999using the old PageID. Likewise, if the UATIComplete message is not received, then the source SRNC and the target SRNC993can release the new UATI once its session KeepAlive timer expires. At913, the AT999accesses eBS1997by sending a RouteOpenRequest with the old UATI to eBS1997. Subsequently, at914, eBSN1sends an IAS-Session Information Request message to the source SRNC with a flag indicating this is an access and starts timer Tsir-ias.

Next, at915, upon receipt of the IAS-Session Information Request message with the old UATI and access flag, the source SRNC unlocks the session and responds to eBS1with an IAS-Session Information Response message. Such message contains the current session, the current Data Attachment Point (DAP), and the current session signature. Upon receipt of the IAS-Session Information Response message, the eBS1stops timer Tsir-ias.

Subsequently, at916, the eBS1sends a RouteOpenAccept message to the AT to complete the route setup procedure with the AT. Likewise, at917, the AT sends a RouteMapStatus to all ANRIs in the Route Set. Next, at918, upon receipt of the IAS-Session Information Request with the old UATI and access flag, the source SRNC also sends an IAS-UATI Update message to the target SRNC to inform the target SRNC that it may release the new UATI. Then, the source SRNC starts timer Tuupd-ias.

Subsequently, at919, upon receipt of the IAS-UATI Update message, the target SRNC releases the new UATI and sends an IAS-UATI Update Ack message back to the source SRNC. Upon receipt of the IAS-UATI Update Ack message, the source SRNC stops timer Tuupd-ias. Accordingly, the call flow900exemplifies a scenario that enables the source controller to recall the session and retain ownership by the source controller, if the UATIAssign message is lost.

FIG. 10illustrates a further exemplary aspect of a call flow1000, which describes a failure scenario for a session reference transfer where the UATIComplete message is lost. Such call flow1000assumes that the source SRNC and the target SRNC are already in the Route Set while eBS1is not yet in the Route Set. Initially, at1001, the target SRNC sends an IAS-SRNC Transfer Request message to the source SRNC to request a session reference transfer and starts timer Tstr-ias. Next, at1002, the source SRNC responds to the target SRNC with an IAS-SRNC Transfer Response message. This message contains the new UATI_SeqNo (for the new UATI). Upon receipt of the IAS-SRNC Transfer Response message, the target SRNC stops timer Tstr-ias.

Subsequently, at1003, the target SRNC sends UATIAssign message containing the new UATI to the AT. Next, at1004, the AT sends a UATIComplete message to the target SRNC. However, as illustrated inFIG. 1000, the AT loses its connection before the message is delivered. During such period, if the source SRNC receives a Paging Request message, then the source SRNC shall initiate a paging procedure for the AT using the old PageID. It is to be appreciated that the AT monitors both the old PageID and the new PageID if the UATIComplete message has not been sent successfully. Moreover, if the UATIComplete message is not received, then the source SRNC and the target SRNC may release the new UATI once its session KeepAlive timer expires. At1005, the AT accesses eBS1by sending RouteOpenRequest message with the new UATI.

Next, at1006, eBS1sends an IAS-Session Information Request message with a flag indicating this is an access to the target SRNC and starts timer Tsir-ias. At1007, and upon receipt of the IAS-Session Information Request message with the new UATI, the target SRNC unlocks the session and sends IAS-Session Information Response message to eBS1. The message contains the session of the AT. Upon receipt of the IAS-Session Information Response message, the eBS1stops timer Tsir-ias.

Subsequently and at1008, eBS1sends a RouteOpenAccept message to the AT to complete route setup procedure. Next, at1009, the AT sends a RouteMapStatus message to all ANRIs in the Route Set, including eBS1and the target SRNC. At1010, upon receipt of the IAS-Session Information Request message with the new UATI, the target SRNC sends an IAS-UATI Update message to the source SRNC and starts timer Tuupd-ias. Next, at1011, upon receipt of the IAS-UATI Update message, the source SRNC sends an IAS-UATI Update Ack message to the target SRNC and may release the old UATI. Upon receipt of the UATI Update Ack message, the target SRNC stops timer Tuupd-ias. As such, the telecommunication system can recover during a failure scenario for a session reference transfer where the UATIComplete message is lost.

FIG. 11illustrates a particular system1100that facilitates transfer for ownership of a session from a source SRNC to a target SRNC. The system1100can be associated with an access point and includes a grouping1102of components that can communicate with one another in connection with transfer of session ownership, and supplying updates to the UATI.

Grouping1102also includes a component1106for transferring a session from a source SRNC to a target. Such grouping can further include components for tracking session signatures (not shown) and a component for supplying QoS configuration1107, wherein if a session is to be moved, such does not necessarily require moving the associated connection therewith. Grouping1102additionally includes a component1108for receiving communication data and/or message exchange from a source SRNC, wherein the data is desirably transmitted to the AT and/or target SRNC. Moreover, the communication data received from the AT can be an IP-encapsulated data packet that is associated with a sequence number or stamp. Grouping1102can further include a component1110for transmitting communication data (e.g., message exchange) to the target SRNC1110in an appropriate sequence. System1100can also include a memory1112, which can retain instructions relating to executing components1104-1110. The system1100further includes a component1104for notifying base stations and other units in communication with the AT of the session transfer and/or the identity of the target SRNC.

FIG. 12illustrates a system1200that can be employed in connection with interaction with a session transmitted to a target SRNC according to an aspect. System1200comprises a receiver1202that receives a signal from, for instance, one or more receive antennas, and performs typical actions thereon (e.g., filters, amplifies, downconverts, . . . ) the received signal and digitizes the conditioned signal to obtain samples. A demodulator1204can demodulate and provide received pilot symbols to a processor1206for channel estimation.

Processor1206can be a processor dedicated to analyzing information received by receiver component1202and/or generating information for transmission by a transmitter1214. Processor1206can be a processor that controls one or more portions of system1200, and/or a processor that analyzes information received by receiver1202, generates information for transmission by a transmitter1214, and controls one or more portions of system1200. System1200can include an optimization component1208that can optimize performance of user equipment before, during, and/or after handoff. Optimization component1208may be incorporated into the processor1206. It is to be appreciated that optimization component1208can include optimization code that performs utility based analysis in connection with determining whether to initiate session handoff from the source SRNC to the target SRNC system. The optimization code can utilize artificial intelligence based methods in connection with performing inference and/or probabilistic determinations and/or statistical-based determination in connection with performing handoffs.

System (user equipment)1200can additionally comprise memory1210that is operatively coupled to processor1206and that stores information such as signal strength information with respect to a base station, scheduling information, and the like, wherein such information can be employed in connection with determining whether and when to initiate and/or request a session handoff. Memory1210can additionally store protocols associated with generating lookup tables, etc., such that system1200can employ stored protocols and/or algorithms to increase system capacity. It will be appreciated that the data store (e.g., memories) components described herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. By way of illustration, and not limitation, nonvolatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). The memory1210is intended to comprise, without being limited to, these and any other suitable types of memory. Processor1206is connected to a symbol modulator1212and transmitter1214that transmits the modulated signal.

FIG. 13illustrates base station functions, wherein the base stations control the connection, which represent an assignment of resources (e.g., dedicated resources) that allow an Access Terminal (AT) to communicate with an Access Network (AN). As illustrated, the system1300comprises a base station1302with a receiver1310that receives signal(s) from one or more user devices1304by way of one or more receive antennas1306, and transmits to the one or more user devices1304through a plurality of transmit antennas1308. In one example, receive antennas1306and transmit antennas1308can be implemented using a single set of antennas. Receiver1310can receive information from receive antennas1306and is operatively associated with a demodulator1312that demodulates received information. Receiver1310can be, for example, a Rake receiver (e.g., a technique that individually processes multi-path signal components using a plurality of baseband correlators, . . . ), an MMSE-based receiver, or some other suitable receiver for separating out user devices assigned thereto, as will be appreciated by one skilled in the art. For instance, multiple receivers can be employed (e.g., one per receive antenna), and such receivers can communicate with each other to provide improved estimates of user data. Demodulated symbols are analyzed by a processor1314that is similar to the processor described above with regard toFIG. 11, and is coupled to a memory1316that stores information related to user device assignments, lookup tables related thereto and the like. Receiver output for each antenna can be jointly processed by receiver1310and/or processor1314. A modulator1318can multiplex the signal for transmission by a transmitter1320through transmit antennas1308to user devices1304.

In one or more aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. A storage medium may be any available media that can be accessed by a computer. By way of example,such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other similar medium that can be used to store desired program code in the form of instructions or data structures and that can he accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.