Method and apparatus for handoff of a wireless packet data services connection

A method and apparatus for handoff of a wireless packet data service connection {METHOD AND APPARATUS FOR HANDOFF OF A WIRELESS PACKET DATA SERVICES CONNECTION}

<b>background</b>

<b>field</b>

The present invention relates to wireless communications. More specifically, the present invention relates to a novel method and apparatus for performing seamless handoff of a mobile station between radio access networks having different wireless interfaces during wireless packet data service operation.

<b>background</b>

To meet the growing demand for data communication in a wireless communication system, the radio network is designed to Internet Protocol (IP) interface with packetized data networks supporting network. The PDSN (Packet Data Service Node: PDSN) provides an interface between the wireless network and the IP network, or other data network. Such as "mobile IP" and a variety of protocols specifies the interface between the radio network and the PDSN.

A mobile station (MS) moves from the serving PDSN to the serving area of ​​the other regions of the single PDSN, MS associated with a home agent (Home Agent: HA) configuration information is updated so as to guide the communication member. An effective method for enabling movement in the communication system.

<b>Brief Description of the Drawings</b>

Feature of the invention, objects, and advantages will, with reference to the accompanying drawings that the same reference symbols identify corresponding throughout the figures, it is apparent from the detailed description set forth below.

Figure 1a is a wireless system configuration using only 1x radio access networks (RAN).

Figure 1b is a wireless system configuration illustrating packet zone identification.

Figure 1c is a diagram showing a flow path in a communication system supporting Internet Protocol (IP) communication.

Figure 1d is a part of a wireless communication system as in Figure 1 b.

2 is a message flow diagram illustrating an IP address assigned to the MS (2) in accordance with the mobile IP standard.

Figure 3 is a wireless system configuration using only HDR radio access networks (RAN).

Figure 4 is a wireless system configuration using 1x and HDR radio access networks (RAN).

5 is a flow chart illustrating the process used by a mobile station during handoff international identity (IMSI) to perform authentication, MS 1x RAN between the HDR RAN.

6 is a message flow diagram illustrating the updating of the location parameters for the access nodes in a wireless communication system.

7 is a flow chart illustrating the update of the location parameter at each PCF in a wireless communication system.

Figure 8 is a block diagram of an access terminal (AT).

Figure 9 is a block diagram of a mobile station (MS).

10 is a block diagram of an Access Network (AN) element.

<b>details</b>

"Exemplary" is herein the term "for example, which serves as silye, or illustration" is used to mean. Any embodiment described as an "exemplary embodiment" is preferred to be in the other embodiments disclosed herein, or should not be interpreted as beneficial.

Code division multiple access (Code Division Multiple Access: CDMA) modulation techniques is one Using the technique of several techniques for facilitating communications systems present a number of users. Time division multiple access (Time Division Multiple Access: TDMA), frequency division multiple access (Frequency Division Multiple Access: FDMA), and amplitude companding single sideband (Amplitude Companded Single Sideband: ACSSB), such as AM modulation of different multiple-access communication system techniques are known in the art. These techniques have been standardized to facilitate the interaction between equipment manufactured by different companies. Code division multiple access communication system has been standardized in Telecommunications Industry Association TIA / EIA / IS-95-B in the United States, "Dual-Mode Wideband Spread Spectrum mobile station for a cellular system-Base Station Compatibility Standard (MOBILE STATION-BASE STATION COMPATIBILITY STANDARD was named FOR DUAL-MODE WIDEBAND SPREAD SPECTRUM CELLULAR SYSTEMS) "La, here referred to as IS-95. In addition, a new standard for CDMA communication systems have been proposed in the Telecommunications Industry Association (TIA) in the United States, 27 October 2000 Here, "CDMA 2000 upper layer for spread spectrum systems (Layer 3) Signaling Standard, A plate Appendix 1 (Upper Layer (Layer 3) Signaling Standard for cdma 2000 Spread Spectrum Systems, Release A - Addendum 1) "was named, in this case" 1x "La referred to. Additional standard for providing high speed data services in the TIA is "CDMA 2000 High Rate Packet Data Air Interface Specification (cdma 2000 High Rate Packet Data Air Interface Specification) La was named, in this case," referred to as HDR "or" IS-856 " The International Telecommunications Union requested the submission of proposed methods for providing high-speed data and high-quality voice service to the last radio channel. The first of these proposals was issued by the proposed Telecommunications Industry Association, the title "IS- 2000 ITU-R RTT Candidate Submission (The IS-2000 ITU-R RTT Candidate Submission) "is the second proposal of such a proposal was presented by the European Telecommunications Standards Institute (ETSI), the title" ETSI UMTS Terrestrial Radio Access (UTRA) ITU-R RTT candidate submission (The ETSI UMTS Terrestrial Radio Access (UTRA) ITU-R RTT Candidate Submission) ", and also" wideband CDMA "to inform was less than the" W-CDMA "referred to third proposal was submitted by US TG 8/1, and the title of "UWC-136 Candidate Submission (The UWC-136 Candidate Submission)", hereinafter referred to as "EDGE". The contents of these proposals are public records, and the art it is known.

delete

Is optimized for the transmission of the voice frame rate - is the original IS-95 variable. After the standards are various additional non-comprising the packet data service was established as a standard that supports voice services. One such set of packet data service is in the United States in Telecommunications Industry Association TIA/EIA/IS-707-A been standardized, the title "Spread Spectrum Systems for the data service option (Data Service Option for Spread Spectrum Systems)", and here, has been incorporated by reference, it is referred to as "IS-707" hereinafter.

IS-707 describes techniques used to provide support to sending over the IS-95 wireless network to the Internet Protocol (IP) packets. Packet is encapsulated (encapsulate) in point-to-point protocol (PPP) byte stream, is called a normal call using a protocol. Using PPP, IP datagrams having lengths of up to 1500 bytes can be transmitted in any fragment size over the wireless network. The wireless network maintains PPP state information for the PPP session time period, or the long additional bytes that can be sent in the continuous byte stream between the PPP end points.

Packet-data-available remote network node such as a personal or laptop computer (PC) connected to a wireless mobile station (MS) may access the Internet through a wireless network in accordance with the IS-707 standard. As used throughout the following description, it refers to the MS, Access Node (AN), Mobile Node (MN) and remote station (remote station), each term of the mobile participant in a wireless communication (mobile participant). Alternatively, the remote network node such as a web browser is installed in the MS, which makes the PC optional. The MS may be to any of the PC card, a personal digital assistant (PDA), external or internal modem, or wireless phone or terminal, including, but not limited number of types of devices. The MS sends data through the wireless network, where the data is processed by a packet data service node (PDSN). Typically, the PPP state for a connection between the MS and the wireless network is maintained in the PDSN. The PDSN is connected to an IP network such as the Internet, and transmits data between the different entities and agents connected to the wireless network and the IP network. In this manner, MS can transmit data to another entity on the IP network through the wireless data connection and receive data from other entities. In addition, the corresponding node is called the target entity on the IP network is called.

MS will be required to obtain the IP address before sending and receiving IP packets over the IP network. In some early implementations, MS was assigned an IP address from a pool of addresses that belong exclusively to the PDSN (pool). Each PDSN was connected to one or more radio access network (RAN) associated with a limited geographical area. As the MS get out of the area served by the PDSN 1, numbered address data to the MS via the PDSN it could not reach the MS 1. When the MS enters the area served by the first PDSN 2, it had MS must receive a new IP address from the address assigned to the space of the 2 PDSN. Ongoing connection to the corresponding node based on the old IP address is abruptly terminated.

When moving from PDSN to PDSN connection is to prevent the loss, MS utilize a protocol known as mobile IP. IETF (Internet Engineering Task Force) is titled "IP Mobility Support (IP Mobility Support)" is, October 1996 letter published, and the art in a known, RFC (request for comments) 2002 in a standardized IP to have . CDMA 2000 in the network using the mobile IP, June 2000 issue of "Wireless IP Network Standard {Wireless IP Network Standard}" has been standardized in EIA / TIA / IS-835 entitled, hereinafter, it will be referred to as "IS-835" . In mobile IP, the PDSN does not provide an IP address from the PDSN own address pool. Instead, PDSN operates as a foreign agent (FA) that facilitates the address assignment from the home agent (HA) located somewhere in the IP network. MS is in communication to the HA via the FA, and receives an IP address assigned from an address pool belonging to the HA. When the MS moves from the PDSN to the 2 1 PDSN, the MS communicates through the second PDSN and FA in order to re-register 2 in the HA IP address of an existing MS.

IS-707 and IS-835 has been established for the transmitted packet data, the sleep mode will be described that a radio link has been idle for a period of time by the network without terminating the re-associated PPP session (dormant mode). When the flow of packet data restart, without having to repeat PPP configuration and negotiation the wireless link is re-established. Preserving the PPP state when the MS and the wireless network is packet data to be re-establishes a PPP state when the wireless link is terminated to resume the transmission more quickly.

The proposed 1x standard provides mechanisms to update routing between an HA and multiple PDSN and 1x RAN. The proposed HDR standards provide mechanisms to update routing between an HA and multiple PDSN and HDR RAN. The HDR and 1x standards all the RAN for a change even when the MS in idle mode, the MS does not move to a RAN using a different type of wireless interface, it is possible to effectively update packet routing. For example, when the MS moves from a 1x RAN to an HDR RAN while dormant, routing ambiguities or redundancies can occur, packets may be lost. According to these various systems are deployed, there is a need for different types of routing packets to the MS to move between RAN using the air interface mechanism to efficiently update.

Fig 1a 1x radio access networks (RAN; 32, 34, 36) shows a network configuration in a system using only. In one embodiment, a personal or laptop computer (PC; 4) is a mobile station (MS; 2) via the data connection 12 is connected to. Data connection between the PC and the MS (2) (12) may use a physical cable such as an Ethernet, serial, or universal serial bus (USB) cable. Alternatively, the data connection 12 is a wireless connection such as an infrared or other optical connection; Or it may be a Bluetooth, or IEEE 802.11, such as wireless (radio) connection. As described above, the PC is optionally incorporated into the MS (2) may enable network access through a single device. In the drawing, MS (2) is a RAN_A (32), RAN_B 34, and RAN_C 36, the coverage area associated with (6, 8, and 10) to change the physical location of the MS (2) between. RAN_A 32 and RAN_B 34 PDSN_One 14 is connected to, PDSN_One 14 is connected to an IP network 18, in this order. RAN_C 36, the PDSN₂ 16 is connected to, and then the PDSN₂ 16 is connected to the IP network 18. In addition, the home agent (HA; 20), authentication, authorization, and billing (authentication, authorization and accounting: AAA) server 22, and a corresponding node (24) is accessible through the IP network 18. PDSN with a number of additional, the HA, the AAA server, and the corresponding nodes have been omitted for simplicity, but can be connected to the IP network 18.

The MS (2) RAN, for example RAN_A The first connection to the (32), MS (2) is It should be to obtain an IP address from any of the entities associated with the IP network 18. As described above, in early implementations MS (2) receives an IP address assigned from an address pool allocated to the PDSN (14). Since all packets having the IP address from that pool of addresses are routed to the PDSN (14) by IP network (18), PDSN (14) can be routed to an MS (2) that corresponds to such a packet. However, if the MS (2) is moved out of the coverage of any RAN connected to the PDSN (14), PDSN (14) can not pass any more packets to the MS (2). For example, MS (2) The RAN_A From the coverage area of ​​the RAN 32_C When moving to the coverage area of ​​the (36), MS (2) the PDSN₂ (16) it must obtain a new IP address from the address pool. PDSN_One It is discarded, and any packets transmitted by 14 and the related billing address, ongoing network connections using the old address is no longer used.

In more recent mobile IP implementations, the MS (2) obtains the IP address of the MS (2) from the HA (20) connected to the IP network instead. After obtaining the address from the HA (20) pool associated with the mobile IP protocol, MS (2) is any of a number of RAN (32, 34, or 36) or through any of a number of PDSN (14 or 16) be able to receive a packet having the IP address through. In another method for the dynamic allocation of IP address from the HA (20), MS (2) also, for activation of the example service, within the address pool of the HA (20) prepared in the memory of the pre-MS (2) IP It may have an address.

Figure 1b illustrates a packet data network 100 according to an embodiment. Other embodiments may have different terminology for similar functional units, it is possible to merge the components and functional parts of different configurations. For this discussion, Figure 1 b, and a detailed view of the other network 100, but used to define a path, other embodiments may define a path according to the specific configuration and functions used. Packet data system 100 includes two System Identification (SID) zones 110, 120, each of which identifies a number of network (NID) zones (112, 114, 116, 122, 124, 126) have. SID / NID are used in voice systems and generally identify a serving area is. For example, MSC serving area is associated with a pair of (SID, NID) values.

For the packet data communications within a system supporting packet data communications, such as system 100 of Figure 1b, the mobile IP communication and Mobile IP connectivity is referred to RFC 2002, C. Perkins (Perkins C.) Dated October 1996 by It is described in "IP Mobility Support". Figure 1c is a predetermined mobile node (MN; 260) according to mobile IP illustrates the flow of information in datagrams for the mobile station or (MS). As illustrated, each mobile node 260 is a network or sub-network different from the network or sub-host or a router for changing the connection point to the network. The mobile node may change its location without changing its IP address; Link to the contact points - if the layer connectivity is available, using the IP address can continue to communicate with other Internet nodes at any location. Each mobile node 260 has an associated home agent 252. The home agent 252, mobile node 260 is distant from the groove, while maintaining the current location information for the mobile node 260, the datagram is passed to the mobile node 260, a tunneling (tunnel) to is a router on the home network of the mobile node.

The foreign agent 254, which provides routing services to the mobile node 260 while registered, a network router, the mobile node is visiting. The foreign agent 254 is transmitted to the tunnel (detunnel) and the mobile node 260 is de-tunneled datagram by the home agent 252 of the mobile node. For the datagram transmitted by the mobile node 260, the foreign agent 254 may function as a default (default) router for registered mobile nodes.

For long-term home agent (long-term) IP address is assigned to the mobile node (260). The home address is "permanent" IP address is provided to operate in the same manner as the stationary host. When away from the home network, "Management of address" is associated with the mobile node 260 to reflect the current point of attachment to the mobile node. The mobile node 260 uses the source address of all IP datagrams that the mobile node sends the home address. When away from home, the mobile node 260 registers the address management in the home agent (252). Depending on the access scheme, the mobile node 260 is registered with the direct or the home agent 252 of the mobile node 260 is registered with the foreign agent 254 to forward the registration to the home agent (252).

For the system 100 of Figure 1 b, is a conventional configuration in each PZID is illustrated in FIG. 1D. Packet Data Service Node (PDSN; 302) is coupled to a Packet Control Function (PCF) nodes (304 and 310), the packet control function (PCF) node (304, and 310) are each of a base station controller (BSC) BSC_One 306 and BSC₂ It is respectively connected to 312. A first communication path from the PCF PDSN (302)_One Through (304) BSC_One 306 is defined by a, BSC_One 306 communicate over the mobile node (308) and the air interface in the PZID (320). The mobile node (MN; 308) when moved to another PZID, such as PZID (330), in the PCF PDSN (302)₂ 310 through BSC₂ The new path is established for packet data communications defined by the (312), BSC₂ 312 communicate over the mobile node (308) and the air interface in the PZID (320). PDSN (302) from the PCF_One 304 and PCF₂ Path connection to the (310) defines the A10 connection. PCF_One 304 to a BSC_One Path Connection and the PCF of the 306₂ From (310) BSC₂ 312 connected to the path defines the A8 connection. The PPP connection is established between the mobile node (308) and the PDSN (302). When the MN changes the PDSN, a new PPP connection is established between the MN and the new PDSN.

For calls supporting packet data services, the interface between the data transmission on the data transmitted from the fixed network and the air interface of the packet data service node (PDSN) is present. The PDSN may be located with the BS, to the BS via the interface may not be located in the packet control function (PCF). For the packet data system illustrated in Fig. 1D, MS (308) it may operate in one of at least three states or modes.

2 is a message flow diagram illustrating an IP address assigned to the MS (2) in accordance with the mobile IP standard. First, MS (2) the PDSN_One 14 and generates a radio connection to the RAN is connected, a first message 202 through a RAN PDSN_One The transmission (14). If the MS (2) is an international mobile station identity with (IMSI), the MS (2) transmits the IMSI in the first message (202). The first message 202 may be a type of one of several different types, depending on the connection state of the radio link between the supported types of air interface or MS (2) by the RAN and the RAN. For example, the first message (202) MS (2) that may be an origination message if it is not connected to the RAN, MS (2) If the communication has already been through the RAN and radio link agent request (solicitation) message It can be. The numbering in the example shown PDSN_One 14 represents the first message 202 also PDSN₂ 16 may be sent through a RAN connected to another PDSN such as.

In response to the first message (202), PDSN_One 14 responds with a message 204 containing an agent advertisement and authentication attempts. Advertising agent PDSN_One 14 identifies the address of the foreign agent (FA) in the. Authentication challenge is part of a handshake (Handshake) that prevents other network entities, either accidentally or intentionally using a different network identity to intercept data packets for the MS (2). MS (2); And authentication, and billing is applied (AAA) server 22 are programmed with shared secret information not available throughout the IP network 18. Before a shared secret information to send a request to the MS (2) the HA (20), the AAA server 22 to verify the identity of the MS (2). If the authentication from the AAA server 22 fails, MS (2) can not request an IP address from the HA (20). In one embodiment, the shared secret takes the form of a user name and password.

PDSN (14) upon receiving the attempt (challenge) in the message 204 received from, MS (2) is trying information to form a challenge response that to verify the identity of the HA (20) the MS (2) and combine the shared secret information used in the MS (2). For example, MS (2) is to combine the shared secret information and try information, uses a one-way hash (hashing) function. MS (2) is the message PDSN 206 including a attempted information, challenge response, and a registration request_One And transmitted back to 14. Thereafter, PDSN_One 14 passes information from the AAA server 22 to three fragments in the message 208. Using the same one-way hashing function, even though the shared secret information itself is never sent over the network, AAA server 22 can verify the shared secret information used by the MS (2). The AAA server 22 can be one of several brands (brand) or type. In one embodiment, a remote authentication dial in user service (Remote Authentication Dial In User Service: RADIUS) server is used.

If the AAA server 22 determines that it is attempting a request from the MS (2) is valid, the AAA server 22 forwards the registration request 210 to the HA (20). HA (20) has a pool of the MS (2) available IP address assigned to a mobile network entity, such as. Is an IP packet transmitted over an IP network (18) having a destination address from the address pool of the HA (20) is routed to the HA (20) by the IP network 18. On the basis of the contents of the registration request (210), HA (20) to form a registration response (212) including the IP address to be used as the source address in the packet to be transmitted to another network entity, by the MS (2). HA (20) is a PDSN_One 14, and transmits the response 212 to the FA in the. The FA records the IP address and associates it establishes a RAN-PDSN (RP) session. In one embodiment, FA are stored in a table indexed according to IP address information to the RP. To complete the assignment of the IP address for the MS (2), PDSN_One 14 transmits a message 214 to the MS (2) through the RAN. Message 214 contains the registration reply from the HA (20), includes an IP address assigned to the MS (2).

After the IP address of the MS (2) is registered, MS (2) starts to send the IP packet through the IP network 18. For example, MS (2) starts to communicate with the same, the corresponding node 24 and the web server. Packet transmitted by the MS (2) is assigned have the source address to the destination address and MS (2) of the corresponding node 24. All messages transmitted by the MS (2) the PDSN_One 14 are routed through the FA in the. The FA may send an outgoing packet directly to the IP network 18, or encapsulated in a numbered addresses of packets to HA (20). If the latter approach is selected, HA (20) is a PDSN_One Transmits the packet to de-encapsulation (decapsulating) the de-encapsulated packet received from (14) to a destination within the correspondent node 24.

The response from the corresponding node 24 has the destination address assigned to the MS (2) from the address pool belonging to the HA (20). All of these messages is routed to the HA (20) by the IP network 18. The HA (20) is monitored for each destination address of the received IP packet to identify the MS (2) and the associated PDSN (14). Then, HA (20) encapsulates the packet in a larger packet having a destination address of the PDSN (14). The encapsulated packet is received by the FA in the PDSN (14). FA de-encapsulates the packet and finds the destination IP address of the de-encapsulated packets in the table RP the FA. Then, FA forwards the packet through the RAN associated with the corresponding RP session. For the MS (2), the mobile IP process is all encapsulated, except for the de-encapsulation, and the additional bit for the transmission delay and clear (transparent).

In Figure 1a, MS (2) is a RAN_A The coverage area of ​​the 32 is shown as being located in the 6. In Figure 1a, all the RAN (32, 34, 36) is used in the air interface of the 1x type. Network using a 1x wireless interface use the IMSI for identifying the mobile station. The new MS to establish the radio link (2) transmits the IMSI of the MS 2 in the outgoing message. RAN is a home location register (HLR; not shown) to try and attempt a response message authenticates the IMSI by exchanging with. It is part of a wireless telephone network; HLR are described and known in the art standardized signaling system (SS7 7). Authenticate the IMSI of the mobile IP authentication is completed with respect to the above-described one-way hash function using a technique similar to the technique.

In one embodiment shown in FIG. 1A, MS (2) is first the 1 1x RAN_A 32 to establish the connection with and in relation to Figure 2 are registered in the HA (20) as described above. After mobile IP registration is complete, MS (2) uses an address from the address pool of a HA (20), PDSN_One Using a PPP state within the FA (14) and transmits the packet. In the 1x system, PDSN_One 14 identifies the MS (2) by the IMSI of the MS (2). RAN_A Within the coverage area 6 of (32), MS (2) is a RAN_A 32 monitors overhead messages broadcast from base stations in the. Among other types of information, those overhead messages RAN_A Identify the packet zone ID (PZID) of 32.

MS (2) The RAN_A 32 leaving the coverage area 6 of RAN and_B When it enters the coverage area 8 of (34), MS (2) is a RAN_B 34 decodes the overhead messages broadcast by the base station in. RAN_B Overhead message RAN_A And a PZID different PZID broadcast by the base station in the. The MS (2) is to detect a change in PZID, MS (2) is a RAN to "false source (fake origination)"_B The transmission (34). In one embodiment, the origination message includes the IMSI, the data transmission ready (DRS) field, and a PREV_PZID field in the MS (20). Since the source is a routing update for the first object, the DRS field is set to 0 point to MS (2) does not have a packet data to be transmitted. If the MS (2) is to have new packet data to be sent to the network, MS (2), using a source having a 1 in the DRS field originates a normal call. The PREV_PZID field MS (2) includes a PZID of the previous system was connected. RAN_B 34 is a serving PDSN of the IMSI and the PREV_PZID of the received outgoing and MS (2) MS (2), PDSN_One The transmission (14). PDSN_One 14, the IMSI from the MS (2) the PDSN_One Determining whether the existing PPP state within and having, MS (2) The RAN_A Came from 32 determines from the PREV_PZID value. PDSN_One The original RAN_A 32 and the destination RAN_B 34 because both are connected to, PDSN_One It may be generally the same PPP state to the destination guide member RAN (34). For some reason PDSN_One 14 is the same if the PPP state to the destination RAN re guide (34), PDSN_One 14 PDSN_One PPP state of the reset 14, and forces the MS (2) to establish a new PPP connection.

MS (2) The RAN_B The coverage area of ​​the 34 (8) leave the RAN_C When it enters the coverage area 10 of (36), MS (2) is a RAN_C 36 decodes the overhead messages broadcast by the base station in. RAN_C 36 overhead messages RAN_B And a broadcast PZID different PZID by 34. The MS (2) is to detect a change in PZID, MS (2) the IMSI of the MS (2), with DRS field value to 0, and the previous RAN the RAN_B 34 comprises a PREV_PZID identifying the PZID of the "false source" RAN_C Transmitted to the 36. RAN_C 36 is a serving PDSN of the IMSI and the PREV_PZID of the received outgoing and MS (2) MS (2), PDSN₂ The transmission (16). MS (2) is previously PDSN₂ Depending on whether or not whether been connected to (16), PDSN₂ 16 may have a PPP state associated with the IMSI of the MS (2). Or without a previous PPP state, PDSN₂ 16 determines whether the MS (2) come from the RAN from the PREV_PZID value connected to a different PDSN. PDSN₂ 16 will not be able to retrieve a PPP state from a different PDSN, as a result it is necessary to establish a new PPP session with the MS (2). PDSN₂ (16) with the old PPP session with the MS (2), and established, that PDSN₂ 16 means that the throw of the PPP session.

A new PPP session, the MS (2) and the PDSN₂ 16 then established between, PDSN₂ 16 PDSN₂ An agent advertisement message identifying the address of the FA within 16 and transmits it to the MS (2). Since each FA is different from the address, PDSN₂ Address of the FA 16 PDSN_One It is different from the address of the FA (14). When the MS (2) receives the agent advertisement having a different address, the MS determines whether the MS is to re-register its IP address to the HA (20). MS (2) are, for example, also be re-registered in the HA (20) to its IP address to the protocol described in connection with the second. Using the mobile IP authentication as described above, the HA (20) the MS (2) recognizes that the mobile was requesting the same IP addresses. If possible, HA (20) allocates the same IP address to the MS (2), and PDSN₂ 16, guide member and a message to that address as a destination. In general, HA (20) is the original PDSN, PDSN_One 14 does not send notification of the material guide path.

Figure 3 is the only HDR RAN (42, 44, 46) shows a network configuration in a system using only. MS (2) is first RAN_A It is located in the coverage area 6 of 42. In Figure 3, all the RAN (42, 44, 46) is used in an HDR type of wireless interface. HDR network using the air interface uses a unicast access terminal identifier (UATI) to identify a mobile station.

HDR RAN generally does not obtain an IMSI from the MS (2), the IMSI to permit identification of the RP session between the PDSN and assign priority to each of the MS (2). To provide the same IMSI support, HDR network can use the same type of PDSN used by 1x systems. In general, a strictly HDR network any IMSI authentication does not carry out, but is not connected to the SS7 wireless phone network.

MS (2) are, for example RAN_A 42 is connected to an HDR system through a first HDR RAN, such as 1, RAN_A And obtains a UATI from 42. Thereafter, RAN_A 42 is a packet data PDSN_One 14 to be routed by the FA in the to be assigned a temporary IMSI to the MS (2). Additionally, RAN_A 42, the case that can authenticate the IMSI, RAN_A 42 PDSN_One The actual IMSI according to (14) assigned to the link is established between the RP MS (2). RAN_A 42, the case that can authenticate the IMSI, RAN_A 42 may use the authentication center by using the AAA server or on the SS7 (22) authenticates the IMSI. Then, MS (2) is registered in the HA (20) as described above with respect to FIG. After mobile IP registration is complete, MS (2) is using the IP address assigned to the MS (2) by the HA (20) and, PDSN_One Using a PPP state within the FA (14) and transmits the packet. RAN_A Within the coverage area of ​​the (42), MS (2) is a RAN_A 42 monitors the overhead messages broadcasted by the base station in. In one embodiment, the overhead message MS (2) that when RAN_A The coverage area associated with the base station (42) includes information to determine if the placement in the 6. MS (2), the overhead message, which allows to identify the RAN associated with a coverage area is referred to as a subnet mask (subnet mask). MS (2) when it enters the coverage area to the other leaving a coverage area, the subnet mask received on the overhead channels will change accordingly.

MS (2) The RAN_A 42 leaving the coverage area (6) of the, RAN_B When it enters the coverage area 8 of (44), MS (2) is a RAN_B 44 decodes the overhead messages broadcast by the base stations of the. When the MS (2) detects a change in the subnet mask, MS (2) is a RAN_B It sends a UATI Update message to 44. UATI update message RAN_A And a UATI assigned to the MS (2) by 42. RAN_B 44 determines that the UATI is assigned by some other RAN, and contact the other HDR RAN connected to the same network for the UATI. As described above, the database UATI, PPP state information, IMSI, and other information is distributed among HDR RAN in a wireless network. Based on the previously assigned UATI, RAN_B 42 obtains the table information associated with the MS (2). RAN_A 42 and RAN_B (44) All the PDSN_One Because it is connected to (14), RAN_B 44 determines the temporary IMSI associated with the UATI of the MS (2) and, associated with that IMSI MS (2) The RAN_B 44, it informs the mobile hayeoteum the PDSN (14) in.

MS (2) The RAN_B Leaving the coverage area of ​​the (44) RAN_C When entering the coverage area of ​​the (46), MS (2) is a RAN_C 46 decodes the overhead messages broadcast by the base station in. RAN_C 46 overhead messages RAN_B 44 includes a sub-net mask is different from the sub-neck mask broadcast by the base station in. When the MS (2) detecting a change in the sub-neck mask, MS (2) is a UATI Update message containing the previously assigned UATI of the MS (2) RAN_C The transmission (46). RAN_C 46 receives the UATI Update message, PDSN₂ MS (2) is connected to a different RAN 16 to the contact to determine whether it has received a UATI assignment of the MS (2) from nearby RAN. MS (2) the PDSN_One RAN is connected to 14_B Since receiving the UATI assignment of the MS (2) in the (44), RAN_C 46 can not be re-guiding the PPP state to itself. Therefore RAN_C 46 is forced to allocate a new UATI to the MS (2) and MS (2) to establish a new PPP session. Thus, MS (2) the PDSN previous MS (2)_One 14 lose state information associated with the PPP session.

A new PPP session, the MS (2) and the PDSN₂ 16 then established between, PDSN₂ 16, the PDSN₂ The agent advertisement identifies the address of the FA within the message 16 and transmits it to the MS (2). Due to the different individual FA of address, PDSN₂ Address of the FA 16 PDSN_One It is different from the address of the FA (14). When the MS (2) to receive the agent advertisement having a different address, the MS determines whether the MS is to re-register its IP address to the HA (20). MS (2) are, for example, also be re-registered in the IP address of the MS (2) HA (20) according to the protocol described above in relation to the second. Using the above mobile IP authentication, HA (20) recognizes that the MS (2) that the mobile is requesting the same IP addresses. If possible, HA (20) is assigned the same IP address to the MS (2), then PDSN₂ 16, the guide member in a message to the address of the destination. In general, HA (20) is the original PDSN, PDSN_One It does not send notification of the material guide (14).

Figure 4 shows a HDR RAN to 52 and 56 and the network configuration in a system using a mixture of the 1x RAN (54). MS (2) is first RAN_A 52 is disposed inside the coverage area 6. MS designed to operate in a mixed HDR and 1x system 2 has the properties of both systems. For example, MS (2) is not only has the IMSI stored in memory, is programmed to connect to an HDR network using a UATI.

If the HDR RAN (52) and the HDR RAN (56) to perform the authentication of the IMSI, PDSN (14) and the PDSN (16) RP link and may be established using the actual IMSI of the MS (2) . IMSI authentication may be accomplished by an HDR RAN using an SS7 network or using the AAA server, the authentication center (22). In one embodiment, the MS (2) transmits the IMSI of the MS (2) at the beginning of HDR session negotiations HDR RAN. HDR RAN (52) and the HDR RAN (56) each of which can use the true IMSI of the PDSN (14) and the PDSN (16) and the MS to establish an RP link (2). Since using the 1x RAN (54) and the HDR RAN to 52 and 56 all have the same IMSI, PDSN can be prevented, and can easily resolve any routing ambiguity wrong routing any packets numbered address as the MS (2) have. Also, if the previous 1x RAN and the destination HDR RAN share a single PDSN is that, for example, RAN_A (52), RAN_B 54, and PDSN_One In the configuration similar to the configuration of (14), the PDSN can re-route the connection of the PDSN to the destination RAN RP, it is possible to re-use the existing PPP state.

However, HDR RAN (52) and the HDR RAN (56) the IMSI the authentication, that can not be the case, HDR RAN (52) and the HDR RAN (56) is a PDSN (14) and the PDSN (16) and the RP link for use to for it may create a temporary IMSI. 1x to the HDR RAN from the RAN, for example RAN_B 54 from RAN_A(52) Subsequent to the PDSN handoff_One It can cause routing problems in a shared PDSN such as 14. In one embodiment, the same routing problems caused by the generation of a plurality of RP session with the IP address or different IMSI can be solved with a small change to PDSN operation.

In one embodiment, MS (2) is an HDR system RAN_A 52 and connected to, RAN_A And obtains a UATI from 52. Thereafter, RAN_A 52 is a packet data PDSN_One 14 to be routed by the FA in the assigned a temporary IMSI to the MS (2). Then, MS (2) is registered in the HA (20) as described above with respect to FIG. After mobile IP registration is complete, MS (2) is to use the assigned IP address to the MS (2), PDSN_One Using a PPP state within the FA (14) and transmits the packet. RAN_A Within the coverage area 6 of (52), MS (2) is a RAN_A 52 monitors the overhead messages broadcasted by the base station in.

MS (2) The RAN_A 52 to leave the coverage area 6 of RAN_B When it enters the coverage area 8 of (54), MS (2) is a RAN_B 54 decodes the overhead messages broadcast by the base station in. As discussed above, RAN_B (54) 1x RAN such as the PZID is broadcast in the overhead channel of the 1x RAN. Thus, MS (2) is a RAN_A 52 receives a subnet mask from and, RAN_B It receives a PZID from 54. RAN_B From the overhead message received from the other (54), MS (2) determines the MS (2) whether or moving into the coverage of a network having a different type of wireless interface. As described below, MS (2) and the PDSN_One 14 is to be a particular care to prevent the packet towards the MS (2) is lost due to routing ambiguity.

In response to changes in the network, MS (2) is a RAN_B It sends a "false origination" containing the actual IMSI of the MS (2) to (54). As a result, RAN_B 54 is based on the actual IMSI of the MS PDSN (2)_One 14 and establish a new RP connection. PDSN_One 14 is not established when the MS (2) and the PPP state in the previous based on the actual IMSI, PDSN_One 14 negotiates the MS (2) with a new PPP state. A new PPP session, the MS (2) and the PDSN_One 14 then established between, PDSN_One 14 PDSN_One The agent advertisement identifies the address of the FA within 14 and transmits it to the MS (2). Because the PDSN not changed, FA address sent in the agent advertisement message RAN_A It is equal to the address received from the FA (52). As a result, MS (2) may not re-register the IP address of the MS (2) to the HA (20). MS (2) the IP address of the RAN MS (2)_A 52 was obtained from the HA (20) through because, RAN_A 52 was assigned a temporary IMSI to the MS (2). IP address to be used by the MS (2) the PDSN_One 14 is linked to the temporary IMSI in the FA within. MS (2) does not re-register the IP address of the MS (2) to the HA (20), PDSN_One 14, and the FA in the arrival, all network packets having the IP address used by the MS (2) is a RAN_A It is routed to a 52.

In one embodiment, MS (2) the MS (2) the HDR RAN (52), and from the coverage area of ​​an HDR RAN (56) each move to the coverage area of ​​a 1x RAN (54), carries out a Mobile IP re-registration. For example, MS (2) The RAN_A RAN from the coverage area 6 of 52_B When moving to the coverage area 8 of (54), FA address received in the agent advertisement message even be equal to that used just before, MS (2) is re-address of the MS (2) to the HA (20) Register.

Unfortunately, it does not entirely solve the routing ambiguity re-registration to the HA (20). MS (2) RAN is the IP address of the first MS (2)_A When obtained from the HA (20) through (52), PDSN_One 14, the foreign agent in the associates the combination of temporary IMSI and IP address used the RP session. MS (2) The RAN_B After moving to the coverage area of ​​the (54), MS (2) and is re-registered in the HA (20), is typically assigned the same IP addresses. However, the re-registration for the first time in the RAN_A It uses the actual IMSI of the MS (2), instead of the temporary IMSI assigned by 52. Therefore, PDSN_One 14 ends that each have the same IP address assigned to two different RP session corresponding to a different IMSI. When receiving a packet from the IP network 18 having the IP address, PDSN_One 14 is unable to unambiguously route the packet to a RAN.

In one embodiment, the PDSN in a mixed network are modified to prevent such ambiguity. Each time the FA is allocated an IP address to IMSI, the FA, regardless of the value of the IMSI, the FA of the table to remove any other entity having the same IP addresses. Sugar in the FA of the PDSN IP address is only allowed one RP session.

And MS (2) is added when moving from a 1x system to an HDR system, MS (2) when moving from an HDR system to a 1x system, special attention should be to avoid routing ambiguity. MS (20) The RAN_C 56 establish a connection through the HDR RAN, such as and, RAN_B Go to the 1x RAN, such as 54, being served by a different PDSN, RAN_B Registering the IP address of the MS (2) to the HA (20) when it is within 54, and then the RAN_C 56, the back, the present problem is especially severe. Recently proposed HDR standards, MS (2) The RAN_C 56 to the MS (2) there is no way to inform the re-registration to another hayeoteum that just arrived from the system using an air interface, or the MS (2) is different to the IP address of the MS (2) system. Because the PREV_PZID in the false source to allow the PDSN MS (2) to determine the re-registered through a different PDSN, when moving from a 1x RAN to the 1x RAN it does not matter. In addition, because the UATI in the UATI Request allows the destination PDSN the MS (2) is to determine whether or not to re-registered through a different PDSN, from the HDR RAN to an HDR RAN to move which is not a problem.

MS (2) a 1x RAN_B 54, from the HDR RAN_C To re-enter the coverage area 10 of (56), MS (2) was previously HDR RAN_C When in the coverage area 10 of (56) transmits a UATI Request containing the UATI used by the MS (2). MS (2) is a re-registration of the MS (2) in the intervening 1x system HDR RAN_C 56, there is no way to tell by the currently proposed protocols. As a result, RAN_C 56 MS (2) used by the previous UATI associated with PDSN₂ Resume network communications using the existing PPP state within 16.

In one embodiment, the MS (2) is reset UATI always MS (2) when moving from a 1x RAN to an HDR RAN. When the reset UATI is sent in the UATI Request, the HDR RAN will assign a new UATI to force the MS (2), and therefore the mobile IP re-registration In general, a mobile IP re-registration will cause the MS (2) who is using the same IP address as previously assigned to the MS (2). Upon completion of the mobile IP re-registration, HA (20) is the HDR RAN, and to the network packets to the appropriate direction MS (2). In another embodiment, MS (2) is achieved the MS (2) is substantially the same simply by PPP reset whenever you move from the 1x RAN to an HDR RAN.

In another embodiment, the HDR standard is changed to the MS (2) initiates a location notification (LocationNotification) message to the HDR RAN. In the existing HDR specification, the location notification message system identifier (SID), network identifier (NID), and MS (2) The piece may include a PZID of the previous system, re-register the IP address of the MS (2). Included in the information, the HDR RAN may contact the PDSN whether the HDR RAN to shift enable the session to the HDR RAN RP. In addition, if the PZID belongs to the 1x RAN associated with a different PDSN, PDSN can reset the PPP session and thus trigger an IP address can be re-registered.

In another embodiment, the MS (2) sends a mobile IP Agent called (AgentSolicitation) message to the FA in the destination PDSN. On the basis of the FA gleaned from the response address, MS (2) is no expansion of the bandwidth necessary to establish a new PPP session, the IP address of the MS (2) re-registered in the HA (20).

Figure 5 is a flow chart showing a process used by the handoff MS (2) between a 1x RAN and in HDR RAN to perform IMSI authentication. In step 502, upon detection of the conversion RAN type, the MS (2) transmits the IMSI of the MS (2) to the destination RAN. If the destination RAN is 1x RAN, IMSI may be sent in the origination message for a "false source". If the destination RAN is HDR RAN, IMSI may be sent in time, the configuration message to be new HDR session negotiations.

If the PDSN connected to the destination RAN does not have an RP session associated with the IMSI of the MS (2), the PDSN will establish a new PPP session with the MS (2). In step 504, the MS (2) will determine whether the new PPP session is established by the PDSN. The PDSN established a new PPP session by the PDSN could mean this does not have an existing PPP state associated with the IMSI of the MS (2). Alternatively, the establishment of a new PPP session by the PDSN to PDSN could mean that you can not send the existing PPP state to the destination RAN RP session from the old RAN. In either case, the PDSN will generally send an agent advertisement message indicating the address of the FA within PDSN to MS (2). If the previous RAN providing service to the MS (2) connected to the same PDSN, the mobile IP is not necessary to re-register the HA (20). HA (20) is to forward packets to the correct PDSN. However, if the previous RAN connected to another PDSN to service the MS (2), MS (2) is to be re-register mobile IP in order to inform new PDSN address the HA (20). Because MS (2) is unable to determine whether the new PPP state by a change of PDSN, in step 506, the mobile MS has re-registered in the IP address of the MS HA (20).

In step 504, if the MS (2) that determines that a new PPP session has been established by the PDSN, in step 508, the MS (2) determines whether a mobile IP re-registration occurred in the previous RAN type. As described above, the protocol to be used in different wireless interfaces are designed to handle the movement of the MS (2) between the different types of the same RAN. Thus, MS (2) when a move from the RAN of the same type, no routing ambiguity. As it is passed between the 1x RAN, the MS (2) transmits the information about the previous RAN such as the PZID to allow the destination RAN determines whether a new PPP session should be established. The MS (2) is movable between the HDR RAN, the destination RAN is a new PPP session is needed by comparing the UATI received from the MS (2) in the UATI Update message and determines whether.

Previous RAN and the destination RAN are connected to a different PDSN, MS (2) Upon re-register a mobile IP address of the MS (2) to the HA (20) of the old system, HA (20) is still the address to the MS (2) and it transmits the encryption of the next packet to the PDSN of the previous RAN. In order to prevent such routing ambiguity, MS (2) When the former performs a Mobile IP re-registration to the RAN type, the MS 506 in step (2) is to register a mobile IP address of the MS (2) Re.

IS-856 standard, and the identification and TIA/EIA/IS-856-1 title "CDMA 2000 High Rate Packet Data Air Interface Specification (cdma 2000 High Rate Packet Data Air Interface Specification)" and, in the following "HRPD standard" means January 2002 issue of the call in a wireless communication system supporting the standard, the access network (AN) is defined as the network equipment providing data connectivity between a packet switched data network (typically the Internet) and the access terminal. The access network is a schematic equivalent to the base station. An access terminal (AT) is defined as a device providing data connectivity to a user. An access terminal may be connected to a computing device such as a laptop personal computer, a personal digital assistant such as a self-may be included (self-contained) data unit. The mobile station and the access terminal is a schematic equivalent.

AT is a radio link protocol: AN and communicate over a wireless link according to (Radio Link Protocol RLP). Location Update Protocol defines location update procedures and messages for mobility management. The location parameter describes the current configuration of the communication path facilitating communication with the AT in the AN. Location parameter &lt;SID, NID, PACKET_ZONE_ID&gt; comprises the triplet (triplet) of the given information, such as. The AN may send a location assignment message to the AT to update the location information. Other, AN may send a location request message to query location information from the AT. AT may be in response to a request from the AN or the location notification message transmitted independently. It includes: (LV Location Value) location notification message position. LV includes the fields illustrated in Table 1. Only a position corresponding to the position notification is in the value of the ANID types of 1x. For example, the LV in HDR does not have a sub-field, it has a number.

<img id="1" file="112005023719168-pct00001.jpg" wi="143" he="37" img-format="jpg" />

LV is passed to the mobile station by the network, the number is used to determine whether the mobile station by the network, whether to establish a PPP session with another PPP. In addition, LV is referred to as Access Network ID (ANID). A11- LV the mobile station to the PANID field mounting (populate) in the registration request report is used by the PCF. CANID is a field provided by the PCF to the PDSN (not shown).

When the AT moves to an area for communication with the AT is facilitated by at least one different AN infrastructure element and the new communication path is not able to reach the serving PDSN, AN sends a location assignment message. In this situation, AN is set to a unique number as a whole to the corresponding LV in the serving PDSN. The AN does not continue to notify the location parameters, and AN is the AT movement, for example does not update the location information every time a new communication path, such as to cause more than a PCF boundary. A wireless session for each mobile station includes the address of the PDSN. Radio session information can be exchanged between the AN through the A13 interface. Session Information Response message is titled "High Rate Packet Data (HRPD) access network interface for interaction potential standard (IOS) (InterOperability Specification for High Rate Packet Data Access Network Interface)" it is, in embodiments TIA/EIA/IS-878 It was. In this manner, searching for the radio session information from the Session Information Response message indicates to the AN whether or not a new serving PDSN is present. Update is made using the IP address of the previous serving PDSN session information included in the response message.

When AN is not able to reach the previous serving PDSN, a new data session (e.g. PPP) it is initiated. Is a flow chart showing the process in the PCF is provided in FIG. As shown, in step 602, the AT enters a target BSC / PCF area. In step 604, the AT transmits the source BSC / PCF, i.e. the identifier of the previous BSC / PCF. In decision diamond 606, the target BSC / PCF, that is the new BSC / PCF is attempting to retrieve a radio session from the source BSC / PCF. If possible, the target BSC / PCF contacts the serving PDSN (610). Otherwise, the target BSC / PCF is not able to retrieve when the wireless session, at step 612, the BSC / PCF establishes a new radio session. Processing continues to step 614 to request the ANID from the AT. If the target BSC / PCF to find the serving PDSN, processing continues to step 610. If not, in step 618 and step 620, the PCF determines a new serving PDSN. Then, in step 622, location information is available to the AT.

Figure 7 illustrates one scenario, the AT has established a PPP session with the serving PDSN. As shown, the PDSN x (704) includes a PPP session unit 702. BSC / PCF (720) is present in the serving area of ​​the support HRPD standard and PDSN x (704). The system 700 further includes PDSN y (714) including portions (716) the PPP session. BSC / PCF (722) supports the HRPD standard and is present in the serving area of ​​the PDSN y (714). PCF (724) supports a system such as 1x and is present in the serving area of ​​the PDSN y (714).

When the AT moves to the location can not reach the serving PDSN y, the AN sends location assignment messages and updates the LV stored in the AT. When the AT moves into the serving area of ​​PCF (720) from the serving area of ​​PCF (722), the PCF (722) sends a location assignment message is LV in the same manner as in ANID_x AT. The mobile node ID (MNID) is identified to IMSI_1, IP address of the PDSN is given as x, y, z, t. When the AT moves into the serving area of ​​PCF (724) from the serving area of ​​PCF (722), the AT will report ANID_x the PCF (724). In response PCF (724) reports a ANID_x the PDSN y (714) as the PANID. PDSN y (714) compares the value with the value of the PANID of the ANID, and transmits a mobile IP agent advertisement, the ANID and the PANID and starts an LCP configuration when it is not matched.

In general, the AT maintains the last LV received from the network in which the data session is established. That is, as in response to a voice call, the AT tunes to a 1x frequency, and, if then tunes back to the HRPD frequency is not re-established in the 1x system, the data session, there is no need to change the LV value.

Figure 8 is a receiver circuit 752, a transmission circuit 756, the control processor 754, and memory with a storage device 758, LV information shows AT (750) stored in the memory storage device (758). Various modules of the AT (750) communicates via the communications bus 760. The LV information stored is a function of the serving PDSN rather than the serving PCF. In this manner, AT (750) receives access network information corresponding to the serving PDSN. AT (750) it does not need to receive access network information for each change of serving PCF.

Figure 9 shows the MS (2) device. As described above, the MS (2) may have a data connection unit (12), such as an external terminal or a personal or laptop computer (PC). In this configuration, the MS (2) may include a local interface 812 to provide necessary call for the data connection signals and digital data. The local interface 812 may be a type in any of a variety of interfaces, such as Ethernet cables, serial, or universal serial bus (USB). Further, the local interface 812 may provide a wireless connection or an infrared or other optical connection such as wireless connection, such as Bluetooth, or IEEE 802.11.

Instead of providing a connection to an external PC (4), MS (2) may provide direct access to the IP network 18. For example, MS (2) may include a web browser application using such protocols as the Wireless Application Protocol. In such combined application, the local interface 812 is a keypad, LCD display, or any suitable touch-display, or a wireless packet data user interfaces such as a pen and an input interface that is used commonly to a portable personal digital assistant device (PDA) It may take the form of a user interface including an input interface to another.

In one embodiment, the local interface 812 may provide application data to a control processor 804. The control processor 804 may be a general purpose processor, a digital signal processor (DSP), programmable logic devices, application specific integrated circuit (ASIC), or any other device capable of performing the functions described herein. The handset user input interface and handset display may include any other input interface appropriate for the keypad, the portable liquid crystal displays are commonly used in the personal digital assistant device (PDA) (LCD) pen input interface, or a wireless packet data user applications.

In addition, the control processor 804 MS (2) is configured IP resource request, PPP sessions mapped, and such as any of a variety of other network protocol processes associated with the air interface, Fig. 1 to be also perform the processing described with 7 . Control processor 804 may be a single processor may include multiple separate processors such as a user interface feature to the local interface 812 and a wireless interface to the microcontroller through the DSP for mapping for mapping protocol.

And MS (2) includes a memory 802 for storing various types of data and information needed during operation of control processor 804. Memory 802 may include a number of devices, such as may be a single device, a flash memory, static or dynamic random access memory (RAM), or erasable or erasure is not possible with the non-volatile memory including read only memory (ROM) can. All memory 802, or some of them may be incorporated in the entire control processor 804 or on a single device, with some of them. Memory 802 may include information such as the executable code, IMSI, the shared secret information used to register a mobile IP address, the address of the HA (20), and the mobile IP address to the control processor 804. Additionally, the memory 802 is configured to provide a temporary copy, and a packet data service in the packet data received from the wireless network and the radio network stores all necessary state variables.

In one embodiment, the data to be transmitted to the wireless network includes a modulator (MOD; 806) encoded in the modulation, and is interleaving (interleave), a diplexer (DIP; 810) and the transmitter before it is transmitted via an antenna 814 ( The amplification and up-conversion (upconvert) at 808); TMTR. Data received from a radio network includes a receiver (RCVR; 816) through the antenna 814 from the gain-controlled and down is converted, control processor demodulator before being processed by a 804; de-interleaving in (DEMOD 818) (deinterleave) , it demodulated, and decoded. Modulator (MOD; 806), a transmitter (TMTR; 808), a receiver (RCVR; 816), and a demodulator (DEMOD; 818) may be, for example, using a wireless interface, such as a plurality of types, and 1x and HDR operable have. If necessary, MS (2) is 1x, HDR, W-CDMA, EDGE, and a number of types, including the number of modulators required for the air interface and compatibility can be a receiver or a demodulator.

Figure 10 is a receiving circuit 902, a control processor 904, transmit circuitry 906, access network information update unit 908, memory storage 912, and the PCF that includes a communication bus 910 (900) the shows. The access network information update unit 908 is configured to implement the method 600 shown in FIG. The access network information update unit 908 receives an instruction to enter the area supported by the AT PCF (900). The AT typically sends a Unicast Terminal Access Identifier (UATI). The AT transmits the address that enables a target BSC / PCF to find a source BSC / PCF, the target is the new BSC / PCF, i.e., BSC / PCF (900), the source is the old BSC / PCF on the movement of the AT. Thereafter, BSC / PCF (900) is attempting to retrieve a radio session from the source BSC / PCF. If the PCF (900) is to retrieve the radio session, PCF (900) will try to reach the end serving PDSN. If possible, contact is made with the final serving PDSN. If that is not possible, a new connection is established with the new PDSN, associated with the new PDSN is provided ANID to the AT.

If BSC / PCF (900) can not retrieve the radio session from the source BSC / PCF, BSC / PCF (900) is to establish a new wireless connection, and contact the LV to the AT. If BSC / PCF (900) is unable to determine the position of the last serving PDSN, BSC / PCF (900) determines a new serving PDSN and establishes a connection.

Those skilled in the art know that information and signals may be represented using any of a variety of different technologies and techniques. For example, that may be referenced throughout the above description, data, instructions, commands, information, signals, bits, symbols, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or their It can be expressed in any combination.

In addition, those skilled in the art the various illustrative logical blocks associated with the embodiments disclosed herein, modules, circuits, and algorithm steps know that may be implemented in a self hardware, computer software, or combinations of both. To clearly illustrates the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Such functionality is implemented as hardware or software depends upon the design constraints imposed on the particular application and the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation choice should not be interpreted as causing a departure from the scope of the invention.

The various illustrative logical blocks described with the embodiments disclosed, modules, and circuits with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device , discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein, or can be performed. A general purpose processor may be a microprocessor, and the other hand the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as, for example, be implemented as a combination of a DSP and a microprocessor, in conjunction with a DSP core one or more microprocessors, or any other such configuration calculator.

In direct hardware steps of a method or algorithm described in conjunction with the embodiments disclosed here, in software executed by a processor, or may be implemented as a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, CD-ROM, or such may be any other form of storage medium known in the art. Storage medium is coupled to the processor, the processor reads the information from the storage device, and to write information to the storage device. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

The foregoing description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Those skilled in the art will be readily apparent to various modifications to these embodiments, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Accordingly, the present invention is not intended to be limited to the embodiments disclosed herein, where is to be accorded the widest scope consistent with the principles and novel features disclosed herein.