WO2008115520A1 - Ip mobility mechanism selection for terminals - Google Patents

Ip mobility mechanism selection for terminals Download PDF

Info

Publication number
WO2008115520A1
WO2008115520A1 PCT/US2008/003607 US2008003607W WO2008115520A1 WO 2008115520 A1 WO2008115520 A1 WO 2008115520A1 US 2008003607 W US2008003607 W US 2008003607W WO 2008115520 A1 WO2008115520 A1 WO 2008115520A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
protocols
tunnel
gateway
network device
Prior art date
Application number
PCT/US2008/003607
Other languages
French (fr)
Inventor
Stefano Faccin
Original Assignee
Marvell World Trade Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US89557007P priority Critical
Priority to US60/895,570 priority
Priority to US95757307P priority
Priority to US60/957,573 priority
Application filed by Marvell World Trade Ltd. filed Critical Marvell World Trade Ltd.
Publication of WO2008115520A1 publication Critical patent/WO2008115520A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/18Multi-protocol handler, e.g. single device capable of handling multiple protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/24Negotiation of communication capabilities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H04W80/045Network layer protocols, e.g. mobile IP [Internet Protocol] involving different protocol versions, e.g. MIPv4 and MIPv6

Abstract

A network device includes a transmit module that transmits an identification of C connectivity protocols and M mobility protocols for communicating with a remote network, where M and C are integers greater than zero. A receive module receives a reply indicating one of support and lack of support for the C connectivity protocols and the M mobility protocols from a gateway of the remote network. A control module communicates with the gateway via a first tunnel based on a supported one of the C connectivity protocols and communicates with the remote network via a second tunnel based on a supported one of the M mobility protocols when the network device roams between a plurality of local networks.

Description

IP MOBILITY MECHANISM SELECTION FOR TERMINALS

CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims the benefit of U.S. Provisional Application No. 60/957,573, filed on August 23, 2007 and U.S. Provisional Application No. 60/895,570, filed on March 19, 2007. The disclosures of the above applications are incorporated herein by reference in their entirety.

FIELD

[0002] The present disclosure relates to communication systems, and more particularly to selecting protocols for managing connectivity and mobility of network devices relative to remote networks.

BACKGROUND

[0003] The background description provided herein is for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent the work is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0004] Referring now to FIG. 1 , a user equipment (UE) 10 (e.g., a mobile network device) may communicate with an access point (AP) 12 in a wireless local area network (WLAN) 14. The UE 10 may access the Internet 16 via the WLAN 14. Additionally, the UE 10 may communicate with a 3rd Generation Partnership Project (3GPP™) network (hereinafter remote network) 18. The remote network 18 may comprise a packet data gateway (PDG) 20 and a remote server (also called a home subscriber server (HSS)) 21. Specifically, the UE 10 may communicate with the remote network 18 via the PDG 20. The

UE 10 may communicate with the PDG 20 via an internet protocol (IP) security tunnel 22 (also referred to herein in as IPsec tunnel 22 or connectivity tunnel 22).

[0005] The WLAN 14 may comply with one or more I. E. E. E. standards - e.g., 802.11 , 802.11 a, 802.11 b, 802.11 g, 802.1 1 h, 802.1 1 n, 802.16, and 802.20, which are incorporated herein by reference in their entirety. The remote network 18 may comply with Technical Specification (TS) 23.234 V.7.4.0 (2006- 12) "3GPP system to Wireless Local Area Network (WLAN) interworking; System description (Release 7)" and TS 33.234 V.7.4.0 (2007-03) "3G security; Wireless Local Area Network (WLAN) interworking security (Release 7)," which are incorporated herein by reference in their entirety.

[0006] The UE 10 may gain IP connectivity by connecting to the WLAN 14 and obtaining a local IP address from the WLAN 14. When the WLAN 14 is a primary local network that the UE 10 communicates with, the WLAN 14 can be referred to as a home network, and the local IP address is called a home address of the UE 10. The WLAN 14 may include a router called a home agent (HA) 15 that stores the home address of the UE 10.

[0007] The connectivity between the UE 10 and the PDG 20 may be set up using an Internet Key Exchange protocol version 2 (IKEv2). The IKEv2 protocol described in Request for Comments (RFC) 4306 is incorporated herein by reference in its entirety. The UE 10 receives a remote IP address (also called a care-of address or CoA) from the PDG 20. The CoA is used to establish the connectivity between the UE 10 and the PDG 20. The remote network 18 uses the CoA of the UE 10 to communicate with the UE 10. The UE 10 may register the CoA with the HA 15. The HA 15 associates or binds the CoA to the home address of the UE 10. When the HA 15 receives packets addressed to the CoA, the HA 15 delivers the packets to the UE 10 via the home address.

[0008] Referring now to FIG. 2, the UE 10 may access the remote network 18 via networks other than the WLAN 14. For example, the UE 10 may access the remote network 18 via a cellular network 26 or a Worldwide Interoperability for Microwave Access (WiMAX) network 28 instead of the WLAN 14. The remote network 18 may comprise a System Architecture Evolution (SAE) gateway 24 for communicating with the other networks.

[0009] The UE 10 may move or roam between the WLAN 14, the cellular network 26, and the WiMAX network 28 without losing connection to the remote network 18. Specifically, when the UE 10 moves from the WLAN 14 to the cellular network 26, IP traffic flows between the SAE gateway 24 and the cellular network 26 instead of flowing between the SAE gateway 24 and the PDG 20. On the other hand, when the UE 10 moves from the WLAN 14 to the WiMAX network 28, the IP traffic flows between the SAE gateway 24 and the WiMAX network 28 instead of flowing between the SAE gateway 24 and the PDG 20.

[0010] When the UE 10 accesses the remote network 18 while roaming between local networks, a mobility tunnel is used to manage mobility of the UE 10 between the local networks and to maintain connectivity of the UE 10 to the remote network 18. When the UE 10 switches from one local network to another, a UE-based system or a network-based system is used to establish the connectivity tunnel (i.e., the IPsec tunnel) 22 and the mobility tunnel. [0011] The UE-based system utilizes a Client Mobile Internet Protocol

MIP (CMIP). The CMIP is also called a host-based MIP. Version 4 of the CMIP (MIPv4) described in RFC 3344 and version 6 of the CMIP (MIPv6) described in RFC 3775 are incorporated herein by reference in their entirety.

[0012] On the other hand, the network-based system utilizes a Proxy MIP (PMIP). Version 4 of the PMIP described in an Internet-Draft titled "Mobility Management using Proxy Mobile IPv4" by Leung et al. is incorporated herein by reference in its entirety.

[0013] When CMIP (MIPv4) is used, the PDG 20 functions as a foreign agent (FA) and provides routing services to the UE 10 when the UE 10 is registered with the PDG 20. When CMIP (MIPv6) is used, the PDG 20 functions as an access router and provides routing services to the UE 10. When PMIP is used, the PDG 20 functions as a PMIP client (i.e., a PMIP agent (PMA)).

[0014] More specifically, when the UE 10 uses CMIP (MIPv4), the UE 10 receives the CoA when a link-layer connection is set up between the UE 10 and the PDG 20 using IKEv2. The PDG 20 does not send an agent solicitation/advertisement and does not initiate any mobility procedure. The UE 10 begins a MIPv4 registration procedure by sending a MIPv4 registration request to the PDG 20 that functions as the FA. The remaining MIPv4 procedure is completed without any additional steps performed by the PDG 20. [0015] Referring now to FIG. 3, when the UE 10 uses CMIP (MlPvβ), the UE 10 sends authentication information to the PDG 20 in step 1. The remote server 21 receives the authentication information from the PDG 20, verifies the authentication information, authorizes the UE 10 to access the remote network 18, and assigns the CoA to the UE 10. The PDG 20 sends the CoA to the UE 10 using IKEv2 in step 2. The IPsec tunnel 22 that connects the UE 10 to the PDG 20 is set up in step 3. [0016] Subsequently, the UE 10 initiates setting up of an IP mobility tunnel in step 4. IPsec Security associations (SAs), which are cooperative relationships formed by exchanging security information, are set up to protect bidirectional traffic between the UE 10 and the PGD 20. The HA 15 binds the CoA to the home address of the UE 10, and the UE 10 sends a binding update to the SAE gateway 24 in step 5. The UE 10 receives a binding acknowledgement from the SAE gateway 24 in step 6. The IP mobility tunnel, also called a CMIP tunnel, is set up between the UE 10 and the SAE gateway 24 in step 7. The CMIP tunnel begins at the UE 10 and ends at the SAE gateway 24. [0017] Referring now to FIG. 4, when PMIP is used, the PDG 20 functions as the PMA, registers the location of the UE 10, and maintains connectivity with the UE 10. The link-layer connectivity is set up between the UE 10 and the PDG 20 using IKEv2 in step 1. The UE 10 sends authentication information to the PDG 20. The remote server 21 receives the authentication information from the PDG 20, verifies the authentication information, authorizes the UE 10 to access the remote network 18, and assigns the CoA to the UE 10.

[0018] Before the IPsec tunnel 22 is set up between the UE 10 and the PDG 20, the PDG 20 initiates a PMIP registration procedure by sending a proxy binding update to the SAE gateway 24, which is also a HA of the remote network 18, in step 2. The PDG 20 receives a proxy binding acknowledgement from the SAE gateway 24 in step 3. The IPsec tunnel 22 that connects the UE 10 to the remote network 18 is set up between the UE 10 and the PDG 20 in step 4. Thereafter, the PDG 20 sends the CoA to the UE 10 using IKEv2 in step 5. The IP mobility tunnel, also called a PMIP tunnel, is set up between the PDG 20 (i.e., the PMA) and the SAE gateway 24 in step 6. SUMMARY

[0019] A network device includes a transmit module that transmits an identification of C connectivity protocols and M mobility protocols for communicating with a remote network, where M and C are integers greater than zero. A receive module receives a reply indicating one of support and lack of support for the C connectivity protocols and the M mobility protocols from a gateway of the remote network. A control module communicates with the gateway via a first tunnel based on a supported one of the C connectivity protocols and communicates with the remote network via a second tunnel based on a supported one of the M mobility protocols when the network device roams between a plurality of local networks.

[0020] In other features, the remote network includes a 3rd Generation Partnership Project network. The plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network. The C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP).

[0021] In other features, when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the remote network.

[0022] In other features, when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network.

[0023] In other features, when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network.

[0024] In other features, when the network device roams from a first network of the plurality of local networks to a second network of the plurality of local networks, a home agent of the remote network switches the second tunnel from the first network to the second network. The transmit module transmits the selection and the receive module receives the reply via Internet Key Exchange (IKE) signals.

[0025] A gateway of a secured network includes a transmit module that transmits a first descriptor that C connectivity protocols and M mobility protocols supported by the gateway, wherein M and C are integers greater than zero. A receive module receives a second descriptor from a network device that indicates a selected one of C connectivity protocols and a selected one of the M mobility protocols selected by the network device. A control module communicates with the network device via a first tunnel based on the selected one of the C connectivity protocols. The network device communicates with the secured network via a second tunnel based on the selected one of the M mobility protocols when the network device roams between a plurality of local networks.

[0026] In other features, the secured network includes a 3rd Generation Partnership Project network. The plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network. The C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP). [0027] In other features, when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the secured network. [0028] In other features, when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.

[0029] In other features, when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.

[0030] In other features, when the network device roams from a first network of the plurality of local networks to a second network of the plurality of local networks, a home agent of the secured network switches the second tunnel from the first network to the second network.

[0031] In other features, the transmit module transmits the first descriptor and the receive module receives the second descriptor via Internet Key Exchange (IKE) signals.

[0032] A method for operating a network device includes transmitting an identification of C connectivity protocols and M mobility protocols for communicating with a remote network, where M and C are integers greater than zero; receiving a reply indicating one of support and lack of support for the C connectivity protocols and the M mobility protocols from a gateway of the remote network; communicating with the gateway via a first tunnel based on a supported one of the C connectivity protocols; and communicating with the remote network via a second tunnel based on a supported one of the M mobility protocols when the network device roams between a plurality of local networks. [0033] In other features, the remote network includes a 3rd Generation

Partnership Project network, and wherein the plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network. The C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP).

[0034] In other features, when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the remote network.

[0035] In other features, when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network.

[0036] In other features, when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network. [0037] In other features, the method includes switching the second tunnel from a first network of the plurality of local networks to a second network of the plurality of local networks when the network device roams from the first network to the second network. The method includes transmitting the selection and receiving the reply via Internet Key Exchange (IKE) signals. [0038] A method for operating a gateway of a secured network includes transmitting a first descriptor of C connectivity protocols and M mobility protocols supported by the gateway, wherein M and C are integers greater than zero; receiving a second descriptor from a network device that indicates a selected one of C connectivity protocols and a selected one of the M mobility protocols selected by the network device; communicating with the network device via a first tunnel based on the selected one of the C connectivity protocols; and communicating with the secured network via a second tunnel based on the selected one of the M mobility protocols when the network device roams between a plurality of local networks. [0039] In other features, the secured network includes a 3rd

Generation Partnership Project network, and wherein the plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network. The C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP). [0040] In other features, when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the secured network. [0041] In other features, when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network. [0042] In other features, when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.

[0043] In other features, the method includes switching the second tunnel from a first network of the plurality of local networks to a second network of the plurality of local networks when the network device roams from the first network to the second network. The method includes transmitting the selection and receiving the reply via Internet Key Exchange (IKE) signals.

[0044] In still other features, the systems and methods described above are implemented by a computer program executed by one or more processors. The computer program can reside on a computer readable medium such as but not limited to memory, non-volatile data storage and/or other suitable tangible storage mediums.

[0045] A network device includes transmit means for transmitting an identification of C connectivity protocols and M mobility protocols for communicating with a remote network, where M and C are integers greater than zero; receive means for receiving a reply indicating one of support and lack of support for the C connectivity protocols and the M mobility protocols from a gateway of the remote network; and control means for communicating with the gateway via a first tunnel based on a supported one of the C connectivity protocols and for communicating with the remote network via a second tunnel based on a supported one of the M mobility protocols when the network device roams between a plurality of local networks.

[0046] In other features, the remote network includes a 3rd Generation Partnership Project network, and wherein the plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network. The C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP). [0047] In other features, when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the remote network. [0048] In other features, when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network. [0049] In other features, when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network.

[0050] In other features, when the network device roams from a first network of the plurality of local networks to a second network of the plurality of local networks, a home agent of the remote network switches the second tunnel from the first network to the second network.

[0051] In other features, the transmit means transmits the selection and the receive means receives the reply via Internet Key Exchange (IKE) signals.

[0052] A gateway of a secured network includes transmit means for transmitting a first descriptor that C connectivity protocols and M mobility protocols supported by the gateway, wherein M and C are integers greater than zero; receive means for receiving a second descriptor from a network device that indicates a selected one of C connectivity protocols and a selected one of the M mobility protocols selected by the network device; and control means for communicating with the network device via a first tunnel based on the selected one of the C connectivity protocols, wherein the network device communicates with the secured network via a second tunnel based on the selected one of the M mobility protocols when the network device roams between a plurality of local networks.

[0053] In other features, the secured network includes a 3rd Generation Partnership Project network, and wherein the plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network. The C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP).

[0054] In other features, when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the secured network.

[0055] In other features, when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.

[0056] In other features, when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.

[0057] In other features, when the network device roams from a first network of the plurality of local networks to a second network of the plurality of local networks, a home agent of the secured network switches the second tunnel from the first network to the second network.

[0058] In other features, the transmit means transmits the first descriptor and the receive means receives the second descriptor via Internet Key Exchange (IKE) signals.

[0059] Further areas of applicability of the present disclosure will become apparent from the detailed description and the drawings. It should be understood that the detailed description and specific examples are intended for purposes of illustration only and are not intended to limit the scope of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The present disclosure will become more fully understood from the detailed description and the accompanying drawings, wherein:

[0061] FIG. 1 is a functional block diagram of an exemplary network system according to the prior art;

[0062] FIG. 2 is a functional block diagram of an exemplary network system according to the prior art;

[0063] FIG. 3 is a schematic showing communication between a remote network and a network device of a local network according to the prior art; [0064] FIG. 4 is a schematic showing communication between a remote network and a network device of a local network according to the prior art;

[0065] FIG. 5 is a functional block diagram of a user equipment (UE) that communicates with a gateway of a remote network according to the present disclosure;

[0066] FIG. 6 is a functional block diagram of a gateway of a remote network that communicates with a UE according to the present disclosure;

[0067] FIG. 7 is a flowchart of a method for exchanging information about protocols between a UE and a gateway of a remote network according to the present disclosure;

[0068] FIG. 8A is a functional block diagram of a high definition television;

[0069] FIG. 8B is a functional block diagram of a vehicle control system;

[0070] FIG. 8C is a functional block diagram of a cellular phone;

[0071] FIG. 8D is a functional block diagram of a set top box; and

[0072] FIG. 8E is a functional block diagram of a mobile device.

DETAILED DESCRIPTION [0073] The following description is merely exemplary in nature and is in no way intended to limit the disclosure, its application, or uses. For purposes of clarity, the same reference numbers will be used in the drawings to identify similar elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A or B or C), using a non-exclusive logical or. It should be understood that steps within a method may be executed in different order without altering the principles of the present disclosure.

[0074] As used herein, the term module refers to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality. [0075] Occasionally, the user equipment (UE) 10 may be capable of using Client Mobile Internet Protocol (CMIP) to set up the mobility tunnel. The packet data gateway (PDG) 20, however, may use Proxy MIP (PMIP). Since

PMIP begins before the IP security (IPsec) tunnel 22 is set up, the UE 10 cannot inform the PDG 20 that the UE 10 can use CMIP. Additionally, the PDG 20 cannot determine whether to function as the foreign agent (FA), the access router, or the Proxy Mobile Agent (PMA) when the UE 10 cannot inform the PDG

20 whether the UE 10 may use CMIP and whether the CMIP is MIPv4 or MIPv6.

[0076] Referring now FIGs. 5 and 6, a UE 50 and a PDG 70 may exchange information about the protocols that may be supported and/or selected by the UE 50 and the PDG 70. Based on the information, the UE 50 and/or the PDG 70 may select CMIP and/or PMIP for connecting the UE 50 to the PDG 70 and for managing the mobility of the UE 50 when the UE 50 roams from one local network to another. [0077] In one implementation, the UE 50 and the PDG 70 exchange the information using the Internet Exchange Key protocol (IKEv2) before the IPsec tunnel 22 is set up between the UE 50 and the PDG 70. The information may be exchanged via IKE payloads (groups of bits) transmitted in IKEv2 signals. The UE 50 or the PDG 70 may initiate the information exchange. For example, the UE 50 can initiate the information exchange when the UE 50 is not configured by a subscriber that controls the remote network 18, and the capabilities of the UE 50 are unknown to the PDG 70.

[0078] Before a detailed description is presented, a brief description of IKEv2 signals and payloads is presented. Typically, an IKE communication comprises pairs of IKE messages or IKE signals. Each pair includes a request followed by a response and is called an exchange. The IKE communication begins with IKE_SA_INIT and IKE_AUTH exchanges. The IKE_SA_INIT exchange is a first request/response pair of the IKE communication, wherein two devices (e.g., the UE 50 and the PDG 70) negotiate security parameters. The IKE_AUTH exchange is a second request/response pair of the IKE communication, wherein the two devices exchange identities and set up IPsec security associations (SAs). [0079] Each IKE message begins with an IKE header (HDR). The IKE header may be followed by one or more IKE payloads. Examples of payloads include Identification-Initiator (IDi), Identification-Responder (IDr), Authentication

(AUTH), and Configuration (CP). The payloads comprise a plurality of bits of information.

[0080] Some payloads include unused bits that are reserved for private use and that may be used for custom purposes. The unused bits may be used to indicate protocol capabilities and preferences that the devices may use for network connectivity and mobility. For example, the devices may use a descriptor called an IP mobility management (MM) protocol selector comprising 8 of the unused bits of a payload. Of the 8 bits, a first bit may be used to indicate support for CMIP. A second bit may be used to indicate that the CMIP is MIPv4. A third bit may be used to indicate that the CMIP is MIPvθ. A fourth bit may be used to indicate support for PMIP. Bits 5-8 may be reserved for future use.

[0081] In FIG. 5, the UE 50 may comprise an antenna 52, an analog front-end module 54, a transmit module 56, a receive module 58, and a control module 60. The analog front-end module 54 may transmit signals generated by the transmit module 56 via the antenna 52 and may output signals received from the antenna 52 to the receive module 58.

[0082] When the UE 50 initiates the information exchange, the control module 60 may generate the descriptor that includes an access point name (APN). The APN may identify a packet data network (PDN) (e.g., the WLAN 14) that the UE 50 selects as the local network. Additionally or alternatively, the descriptor may indicate an IP MM protocol (e.g., CMIP and/or PMIP) that the UE 50 prefers to use for connectivity and mobility when communicating with the remote network 18. The UE 50 may select CMIP or PMIP for both connectivity (e.g., to connect to the PDG 70) and mobility (e.g., for network handover). Alternatively, the UE 50 may select a different IP MM protocol for connectivity than for mobility. For example, the UE 50 may select PMIP for connectivity and CMIP for mobility. [0083] The control module 60 may include the descriptor in an IKEv2 configuration payload such as CFG_REQUEST. The transmit module 56 may transmit the payload via an IKE_SA_INIT request message. The PDG 70 may reply using an IKEv2 payload such as CFG_REPLY. The reply may include a confirmation that the PDG 70 supports the IP MM protocol(s) selected by the UE 50. Alternatively, the reply may include an error when the PDG 70 does not support the IP MM protocol(s) selected by the UE 50. The PDG 70 may transmit the payload CFG_REPLY via an IKE_AUTH response message.

[0084] When the IP MM protocol selected by the UE 50 (and supported by the PDG 70) for connectivity is CMIP, the control module 60 may set up the connectivity tunnel 22 between the UE 50 and the PDG 70 using CMIP. The PDG 70 may function as the FA or the access router when the CMIP is MIPv4 or MIPv6, respectively.

[0085] On the other hand, when the IP MM protocol selected by the UE 50 for connectivity is PMIP, the PDG 70 may set up the connectivity tunnel 22 between the UE 50 and the PDG 70 using PMIP. The PDG 70 may function as the PMA. The UE 50 may connect to the PDG 70 via the connectivity tunnel 22 set up between the UE 50 and the PDG 70.

[0086] Additionally, when the IP MM protocol selected by the UE 50 (and supported by the PDG 70) for mobility is CMIP, the control module 60 may set up the mobility tunnel between the UE 50 and the home agent (HA) of the remote network 18 (e.g., the SAE gateway 24). When the IP MM protocol selected by the UE 50 for mobility is PMIP, the PDG 70 may set up the mobility tunnel between the PDG 70 and the HA of the remote network 18. Alternatively, when the IP MM protocols selected by the UE 50 for connectivity and mobility are CMIP and PMIP, respectively, the control module 60 and the PDG 70 may set up the connectivity and mobility tunnels, respectively.

[0087] The UE 50 may communicate with the remote network 18 via the mobility tunnel when the UE 50 roams from one local network to another (e.g., from the WLAN 14 to the cellular network 26). The HA switches the mobility tunnel from one local network to another when the UE 50 roams from one local network to another. For example, the HA uses PMIP to switch the mobility tunnel from PDG 70 to another local network (e.g., the cellular network 26) when the UE 50 roams from the WLAN 14 to the other local network.

[0088] In Fig. 6, the PDG 70 may comprise an antenna 72, an analog front-end module 74, a transmit module 76, a receive module 78, and a control module 80. The analog front-end module 74 may transmit signals generated by the transmit module 76 via the antenna 72 and may output signals received from the antenna 72 to the receive module 78.

[0089] When the PDG 70 initiates the information exchange, the control module 80 may generate the descriptor that indicates the IP MM protocol or protocols supported by the PDG 70. The control module 80 may include the descriptor in an IKEv2 payload such as IDi and IDr. The transmit module 76 may transmit the payload via an IKE_SA_INIT response message. The UE 50 may select the IP MM protocol or protocols supported by the PDG 70. The UE 50 may indicate the selection in the descriptor in an IKEv2 configuration payload such as CFG_REQUEST.

[0090] The UE 50 may transmit the payload via an IKE_AUTH request message. The receive module 78 may receive the IKE_AUTH request message. The control module 80 may generate a reply to confirm the protocol selection of the UE 50 using the descriptor in an IKEv2 payload such as CFG_REPLY. The transmit module 76 may transmit the payload CFG_REPLY via the IKE_AUTH response message.

[0091] When the UE 50 receives the reply, the connectivity and mobility tunnels are set up depending on the IP MM protocols selected by the UE 50. For example, when the UE 50 selects CMIP as the IP MM protocol for connectivity and mobility, the UE 50 sets up the connectivity and mobility tunnels. When the UE 50 selects PMIP as the IP MM protocol for connectivity and managing mobility, the control module 80 sets up the connectivity and mobility tunnels. When the UE 50 selects CMIP and PMIP as the IP MM protocols for connectivity and mobility, respectively, the UE 50 and the control module 80 may set up the connectivity and mobility tunnels, respectively.

[0092] Referring now to FIG. 7, a method 100 for exchanging information about protocols between the UE 50 and the PDG 70 before forming the connectivity and mobile tunnels is shown. The method 100 begins at step 102. Whether the UE 50 initiates the information exchange is determined in step 104. If the result of step 104 is true, the control module 60 selects connectivity and/or mobility protocols (e.g., CMIP and/or PMIP) to communicate with the remote network 18 in step 106. The transmit module 56 transmits the information about the protocols selected by the UE 50 to the PDG 70 via an IKEv2 payload in step 108.

[0093] In step 110, the receive module 78 receives the information, and the control module 80 determines whether the PDG 70 supports the protocols selected by the UE 50. If the result of step 110 is true, the UE 50 and/or the PDG 70 set up the connectivity and/or the mobility tunnels in step 112 based on the protocols selected by the UE 50. If the result of step 110 is false or at the end of step 112, the method 100 ends in step 114.

[0094] If the result of step 104 is false, the method 100 performs step 116, wherein whether the PDG 70 initiates the information exchange is determined. If the result of step 1 16 false, the method 100 returns to step 104. If the result of step 116 is true, the transmit module 76 transmits information about the protocols supported by the PDG 70 to the UE 50 via an IKEv2 payload in step 118. [0095] The control module 80 determines in step 120 whether the UE

50 selected any of the protocol based on information received by the receive module 78, if any. If the UE 50 did not select any of the protocols, the PDG 70 sets up the connectivity and mobility tunnels using PMIP in step 122. If the UE 50 selects any of the protocols, the transmit module 56 transmits the information about the protocols selected by the UE 50 to the PDG 70 via an IKEv2 payload in step 124. The UE 50 receives a confirmation from the PDG 70 in step 126. The UE 50 and/or the PDG 70 set up the connectivity and/or the mobility tunnels in step 128 based on the protocols selected by the UE 50, and the method 100 ends in step 114. [0096] Referring now to FIGs. 8A-8E, various exemplary implementations incorporating the teachings of the present disclosure are shown. In FIG. 8A, the teachings of the disclosure can be implemented in a network interface 243 of a high definition television (HDTV) 237. The HDTV 237 includes an HDTV control module 238, a display 239, a power supply 240, memory 241 , a storage device 242, the network interface 243, and an external interface 245. If the network interface 243 includes a wireless local area network interface, an antenna (not shown) may be included.

[0097] The HDTV 237 can receive input signals from the network interface 243 and/or the external interface 245, which can send and receive data via cable, broadband Internet, and/or satellite. The HDTV control module 238 may process the input signals, including encoding, decoding, filtering, and/or formatting, and generate output signals. The output signals may be communicated to one or more of the display 239, memory 241 , the storage device 242, the network interface 243, and the external interface 245.

[0098] Memory 241 may include random access memory (RAM) and/or nonvolatile memory. Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states. The storage device 242 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD). The HDTV control module 238 communicates externally via the network interface 243 and/or the external interface 245. The power supply 240 provides power to the components of the HDTV 237.

[0099] In FIG. 8B, the teachings of the disclosure may be implemented in a network interface 252 of a vehicle 246. The vehicle 246 may include a vehicle control system 247, a power supply 248, memory 249, a storage device 250, and the network interface 252. If the network interface 252 includes a wireless local area network interface, an antenna (not shown) may be included. The vehicle control system 247 may be a powertrain control system, a body control system, an entertainment control system, an anti-lock braking system (ABS), a navigation system, a telematics system, a lane departure system, an adaptive cruise control system, etc.

[0100] The vehicle control system 247 may communicate with one or more sensors 254 and generate one or more output signals 256. The sensors 254 may include temperature sensors, acceleration sensors, pressure sensors, rotational sensors, airflow sensors, etc. The output signals 256 may control engine operating parameters, transmission operating parameters, suspension parameters, braking parameters, etc. [0101 ] The power supply 248 provides power to the components of the vehicle 246. The vehicle control system 247 may store data in memory 249 and/or the storage device 250. Memory 249 may include random access memory (RAM) and/or nonvolatile memory. Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states. The storage device 250 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD). The vehicle control system 247 may communicate externally using the network interface 252. [0102] In FIG. 8C, the teachings of the disclosure can be implemented in a network interface 268 of a cellular phone 258. The cellular phone 258 includes a phone control module 260, a power supply 262, memory 264, a storage device 266, and a cellular network interface 267. The cellular phone 258 may include the network interface 268, a microphone 270, an audio output 272 such as a speaker and/or output jack, a display 274, and a user input device 276 such as a keypad and/or pointing device. If the network interface 268 includes a wireless local area network interface, an antenna (not shown) may be included.

[0103] The phone control module 260 may receive input signals from the cellular network interface 267, the network interface 268, the microphone 270, and/or the user input device 276. The phone control module 260 may process signals, including encoding, decoding, filtering, and/or formatting, and generate output signals. The output signals may be communicated to one or more of memory 264, the storage device 266, the cellular network interface 267, the network interface 268, and the audio output 272. [0104] Memory 264 may include random access memory (RAM) and/or nonvolatile memory. Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states. The storage device 266 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD). The power supply 262 provides power to the components of the cellular phone 258.

[0105] In FIG. 8D, the teachings of the disclosure can be implemented in a network interface 285 of a set top box 278. The set top box 278 includes a set top control module 280, a display 281 , a power supply 282, memory 283, a storage device 284, and the network interface 285. If the network interface 285 includes a wireless local area network interface, an antenna (not shown) may be included.

[0106] The set top control module 280 may receive input signals from the network interface 285 and an external interface 287, which can send and receive data via cable, broadband Internet, and/or satellite. The set top control module 280 may process signals, including encoding, decoding, filtering, and/or formatting, and generate output signals. The output signals may include audio and/or video signals in standard and/or high definition formats. The output signals may be communicated to the network interface 285 and/or to the display 281. The display 281 may include a television, a projector, and/or a monitor. [0107] The power supply 282 provides power to the components of the set top box 278. Memory 283 may include random access memory (RAM) and/or nonvolatile memory. Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states. The storage device 284 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD).

[0108] In FIG. 8E, the teachings of the disclosure can be implemented in a network interface 294 of a mobile device 289. The mobile device 289 may include a mobile device control module 290, a power supply 291 , memory 292, a storage device 293, the network interface 294, and an external interface 299. If the network interface 294 includes a wireless local area network interface, an antenna (not shown) may be included.

[0109] The mobile device control module 290 may receive input signals from the network interface 294 and/or the external interface 299. The external interface 299 may include USB, infrared, and/or Ethernet. The input signals may include compressed audio and/or video, and may be compliant with the MP3 format. Additionally, the mobile device control module 290 may receive input from a user input 296 such as a keypad, touchpad, or individual buttons. The mobile device control module 290 may process input signals, including encoding, decoding, filtering, and/or formatting, and generate output signals.

[0110] The mobile device control module 290 may output audio signals to an audio output 297 and video signals to a display 298. The audio output 297 may include a speaker and/or an output jack. The display 298 may present a graphical user interface, which may include menus, icons, etc. The power supply 291 provides power to the components of the mobile device 289. Memory 292 may include random access memory (RAM) and/or nonvolatile memory.

[0111] Nonvolatile memory may include any suitable type of semiconductor or solid-state memory, such as flash memory (including NAND and NOR flash memory), phase change memory, magnetic RAM, and multi-state memory, in which each memory cell has more than two states. The storage device 293 may include an optical storage drive, such as a DVD drive, and/or a hard disk drive (HDD). The mobile device may include a personal digital assistant, a media player, a laptop computer, a gaming console, or other mobile computing device.

[0112] Those skilled in the art can now appreciate from the foregoing description that the broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims.

Claims

CLAIMS What is claimed is:
1. A network device comprising: a transmit module that transmits an identification of C connectivity protocols and M mobility protocols for communicating with a remote network, where M and C are integers greater than zero; a receive module that receives a reply indicating one of support and lack of support for said C connectivity protocols and said M mobility protocols from a gateway of said remote network; and a control module that: communicates with said gateway via a first tunnel based on a supported one of said C connectivity protocols; and communicates with the remote network via a second tunnel based on a supported one of said M mobility protocols when the network device roams between a plurality of local networks.
2. The network device of claim 1 wherein the remote network includes a 3rd Generation Partnership Project network, and wherein said plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network.
3. The network device of claim 1 wherein the C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP).
4. The network device of claim 1 wherein when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the remote network.
5. The network device of claim 1 wherein when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network.
6. The network device of claim 1 wherein when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network.
7. The network device of claim 1 wherein when the network device roams from a first network of the plurality of local networks to a second network of the plurality of local networks, a home agent of the remote network switches the second tunnel from the first network to the second network.
8. The network device of claim 1 wherein the transmit module transmits the selection and the receive module receives the reply via Internet Key Exchange (IKE) signals.
9. A gateway of a secured network comprising: a transmit module that transmits a first descriptor that C connectivity protocols and M mobility protocols supported by the gateway, wherein M and C are integers greater than zero; a receive module that receives a second descriptor from a network device that indicates a selected one of C connectivity protocols and a selected one of the M mobility protocols selected by the network device; and a control module that communicates with said network device via a first tunnel based on the selected one of the C connectivity protocols, wherein the network device communicates with the secured network via a second tunnel based on the selected one of the M mobility protocols when the network device roams between a plurality of local networks.
10. The gateway of claim 9 wherein the secured network includes a 3rd
Generation Partnership Project network, and wherein the plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network.
1 1. The gateway of claim 9 wherein the C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP).
12. The gateway of claim 9 wherein when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the secured network.
13. The gateway of claim 9 wherein when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.
14. The gateway of claim 9 wherein when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.
15. The gateway of claim 9 wherein when the network device roams from a first network of the plurality of local networks to a second network of the plurality of local networks, a home agent of the secured network switches the second tunnel from the first network to the second network.
16. The gateway of claim 9 wherein the transmit module transmits the first descriptor and the receive module receives the second descriptor via Internet Key Exchange (IKE) signals.
17. A method for operating a network device, comprising: transmitting an identification of C connectivity protocols and M mobility protocols for communicating with a remote network, where M and C are integers greater than zero; receiving a reply indicating one of support and lack of support for said C connectivity protocols and said M mobility protocols from a gateway of said remote network; communicating with said gateway via a first tunnel based on a supported one of said C connectivity protocols; and communicating with the remote network via a second tunnel based on a supported one of said M mobility protocols when the network device roams between a plurality of local networks.
18. The method of claim 17 wherein the remote network includes a 3rd Generation Partnership Project network, and wherein said plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network.
19. The method of claim 17 wherein the C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP).
20. The method of claim 17 wherein when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the remote network.
21. The method of claim 17 wherein when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the C connectivity protocols and the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network.
22. The method of claim 17 wherein when a Client Mobile Internet Protocol (CMIP) implements the supported one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the supported one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the remote network.
23. The method of claim 17 further comprising switching the second tunnel from a first network of the plurality of local networks to a second network of the plurality of local networks when the network device roams from the first network to the second network.
24. The method of claim 17 further comprising transmitting the selection and receiving the reply via Internet Key Exchange (IKE) signals.
25. A method for operating a gateway of a secured network comprising: transmitting a first descriptor of C connectivity protocols and M mobility protocols supported by the gateway, wherein M and C are integers greater than zero; receiving a second descriptor from a network device that indicates a selected one of C connectivity protocols and a selected one of the M mobility protocols selected by the network device; communicating with said network device via a first tunnel based on the selected one of the C connectivity protocols; and communicating with the secured network via a second tunnel based on the selected one of the M mobility protocols when the network device roams between a plurality of local networks.
26. The method of claim 25 wherein the secured network includes a 3rd
Generation Partnership Project network, and wherein the plurality of local networks include a wireless local area network (WLAN), a cellular network, and a Worldwide Interoperability Microwave Access (WiMAX) network.
27. The method of claim 25 wherein the C connectivity protocols and the M mobility protocols include at least one of a Client Mobile Internet Protocol (CMIP) and a Proxy Mobile Internet Protocol (PMIP).
28. The method of claim 25 wherein when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the network device and a home agent of the secured network.
29. The method of claim 25 wherein when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the C connectivity protocols and the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.
30. The method of claim 25 wherein when a Client Mobile Internet Protocol (CMIP) implements the selected one of the C connectivity protocols and when a Proxy Mobile Internet Protocol (PMIP) implements the selected one of the M mobility protocols, the first tunnel is generated between the network device and the gateway, and the second tunnel is generated between the gateway and a home agent of the secured network.
31. The method of claim 25 further comprising switching the second tunnel from a first network of the plurality of local networks to a second network of the plurality of local networks when the network device roams from the first network to the second network.
32. The method of claim 25 further comprising transmitting the selection and receiving the reply via Internet Key Exchange (IKE) signals.
PCT/US2008/003607 2007-03-19 2008-03-19 Ip mobility mechanism selection for terminals WO2008115520A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US89557007P true 2007-03-19 2007-03-19
US60/895,570 2007-03-19
US95757307P true 2007-08-23 2007-08-23
US60/957,573 2007-08-23

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP20080726982 EP2130351A1 (en) 2007-03-19 2008-03-19 Ip mobility mechanism selection for terminals
JP2009554565A JP2010522480A (en) 2007-03-19 2008-03-19 Selection of IP mobility mechanism for multi-mode terminals with tunnel IP connectivity

Publications (1)

Publication Number Publication Date
WO2008115520A1 true WO2008115520A1 (en) 2008-09-25

Family

ID=39563628

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2008/003607 WO2008115520A1 (en) 2007-03-19 2008-03-19 Ip mobility mechanism selection for terminals

Country Status (4)

Country Link
EP (1) EP2130351A1 (en)
JP (1) JP2010522480A (en)
TW (1) TW200901706A (en)
WO (1) WO2008115520A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010530161A (en) * 2007-06-07 2010-09-02 クゥアルコム・インコーポレイテッドQualcomm Incorporated Mobility management mode selection in multiple access wireless networks

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050128956A1 (en) * 2003-08-05 2005-06-16 Hsu Raymond T. Packet data services using version and capability Information

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050128956A1 (en) * 2003-08-05 2005-06-16 Hsu Raymond T. Packet data services using version and capability Information

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
DAMIC D PREMEC B PATIL M SAHASRABUDHE NOKIA SIEMENS NETWORKS S KRISHNAN ERICSSON D: "Proxy Mobile IPv6 indication and discovery; draft-damic-netlmm-pmip6- ind-discover-03.txt" IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, no. 3, 25 February 2008 (2008-02-25), XP015052749 ISSN: 0000-0004 *
KRISHNAN ERICSSON S: "Client Initiated Selection of Proxy Mobility; draft-krishnan-netlmm-pmip-sel-00.txt" IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, 7 June 2007 (2007-06-07), XP015051890 ISSN: 0000-0004 *
YUANKUI ZHAO SHANGHAI HUAWEI TECHNOLOGY: "DHCP option for MIP type Decision; draft-zhao-dhc-miptype-00.txt" IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, 25 February 2006 (2006-02-25), XP015050627 ISSN: 0000-0004 *
YUANKUI ZHAO SHANGHAI HUAWEI TECHNOLOGY: "MIP type decision in netlmm workgroup; draft-zhao-netlmm-miptype-00.txt" IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, 25 February 2006 (2006-02-25), XP015050629 ISSN: 0000-0004 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2010530161A (en) * 2007-06-07 2010-09-02 クゥアルコム・インコーポレイテッドQualcomm Incorporated Mobility management mode selection in multiple access wireless networks
US8619668B2 (en) 2007-06-07 2013-12-31 Qualcomm Incorporated Mobility management mode selection in multiple access wireless networks

Also Published As

Publication number Publication date
JP2010522480A (en) 2010-07-01
TW200901706A (en) 2009-01-01
EP2130351A1 (en) 2009-12-09

Similar Documents

Publication Publication Date Title
JP5186603B2 (en) Method for enabling simultaneous use of a home network and a foreign network by a multihomed mobile node
EP2338264B1 (en) Optimization of handovers to untrusted non-3gpp networks
US8671209B2 (en) Mobile terminal management system, network device, and mobile terminal operation control method used for them
JP5118055B2 (en) Internet protocol tunneling over mobile networks
EP1933520A1 (en) Local mobility anchor relocation and route optimization during handover of a mobile node to another network area
CN1231079C (en) Method for indicating macro mobile object in access network and access system
US20180198672A1 (en) Methods For IP Mobility Management
US8345694B2 (en) Network address translation for tunnel mobility
US20060159088A1 (en) Network mobility
US20100189103A1 (en) Header Size Reduction of Data Packets
US8437345B2 (en) Terminal and communication system
EP1634422B1 (en) Method, system and apparatus to support hierarchical mobile ip services
US8134969B2 (en) IP layer-handoff using mobility domains and IP caching
JP5205468B2 (en) Continuity of route optimization during handover from network-based mobility to host-based mobility
RU2497297C2 (en) Method and device to provide opportunity of data exchange between cdma2000 and cprs networks
EP2244495B1 (en) Route optimazion of a data path between communicating nodes using a route optimization agent
US20100215019A1 (en) Detection of mobility functions implemented in a mobile node
US8688970B2 (en) Access-network to core-network trust relationship detection for a mobile node
EP2512094B1 (en) Dynamic assignment of home agent and home address in wireless communications
EP2384571B1 (en) Trustworthiness decision making for access authentication
CN101395934B (en) System and method for handover of an access terminal in a communication network
EP1575238A1 (en) IP mobility in mobile telecommunications system
JP2006527968A (en) Method, system and apparatus for supporting mobile IP version 6 service in a CDMA system
EP2174444B1 (en) Methods and apparatus for providing pmip key hierarchy in wireless communication networks
US7701937B2 (en) Method and apparatus for IP multicasting

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08726982

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2009554565

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2008726982

Country of ref document: EP

NENP Non-entry into the national phase in:

Ref country code: DE