[go: up one dir, main page]

WO2010000090A1 - Mécanismes de transfert inter-domaines entre des domaines localisés de mobilité réseau basés sur un réseau - Google Patents

Mécanismes de transfert inter-domaines entre des domaines localisés de mobilité réseau basés sur un réseau Download PDF

Info

Publication number
WO2010000090A1
WO2010000090A1 PCT/CN2008/001251 CN2008001251W WO2010000090A1 WO 2010000090 A1 WO2010000090 A1 WO 2010000090A1 CN 2008001251 W CN2008001251 W CN 2008001251W WO 2010000090 A1 WO2010000090 A1 WO 2010000090A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile node
mobility anchor
network
mobility
local
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.)
Ceased
Application number
PCT/CN2008/001251
Other languages
English (en)
Other versions
WO2010000090A8 (fr
Inventor
Xiaoming Fu
Niklas Neumann
Jun LEI
Gong Zhang
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.)
Huawei Technologies Co Ltd
Georg August Universitaet Goettingen
Universitaetsmedizin Goettingen Georg August Universitaet
Original Assignee
Huawei Technologies Co Ltd
Georg August Universitaet Goettingen
Universitaetsmedizin Goettingen Georg August Universitaet
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 Huawei Technologies Co Ltd, Georg August Universitaet Goettingen, Universitaetsmedizin Goettingen Georg August Universitaet filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2008/001251 priority Critical patent/WO2010000090A1/fr
Publication of WO2010000090A1 publication Critical patent/WO2010000090A1/fr
Publication of WO2010000090A8 publication Critical patent/WO2010000090A8/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/12—Reselecting a serving backbone network switching or routing node
    • H04W36/125—Reselecting a serving backbone network switching or routing node involving different types of service backbones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]

Definitions

  • the invention relates to the field of mobile data connections, in which a mobile node, e.g. a notebook is connected to a fixed node like a wireless router. Data is transferred between router and notebook via a wireless connection, the router routing data from and to a network, e.g. the Internet, connected to the router via a wired connection.
  • the mobile node changes the point of connection requiring signaling and link control processes to enable another point of connection (another wireless router) to be connected to the mobile node.
  • the present invention relates to the field of handover mechanism providing such processes.
  • This invention relates to a mechanism to setup and maintain handover and data forwarding procedures that allows a mobile node (MN) to move between different domains that provide (localized) network-based mobility support for the MN to communicate with a corresponding node (CN).
  • MN mobile node
  • CN corresponding node
  • This new approach does not require a home domain or a central entity which performs complex signaling processes induced by handover, and the all the mobile nodes' data forwarding and possible charging.
  • a mobile node in the current internet needs to maintain a fixed endpoint when it moves to allow for seamless connectivity with its corresponding nodes.
  • a steady anchor point has to be provided for corresponding nodes.
  • this is the home agent (HA).
  • HA home agent
  • Such approaches are described as the standard RFC3775 of the Internet Engineering Task Force (IETF), defined in at least in parts in "Mobility Support in IPv6", Network Working Group D. Johnson, Rice University; C. Perkins, Nokia Research Center; J. Arkko, Ericsson, June 2004, retrievable under ftp://ftp.rfc-editor.org/in-notes/rfc3775.txt.
  • Proxy Mobile IPv6 In the standard draft Proxy Mobile IPv6 (PMIP), the steady anchor point is the local mobility anchor (LMA).
  • LMA local mobility anchor
  • a document describing the PMIP standard the IETF draft ,,Proxy Mobile IPv6, draft-ietf-netlrnm-proxymip6-15.txt" by NETLMM WG, S. Gundavelli (Editor); K. Leung, Cisco; V. Devarapall, Wichorus; K. Chowdhury, Starent Networks; B. Patil, Nokia Siemens Networks of May 16, 2008, which retrievable under http://tools.ietf.org/html/draft-ietf-netlmm-proxymip6-15.
  • the anchor point defined in this standard draft allows the mobile node to change its point of attachment (so-called mobile access gateway, or MAG) to a network without its corresponding nodes to notify that. All the mobile node's traffic is routed through this anchor point which then forwards the traffic to the mobile node.
  • MAG mobile access gateway
  • a network-based mobility management protocol like Proxy Mobile IPv6 does not rely on changes on mobile nodes, but mainly rely on the network to handle the mobility management; it also provides better performance with less overhead than Mobile IPv6-based approaches.
  • each handover involves connecting to a new network mobility domain by an authentication process carried out by an AAA (entity for authentication, authorization and accounting maintained by a provider), which may reside on a server located far away. Further, the AAA retrieves the address of the initial local mobility anchor and sends it to the mobile access gateway.
  • AAA entity for authentication, authorization and accounting maintained by a provider
  • This mechanism is inherently linked with a time consuming authentication process, data transfer over long distances and a large overhead since each handover starts an authentication process even if a authentication is not required by the new network mobility domain. This is apparent when imaging a scenario with small domains and a relatively fast moving mobile node, e.g. a laptop in a train or car passing an office with a number of departments, each providing a network mobility domain (e.g. a WLAN area).
  • the handover mechanisms known in the prior art suffer from complexity as regards system structure and process steps, reduced flexibility when moving between different domains and a high latency when connecting to the new network mobility domain, which substantially impairs the reliability of the connection.
  • the invention provides an improved handover mechanism by the implementation of the session mobility anchor (SMA), to which the mobile node (MN) is dedicated (before and after the handover), as well as by a local mobility anchor (LMA) of a network mobility domain to which the mobility node is handed over (a visited local mobility anchor, LMAv), which locates the session mobility anchor (SMA).
  • SMA is the first LMA of at least two LMAs to which a mobile node (MN) connects to.
  • the functionality of locating the session mobility anchor (SMA) is realized by the visited local mobility anchor (LMAv).
  • the visited local mobility anchor (LMAv) can establish a connection between the MN and the SMA.
  • the MN can be assigned to the SMA before and after the handover, the SMA thus providing a persistent local mobility anchor for the MN.
  • the MN can be associated to the first LMA to which it connects to, that is to the SMA, and remains to be associated or designated to the SMA during handovers among the at least two network mobility domains.
  • the MN can be handed over without any change of the dedicated local mobility node for the MN.
  • the handover mechanism of the invention provides transparent routing without routing or signaling involvement of the MN as regards LMA changes.
  • the entity locating the SMA to which the MN is associated or dedicated to can be any local entity of the second network mobility domain.
  • the local entity is preferably the LMA of the second network mobility domain.
  • This LMA is also denoted as visited local mobility anchor (LMAv) since it is the current LMA to which the MN tries to connect to.
  • Other realizations of the local entity are a mobile access gateway (MAG) of the second network mobility domain or other entities or units pertaining to and being connected to the second network mobility domain.
  • MAG mobile access gateway
  • Such entities or units form a part or perform a function of the second network mobility domain, such that the step of locating according to the invention is an additional feature of the respective (local) entity or unit.
  • the local entity pertaining to a mobile network domain preferably pertains exclusively to this mobile network domain or is shared by a subgroup of mobile network domain of the at least two mobile network domains.
  • the mobile network domain to which the local entity pertains to is connectable by the MN; thus, the MN is in the range of the mobile network domain to which the MN tries to connect to.
  • the LMAv is located in the mobile network domain, to which the MN pertains to.
  • the visited network where a mobile node is initially connected to i.e., bootstraps or "root"
  • bootstraps or "root” This is independent from the actual or previous location of the mobile node, i.e. independent of the identity of LANs (or network mobility domains to which the mobile node MN has been previously connected to).
  • the first network to which the MN connects to is responsible to provide the actual mobility services to the MN, no matter where the MN moves to.
  • the mechanisms according to the invention implement an inter-domain signaling between the bootstrapping network domain (i.e.
  • the network domain of the SMA and the new visited domain (the domain of the LMAv), to setup session handover and data forwarding between the different domains.
  • a central node within all network mobility domains or within a common network to which the network mobility domains are connected to is responsible for forwarding and resolving the SMA.
  • the local entity resolving the first network mobility domain of the SMA provides forwarding by establishing a connection between the network mobility domain of the SMA and the network mobility domain of the LMAv, e.g. between SMA and LMAv.
  • This connection can be a tunneling connection established by the LMAv.
  • the concept underlying the invention as described therein can be realized by: a method for handovers between at least two network mobility domains (one of which comprising the
  • SMA and another comprising the LMAv in which the SMA is located the LMAv, which retrieves a SMA identification e.g. from a transmission of the MN or from a data base mapping the MN (MN identification) onto the corresponding SMA (SMA identification).
  • a SMA identification e.g. from a transmission of the MN or from a data base mapping the MN (MN identification) onto the corresponding SMA (SMA identification).
  • the LMAv or anther entity of the network e.g. an entity of the network domain, to which the MN connects to, a connection from this network domain to the network domain of the SMA can be established, preferably by establishing a tunnel.
  • the LMA a LMA adapted to retrieve the SMA identification as described above.
  • the LMA comprises a port and a retrieval unit for retrieving the SMA identification.
  • the retrieval unit is connected to the port and is adapted to detect the SMA identification from a transmission received by the port and sent by the mobile node to a network mobility domain.
  • a MAG or another local entity pertaining to a mobile network domain can be used to implement the invention.
  • the MAG or other local entity is defined by the features described with regard to LMA.
  • a LMA comprising an identification request port, a identification request generation unit and an identification request receive unit, which are operatively connected with each other.
  • the identification request generation unit is a code generator which generated a session mobility anchor request containing the MN identification of the MN (preferably together with an identification of the LMAv).
  • the LMA transmits the request to a data base (DB).
  • DB data base
  • the LMA further comprises a receiver for receiving the response of the DB, the response containing the SMA identification (of the SMA to which the MN is dedicated to).
  • LMA a MAG or another local entity pertaining to a mobile network domain
  • the MAG or other local entity is defined by the features described with regard to LMA.
  • the first embodiment of the LMA retrieves the SMA passively from a message of the MN (similar to a message monitor detecting the SMA information), whereas the second embodiment of the LMA (or MAG or local entity) actively generates and sends a request to a database for resolving the SMA of the MN.
  • Both embodiments can be combined in one LMA (the mode of operation of the LMA should be selectable).
  • both embodiments are preferably adapted to establish a connection to another LMA (i.e. the SMA). This could be realized by a connection establishing unit with a port for receiving the SMA address and being adapted to establish a tunneling connection with the SMA.
  • the process of establishing could be carried out by a TX/RX-entity processing data according to the respective protocol stack for establishing an IP-tunnel.
  • a computer program product comprising code representing instructions implementing the step of retrieving an SMA identification as described above.
  • SMA is retrieved from a transmission sent by the MN (i.e. the passive retrieval process described above) or from the data base mapping MN data on LMA (SMA) data (i.e. the active retrieval process described above).
  • identification request response unit comprising a memory, a processor connected therewith, and a I/O-port connected to the processor.
  • the memory together with the processor, is adapted for maintaining a look-up table which realizes the mapping of MN data onto LMA data, and, consequently realizes the data base.
  • the response unit comprises an I/O- port receiving requests and transmitting the request data to the processor.
  • the processor retrieves the corresponding SMA data from the look-up table (i.e.
  • the data base transmits this SMA data (which also might be a not-in-list-signal) to the I/O-port, which in turn forwards the SMA data to a respective entity (to the second network mobility domain or to the LMAv).
  • the I/O-port might send the information to another entity forwarding the information to the entity from which the request has been sent.
  • the first or second embodiment of the LMA or the identification request response unit can realized in hardware only, as a hardware/software combination or as computer code modules, together with a programmable processor realizing the respective features.
  • the LMA or the identification request response unit can be a part of a unit realizing other functions.
  • the LMA and the identification request response unit can be computer code added to the (memory of) the unit and some of the features (e.g. the ports and the processor) can be realized by elements being part of the unit and being used for the realization of the other functions of the unit.
  • a local mobility anchor or a group of or all local mobility anchors of a plurality of network mobility domains has/have the ability to identify the SMA initially associated to a MN and has preferably further the ability to establish a connection to the session mobility anchor.
  • This mechanism of identifying the SMA and routing/forwarding between MN and SMA is distributed over all network mobility domains comprising a local mobility anchor according to the invention.
  • the entity implementing the identification process for identifying the SMA to which the MN is dedicated is provided in a decentralized arrangement and is realized by (distributed) local mobility anchors of (distributed) network mobility domains, in contrast to centralized approaches (centralized LMA identification / centralized signaling / centralized routing) described in the prior art.
  • This fundamental difference as regards the system architecture results in simple implementations (existent local mobility anchors can be used for implementing the function of identifying the session mobility anchor e.g.
  • the LMA is preferably adapted for establishing a connection to the session mobility anchor as well as to the mobile node.
  • the process of establishing a connection between the visited local mobility anchor (LMAv) and the SMA is carried out by another entity of the network or of one of the network mobility domains, for example, by the SMA or by a mobile access gateway (MAG) of the new network mobility domain (to which the MN is handed over) or of the preceding network mobility domain (to which the MN has been dedicated before handover).
  • MAG mobile access gateway
  • Such a connection between visited local mobility anchor (the new local mobility anchor of the network mobility domain, to which the MN is handed over) is preferably a tunnel providing a transparent connection.
  • a handover is carried out between (at least) two network mobility domains, each of which comprises a local mobility anchor, by establishing a first mobile connection between mobile node MN and a first network mobility domain.
  • the first network mobility domain is preferably the network mobility domain of (at least) two network mobility domains, to which the MN initially connects to.
  • the local mobility anchor of the first network mobility domain is designated as a session mobility anchor (which can be seen as the "root" local mobility anchor), and the mobile node is designated to this session mobility anchor as the local mobility anchor, which is initially dedicated to or associated with the mobile node.
  • the association between mobile node and session mobility anchor is kept unchanged.
  • the mobile node Upon movement of the mobile node, the mobile node is coming into the range of a new network mobility domain denoted as second network mobility domain, to which a connection is required, when the first connection is to be released (e.g. due to critical signal strength / SNR level).
  • the first connection is replaced by the second connection, preferably in a overlapping manner.
  • handover Such a change between first and second connection is denoted as handover.
  • the second mobile connection between the mobile node and the second network mobility domain is established (and the first connection is released, preferably after successful establishment of the second connection, i.e. overlapping).
  • Locating the SMA can be performed by assessing an identification or identifier of the SMA and does not necessarily mean to locate the session mobility anchor in the sense of a spatial localization like in form of geographic coordinates.
  • Locating the SMA comprises retrieving a session mobility anchor identification, whereby this retrieval can be carried out directly (actively) or indirectly (passively).
  • a session mobility anchor identification is preferably a unique identification, e.g. realized in form of a binary code with a predefined number of bits such as a (physical) address, a MAC (medium access control) address, an IP address, an IP submask or a similar binary number, which also can be represented as HEX code or ASCII code.
  • the MN identification can be a identifier directly denoting the MN of can be an (indirect) identifier, which is mapped onto the identity (or an IP address, e.g. the MN's home address) of the MN.
  • the MN is identified by its home address of the MN.
  • the MN has a mobile node identification, which can be realized in the same or a different way as the SMA identification.
  • the identifications can by unique among all entities or within subgroups of all SMA or MN entities.
  • Direct Retrieval A direct retrieval is carried out by the visited local mobility anchor (LMAv), which retrieves an entry of a data base (DB), the data base storing SMAs (local mobility anchors, which have been initially accessed by a MN) in relationship with respective mobile nodes MN, which are dedicated to the respective SMA.
  • direct retrieval or direct location means to provide a data base (DB) which is dedicated to the function of maintaining session mobility anchor information in relationship with mobile note information of the MNs dedicated thereto.
  • DB data base
  • a LMAv can send a request identifying the MN requesting connection to the LMAv.
  • a DB receives this request (for example in form of a request message sent by the LMAv) and returns the SMA information associated with the MN information.
  • the SMA information is sent back to the LMAv, for example, in form of a request return message transmitted by the DB or by an transmitting unit (e.g. a processor) connected therewith.
  • the DB stores SMA information (only once for one SMA), in relation to information identifying the MN or MNs which has or have been dedicated to the SMA.
  • the visited local mobility anchor retrieves an entry of a shared look-up table the entries of which map mobile node identifications onto session mobility anchors dedicated thereto.
  • the shared look-up data table is accessible by each of the local mobility anchors of the network mobility domains, the look-up data table realizing the DB.
  • the DB stores the mobile node information together with information identifying the actual LMA to which the MN is dedicated to.
  • the request sent by the LMAv preferably comprises both: information identifying the MN as well as information identifying the LMA to which the MN established a connection.
  • the request can be sent by the LMA via the mobile access gateway (MAG) or could be sent by the MAG of the network mobility domain to which the MN establishes the connection upon the requesting of the LMA.
  • MAG mobile access gateway
  • the LMAv can request other entities of its network mobility domain to correspond with the DB in order to support the requesting LMAv retrieve the SMA information requested by the LMAv.
  • Such assisting units corresponding with the DB are preferably adapted to forward the information gathered from the DB to the LMAv.
  • the DB's response can be transmitted directly from the DB to the requesting LMAv.
  • the MNs identity can be resolved by retrieving a corresponding entry of the Binding Update List (stored in the MN).
  • the second mobility network domain can retrieve the MN' s SMA (initial LMAv) by a request sent to the MN, the MN responding by sending the corresponding (latest) LMA entry to the second mobility network domain, e.g. to the LMAv, the MAG of the second mobility network domain or another local entity of the second network mobility domain retrieving the identity of the SMA to which the MN is dedicated to.
  • the DB is distributed over the MNs of the system or located within the connecting MN.
  • the DB can be a stand-alone unit or can be a part of a router or server unit.
  • the DB is provided by a cache memory of a router or of a server and a processor connected therewith.
  • a mobile access gateway provides the DB, preferable at least one MAG of at least two network mobility domains, all MAGs of at least two network mobility domains or the MAG of the first mobility domain.
  • the session mobility anchor (the first LMA to which the MN connects to or tries to connect) is detected by analyzing the behavior of the MN, that is by analyzing messages or requests (in general: transmissions), which are sent from the mobile node to the second network mobility domain, that is to the local mobility anchor to which the MN connects to (the LMAv).
  • the MN sends a connection request to the LMA when coming into range of the LMA, making the
  • the MN sends a router solicitation message to the LMA comprising information identifying the MN.
  • a connection request message comprises, among other, information identifying the MN, e.g. a binary code in the header of the message representing a physical address or a MAC address or a IP address of the MN.
  • the MN identification data can be retrieved from a Binding Update message.
  • FIG. 1 shows an exemplary embodiment of the inventive hand-over mechanism as a system overview, together with a data base for active SMA retrieval;
  • Fig. 2 shows an exemplary of the inventive hand-over mechanism using passive SMA retrieval.
  • Fig. 1 shows a system performing the inventive handover process.
  • the system comprises a corresponding node CN and three network mobility domains Nl 5 N2 and N3.
  • Each network mobility domain has a mobile access gateway MAG_1, MAGJ2 and MAG_3 and a local mobility anchor LMA_1, LMA_2 and LMA_3.
  • MAG_1 of Nl is connected to LMA_1, MAG_2 of N2 is connected to LMA_2 and MAG_3 of N3 is connected to LMA_3.
  • each MAG of the respective network mobility domain is connected to the LMA of the respective network mobility domain.
  • LMA_1 is the first LMA to be connected to mobile node MN
  • LMA is the SMA (session mobility domain) for the network mobility domains Nl - N3 (i.e. for all network mobility domains of the system).
  • SMA session mobility domain
  • Nl - N3 i.e. for all network mobility domains of the system.
  • PMIP Proxy Mobile IPv6 domains.
  • a data base is connected to LMA_1, LMA_2 and LMA_3.
  • DB data base
  • a mobile node MN initially attaches to network mobility domain Nl, i.e. a PMIP domain
  • the local mobility anchor LMA_1 of Nl becomes the session mobility anchor (SMA) for the mobile node.
  • SMA session mobility anchor
  • the new PMIP domain's LMA J2 will initialize a connection cl (e.g. a tunnel) to the SMA to allow the SMA to continue to serve as an anchor point for the MN.
  • a connection cl e.g. a tunnel
  • LMAv visited LMA
  • the current LMA LMAJ2 of a MN can be seen as a MAG (MAGJ2) which performs the corresponding operations.
  • connection c2 e.g. a tunnel
  • SMA SMA
  • the LMA of the new domain (LMA_2 after move mvel and LMA_3 after move mve2) localizes the SMA.
  • the DB retrieves the corresponding SMA identification information and transmits the information to the requesting LMAv.
  • a corresponding on the connections shown with dotted lines can be used for transmitting the information to the requesting LMAv.
  • the DB can be connected to the LMAv (LMA_1 - LMA_3) via the CN.
  • the LMA of this domain has to locate the SMA for this MN and initiate a tunnel between itself and the SMA.
  • the PMIP domain is the first domain the MN attaches to within its mobility session, the current LMA becomes the SMA and continues with its regular PMIP operations.
  • the MN was already attached to a different PMIP domain, its SMA resides within this previous domain and the LMA needs to establish a binding with the SMA in order to send and receive the data for the MN through its SMA.
  • the LMA can directly or indirectly locate the
  • SMA for a MN Direct location or active location or retrieval of a SMA for a MN requires some kind of look-up between associated PMIP domains Nl - N3. For example, this can be achieved by maintaining the common database DB shown in Fig. 1, where SMAs deposit the information for which MN they are responsible for, i.e. for each known MN an SMA to which the MN is dedicated to.
  • Such a database as shown in dotted lines in Fig. 1 can be established by service level agreements between the operators of PMIP domains Nl - N2.
  • the MNs identity can be its Network Access Identifier (NAI) as the look-up key.
  • NAI Network Access Identifier
  • the Network Access Identifier (NAI) is the user identity submitted by the client during network access authentication.
  • the purpose of the NAI is to identify the user as well as to assist in the routing of the authentication request.
  • the NAI is defined in the IETF Standard: "RFCc4282 - The Network Access Identifier", Network Working Group, B. Aboba, Microsoft; M. Beadle, ENDFORCE; J. Arkko, Ericsson; P. Eronen, Nokia; December 2005. If the database does not have an entry for the MN, the LMAv becomes the SMA for the mobility session of the MN.
  • the DB can be connected to the LMAs as depicted in Fig. 1, or, alternatively, be a part of the MN or can be an entity directly connectable by the MN, e.g. a look-up table stored in the MN like a cache or binding update list. Further, these implementations can be provided as a combination of these examples.
  • a direct (or active) retrieval is carried out using the DB shown in Fig. 1 as described above.
  • An indirect or passive retrieval is described in the following by means of Fig. 2.
  • Fig. 2 shows a signaling flow according to an embodiment of the invention.
  • Fig. 2 shows signals and events together with the corresponding entities in form of a protocol flow over time t (vertical arrow).
  • the LMA (the LMAv) can use an indirect scheme to locate the SMA of a MN.
  • the LMA infers the SMA assigned IP address of the MN and uses this address to send its session transfer request to. Since the SMA is responsible for this IP address, the LMA will indirectly reach the SMA. If there is no reply to the request, the LMA must assume that no previous SMA exists and become the SMA for the mobility session of the MN.
  • the SMA assigned IP address of a MN is the IP address the MN got assigned when it initially attached to a PMIP domain.
  • the LMA can try to infer this IP address, for example, by analyzing the MN' s Router Solicitation or DHCP requests.
  • Figure 2 shows the signalling flow when a MN attaches to a PMIP domain.
  • the MN attaches to the MAG (Attach) and sends a router solicitation message (Rtr Sol) 10, to the MAG of the visited network domain.
  • the MN sends a Router Solicitation message 10 that is received by the local MAG.
  • a PBU Proxy Binding Update
  • a PBU is a binding registration request message sent by a mobile access gateway MAG to a mobile node's local mobility anchor LMA (in Fig. 2 identical with LMAv) for establishing a binding between the mobile node's home network prefix(es) assigned to a given interface of a mobile node and its current care-of address (Proxy-CoA), i.e. the SMA.
  • a Proxy Binding Acknowledgement (PBA) message is a binding registration reply message sent by a local mobility anchor (in this case the SMA) in response to a PBU request message that it received from a mobile access gateway (MAG).
  • PBA Proxy Binding Acknowledgement
  • the LMA forwards the received PBA 40 in form of a PBA message 60 to its MAG which in turn uses the PBA 60 to configure the MN. Also, the LMA establishes a connection 70 to the MAG by providing a bi-direct tunnel to this MAG. All traffic for the MN is then routed from the SMA through the LMA and the MAG, i.e. via the concatenated connections 50 and 70.
  • the MAG Upon reception of PBA message 60, the MAG responds on the router solicitation message 10 by sending a Router Advertisement message (Rtr Adv) 80 to the MN. All future movements of the MN within the new PMIP domain are covered by local mobility operations, e.g. the operations described in as described in IETF draft ,,Proxy Mobile IPv6, draft-ietf-netlmm-proxymip6-15.txt" by NETLMM WG, S. Gundavelli (Editor); K. Leung, Cisco; V. Devarapall, Wichorus; K. Chowdhury, Starent Networks; B. Patil, Nokia Siemens Networks of May 16, 2008, a discussed in the introductory part of the description.
  • AU messages and steps described above are according to the protocol Proxy Mobile IPv6. In this standard, the particular physical implantations and respective definitions are discussed.
  • a wireless connection is used, e.g. WLAN, IEEE 802.11, or any other wireless data connection.
  • the MN can be a WLAN enabled notebook as known from the prior art.
  • the MAG (MAGs) and/or the LMA (LMAs) can be realized by a wireless router configured to realize the invention.
  • a server can be used, e.g. an IP server comprising memory for storing the respective mapping data.
  • the mapping data (MN->SMA) can also be stored within the MN as binding data list as defined in the RFC standards given above, e.g RFC 3775.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de transfert entre au moins deux domaines de mobilité réseau. Les domaines font partie d’un système doté d’ancres locales de mobilité et d’un nœud mobile susceptible d’être relié à chacun des domaines de mobilité réseau. Une première connexion est établie entre le nœud mobile et un premier domaine de mobilité réseau; et l’ancre locale de mobilité du premier domaine de mobilité réseau est désignée comme ancre de mobilité de session. Une deuxième connexion est établie entre le nœud mobile et un deuxième domaine de mobilité réseau parmi lesdits au moins deux domaines de mobilité réseau. L’étape d’établissement comporte une étape de localisation où une entité locale relevant du deuxième domaine de mobilité réseau localise l’ancre de mobilité de session à laquelle est affecté le nœud mobile. L’étape de localisation de l’ancre de mobilité de session comporte l’étape, exécutée par l’entité locale, consistant à récupérer une identification de l’ancre de mobilité de session. L’identification de l’ancre de mobilité de session est récupérée à partir d’au moins une source parmi : une émission envoyée par le nœud mobile au deuxième domaine de mobilité réseau, et une base de données comportant une identification de nœud mobile identifiant le nœud mobile. La base de données conserve l’identification de nœud mobile liée à une identification de l’ancre de mobilité de session dédiée au nœud mobile. L’entité locale comporte au moins un élément parmi : une passerelle d’accès pour mobiles du deuxième domaine de mobilité réseau, l’ancre locale de mobilité du deuxième domaine de mobilité réseau qui met à disposition une ancre locale de mobilité visitée, ou une autre entité relevant du deuxième domaine de mobilité réseau et reliée à celui-ci. L’invention concerne en outre une ancre locale de mobilité prévue pour récupérer l’identification selon l’invention. L'invention concerne de plus une unité de récupération servant à fournir des informations demandées relatives à l’ancre de mobilité de session à une ancre locale de mobilité qui les demande, l’unité de récupération comprenant la base de données. L'invention concerne enfin un progiciel informatique mettant en œuvre le procédé de l’invention lorsqu’il est exécuté sur un processeur programmable.
PCT/CN2008/001251 2008-07-01 2008-07-01 Mécanismes de transfert inter-domaines entre des domaines localisés de mobilité réseau basés sur un réseau Ceased WO2010000090A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2008/001251 WO2010000090A1 (fr) 2008-07-01 2008-07-01 Mécanismes de transfert inter-domaines entre des domaines localisés de mobilité réseau basés sur un réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2008/001251 WO2010000090A1 (fr) 2008-07-01 2008-07-01 Mécanismes de transfert inter-domaines entre des domaines localisés de mobilité réseau basés sur un réseau

Publications (2)

Publication Number Publication Date
WO2010000090A1 true WO2010000090A1 (fr) 2010-01-07
WO2010000090A8 WO2010000090A8 (fr) 2010-03-11

Family

ID=41465444

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/001251 Ceased WO2010000090A1 (fr) 2008-07-01 2008-07-01 Mécanismes de transfert inter-domaines entre des domaines localisés de mobilité réseau basés sur un réseau

Country Status (1)

Country Link
WO (1) WO2010000090A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1980206A1 (fr) 2002-05-09 2008-10-15 Lifescan, Inc. Dispositif d'analyse à procédure minimale
US9820928B1 (en) 2016-04-27 2017-11-21 Corn Products Development, Inc. Modified polysaccharides

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1524805A2 (fr) * 2003-10-18 2005-04-20 Samsung Electronics Co., Ltd. Système et procédé pour découvrir un point d'ancrage de mobilité et pour gérer la mobilité d'un noeud mobile dans un réseau mobile IP
EP1662723A1 (fr) * 2003-11-28 2006-05-31 Matsushita Electric Industrial Co., Ltd. Systeme de communication et procede de communication
WO2006120289A2 (fr) * 2005-05-11 2006-11-16 Nokia Siemens Networks Oy Procede permettant d'effectuer des transferts entre systemes dans un systeme de communications mobile
EP1782600A1 (fr) * 2004-07-20 2007-05-09 Nokia Corporation Systeme et noeud mobile associe, agent etranger et procede de transfert intercellulaire rapide assiste mobile ip a couche de liaison, d'un reseau a acces rapide a un reseau a acces lent
CN101047637A (zh) * 2006-06-30 2007-10-03 华为技术有限公司 接入路由器获取本地移动锚点信息的方法及其应用

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1524805A2 (fr) * 2003-10-18 2005-04-20 Samsung Electronics Co., Ltd. Système et procédé pour découvrir un point d'ancrage de mobilité et pour gérer la mobilité d'un noeud mobile dans un réseau mobile IP
EP1662723A1 (fr) * 2003-11-28 2006-05-31 Matsushita Electric Industrial Co., Ltd. Systeme de communication et procede de communication
EP1782600A1 (fr) * 2004-07-20 2007-05-09 Nokia Corporation Systeme et noeud mobile associe, agent etranger et procede de transfert intercellulaire rapide assiste mobile ip a couche de liaison, d'un reseau a acces rapide a un reseau a acces lent
WO2006120289A2 (fr) * 2005-05-11 2006-11-16 Nokia Siemens Networks Oy Procede permettant d'effectuer des transferts entre systemes dans un systeme de communications mobile
CN101047637A (zh) * 2006-06-30 2007-10-03 华为技术有限公司 接入路由器获取本地移动锚点信息的方法及其应用

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1980206A1 (fr) 2002-05-09 2008-10-15 Lifescan, Inc. Dispositif d'analyse à procédure minimale
US9820928B1 (en) 2016-04-27 2017-11-21 Corn Products Development, Inc. Modified polysaccharides

Also Published As

Publication number Publication date
WO2010000090A8 (fr) 2010-03-11

Similar Documents

Publication Publication Date Title
US11477634B2 (en) Home agent discovery upon changing the mobility management scheme
JP5072864B2 (ja) 通信システム及びドメイン管理装置
JP5238029B2 (ja) 通信ネットワーク間でのローミングの方法および装置
JP5048761B2 (ja) 通信セッションのためのロケーション・プライバシーとルート最適化とを同時に実施する方法及び装置
US20100103876A1 (en) Mobile terminal and communication management device
KR101031979B1 (ko) 통신 시스템
WO2010000174A1 (fr) PROCÉDÉ ET DISPOSITIF POUR L’ENREGISTREMENT, LA COMMUNICATION ET LE TRANSFERT INTERCELLULAIRE DE NœUDS MOBILES
WO2009116246A1 (fr) Procédé de communication, système de communication, nœud mobile, routeur d'accès
KR100973488B1 (ko) 고속 핸드오버 시스템 및 그 방법
US8824353B2 (en) Mobility route optimization in a network having distributed local mobility anchors
US20060280146A1 (en) Handover support for multiple types of traffic
WO2010000090A1 (fr) Mécanismes de transfert inter-domaines entre des domaines localisés de mobilité réseau basés sur un réseau
KR101037531B1 (ko) 무선 인터넷 시스템에서 통신 상태 정보를 이용한 소프트핸드오버 방법
Elfadil et al. Extended Proxy Mobile IPv6 Scheme Using Global Local Mobility Anchor.
KR101527611B1 (ko) 이종망 접속 방법
CN102281526B (zh) 移动通信控制方法、系统、映射转发服务器及接入路由器
Zhong et al. EFLoM: An Efficient Framework for Local Mobility
Homnan Possible solutions for IPv6 networks-based handover
CN101208930A (zh) 多宿主节点的移动性支持
Tarbani et al. Proposal of PMIPv6 Handover delay improvement with eMAG.
CN102281526A (zh) 移动通信控制方法、系统、映射转发服务器及接入路由器

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: 08773004

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08773004

Country of ref document: EP

Kind code of ref document: A1