TWI390876B - Methods and apparatuses for cdma2000/gprs roaming - Google Patents

Description

Method and device for CDMA2000/GPRS roaming

The embodiments disclosed herein relate generally to wireless communications, and more particularly to roaming in the context of CDMA2000 (Code Division Multiple Access (CDMA) 2000) and GPRS (General Packet Radio Service) systems.

A wireless subscriber may need to use its wireless terminal in conjunction with a wireless system other than its home system to gain access to the service by its existing subscription. Access to such services via a wireless system other than their home system may be independent of their normal wireless terminal. This may occur, for example, when a user roams outside of the service area of their home system. Therefore, the manufacturer and system operator need to allow the user to receive the service by using its terminal and by a system that may not be the user's home system (provided the terminal is compatible with the service system).

Even when the service system uses the same technology as the home system, it is still difficult to provide services for roaming users. When the radio interface used by the service system is different from the radio interface used in the user's home system, such inter-system interworking is typically performed due to fundamental differences between message protocols, call patterns, and the like. This interconnection can be achieved via the Interconnect and Interworking Function (IIF).

An example of an IIF is described in U.S. Patent Application Serial No. 2002/094,811, issued to to-A. U.S. Patent Application Serial No. 2002/094811 A1 provides service between GSM (Global System for Mobile Communication)/GPRS wireless GPRS interconnection and interworking function (IIF) between GSM (Global System for Mobile Communication)/GPRS wireless system and a second wireless system of one different technology family. The IIF allows a mobile station with a second wireless system to be a home system to operate in a GSM/GPRS system. A telecommunications system component that allows interconnection and interoperation between a GSM and/or GPRS system and certain "local area wireless" systems is provided in accordance with U.S. Patent Application Serial No. 2002/094,811, filed on Jan. For example, with the wireless system of the local area as the home system, the mobile station registered in the service system in the GPRS-only mode can receive the service from the service system. U.S. Patent Application Serial No. 2002/094811 A1, the entire disclosure of which is incorporated herein by reference in its entirety in its entirety, the the the the the the the the the the the the the the the the the the the the the the the the Non-GSM systems compatible with equivalent standards, such as those commonly used in North America, or compatible with other similar systems.

Although the U.S. Patent Application Serial No. 2002/094811 A1 recognizes the need for the IIF to allow the mobile station of the CDMA wireless system to operate in the GSM/GPRS system, the US Patent Application No. 2002/094811 A1 does not discuss the use of the terminal. The Internet Protocol (IP) or Simple IP is applicable to the IIF of the CDMA2000/GPRS roaming case. When the terminal is using Mobile IP or Simple IP, the US Patent Application No. 2002/094811 A1 fails to construct a mobile station that allows the mobile station with the CDMA2000 wireless system to be the home system to operate in the GSM/GPRS system. Provide enough information, direction or guidance. For example, what modules are needed to implement this IIF, how the modules are connected, timed, and controlled to obtain the specific operations required to implement the IIF, US Patent Application No. 2002/094811 A1 fails to mention For any details.

Therefore, there is a need in the art for a general architecture suitable for CDMA2000/GPRS roaming cases, such as GPRS field mode using IPv4 (Internet Protocol version 4); using simple IPv4 or IPv6 (Internet Protocol version 6) GPRS field mode; CDMA2000 packet data field using mobile IPv4; and CDMA2000 packet data field using simple IP, mobile IPv4 or mobile IPv6. We expect that when CDMA2000 packet data using simple IP, mobile IPv4 or mobile IPv6 roams to the GPRS system, it can be supported by supporting bearer connectivity between GPRS and CDMA2000 packet data systems. Communication between the CDMA2000 packet data system and the GPRS system is possible. Similarly, we also expect that when the GPRS home subscriber roams from the GPRS system to the CDMA2000 packet data system by using simple IP, mobile IPv4 or mobile IPv6, it can support the bearer connectivity between the GPRS system and the CDMA2000 packet data system. This enables communication between the GPRS system and the CDMA2000 packet data system.

According to an aspect of the present invention, an interface entity is provided between a CDMA2000 packet data system and a GPRS system. When a CDMA2000 packet data belongs to a user roaming to the GPRS system, the interface entity provides a packet. The routing function thus supports the bearer connectivity between the GPRS and CDMA2000 packet data systems to enable communication between the CDMA2000 packet data system and the GPRS system.

According to an aspect of the present invention, an interface entity is provided when an action is used When the IPv4 CDMA2000 packet data belongs to the visited GPRS system, the interface entity enables communication between the CDMA2000 packet data system and the visited GPRS system including an SGSN (Serving GPRS Support Node).

For example, in one embodiment in which a CDMA2000 packet data attribution user roams to a visited system and uses Mobile IPv4, an interface entity can be provided that couples the home system to the visited system such that Communication between the home system and the interviewed system is possible. In this case, the home system is a CDMA2000 packet data system, which may include an ANSI-41 home location register, an AAA (authentication, authorization and accounting) entity, and a home agent, and the system is visited. It can be a GPRS system including an SGSN.

According to one aspect of the embodiment, the interface includes a GSM home location register emulation module and an ANSI-41 visited location register emulation module. The GSM local location register emulation module that allows the user to register via the Gr interface can be coupled to the SGSN via a Gr interface, and allows the user to register the ANSI-41 visited location register via the D interface. The analog module can be coupled to the ANSI-41 home location register via the D interface. According to an aspect of the embodiment, the interface further includes a foreign agent simulation module and a GGSN (Gateway GPRS Support Node) analog module. The foreign agent simulation module can be coupled to the home agent via an X1 interface, and supports bearer connectivity between the visited system and the home system, so that the foreign agent interface and the AAA interface are presented to the CDMA2000 packet data through the X1 interface. system. The GGSN analog module can be coupled to the SGSN via the Gp interface, and can be supported The bearer connectivity between the visited system and the home directory system is such that the GGSN interface is presented to the interviewed system via the Gp interface. The interface acts as one of the endpoints of the GTP (GPRS Tunneling Protocol) tunnel and the mobile IP tunnel. In this embodiment, the interface provides a packet routing function between the GGSN interface and the foreign agent interface. According to another aspect of the embodiment, the interface can also include an AAA analog module coupled to the AAA entity via an X3 interface. In this embodiment, the AAA analog module provides an account processing function by interacting with the AAA of the home network for mobile IP foreign agent challenge authentication and 3GPP2 (3rd Generation Partnership Project 2) packet data account processing ( Accounting function).

According to an aspect of the present invention, an interface entity is provided. When a CDMA2000 packet data of a simple IP is used to roam the user to the visited GPRS system, the interface entity enables the GPRS 2000 packet data system and the visited GPRS including an SGSN. Communication between systems.

In an embodiment in which a CDMA2000 packet data attribution user roams to a visited system and uses a simple IP, an interface entity can be provided, the interface entity coupling the home directory system to the visited system to enable The system communicates with the system being interviewed. In this case, the home system is a CDMA2000 packet data system that can include an ANSI-41 home location register, an AAA entity, and an LNS (Layer 2 Tunneling Protocol Network Server), and the visited system can include an SGSN. GPRS system.

According to one aspect of this embodiment, the interface includes an ANSI-41 visited location register and a GSM home location register. The ANSI-41 visited location register can be coupled to the ANSI-41 home location register via a D interface and allows the user to register via the D interface. GSM local location register can be accessed via Gr The interface is coupled to the SGSN and allows the user to register via the Gr interface. According to another aspect of the embodiment, the interface may include a LAC (Location Area Code) analog module and a GGSN analog module. The LAc analog module can be coupled to the LNS via the X2 interface and supports the bearer connectivity between the visited and the home network via the X2 interface. The GGSN analog module can be coupled to the SGSN via the Gp interface and provided between the GGSN interface and the home system via the Gp interface by presenting a GGSN interface to the visited system and presenting a normal routing interface to the CDMA2000 packet data system. A packet routing function to support bearer connectivity between the visited and the home network. In this case, the interface acts as an endpoint of a GTP tunnel and an IPSec (IP Security) tunnel. According to another aspect of this embodiment, the interface can include an AAA analog module that can be coupled to the AAA entity via the X3 interface. The AAA analog module can provide an account processing function by interacting with the AAA of the home network via the X3 interface for L2TP (Layer 2 Tunneling Protocol) authentication and 3GFP2 packet data account processing.

According to another aspect of the present invention, an interface entity between a GPRS system and a CDMA2000 packet data system is provided, when a GPRS home subscriber roams from a GPRS system to a CDMA2000 packet data system by using one of mobile IPv4 and simple IP. The interface entity supports bearer connectivity between the GPRS system and the CDMA2000 packet data system by providing a packet routing function to enable communication between the GPRS system and the CDMA2000 packet data system.

According to another aspect of the present invention, an interface entity is provided. When a GPRS home subscriber using Mobile IPv4 roams to a visited CDMA2000 packet data system, the interface entity enables a GSM local location register, a GGSN And an AAA entity's native GPRS system; communicating with a CDMA2000 packet data system including an ANSI-41 visited location register, an AAA entity, and a packet data service node/foreign agent News.

In one embodiment in which a GPRS home subscriber roams to a visited system and uses Mobile IPv4, an interface entity can be provided that couples the home system to the visited system such that the home system can be Communicate between the access systems. In this case, the home system is a GPRS system including a GSM home location register, a GGSN, and an AAA entity, and the visited system may include a CDMA2000 packet data system, and the CDMA2000 packet data system includes an ANSI-41. The visited location register, an AAA entity, and a packet data service node/foreign agent.

According to an aspect of the embodiment, the interface includes a home agent simulation module and an SGSN analog module. The home agent simulation module can be coupled to the packet data service node/foreign agent via the X1 interface, and present a home agent interface to the interviewed system. The SGSN analog module can be coupled to the GGSN via the Gp interface, and the SGSN interface is presented to the home system to support the bearer connection between the visited and the home network by providing a packet routing function between the SGSN interface and the home agent interface. Sex. Here, the interface acts as an endpoint for one GTP tunnel and one mobile IP tunnel. According to another aspect of the embodiment, the interface may also include an ANSI-41 home location register emulation module and a GSM visited location register emulation module. The ANSI-41 local location register emulation module can be coupled to the ANSI-41 visited location register via the D interface, and the GSM visited location register emulation module can be coupled to the GSM local location via the D interface. A scratchpad to allow users to register. According to another aspect of the embodiment, the interface may also include an AAA analog module, which may be coupled to the AAA entity via the Gi interface and may be coupled via the X3 interface. Connect to the AAA entity. The AAA analog module interacts with the AAA of the visited network through the X3 interface for mobile IP authentication and 3GPP2 packet data account processing, and can interact with the AAA of the home network through the Gi interface for 3GPP packet data account processing. .

According to an aspect of the present invention, an interface entity is provided. When a GPRS home subscriber using a simple IP roams to the visited CDMA2000 packet data system, the interface entity enables the inclusion of a GSM local location register and a GGSN. And an AAA entity's GPRS system communicates with a CDMA2000 packet data system including an ANSI-41 visited location register, an AAA entity, and a packet data service node/LAC entity.

In an embodiment in which a GPRS home subscriber roams to a visited system and uses a simple IP, an interface entity can be provided that couples the home system to the interviewed system such that the home and the interview are available Communication between systems. In this case, the home system is a GPRS system including a GSM home location register, a GGSN, and an AAA entity, and the visited system may include a CDMA2000 packet data system, the CDMA2000 packet data system including an ANSI- 41 interviewed location register, an AAA entity, and a packet data service node/LAC entity. According to one aspect of the invention, the interface supports bearer connectivity between the visited network and the home network by providing a packet routing function. For example, the interface can include an SGSN analog module and an LNS analog module. The SGSN analog module can be coupled to the GGSN through the Gp interface and display the SGSN interface to the home system, and the LNS analog module can be coupled to the packet data service node/LAC entity and the L2TP network server through the X2 interface. The (LNS) interface is presented to the interviewed system. with In this way, the interface provides packet routing between the SGSN analog module and the LNS analog module. Here, the interface acts as an endpoint for the GTP tunnel and the mobile L2TP tunnel.

According to another aspect of the embodiment, the interface includes an ANSI-41 home location register emulation module and a GSM visited location register emulation module. The ANSI-41 local location register emulation module can be coupled to the ANSI-41 visited location register via a D interface, while the GSM visited location register emulation module can be coupled to GSM via another D interface. Home location register. This allows the user to register. According to another aspect of the embodiment, the interface can also include an AAA analog module, which can be coupled to the AAA entity via the Y3 interface and can be coupled to the AAA entity via the X3 interface. The AAA analog module interacts with the AAA entity of the visited network through the X3 interface for L2TP authentication and 3GPP2 packet data account processing, and interacts with the AAA entity of the home network through the Gi interface to perform 3GPP packet data account processing.

The term "exemplary" is 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 preferred.

1 is a block diagram of a system including a home system 10 such as a CDMA2000 packet data system or a GPRS system; a visited system 20 such as a GPRS system or a CDMA2000 packet data system; and an interface entity 30, or "IIF The interface entity couples the home directory system 10 to the visited system 20 and enables communication between the home directory system 10 and the visited system 20.

The following sections describe architectures that can be applied to CDMA2000/GPRS roaming cases, such as the GPRS field mode using mobile IPv4, the GPRS field mode using simple IPv4 or IPv6, and the CDMA2000 packet data using mobile IPv4. Mode, and field mode of CDMA2000 packet data using simple IPv4 or IPv6.

GPRS field mode using mobile IPv4

2A is an exemplary block diagram 2000 of a GPRS field mode employing Mobile IPv4, and depicts the functionality and control interface provided by an IIF in this embodiment. This roaming case occurs when a CDMA2000 packet data belongs to the user operating the IPv4 [IS-835-C] in the GPRS foreign mode. In this embodiment, the home system 10 can be a CDMA2000 packet data system in which a CDMA2000 packet data home subscriber roams to a GPRS system and uses mobile IPv4. The home registration system 10 includes an ANSI-41 home location register 131, an AAA entity 116, and a home agent 135. The interviewed system 20 can be a GPRS system that includes a SGSNI 37.

The interface 30 or "IIF" includes an ANSI-41 visited location register 111 coupled to the ANSI-41 home location register 131 via a D interface 113; a GSM home registration coupled to the SGSN 137 via the Gr interface 123 a location register 124; a GGSN 126 coupled to the SGSN 137 via a Gp interface 127 and coupled to the Internet via a Gi interface; an AAA entity 140 coupled to the AAA entity 116 via an X3 interface 117; and an X1 via X1 The interface 115 is coupled to the agent 118 outside the home agent 135. IIF provides both GSM HLR (Home Location Register) and ANSI-41 VLR (Visited Location Register) simulation to allow user registration. This interconnection can be provided by referring to "Gr" and "D" at the interface. IIF provides GGSN and FA (Foreign Agent) simulations to The IIF supports the bearer connectivity between the interviewed and the home network. This interconnection can be provided by the interface references "Gn" and "X1". The IIF provides an AAA simulation to interact with the AAA of the home network for action IP foreign agent challenge authentication and 3GPP2 packet data account processing. This interconnection can be provided by the interface reference "X3".

If there is no need to carry connectivity between the GPRS system and the CDMA2000 packet data system, reverse tunneling on the X1 interface is not required. In contrast, MS (Mobile Station) terminated communication traffic through the X1 and Gp interfaces. In the case where reverse tunneling is not required, the IIF delivers the incoming communication traffic of the MS received on the Gp interface directly to the Internet via a Gi interface.

Therefore, for users roaming to the GSM system with the CDMA mobile IP system as the home system, the IIF can present a GGSN interface to GSM and an FA and AAA interface to the CDMA system. The IIF can act as an endpoint for GTP and Mobile IP tunneling through the packet routing function between the GGSN and the FA. The IIF can also provide account processing functionality that allows the operator to bill based on configurable measurements such as packet count, bandwidth, date, and the like.

2B is an exemplary call flow diagram 2010 showing mobile IPv4 operation in a GPRS foreign mode. 2B depicts an example of a call flow for a roaming case in which a CDMA2000 packet material home user operates the IPv4 [IS-835-C] in GPRS foreign mode. In this example, the MS shares a secret with the native CDMA2000 system for mobile IP authentication. The MS may require the home CDMA2000 system to assign an HA (Home Agent) and/or an IP address. Reverse tunneling can be enabled to enable all data traffic (MS starts) And the MS terminated) through the IIF and the CDMA2000 system. The IIF generates a 3GPP2 packet data account processing record and delivers it to the CDMA2000 system via the RADIUS (Remote Authentication Dial-In User Service).

The MS performs the attachment of GPRS and SGSN. The combination with GPRS attachment is recognized as SIM-based authentication requiring Ki keys. The IIF acts as a GSM HLR configured with Ki Secret. Under no circumstances should the IIF be required to communicate with the HLR in the CDMA2000 system for authentication. (Step 1) The MS sends a PDP (Packet Data Protocol) context request to the SGSN. This message includes the Access Point Name (APN). The APN has this format: <network ID>.<MNC>.<MCC>.gprs. The network ID (eg, CDMA2000carrier.com) indicates the external network with which the MS wants to establish a logical connection. The requested PDP address can be omitted from the message. The MS has a static mobile IP address or a new mobile IP address. (Step 2) The SGSN selects a GGSN based on the APN. The SGSN uses the APN as the query name to query a DNS (Domain Name System) server (not shown) and obtains a list of available GGSNs that can be used to support the requested APN. The network ID of the APN indicates a CDMA2000 operator; therefore, the DNS server returns with the IP address of the IIF. (Step 3) The SGSN sends a Start PDP Context Request to the selected IIF to establish a PDP context for the MS. The message includes the APN, but the requested PDP address can be omitted. (Step 4) The IIF is used as a GGSN and sends a Create PDP Context Response to the SGSN, which in turn sends a Start PDP Context Acceptance to the MS. The PDP address in both messages can be set to 0.0.0.0 to indicate that the PDP address will be assigned after the active IP is successfully registered later. (Step 5) because on the boot PDP Omitting the requested PDP address in the request below may indicate that the MS wishes to use the mobile IP, so the IIF is used as the FA and one or more mobile IP proxy advertisements are sent to the MS. The proxy advertisement can be sent by the established PDP context. The agency advertisement contains the FA transfer address and FA question (FAC). (Step 6)

The MS sends an action IP registration request to the IIF via the PDP context. The registration request may contain the following information; MS's NAI (Network Access Identifier) [RFC 2794] has this format: <user name>@<domain_name>, where the domain_name identifies the MS's native CDMA2000 system. The MS-HA authenticator can be calculated based on the content of the registration request and the secret shared between the MS and the HA [RFC2002]. The MS-AAA authenticator can be calculated based on the secret shared between the FAC and the MS and the home AAA server [RFC 3012]. If the MS uses a permanent HA, the HA address field can be set to a known value, or if the MS wishes to assign a new HA from the home network, the HA address field can be set to 0.0.0.0. If the MS uses a permanent address, the home address field can be set to a known value, or if the MS wishes to assign a new address by the HA, the home address field can be set to 0.0.0.0. The T bit can be set to one to enable reverse tunneling from the IIF to the MS's HA. (Step 7) The IIF is used as a RADIUS client and sends a RADIUS access request to the home AAA server. The RADIUS access request conveys the NAI of the MS, the FAC authenticator, the FAC, the HA address, etc. [IS-835]. (Step 8) If the authentication is successful, the AAA server responds with RADIUS Access Accept (Access-Accept) including the MS's HA address. (Step 9) The IIF is used as the FA and the Mobile IP Registration Request is forwarded to the HA address included in the RADIUS Access Acceptance. (Step 10) The HA verifies the MS-HA Authenticator in the Mobile IP Registration Request. If the HA does not have the secret shared (such as dynamically assigning HA) In the case of a general case, it communicates with the AAA server of the home for the shared secret. The HA responds to the action IP registration request with an action IP registration reply containing a registration result (eg, success or code error). If the MS wants a new home address, it can return a new address in the registration reply; otherwise, it can return to the permanent address of the MS. (Step 11) The IIF is used as the FA, and the Mobile IP registration reply is forwarded to the MS by the appropriate PDP context. The IIF FA function records the assigned MS IP address and shares the address with the IIF GGSN function.

(Step 12)

The IIF is used as a GGSN and its PDP context is updated by setting the PDP address to the MS's home address (as displayed in the registration reply and shared with the FA function). The PDP address (and hence the MS's home address) can be associated with a GTP tunnel identified by the Tunnel Endpoint ID (TEID). (Step 13) The IIF is used as a GGSN and the GGSN initiated PDP context correction procedure is triggered to update the PDP address in the SGSN and MS [3GPP TS 29.061]. The IIF sends an 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 Response, which forwards it to the IIF. (Step 15) The IIF is used as a RADIUS client and sends a RADIUS account processing request (start) to the home AAA server [IS-835]. The 3GPP2 provider specified attributes are used to convey account processing records, but some wireless link record attributes (such as service options, multiplex options, etc.) are not available. (Step 16) The home AAA server responds with a RADIUS account processing response (start). (Step 17) If reverse tunneling from IIF to HA is enabled, the bearer traffic flows through the IIF in both directions. For the packet originating from the MS, the IIF is reversed via an action IP. The tunnel delivers the packet received from the MS's GTP tunnel (marked by TEID) to the HA of the MS. For a packet that is terminated by the MS, the IIF will receive a packet from the HA to FA tunnel to the GTP tunnel of the MS. IPSec can be used to protect mobile IP tunnels between HA and IIF, and GTP tunnels between IIF and SGSN.

(Step 18)

GPRS field mode using simple IP

3A is an exemplary block diagram 3000 of a GPRS foreign mode employing simple IP, showing a roaming case in which a CDMA2000 packet material belongs to a user operating IPv4 or IPv6 in a GPRS foreign mode. Figure 3A also depicts the functionality and control interface provided by an interface or IIF in this situation. In this embodiment, the home system 10 can be a CDMA2000 packet data system in which a CDMA2000 packet data belongs to a user roaming to a GPRS system and uses a simple IP. The home registration system 10 includes an ANSI-41 home location register 131, an AAA entity 116, and an LNS 139. The interviewed system 20 can be a GPRS system including an SGSN 137.

The interface 30 or "IIF" includes an ANSI-41 visited location register 111 coupled to the ANSI-41 home location register 131 via the D interface 113; a GSM coupled to the SGSN 137 via the Gr interface 123 a local location register 124; a GGSN 126 coupled to the SGSN 137 via the Gp interface 127 and coupled to the Internet via the Gi interface; an AAA entity 140 coupled to the AAA entity 116 via the X3 interface 117; And an LAC entity 109 coupled to the LNS 139 via the X2 interface 119. IIF provides both GSM HLR and ANSI-41 VLR emulation to allow user registration. This interconnection can be provided by referring to "Gr" and "D" at the interface. IIF provides GGSN and LAC simulations to IIF supports the connectivity of the interviewed and home network. This interconnection can be provided by referring to "Gn" and "X2" interfaces. IIF provides AAA emulation to interact with the AAA of the home network for L2TP authentication and 3GPP2 packet data account processing. This interconnection can be provided by the interface reference "X3".

If the connectivity between the CDMA2000 packet data system and the GPRS system does not need to be carried, the X2 interface is not required. The IIF still supports the Gp interface for the SGSN and provides Internet access via the Gi interface (not shown).

Therefore, for a user who is a CDMA simple IP system and roams to the GSM system, the IIF can present a GGSN interface to GSM and present a normal routing interface to the CDMA system. The IIF can act as an endpoint for GTP and IPSec tunnels by packet routing between the GGSN and the CDMA system. The IIF can also provide account processing functionality, and appropriate operators can bill based on configurable metrics such as packet count, bandwidth, date, and the like.

3B is an exemplary call flow diagram 3010 showing simple IP operation in a GPRS foreign mode and explaining a roaming case in which a CDMA2000 packet data belongs to a user operating a simple IP in a GPRS foreign mode. In this example, the MS shares a secret with the native CDMA2000 system for simple IP authentication (ie, CHAP). The MS establishes a PPP (Point-to-Point Protocol) session to the CDMA2000 system via L2TP. During the establishment of the PPP, the CDMA2000 system dynamically assigns an IP address to the MS. All MS data traffic (from the beginning of the MS and the termination of the MS) passes through the IIF and the CDMA2000 system. The IIF generates a 3GPP2 packet data account processing record and sends it to the CDMA2000 system via RADIUS.

The MS performs the attachment of GPRS and SGSN. The combination with GPRS attach is recognized as a SIM (Subscriber Identity Module) based authentication requiring Ki secret. The IIF is used as a GSM HLR or GSM VLR that is secretly configured with Ki. In any case, the IIF is not required to communicate with the HLR in the CDMA2000 system for authentication. (Step 1) The MS sends a Start PDP Context Request to the SGSN. This message includes the APN (Access Point Name). The APN has this format: <network ID>.<MNC>.<MCC>.gprs. The network ID (eg, CDMA2000carrier.com) indicates the external network with which the MS wants to establish a logical connection. The requested PDP address may be omitted in the message such that the IIF (used as a GGSN) will not assign an IP address to the MS later; instead, the address will be assigned by the LNS. (Step 2) The SGSN selects a GGSN based on the APN. The SGSN queries a DNS server (not shown) and obtains a list of available GGSNs that can be used to support the requested APN. In this case, the network ID of the APN indicates a CDMA2000 operator; therefore, the DNS server returns with the IP address of the IIF. (Step 3)

The SGSN sends a Start PDP Context Request to the selected IIF to establish a PDP context for the MS. The message includes the APN, but the requested PDP address can be omitted. (Step 4) The IIF is used as the GGSN, and the Create PDP Context Response is sent to the SGSN, which in turn sends an Activate PDP Context Accept to the MS. The PDP address in both messages can 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, the MS and the IIF perform a PPP LCP (Link Control Protocol) negotiation. The IIF LAC function is combined with an LNS to establish an L2TP tunnel. IIF determines which one based on the required APN LNS. The IIF is configured with LNS information corresponding to an APN (eg, the IP address of the LNS). After the L2TP tunnel is established, the IIF LAC function forwards the LCP information between the LNS and the MS. During LCP negotiation, the LNS and the MS negotiate PAP (Password Authentication Protocol) or CHAP (Challenge Handshake Authentication Protocol) as a protocol for PPP authentication. (Step 6) Perform PPP authentication (PAP or CHAP). The credential of the MS is authenticated by the AAA of the CDMA2000 system. The RADIUS interaction between the LNS and the AAA is not shown in the figure. (Step 7) The LNS and the MS perform PPP IPCP (IP Control Protocol) negotiation. The IIF LAC function relays IPCP messages between the L2TP tunnel and the PDP context. During the negotiation, the LNS assigns an IP address to the MS. The IIF monitors this address and uses it as the PDP address of the MS. (Step 8)

The IIF is also required to notify the SGSN and the MS of the updated PDP address. It should be remembered that the PDP address was 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 by updating the PDP context response, which the SGSN forwards to the 1IF. (Step 10)

The IIF acts as a RADIUS client and sends a RADIUS account to process the request (start) to the home AAA server [IS-835]. The 3GPP2 provider-specified attribute is used to convey account processing records, but some wireless link record attributes (such as service options, multiplex options, etc.) do not apply. (Step 11) The home AAA server responds with a RADIUS account processing response (beginning). (Step 12) The bearer traffic flows through the IIF in both directions. For the packet originating from the MS, the IDF will deliver the packet received from the MS's GTP tunnel (identified by TEID) to the L2TP tunnel/session of the MS. For the packet that is sent to the MS to terminate, the IIF will receive it from The L2TP tunnel/session packet of the MS is delivered to the GTP tunnel of the MS. IPsec can be used to protect the L2TP tunnel/session between LNS and IIF, and the GTP tunnel between IIF and SGSN. (Step 13)

Using the mobile IPv4 CDMA2000 packet data field model

4A is an exemplary block diagram 4000 of one of the CDMA2000 packet data field modes using Mobile IPv4. This section describes a roaming case in which a GPRS home subscriber operates the IPv4 [IS-835-C] in a CDMA2000 packet data field mode. Figure 4A also depicts the functionality and control interface provided by the IIF in this situation. In this embodiment, the home system 10 can be a GPRS system. A GPRS home subscriber roams to a CDMA2000 packet data system and uses a simple IP. The home system 10 includes a GSM home location register 124, a GGSN 126, and an AAA entity 128. The interviewed system 20 can be a CDMA2000 packet data system that includes an ANSI-41 visited location register 111, an AAA entity 116, and a packet data service node/foreign agent 118.

The interface 30 or "IIF" includes an ANSI-41 home location register 131 coupled to the ANSI-41 visited location register 111 via the D interface 113; coupled to the GSM home location via the D interface 121. The GSM visited location register 133 of the memory 124; coupled to the SGSN 137 of the GGSN 126 via the Gp interface 127; coupled to the AAA entity 128 via the X4 interface 129 and coupled to the AAA via the X3 interface 117 The AAA entity 140 of the entity 116; and a home agent 135 coupled to the packet data service node/foreign agent 118 via the X1 interface 115. IIF provides both GSM VLR and ANSI-41 HLR emulation to allow user registration. This interconnection can be provided by the interface reference "D". IIF provides HA and SGSN simulations to support the relationship between the interviewed and the home network via the IIF. Load connectivity. This interconnection can be provided by the interface reference "X1" and "Gn". The IIF provides AAA emulation to interact with the AAA of the visited network for mobile IP authentication and 3GPP2 packet data account processing. The IIF can also interact with the AAA of the home network for 3GPP packet account processing. This interconnection can be provided by referring to "X3" and "X4" interfaces. The IIF/AAA requirements for the field model of CDMA2000 packet data using Mobile IP will be described in more detail below.

If the connected CDMA2000 packet data system does not need to bear connectivity between the GPRS system and the GPRS system, the Gp interface is not needed. In this case, the data traffic of the origin of the action can be directly sent to the Internet via the PDSN (Packet Data Serving Node)/FA in the visited system, or, if reverse tunneling is enabled, via the IIF/ HA is delivered. The data traffic for the termination of the operation is delivered to the PDSN/FA via the IIF/HA. In order to interconnect the AAA messages between the IIF and the CDMA2000 AAA server and the GPRS AAA server, interfaces X3 and X4 are required.

Therefore, for a user who is a GSM system-based system and roams to a CDMA mobile IP system, the IIF can present an HA interface to the CDMA system and present an SGSN interface to the GSM system. A subset of the SGSN functionality is required, which includes an APN solution. The IIF acts as an endpoint for mobile IP and GTP tunnels through the packet routing function between the HA and SGSN functions.

4B is an exemplary call flow diagram 4010 showing mobile IPv4 operation in a CDMA2000 packet data foreign mode. This call flow example shows a roaming case in which a GPRS home subscriber operates the IPv4 [IS-835-C] in a CDMA2000 packet data field mode. In this example, the GPRS system does not support HA; therefore, the MS shares the secret with the IIF for action IP authentication. recognize. The GPRS system of the home dynamically assigns an IP address to the MS. All MS data traffic (from the beginning of the MS and the termination of the MS) passes through the IIF and the GPRS system of the home. The IIF receives the 3GPP2 account processing record from the visited CDMA2000 system and maps it to the 3GPP account processing record and forwards it to the local GPRS system via RADIUS.

The MS initiates SO 33 and establishes a PPP session with the PDSN/FA. (Step 1) Since omitting the IP address configuration option during PPP IPCP negotiation indicates that the MS wishes to use the Mobile IP, the PDSN/FA sends one or more Mobile IP Agent advertisements to the MS. The agency advertisement contains the FA transfer address and FA question (FAC). (Step 2)

The MS sends a mobile IP registration request to the PDSN/FA. The registration request may contain the following information: MS's NAI [RFC 2794] has this format: <user name>@<domain_name>, where the domain_name identifies the MS's native GPRS system. The MS-HA authenticator can be calculated based on the content of the registration request and the secret shared between the MS and the HA [RFC 2002]. The MS-AAA authenticator can be calculated based on the secret shared between the FAC and the MS and the home AAA server [RFC 3012]. If the MS uses a permanent HA, the HA address field can be set to a known value, or if the MS wishes to assign a new HA from the home network, the HA address field can be set to 0.0.0.0. The HA column can be set to 0.0.0.0 to request a new address assigned by the HA. The T bit can be set to one to request the PDSN/FA to establish a reverse tunnel to the HA of the MS. (Step 3)

The PDSN/FA generates a RADIUS access request that conveys the NAI of the MS, the FAC authenticator, the FAC, the HA address, etc. [IS-835]. Since the domain name of the NAI of the MS indicates a GPRS system, the PDSN/FA is via the CDMA2000 system. The AAA sends a RADIUS access request to the IIF. The IIF can amend this message in accordance with [3GPP TS 29.061]. (Step 4) If the authentication is successful, the AAA server responds with a RADIUS access accept. The message can be sent back to the PDSN via the IIF and the visited AAA. The IIF can correct 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 verifies the MS-HA authenticator in the action registration request. (Step 6)

If the authentication is successful, the IIF SGSN function establishes a GTP tunnel with the GGSN in the GPRS system, and requests an IP address from the GGSN. The IIF SGSN function derives an APN having the format: <network ID>.mnc<MNC>.mcc<MCC>.gprs[TS 23.003]. <Network ID> is the realm portion of the NAI of the MS and indicates which GGSN the MS wishes to access for the requested service. <MNC> and <MCC> are derived from IMSI (International Mobile Station Identity) of MS. The NAI and IMSI of the MS can be obtained from the RADIUS access request in step 4. The SGSN function uses the derived APN as the query name for querying the GPRS DNS server (not shown) and from it obtains a list of available GGSNs that can be used to support the requested service. The IIF SGSN function sends a Create PDP Context Request to the selected GGSN. The requested PDP address in the message is set to 0.0.0.0 to request a new IP address. (Step 7) The GGSN responds with a Create PDP Context Response, including the new IP address assigned to the MS. (Step 8) The IIF is used as the HA and the Mobile IP registration reply is sent to the MS via the PDSN/FA. The home address field in the Mobile IP registration reply can be set to the IP address assigned by the GGSN. (Step 9) The PDSN sends a RADIUS account processing request containing the 3GPP2 packet data account processing information [P.S0001-A V3.0] (open beginning). Since the domain name of the NAI of the MS indicates a GPRS system, the RADIU account processing request (beginning) is delivered to the home AAA in the GPRS system via the visited AAA and IIF. IIF can amend the message according to [3GPP TS 29.061]. (Step 10) The IIF acts as a RADIUS server and responds with a RADIUS account (start) to respond. (Step 11)

The bearer traffic flows through the IIF in both directions. For the packet originating from the MS, the IIF will send the packet received from the Mobile IP Reverse Tunnel to the GTP tunnel of the MS (identified by TEID). For packets that are terminated by the MS, the IIF delivers the packets received from the GTP tunnel to the HA to FA tunnel. IPsec can be used to protect the IP tunnel between the PDSN/FA and the IIF and the GTP tunnel between the IIF and the GGSN. (Step 12)

IIF/AAA requirements for the field model of CDMA2000 packet data using Mobile IP

The IIF requirements for processing RADIUS access requests received from the visited CDMA2000 packet data system will now be described.

IIF uncorrected proxy except for the Calling-Station-ID attribute, Called-Station-ID attribute, and Framed-Protocol attributes. IETF RADIUS attributes. The processing of these three attributes is described below. If the call base ID attribute in the received RADIUS access request contains an IMSI, the IIF copies the IMSI into the 3GPP-IMSI attribute [3GPP TS 29.061] and includes it in the RADIUS access specified for the MS's home GPRS system. Requested. The IIF does not include the Call Station ID attribute in the RADIUS Access Request sent to the Home AAA in the GPRS system. If received The call station ID attribute in the RADIUS access request contains MIN (Mobile Intelligent Network) or IRM (International Roaming Mobile Identification Number), and the IIF maps it to the IMSI of the MS used in the GPRS system of the home, and includes it in the designation. In the 3GPP-IMSI attribute of the RADIUS access request for the GPRS system of the home. The IIF does not include the Call Station ID attribute in the RADIUS Access Request issued to the Home AAA in the GPRS system.

The IIF will include the called station ID attribute in the RADIUS access request specified for the MS's home GPRS system. The value column of the called station ID attribute is set to APN (see Section 8.3.4). If the received RADIUS access request includes a frame protocol attribute, the IIF overrides the value to 7 [3GPP TS 29.061]. The IIF removes all 3GPP2 VSA (Virtual System Architecture) from the received RADIUS access request. The IIF is not required to include any 3GPP VSAs other than the 3GPP IMSI attributes in the transmitted RADIUS access request for the MS's home GPRS system.

The IIF requirements for handling RADIUS access acceptance for receiving a home GPRS system from the MS will now be described.

IIF proxies all IETF RADIUS attributes without modification. The IIF accepts all 3GPP VSAs from the received RADIUS access before transmitting the RADIUS access accept to the visited CDMA2000 packet data system.

If the policy of the GPRS system of the home cradle requires that the data communication traffic of the MS that is roaming passes through the IIF through the GPRS system of the home, and in the corresponding RADIUS access request previously received from the CDMA2000 packet data system visited, Including the HA address VSA, the IIF includes the reverse tunnel specification VSA in the RADIUS access acceptor designated for transmission to the visited CDMA2000 packet data system. The value column of the VSA is set to 1 to indicate that reverse tunneling is required.

The IIF requirements for handling RADIUS account processing request-accounting (Accounting-Request START) and account processing request-interval (Accounting-Request INTERIM) are the same as those for processing RADIUS access requests.

The IIF requirement for handling RADIUS account processing request stop (Accounting-Request STOP) is the same as the IIF requirement for handling RADIUS access requests with the following additional requirements: if the received RADIUS account processing request is stopped, the VSA will be continued. "No" (FALSE), and if the IIIF has not previously received an account processing request (start) from another PDSN with the same IP address (for the case of handover between PDSNs using mobile IP), then IIF A 3GPP-Session-Stop-Indicator VSA is inserted to indicate that the PDP session has expired.

CDMA2000 packet data field using simple IP

FIG. 5A is an exemplary block diagram 5000 of an external mode of CDMA2000 packet data using simple IP. This section describes a roaming case in which a GPRS home subscriber operates IPv4 or IPv6 in a CDMA2000 packet data field mode. Figure 5A also depicts the functionality and control interface provided by interface 30 or "IIF" in this situation. In this embodiment, the home system 10 can be a GPRS system in which a GPRS home subscriber roams to a CDMA2000 packet data system and uses mobile IPv4. The home system 10 includes a GSM home location register 124, a GGSN 126, and an AAA entity 128. The interviewed system 20 can be a CDMA2000 packet data system including an ANSI-41 visited location register 111, an AAA entity 116, and a home system 109.

The interface 30 or "IIF" includes an ANSI-41 home location register 131 coupled to the ANSI-41 visited location register 111 via the D interface 113; coupled to the GSM home location via the D interface 121. The GSM visited location register 133 of the memory 124; coupled to the SGSN 137 of the GGSN 126 via the Gp interface 127; coupled to the AAA entity 128 via the X4 interface 129 and coupled to the AAA via the X3 interface 117 The AAA entity 140 of the entity 116; and an LCS entity 139 coupled to the packet data service node/LAC entity 109 via the X2 interface 119. IIF provides both GSM VLR and ANSI-41 HLR emulation to allow user registration. This interconnection can be provided by the interface reference "D". IIF provides LNS and SGSN simulations to support bearer connectivity between the interviewed and home network via IIF. This interconnection can be provided by the interface reference "X2" and "Gn". The IIF provides AAA emulation to interact with the AAA of the visited network for L2TP authentication and 3GPP2 packet data account processing. IIF can also interact with the AAA of the home network for 3GPP packet data account processing. This interconnection can be provided by referring to "X3" and "X4" interfaces. The IIF/AAA requirements for the field model for CDMA2000 packet data using simple IP will be described in more detail below.

If the connected CDMA2000 packet data system does not need to bear connectivity between the GPRS system and the GPRS system, the X2 and Gp interfaces are not needed. In this case, both the start of the action and the data communication traffic terminated by the action are delivered to the Internet or from the Internet via the PDSN in the visited system. In order to interconnect the AAA messages between the IIF and the CDMA2000 AAA server and the GPRS AAA server, interface X3 and interface X4 are required.

Therefore, for a GSM system-based system and roaming to a CDMA For users of simple IP systems, the IIF can present an L2TP Network Server (LNS) interface to the CDMA system and present an SGSN interface to the GSM system. A subset of the SGSN functionality of the APN solution is required. The IIF can act as an endpoint for mobile L2TP and GTP tunnels through the routing function between the LNS and the SGSN.

FIG. 5B is an exemplary call flow diagram 5010 showing a simple IP operation in a CDMA2000 packet data foreign mode. This call flow example illustrates a roaming case in which a GPRS home subscriber operates a simple IP in a CDMA2000 packet data field mode. In this example, the MS shares a secret with the home AAA in the GPRS system for CHAP authentication. The GPRS system of the home dynamically assigns an IP address to the MS. All MS data traffic (MS initiated and terminated) passes through the IIF and the GPRS system. The IIF receives the 3GPP2 account processing record from the visited CDMA2000 system and maps it to the 3GPP account processing record and forwards it to the home GPRS system via RADIUS.

The MS starts the SO 33 and initiates a PPP LCP negotiation with the PDSN/LAC (Packet Data Serving Node/Layer 2 Tunneling Protocol Access Concentrator). CHAP can be negotiated as an agreement for PPP authentication. (Step 1) The PDSN/LAC sends a CHAP challenge to the MS. (Step 2) The MS responds with its NAI and the interrogation response calculated based on the challenge and the secret shared with the AAA in the GPRS system. The PDSN/LAC sends a RADIUS access request. Since the domain name of the NAI of the MS indicates a GPRS system, the RADIUS access request can be delivered by the visited AAA and the IIF, wherein the IIF proxyes the message to the AAA of the GPRS system. The IIF can correct the message according to [3GPP TS 29.061]. (Step 3) If the authentication is successful, the AAA will respond with a RADIUS access accept. This message can be sent back to the PDSN/LAC via the IIF and the AAA being interviewed. IIF will tunnel server endpoint The attribute is inserted into the RADIUS access accept. This attribute informs the PDSN/LAC to establish an L2TP tunnel with the IIF used as the LNS. The PDSN/LAC sends a CHAP successfully to notify the MS that the authentication is successful. (Step 4)

The PDSN/LAC establishes an L2TP tunnel/session with the IIF used as the LNS. During the establishment of the L2TP tunnel/session, the PDSN/LAC forwards the LCP information (exchanged between the MS and the PDSN/LAC) to the IIF. Prior to IPCP negotiation, the IIF LNS function may initiate a CHAP challenge (not shown) to authenticate the MS. (Step 5) The IIF SGSN function establishes a GTP tunnel with the GGSN in the GPRS system of the home, and can request an IP address from the GGSN. The IIF exports an APN with this format: <network ID>.mnc <MNC>. mcc <MCC>. gprs. <Network ID> is the realm part of the NAI of the MS and is used to indicate which GGSN the MS wishes to access for the requested service. <MNC> and <MCC> are derived from the IMSI of MS. The NAI and IMSI of the MS can be obtained from the RADIUS access request in step 3. The IIF SGSN function uses the derived APN as the query name to query the GPRS DNS server (not shown) and obtain a list of available GGSNs that can be used to support the requested service. The IIF SGSN function sends a Create PDP Context Request to the selected GGSN. The requested PDP address in the message is set to 0.0.0.0 to request a new IP address. (Step 6) The GGSN responds with a PDP context response, including the new IP address assigned to the MS. (Step 7)

This new IP address can be assigned to the MS during PPP IPCP negotiation between the IIF and the MS. (Step 8) The PDSN/FA sends a RADIUS Account Processing Request (Start) containing the 3GPP2 Packet Data Account Processing Information [IS-835]. The PDSN sends the account processing information [P.S0001-A V3.0] containing the 3GPP2 packet data. The RADIUS account processes the request (beginning). Since the domain name of the NAI of the MS indicates a GPRS system, the RADIUS account processing request (beginning) is delivered to the home AAA in the GPRS system via the visited AAA and IIF. The IIF can correct this message according to [3GPP TS 29.061]. (Step 9) The home AAA responds with a RADIUS account processing response (start), and the RADIUS account processing response is sent back to the PDSN via the IIF and the visited AAA. (Step 10) The bearer traffic flows through the IIF in both directions. For the packet originating from the MS, the IIF will deliver the L2TP tunnel/session packet from the MS to the GTP tunnel of the MS (identified by TEID). For a packet terminated by the MS, the IIF delivers the packet received from the GTP tunnel of the MS to the L2TP tunnel/session of the MS. IPsec can be used to protect the L2TP tunnel/session between the PDSN/LAC and the IIF and the GTP tunnel between the IIF and the GGSN. (Step 11)

IIF/AAA requirements for field mode of CDMA2000 packet data using simple IP

The IIF requirements for processing RADIUS access requests are the same as those described above for handling RADIUS access requests for the CDMA2000 packet data foreign mode for mobile IP.

The IIF requirements for handling RADIUS access acceptance are similar to the RADIUS access acceptance requirements for handling the CDMA2000 packet data foreign mode for mobile IP, but if the GPRS system policy requires the data of the MS being roamed The traffic flows through the IIF through the GPRS system, and the HA address VSA is not included in the corresponding RADIUS access request previously received from the visited CDMA2000 packet data system. The IIF will tunnel the server endpoint, tunnel type and tunnel media. Type attribute insertion specified for interview The RADIUS access received by the CDMA2000 packet data system is accepted. 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 account processing request start and account processing request cessation are the same as those for the RADIUS account processing request start and account processing request traversal described above for handling the CDMA2000 packet data foreign mode for mobile IP.

The IIF requirement for processing RADIUS account processing request termination is substantially the same as the RADIUS account processing request termination request for handling the CDMA2000 packet data foreign mode for mobile IP, however, if the received RADIUS account processing request is terminated If the VSA is set to No (FALSE) and the IP technology VSA indicates a simple IP, the IIF inserts the 3GPP Session End Indicator VSA to indicate that the PDP session has expired.

Those skilled in the art will appreciate that information and signals can be represented by the use of any of a variety of different technologies and techniques. For example, the materials, instructions, commands, information, signals, bits, symbols, and wafers that may be mentioned throughout the above description may be voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof. To represent.

It will be appreciated by those skilled in the art that the various illustrative logic blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. Implementation. To clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are described above generally in terms of their functionality. These functions can be implemented as hardware or software depending on Specific application and design constraints imposed on the overall system. The above-described functions may be implemented by the skilled person in different ways for each particular application, but such implementation decisions should not be considered to result in a departure from the scope of the invention.

The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein can be implemented or carried out with the following items designed to perform the functions described herein: general purpose processor, digital signal processor (DSP), Special Application 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 these . A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other configuration.

The steps of the method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in the hardware, in a software module executed by the processor, or in a combination of the two. The software module can be in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, scratchpad, hard disk, removable disk, CD-ROM, or any known in the art. Other forms of storage media. An exemplary storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be part of the processor as a whole. The processor and the storage medium can be in an ASIC. The ASIC can be in a user terminal. Or, the processor and the storage medium can be used as The component is in the user terminal.

The previous description of the disclosed embodiments may be provided to enable any person skilled in the art to make or use the invention. A variety of modifications to the embodiments are readily apparent to those skilled in the art, and the general 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 herein, but may be accorded to the broadest scope of the principles and novel features disclosed herein.

AAA‧‧‧Access, Identification and Account Processing

ANSI-41 HLR‧‧‧ANSI-41 Home Location Register

ANSI-41 VLR‧‧‧ANSI-41 Visited Location Register

D, Gr, Gp, Gi, X1, X2, X3, X4‧‧ interface

FA‧‧ Foreign Agent

GGSN‧‧‧ gateway GPRS support node

HA‧‧‧Home agent

HLR‧‧‧Home location register

IIF‧‧‧Interconnect and interoperability functions

LAC‧‧‧ Link Access Control

LNS‧‧‧L2TP network server

MS‧‧‧ Mobile

SGSN‧‧‧Service GPRS Support Node

1 is a block diagram of a system including a home system, a visited system, and an interface entity for communicating between the home system and the visited system; FIG. 2A is a GPRS field mode using mobile IPv4. Figure 2B is a call flow diagram showing the mobile IPv4 operation in the GPRS foreign mode; Figure 3A is a block diagram of a GPRS foreign mode using a simple IP; Figure 3B is a call flow diagram showing the GPRS field Figure 4A is a block diagram of a field mode of CDMA2000 packet data using mobile IPv4; Figure 4B is a call flow diagram showing mobile IPv4 operation in a CDMA2000 packet data field mode; Figure 5A is a simple operation Block diagram of IP CDMA2000 packet data field mode; Figure 5B is a call flow diagram showing CDMA2000 packet data Simple IP operation of the ground mode.

(no component symbol description)

Claims (85)

A CDMA (Code Division Multiple Access) 2000 packet data using IPv4 (Internet Protocol version 4) is used by a user to roam from a CDMA2000 packet data system to a GPRS (Included GPRS Support Node) GPRS (General) The method of the Packet Radio Service system includes: coupling the home system to the visited system to enable communication between the home system and the visited system, wherein the native CDMA2000 packet data system includes an ANSI- 41 (American National Standards Institute) home location register, an AAA (authentication, authorization and accounting) entity and a home agent; and providing a different interface for the ANSI-41 home location register, Each of the AAA entity and the agent of the home. The method of claim 1, wherein the CDMA2000 packet data system comprises an ANSI-41 home location register, an AAA entity, and a home agent, the method further comprising: allowing a user to register by a first interface; The user is allowed to register by a second interface. The method of claim 1, further comprising: supporting bearer connectivity between the visited system and the home system, such that a foreign agent interface and an AAA interface are presented to the CDMA2000 packet data system by a third interface. ;and The bearer connectivity between the visited system and the home directory system is supported, so that a GGSN (Gateway GPRS Support Node) interface is presented to the visited system by a fourth interface. The method of claim 3, further comprising: providing an endpoint for a GTP (GPRS Tunneling Protocol) tunnel and an IP protocol (Internet Protocol) tunnel. The method of claim 4, further comprising: providing a packet routing function between the GGSN interface and a foreign agent interface. The method of claim 1, further comprising: providing an account processing function by interacting with a AAA of the home network for performing mobile IP foreign agent challenge authentication and 3GPP2 (3rd Generation Partnership Project 2) packet data account processing. A method for roaming a CDMA2000 packet data using a simple IP from a CDMA2000 packet data system to a visited GPRS system including an SGSN, comprising: coupling the home system to the visited system to enable Communicating between the home system and the visited system, wherein the native CDMA2000 packet data system includes an ANSI-41 home location register, an AAA entity, and an LNS (Layer 2 Tunneling Protocol Network Server); A different interface is used for each of the ANSI-41 home location register, the AAA entity, and the LNS. The method of claim 7, further comprising: Allowing a user to register via a first interface; and allowing the user to register via a second interface. The method of claim 8, further comprising: supporting bearer connectivity between the visited network and the home network by a third interface; and by presenting a GGSN interface to the visited system and The normal routing interface is presented to the CDMA2000 packet data system, so that a packet routing function is provided between the GGSN interface and the home system to support the bearer connection between the visited network and the home network through a fourth interface. Sex. The method of claim 9, further comprising: providing an endpoint for a GTP tunnel and an IPSec (IP Security) tunnel. The method of claim 10, further comprising: providing an account processing function by performing an L2TP (Layer 2 Tunneling Protocol) authentication and a 3GPP2 packet data account processing by interacting with the AAA of the home network through a fifth interface. A method for roaming a GPRS home system using a mobile IPv4 to a visited CDMA2000 packet data system, wherein the CDMA2000 packet data system includes an ANSI-41 visited location register, an AAA entity, and a Encapsulating a data service node/foreign agent, the method comprising: coupling the home directory system to the visited system to enable communication between the home directory system and the visited system, The GPRS system includes a GSM (Global System for Mobile Communication) home location register, a GGSN and an AAA entity; and provides a different interface for the GSM local location register, the GGSN and Each of the AAA entities. The method of claim 12, further comprising: presenting a home agent interface to the visited system; and presenting an SGSN interface to the home directory system to provide a package between the SGSN interface and the home agent interface Routing functionality to support bearer connectivity between the visited network and the home network. The method of claim 13, further comprising: providing an endpoint for a GTP tunnel and a mobile IP tunnel. The method of claim 13, further comprising: allowing a user to register. The method of claim 15, further comprising: interacting with the AAA of the visited network by a fifth interface to perform mobile IP authentication and 3GPP2 packet data account processing; and using a fourth interface with the home network AAA interaction for 3GPP packet data account processing. A method for roaming from a GPRS system to a visited CDMA2000 packet data system by using a GPRS home subscriber using a simple IP, wherein the CDMA2000 packet data system includes an ANSI-41 visited location register, an AAA entity, and a PDSN /LAC (Packet Data Serving Node/Layer 2 Tunneling Protocol Access Concentrator) The method includes: coupling the home system to the visited system to enable communication between the home system and the visited system, wherein the home GPRS system includes a GSM home location register, The GGSN and an AAA entity; and provide a different interface for each of the GSM local location register, the GGSN, and the AAA entity. The method of claim 17, further comprising: supporting bearer connectivity between the visited network and the home network by providing a packet routing function. The method of claim 18, further comprising: presenting an SGSN interface to the home system; presenting an L2TP network server (LNS) interface to the visited system; and an SGSN analog module and an LNS analog module This packet routing function is provided between groups. The method of claim 19, further comprising: providing an endpoint for a GTP tunnel and an active L2TP tunnel. The method of claim 20, further comprising: allowing a user to register. The method of claim 21, further comprising: interacting with the AAA entity of the visited network by means of a fifth interface for L2TP authentication and 3GPP2 packet data account processing; and using a sixth interface with the home network The AAA entity interacts for 3GPP packet data account processing. A method for communicating between a CDMA2000 packet data system and a visited GPRS system including an SGSN when a CDMA2000 packet data using mobile IPv4 is roamed to a visited GPRS system, including: a user is registered by a first interface, wherein the first interface couples a GSM local location register emulation module to the SGSN; and the user is allowed to register by the second interface, wherein the second interface is The ANSI-41 visited location register emulation module is coupled to an ANSI-41 home location register. The method of claim 23, wherein the native CDMA2000 packet data interface entity comprises an ANSI-41 home location register, an AAA entity, and a home agent. The method of claim 23, further comprising: coupling the home agent to a foreign agent simulation module via a third interface, wherein the foreign agent simulation module supports the bearer between the visited interface entity and the home interface entity The connectivity is such that a foreign agent interface and an AAA interface are presented to the CDMA2000 packet data interface entity by the third interface; and a GGSN analog module is coupled to the SGSN via a fourth interface, wherein the GGSN The simulation module supports bearer connectivity between the visited interface entity and the home interface entity, so that a GGSN interface is presented to the visited interface entity by the fourth interface. The method of claim 25, further comprising: Provide an endpoint for a GTP tunnel and a mobile IP tunnel. The method of claim 26, further comprising: providing a packet routing function between the GGSN interface and the foreign agent interface. The method of claim 23, further comprising: coupling an AAA analog module to the AAA entity via a fifth interface, wherein the AAA analog module performs an action IP foreign agent by interacting with a AAA of the home network Interrogation authentication and 3GPP2 packet data account processing to provide an account processing function. A method for communicating between a CDMA2000 packet data system and a visited GPRS system including an SGSN when a CDMA2000 packet data using a simple IP is roamed to a visited GPRS system, wherein the method is The CDMA2000 packet data system includes an ANSI-41 home location register, an AAA entity, and an LNS, the method comprising: coupling an ANSI-41 visited location register to the ANSI-41 home via a first interface a location register, wherein the ANSI-41 visited location register allows a user to register via the first interface; and couples a GSM home location register to the SGSN via a second interface, wherein the GSM The home location register allows a user to register with the second interface. The method of claim 29, further comprising: coupling a LAC (Layer 2 Tunneling Protocol Access Concentrator) analog module to the LNS via a third interface, where The LAC analog module supports the bearer connectivity between the visited network and the home network through the third interface; and couples a GGSN analog module to the SGSN via a fourth interface, where the GGSN simulates The module supports the bearer connectivity between the visited network and the home network through the fourth interface by: displaying a GGSN interface to the visited system; and presenting a normal routing interface to the The CDMA2000 packet data system provides a packet routing function between the GGSN interface and the home system. The method of claim 29, further comprising: providing an endpoint for a GTP tunnel and an IPSec tunnel. The method of claim 31, further comprising: coupling an AAA analog module to the AAA entity via a fifth interface, wherein the AAA simulation module provides an account processing function by using the fifth interface: Interact with the AAA of the home network for L2TP authentication and 3GPP2 packet data account processing. One such that when a GPRS home subscriber using mobile IPv4 roams to an interviewed CDMA2000 packet data system including an ANSI-41 visited location register, an AAA entity, and a packet data service node/foreign agent, A method for communicating between a GSM home location register, a GGSN, and an AAA entity GPRS system and the visited CDMA2000 packet data system includes: coupling a home agent analog module via a first interface To the packet a data service node/foreign agent, wherein the home agent simulation module presents a home agent interface to the visited system; and couples an SGSN analog module to the GGSN via a second interface, wherein the SGSN analog module An SGSN interface is presented to the home directory system to support bearer connectivity between the visited network and the home network by providing a packet routing function between the SGSN interface and the home agent interface. The method of claim 33, further comprising: providing an endpoint for a GTP tunnel and a mobile IP tunnel. The method of claim 33, further comprising: coupling an ANSI-41 home location register emulation module to the ANSI-41 visited location register via a third interface; and placing a third interface via a third interface The GSM visited location register emulation module is coupled to the GSM home location register to allow a user to register. The method of claim 35, further comprising: coupling an AAA analog module to the AAA entity via a fourth interface and coupling the AAA entity to the AAA entity via a fifth interface, wherein the AAA analog module The fifth interface interacts with the AAA of the visited network to perform mobile IP authentication and 3GPP2 packet data account processing, and interacts with the AAA of the home network through the fourth interface to perform 3GPP packet data account processing. One that enables a GPRS home subscriber using a simple IP to roam to an ANSI-41 visited location register, an AAA entity, and a packet profile Method for communicating between the CDMA2000 packet data system including the GSM local location register, a GGSN and an AAA entity, and the visited CDMA2000 packet data system when the CDMA2000 packet data system is accessed by the serving node/LAC entity The SGSN analog module is coupled to the GGSN by a first interface, wherein the SGSN analog module presents an SGSN interface to the home system; and an LNS analog module is provided by a second interface. And coupled to the packet data service node/LAC entity, wherein the LNS analog module presents an L2TP network server (LNS) interface to the visited system, wherein the interface is in the SGSN analog module and the LNS analog module This packet routing function is provided between groups. The method of claim 37, wherein the bearer connectivity is supported between the visited network and the home network by providing a packet routing function. The method of claim 38, further comprising: providing an endpoint for a GTP tunnel and an active L2TP tunnel. The method of claim 38, further comprising: coupling an ANSI-41 home location register emulation module to the ANSI-41 visited location register via a third interface, wherein the ANSI-41 location is temporarily The memory emulation module allows a user to register; and couples a GSM visited location register emulation module to the GSM home location register via another third interface, wherein the GSM visited location register emulator The module allows the user to register. The method of claim 40, further comprising: An AAA analog module is coupled to the AAA entity via a fourth interface and coupled to the AAA entity via a fifth interface, wherein the AAA analog module is connected to the visited network by a fifth interface The AAA entity interacts for L2TP authentication and 3GPP2 packet data account processing, and interacts with the AAA entity of the home network through a sixth interface to perform 3GPP packet data account processing. A system for using mobile IPv4 CDMA2000 packet data to roam to a visited GPRS system including an SGSN, comprising: a CDMA2000 packet data system, comprising an ANSI-41 home location register, an AAA entity And a home agent; and an interface entity that couples the home directory system to the visited system to enable communication between the home directory system and the visited system, wherein the interface entity includes a different interface It is used for each of the ANSI-41 home location register, the AAA entity, and the home agent. The system of claim 42, wherein the CDMA2000 packet data system comprises an ANSI-41 home location register, an AAA entity, and a home agent, and wherein the interface entity further comprises: a GSM local location register emulation module a group coupled to the SGSN via a first interface and allowing a user to register via a first interface; and an ANSI-41 visited location register emulation module via a second The interface is coupled to the ANSI-41 home location register and allows a user to register via the second interface. The system of claim 42, wherein the interface entity further comprises: a foreign agent simulation module coupled to the home agent via a third interface, and supporting bearer connectivity between the visited system and the home system So that a foreign agent interface and an AAA interface are presented to the CDMA2000 packet data system by the third interface; and a GGSN analog module coupled to the SGSN via a fourth interface, and supporting the The bearer connectivity between the visited system and the home directory system enables a GGSN interface to be presented to the interviewed system by the fourth interface. The system of claim 44, wherein the interface entity acts as an endpoint for a GTP tunnel and a mobile IP tunnel. The system of claim 45, wherein the interface entity provides a packet routing function between the GGSN interface and the foreign agent interface. The system of claim 42, wherein the interface entity further comprises: an AAA analog module coupled to the AAA entity via a fifth interface, and interacting with a AAA of the home network to perform an action IP field Proxy-style authentication and 3GPP2 packet data account processing to provide an account processing function. A CDMA2000 packet data using a simple IP is a system for a user to roam to a visited GPRS system including an SGSN, comprising: a CDMA2000 packet data system, comprising: an ANSI-41 home location register, an AAA Entity and an LNS; and An interface entity that couples the home directory system to the visited system such that communication between the home directory system and the visited system is possible, wherein the interface entity includes a different interface than the other ANSI-41 home location register, the AAA entity, and each of the LNSs. The system of claim 48, wherein the interface entity further comprises: an ANSI-41 visited location register coupled to the ANSI-41 home location register via a first interface and allowing a user to borrow Registered by the first interface; and a GSM local location register coupled to the SGSN via a second interface and allowing a user to register via the second interface. The system of claim 49, wherein the interface entity further comprises: an LAC analog module coupled to the LNS via a third interface, and supporting the network between the visited network and the home network And a GGSN analog module coupled to the SGSN via a fourth interface, and presenting a GGSN interface to the visited system and presenting a normal routing interface to the SGSN The CDMA2000 packet data system provides a packet routing function between the GGSN interface and the home system to support bearer connectivity between the visited network and the home network through the fourth interface. The system of claim 50, wherein the interface acts as an endpoint for a GTP tunnel and an IPSec tunnel. The system of claim 51, wherein the interface further comprises: An AAA analog module coupled to the AAA entity via a fifth interface, and providing L2TP authentication and 3GPP2 packet data account processing by interacting with the AAA of the home network through the fifth interface Account processing features. A system for a CDMA2000 packet data system comprising a mobile IPv4 GPRS home subscriber roaming to an ANSI-41 visited location register, an AAA entity, and a packet data service node/foreign agent, comprising: The GPRS system includes a GSM local location register, a GGSN and an AAA entity; and an interface entity that couples the home system to the visited system, wherein the interface entity enables the home system to be The interviewed system communicates, wherein the interface entity includes a different interface for each of the GSM local location register, the GGSN, and the AAA entity. The system of claim 53, wherein the interface entity further comprises: a home agent simulation module coupled to the packet data service node/foreign agent via a first interface, and presenting a home agent interface to the recipient And an SGSN analog module coupled to the GGSN via a second interface, and displaying an SGSN interface to the home system to provide a connection between the SGSN interface and the home agent interface The packet routing function supports bearer connectivity between the visited network and the home network. The system of claim 54, wherein the interface entity acts as an endpoint for a GTP tunnel and a mobile IP tunnel. The system of claim 54, wherein the interface entity further comprises: an ANSI-41 local location register emulation module coupled to the ANSI-41 visited location register via a third interface; The GSM visited location register emulation module is coupled to the GSM home location register via a third interface to allow a user to register. The system of claim 56, wherein the interface entity further comprises: an AAA analog module coupled to the AAA entity via a fourth interface and coupled to the AAA entity via a fifth interface for borrowing The fifth interface interacts with the AAA of the visited network to perform mobile IP authentication and 3GPP2 packet data account processing, and interacts with the AAA of the home network through the fourth interface to perform 3GPP packet data account processing. A system in which a GPRS home subscriber using a simple IP roams to an CDMA2000 packet data system including an ANSI-41 visited location register, an AAA entity, and a PDSN/LAC entity, including: a GPRS system a GSM home location register, a GGSN, and an AAA entity; and an interface entity that couples the home system to the visited system, wherein the interface entity enables access to the home system and the interview Communicating between the systems, and wherein the interface entity includes a different interface for the GSM local location register, the GGSN, and the AAA entity By. The system of claim 58, wherein the interface entity supports bearer connectivity between the visited network and the home network by providing a packet routing function. The system of claim 59, wherein the interface entity further comprises: an SGSN analog module coupled to the GGSN by a first interface, and an SGSN interface is presented to the home system; and an LNS analog module The group is coupled to the packet data service node/LAC entity by a second interface, and presents an L2TP network server (LNS) interface to the visited system, wherein the interface is in the SGSN analog module The packet routing function is provided between the LNS analog module. The system of claim 60, wherein the interface entity acts as an endpoint for a GTP tunnel and an active L2TP tunnel. The system of claim 61, wherein the interface entity further comprises: an ANSI-41 home location register emulation module coupled to the ANSI-41 visited location register via a third interface, and allowing A user registration; and a GSM visited location register emulation module coupled to the GSM home location register via another third interface and allowing the user to register. The system of claim 62, wherein the interface entity further comprises: an AAA analog module coupled to the AAA entity via a fourth interface and coupled to the AAA entity via a fifth interface, Performing L2TP authentication and 3GPP2 packet data account processing by interacting with the AAA entity of the visited network through a fifth interface, and interacting with the AAA entity of the home network through a sixth interface to perform a 3GPP packet data account deal with. An interface entity that enables communication between a CDMA2000 packet data system and a visited GPRS system including an SGSN when a CDMA2000 packet data using mobile IPv4 is roamed to a visited GPRS system, where The CDMA2000 packet data system includes an ANSI-41 home location register, an AAA entity, and a home agent, and wherein the interface entity includes a different interface for the ANSI-41 home location register, Each of the AAA entity and the agent of the home. The interface entity of claim 64, wherein the interface entity further comprises: a GSM local location register emulation module coupled to the SGSN via a first interface, and allowing a user to register by a first interface And an ANSI-41 visited location register emulation module coupled to the ANSI-41 home location register via a second interface and allowing a user to register via the second interface. The interface entity of claim 64, wherein the interface entity further comprises: a foreign agent simulation module coupled to the home agent via a third interface, and supporting the interface between the visited interface entity and the home interface entity Carrying connectivity such that a foreign agent interface and an AAA interface are presented to the CDMA2000 packet data system by the third interface; and a GGSN analog module coupled to the SGSN via a fourth interface, and supporting bearer connectivity between the visited interface entity and the home interface entity, such that a GGSN interface is presented by the fourth interface Give the interviewed interface entity. The interface entity of claim 66, wherein the interface entity acts as an endpoint for a GTP tunnel and a mobile IP tunnel. The interface entity of claim 67, wherein the interface entity provides a packet routing function between the GGSN interface and the foreign agent interface. The interface entity of claim 64, wherein the interface entity further comprises: an AAA analog module coupled to the AAA entity via a fifth interface, and interacting with a AAA of the home network for action IP Foreign agent interrogation authentication and 3GPP2 packet data account processing to provide an account processing function. An interface entity that enables communication between a CDMA2000 packet data system and a visited GPRS system including an SGSN in a CDMA2000 packet data system that uses a simple IP to roam to a visited GPRS system, where The CDMA2000 packet data system includes an ANSI-41 home location register, an AAA entity, and an LNS, and wherein the interface entity includes a different interface for the ANSI-41 home location register, AAA entity and each of the LNS. The interface entity of claim 70, wherein the interface entity further comprises: an ANSI-41 visited location register coupled to the ANSI-41 home location register via a first interface and allowing a user With this The first interface is registered; and a GSM local location register is coupled to the SGSN via a second interface and allows a user to register by the second interface. The interface entity of claim 71, wherein the interface entity further comprises: an LAC analog module coupled to the LNS via a third interface, and supporting the network between the visited network and the home network The third interface is connected to the SGSN, and is coupled to the SGSN via a fourth interface, and presents a normal routing interface by presenting a GGSN interface to the visited system. The CDMA2000 packet data system provides a packet routing function between the GGSN interface and the home directory system to support bearer connectivity between the visited network and the home network through the fourth interface. The interface entity of claim 72, wherein the interface entity acts as an endpoint for a GTP tunnel and an IPSec tunnel. The interface entity of claim 73, wherein the interface entity further comprises: an AAA analog module coupled to the AAA entity via a fifth interface, and AAA through the fifth interface and the home network The interaction provides L2TP authentication and 3GPP2 packet data account processing to provide an account processing function. An interface entity that enables a GPRS home subscriber using mobile IPv4 to roam to an CDMA2000 packet data system that includes an ANSI-41 visited location register, an AAA entity, and a packet data service node/foreign agent Can be included in a GSM local location register, one The GGSN and an AAA entity's home GPRS system communicate with the visited CDMA2000 packet data system, wherein the interface entity includes a different interface for the GSM local location register, the GGSN, and the AAA Each of the entities. The interface entity of claim 75, wherein the interface entity further comprises: a home agent simulation module coupled to the packet data service node/foreign agent via a first interface, and presenting a home agent interface to the The SGSN analog module is coupled to the GGSN via a second interface, and an SGSN interface is presented to the home system to provide between the SGSN interface and the home agent interface. A packet routing function to support bearer connectivity between the visited network and the home network. The interface entity of claim 76, wherein the interface entity acts as an endpoint for a GTP tunnel and a mobile IP tunnel. The interface entity of claim 76, wherein the interface entity further comprises: an ANSI-41 local location register emulation module coupled to the ANSI-41 visited location register via a third interface; A GSM visited location register emulation module is coupled to the GSM home location register via a third interface to allow a user to register. The interface entity of claim 78, wherein the interface entity further comprises: an AAA analog module coupled to the AAA entity via a fourth interface and coupled to the AAA entity via a fifth interface for borrowing The fifth interface interacts with the AAA of the visited network to perform mobile IP authentication and 3GPP2 packet data account processing; and The third interface interacts with the AAA of the home network to perform 3GPP packet data account processing. An interface entity that enables a GPRS home subscriber using a simple IP to roam to an interviewed CDMA2000 packet data system that includes an ANSI-41 visited location register, an AAA entity, and a packet data service node/LAC entity And communicating with the CDMA2000 packet data system including a GSM local location register, a GGSN, and an AAA entity, wherein the interface entity includes a different interface, Each of the GSM local location register, the GGSN, and the AAA entity. For example, the interface entity of claim 80, wherein the interface entity supports bearer connectivity between the visited network and the home network by providing a packet routing function. The interface entity of claim 81, wherein the interface entity further comprises: an SGSN analog module coupled to the GGSN by a first interface, and an SGSN interface is presented to the home system; and an LNS simulation The module is coupled to the packet data service node/LAC entity by a second interface, and presents an L2TP network server (LNS) interface to the visited system, wherein the interface is in the SGSN analog mode The packet routing function is provided between the group and the LNS analog module. The interface entity of claim 82, wherein the interface entity acts as an endpoint for a GTP tunnel and an active L2TP tunnel. The interface entity of claim 83, wherein the interface entity further comprises: An ANSI-41 local location register emulation module coupled to the ANSI-41 visited location register via a third interface and allowing a user to register; and a GSM visited location register emulation A module coupled to the GSM home location register via another third interface and allowing the user to register. The interface entity of claim 84, wherein the interface entity further comprises: an AAA analog module coupled to the AAA entity via a fourth interface and coupled to the AAA entity via a fifth interface for borrowing A fifth interface interacts with the AAA entity of the visited network for L2TP authentication and 3GPP2 packet data account processing; and interacts with the AAA entity of the home network through a sixth interface to perform 3GPP packet data account processing .