CN1918934B - Methods and apparatuses for CDMA2000/GPRS roaming - Google Patents

Abstract

IIF architectures and corresponding call flows are provided for CDMA2000/GPRS roaming scenarios such as GPRS foreign mode with Mobile IPv4, GPRS foreign mode with Simple IPv4 or IPv6, CDMA2000 packet data foreign mode with Mobile IPv4, and CDMA2000 packet data foreign mode with Simple IPv4 or IPv6.

Description

Method and device for CDMA2000/GPRS roaming

Priority claims under 35 U.S.C § 119

This patent application claims priority to Provisional Application No. 60/526,557, filed December 3, 2003, entitled "CDMA/GPRS Packet Data Roaming," which is assigned to the applicant of this application assignee, which is hereby expressly incorporated by reference.

technical field

Embodiments disclosed herein relate generally to wireless communications and, more specifically, to roaming in the context of CDMA2000 and GPRS systems.

Background technique

Wireless users may desire to use their wireless terminals in conjunction with wireless systems other than their home system to access services using their existing subscriptions. Access to these services may be via wireless systems other than their home systems independent of their standard wireless terminals. For example, this can occur when users roam outside the service area of their home system. Therefore, manufacturers and system operators desire to allow users to use their terminals and subscribe to receive services through the system, which may not be the user's home system, as long as the terminal and service system are compatible.

Serving a roaming user can be difficult even when the serving system and the home system employ the same technology. Interworking between these systems typically takes place when the serving system uses a different air interface than that used in the user's home system due to fundamental differences in message protocols, call models, and the like. This interworking can be achieved through Interworking and Interoperability Function (IIF: Interworking and Interoperability Function).

An example of IIF is described in US patent application 2002/094811A1 by Bright et al. entitled "Interworking and Interoperability of GPRS Systems With Systems of Other Technology Families" . US Patent Application 2002/094811A1 provides a GPRS Interworking and Interoperability Function (IIF) between a serving GSM/GPRS wireless system and a second wireless system of a different technology family. The IIF allows mobile stations belonging to a second wireless system to work in the GSM/GPRS system. According to US patent application 2002/094811A1 telecommunication system components are provided which allow interworking and interoperability of serving GSM and/or GPRS systems with certain "in-country wireless" systems. For example, a mobile station that is homed to such a domestic wireless system but is registered with a serving system in single GPRS mode can receive service from that serving system. US patent application 2002/094811A1 mentions the term "domestic wireless (DW: domestic wireless)" to mean compatible with ANSI or equivalent standards for TDMA, CDMA and analog cellular systems commonly used in North America or other similar systems Compatible with non-GSM systems.

Although US patent application 2002/094811A1 recognizes the need for an IIF that allows mobile stations assigned to CDMA wireless systems to operate in GSM/GPRS systems, US patent application 2002/094811A1 does not address the need for mobile IP or IIF for CDMA 2000/GPRS roaming scenarios when simple IP is discussed. US Patent Application 2002/094811A1 fails to provide sufficient information, guidance or guidelines as to how an IIF can be constructed to allow a mobile station belonging to the CDMA 2000 wireless system to operate on GSM/GPRS when the terminal uses Mobile IP or Simple IP system. For example, US Patent Application 2002/094811A1 fails to provide any details about what modules are needed to implement such an IIF, how these modules are interconnected, timed and controlled to achieve the specific operations required to implement such an IIF.

Therefore, there is a need in the art for a generic structure that can be adapted for CDMA 2000/GPRS roaming scenarios such as GPRS foreign mode with mobile IPv4, GPRS foreign mode with simple IPv4 or IPv6 , CDMA 2000 Packet Data Foreign Mode with Mobile IPv4, and CDMA 2000 Packet Data Foreign Mode with Simple IP, Mobile IPv4, or Mobile IPv6. It is expected that by supporting the bearer connection between the GPRS system and the CDMA 2000 packet data system, when the local user of the CDMA 2000 packet data using simple IP, mobile IPv4 or mobile IPv6 roams to the GPRS system, it can communicate between the CDMA 2000 packet data system and the GPRS Communication between systems. Similarly, it is also expected that by supporting the bearer connection between GPRS and CDMA2000 packet data systems, when a GPRS local user roams from the GPRS system to the CDMA 2000 packet data system using simple IP, mobile IPv4 or mobile IPv6, the GPRS system can Communication with CDMA 2000 packet data systems.

Contents of the invention

According to one aspect of the present invention, an interface entity between the CDMA 2000 packet data system and the GPRS system is provided, the interface entity supports the bearer connection between the GPRS and the CDMA 2000 packet data system by providing a packet routing function, so that when When the local user of CDMA 2000 packet data roams to the GPRS system, the communication between the CDMA 2000 packet data system and the GPRS system can be carried out.

According to one aspect of the present invention, a kind of interface entity is provided, when the local user of CDMA 2000 packet data using Mobile IPv4 roams to the visited GPRS system, the interface entity enables the local CDMA 2000 packet data system and the visited including SGSN Communication between GPRS systems is possible.

For example, in an embodiment where a local user of CDMA 2000 packet data roams to a visited system and uses Mobile IPv4, an interface entity may be provided which connects the home system to the visited system so that the local system and the visited system able to communicate. In this case, the home system is a CDMA 2000 packet data system, which may include ANSI-41 home location registers, AAA entities and home agents, and the visited system may be a GPRS system including the SGSN.

According to an aspect of this embodiment, the interface includes a GSM home location register emulation module and an ANSI-41 visitor location register emulation module. The GSM home location register emulation module can be connected to the SGSN through the Gr interface, which allows the user to register through the Gr interface, while the ANSI-41 visiting location register emulation module can be connected to the ANSI-41 home location register through the D interface, which allows the user Register through the D interface. According to an aspect of this embodiment, the interface further includes a foreign agent emulation module and a GGSN emulation module. The foreign agent emulation module can be connected to the home agent through the X1 interface, and the foreign agent emulation module supports bearer connection between the visited system and the home system, so that the foreign agent interface and the AAA interface are provided to the CDMA2000 packet data system through the X1 interface. The GGSN emulation module can be connected to the SGSN through the Gp interface, and the GGSN emulation module can support the bearer connection between the visited system and the local system, so that the GGSN interface is provided to the visited system through the Gp interface. This interface can be used as the endpoint of GTP tunnel and mobile IP tunnel. In this embodiment, the interface provides packet routing functionality between the GGSN interface and the foreign agent interface. According to another aspect of this embodiment, the interface may further include an AAA emulation module, and the AAA emulation module may be connected to the AAA entity through the X3 interface. In this embodiment, the AAA emulation module provides accounting functionality to interact with the local network's AAA for Mobile IP foreign agent challenge authentication and 3GPP2 packet data accounting.

According to one aspect of the present invention, an interface entity is provided that enables the local CDMA 2000 packet data system and the visited GPRS system including the SGSN when a local user of CDMA 2000 packet data using Simple IP roams to a visited GPRS system Communication between GPRS systems is possible.

In an embodiment where a local user of CDMA 2000 packet data roams to a visited system and uses simple IP, an interface entity may be provided which connects the home system to the visited system so that the local system and the visited system able to communicate. In this case, the home system is a CDMA 2000 packet data system, which may include ANSI-41 home location registers, AAA entities and LNS, and the visited system may be a GPRS system including SGSN.

According to an aspect of this embodiment, the interface includes an ANSI-41 Visitor Location Register and a GSM Home Location Register. The ANSI-41 visitor location register can be connected to the ANSI-41 home location register through the D interface, and the ANSI-41 visitor location register allows users to register through the D interface. The GSM home location register can be connected to the SGSN through the Gr interface, and the GSM home location register allows users to register through the Gr interface. According to another aspect of this embodiment, the interface may include a LAC emulation module and a GGSN emulation module. The LAC emulation module can be connected to the LNS through the X2 interface, and the LAC emulation module supports the bearer connection between the visited network and the local network through the X2 interface. The GGSN emulation module can be connected to the SGSN through the Gp interface, and the GGSN emulation module supports the bearer connection between the visited network and the local network through the Gp interface, which is provided by providing the GGSN interface to the visited system and the normal routing interface to the CDMA The 2000 packet data system is thus implemented by providing a packet routing function between the GGSN interface and the local system. In this case, the interface acts as the endpoint of the GTP tunnel and the IPSec tunnel. According to another aspect of this embodiment, the interface may include an AAA emulation module, and the AAA emulation module may be connected to the AAA entity through the X3 interface. The AAA emulation module interacts with the local network's AAA for L2TP authentication and 3GPP2 packet data accounting through the X3 interface to provide accounting functions.

According to another aspect of the present invention, an interface entity between the GPRS system and the CDMA 2000 packet data system is provided, the interface entity supports the carrier connection between the GPRS system and the CDMA 2000 packet data system by providing packet routing functions, so that When a GPRS local user uses one of mobile IPv4 and simple IP to roam from the GPRS system to the CDMA 2000 packet data system, communication between the GPRS system and the CDMA 2000 packet data system can be performed.

According to another aspect of the present invention, a kind of interface entity is provided, when the local user of GPRS using Mobile IPv4 roams to the visited CDMA 2000 packet data system, the interface entity makes the local GPRS system and the visited CDMA 2000 packet data Communication between systems is possible, where the local GPRS system includes GSM Home Location Register, GGSN and AAA entity, and the visited CDMA 2000 packet data system includes ANSI-41 Visitor Location Register, AAA entity and packet data service node/foreign agent.

In the embodiment where the GPRS local user roams to the visited system and uses Mobile IPv4, an interface entity can be provided, which connects the local system to the visited system, so that the local system and the visited system can communicate . In this case, the home system is a GPRS system including the GSM Home Location Register, GGSN and AAA entities, while the visited system may consist of ANSI-41 Visitor Location Register, AAA entities and Packet Data Serving Node/Foreign Agent CDMA 2000 packet data system.

According to an aspect of this embodiment, the interface includes a home agent emulation module and an SGSN emulation module. The home agent emulation module can be connected to the packet data service node/foreign agent through the X1 interface, and the home agent emulation module provides a home agent interface to the visited system. The SGSN emulation module can be connected to the GGSN through the Gp interface, and the SGSN emulation module provides the SGSN interface to the local system to support between the visited network and the local network by providing the packet routing function between the SGSN interface and the local proxy interface carrier connection. Here, this interface serves as the endpoint of the GTP tunnel and the Mobile IP tunnel. According to another aspect of this embodiment, the interface may further include an ANSI-41 home location register emulation module and a GSM visitor location register emulation module. The ANSI-41 home location register emulation module can be connected to the ANSI-41 visitor location register through a D interface, while the GSM visitor location register emulation module can be connected to the GSM home location register through a D interface to allow registration by the user. According to another aspect of this embodiment, the interface may further include an AAA emulation module, which may be connected to the AAA entity through the Gi interface and may be connected to the AAA entity through the X3 interface. The AAA emulation module can interact with the AAA of the visited network for mobile IP authentication and 3GPP2 packet data charging through the X3 interface, and can interact with the AAA of the local network for 3GPP packet data charging through the Gi interface.

According to one aspect of the present invention, a kind of interface entity is provided, when the local user of GPRS using simple IP roams to the visited CDMA 2000 packet data system, the interface entity makes the local GPRS system and the visited CDMA 2000 packet data system Among them, the local GPRS system includes GSM home location register, GGSN and AAA entity, and the visited CDMA 2000 packet data system includes ANSI-41 visitor location register, AAA entity and packet data service node/LAC entity.

In the embodiment where the GPRS local user roams to the visited system and uses simple IP, an interface entity can be provided, which connects the local system to the visited system, so that the local system and the visited system can communicate communication. In this case, the home system is a GPRS system including the GSM Home Location Register, GGSN and AAA entities, while the visited system may consist of ANSI-41 Visitor Location Register, AAA entities and Packet Data Serving Node/LAC entities CDMA 2000 packet data system. According to an aspect of the invention, the interface supports bearer connectivity between the visited network and the home network by providing packet routing functionality. For example, the interface may include an SGSN emulation module and an LNS emulation module. The SGSN emulation module can be connected to the GGSN through the Gp interface, and the SGSN emulation module provides the SGSN interface to the local system, and the LNS emulation module can be connected to the packet data service node/LAC entity through the X2 interface, and the LNS emulation module provides It provides an L2TP Network Server (LNS: L2TP Network Server) interface to the accessed system. As such, the interface provides packet routing functionality between the SGSN emulation module and the LNS emulation module. Here, the interface serves as the endpoint of the GTP tunnel and the mobile L2TP tunnel.

According to another aspect of this embodiment, the interface includes an ANSI-41 home location register emulation module and a GSM visitor location register emulation module. The ANSI-41 home location register emulation module can be connected to the ANSI-41 visitor location register through a D interface, while the GSM visitor location register emulation module can be connected to the GSM home location register through another D interface. This allows users to register. According to another aspect of this embodiment, the interface may further include an AAA emulation module, the AAA emulation module may be connected to the AAA entity through the Y3 interface, and the AAA emulation module may be connected to the AAA entity through the X3 interface. The AAA emulation module can interact with the AAA entity of the visited network through the X3 interface to perform L2TP authentication and 3GPP2 packet data accounting, and can interact with the AAA entity of the local network through the Gi interface to perform 3GPP packet data accounting.

Brief description of the drawings

1 is a block diagram of a system including a local system, a visited system, and an interface entity that enables communication between the local system and the visited system;

Fig. 2 A is the block diagram that has the GPRS foreign mode of mobile IPv4;

Figure 2B is a call flow diagram illustrating Mobile IPv4 operation in GPRS foreign mode;

Figure 3A is a block diagram of a GPRS foreign mode with simple IP;

Figure 3B is a call flow diagram illustrating simple IP operation in GPRS foreign mode;

Figure 4A is a block diagram of a CDMA 2000 packet data foreign mode with Mobile IPv4;

Figure 4B is a call flow diagram illustrating Mobile IPv4 operation in CDMA 2000 packet data foreign mode;

Figure 5A is a block diagram of a CDMA 2000 packet data field mode with simple IP; and

Figure 5B is a call flow diagram illustrating simple IP operation in CDMA 2000 packet data foreign mode.

Detailed ways

The word "exemplary" may be used herein to mean "serving as an example, instance, or illustration." Embodiments described herein as "exemplary" are not necessarily to be construed as preferred or advantageous over other embodiments.

1 is a block diagram of a system comprising a home system 10 such as a CDMA 2000 packet data system or a GPRS system, a visited system 20 such as a GPRS system or a CDMA 2000 interface entity 30 or "IIF" A packet data system, an interface entity 30 or "IIF" connects the home system 10 to the visited system 20 and enables communication between the home system 10 and the visited system 20 .

Subsequent sections describe structures that can be applied to CDMA 2000/GPRS roaming scenarios such as GPRS Foreign Mode with Mobile IPv4, GPRS Foreign Mode with Simple IPv4 or IPv6, CDMA 2000 with Mobile IPv4 Packet data foreign mode, and CDMA 2000 packet data foreign mode with simple IPv4 or IPv6.

GPRS Foreign Mode with Mobile IPv4

Figure 2A is an exemplary block diagram of GPRS foreign mode with Mobile IPv4, describing the functions and control interfaces provided by the IIF in this embodiment. This roaming scenario occurs when a CDMA 2000 packet data native user is running Mobile IPv4 [IS-835-C] in GPRS foreign mode. In this embodiment, the home system 10 may be a CDMA 2000 packet data system, where a CDMA 2000 packet data home user roams to a GPRS system and uses Mobile IPv4. Home system 10 includes ANSI-41 Home Location Register (ANSI-41 HLR) 131 , AAA entity 116 , and Home Agent (HA) 135 . The visited system 20 may be a GPRS system comprising the SGSN 137.

Interface 30 or "IIF" includes ANSI-41 Visitor Location Register (ANSI-41 VLR) 111, GSM Home Location Register (GSM HLR) 124, GGSN 126, AAA entity 140, and Foreign Agent (FA) 118, wherein, via the D interface 113 connects the ANSI-41 visitor location register 111 to the ANSI-41 home location register 131, connects the GSM home location register 124 to the SGSN 137 via the Gr interface 123, connects the GGSN 126 to the SGSN 137 via the Gp interface 127 and connects the GGSN 126 is connected to the Internet, AAA entity 140 is connected to AAA entity 116 through X3 interface 117, and foreign agent 118 is connected to home agent 135 through X1 interface 115. The IIF provides GSM HLR and ANSI-41 VLR emulations to allow users to register. This interworking may be provided through interfaces referenced "Gr" and "D". IIF provides GGSN and FA emulation to support bearer connection between visited network and home network through IIF. This interworking may be provided through interfaces referenced "Gn" and "X1". The IIF provides AAA emulation to interact with the home network's AAA for mobile IP foreign agent challenge authentication and 3GPP2 packet data accounting. This interworking may be provided through an interface referenced "X3".

If the bearer connection between the GPRS system and the CDMA 2000 packet data system is not required, then the reverse tunnel on the X1 interface is not required. More precisely, MS-terminated traffic goes through the X1 and Gp interfaces. In cases where reverse tunneling is not required, the IIF routes MS-originated traffic received on the Gp interface directly to the Internet via the Gi interface.

Therefore, for users belonging to the CDMA mobile IP system but roaming to the GSM system, the IIF can provide the GGSN interface to GSM and the FA and AAA interfaces to the CDMA system. The IIF can be used as the endpoint of the GTP tunnel and the mobile IP tunnel, and it has a packet routing function between the GGSN and the FA. The IIF can also provide charging functionality so that operators can charge based on configurable metrics such as packet count, bandwidth, time of day, and so on.

Figure 2B is an exemplary call flow diagram illustrating Mobile IPv4 operation in GPRS foreign mode. Figure 2B depicts an example call flow for a roaming scenario in which a CDMA2000 packet data native user is running Mobile IPv4 [IS-835-C] in GPRS foreign mode. In this example, the MS has a shared secret with the home CDMA 2000 system for Mobile IP authentication. The MS may request the local CDMA2000 system to assign an HA and/or IP address. Reverse tunneling can be enabled so that all data traffic (from or to the MS) passes through the IIF and the native CDMA 2000 system. The IIF generates 3GPP2 packet data accounting records and sends them to the local CDMA 2000 system via RADIUS.

MS utilizes SGSN to complete GPRS attachment. Authentication related to GPRS attach may be SIM based authentication requiring a Ki key. The IIF acts as the GSM HLR configured with the Ki key. In any case, the IIF may not be required to communicate with the HLR in the local CDMA2000 system for this authentication. (Step 1) MS sends "Activate PDP Context Request" to SGSN. The message includes the access point name (APN: Access Point Name). The APN has the format <network ID>.<MNC>.<MCC>.gprs. The Network ID (eg CDMA2000carrier.com) indicates which external network the MS wants to establish a logical connection with. The Requested PDP Address may be omitted in this message. The MS has a static mobile IP local address or obtains a new mobile IP local address. (Step 2) SGSN selects GGSN based on APN. The SGSN uses the APN as a lookup name to query a DNS server (not shown in the figure) and obtain a list of available GGSNs that can be used to support the requested APN. The APN's Network ID indicates the CDMA 2000 operator, so the DNS server returns the IIF's IP address. (Step 3) SGSN sends "Activate PDP Context Request" to the selected IIF to establish PDP context for MS. The message includes the APN, but the requested PDP address may be omitted. (Step 4) The IIF acts as a GGSN and sends a "Create PDP Context Ack" to the SGSN, which then sends an "Activate PDP Context Accept" to the MS. The PDP Address in both messages may be set to 0.0.0.0 to indicate that the PDP address will be assigned after a successful Mobile IP registration. (Step 5) Since omitting the requested PDP address in the "Activate PDP Context Request" may indicate that the MS desires to use Mobile IP, the IIF acts as FA and sends one or more Mobile IP Proxy Advertisements to the MS. Proxy Advertisements may be sent over established PDP contexts. Proxy announcements include FA care-of address (FA COA: FA Care-of Address) and FA challenge (FAC: FA Challenge). (step 6)

MS sends "Mobile IP Registration Request" to IIF through PDP context. Subsequent information may be included in this registration request: The MS's NAI [RFC 2794] has the format <username>@<domain name>, where the domain name identifies the MS's native CDMA 2000 system. The MS-HA Authentication Code [RFC 2002] can be computed based on the contents of the Registration Request and a secret shared between the MS and the HA. The MS-AAA authentication code [RFC 3012] may be computed based on the FAC and a secret shared between the MS and the local AAA server. If the MS uses a permanent HA, it can set the HA Address field to a known value; or if the MS wants to assign a new HA by the local network, it can set the HA Address field to 0.0.0.0. If the MS uses a permanent address, the Local Address field can be set to a known value; or if the MS wants a new address assigned by the HA, the Local Address field can be set to 0.0.0.0. The T-bit can be set to 1 to enable reverse tunneling from the IIF to the HA of the MS. (Step 7) The IIF acts as a RADIUS client and sends a "RAIDUS Access Request" to the local AAA server. The "RAIDUS Access Request" transmits the MS's NAI, FAC authentication code, FAC, HA address, etc. [IS-835]. (Step 8) If the authentication is successful, the local AAA server replies with "RADIUS Access Accept" including the HA address of the MS. (Step 9) The IIF acts as FA and forwards the "Mobile IP Registration Request" to the HA address contained in the "RADIUS Access Accept". (Step 10) HA checks the MS-HA authentication code in the "Mobile IP Registration Request". As in the case of a dynamically allocated HA, if the HA does not have the shared secret, it communicates with the local AAA server to obtain the shared secret. The HA responds to the "Mobile IP Registration Request" with a "Mobile IP Registration Response" containing the registration result (eg success or error code). If the MS expects a new local address, the new address may be returned in the Registration Reply; otherwise, the MS's permanent address may be returned. (Step 11) The IIF acts as FA and forwards the "Mobile IP Registration Reply" to the MS through the appropriate PDP context. The IIF FA function records the assigned MS IP address and shares this address with the IIF GGSN function. (step 12)

The IIF acts as a GGSN and updates its PDP context by setting the PDP address to the MS's home address (as indicated in the Registration Reply and shared by the FA function). The PDP address (and therefore the local address of the MS) can be associated with the GTP tunnel, and the GTP tunnel can be identified by the Tunnel Endpoint ID (TEID: Tunnel Endpoint ID). (Step 13) The IIF acts as the GGSN and triggers the GGSN-initiated PDP context modification procedure to update the PDP address in the SGSN and MS [3GPP TS 29.061]. The IIF sends the "Update PDP Context Request" to the SGSN, which forwards it to the MS. (Step 14) The MS responds to the SGSN with an "Update PDP Context Acknowledgment", and the SGSN forwards it to the IIF. (Step 15) The IIF acts as a RADIUS client and sends a "RADIUS Accounting-Request (start)" to the local AAA server [IS-835]. Charging records are delivered using 3GPP2 vendor-defined attributes, but some airlink record attributes (eg: service option, multicast option, etc.) are not available. (Step 16) The local AAA server responds with "RADIUS Accounting Reply (Start)". (Step 17) If reverse tunneling from IIF to HA is enabled, bearer traffic goes through the IIF in both directions. To route MS-originated packets, the IIF routes packets received from the MS's GTP tunnel (identified by TEID) to the MS's HA through the Mobile IP reverse tunnel. To route MS-terminated packets, the IIF routes packets received from the HA-to-FA tunnel to the MS's GTP tunnel. IPsec can be used to protect the Mobile IP tunnel between HA and IIF and the GTP tunnel between IIF and SGSN. (step 18)

GPRS field mode with simple IP

3A is an exemplary block diagram of GPRS foreign mode with simple IP showing a roaming scenario for a CDMA2000 packet data native user running IPv4 or IPv6 in GPRS foreign mode. Figure 3A also describes the functions and control interfaces provided by the interface or IIF in this case. In this embodiment, the home system 10 may be a CDMA 2000 packet data system where a CDMA 2000 packet data home user roams to a GPRS system and uses simple IPv4. Home system 10 includes ANSI-41 Home Location Register (ANSI-41 HLR) 131, AAA entity 116, and LNS 139. The visited system 20 may be a GPRS system including the SGSN 137.

Interface 30 or "IIF" includes ANSI-41 Visitor Location Register (ANSI-41 VLR) 111, GSM Home Location Register (GSM HLR) 124, GGSN 126, AAA entity 140 and LAC entity 109, wherein ANSI -41 Visiting location register 111 is connected to ANSI-41 home location register 131, GSM home location register 124 is connected to SGSN 137 through Gr interface 123, GGSN 126 is connected to SGSN 137 through Gp interface 127 and GGSN 126 is connected through Gi interface To the Internet, the AAA entity 140 is connected to the AAA entity 116 through the X3 interface 117, and the LAC entity 109 is connected to the LNS 139 through the X2 interface 119. The IIF provides GSM HLR and ANSI-41 VLR emulations to allow users to register. This interworking may be provided through interfaces referenced "Gr" and "D". IIF provides GGSN and LAC emulation to support bearer connection between visited network and home network through IIF. This interworking may be provided through interfaces referenced "Gn" and "X2". The IIF provides AAA emulation to interact with the local network's AAA for L2TP authentication and 3GPP2 packet data accounting. This interworking may be provided through an interface referenced "X3".

If the bearer connection between the CDMA 2000 packet data system and the GPRS system is not required, then the X2 interface is not required. The IIF still supports the Gp interface to the SGSN and provides Internet access through the Gi interface (not shown in the figure).

Therefore, for users belonging to the CDMA simple IP system but roaming to the GSM system, the IIF can provide the GGSN interface to GSM and the normal routing interface to the CDMA system. The IIF can serve as the endpoint of the GTP tunnel and the IPsec tunnel, and it has a packet routing function between the GGSN and the CDMA system. The IIF can also provide charging functionality so that operators can charge based on configurable metrics such as packet count, bandwidth, time of day, and so on.

3B is an exemplary call flow diagram illustrating Simple IP operation in GPRS foreign mode, and explains a roaming scenario for a CDMA2000 packet data native user operating Simple IP in GPRS foreign mode. In this example, the MS has a shared secret (ie CHAP) for simple IP authentication with the native CDMA2000 system. The MS establishes a PPP session to the local CDMA 2000 system through L2TP. During PPP establishment, the local CDMA 2000 system dynamically assigns an IP address to the MS. All MS data services (originating from MS and terminating at MS) go through IIF and local CDMA 2000 system. The IIF generates 3GPP2 packet data accounting records and sends them to the local CDMA 2000 system via RADIUS.

MS utilizes SGSN to complete GPRS attachment. Authentication related to GPRS attach may be SIM based authentication requiring a Ki key. The IIF acts as a GSMHLR or GSM VLR configured with a Ki key. In any case, the IIF may not need to communicate with the HLR in the local CDMA2000 system to perform the authentication. (Step 1) MS sends "Activate PDP Context Request" to SGSN. The message includes the access point name (APN: AccessPoint Name). The APN has the format <network ID>.<MNC>.<MCC>.gprs. The network ID (eg CDMA 2000 carrier.com) indicates which external network the MS wants to establish a logical connection with. The requested PDP address can be omitted in this message so that instead of the IIF (as GGSN) subsequently assigning an IP address to the MS, the LNS assigns the address. (Step 2) SGSN selects GGSN based on APN. The SGSN queries a DNS server (not shown in the figure) and obtains a list of available GGSNs that can be used to support the requested APN. In this case, the APN's Network ID indicates the CDMA2000 operator, so the DNS server returns the IIF's IP address. (step 3)

SGSN sends "activate PDP context request" to the selected IIF to establish PDP context for MS. The message includes the APN, but the requested PDP address may be omitted. (Step 4) IIF acts as GGSN and sends "Create PDP Context Ack" to SGSN, which then sends "Activate PDP Context Accept" to MS. The PDP address in both messages may be set to 0.0.0.0 to indicate that the PDP address will be reset later. (step 5)

After the PDP context can be established, MS and IIF conduct PPP LCP negotiation. The IIFLAC function establishes an L2TP tunnel with the LNS. The IIF determines an LNS based on the requested APN. The IIF is configured with the LNS information corresponding to the APN (for example: the IP address of the LNS). After the L2TP tunnel is established, the IIF function forwards the LCP information between the LNS and the MS. During LCP negotiation, LNS and MS will negotiate PAP or CHAP as the protocol for PPP authentication. (Step 6) Perform PPP authentication (PAP or CHAP). The certificate of the MS is authenticated through the local AAA in the CDMA 2000 system. The RADIUS interaction between the LNS and the local AAA is not shown in the figure. (Step 7) LNS and MS conduct PPP IPCP negotiation. The IIF LAC function resumes IPCP messages between the L2TP tunnel and the PDP context. During negotiation, the LNS assigns an IP address to the MS. The IIF monitors this address and uses it as the MS's PDP address. (step 8)

The IIF also needs to notify the updated PDP address for the SGSN and MS. Recall that the PDP address can be initially set to 0.0.0.0. Therefore, the IIF sends an "Update PDP Context Request" to the SGSN, which forwards it to the MS. (Step 9) The MS responds to the SGSN with "Update PDP Context Acknowledgment", and the SGSN forwards it to the IIF. (step 10)

The IIF acts as a RADIUS client and sends a "RADIUS Accounting-Request (start)" to the local AAA server [IS-835]. Charging records are delivered using 3GPP2 vendor-defined attributes, but some airlink record attributes (eg: service option, multicast option, etc.) are not available. (Step 11) The local AAA server responds with "RADIUS Accounting Reply (Start)". (Step 12) Bearer traffic goes through the IIF in both directions. To route MS-originated packets, the IIF routes packets received from the MS's GTP tunnel (identified by the TEID) to the MS's L2TP tunnel/session. To route MS-terminated packets, the IIF routes packets received from the MS's L2TP tunnel/session to the MS's GTP tunnel. IPsec can be used to protect the L2TP tunnel/session between LNS and IIF and the GTP tunnel between IIF and SGSN. (step 13)

CDMA 2000 Packet Data Foreign Mode with Mobile IPv4

4A is an exemplary block diagram of a CDMA 2000 packet data foreign mode with Mobile IPv4. This clause describes roaming scenarios for GPRS native users operating Mobile IPv4 [IS-835-C] in CDMA 2000 packet data foreign mode. Figure 4A also describes the functions and control interfaces provided by the IIF in this case. In this embodiment, the local system 10 may be a GPRS system. GPRS native users roam to CDMA 2000 packet data system and use simple IP. Home system 10 includes GSM home location register 124 , GGSN 126 , and AAA entity 128 . The visited system 20 may be a CDMA 2000 packet data system comprising an ANSI-41 Visitor Location Register (ANSI-41 VLR) 111, an AAA entity 116, and a Packet Data Serving Node/Foreign Agent (PDSN/FA) 118.

Interface 30 or "IIF" includes ANSI-41 Home Location Register (ANSI-41 HLR) 131, GSM Visitor Location Register (GSM VLR) 133, SGSN 137, AAA entity 140, and Home Agent 135, wherein ANSI -41 home location register 131 connected to ANSI-41 visitor location register 111, GSM visitor location register 133 connected to GSM home location register 124 via D interface 121, SGSN 137 connected to GGSN 126 via Gp interface 127, via X4 interface 129 AAA entity 140 is connected to AAA entity 128 and is connected to AAA entity 116 through X3 interface 117 and home agent 135 is connected to packet data serving node/foreign agent 118 through X1 interface 115 . IIF provides GSM VLR and ANSI-41 HLR emulation to allow users to register. This interworking may be provided through an interface referenced "D". IIF provides HA and SGSN emulation to support bearer connection between visited network and local network through IIF. This interworking may be provided through interfaces referenced "X1" and "Gn". The IIF provides AAA emulation to interact with the visited network's AAA for mobile IP authentication and 3GPP2 packet data accounting. The IIF can also interact with the local network's AAA for 3GPP packet data charging. This interworking may be provided through interfaces referenced "X3" and "X4". The IIF/AAA requirements for CDMA 2000 Packet Data Foreign Mode with Mobile IP are described in more detail below.

If no bearer connection between the visited CDMA2000 packet data system and the local GPRS system is required, then the Gp interface is not required. In this case, MS-originated data traffic can be routed directly to the Internet via the PDSN/FA in the visited system, or via the IIF/HA if reverse tunneling is enabled to the Internet. The data traffic terminated at the MS is routed to the PDSN/FA through the IIF/HA. IIF needs interfaces X3 and X4 to interwork AAA messages between CDMA 2000 AAA server and GPRS AAA server.

Therefore, for users belonging to the GSM system but roaming to the CDMA mobile IP system, the IIF can provide the HA interface to the CDMA system and the SGSN interface to the GSM system. A subset of SGSN functionality including APN resolution is required. The IIF can serve as the endpoint of a mobile IP tunnel and a GTP tunnel, which has a packet routing function between the HA and SGSN functions.

4B is an exemplary call flow diagram illustrating Mobile IPv4 operation in CDMA 2000 packet data foreign mode. This call flow example shows a roaming scenario for a GPRS native user running Mobile IPv4 [IS-835-C] in CDMA 2000 packet data foreign mode. In this example, the home GPRS system does not support HA, so the MS and IIF have a shared secret for Mobile IP authentication. The local GPRS system dynamically assigns IP addresses to MSs. All MS data services (originating from MS and terminating at MS) go through IIF and local GPRS system. The IIF receives 3GPP2 charging records from the visited CDMA 2000 system, maps these records to 3GPP charging records, and forwards these records to the local GPRS system through RADIUS.

MS sends SO 33 and establishes PPP session with PDSN/FA. (Step 1) Since ignoring the IP address configuration option during PPP IPCP negotiation indicates that the MS desires to use Mobile IP, the PDSN/FA sends one or more Mobile IP Proxy Advertisements to the MS. The proxy announcement includes FA care-of address (FA COA: FA Care-of Address) and FA challenge (FAC: FA Challenge). (step 2)

MS sends "Mobile IP Registration Request" to PDSN/FA. Subsequent information may be included in this registration request: The MS's NAI [RFC 2794] has the format <username>@<domain name>, where the domain name identifies the MS's local GPRS system. The MS-HA Authentication Code [RFC2002] can be computed based on the content of the Registration Request and a secret shared between the MS and the HA. The MS-AAA authentication code [RFC 3012] can be computed based on the FAC and a secret shared between the MS and the local AAA server. If the MS uses a permanent HA, it can set the HA Address field to a known value; or if the MS wants to assign a new HA by the local network, it can set the HA Address field to 0.0.0.0. The HA field can be set to 0.0.0.0 to request a new address assigned by the HA. The T-bit may be set to 1 to request the PDSN/FA to establish a reverse tunnel to the MS's HA. (step 3)

The PDSN/FA generates a "RADIUS Access Request", which conveys the MS's NAI, FAC authentication code, FAC, HA address, etc. [IS-835]. Since the domain name of the MS's NAI indicates the GPRS system, the PDSN/FA sends the "RADIUS Access Request" to the IIF through the AAA in the CDMA 2000 system. The IIF may modify this message according to [3GPP TS 29.061]. (Step 4) If the authentication is successful, the local AAA server replies with "RADIUS Access Accept". The message is routed back to the PDSN through the IIF and the visited AAA. The IIF may modify this message according to [P.S0001-A V3.0]. (Step 5) The PDSN/FA forwards the "Mobile IP Registration Request" to the HA function in the IIF. The IIF checks the MS-HA authentication code in the "Mobile IP Registration Request". (step 6)

If the authentication is successful, the IIF SGSN function establishes a GTP tunnel with the GGSN in the local GPRS system and can request an IP address from the GGSN. The IIF SGSN function gets an APN which has the format: <Network ID>.mnc<MNC>.mcc<MCC>.gprs[TS 23.003]. <Network ID> is part of the MS's NAI scope, which indicates which GGSN the MS wants to access to obtain the requested service. Get <MNC> and <MCC> from MS's IMSI. The NAI and IMSI of the MS can be obtained from the "RADIUS Access Request" in step 4. The SGSN function uses the obtained APN as a lookup name to query a GPRS DNS server (not shown in the figure) and obtain a list of available GGSNs therefrom that can be used to support the requested service. The IIF SGSN function sends a "Create PDP Context Request" to the selected GGSN. Set the Requested PDP Address in this message to 0.0.0.0 to request a new IP address. (Step 7) The GGSN responds with a "Create PDP Context Answer" including the new IP address assigned to the MS. (Step 8) IIF acts as HA and sends "Mobile IP Registration Reply" to MS through PDSN/FA. The local address field in the "Mobile IP Registration Reply" can be set to the IP address assigned by the GGSN. (Step 9) PDSN sends "RADIUS accounting request (start)" including 3GPP2 packet data accounting information [P.S0001-A V3.0]. Since the domain name of the MS's NAI indicates the GPRS system, the "RADIUS Accounting Request (start)" is routed to the local AAA in the GPRS system through the visited AAA and IIF. The IIF may modify this message according to [3GPP TS 29.061]. (Step 10) The IIF acts as a RADIUS server and replies with "RADIUS Accounting Reply (Start)". (step 11)

Bearer traffic passes through the IIF in both directions. To route MS-originated packets, the IIF routes packets received from the Mobile IP reverse tunnel to the MS's GTP tunnel (identified by TEID). To route MS-terminated packets, the IIF routes packets received from the GTP tunnel to the HA-to-FA tunnel. IPsec can be used to protect the Mobile IP tunnel between PDSN/FA and IIF and the GTP tunnel between IIF and GGSN. (step 12)

IIF/AAA Requirements for CDMA 2000 Packet Data Field Mode with Mobile IP

The IIF requirements for processing "RADIUS Access Requests" received from visited CDMA 2000 packet data systems are now described.

The IIF proxies all IETF RADIUS attributes without modification, except the calling station ID attribute, called station ID attribute, and framed protocol attribute. The processing of the above three attributes is described below. If the Calling Station ID attribute in the received "RADIUS Access Request" contains an IMSI, then the IIF copies the IMSI into the 3GPP-IMSI attribute [3GPP TS 29.061] and includes it in the " RADIUS Access Request". The IIF does not include the calling station ID attribute in the "RADIUS Access Request" sent to the local AAA in the GPRS system. If the Calling Station ID attribute in the received "RADIUS Access Request" contains MIN or IRM, then the IIF maps it to the IMSI used by the MS in the local GPRS system and includes it in the "RADIUS Access Request" sent to the local GPRS system. Access Request" in the 3GPP-IMSI attribute. The IIF does not include the calling station ID attribute in the "RADIUS Access Request" sent to the local AAA in the GPRS system.

The IIF includes the called station ID attribute in the "RADIUS Access Request" sent to the MS's home GPRS system. Set the Value field of the called station ID attribute to APN (see section 8.3.4). If the Frame Protocol attribute is included in the received "RADIUS Access-Request", the IIF replaces the value with 7 [3GPP TS 29.061]. The IIF removes all 3GPP2 VSAs from received RADIUS Access-Requests. Apart from the 3GPP-IMSI attribute, the IIF does not need to include any 3GPP2 VSA in the sent "RADIUS Access Request" to the MS's home GPRS system.

The IIF requirements for handling "RADIUS Access Accept" received from the MS's home GPRS system are now described.

The IIF proxies all IETF RADIUS attributes without modification. The IIF removes all 3GPP VSAs from the received "RADIUS Access-Accept" before sending the "RADIUS Access-Accept" to the visited CDMA 2000 packet data system.

If the policy of the home GPRS system requires the data traffic of the roaming MS to pass through the home GPRS system via the IIF, and the HA-address VSA was included in the corresponding "RADIUS Access Request" previously received from the visited CDMA2000 packet data system, then the IIF shall The reverse tunnel specification VSA is included in the sent "RADIUS Access Accept" to the visited CDMA 2000 packet data system. Setting the Value field of this VSA to 1 indicates that a reverse tunnel is required.

The IIF requirements for handling "RADIUS Accounting Request Start" and "Accounting Request Period (INTERIM)" are the same as for handling "RADIUS Access Request".

The IIF requirements for processing a "RADIUS Accounting-Request-Stop" are the same as for processing a "RADIUS Access-Request" with the following additional requirements: If a session-continue VSA is included in a received "RADIUS Accounting-Request-Stop" Set to "false" and the IIF inserts a 3GPP session stop indication if the IIF has not previously received an "Accounting Request (Start)" from another PDSN with the same IP address (for the case of inter-PDSN handover with Mobile IP) symbol VSA to indicate that the PDP session has been terminated.

CDMA 2000 group data field mode with simple IP

FIG. 5A is an exemplary block diagram of a CDMA 2000 packet data foreign mode with simple IP. This clause describes roaming scenarios for GPRS native users running IPv4 or IPv6 in CDMA 2000 packet data foreign mode. Figure 5A also describes the functionality and control interface provided by interface 30 or "IIF" in this case. In this embodiment, the home system 10 may be a GPRS system, where a GPRS home user roams to a CDMA 2000 packet data system and uses Mobile IPv4. Home system 10 includes GSM home location register 124, GGSN 126, and AAA entity 128. The visited system 20 may be a CDMA2000 packet data system including an ANSI-41 Visitor Location Register (ANSI-41 VLR) 111, an AAA entity 116, and a home system 109.

Interface 30 or "IIF" includes ANSI-41 Home Location Register (ANSI-41 HLR) 131, GSM Visitor Location Register (GSM VLR) 133, SGSN 137, AAA entity 140 and LCS entity 139, wherein ANSI -41 home location register 131 connected to ANSI-41 visitor location register 111, GSM visitor location register 133 connected to GSM home location register 124 via D interface 121, SGSN 137 connected to GGSN 126 via Gp interface 127, via X4 interface 129 AAA entity 140 is connected to AAA entity 128 and to AAA entity 116 through X3 interface 117 and LCS entity 139 is connected to packet data serving node/LAC entity 109 through X2 interface 119 . IIF provides GSM VLR and ANSI-41 HLR emulation to allow users to register. This interworking may be provided through an interface referenced "D". IIF provides LNS and SGSN emulation to support bearer connection between visited network and home network through IIF. This interworking may be provided through interfaces referenced "X2" and "Gn". The IIF provides AAA emulation to interact with the visited network's AAA for L2TP authentication and 3GPP2 packet data accounting. The IIF can also interact with the local network's AAA for 3GPP packet data charging. This interworking may be provided through interfaces referenced "X3" and "X4". The IIF/AAA requirements for CDMA 2000 Packet Data Foreign Mode with Simple IP are described in more detail below.

If no bearer connection between the visited CDMA 2000 packet data system and the local GPRS system is required, then the X2 and Gp interfaces are not required. In this case, MS-originated and MS-terminated data traffic can be routed to/from the Internet through the PDSN in the visited system. IIF needs interfaces X3 and X4 to interwork AAA messages between CDMA 2000 AAA server and GPRS AAA server.

Therefore, for users belonging to the GSM system but roaming to the CDMA simple IP system, the IIF can provide the L2TP Network Server (LNS: L2TP Network Server) interface to the CDMA system and the SGSN interface to the GSM system. A subset of SGSN functionality including APN resolution is required. The IIF can serve as the endpoint of a mobile L2TP tunnel and a GTP tunnel, which has a packet routing function between the LNS function and the SGSN function.

Figure 5B is an exemplary call flow diagram illustrating simple IP operation in CDMA 2000 packet data foreign mode. This call flow example illustrates a roaming scenario for a GPRS native user running Simple IP in CDMA 2000 packet data foreign mode. In this example, the MS has a shared secret for CHAP authentication with the local AAA in the GPRS system. The local GPRS system dynamically assigns IP addresses to MSs. All MS data services (originating from MS and terminating at MS) go through IIF and local GPRS system. The IIF receives 3GPP2 charging records from the visited CDMA 2000 system, maps these records to 3GPP charging records, and forwards these records to the local GPRS system through RADIUS.

MS sends SO 33 and starts PPP LCP negotiation with PDSN/LAC. CHAP can be negotiated as the protocol used for PPP authentication. (Step 1) PDSN/LAC sends CHAP challenge to MS. (Step 2) The MS replies with its NAI and a challenge response calculated based on the challenge and a secret shared with the local AAA in the GPRS system. The PDSN/LAC sends a "RADIUS Access Request". Since the domain name of the MS's NAI indicates the GPRS system, the "RADIUS Access Request" can be routed to the local AAA in the GPRS system via the visited AAA and the IIF of the proxy message. The IIF may modify this message according to [3GPP TS 29.061]. (Step 3) If the authentication is successful, the local AAA server replies with "RADIUS Access Accept". The message is routed back to the PDSN/LAC through the IIF and the visited AAA. The IIF inserts the Tunnel-Server-Endpoint attribute into the "RADIUS Access Accepted". This attribute informs PDSN/LAC to establish L2TP tunnel with IIF as LNS. The PDSN/LAC sends "CHAP Success" to inform the MS of successful authentication. (step 4)

PDSN/LAC establishes L2TP tunnel/session with IIF as LNS. During L2TP tunnel/session establishment, the PDSN/LAC forwards the LCP information (exchanged between MS and PDSN/LAC) to the IIF. The IIF LNS function can initiate a CHAP challenge (not shown in the figure) to authenticate the MS prior to IPCP negotiation. (Step 5) The IIF SGSN function sets up the GTP tunnel with the GGSN in the local GPRS system, and can request an IP address from the GGSN. The IIF gets the APN, which has the format: <network ID>.mnc<MNC>.mcc<MCC>.gprs. <Network ID> is part of the NAI scope of the MS and is used to indicate which GGSN the MS wants to access to obtain the requested service. Get <MNC> and <MCC> from MS's IMSI. The NAI and IMSI of the MS can be obtained from the "RADIUS Access Request" in step 3. The IIF SGSN function uses the obtained APN as a lookup name to query the GPRS DNS server (not shown in the figure), and obtains a list of available GGSNs that can be used to support the requested service. The IIFSGSN function sends a "Create PDP Context Request" to the selected GGSN. Set the Requested PDP Address in this message to 0.0.0.0 to request a new IP address. (Step 6) The GGSN responds with a "Create PDP Context Response" including the new IP address assigned to the MS. (step 7)

This new IP address may be assigned to the MS during the PPP IPCP negotiation between the IIF and the MS. (Step 8) PDSN/FA transmits "RADIUS Accounting Request (Start)" including 3GPP2 Packet Data Accounting Information [IS-835]. PDSN transmits "RADIUS Accounting Request (Start)" including 3GPP2 Packet Data Accounting Information [P.S0001-AV3.0]. Since the domain name of the MS's NAI indicates the GPRS system, the "RADIUS Accounting Request (start)" is routed to the local AAA in the GPRS system through the visited AAA and IIF. The IIF may modify this message according to [3GPP TS 29.061]. (Step 9) The local AAA replies with a "RADIUS Accounting Reply (Start)", which is routed back to the PDSN through the IIF and the visited AAA. (step 10)

Bearer traffic passes through the IIF in both directions. To route MS-originated packets, the IIF routes packets received from the MS's L2TP tunnel/session to the MS's GTP tunnel (identified by TEID). To route MS-terminated packets, the IIF routes packets received from the MS's GTP tunnel to the MS's L2TP tunnel/session. IPsec can be used to protect the L2TP tunnel/session between PDSN/LAC and IIF and the GTP tunnel between IIF and GGSN. (step 11)

IIF/AAA Requirements for CDMA 2000 Packet Data Foreign Mode with Simple IP

The IIF requirements for handling a "RADIUS Access Request" are the same as those described above for handling a "RADIUS Access Request" for CDMA 2000 Packet Data Foreign Mode with Mobile IP.

The IIF requirements for handling "RADIUS Access Accept" are similar to the requirements for handling "RADIUS Access Accept" for CDMA 2000 Packet Data Foreign Mode with Mobile IP, however, if the policy of the local GPRS system requires roaming MS data traffic passing through the local GPRS system via the IIF, and did not include the HA-address VSA in the corresponding "RADIUS Access Request" previously received from the visited CDMA2000 packet data system, then the IIF will tunnel-server-endpoint, tunnel-type and The Tunnel-Media-Type attribute is inserted in the sent "RADIUS Access-Accept" to the visited CDMA 2000 packet data system. The Tunnel-Server-Endpoint attribute indicates the IIF/LNS address. The tunnel-type attribute indicates L2TP. The tunnel-media-type attribute indicates IPv4.

The IIF requirements for handling "RADIUS Accounting-Request Start" and "Accounting-Request Period" are the same as those described above for handling "RADIUS Accounting-Request Start" and "Accounting-Request Fee Request Period" requirements are the same.

The IIF requirements for handling "RADIUS Accounting-Request Stop" are essentially the same as for handling "RADIUS Accounting-Request Stop" for CDMA 2000 Packet Data Foreign Mode with Mobile IP, however, if the received " If the session-continue VSA is set to "false" in RADIUS accounting request stop", and the IP-technology VSA indicates simple IP, then the IIF inserts the 3GPP session-stop-indicator VSA to indicate that the PDP session has terminated.

Those of skill in the art would understand that information and signals may be represented using various different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination of the above , and chips.

Those skilled in the art should also understand that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above primarily in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints placed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation should not be interpreted as causing a departure from the scope of the present invention.

A general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or Any combination of the above components designed to perform the functions described herein implements or performs the various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, eg, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be directly embodied in hardware, in a software model executed by a processor, or in a combination of both. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium can be integrated with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in the user terminal. Alternatively, the processor and the storage medium may exist in the user terminal as discrete components.

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

Claims (38)

1. interface entities, when travelling carriage was just roaming into the GPRS visited network, this interface entities makes can carry out mobile IP communication between CDMA2000 local network and the described GPRS visited network, and this interface entities comprises:

The access control emulation module, it is definite user's who is associated with described travelling carriage identity and privilege safely;

Be coupled to the mobile agent emulation module of described access control emulation module, it supports the carrier between described visited network and the described local network to connect, make described mobile agent emulation module and described access control emulation module to be offered described local network by first external interface, and

The gateway that is coupled to described mobile agent emulation module and described access control emulation module is supported emulation module, it supports the carrier between described visited network and the described local network to connect, and makes and by second external interface described gateway is supported that emulation module offers described visited network.

2. interface entities as claimed in claim 1 also comprises:

Global system for mobile communications (GSM) home location register emulation module, it is coupled to described visited network by the 3rd external interface; And

ANSI-41 Visited Location Registor emulation module, its by all round portion's interface be coupled to ANSI-41 Home Location Register in the described local network.

3. interface entities as claimed in claim 2, wherein, described gateway supports that emulation module is Gateway GPRS Support Node (GGSN) emulation module, it is coupled to Serving GPRS Support Node (SGSN) in the described visited network by described second external interface.

4. interface entities as claimed in claim 3, wherein, described GGSN emulation module is coupled to the Internet by the 5th external interface.

5. interface entities as claimed in claim 3, wherein, described GSM Home Location Register is coupled to described SGSN by described the 3rd external interface.

6. interface entities as claimed in claim 1, wherein, described access control emulation module is (AAA) emulation module that inserts, authorizes, charges, it is coupled to AAA entity in the described local network by the 6th external interface, wherein, described AAA emulation module is undertaken alternately chargeing billing function being provided to carry out mobile IP Foreign Agent challenge authentication and 3GPP2 grouped data by the AAA entity with described local network.

7. interface entities as claimed in claim 1, wherein, described mobile agent emulation module is the foreign agent emulation module by the coupling of the local agent in described first external interface and the described local network.

8. interface entities, when travelling carriage was just roaming into the GPRS visited network, this interface entities makes between CDMA2000 local network and the described GPRS visited network can carry out simple IP communication, and this interface entities comprises:

The access control emulation module, it is definite user's who is associated with described travelling carriage identity and privilege safely;

Be coupled to the link access control emulation module of described access control emulation module, it supports the carrier between described visited network and the described local network to connect, make described link access control emulation module and described access control emulation module to be offered described local network by first external interface, and

The gateway that is coupled to described link access control emulation module and described access control emulation module is supported emulation module, it supports the carrier between described visited network and the described local network to connect, and makes and by second external interface described gateway is supported that emulation module offers described visited network.

9. interface entities as claimed in claim 8 also comprises:

Global system for mobile communications (GSM) home location register emulation module, it is coupled to described visited network by the 3rd external interface, and wherein, described GSM Home Location Register allows the user to register by described the 3rd external interface; And

ANSI-41 Visited Location Registor emulation module, its by all round portion's interface be coupled to ANSI-41 Home Location Register in the described local network, wherein, described Visited Location Registor allow the user by described all round portion's interface register.

10. interface entities as claimed in claim 9, wherein, described gateway supports that emulation module is Gateway GPRS Support Node (GGSN) emulation module, it is coupled to Serving GPRS Support Node (SGSN) in the described visited network by described second external interface.

11. interface entities as claimed in claim 10, wherein, described GGSN emulation module is coupled to the Internet by the 5th external interface.

12. interface entities as claimed in claim 10, wherein, described GSM Home Location Register by described all round portion's interface be coupled to described SGSN.

13. interface entities as claimed in claim 8, wherein, described access control emulation module is (AAA) emulation module that inserts, authorizes, charges, it is coupled to AAA entity in the described local network by the 6th external interface, wherein, described AAA emulation module is undertaken alternately chargeing billing function being provided to carry out L2TP authentication and 3GPP2 grouped data by the AAA entity with described local network.

14. interface entities as claimed in claim 8, wherein, described link access control emulation module is by be coupled down L2TP Network Server in the described local network of described first external interface, and wherein, described Link Access Control Sublayer is layer 2 a last sublayer, and is provided for correct transmission and transmits mechanism at the signaling message of layer 3 generation.

15. an interface entities, when travelling carriage was just roaming into the CDMA visited network, this interface entities makes can carry out mobile IP communication between GPRS local network and the described CDMA visited network, and this interface entities comprises:

The access control emulation module, it is definite user's who is associated with described travelling carriage identity and privilege safely;

Be coupled to the home agent emulation module of described access control emulation module, it supports the carrier between described visited network and the described local network to connect, make described home agent emulation module and described access control emulation module to be offered described visited network by first external interface, and

Be coupled to the service support emulation module of described home agent emulation module, it supports the carrier between described visited network and the described local network to connect, and makes by second external interface described service support emulation module to be offered described local network.

16. interface entities as claimed in claim 15 also comprises:

Global system for mobile communications (GSM) Visited Location Registor emulation module, it is coupled to described local network by the 3rd external interface; And

The ANSI-41 home location register emulation module, its by all round portion's interface be coupled to ANSI-41 Visited Location Registor in the described visited network.

17. interface entities as claimed in claim 16, wherein, described service support emulation module is Serving GPRS Support Node (SGSN) emulation module, and it is coupled to Gateway GPRS Support Node (GGSN) in the described local network by described second external interface.

18. interface entities as claimed in claim 16, wherein, described GSM Visited Location Registor is coupled to GSM Home Location Register in the described local network by described the 3rd external interface.

19. interface entities as claimed in claim 15, wherein, described access control emulation module is (AAA) emulation module that inserts, authorizes, charges, and it is coupled to the AAA entity in the described local network and is coupled to AAA entity in the described visited network by the 6th external interface by the 5th external interface.

20. interface entities as claimed in claim 15, wherein, described home agent emulation module is coupled to packet data serving node (PSDN)/Foreign Agent in the described visited network by described first external interface.

21. an interface entities, when travelling carriage was just roaming into the CDMA visited network, this interface entities makes between GPRS local network and the described CDMA visited network can carry out simple IP communication, and this interface entities comprises:

The access control emulation module, it is definite user's who is associated with described travelling carriage identity and privilege safely;

Be coupled to L2TP Network Server (LNS) emulation module of described access control emulation module, it supports the carrier between described visited network and the described local network to connect, make described LNS emulation module and described access control emulation module to be offered described visited network by first external interface, and

Be coupled to the service support emulation module of described LNS emulation module, it supports the carrier between described visited network and the described local network to connect, and makes by second external interface described service support emulation module to be offered described local network.

22. interface entities as claimed in claim 21 also comprises:

Global system for mobile communications (GSM) Visited Location Registor emulation module, it is coupled to described local network by the 3rd external interface; And

The ANSI-41 home location register emulation module, its by all round portion's interface be coupled to ANSI-41 Visited Location Registor in the described visited network.

23. interface entities as claimed in claim 22, wherein, described service support emulation module is Serving GPRS Support Node (SGSN) emulation module, and it is coupled to Gateway GPRS Support Node (GGSN) in the described local network by described second external interface.

24. interface entities as claimed in claim 22, wherein, described GSM Visited Location Registor is coupled to GSM Home Location Register in the described local network by described the 3rd external interface.

25. interface entities as claimed in claim 21, wherein, described access control emulation module is (AAA) emulation module that inserts, authorizes, charges, and it is coupled to the AAA entity in the described local network and is coupled to AAA entity in the described visited network by the 6th external interface by the 5th external interface.

26. interface entities as claimed in claim 21, wherein, described LNS emulation module is coupled to packet data serving node (PSDN)/link access control in the described visited network by described first external interface.

27. one kind is used for initiating mobile IP method for communicating when travelling carriage is just roaming into the GPRS visited network between CDMA2000 local network and described GPRS visited network, comprises:

Initiate and the communicating by letter of described travelling carriage by described visited network;

Send one or more mobile IP agent bulletins to described travelling carriage;

Receive mobile IP login request from described travelling carriage;

Authenticate with described local network;

Sending mobile IP registration to described travelling carriage answers; And

Upgrade the PDP Context request with described travelling carriage and reply.

28. method as claimed in claim 27 wherein, is initiated to comprise with communicating by letter of described travelling carriage by described visited network:

Be used for the request that GPRS is additional and authenticate from the travelling carriage reception;

Receive the request of activation PDP Context from Serving GPRS Support Node (SGSN), be used for the PDP Context of described travelling carriage with foundation; And

Sending the establishment PDP Context to described SGSN replys.

29. method as claimed in claim 27 wherein, authenticates with described local network and to comprise:

Send RADIUS to (AAA) entity that inserts, authorizes, charges and insert request;

Receive RADIUS from described AAA entity and insert acceptance;

Send mobile IP login request to local agent;

Receiving mobile IP registration from described local agent answers; And

Described AAA entity on described local network is initiated RADIUS account.

30. one kind is used for initiating mobile IP communicating devices when travelling carriage is just roaming into the GPRS visited network between CDMA2000 local network and described GPRS visited network, comprises:

By the module of communicating by letter of described visited network initiation with described travelling carriage;

Send the module of one or more mobile IP agent bulletins to described travelling carriage;

Receive the module of mobile IP login request from described travelling carriage;

The module that authenticates with described local network;

Send the module that mobile IP registration is answered to described travelling carriage; And

The module of upgrading the PDP Context request and replying with described travelling carriage.

31. device as claimed in claim 30 wherein, initiates to comprise with the module of communicating by letter of described travelling carriage by described visited network:

Receive the module of the request be used for the additional and authentication of GPRS from travelling carriage;

Receive the request of activation PDP Context from Serving GPRS Support Node (SGSN), be used for the module of the PDP Context of described travelling carriage with foundation; And

Send the module that the establishment PDP Context is replied to described SGSN.

32. device as claimed in claim 30, wherein, the module that authenticates with described local network comprises:

(AAA) entity sends the module that RADIUS inserts request to inserting, authorize, chargeing;

Receive RADIUS from described AAA entity and insert the module of accepting;

Send the module of mobile IP login request to local agent;

Receive the module that mobile IP registration is answered from described local agent; And

Described AAA entity on described local network is initiated the module of RADIUS account.

33. one kind is used for initiating the simple IP method for communicating when travelling carriage is just roaming into the GPRS visited network between CDMA2000 local network and described GPRS visited network, comprises:

Initiate and the communicating by letter of described travelling carriage by described visited network;

Carrying out PPP(Point-to-Point Protocol)/LCP (LCP) with described travelling carriage consults;

Set up L2TP Tunnel with the LNS in the described local network;

Upgrade the PDP Context request with described travelling carriage and reply; And

Initiate RADIUS account to described local network.

34. method as claimed in claim 33 wherein, is initiated to comprise with communicating by letter of described travelling carriage by described visited network:

Be used for the request that GPRS is additional and authenticate from the travelling carriage reception;

Receive the request of activation PDP Context from Serving GPRS Support Node (SGSN), be used for the PDP Context of described travelling carriage with foundation; And

Sending the establishment PDP Context to described SGSN replys.

35. method as claimed in claim 33 wherein, is initiated RADIUS account and is comprised:

(AAA) entity sends the RADIUS account request to inserting, authorize, chargeing; And

Receiving RADIUS account from described AAA entity accepts.

36. one kind is used for initiating the simple IP communicating devices when travelling carriage is just roaming into the GPRS visited network between CDMA2000 local network and described GPRS visited network, comprises:

By the module of communicating by letter of described visited network initiation with described travelling carriage;

Carry out the module that PPP(Point-to-Point Protocol)/LCP (LCP) is consulted with described travelling carriage;

Set up the module of L2TP Tunnel with the LNS in the described local network;

The module of upgrading the PDP Context request and replying with described travelling carriage; And

Initiate the module of RADIUS account to described local network.

37. device as claimed in claim 36 wherein, initiates to comprise with the module of communicating by letter of described travelling carriage by described visited network:

Receive the module of the request be used for the additional and authentication of GPRS from travelling carriage;

Receive the request of activation PDP Context from Serving GPRS Support Node (SGSN), be used for the module of the PDP Context of described travelling carriage with foundation; And

Send the module that the establishment PDP Context is replied to described SGSN.

38. device as claimed in claim 36, wherein, the module of initiating RADIUS account comprises:

Send the module of RADIUS account request to (AAA) entity that inserts, authorizes, charges; And

Receive the module that RADIUS account is accepted from described AAA entity.

Images