Patent Application
20090207806
The invention relates to IP mobility, and in particular to arranging IP mobility multihoming.
Internet Protocols (IP) are the backbone of modern networking and supported in most of the current telecommunications devices. IP is adaptable and has been extended to provide additional functionality.
Nowadays terminal devices are highly mobile and can change their point of attachment to the Internet at any time, even during active network connections. Mobile IP protocols, defined for IP version 6 (IPv6) in IETF specification RFC3775 and for IP version 4 (IPv4) in RFC 3344, allow mobile nodes to change their access point to the Internet without changing their IP address. Mobile IP defines a system for routing data of a mobile node to the current location of the node. This is accomplished through the use of a Home Agent that monitors the permanent IP address and current location of the mobile node. The Home Agent allows the mobile node to have a permanent address that is translated by the Home Agent into the mobile node's current address.
The Mobile IP standards assume that the host device has only one so called home network through which the device is always logically reachable regardless of where it physically happens to be at any given time. A problem with the mobile device arises should it have more than one home network, when those networks should be reached simultaneously. In such a situation, mobile nodes would be allocated multiple addresses and would be multihomed. The Mobile IP standards as such cannot cope with this kind of situation.
A method, apparatuses, and a computer program product are now provided, which are characterized by what is stated in the independent claims. Some embodiments of the invention are described in the dependent claims.
According to an aspect of the invention, a plurality of IP mobility configuration parameter sets is accessed, each of the sets being associated with a destination network. One of the IP mobility configuration parameter sets is selected for an IP data connection, the selected IP mobility configuration parameter set being associated with a destination network of the IP data connection. An IP mobility protocol instance associated with the destination network is activated on the basis of the selected IP mobility configuration parameter set.
The invention and various embodiments of the invention provide several advantages, which will become apparent from the detailed description below. One advantage is that, amongst a plurality of IP mobility configuration parameter sets, one associated with the same destination network as the data connection being established may be selected. Further, it is possible to have a plurality of IP mobility protocol instances active simultaneously, each associated with a specific destination network.
Embodiments of the present invention are described below, by way of example only, with reference to the accompanying drawings, in which
The following embodiments are exemplary. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations, this does not necessarily mean that each such reference is to the same embodiment(s), or that the feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments.
An embodiment of the invention will be illustrated in the following with reference to the communications system in
A mobile node (MN) 10 may connect to various network resources via one or more access networks 20, 22, 24. For instance, the access network 20 could be a (wireless) local access network connected to the Internet and an Internet access gateway. Another example is a private access network 22, such as a wireless company LAN connected to a company intranet 50. A further example is a public access network 24, in one embodiment a cellular radio access network of a Public Land Mobile Network PLMN operator. For instance, the access network 24 may be a GSM/GPRS radio access network or a radio access network standardized by the Third Generation Partnership Project (3GPP) or connectable to a core network standardized by the 3GPP, which may also be referred to as a 3GPP access network or UMTS Radio Access Network (UTRAN) based on Wideband Code Division Multiple Access (WCDMA). The operator network 60 may thus be a GSM/GPRS core network or a core network standardized by the 3GPP, which may also be referred to as a 3GPP core network or UMTS core network, connected to the Internet. The MN 10 may be connected to one or more access networks 20, 22, 24 simultaneously and is capable of establishing connections to various resources of destination networks, such as a resource of the intranet 50, an Internet resource 70, or a resource of an operator network 60, even simultaneously.
The system comprises home agents (HA) 30, 32, 34 to hide the mobility of the MN 10 by transmitting packets to the home address of the MN to current care-of address of the MN obtained from the currently visited access network 20, 22, 24. In case of mobile IP version 4 (IPv4) a foreign agent would be provided in an access network or co-located in a terminal hosting the MN, but in mobile IP version 6 (MIPv6) no specific foreign agents are provided in access networks. A virtual private network (VPN) connection between the MN 10 and a VPN gateway 40 may be required for the MN 10 to connect the intranet 50 via an insecure network.
As can be seen, the MN 10 may have more than one home network. In some cases communications may be needed for the MN 10 via a plurality of home networks (and home agents 30, 32, 34) simultaneously, i.e. the mobile node may have a number of connections active simultaneously. For instance, one connection may be established to company intranet pages and another connection may be open to read e-mails from a private e-mail service by the internet operator, where these networks host an IP mobility service.
An improved IP mobility arrangement has now been developed in which a specific mobile IP protocol instance is established for and associated with a so-called destination network. A destination network may be represented by a destination network identifier identifying the destination IP network whose service the mobile node 10 is using or desires to use. The destination network may refer to a home network 50, 60 of the MN 10 including a home agent 32, 34 for the MN. The destination network may also refer to some other network for which an IP data connection is to be established, for instance generally the Internet. The present IP mobility arrangement is configured such that each mobile IP instance is valid only within the scope of one destination network. This enables running multiple mobile IP instances simultaneously. The mobile IP protocol instance is to be understood broadly to refer to any protocol instance or entity for IP communications facilitating mobility of a mobile node.
A plurality of IP mobility configuration parameter sets, each of the sets comprising a parameter for indicating a destination network, is stored in the storage 220 and retrieved by the manager 210. The manager 210 selects, for an IP data connection, one of the IP mobility configuration parameter sets amongst IP mobility configuration parameter sets associated with a destination network of the IP data connection. The manager 210 activates an IP mobility protocol instance on the basis of the selected IP mobility configuration parameter set. It is to be noted that the manager 210 could be a specific IP mobility controller only controlling IP mobility features.
Some further embodiments of features for the apparatus 200, and in particular for the connection manager 210, are illustrated below in connection with
The apparatus 200 may be any communications device capable of supporting IP address multihoming, such as the MN 10 roaming between and connected to a plurality of access networks 20, 22, 24. Examples of a communications device include a personal computer, an entertainment device such as a game console, a laptop, or a personal digital assistant with IP networking capability, an embedded computing device or a mobile station (mobile phone). In case of a mobile communications device comprising typically a plurality of transceivers for wireless communications, a wireless connection may be implemented with a wireless transceiver operating according to the GSM (Global System for Mobile Communications), WCDMA (Wideband Code Division Multiple Access), a network operating on non-licenced frequencies, such as WLAN (Wireless Local Area Network) or WiMAX, or any other suitable standard/non-standard wireless communication means.
Although the apparatus 200 has been depicted as one entity, different modules and memory may be implemented in one or more physical or logical entities. Although the modules are functionally separated in
The apparatus could be in a form of a chip unit or some other kind of hardware module for controlling a data processing device. Such hardware module comprises connecting means for connecting the data processing device mechanically and/or functionally. Thus, the hardware module may form part of the device and could be removable. Some examples of such hardware module are a sub-assembly or an accessory device. For instance, all or some of the modules in
The apparatus comprises not only prior art means, but also means for arranging destination network-specific IP mobility protocol instances. In particular, means may be provided for arranging at least some of the features illustrated in connection with
The apparatus may be implemented as an electronic digital computer, which may comprise memory, a central processing unit (CPU), and a system clock. The CPU may comprise a set of registers, an arithmetic logic unit, and a control unit. The control unit is controlled by a sequence of program instructions transferred to the CPU from the memory. The program instructions may be coded by a programming language, which may be a high-level programming language, such as C, Java, etc., or a low-level programming language, such as a machine language, or an assembler.
An embodiment provides a computer program embodied on a distribution medium, comprising program instructions which, when loaded into an electronic apparatus, constitute one or more of the modules in
The apparatus or the module 200 may also be implemented as one or more integrated circuits, such as application-specific integrated circuits ASIC. Other hardware embodiments are also feasible, such as a circuit built of separate logic components. A hybrid of these different implementations is also feasible.
If another application 302 activates another connection to another destination network with Mobile IP support, then either another instance of Mobile IP protocol implementation is started or a single Mobile IP implementation can handle multiple protocol instances by running them as separate entities, either way using a destination network as an identifier. A second IP mobility protocol instance 314 is assigned for a second IP data connection on the basis of an IP mobility configuration parameter set including an identifier of a second destination network (of the second IP data connection). These Mobile IP instances 312, 314 may be associated to different home agents, i.e. set up mobility bindings to different home networks. The instances 312, 314 are in one embodiment Mobile IPv4 or v6 instances. However, the present features are not limited to these protocols, but may be applied for any present or future protocol facilitating IP mobility, such as IKEv2/Mobike.
The IP data connections associated with different mobility protocol instances 312, 314 may be considered as separate layer 3 data flows. As illustrated in the embodiment of
For instance, the first protocol instance 312 may set up a mobility binding with the company intranet 50 home agent 34 for company intranet access purposes, whereas the second protocol instance 314 is establishes mobility binding with the home agent 32 in the PLMN operator's network 60. For instance, the user may wish to browse the company intranet 50 pages and also have a connection read some personal emails from a server in the Internet. The company intranet 50 may provide mobility services so that the user may switch seamlessly between the company's access network connection and a dedicated dial-up connection while continuing to surf the intranet. In this example the first IP mobility protocol instance 312 may update binding by submitting a new care of address, obtained from the cellular network 24, 60, to the home agent 34 in response to the MN 10 leaving coverage area of the WLAN access network 22 (and being connected to the cellular radio access network 24).
Another example is that in the Internet there can be a public Mobile IP service 30, which enables seamless handover from e.g. a GPRS connection to a public WLAN hotspot. With the present arrangement, both applications 240, 242 could utilize automatically the best available data bearer and roam seamlessly when another one becomes available or disappears.
In step 404 the IP mobility configuration parameter sets are accessed. In particular, the destination network identifiers stored as part of the parameter sets are reviewed and compared to the present destination network identifier determined in step 402. If in step 406 one or more matching network identifiers are found, in step 408 an IP mobility configuration parameter set with matching network ID is selected.
If there is more than one candidate parameter set with matching network ID, an algorithm may be executed in step 408 to select the most favorable access method/network to provide access at least partly to the destination network. The most appropriate IP mobility configuration is determined for the IP data connection amongst the plurality of IP mobility configuration parameter sets with matching destination network identifier on the basis of one or more selection criterion. An IP mobility configuration parameter set determined as the most appropriate IP mobility configuration is selected for the IP data connection.
If no matching network identifier was found in step 406, the destination network does not support or use Mobile IP 410. Hence, the Mobile IP related procedure of
In step 412 an IP mobility protocol instance associated with the destination network is activated on the basis of configuration parameters of the selected IP mobility configuration parameter set. In step 414 lower layer access, in accordance with the underlying lower layer (L2/L1) 320, 330 infrastructure, is activated for the IP mobility protocol instance for enabling access to the Mobile IP home network.
In one embodiment, a Mobile IPv4 or v6 protocol instance, specific to the destination network, is activated in step 412. Procedures for establishing a mobility binding are then started in accordance with the MIP4 or MIPv6 protocol and a care of address is acquired for the MN 10. A Mobile IP registration request (MIPv4) or binding update (MIPv6) is transmitted to a home agent indicated in the selected IP mobility configuration parameter set.
After establishing the IP mobility protocol instance associated with the destination network, IP packets to/from this destination network and associated with the care-of-address belong to the IP data flow controlled by the destination network specific mobility protocol instance.
In one embodiment, each IP mobility protocol instance 312, 314 operates its own Mobile IP session independently of other instances. Each IP mobility protocol instance may thus carry out Mobile IPv4 or v6 operations after steps 412 and 414 as required. For instance, Mobile IPv4 or v6 mobility binding updates are carried out with the home agent in accordance with changes in lower layer access service for the IP mobility protocol instance. Since these instances are independent of each other in the present Mobile IP implementation, changes related to one mobility instance do not affect the other. Hence, the mobile node 10 may roam between different access networks 20, 22, 24 and remove mobility binding to a first destination network without any effect to the mobility binding to a second destination network and the operation of the second IP mobility protocol instance.
The destination network identifier may be included as an additional parameter in existing mobile IP configuration parameter sets. In addition to home address and destination network ID, further configuration information for Mobile IP mobility are stored in the parameter sets. For instance, the Mobile IP parameter sets may include the following MIPv6 parameters:_HomeAddress, HomeAgentAddress, PrefixLength, EnableRouteOptimization, EnableIPSec, MNHMuthAlgorithm, MNHAEncryptAlgorithm, MNHASPIIndicator, MNHASPI, MNHASSData. Further information related to these parameters is available in the Mobile IPv6 specification RFC3775.
Each destination network where Mobile IP is supported may be pre-configured with its own Mobile IP configuration parameters, such as address of home agent HA. In one embodiment, specific destination network specific profiles or collections of IP mobility configuration parameters are stored in the storage 220.
In one embodiment, each of the IP mobility configuration parameter sets, such as a table including above Mobile IPv6 parameters, is directly or indirectly linked with destination network information. An IP mobility configuration parameter set linked with the destination network of an IP data connection being established is selected for establishing the IP mobility protocol instance for the IP data connection. In one embodiment a mapping table is used to provide the association between destination network identifiers and mobile IP configuration sets.
In one embodiment, each access point or network configuration in the mobile device 10, 200 is associated with a destination network. Hence, the same destination network identifier included in an IP mobility configuration parameter set may be included in an access point configuration specifying a set of parameters for establishing an access network (20, 22, 24) connection. When an application initiates a data connection to a destination network, for instance network 50, 60 or the Internet, the most appropriate access point configuration is selected to establish a L2 entity 322, 324 to serve to serve the data connection.
Additionally, if IP mobility is enabled in the destination network, i.e. an IP mobility configuration parameter set with matching destination network is found, the Mobile IP protocol implementation may register with the HA in the home network 50, 60 of the selected configuration parameter set as already indicated. Hence, according to an embodiment, the destination network is detected 402 on the basis of a selected one of a plurality of access point parameter sets.
In one embodiment, when selecting an access network for a Mobile IP connection, i.e. activating (414) or modifying an L2 320 connection, only the access networks and access point configurations associated with that particular destination networks are included in selection procedure. Such procedure can be carried out in connection with initial Mobile IP connection establishment (414) or in response to mobility of the MN 10 to a new access network to provide service continuity of the Mobile IP based connection to the destination network for the active IP mobility protocol instance 312, 314 associated with this destination network. Hence, the access point or network selection procedure in a roaming situation or in step 414 may be based on the destination network identifier associated with the IP mobility protocol instance. The selection can be based on one or more mobility policies that determine the priority order of access networks within the destination network.
It is to be noted that the access point and IP mobility parameter sets do not need to be separate, but there may be access configuration parameter sets comprising both access network and IP mobility related parameters, each configuration being associated with a destination network. Hence, the presently used term “IP mobility configuration parameter set” may refer to such access configuration parameter set.
In one embodiment a destination network parameter is included in one or more VPN profiles stored in the configuration storage 220. The steps as illustrated in
In addition to running multiple Mobile IP instances “side by side”, it is also possible to stack the protocol instances so that they are run layered on top of each other. An expected use case is such that the mobile device 10 takes a connection to company intranet, where Mobile IP is used. If there is no direct connection to the intranet, a VPN tunnel is established over the Internet. In the Internet, some public Mobile IP service is used. Here the relevant protocol stack looks like:
Mobile IP (Service hosted by the company intranet)
VPN (over Internet)
Mobile IP (Service hosted by another provider in the Internet)
The topmost Mobile IP instance handles the mobility within the company intranet. VPN provides a secure connection to the company intranet over the public Internet. The lower Mobile IP instance provides mobility for the Internet connection that the VPN is using.
The above situation may be addressed by the present destination network specific protocol instances, as illustrated above, together with the ability to stack protocols on top of each other, which can be done by using so called virtual access points, for instance. Virtual access points are like conventional access points, but instead of providing a direct network connection they refer to another underlying access point or access point group (Destination Network) for providing the connection. It is to be noted that even without protocol stacking, Mobile IP and VPN instances may utilize virtual access points.
In one embodiment at least some of the above features are applied in Symbian operating system communication infrastructure. However, it is to be noted that the implementation of the present features is not limited to any particular operating system.
In Symbian communications architecture, applications use networking API classes in DLLs (Dynamic Link Library) to access communications features. As with other application-level DLLs, the communication DLLs hide the details of the underlying architecture. A socket server is a process that implements and manages communication sockets. Applications act as clients to this server through the application-level communication DLLs. Protocol modules are used for handling the network data protocols. One of such protocol modules is the TCP/IP module. A connection agent is a DLL that is responsible for starting and stopping the communication connection. A connection agent will consult a communication database to determine how to establish the network connection. This database contains all the settings applicable to communication connections. Once a connection is chosen, the agent will extract all the applicable connection parameters from the database to start the connection by using lower level services. A connection to a network on a Symbian smartphone is known as an Internet Access Point (IAP).
A parameter called Network ID in Symbian IAP settings is in one embodiment used for identifying the destination network for IP mobility purposes by utilizing at least part of the features illustrated above. The network ID may be used in routing decisions, and applications may use it when setting up network connections. For example, a GPRS IAP may be determined as one connection resource (IAP in the Symbian terminology) for providing access to the Internet, i.e. the Internet is the target network. The GPRS IAP comprises not only the network identifier, but also the PDP context type (IPv4/IPv6), GPRS access point name and applied TCP/IP settings, for instance. For instance, the destination network and the IAP information may be indirectly linked to a Mobile IP table including appropriate Mobile IP parameters.
The Symbian operating system, starting from version 7.0, provides the possibility of using multiple simultaneous IP data connections, each with its own unique IP address. Multiple simultaneous OSI layer 2 datalink interfaces may be provided to server these IP data connections. Multiple IAPs can be active, and applications can specify which ones they will use. With the present features, it is now possible to run also multiple Mobile IP instances, each linked to a specific destination network, in Symbian communications architecture. The multiple mobile IP instances may be modelled as multiple virtual IP connections.
It will be obvious to a person skilled in the art that, as technology advances, the inventive concept can be implemented in various ways. The invention and its embodiments are not limited to the examples described above but may vary within the scope of the claims.
