US20100062760A1 - Data communications - Google Patents

Data communications Download PDF

Info

Publication number
US20100062760A1
US20100062760A1 US12/516,567 US51656707A US2010062760A1 US 20100062760 A1 US20100062760 A1 US 20100062760A1 US 51656707 A US51656707 A US 51656707A US 2010062760 A1 US2010062760 A1 US 2010062760A1
Authority
US
United States
Prior art keywords
mobile node
radio interface
radio
data traffic
node
Prior art date
Legal status (The legal status 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 status listed.)
Abandoned
Application number
US12/516,567
Other languages
English (en)
Inventor
Jean-Louis Fuccellaro
Stéphane Antoine
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Orange SA
Original Assignee
France Telecom SA
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
Application filed by France Telecom SA filed Critical France Telecom SA
Publication of US20100062760A1 publication Critical patent/US20100062760A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/04—Access restriction performed under specific conditions based on user or terminal location or mobility data, e.g. moving direction, speed
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates to a method of controlling a mobile node in a data communications network including a plurality of different radio access technologies, and a mobile node for use in such a data communications network.
  • GSM Global System for Mobiles
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications System
  • WLAN Wireless Local Area Network
  • WiFiTM Wireless Local Area Network
  • GSM Global System for Mobile communications
  • MIP Mobile Internet Protocol
  • IETF Internet Engineering Task Force
  • RFC 3344 C. Perkins, Request for Comments: 3344, August 2002, “IP Mobility Support for IPv4”, the contents of which are incorporated herein by reference.
  • MIP enables a mobile node to maintain the continuity of an internet session while moving across and between access networks.
  • MIP requires the mobile node to register periodically with its Home Agent (HA).
  • HA Home Agent
  • the MIP registration consists of an exchange of mobility protocol data traffic in the form of Registration Request and Registration Reply messages that establish a MIP tunnel between the MIP mobile node address (its Care of Address) and the HA.
  • Mobile devices having multiple radio interfaces are known, each interface using a different radio communications technology.
  • Known MIP clients available on such devices integrate a radio interface selection feature that enables a desired prioritisation of radio interfaces.
  • Interfaces can be preconfigured and each preconfigured radio interface is attributed a level of priority.
  • the radio interface which has been attributed the highest level of priority will be used by default to register the MIP client with the HA. If there is no available network associated with the radio interface configured with the highest level of priority, the MIP client will successively attempt to register using radio interfaces of decreasing levels of priority until the registration succeeds on the available radio interface of the highest level of priority.
  • An MIP client having several radio interfaces available is likely to be configured with the highest bandwidth radio interface as the radio interface with the highest priority.
  • a radio interface may for example be the Wifi radio interface.
  • the MIP client may also be configured with other radio interfaces such as a GPRS or UMTS radio interfaces with lower levels of priority. Such configuration choice is intended to select the Wifi radio interface to register and receive/send traffic when the mobile node is in the simultaneous coverage of Wifi and other access networks.
  • a particular radio interface is configured with the highest level of priority, that radio interface will be used by default for both the user data traffic and the mobility protocol data traffic when available.
  • Receiving traffic through the highest bandwidth radio interface typically offers the best Quality of Service (QoS) to the user.
  • QoS Quality of Service
  • radio interfaces such as a Wifi radio interface
  • consume lots of power Since a mobile device's power resources are limited, this can significantly reduce their battery lifetimes.
  • a method of controlling a mobile node in a data communications network including a plurality of different radio access technologies, the mobile node including a first radio interface for communicating via a first radio access technology, and a second radio interface for communicating via a second radio access technology, the mobile node having an application requiring the mobile node to communicate user data traffic with a remote node, said user data traffic being capable of being communicated via both said first radio interface and said second radio interface, wherein the method comprises using a mobility protocol for managing mobility of the mobile node between different access nodes, the mobility protocol requiring communication of mobility protocol data traffic with a network entity, preferentially selecting between said first and second radio interfaces when each of said first and second radio access technologies have coverage available to said mobile node, wherein said method comprises communicating via said first radio interface when there is said user data traffic being communicated, the first radio interface having been selected according to a first preferential selection, and altering the preferential selection from said first radio interface to said second radio interface in response to a trigger
  • the first radio interface is deactivated when the second radio interface is preferentially selected in this manner.
  • the first radio interface may for example be deactivated such that future re-selection of the first radio interface for the communication of user data traffic requires re-authentication using the first radio access technology.
  • the trigger may be a trigger indicating a halt to said user data traffic being communicated.
  • the trigger is preferably generated in response to the detection of none of said user data traffic being communicated for a period of time after user data traffic has been communicated.
  • the mobility of the mobile node is managed by a MIP client function.
  • the MIP client function may be implemented in software or hardware.
  • the user data traffic being communicated to and from the mobile node is monitored by a monitoring function.
  • the monitoring comprises the monitoring function communicating with the application.
  • the monitoring function can monitor the amount of user data traffic being communicated via an application running on the mobile node.
  • the trigger is generated by a MIP client function.
  • a MIP client function may generate a trigger according to the amount of user data traffic being communicated to and from the mobile node.
  • a trigger may be generated only when there is a change in the amount of user data traffic being communicated.
  • the trigger generation is in response to an enquiry from the monitoring function. Enquiries may occur at regular intervals in time.
  • the MIP client function is located in the mobile node.
  • mobility protocol data traffic may be processed by a MIP client function located in the mobile node.
  • the mobility protocol data traffic is capable of being communicated via both the first radio interface and the second radio interface.
  • mobility data traffic may be communicated via the first radio interface.
  • mobility data traffic may be communicated via the second radio interface.
  • preferential selection is performed in the mobile node.
  • decisions as to which radio interface is used on the mobile node can be carried out in the mobile node.
  • a MIP client function is located in a mobility protocol handling node remote to the mobile node.
  • mobility protocol data traffic can be processed by a MIP client function located in a mobility protocol handling node located in the network.
  • the mobility protocol handling node is responsible for managing the mobility of the mobile node between different access nodes.
  • a mobility protocol handling node can manage mobility of the mobile node on behalf of the mobile node.
  • the monitoring function is located in the mobility protocol handling node.
  • the mobility protocol handling node can preferentially select between the radio interfaces of the mobile node according to the monitored user data traffic.
  • preferential selection is performed in the mobility protocol handling node.
  • decisions as to which radio interface is used on the mobile node may be carried out in the mobility protocol handling node.
  • the mobility protocol handling node communicates with the network entity using a mobility protocol.
  • the mobility protocol handling node supports a mobility protocol and mobility management of the mobile node can be carried out by communication with the network entity using the mobility protocol.
  • the mobility network node communicates with the mobile node using a different protocol to the mobility protocol.
  • the mobile node can communicate with the mobility protocol handling node using one or more non-mobility protocols, such as the Internet Protocol Control Protocol (IPCP) and/or the Dynamic Host Configuration Protocol (DHCP).
  • IPCP Internet Protocol Control Protocol
  • DHCP Dynamic Host Configuration Protocol
  • the first radio interface is preferably used to communicate both said mobility protocol data traffic and said user data traffic, when said first radio interface is selected.
  • a method of controlling a mobile node in a data communications network including a plurality of different radio access technologies, the mobile node including a first radio interface for communicating via a first radio access technology, and a second radio interface for communicating via a second radio access technology, wherein each of said first and second radio interfaces are assigned a priority, indicative of an order in which the radio interfaces are to be selected, the method comprising dynamically updating said priority order in response to a trigger.
  • a method of controlling a mobile node in a data communications network including a plurality of different radio access technologies, the mobile node including a first radio interface for communicating via a first radio access technology, and a second radio interface for communicating via a second radio access technology, the mobile node having an application requiring the mobile node to communicate user data traffic with a remote node, said user data traffic being capable of being communicated via both said first radio interface and said second radio interface, wherein the method comprises using a mobility protocol for managing mobility of the mobile node between different access nodes, the mobility protocol requiring communication of mobility protocol data traffic with a network entity, at a mobility protocol handling node, monitoring user data traffic being communicated between said mobile node and said remote node, and in response to said monitoring indicating a change in an amount of user data traffic being communicated, transmitting a command from said mobility protocol handling node to said mobile node, said command indicating to said mobile node to switch on or switch off the power to one of said first or second radio
  • the power to a number of radio interfaces on a mobile node can be switched between the different radio interfaces according to the amount of user data traffic being communicated to and from an application running on the mobile node.
  • the amount of traffic being communicated to and from the mobile node can be monitored in a mobility protocol handling node located in the network remote from the mobile node.
  • the mobility protocol handling node can send a command to the mobile node to indicate that the power to a radio interface on the mobile node should be switched on or switched off.
  • a radio interface capable of higher data rate communication for example a higher bandwidth, will tend to have a higher power consumption than a radio interface only capable of lower data rate communication. If higher data rate communication is not required by the mobile node, then using a higher power radio interface can be wasteful in terms of power consumption. It can thus be beneficial to use a radio interface of lower power if that radio interface has an adequate communication data rate for current communication requirements. This can help to more efficiently use power resources which are limited on a mobile node.
  • a further command is transmitted from the mobility protocol handling node, the further command indicating to the mobile node to switch on or switch off the power to the other of the first and second radio interfaces.
  • the mobility protocol can command the mobile node to switch off one radio interface and switch on another radio interface instead.
  • the command and a further command are combined into a single command transmitted from the mobility protocol handling node to the mobile node.
  • the mobility protocol handling node may send a single command to the mobile node to indicate that it should switch off one radio interface and switch on another instead.
  • the first radio interface is a relatively high power interface compared to the second radio interface.
  • the relatively low power interface can be used instead of the relatively high power radio interface to help save limited power resources on the mobile node.
  • the change is a reduction or halt in the amount of user data traffic being communicated.
  • the amount of user data traffic reduces or halts, using a relatively low power radio interface may be sufficient.
  • the command indicates to the mobile node to switch off the first radio interface.
  • the relatively high power first radio interface may be switched off when communication at a higher data rate is not required.
  • the command indicates to the mobile node to switch on the second radio interface.
  • the relatively low power second radio interface may be switched on when communication at a lower data rate is adequate.
  • the change is an increase in the amount of user data traffic being communicated.
  • the amount of user data traffic increases, using a relatively low power radio interface may not provide sufficient communication capabilities.
  • the command indicates to said mobile node to switch on said first radio interface.
  • the relatively high power first radio interface may be switched on when communication at a higher data rate is required.
  • a further command indicates to the mobile node to switch off the second radio interface.
  • all communication may take place via the first radio interface only.
  • the mobility protocol handling node communicates with the network entity using the mobility protocol.
  • the mobility protocol handling node may communicate mobility protocol data traffic with the network entity using a mobility protocol.
  • the mobility protocol handling node can thus manage mobility on behalf of the mobile node using a mobility protocol such as the Proxy Mobile IPv4 protocol.
  • the mobility protocol handling node communicates with the mobile node using a protocol different to the mobility protocol.
  • the mobile may not support a mobility protocol, so the mobility protocol handling node may communicate with the mobile node in a different protocol. This can help reduce the cost and complexity of mobile nodes, as their hardware and/or software specifications can be simplified.
  • the command and/or the further command are transmitted using the different protocol.
  • the mobility protocol handling node may send commands to the mobile node in a protocol that the mobile node supports, rather than using a mobility protocol.
  • Such supported protocols may include the Internet Protocol Control Protocol (IPCP) and/or the Dynamic Host Configuration Protocol (DHCP).
  • a mobile node a mobility protocol handling node, apparatus and computer software adapted to perform the methods of the above aspects.
  • the above aspects of the invention allow for the re-prioritisation of radio interfaces based on requirements such as power management, whereby power resources may be conserved.
  • FIG. 1 shows a data communications network according to an embodiment of the invention.
  • FIG. 2 shows a flow diagram illustrating a mobile node control procedure according to an embodiment of the invention.
  • FIG. 3 is a block diagram showing communication between an interface, a control module, a MIP client and an application on a mobile node according to an embodiment of the invention.
  • FIG. 4 shows a data communications network according to an embodiment of the invention.
  • FIG. 5 is a diagram showing communication message flows for an exemplary registration sequence according to an embodiment of the invention.
  • FIG. 6 is a diagram showing communication message flows for deactivation of a radio interface according to an embodiment of the invention.
  • FIG. 7 is a diagram showing communication message flows for activation of a radio interface according to an embodiment of the invention.
  • FIG. 1 A general system architecture for elements forming a data communications network according to an embodiment of the present invention is illustrated in FIG. 1 .
  • the exemplary network includes a first access network 102 and a second access network 104 , each connected to a common core network beyond.
  • the common core network may for example be the internet.
  • network access is provided via a different radio access node 110 across wireless radio links 112 .
  • a network entity 106 for example a home agent HA, is arranged in the common core network to execute a network layer protocol stack for providing mobile internet protocol support to a set of mobile nodes MN 100 .
  • a communications link via which the protocol is provided utilises an internet protocol which is supported over a selected communications channel which may be effected via a number of mobile communications access networks.
  • An application server AS 108 is arranged in the common core network to provide an application layer service to a mobile node MN 100 .
  • a communications link via which the service is provided utilises an internet protocol which is supported over a selected communications channel which may be effected via a number of mobile communications access networks.
  • Each mobile node MN 100 includes a first radio interface for communicating with the first mobile access network, and beyond into the common core network, via a first radio access technology and a second radio interface for communicating with the second mobile access network, and beyond into the common core network, via a second radio access technology.
  • the first access network 102 may for example operate in accordance with a non-cellular radio wireless communications standard such as a WifiTM standard whereby network access is provided via a number of different Wifi access points.
  • the second access network 104 may for example operate in accordance with a cellular radio communications standard such as a GSM (including GPRS) standard or a UMTS standard, whereby network access is provided via a number of different cellular radio access nodes.
  • a third access network (not shown) may for example operate in accordance with another communications standard, for example an alternative non-cellular radio communications standard such as a BluetoothTM standard.
  • the mobile nodes MN may have first, second and third radio interfaces which implement features corresponding to the standards implemented by the first, second and third access networks, respectively.
  • the application server AS 108 manages one or several application layer applications for providing communications services to one or several of the mobile nodes using for example IP communications with the mobile nodes.
  • the mobile nodes MN 100 each have one or more corresponding applications which communicate with entities such as the application server AS 108 , which communications take the form of user data traffic communicated between the mobile nodes MN 100 and the application server AS 108 .
  • the user data traffic can be communicated via either said first radio interface or said second radio interface.
  • User data traffic may also comprise data transmitted between an application layer application on a mobile node and an application layer application on another mobile node, using for example IP communications between the mobile nodes.
  • the user data traffic may for example include one or more types of multi-media content such as multi-media documents, image files, video data, audio data, etc.
  • the home agent HA 106 manages one or more network layer applications which implement a mobile internet protocol (MIP) protocol stack.
  • the mobile nodes MN 100 each have a corresponding application which implements a mobile internet protocol (MIP) protocol stack, which application is referred to as a MIP client.
  • Communications between the MIP client and the HA take the form of mobility protocol data traffic communicated between the mobile nodes MN 100 and the home agent HA 106 .
  • the mobility protocol data traffic can be communicated via either said first radio interface or said second radio interface.
  • Embodiments of the present invention provide a facility for controlling mobile nodes to select various access networks in accordance with a selection algorithm.
  • Each of the mobile nodes has a MIP client which is controlled to select the access networks in dependence upon a setting indicating the level of priority attached to the radio access technology implemented by the access network.
  • FIG. 2 An example operation of a MIP client according to one embodiment of the invention is provided by a flow diagram illustrated in FIG. 2 .
  • the user data traffic is preferentially routed through MIP and through the first access network.
  • the MIP client receives a trigger indicating that user data traffic is being communicated.
  • the first radio interface of the mobile node MN is activated and selected as default radio interface, step S 1 .
  • Activation typically involves the mobile node authenticating with the first mobile access network.
  • the mobile node MN then registers with the HA on the first radio interface, step S 2 , and the user data traffic can be transported in a MIP tunnel ending on the first radio interface.
  • the MIP client When the MIP client is not sending or receiving any traffic for a certain period of time, the MIP client receives a trigger indicating that the communication of user data traffic has halted. This may be immediately in response to the halting of the transmission of data by an application on the mobile node, or may be triggered only after a preset delay. In response to this trigger, the MIP client selects the second radio interface to renew its registration with the HA, step S 3 . The mobile node MN completes its registration through the second radio interface, or possibly any other lower power-consuming radio interfaces. Re-registration may be necessary as a confirmation procedure and may occur at regular intervals.
  • the relatively high power-consuming first radio interface can then be shut down, step S 4 , thus saving power resources and significantly extending battery lifetime.
  • the less demanding second radio interface on which MIP has been registered may then stay on for the mobile node MN to be reachable through MIP and to prevent any disruption of flows of data traffic.
  • the first radio interface of the mobile node is reactivated and selected as the default radio interface, returning to step S 1 .
  • Reactivation typically involves the mobile node re-authenticating with the first mobile access network.
  • the selection of another radio interface to perform MIP re-registration before, or after, the default radio interface is turned off can be performed by several methods.
  • the priority levels of the different radio interfaces are stored in memory in the form of a look-up table, and a selection algorithm is used to perform selection according to the settings in the table of priority settings.
  • the settings may be user-configured.
  • the method of the invention can be achieved by re-prioritising temporarily the radio interfaces while keeping in memory the initial table of priority settings. Table 1 below shows priority settings assigned initially to different radio interfaces and Table 2 below shows a new priority scheme corresponding to radio interfaces being re-prioritised.
  • Table 1 as the initial configuration table is kept in non-volatile memory.
  • Table 2 applies to enable the MIP client to select the cellular radio interface to send the MIP signalling traffic before the Wifi radio interface is shut down.
  • Activating or deactivating an interface based on the amount of user data traffic sent from or received at a mobile node may be implemented using a control module located between the interface and a MIP client.
  • the user data traffic flowing to and from the mobile node can be referred to as the user data traffic layer.
  • a MIP client can gain access to the user data traffic layer via the one or more applications running on the mobile node.
  • FIG. 3 is a block diagram showing an arrangement of a mobile node where a control module 324 is located between interface 308 and MIP client 300 , which is able to access application(s) 326 .
  • Control module 324 may be organised into three logical parts: a monitoring module 302 , a decision module 304 and a command module 306 .
  • the monitoring of the user data traffic layer can be implemented using an enquiry method or by an event notification method, each of which are explained below in turn.
  • An enquiry method involves enquiring as to the state of the user data traffic layer, for example at regular intervals of time.
  • a ‘state request’ can be generated by decision module 304 for this purpose.
  • a state request 312 transmitted from decision module 304 to the user data traffic layer 300 will cause a ‘state reply’ to be generated by the user data traffic layer.
  • State reply 314 is transmitted back from the user data traffic layer, informing decision module 304 of the state of the user data traffic layer.
  • the state can be evaluated during the time that has elapsed between the reception of state request 312 and the transmittal of state reply 314 .
  • the time difference that elapses between the reception of a state request and the sending of its associated state reply is at least a value of ‘State_Eval_Time’ which can be defined as follows:
  • Several consecutive state requests may return the same value for the state of the user data traffic layer. If the state of the user data traffic layer changes between two consecutive state requests, then a state reply can carry that information to decision module 304 .
  • An event notification method can be implemented through the generation of a signal in the user data traffic layer, for example an interrupt signal, informing decision module 304 of a change of state of the user data traffic layer.
  • the event notification signal can be generated when an event of interest occurs in the user data traffic later.
  • Such events of interest may include:
  • the enquiry and event notification methods can be implemented through a Software Development Kit (SDK) (or ‘Devkit’) for use with MIP.
  • SDK Software Development Kit
  • decision module 304 When decision module 304 receives an event notification interruption or a state reply informing of a state change from a previous state reply, it queries the state of interface 308 using interface request 316 . Interface 308 then replies with interface reply 318 .
  • Decision module 304 takes the decision to turn interface 308 on or off according to a policy decision that achieves the dynamic interface selection described herein.
  • Interface 308 can be turned on or off by decision module sending a command signal to command module 306 which then activates or deactivates interface 308 accordingly 322 .
  • the logic for commanding the interface using the event notification method can be implemented as follows:
  • the logic for commanding the interface using the enquiry method can be implemented as follows:
  • a decision can be made by the decision module whenever the result of an enquiry is a change of state, either from S 1 to S 2 or S 2 to S 1 .
  • the logic for controlling the interface can be implemented as follows:
  • FIG. 4 A general system architecture for elements forming a data communications network according to a further embodiment of the present invention is illustrated in FIG. 4 .
  • the exemplary network includes mobile nodes 400 , a first access network 402 , a second access network 404 , each connected to a common core network beyond, and application server 408 .
  • network access is provided via a number of different radio access nodes 410 across wireless radio links 412 .
  • An application server AS 408 is arranged in the common core network to provide an application layer service to a mobile node MN 100 .
  • Each mobile node MN 100 includes a first radio interface for communicating with the first mobile access network, and beyond into the common core network, via a first radio access technology and a second radio interface for communicating with the second mobile access network, and beyond into the common core network, via a second radio access technology.
  • radio access nodes 410 communicate with network entity 406 via mobility protocol handling node 414 .
  • the mobile nodes are not aware of any mobility protocol.
  • the mobiles nodes do not run MIP client software and their mobility is instead handled by mobility protocol handling node (MPHN) 414 .
  • MPHN mobility protocol handling node
  • MPHN 414 may for example use a Proxy Mobile IP (PMIP) protocol such as Proxy Mobile IPv4 protocol (PMIPv4), which provides several benefits.
  • PMIPv4 supports mobility without any modification required to host entities.
  • PMIPv4 can provide mobility for a number of nodes without the need to modify networking stacks and without requiring additional software.
  • PMIPv4 can help to reduce signalling overhead in the network as multiple mobile nodes can be aggregated on the same tunnel.
  • PMIPv4 allows support for mobility between heterogeneous wireless link technologies.
  • PMIPv4 enables a node which does not have MIP functionality to move across access networks.
  • other network nodes provide the mobility support on behalf of the mobility unaware device.
  • IPv4 devices which do not have or cannot be enabled with MIP functionality.
  • the PMIPv4 scheme is based on an external network node acting as a proxy mobile node that registers the location of the device and maintains reachability while the device is on the network.
  • MPHN Mobility Proxy Agent
  • the MPHN offers proxy mobility services for mobile nodes by performing registration functions on their behalf.
  • the MPHN functionality may be combined with any access point, base station, access router or access gateway entities in the network.
  • FIG. 5 shows an exemplary registration message sequence where mobile node 500 registers with MPHN 502 , i.e. mobility protocol handling node 502 .
  • Mobile node 500 can connect to MPHN 502 using one of several connection protocols, for example Point to Point Protocol (PPP) or Dynamic Host Configuration Protocol (DHCP).
  • PPP Point to Point Protocol
  • DHCP Dynamic Host Configuration Protocol
  • Step 510 involves mobile node 500 initiating communication with MPHN 502 .
  • MPHN 502 then exchanges 512 Authentication Authorisation Accounting (AAA) messages with AAA server 506 in the network to perform authentication and authorisation of mobile node 502 .
  • AAA server 506 may download information about mobile node 500 , for example user profile, handset type, assigned home agent address, and other capabilities of the mobile node.
  • Mobile node 500 then sends 514 an Internet Protocol Control Protocol (IPCP) ‘Config request’ message to MPHN 502 in the case of PPP being used to request an IPv4 address, or a ‘DHCP Discovery’ message in the case of DHCP being used.
  • IPCP Internet Protocol Control Protocol
  • MPHN 502 Upon receiving message 514 , MPHN 502 sends a MIPv4 registration request to home agent 508 in step 516 .
  • Home agent 508 registers the mobile node's session and assigns a home address (HoA).
  • Home Agent 518 then transmits the HoA to MPHN 502 in a proxy registration reply message 518 .
  • MPHN 502 Upon receiving message 518 , MPHN 502 transmits a message 520 to mobile node 500 to suggest the IPv4 address which is the HoA allocated by home agent 518 .
  • message 520 could be in the form of an ‘IPCP Config-NAK’ message.
  • message 520 could be in the form of a ‘DHCP Offer’ message with the IPv4 address set equal to the received HoA.
  • Mobile node 500 is then able to exchange regular IPCP Network Control Protocol messages 522 with MPHN 502 .
  • the IP stack of mobile node 500 is then ready to send and receive IP packets.
  • messages 522 may be in the form of ‘DHCP Request’ or ‘DHCP Ack’ message exchanges and the mobile node's IP stack is configured with the assigned IPv4 address.
  • the mobile node does not understand or handle any mobility protocol. Instead, the MPHN performs monitoring of the user data traffic sent and received by a particular mobile node. The MPHN is responsible for making decisions as to which interface a mobile node should use. Once a decision has been made, MPHN sends a command to the mobile node to de-activate or to activate an interface. Thus, the activity of dynamic interface selection based on user data traffic is delegated to the MPHN.
  • This embodiment thus offers the benefits of removing the processing load required for dynamic interface selection from a mobile node, which in turn can lead to simpler and hence cheaper mobile node hardware.
  • the MPHN that a mobile node has been sending/receiving user data traffic through on its first radio interface is called the current MPHN.
  • the current MPHN monitors the user data traffic of the mobile node, for example using the mobile node's HoA.
  • the steps involved in the de-activation of the first radio interface on a mobile node as a command or instruction received from the current MPHN are illustrated in FIG. 6 .
  • Current MPHN 602 constantly monitors 610 the level of user data traffic for mobile node 600 . If current MPHN 602 notices that mobile node 600 is not sending or receiving any user data traffic for a certain period of time, MPHN 602 initiates the interface selection on mobile node 600 by sending an ‘IPCP Config’ or ‘DHCP Req’ message 612 to mobile node 600 . In response, mobile node 600 advertises 614 to current MPHN 602 its list of available access networks. Current MPHN 602 selects another interface such as the mobile node's second radio interface which is to be registered on a target MPHN 606 . Current MPHN 602 then sends a command message 616 to mobile node 600 to instruct mobile node 600 to initiate a proxy Mobile IP registration using the target network available via the second radio interface.
  • mobile node 600 sends an ‘IPCP Req’ or ‘DHCP Discovery’ message 618 to MPHN 606 in the target network.
  • Target MPHN uses PMIPv4 to initiate registration 620 of the second radio interface on mobile node 600 with home agent 608 in the target network.
  • Home agent 608 transmits a ‘PMIPv4 Registration revocation’ message 622 to the current (now previous) MPHN 602 , which in turn sends a command 624 to mobile node 600 to turn off its first radio interface.
  • the current (now previous) MPHN 602 responds to the ‘PMIPv4 Registration revocation’ message by transmitting an acknowledging ‘PMIPv4 Registration Ack’ message 626 to home agent 608 .
  • the interface selection process is then completed by home agent 608 transmitting a ‘PMIPv4 Registration Reply’ message 628 to target MPHN 606 .
  • the first radio interface on a mobile node is a relatively high bandwidth interface, for example a WLAN interface, it will tend to use more power than a lower bandwidth interface such as a GPRS or 3G interface. Commanding a mobile node to de-activate the first radio interface in this way thus allows saving of precious battery resources on the mobile node.
  • the less demanding interface, whose care of address has been registered with PMIP may stay switched on for the mobile node to be reachable and to avoid any disruption of data flow to and from the mobile node.
  • the first radio interface on a mobile node has been deactivated, i.e. is turned off, and the mobile node can send and receive data via its second radio interface.
  • the steps involved in the activation of the first radio interface on a mobile node as a command or instruction received from the current MPHN are illustrated in FIG. 7 .
  • the current MPHN 702 monitors 710 user data traffic sent and received by mobile node 700 .
  • current MPHN 702 When current MPHN 702 notices that mobile node 700 has started to send or receive traffic for a certain period of time, it initiates interface selection on mobile node 700 , by sending an ‘IPCP Config’ or ‘DHCP Req’ message 712 to mobile node 700 .
  • Mobile node 700 responds with an ‘IPCP Ack’ or ‘DHCP ‘Ack’ message 714 if it has a second radio interface available.
  • Current MPHN then sends a command 716 instructing mobile node 700 to turn on its second radio interface and to initiate registration 718 using its target network. This registration would usually take place over the first radio interface once it is activated, but could alternatively take place over the second radio interface before it is deactivated.
  • Registration of the target MPHN 706 and revocation of the current MPHN 702 is shown by steps 720 , 722 , 724 and 726 in a similar manner to steps 620 , 622 , 626 and 628 respectively as described above.
  • commanding the mobile node to activate the first radio interface when the mobile node is sending or receiving traffic through the current network is intended to improve the mobile node data throughput.
  • This can be of use when a higher data rate, bandwidth and/or Quality of Service (QoS) is required by a mobile node than can be provided via the current interface.
  • QoS Quality of Service
  • selection may be performed on the basis of parameters other than simply whether user data traffic is to be sent, for example signal strength.
  • the mobile node implements on its second radio interface an IEEE 802.11 WLAN standard (examples include variants of the 802.11 standard such as IEEE 802.11a, IEEE 802.11b, IEEE 802.11g).
  • a mobile node may implement on its second radio interface an IEEE 802.16 standard (examples include variants of the 802.16 standard such as IEEE 802.16a, IEEE 802.16b, IEEE 802.16g).
  • the 802.16 standards relate to a non-cellular radio access technology commonly referred by the term WiMaxTM, which is a trademark of the WiMax Forum.
  • This technique is intended to save battery lifetime of small devices such as Laptops, PDAs or Smartphones which use an implementation of Mobile IP.
  • the dynamic selection of radio interfaces presented in this technique could apply to mobility protocols other than MIP. In general it could apply to any protocol that requires the mobile node to communicate with one or several network entities whether the mobile node is active or not.
  • MIP clients i.e. are MIP compliant
  • other mobile nodes do not comprise MIP clients, i.e. are not MIP compliant and must employ the services of one or more mobility protocol handling nodes.
  • the functionality of one or more radio access nodes and one or more mobility protocol handling nodes may be combined into a single network node.
  • FIGS. 1 and 4 only show one application server, but more than one application server may equally be employed to provide communications services to the mobile nodes.
US12/516,567 2006-11-27 2007-11-26 Data communications Abandoned US20100062760A1 (en)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
EP06291826 2006-11-27
EP06291826.3 2006-11-27
EP07290332.1 2007-03-19
EP07290332A EP1926283A1 (de) 2006-11-27 2007-03-19 Datenkommunikation
PCT/EP2007/062820 WO2008065079A1 (en) 2006-11-27 2007-11-26 Data communications

Publications (1)

Publication Number Publication Date
US20100062760A1 true US20100062760A1 (en) 2010-03-11

Family

ID=39048035

Family Applications (1)

Application Number Title Priority Date Filing Date
US12/516,567 Abandoned US20100062760A1 (en) 2006-11-27 2007-11-26 Data communications

Country Status (3)

Country Link
US (1) US20100062760A1 (de)
EP (2) EP1926283A1 (de)
WO (1) WO2008065079A1 (de)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090257425A1 (en) * 2008-04-14 2009-10-15 Cisco Technology, Inc. Synchronizing DHCP And Mobile IP Messaging
US20100009676A1 (en) * 2008-07-11 2010-01-14 Research In Motion Limited System and method for radio access technology-specific routing for multi-mode mobile devices
US20100220640A1 (en) * 2009-02-27 2010-09-02 Research In Motion Uk Limited Method, apparatus and system for battery resource management via traffic steering
US20120069827A1 (en) * 2010-09-16 2012-03-22 Qualcomm Incorporated Power conservation in wireless client terminals using proxy device
US8699464B1 (en) * 2012-04-26 2014-04-15 Sprint Spectrum L.P. Multi-band communication with a wireless device
US20140355522A1 (en) * 2013-06-03 2014-12-04 Broadcom Corporation Systems and Methods for Splitting and Recombining Communications in Multi-Network Environments
US8929852B1 (en) 2013-01-22 2015-01-06 Sprint Spectrum L.P. Method and system for managing a wireless communication device to apply a revised scanning order in response to external events

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8825109B2 (en) 2008-02-15 2014-09-02 Blackberry Limited Policy-based data routing for a multi-mode device
EP2224772B1 (de) * 2009-02-27 2017-11-08 BlackBerry Limited Verfahren, Vorrichtung und System für die Batterieressourcenverwaltung durch Verkehrslenkung
US8750188B2 (en) * 2010-12-01 2014-06-10 Deutsche Telekom Ag System support for accessing and switching among multiple wireless interfaces on mobile devices
US9345059B2 (en) 2011-11-25 2016-05-17 Bandwidthx Inc. Mobile device radio management
US9826464B2 (en) 2013-03-26 2017-11-21 Bandwidthx Inc. Systems and methods for establishing wireless connections based on access conditions
EP3328131A1 (de) * 2016-11-28 2018-05-30 Nokia Technologies OY Verfahren zur auswahl einer kommunikationsverbindung, system, vorrichtung mit geringer komplexität und computerprogrammprodukt
US10856151B2 (en) 2016-12-27 2020-12-01 Bandwidthx Inc. Radio management based on user intervention
US10194382B2 (en) 2016-12-27 2019-01-29 Bandwidthx Inc. Auto-discovery of amenities
US11071063B2 (en) * 2017-07-23 2021-07-20 Ali Atefi Apparatuses, methods, and computer-readable medium for communication in a wireless local area network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040077341A1 (en) * 2002-10-17 2004-04-22 Chandranmenon Girish P. Multi-interface mobility client
US7039404B2 (en) * 2002-06-27 2006-05-02 Intel Corporation Continuous mobility across wireless networks by integrating mobile IP and GPRS mobility agents
US20060140150A1 (en) * 2004-11-05 2006-06-29 Interdigital Technology Corporation Wireless communication method and system for implementing media independent handover between technologically diversified access networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7039404B2 (en) * 2002-06-27 2006-05-02 Intel Corporation Continuous mobility across wireless networks by integrating mobile IP and GPRS mobility agents
US20040077341A1 (en) * 2002-10-17 2004-04-22 Chandranmenon Girish P. Multi-interface mobility client
US20060140150A1 (en) * 2004-11-05 2006-06-29 Interdigital Technology Corporation Wireless communication method and system for implementing media independent handover between technologically diversified access networks

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8351928B2 (en) * 2008-04-14 2013-01-08 Cisco Technology, Inc. Synchronizing DHCP and mobile IP messaging
US20090257425A1 (en) * 2008-04-14 2009-10-15 Cisco Technology, Inc. Synchronizing DHCP And Mobile IP Messaging
US8774805B2 (en) 2008-07-11 2014-07-08 Blackberry Limited System and method for radio access technology-specific routing for multi-mode mobile devices
US20100009676A1 (en) * 2008-07-11 2010-01-14 Research In Motion Limited System and method for radio access technology-specific routing for multi-mode mobile devices
US20100220640A1 (en) * 2009-02-27 2010-09-02 Research In Motion Uk Limited Method, apparatus and system for battery resource management via traffic steering
US8131325B2 (en) * 2009-02-27 2012-03-06 Research In Motion Limited Method, apparatus and system for battery resource management via traffic steering
US9161266B2 (en) 2009-02-27 2015-10-13 Blackberry Limited System, server and device for battery resource management via traffic steering
US8588120B2 (en) * 2010-09-16 2013-11-19 Qualcomm Incorporated Power conservation in wireless client terminals using proxy device
US20120069827A1 (en) * 2010-09-16 2012-03-22 Qualcomm Incorporated Power conservation in wireless client terminals using proxy device
US8699464B1 (en) * 2012-04-26 2014-04-15 Sprint Spectrum L.P. Multi-band communication with a wireless device
US8929852B1 (en) 2013-01-22 2015-01-06 Sprint Spectrum L.P. Method and system for managing a wireless communication device to apply a revised scanning order in response to external events
US20140355522A1 (en) * 2013-06-03 2014-12-04 Broadcom Corporation Systems and Methods for Splitting and Recombining Communications in Multi-Network Environments
US9730271B2 (en) * 2013-06-03 2017-08-08 Avago Technologies General Ip (Singapore) Pte. Ltd. Systems and methods for splitting and recombining communications in multi-network environments

Also Published As

Publication number Publication date
EP2090054A1 (de) 2009-08-19
WO2008065079A1 (en) 2008-06-05
EP1926283A1 (de) 2008-05-28

Similar Documents

Publication Publication Date Title
US20100062760A1 (en) Data communications
US10972949B2 (en) Sleep-state for mobile terminal and service initiation for mobile terminals in sleep-state
EP2210387B1 (de) Technik zur bereitstellung von unterstützung für mehrere mobilitätsverwaltungsprotokolle
US7272123B2 (en) System and method for handoff processing
JP4987854B2 (ja) マルチｉｐネットワークインタフェース・モバイル機器におけるシームレスなネットワークインタフェースの選択、ハンドオフ及び管理
US20060126582A1 (en) Delivering data to a mobile node in idle mode
US20090052398A1 (en) Method of performing a handover
EP1986372A1 (de) Verfahren und Vorrichtung zur Unterstützung des Handovers zwischen heterogenen Zugangsnetzwerken

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION