[go: up one dir, main page]

WO2015180024A1 - Procédé et instrument de traitement de gestion de mobilité de réseau - Google Patents

Procédé et instrument de traitement de gestion de mobilité de réseau Download PDF

Info

Publication number
WO2015180024A1
WO2015180024A1 PCT/CN2014/078435 CN2014078435W WO2015180024A1 WO 2015180024 A1 WO2015180024 A1 WO 2015180024A1 CN 2014078435 W CN2014078435 W CN 2014078435W WO 2015180024 A1 WO2015180024 A1 WO 2015180024A1
Authority
WO
WIPO (PCT)
Prior art keywords
mri
tunnel router
eid
mapping
destination
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/CN2014/078435
Other languages
English (en)
Chinese (zh)
Inventor
薛开平
陈珂
吴义镇
魏鑫鹏
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
University of Science and Technology of China USTC
Original Assignee
Huawei Technologies Co Ltd
University of Science and Technology of China USTC
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, University of Science and Technology of China USTC filed Critical Huawei Technologies Co Ltd
Priority to PCT/CN2014/078435 priority Critical patent/WO2015180024A1/fr
Priority to CN201480029574.XA priority patent/CN105308928B/zh
Publication of WO2015180024A1 publication Critical patent/WO2015180024A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a processing method and device for network mobility management. Background technique
  • the user network In the Location-ID Separation Protocol (LISP), the user network is separated from the core network (usually the carrier network), and the IP address is decoupled into an Endpoint Identifier (EID) and a routing location according to different functions. Two types of logos (Routing Locator, RLOC).
  • the EID is only used for the host ID in the LISP network. It is usually represented by the local IP address of the host and does not have routing capability.
  • the two user networks pass the ingress tunnel router (ITR) and the egress tunnel router (Egress Tunnel Router). , ETR) establishes a tunnel between the transport networks to connect.
  • ITR ingress tunnel router
  • Egress Tunnel Router egress Tunnel Router
  • the user network implements the maintenance of the mapping information of the EID to the RLOC through a separate mapping system; the RLOC is a routable address of the entire network, and the data packets are routed and forwarded according to the RLOC in the core network, and are generally allocated by the ITR to which the host belongs.
  • the LISP protocol does not modify the terminal protocol stack, and implements mapping and data transmission on the network side.
  • a LISP mobile node Mobile Node, MN
  • MN LISP mobile node
  • xTR ingress/egress tunnel router
  • ESR ingress/egress tunnel router
  • Map-Server mapping server
  • Embodiments of the present invention provide a method and a device for processing network mobility management. After a MN mobile handover, a mobile router device (MRI) that manages multiple MNs is used. Instead of performing the network registration by the MN after the mobile switching, the signaling interaction in the network is effectively reduced, and the communication efficiency is improved.
  • MRI mobile router device
  • an embodiment of the present invention provides a mobile router device, where the mobile router device includes:
  • a receiving unit configured to receive an attach request message of the mobile node, where the attach request message includes a terminal identifier EID lx of the mobile node that accesses the mobile router device MRI, where the EID lx is used to indicate access to the MRI Terminal ID of the mobile node X;
  • a first processing unit configured to: if the MRI does not complete the attach, trigger the destination tunnel router to allocate a routing location identifier to the MRI, and trigger the mapping server to update and store the terminal identifier EIDi including the MRI and the corresponding to the Sprint 1
  • the MRI forwards the attach request message to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server pair.
  • mapping information corresponding to the EID lx stored in the respective ones is updated, and after the update, the mapping server stores mapping information of the EIDi and the allocated routing location identifier, where the mapping server and the destination tunnel router both store Mapping information of EIDi and the EID lx ;
  • a second processing unit configured to: if the MRI has completed attaching, forwarding the attach request message to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server to each store The mapping information corresponding to the EID lx is updated. After the update, the mapping server and the destination tunnel router both store the mapping between the EIDi and the EID lx .
  • the mobile node is moved by the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the mapping information that is stored by the mapping server and includes the routing location identifier further includes identifier bit information for identifying the routable capability; and the mapping server stores The mapping information including the EIDi and the EID lx further includes identifier bit information for identifying that there is no routable capability.
  • the mobile router device further includes:
  • a second receiving unit configured to receive a data packet sent by a mobile node, where the data packet is origin
  • the destination is the terminal identifier of the mobile node, and the destination address is the terminal identifier of the peer node;
  • the forwarding unit is configured to forward the data packet to the destination tunnel router, so that the destination tunnel router encapsulates the data packet
  • the source address of the encapsulated data packet is a routing location identifier corresponding to the mobile node, and the destination address is a routing location identifier corresponding to the peer node.
  • the embodiment of the present invention provides a tunnel router, where the tunnel router includes: a detecting unit, configured to detect whether the mobile router device MRI is attached;
  • a first processing unit configured to: if the MRI does not complete the attach, allocate a routing location identifier to the MRI, and cause the mapping server to update the stored mapping of the terminal identifier EIDi of the MRI and the routing location identifier corresponding to the EIDi
  • the attachment of the MRI is completed, and an attach request message of the mobile node forwarded by the MRI is received, where the attach request message includes a terminal identifier EID lx of the mobile node that accesses the MRI, where the EID lx is used.
  • mapping server Representing the terminal identifier of the mobile node X that accesses the MRI, updating the mapping information corresponding to the stored EID lx , and triggering the mapping server to update the mapping information corresponding to the stored EID lx .
  • the mapping server And storing mapping information of the EID! and the allocated routing location identifier, where the mapping server and the destination tunnel router store mapping information of the UI and the EID lx ;
  • a second processing unit configured to: if the MRI has completed attaching, receive the attach request message forwarded by the MRI, update the stored mapping information corresponding to the EID lx , and trigger the mapping server to update the stored Mapping information corresponding to the EID lx , after the update, the mapping server and the destination tunnel router store mapping information of the EIDi and the EID lx ;
  • the mobile node is moved by the management domain of the source tunnel router to the management domain of the tunnel router.
  • the mapping information that is included in the mapping server that is included in the mapping location identifier includes: identifier bit information that is used to identify the routable capability;
  • the mapping information including the information and the EID lx further includes identifier bit information for identifying that the RB is not routable.
  • the tunnel router further includes:
  • a receiving unit configured to receive a data packet sent by the mobile node that is forwarded by the MRI, where a source address of the data packet is a terminal identifier of the mobile node, and the destination address is a terminal identifier of the peer node;
  • the encapsulating unit is configured to encapsulate the data packet, where the source address of the encapsulated data packet is a routing location identifier allocated by the tunnel router for the MRI, and the destination address is a routing location identifier of the peer tunneling router
  • the peer node is located in the management domain of the peer tunnel router, and the route location identifier of the peer tunnel router is that the tunnel router is from the mapping server according to the terminal identifier of the peer node. Query obtained;
  • a forwarding unit configured to send the encapsulated data packet to the peer tunnel router.
  • an embodiment of the present invention provides a tunnel router, where the tunnel router includes: a notification unit, configured to: after a mobile node switches from an administrative domain of the tunnel router to a management domain of another tunnel router, The tunnel router to which the peer node that the mobile node communicates sends a notification message, where the notification message is used to notify the tunnel router to which the peer node that communicates with the mobile node belongs to obtain the updated mapping to the mapping server. information.
  • the embodiment of the present invention provides a mapping server, where the mapping server includes: an indication unit, configured to enable the destination tunnel router to detect whether the mobile router device MRI is completed with a first processing unit, if the MRI is not completed. Attaching, the destination tunneling router allocates a routing location identifier to the MRI, and updates the stored mapping information including the terminal identifier EIDi of the MRI and the routing location corresponding to the EIDi, and then completes the attachment of the MRI.
  • an indication unit configured to enable the destination tunnel router to detect whether the mobile router device MRI is completed with a first processing unit, if the MRI is not completed. Attaching, the destination tunneling router allocates a routing location identifier to the MRI, and updates the stored mapping information including the terminal identifier EIDi of the MRI and the routing location corresponding to the EIDi, and then completes the attachment of the MRI.
  • the attach request message includes a terminal identifier EID lx of the mobile node accessing the MRI, where the EID lx is used to indicate Accessing the terminal identifier of the mobile node X of the MRI, updating the stored mapping information corresponding to the EID lx , and triggering the destination tunnel router to update the mapping information corresponding to the stored EID lx , after updating, the mapping server the £ 10 1 and storing routing information mapping the allocated location identifier, the mapping server and the Tunnel routers store the mapping information of EIDi the EID lx;
  • a second processing unit configured to: if the MRI has completed attaching, receive a request message generated by the destination tunnel router after receiving an attach request message of the mobile node, update the stored mapping information corresponding to the EID lx , and trigger The destination tunneling router updates the mapping information corresponding to the stored EID lx , and after the update, the mapping server and the destination tunnel router store mapping information of the EIIi and the EID lx ;
  • the mobile node is moved by the management domain of the source tunnel router to the destination tunnel route.
  • the administrative domain of the device is defined by the management domain of the source tunnel router to the destination tunnel route.
  • the mapping information that is included in the mapping server that is included in the mapping location identifier includes: identifier bit information that is used to identify the routable capability;
  • the mapping information including the EIDi and the EID lx further includes identifier bit information for identifying that there is no routable capability.
  • mapping server further includes:
  • a receiving unit configured to receive a query request sent by the destination tunnel router, where the query request is sent after the destination tunnel router receives the data packet sent by the mobile node forwarded by the MRI, and the source of the data packet
  • the address is a terminal identifier of the mobile node
  • the destination address is a terminal identifier of the peer node
  • the query request includes a terminal identifier of the peer node
  • a query unit configured to query, in the stored mapping information, the routing location identifier of the peer tunnel router corresponding to the terminal identifier of the peer node, and return the routing location identifier to the destination tunnel router according to the terminal identifier of the peer node
  • the peer node is located in a management domain of the peer tunnel router.
  • an embodiment of the present invention provides a method for processing network mobility management, where the method includes:
  • the mobile router device MRI receives the attach request message of the mobile node, where the attach request message includes the terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the mobile node X accessing the MRI. Terminal identification;
  • the MRI triggers the destination tunnel router to allocate a routing location identifier to the MRI and triggers the mapping server to update the stored terminal identifier EIDi containing the MRI and the routing location identifier corresponding to the Sprint 1
  • the MRI is attached, and the MRI forwards the attach request message to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server to store the respective The mapping information corresponding to the EID lx is updated, and after the updating, the mapping server stores mapping information of the EIDi and the allocated routing location identifier, where the mapping server and the destination tunnel router store the EIDi and the The mapping information of the EID lx ;
  • the MRI forwards the attach request message to the destination tunnel router to cause the destination tunnel router to trigger the destination tunnel router and the mapping
  • the server updates the mapping information corresponding to the EID lx that is stored by the server. After the update, the mapping server and the destination tunnel router store the mapping information of the EII and the EID lx .
  • the management domain of the source tunnel router moves to the management domain of the destination tunnel router.
  • the mapping information that is included in the map server that is included in the mapping location identifier includes: identifier bit information for identifying the routable capability;
  • the mapping information including the EIDi and the EID lx further includes identifier bit information for identifying that there is no routable capability.
  • the method further includes:
  • the MRI receives a data packet sent by a mobile node, where a source address of the data packet is a terminal identifier of the mobile node, and a destination address is a terminal identifier of the peer node;
  • the MRI forwards the data packet to the destination tunnel router, so that the destination tunnel router encapsulates the data packet, and the source address of the encapsulated data packet is a routing location identifier corresponding to the mobile node.
  • the destination address is the route location identifier corresponding to the peer node.
  • an embodiment of the present invention provides a method for processing network mobility management, where the method includes:
  • the destination tunnel router detects whether the mobile router device MRI is attached
  • the destination tunnel router allocates a routing location identifier to the MRI and causes the mapping server to update the stored mapping information of the terminal identifier EIDi of the MRI and the routing location identifier corresponding to the £.
  • the destination tunnel router receives an attach request message of the mobile node forwarded by the MRI, where the attach request message includes a terminal identifier EID lx of the mobile node that accesses the MRI,
  • the EID lx is used to indicate the terminal identifier of the mobile node X that accesses the MRI, and the destination tunnel router updates the stored mapping information corresponding to the EID lx and triggers the mapping server to update the stored corresponding value of the Sprint 1 Mapping information, after the update, the mapping server stores mapping information of the EIDi and the allocated routing location identifier, where the mapping server and the destination tunnel router store mapping information of the EIDi and the EID lx ;
  • the destination tunnel router receives the attach request message forwarded by the MRI, and the destination tunnel router updates the stored mapping corresponding to the EID lx .
  • the information is triggered by the mapping server to update the stored mapping information corresponding to the EID lx .
  • the mapping server and the destination tunnel router both store the mapping between the EIDi and the EID lx .
  • the mobile node is moved by the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the mapping information that is included in the mapping server that is included in the mapping location identifier further includes identifier bit information that is used to identify the routable capability;
  • the mapping information including the EIDi and the EID lx further includes identifier bit information for identifying that there is no routable capability.
  • the method further includes:
  • the destination tunnel router receives the data packet sent by the mobile node that is forwarded by the MRI, the source address of the data packet is the terminal identifier of the mobile node, and the destination address is the terminal identifier of the peer node;
  • the destination tunnel router encapsulates the data packet, and the source address of the encapsulated data packet is a routing location identifier assigned by the destination tunnel router to the MRI, and the destination address is a routing location of the peer tunnel router.
  • An identifier of the peer node is located in a management domain of the peer tunnel router, and a route location identifier of the peer tunnel router is that the destination tunnel router according to the terminal identifier of the peer node from the mapping Queryed by the server;
  • a seventh aspect of the present invention provides a method for processing network mobility management, where the method includes:
  • the source tunnel router After the mobile node switches from the management domain of the source tunnel router to the management domain of the other tunnel router, the source tunnel router sends a notification message to the tunnel router to which the peer node that communicates with the mobile node belongs, where the notification message is used. And notifying the tunnel router to which the peer node that communicates with the mobile node belongs to obtain updated mapping information to the mapping server.
  • an embodiment of the present invention provides a method for processing network mobility management, where the method includes:
  • the mapping server causes the destination tunnel router to detect whether the mobile router device MRI completes attachment; if the MRI does not complete attachment, the mapping server makes the destination tunnel router After the MRI allocates the routing location identifier and updates the stored mapping information including the terminal identifier EIIi of the MRI and the routing location corresponding to the EIDi, the MRI attachment is completed, and the mapping server receives the destination tunnel router and receives the mapping.
  • the mapping server after updating the stored EID and the mapping information corresponding to the trigger lx tunnel router updates the map information stored EID lx corresponding to the destination, updating the mapping server stores the Mapping information of the EIDi and the allocated routing location identifier, where the mapping server and the destination tunneling router store mapping information of the EIDi and the EID lx ;
  • the mapping server receives the request message generated by the destination tunnel router after receiving the attach request message of the mobile node, and the mapping server updates the stored mapping information corresponding to the EID lx and And triggering, by the destination tunneling router, the stored mapping information corresponding to the EID lx , and after the updating, the mapping server and the destination tunneling router respectively store mapping information of the EIIi and the EID lx ;
  • the mobile node is moved by the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the mapping information that is included in the mapping server that is included in the mapping location identifier includes: identifier bit information that is used to identify the routable capability;
  • the mapping information including the EIDi and the EID lx further includes identifier bit information for identifying that there is no routable capability.
  • the method further includes:
  • the mapping server receives the query request sent by the destination tunnel router, where the query request is sent after the destination tunnel router receives the data packet sent by the mobile node forwarded by the MRI, and the source address of the data packet a terminal identifier of the mobile node, where the destination address is a terminal identifier of the peer node, and the query request includes a terminal identifier of the peer node;
  • the mapping server queries, according to the terminal identifier of the peer node, the routing location identifier of the peer tunnel router corresponding to the terminal identifier of the peer node, and returns the routing location identifier to the destination tunnel router;
  • the peer node is located in a management domain of the peer tunnel router.
  • the embodiment of the present invention provides a mobile router device, where the mobile router device includes: a communication interface, a memory, and a processor; the communication interface is configured to communicate with a network element, and the memory is used to store a computer code; The processor executes the computer code for:
  • the attach request message includes a terminal identifier EID lx of the mobile node that accesses the MRI, where the EID lx is used to indicate a terminal identifier of the mobile node X that accesses the MRI;
  • the destination tunnel router is triggered to allocate the routing location identifier to the MRI, and triggers the mapping server to update the stored mapping information of the terminal identifier EIDi of the MRI and the routing location identifier corresponding to the Sprint 1
  • the attach request message is forwarded to the destination tunnel router, so that the destination tunnel router triggers the mapping between the destination tunnel router and the mapping server to the respective stored EID lx .
  • the mapping server stores the mapping information of the EIDi and the allocated routing location identifier, and the mapping server and the destination tunnel router both store mapping information of the EIDi and the EID lx . ;
  • mapping server and the destination tunnel router store mapping information of the EIIi and the EID lx ;
  • the mobile node is moved by the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the mapping information that is included in the mapping server that is included in the mapping location identifier includes: identifier bit information for identifying the routable capability;
  • the mapping information including the EIDi and the EID lx further includes identifier bit information for identifying that there is no routable capability.
  • the executing the computer code by the processor is further used to:
  • a source address of the data packet is a terminal identifier of the mobile node, and a destination address is a terminal identifier of the peer node;
  • the destination tunnel router Forwarding the data packet to the destination tunnel router, so that the destination tunnel router encapsulates the data packet, and the source address of the encapsulated data packet is a route corresponding to the mobile node Location identifier, the destination address is the routing location identifier corresponding to the peer node.
  • an embodiment of the present invention provides a tunnel router, where the tunnel router includes: a communication interface, a memory, and a processor; the communication interface is configured to communicate with a network element, and the memory is configured to store a computer code; The processor executes the computer code for:
  • the routing location identifier is allocated to the MRI, and the mapping server updates the stored mapping information including the terminal identifier EIDi of the MRI and the routing location identifier corresponding to the EIDi, and then completes the MRI.
  • Attaching receiving an attach request message of the mobile node forwarded by the MRI, the attach request message includes a terminal identifier EID lx of the mobile node accessing the MRI, where the EID lx is used to indicate access to the MRI x is the terminal identification of the mobile node, updating the stored map information corresponding to the EID lx and triggering the EID lx mapping information corresponding to the mapping server updates the stored, updated, the server stores the mapping of the EIDi And mapping information of the assigned route location identifier, where the mapping server and the destination tunnel router store mapping information of the EIIi and the EID lx ;
  • the mapping server and the destination tunnel router both store mapping information of the EIIi and the EID lx ;
  • the mobile node is moved by the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the mapping information that is included in the mapping server that is configured to include the routing location identifier further includes identifier bit information that is used to identify the routable capability;
  • the mapping information including the EIDi and the EID lx further includes identifier bit information for identifying that there is no routable capability.
  • the executing the computer code by the processor is further used to:
  • the source address of the data packet is a terminal identifier of the mobile node, and the destination address is a terminal identifier of the opposite node;
  • the source address of the encapsulated data packet is the routing location identifier assigned by the destination tunnel router to the MRI, and the destination address is the path of the peer tunnel router.
  • the location identifier is located in the management domain of the peer tunnel router, and the route location identifier of the peer tunnel router is the destination tunnel router according to the terminal identifier of the peer node.
  • the encapsulated data packet is sent to the peer tunnel router.
  • an embodiment of the present invention provides a tunnel router, where the tunnel router includes: a communication interface, a memory, and a processor; the communication interface is configured to communicate with a network element, and the memory is used to store a computer code; The processor executes the computer code for:
  • the notification message is used to notify the The tunnel router to which the correspondent node that communicates with the mobile node belongs acquires updated mapping information to the mapping server.
  • mapping server includes: a communication interface, a memory, and a processor; the communication interface is configured to communicate with a network element, and the memory is used to store a computer code; The processor executes the computer code for:
  • the destination tunnel router is configured to allocate a routing location identifier to the MRI, and update the stored mapping information including the terminal identifier EIDi of the MRI and the routing location corresponding to the EIDi.
  • Attaching the MRI receiving the request message generated by the destination tunnel router after receiving the attach request message of the mobile node, where the attach request message includes the terminal identifier EID lx of the mobile node accessing the MRI, representing £ 10 1 to said access node the mobile terminal X MRI identification, updating the mapping information stored in the corresponding EID lx and trigger the tunnel router updates the stored mapping information corresponding to the destination EID lx,
  • the mapping server stores mapping information of the EIDi and the allocated routing location identifier, where the mapping server and the destination tunnel router store mapping information of the EIDi and the EID lx ;
  • the MRI has completed the attaching, receiving a request message generated by the destination tunnel router after receiving the attach request message of the mobile node, updating the stored mapping information corresponding to the réelle 1 and triggering the destination tunnel router to update
  • the mapping information corresponding to the stored EID lx is stored, and the mapping server and the destination tunnel router store mapping information of the EIDi and the EID lx ;
  • the mobile node is moved by the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the mapping information that is included in the mapping server that is included in the mapping location identifier includes: identifier bit information that is used to identify the routable capability;
  • the information about the EIDi and the EIDiJ ⁇ mapping information further includes identifier bit information for identifying that there is no routable capability.
  • the processor executing the computer code is further configured to:
  • the query request is sent after the destination tunnel router receives the data packet sent by the mobile node forwarded by the MRI, and the source address of the data packet is the mobile a terminal identifier of the node, where the destination address is a terminal identifier of the peer node; the query request includes a terminal identifier of the peer node;
  • the mobile router device receives the attach request message of the mobile node, and if the mobile router device does not complete the attach, the tunnel router causes the mobile router device to map to the mobile router first. After the server completes the attach, the tunnel router receives the attach request message of the mobile node forwarded by the mobile router device, and then causes the mobile node to complete the attach to the mapping server through the mobile router device. If the mobile router device completes the attach, the tunnel router receives the mobile node forwarded by the mobile router device. After the attach request message, the mobile node completes the attach to the mapping server through the mobile router device.
  • the mobile router device that manages multiple MNs replaces the MN after the mobile switching to perform network registration, which effectively reduces signaling interaction in the network and improves communication efficiency.
  • FIG. 1 is a schematic structural diagram of an implementation of an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of an MRI attachment according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart 1 of a MN attached by an MRI according to an embodiment of the present invention
  • FIG. 4 is a schematic structural diagram 1 of a mobile router device according to an embodiment of the present invention
  • FIG. 5 is a second schematic diagram of a process of attaching a MN through an MRI according to an embodiment of the present invention
  • FIG. 6 is a schematic structural diagram 2 of a mobile router device according to an embodiment of the present invention
  • FIG. 7 is a schematic structural diagram 1 of a tunnel router according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram 2 of a tunnel router according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart of sending data to a MN according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram 3 of a tunnel router according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram 1 of a mapping server according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram 2 of a mapping server according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic flowchart 1 of a method for processing network mobility management according to an embodiment of the present invention
  • FIG. 14 is a schematic flowchart 2 of a method for processing network mobility management according to an embodiment of the present invention
  • FIG. FIG. 16 is a flow chart 4 of a method for processing network mobility management according to an embodiment of the present invention
  • FIG. 17 is a schematic flowchart of a method for processing network mobility management according to an embodiment of the present invention
  • FIG. 18 is a schematic flowchart of a method for processing a network mobility management according to an embodiment of the present invention
  • FIG. 19 is a schematic structural diagram of a mobile router device according to an embodiment of the present invention
  • FIG. 21 is a schematic structural diagram 5 of a tunnel router according to an embodiment of the present disclosure.
  • FIG. 22 is a schematic structural diagram 3 of a mapping server according to an embodiment of the present invention. detailed description
  • xTR1 manages the terminals and MRIs connected to the user network, and the sending or receiving of data packets in the user network must be encapsulated and decapsulated by xTR1.
  • MRI can be regarded as a normal MN, but it needs to provide xTR1 with EID information of multiple MNs it manages.
  • MRI is the management node of the whole mobile domain of the domain, with xTRl Bind registration function.
  • the Correspondent Node (CN) is located in the xTR2 domain and is a node that communicates with multiple MNs.
  • Map-Resolver is a mapping parser, Map-Server, which is used to store mapping information of EID-RLOC class and EID-EID class.
  • the mapping information of the EID-EID class between the MRI and the plurality of MNs is stored in the xTR.
  • the MRI initiates an attach request (MRI Attachment) to xTR1, indicating that the current access to the xTRl: RLO domain.
  • the attach request contains the EID of the MRI l t3
  • the MN (EID) is initially connected to the MRI domain, and initiates an attach request to the MRI.
  • the MRI forwards the attach request initiated by the mobile node to xTR1.
  • xTRl After receiving the mobile node attach request forwarded by the MRI, xTRl registers with the Map-Server. After receiving the registration message, Map-Server adds the mapping entries: ⁇ map:EIDminister, EIDj , 1>, and returns a Map-Notify message to xTR1 to confirm the attachment success.
  • the MN completes the attachment to the Map-Server in the core network through MRI.
  • the Map-Server stores the mapping information of the EID-RLOC class and the EID-EID class
  • the XTR1 stores the mapping information.
  • the mapping entry containing the routing location identifier stored in the Map-Server includes the identifier bit information for identifying the routable capability, and the EIDi and the mobile node MN including the MRI stored in the Map-Server.
  • the terminal identifier EIDiJ ⁇ mapping information includes identifier bit information for identifying that there is no routable capability. As shown in FIG.
  • the identifier bit information for identifying the routable capability may be 0, for
  • the identifier bit information identifying that there is no routable capability may be 1, for example, a mapping entry of xTR1 and xTR2 stored in the Map-Server ( ⁇ map: EID 1 , RLOd , 0>, ⁇ map: EID 2 , RLOC 2 , 0>); for example, the EIDi containing the MRI stored in the Map-Server and the terminal identifier EID lx of the MN accessing the MRI do not include the mapping entry of the routing location ( ⁇ map: EID din, EID ⁇ 1> , ⁇ map:EID 12 , EID ⁇ 1>)
  • Map-Server can also store mapping information of MNs registered directly to Map-Server through xTR1, such as Map. xTRl direct access to the stored -Server MN (EID 14) of enantiomer Information
  • the embodiment of the present invention provides a mobile router device 10.
  • the mobile router device 10 includes: a first receiving unit 11, a first processing unit 12, and a second processing unit 13.
  • the first receiving unit 11 is configured to receive an attach request message of the mobile node.
  • the attach request message includes a terminal identifier EID lx of the mobile node accessing the mobile router device MRI, and the EID lx is used to indicate the terminal identifier of the mobile node X accessing the MRI, and the mobile node is moved from the management domain of the source tunnel router to the tunnel router. Administrative domain.
  • multiple MNs (EID Arlington, EID 12 , EID 13 ) need to register with the Map-Server in the core network, and the MRI receives the attachment of multiple MNs (EIDedia, EID 12 , EID 13 ). Requesting subsequent forwarding, the MRI can connect multiple MNs and manage their connection to the xTR.
  • the first processing unit 12 is configured to: if the MRI does not complete the attach, trigger the destination tunnel router to allocate a routing location identifier to the MRI, and trigger the mapping server to update the stored mapping information of the routing location identifier corresponding to the MRI terminal identifier EID ⁇ n EIDi.
  • the MRI forwards the attach request message to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server to update the mapping information corresponding to the stored EID lx .
  • the mapping server stores the EIDi and the allocated information.
  • the mapping information of the routing location identifier, the mapping server and the destination tunneling router all store mapping information of EIDi and EID lx .
  • the MRI and the plurality of MNs managed by the MRI move to the new user network, for example, the user network 1 managed by the xTR1
  • the MRI as shown in FIG. 2 is first attached to the Map-Server, and the MRI is attached. Then, the MN attached to the Map-Server as shown in FIG. 3 is executed.
  • the second processing unit 13 is configured to: if the MRI has completed the attachment, forward the attach request message to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server to update the mapping information corresponding to the stored EID lx , after the update,
  • the mapping server and the destination tunnel router both store mapping information of EIDi and EID lx .
  • the MRI has completed the attachment, and only needs to establish the mapping information of the EID-EID between the new MN and the MRI, and store the mapping entry correspondingly.
  • Map-Server and xTRl are post-attached.
  • the xTR-N After receiving the mobile node attach request sent by the MRI EIDi ⁇ *, the xTR-N performs a mapping entry (MAP) update to the Map-Server.
  • MAP mapping entry
  • the mobile router device 10 may further include: a second receiving unit 14 and a forwarding unit 15.
  • the second receiving unit 14 is configured to receive a data packet sent by a mobile node, where a source address of the data packet is a terminal identifier of the mobile node, and a destination address is a terminal identifier of the peer node.
  • the second receiving unit 14 receives the data packet sent by the MN (EID toast) under the xTR1 management domain to the CN (EID 2 ) under the xTR2 management domain, and the source address of the data packet is the terminal identifier EID of the MN, The destination address is the terminal identifier EID 2 of the CN.
  • the forwarding unit 15 is configured to forward the data packet to the destination tunnel router, so that the destination tunnel router encapsulates the data packet, and the source address of the encapsulated data packet is a routing location identifier corresponding to the mobile node, and the destination address is a route corresponding to the peer node. Location identifier.
  • the forwarding unit 15 forwards the data packet received by the second receiving unit 14 to the xTR1, and the xTR1 encapsulates the data packet.
  • the source address of the encapsulated data packet is the routing location identifier RLOd corresponding to the MN (EID).
  • the destination address is the routing location identifier RLOC 2 corresponding to CN (EID 2 ).
  • the mobile router device receives the attach request message of the mobile node after the mobile node moves, and triggers the tunnel router to make the mobile router device attach to the mapping server first, and then tunnels to the tunnel if the mobile router device does not complete the attaching.
  • the router forwards the attach request message of the mobile node to enable the mobile node to complete the attach to the mapping server through the mobile router device, and if the mobile router device completes the attach, forward the attach request message of the mobile node to the tunnel router, so that the mobile node completes the attach to the mapping server through the mobile router device.
  • the mobile router device managing multiple MNs performs network registration instead of the mobile switched MN, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • the embodiment of the present invention provides a tunnel router 20.
  • the tunnel router 20 includes: a detecting unit 21, a first processing unit 22, and a second processing unit 23.
  • the mobile node is moved by the management domain of the source tunnel router to the management domain of the tunnel router 20.
  • the detecting unit 21 is configured to detect whether the mobile router device MRI completes attachment.
  • the detecting unit 21 can know whether the attachment has been completed by querying whether to store the mapping information of the EID of the MRI.
  • the first processing unit 22 is configured to: if the MRI does not complete the attach, allocate a routing location identifier to the MRI, and enable the mapping server to update the stored route corresponding to the MRI terminal identifiers EIDi and EIDi. After the mapping information of the location identifier is completed, the attachment of the MRI is completed, and the attach request message of the mobile node forwarded by the MRI is received.
  • the attach request message includes the terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the mobile node X accessing the MRI.
  • the terminal identifier is used to update the mapping information corresponding to the stored EID lx and trigger the mapping server to update the mapping information corresponding to the stored EID lx .
  • the mapping server stores the mapping information of the EIDi and the assigned routing location identifier, and the mapping server and the destination tunnel router.
  • the mapping information of EIDi and EID lx is stored.
  • the MRI and the plurality of MNs managed by the MRI move to the new user network, for example, the user network 1 managed by the xTR1
  • the MRI as shown in FIG. 2 is first attached to the Map-Server, and the MRI is attached. Then, the MN attached to the Map-Server as shown in FIG. 3 is executed.
  • the MRI After the second processing unit 23, for attachment has been completed if the MRI, the MRI receiving an attach request message forwarded to update the mapping information corresponding to the stored EID lx and trigger mapping server updates the stored EID lx mapping information corresponding to the updated mapping Both the server and the destination tunnel router store the mapping information of EIDi and EID lx .
  • Map-Server and xTRl are post-attached. Specifically, it can be implemented by referring to the process shown in FIG. 5.
  • the tunnel router 20 may further include:
  • the receiving unit 24, the encapsulating unit 25, and the forwarding unit 26 are identical to the receiving unit 24, the encapsulating unit 25, and the forwarding unit 26.
  • the receiving unit 24 is configured to receive the data packet sent by the mobile node forwarded by the MRI, where the source address of the data packet is the terminal identifier of the mobile node, and the destination address is the terminal identifier of the opposite node.
  • the receiving unit 24 receives the MRI-forwarded MN (EID refrain) packet to be sent to the CN (EID 2 ) under the xTR2 management domain, the data packet
  • the source address is the terminal identifier EID of the MN
  • the destination address is the terminal identifier EID 2 of the CN.
  • the tunnel router in the embodiment of the present invention may also receive a data packet that needs to be sent to the opposite node by the mobile node directly managed by the tunnel router.
  • the encapsulating unit 25 is configured to encapsulate the data packet, where the source address of the encapsulated data packet is a routing location identifier assigned by the tunnel router to the MRI, and the destination address is a routing location identifier of the peer tunnel router, where the peer node is located Peer tunnel router in the management domain, peer tunnel router The routing location identifier is obtained by the tunnel router from the mapping server according to the terminal identifier of the peer node.
  • the MN (EID 0.) under the xTR1 management domain sends data to the correspondent node CN (EID 2 ) under the peer tunneling router xTR2 management domain, and xTR1 queries the mapping server Map-Server for CN (EID 2 ) location identifier corresponding routing xTR2 i.e. route location identification RLOC 2, then xTRl encapsulating the data packet, the source address of the packet is encapsulated MN (EID ”) corresponding to the route location identifier i.e. the route location identifier xTRl RLOd, the destination address is the routing location identifier RLOC 2 corresponding to CN (EID 2 ).
  • the forwarding unit 26 is configured to send the encapsulated data packet to the peer tunnel router.
  • xTRl sends the encapsulated packet to xTR2.
  • the tunnel router xTR2 needs to encapsulate the data packet after the CN (EID 2 ) sends the data packet to the MN (EID cinnamon), and the encapsulated data packet needs CN (EID 2 ) and MN (EID mild) respectively.
  • the routing location identifier is obtained by querying the routing location identifier of the peer tunneling router xTR-N according to the terminal identifier EID of the opposite node MN (EID).
  • Map-Server queries the mapping table of EID, and the query process is as follows:
  • the identifier bit is the second identifier 1
  • the outer header of the data packet is encapsulated and sent to the xTR-N.
  • the encapsulated source and destination addresses are the routable addresses RLOC 2 and RLOC 3 respectively .
  • the MN acts as its own xTR, and all the outgoing data packets are encapsulated and transmitted by using its own RLOC; the MN acts as its own EID prefix xTR, which is responsible for registering its own RLOC changes with the MS. And update the remote cache to its original mapping information ITR, proxy entry tunnel router (Proxy-ITR, PITR).
  • the xTR After the MN roams to the new xTR, the xTR allocates a regular global RLOC to the MN for encapsulating the outer-header to be used in the core network; and assigns the local ROLC to the MN using the xTR's own EID prefix, Used to encapsulate the middle-header used within the site.
  • the data packet is encapsulated three times, three other sub-header 1 J is the out-header, middle-header, inner-header (the EID of the sending node - the EID of the receiving node) so that the packets are forwarded between the xTRs.
  • the data packet is encapsulated twice (two-layer out-header, inner-header), which can reduce the number of times of encapsulation and improve the efficiency of data communication.
  • the tunnel router provided by the embodiment of the present invention first detects whether the mobile router device completes attachment, and if the mobile router device does not complete attachment, the mobile router device completes attachment to the mapping server, and then receives the mobile node attachment request message forwarded by the mobile router device. Afterwards, the mobile node completes the attaching to the mapping server through the mobile router device, and if the mobile router device completes the attach, receives the attach request message of the mobile node forwarded by the mobile router device, and then causes the mobile node to complete the attaching to the mapping server through the mobile router device.
  • the mobile router device that manages multiple MNs replaces the mobile switched MN to perform network registration, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • the embodiment of the present invention provides a tunnel router 200.
  • the tunnel router 200 includes: a notification unit 210.
  • the notification unit 210 is configured to: after the mobile node switches from the management domain of the tunnel router to the management domain of the other tunnel router, send a notification message to the tunnel router to which the correspondent node that communicates with the mobile node belongs, and the notification message is used for notification and movement.
  • the tunnel router to which the peer node that the node communicates acquires the updated mapping information from the mapping server.
  • the xTR can record the data packet source and destination address forwarded to the core network in a short time, for example, as shown in FIG. 5, when the MN or MRI carries the switched handover from the xTR-P domain to the xTR with its managed MN. -N domain, in order to maintain continuous data communication between the MN and the CN after the mobile handover, after the handover process occurs, the data packet in the network link arrives at the xTR-P before the MN or MRI handover, xTR-P The data packet is searched for the destination port's forwarding port failed, and it is determined that the MN has been removed from the xTR-P.
  • the xTR-P detects the MRI and the MN leaving event in the management domain, and requests the mapping request.
  • the Solicit Map Request (SMR) message sets a preset option to notify other xTRs that the MN has sent data in the MRI management domain within one minute, and informs other xTRs that the new mapping entry should be retrieved from the Map-Server, wherein the preset option may be Is the default flag, such as 0.
  • the tunnel router After the mobile node switches from the management domain of the tunnel router to the management domain of another tunnel router, the tunnel router sends a notification message to the tunnel router to which the peer node that communicates with the mobile node belongs.
  • the notification message is used to notify the tunnel router to which the peer node that has communicated with the mobile node belongs to obtain the updated mapping information from the mapping server. In this way, the tunnel router can learn and update the mapping information about the mobile node more quickly when the mobile node moves and the mapping information changes.
  • the embodiment of the present invention provides a mapping server 30.
  • the mapping server 30 includes: an indication unit 31, a first processing unit 32, and a second processing unit 33.
  • the mobile node is moved from the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the indicating unit 31 is configured to enable the destination tunnel router to detect whether the mobile router device MRI is attached.
  • the instructing unit 31 can cause the tunneling router xTR to query whether to store the mapping information of the EID of the MRI by sending signaling to know whether the attachment has been completed.
  • the first processing unit 32 is configured to: after the MRI does not complete the attachment, enable the destination tunnel router to allocate a routing location identifier to the MRI and update the mapping information of the stored routing location corresponding to the MRI terminal identifier EID ⁇ n réelle 1 to complete the MRI.
  • Attachment receiving a request message generated by the destination tunnel router after receiving the attach request message of the mobile node, where the attach request message includes the terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the mobile access MRI
  • the terminal identifier of the node x updates the mapping information corresponding to the stored Mé 1 and triggers the mapping information corresponding to the stored EID lx of the destination tunnel router.
  • the mapping server stores the mapping information of the EIDi and the assigned routing location identifier, and maps the server. Both the destination tunnel router and the destination tunnel router store mapping information of EIDi and EID lx .
  • the MRI and the plurality of MNs managed by the MRI move to the new user network, for example, the user network 1 managed by the xTR1
  • the MRI as shown in FIG. 2 is first attached to the Map-Server, and the MRI is attached.
  • the MN is attached to the Map-Server as shown in FIG. 3, where the request message generated by the destination tunnel router after receiving the attach request message of the mobile node may be A Map-Register message, such as the Map-Register message sent by xTR1 to the mapping server in Figure 2 and Figure 3.
  • the second processing unit 33 is configured to: if the MRI has completed the attaching, receive the request message generated by the destination tunnel router after receiving the attach request message of the mobile node, update the mapping information corresponding to the stored EID lx , and trigger the destination tunnel router to update the storage.
  • the mapping information corresponding to the EID lx is updated.
  • the mapping server and the destination tunnel router store the mapping information of the EIDi and the EID lx .
  • Map-Server and xTRl are post-attached. Specifically, it can be implemented by referring to the process shown in FIG. 5.
  • the mapping server 30 may further include: a receiving unit 34 and a query unit 35.
  • the receiving unit 34 is configured to receive a query request sent by the destination tunnel router, where the query request is sent after the destination tunnel router receives the data packet sent by the mobile node forwarded by the MRI, and the source address of the data packet is the terminal identifier of the mobile node, and the destination The address is the terminal identifier of the peer node; the query request includes the terminal identifier of the peer node.
  • mapping server receives the query request.
  • the querying unit 35 is configured to query, in the stored mapping information, the routing location identifier of the peer tunneling router corresponding to the terminal identifier of the peer node, and return the routing location identifier to the destination tunnel router, where the peer end The node is located in the management domain of the peer tunnel router.
  • mapping queries the server to obtain the corresponding EID 2 in the mapping information storage location identifier in the routing RLOC 2, then routing xTR2 location query to get back to the identification RLOC 2 xTRl o
  • the mapping server provided by the embodiment of the present invention first enables the destination tunnel router to detect whether the mobile router device completes attachment. If the mobile router device does not complete the attachment, the mobile router device is first attached, and then the destination tunnel router receives the mobile node. The request message generated after attaching the request message completes the attachment of the mobile node, and if the mobile router device has finished attaching, The request message generated by the destination tunnel router after receiving the attach request message of the mobile node completes the attach of the mobile node.
  • the mobile router device managing multiple MNs performs network registration instead of the MN after the mobile handover, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • Embodiments of the present invention provide a method for processing network mobility management, based on a mobile router device MRI side, wherein a mobile node is moved from a management domain of a source tunnel router to a management domain of a destination tunnel router. As shown in Figure 13, the method includes:
  • Step 101 The mobile router device MRI receives an attach request message of the mobile node.
  • the attach request message includes a terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the terminal identifier of the mobile node X accessing the MRI.
  • Step 102 If the MRI does not complete the attach, the MRI causes the destination tunnel router to allocate a routing location identifier to the MRI, and causes the mapping server to update the stored mapping information of the routing location identifier corresponding to the MRI terminal identifier EID ⁇ n EIDi, and then complete the MRI. Attached, the MRI forwards the attach request message to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server to update the mapping information corresponding to the stored EID lx . After the update, the mapping server stores the EIDi and the assigned route location identifier. The mapping information, mapping server and destination tunnel router both store mapping information of Georgia 1 and Georgia 1 .
  • Step 103 If the MRI has been attached, the MRI forwards the attach request message to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server to update the mapping information corresponding to the stored EID lx . After the update, the mapping server is updated. Both the destination tunnel router and the destination tunnel router store mapping information of EIDi and EID lx .
  • the mobile router device receives the attach request message of the mobile node, and if the mobile router device does not complete the attach, triggers the tunnel router to make the mobile router device first to the mapping server.
  • the mobile node's attach request message is forwarded to the tunnel router to enable the mobile node to complete the attach to the mapping server through the mobile router device, and if the mobile router device completes the attach, the mobile node's attach request message is forwarded to the tunnel router to make the mobile node pass the mobile router.
  • the device completes the attach to the mapping server.
  • the mobile router device managing multiple MNs performs network registration instead of the mobile switched MN, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • the method is based on the mobile router device MRI side, wherein the mobile node is moved from the management domain of the source tunnel router to the management domain of the destination tunnel router. As shown in FIG. 14, the method includes:
  • Step 201 The mobile router device MRI receives an attach request message of the mobile node.
  • the attach request message includes a terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the terminal identifier of the mobile node X accessing the MRI.
  • multiple MNs (EID Arlington, EID 12 , EID 13 ) need to register with the Map-Server in the core network, and the MRI receives the attachment of multiple MNs (EIDedia, EID 12 , EID 13 ). Requesting subsequent forwarding, the MRI can connect multiple MNs and manage their connection to the xTR.
  • the MN itself registers with the Map-Server of the core network through the xTR. If multiple MNs move frequently, a large number of signaling interactions are generated with the core network, and the The MRI proposed in the embodiment of the invention replaces the registration of multiple MNs with the Map-Server of the core network, which can significantly reduce the signaling interaction.
  • Step 202 If the MRI does not complete the attach, the MRI causes the destination tunnel router to allocate a routing location identifier to the MRI, and causes the mapping server to update the stored mapping information of the routing location identifier corresponding to the MRI terminal identifier EID ⁇ n EIDi, and then complete the MRI. Attached.
  • the MRI and the plurality of MNs managed by the MIR move to the new user network as a whole, for example, the user network 1 managed by the xTR1, the MRI attached to the Map-Server as shown in FIG. 2 is first performed.
  • Step 203 If the MRI has been attached, the MRI forwards the attach request message to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server to update the mapping information corresponding to the stored EID lx . After the update, the mapping server is updated. Both the destination tunnel router and the destination tunnel router store mapping information of réelle 1 and Georgia 1 .
  • the MN is attached by MRI for the first time, and the MRI has been attached, and then the MN is attached to the Map-Server as shown in FIG. If the new MN mobility is switched to the MRI under xTR1, the MRI has completed the attachment, and only the mapping information of the EID-EID between the new MN and the MRI is established, and the mapping entry is correspondingly stored in the Map-Server and The attachment is completed after xTR1.
  • the management domain is the new node in the management domain of the MRI EIDi:) mobile switch to the xTR-N management domain.
  • EID1 MRI (EID1) management domain
  • MRI EIDi Forwards the attach request initiated by the mobile node to the xTR-N.
  • the xTR-N After receiving the mobile node attach request sent by the MRI EIDi ⁇ *, the xTR-N performs a mapping entry (MAP) update to the Map-Server.
  • MAP mapping entry
  • the Map-Server modifies the mapping entry as: ⁇ map:EID 13 , EID! , 1>, and the XTR-N side maintains the EID mapping entry between the MN and the MRI EID ⁇ map :EID 13 , EID ⁇
  • Step 204 The MRI receives a data packet sent by a mobile node, where a source address of the data packet is a terminal identifier of the mobile node, and a destination address is a terminal identifier of the peer node.
  • the MRI receives the MN (EID cough) under the xTR1 management domain to send the data packet to the CN (EID 2 ) under the xTR2 management domain.
  • the source address of the data packet is the terminal identifier EID of the MN, and the destination address is CN.
  • the terminal ID is EID 2 .
  • Step 205 The MRI forwards the data packet to the destination tunnel router, so that the destination tunnel router encapsulates the data packet, and the source address of the encapsulated data packet is a routing location identifier corresponding to the mobile node, and the destination address is a routing location corresponding to the peer node. logo.
  • the MRI forwards the received data packet to the xTR1, and the xTR1 encapsulates the data packet.
  • the source address of the encapsulated data packet is the routing location identifier RLOd corresponding to MN (EID cinnamon), and the destination address is CN (EID). 2 )
  • the corresponding routing location identifies RLOC 2 .
  • step 204 and the step 203 are not strictly sequential.
  • FIG. 14 is only an exemplary execution manner.
  • step 204 and step 205 may be directly executed, and step 203 may be executed before execution.
  • Step 204 and step 205 if the MN has already sent the data packet by the MRI completion, the MRI performs step 204 and step 205. If the MN first completes the attachment through the MRI and then sends the data packet through the MRI, the MRI performs the step. 201 to step 205.
  • the processing method of the network mobility management provided by the embodiment of the present invention, after the mobile node moves the handover, the mobile router device receives the attach request message of the mobile node, and if the mobile router device does not complete the attach, triggers the tunnel router to make the mobile router device first to the mapping server. Complete the attach, and then forward the mobile node's attach request message to the tunnel router to make the mobile node map through the mobile router device.
  • the shot server completes the attach, and if the mobile router device completes the attach, the mobile node's attach request message is forwarded to the tunnel router so that the mobile node completes the attach to the mapping server through the mobile router device.
  • the mobile router device managing multiple MNs performs network registration instead of the MN after the mobile handover, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • Embodiments of the present invention provide a method for processing network mobility management, based on a tunnel router xTR side, wherein a mobile node is moved from a management domain of a source tunnel router to a management domain of a destination tunnel router. As shown in Figure 15, the method includes:
  • Step 301 The destination tunnel router detects whether the mobile router device MRI completes attachment.
  • Step 302 If the MRI does not complete the attachment, the destination tunnel router allocates a routing location identifier to the MRI, and causes the mapping server to update the stored mapping information of the MRI-containing terminal identifiers EIDi and the routing location identifier corresponding to the EIDi, and then complete the MRI attachment.
  • the tunnel router receives the attach request message of the mobile node forwarded by the MRI, and the attach request message includes the terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the terminal identifier of the mobile node x accessing the MRI, and the destination tunnel router updates the storage.
  • mapping server updates the stored 101 the mapping information corresponding to the updated mapping server stores £ 101 and map the allocated routing information location identifier, the mapping server and the destination tunnel router are stored EIDi Mapping information with EID lx .
  • Step 303 If the MRI has been attached, the destination tunnel router receives the attach request message forwarded by the MRI, and the destination tunnel router updates the stored mapping information corresponding to Georgia 1 and triggers the mapping server to update the stored mapping information corresponding to the EID lx . After that, the mapping server and the destination tunnel router both store mapping information of EIDi and EID lx .
  • the method for processing network mobility management provided by the embodiment of the present invention firstly detects whether the mobile router device completes attachment, and if the mobile router device does not complete attachment, the mobile router device completes attachment to the mapping server, and then receives the mobile router device to forward. After the attach request message of the mobile node, the mobile node completes the attaching to the mapping server through the mobile router device, and if the mobile router device completes the attach, receives the attach request message of the mobile node forwarded by the mobile router device, and then causes the mobile node to map to the mobile router device.
  • the server has finished attaching.
  • the mobile router device that manages multiple MNs replaces the MN after the mobile handover to perform network registration, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • the method is based on the tunnel router xTR side, wherein the mobile node is moved from the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the method includes: Step 401: The destination tunnel router detects whether the mobile router device MRI completes attachment.
  • the xTR can know whether the attachment has been completed by querying whether to store the mapping information of the EID of the MRI.
  • Step 402 If the MRI is not completed, the destination tunnel router allocates a route location identifier to the MRI, and causes the mapping server to update the stored mapping information of the MRI-equipped terminal identifier EIDi and the route location identifier corresponding to the EIDi, and then complete the MRI attachment.
  • the MRI and the plurality of MNs managed by the MIR move to the new user network as a whole, for example, the user network 1 managed by the xTR1, the MRI attached to the Map-Server as shown in FIG. 2 is first performed.
  • Step 403 If the MRI has been attached, the destination tunnel router receives the MRI forwarded attach request message, where the attach request message includes the terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the mobile node X accessing the MRI.
  • the terminal identifier the destination tunnel router updates the mapping information corresponding to the stored EID lx and triggers the mapping server to update the mapping information corresponding to the stored EID lx .
  • the mapping server and the destination tunnel router both store the mapping of £ 1 and Mega 1 . information.
  • the MN is attached by MRI for the first time, and the MRI has been attached, and then the MN is attached to the Map-Server as shown in FIG. If the new MN mobility is switched to the MRI under xTR1, the MRI has completed the attachment, and only the mapping information of the EID-EID between the new MN and the MRI is established, and the mapping entry is correspondingly stored in the Map-Server and The attachment is completed after xTR1. Specifically, it can be implemented by referring to the flow shown in FIG. 5.
  • Step 404 The destination tunnel router receives the data packet sent by the mobile node forwarded by the MRI, where the source address of the data packet is the terminal identifier of the mobile node, and the destination address is the terminal identifier of the opposite node.
  • xTRl receives the MRI-forwarded MN (EID cinnamon) the packet to be sent to the CN (EID 2 ) under the xTR2 administrative domain, the source address of the packet.
  • the terminal ID of the MN is EID
  • the destination address is the terminal identifier EID 2 of the CN.
  • the tunnel router in the embodiment of the present invention may also receive a data packet that needs to be sent to the opposite node by the mobile node directly managed by the tunnel router.
  • Step 405 The destination tunnel router encapsulates the data packet.
  • the source address of the encapsulated data packet is the routing location identifier assigned by the destination tunnel router to the MRI, and the destination address is the routing location identifier of the peer tunnel router, and the peer node is located at the opposite end.
  • the routing location identifier of the peer tunnel router is obtained by the destination tunnel router from the mapping server according to the terminal identifier of the peer node.
  • the MN (EID 0.) under the xTR1 management domain sends data to the correspondent node CN (EID 2 ) under the peer tunneling router xTR2 management domain, and xTR1 queries the mapping server Map-Server for CN (EID 2 ) location identifier corresponding routing xTR2 i.e. route location identification RLOC 2, then xTRl encapsulating the data packet, the source address of the packet is encapsulated MN (EID ”) corresponding to the route location identifier i.e. the route location identifier xTRl RLOd, the destination address is the routing location identifier RLOC 2 corresponding to CN (EID 2 ).
  • Step 406 The destination tunnel router sends the encapsulated data packet to the peer tunnel router.
  • xTRl sends the encapsulated packet to xTR2.
  • Step 404 is not limited to being executed after step 403. Steps 404 and 403 have no strict sequence. FIG. 16 is only an exemplary execution manner. In practice, step 404 can be directly executed. To step 406, or after step 403, step 404 to step 406 may be performed. If the attached MN has sent the data packet through the MRI, the MRI performs steps 404 and 406, if the MN passes first. After the MRI completes the attachment and then sends the data packet through the MRI, the MRI performs step 403 and then performs steps 404 to 406.
  • the tunnel router xTR2 needs to encapsulate the data packet after the CN (EID 2 ) sends the data packet to the MN (EID cinnamon), and the encapsulated data packet needs CN (EID 2 ) and MN (EID mild) respectively.
  • the routing location identifier is obtained by querying the routing location identifier of the peer tunneling router xTR-N according to the terminal identifier EID of the opposite node MN (EID).
  • xTR2 Since xTR2 does not know the routable address RLOC of the destination address EID, it queries the Map-Server for the mapping table of EID. The query process is as follows:
  • the identifier bit is the second identifier 1
  • the outer header of the data packet is encapsulated and sent to the xTR-N.
  • the encapsulated source and destination addresses are the routable addresses RLOC 2 and RLOC 3 respectively .
  • the MN acts as its own xTR, and all the outgoing data packets are encapsulated and transmitted by using its own RLOC; the MN acts as its own EID prefix xTR, which is responsible for registering its own RLOC changes with the MS. And update the ITR and proxy ingress tunnel router (Proxy-ITR, PITR) that caches its original mapping information.
  • the xTR After the MN roams to the new xTR, the xTR allocates a regular global RLOC to the MN for encapsulating the outer-header to be used in the core network; and assigns the local ROLC to the MN using the xTR's own EID prefix, Used to encapsulate the middle-header used within the site.
  • the data packet is encapsulated three times, three other sub-header 1 J is the out-header, middle-header, inner-header (the EID of the sending node - the EID of the receiving node) so that the packets are forwarded between the xTRs.
  • the data packet is encapsulated twice (two-layer out-header, inner-header), which can reduce the number of times of encapsulation and improve the efficiency of data communication.
  • the method for processing network mobility management provided by the embodiment of the present invention firstly detects whether the mobile router device completes attachment, and if the mobile router device does not complete attachment, the mobile router device completes attachment to the mapping server, and then receives the mobile router device to forward. After the attach request message of the mobile node, the mobile node completes the attaching to the mapping server through the mobile router device, and if the mobile router device completes the attach, receives the attach request message of the mobile node forwarded by the mobile router device, and then causes the mobile node to map to the mobile router device.
  • the server has finished attaching.
  • the mobile router device that manages multiple MNs replaces the MN after the mobile handover to perform network registration, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • An embodiment of the present invention provides a method for processing network mobility management, where the method includes: after a mobile node switches from an administrative domain of a source tunnel router to a management domain of another tunnel router, the source tunnel router communicates with the opposite end of the communication with the mobile node.
  • the tunnel router to which the node belongs sends a notification message, and the notification message is used to notify the tunnel router to which the peer node that communicates with the mobile node belongs to obtain the updated mapping information from the mapping server.
  • the xTR can record the source and destination address of the packet forwarded to the core network in a short time. For example, as shown in FIG. 5, when the MN or MRI moves from the xTR-P domain to the xTR-N domain with its managed MN, in order to maintain continuous data communication between the MN and the CN after the mobile handover, the handover process After the data packet in the network link arrives after the MN or the xTR-P accessed before the MRI handover, the xTR-P packet fails to find the forwarding port of the destination terminal, and it is determined that the MN has been removed from the xTR-P.
  • a preset option is set in the Solicit Map Request (SMR) message to notify other xTRs that the MN has sent data in the MRI management domain within one minute, and inform other The xTR should re-acquire a new mapping entry to the Map-Server, where the preset option can be a preset identifier, such as 0.
  • the tunnel router After the mobile node switches from the management domain of the tunnel router to the management domain of another tunnel router, the tunnel router sends a notification message to the tunnel router to which the peer node that communicates with the mobile node belongs.
  • the notification message is used to notify the tunnel router to which the peer node that has communicated with the mobile node belongs to obtain the updated mapping information from the mapping server. In this way, the tunnel router can learn and update the mapping information about the mobile node more quickly when the mobile node moves and the mapping information changes.
  • Embodiments of the present invention provide a processing method of network mobility management, based on a mapping server.
  • the method includes:
  • Step 501 The mapping server causes the destination tunnel router to detect whether the mobile router device MRI is attached.
  • Step 502 If the MRI does not complete the attach, the mapping server causes the destination tunnel router to allocate the routing location identifier to the MRI and update the mapping information of the stored routing location corresponding to the MRI terminal identifier EID ⁇ n Mega, and then complete the MRI attachment.
  • the mapping server receives the request message generated by the destination tunnel router after receiving the attach request message of the mobile node, where the attach request message includes the terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the mobile node accessing the MRI.
  • mapping information EID lx corresponding to the terminal identification of X the mapping server updates the stored map information EID lx corresponding to and triggering destination router updates the stored tunnel, after updating the mapping information route location identifier mapping server stores EIDi and allocation, mapping server Both the destination tunnel router and the destination tunnel router store mapping information of Georgia 1 and Georgia 1 .
  • Step 503 If the MRI has completed the attach, the mapping server receives the request message generated by the destination tunnel router after receiving the attach request message of the mobile node, and the mapping server updates the stored The map information corresponding to Georgia 1 triggers the mapping information corresponding to the stored EID lx of the destination tunnel router. After the update, both the mapping server and the destination tunnel router store the mapping information of Georgia 1 and Georgia 1 .
  • the mapping server causes the destination tunnel router to detect whether the mobile router device completes attachment. If the mobile router device does not complete the attachment, the mobile router device is first attached, and then the destination tunnel router is received.
  • the request message generated after receiving the attach request message of the mobile node completes the attach of the mobile node, and if the mobile router device has completed attaching, the receiving destination tunnel router completes the request message generated after receiving the attach request message of the mobile node to complete the mobile node. Attachment.
  • the mobile router device managing multiple MNs performs network registration instead of the MN after the mobile switching, which effectively reduces the signaling interaction in the network and improves the communication efficiency.
  • the processing method of the network mobility management provided by the embodiments of the present invention is described in detail below by using a specific embodiment, and the method is based on the mapping server Map- On the server side, where the mobile node is moved from the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • the method includes:
  • Step 601 The mapping server causes the destination tunnel router to detect whether the mobile router device MRI is attached.
  • the mapping server may send the signaling to enable the tunneling router xTR to query whether to store the mapping information of the EID of the MRI to know whether the attachment has been completed.
  • Step 602 If the MRI does not complete the attach, the mapping server causes the destination tunnel router to allocate a routing location identifier to the MRI and update the stored mapping information of the routing location corresponding to the MRI terminal identifier EID ⁇ n Mega to complete the MRI attach.
  • the MRI and the plurality of MNs managed by the MIR move to the new user network as a whole, for example, the user network 1 managed by the xTR1, the MRI attached to the Map-Server as shown in FIG. 2 is first performed.
  • Step 603 If the MRI has completed the attach, the mapping server receives the request message generated by the destination tunnel router after receiving the attach request message of the mobile node, where the attach request message includes the terminal identifier EID lx , EID lx of the mobile node accessing the MRI.
  • MRI is used to indicate the access terminal identifier of the mobile node x
  • mapping server updates the stored map information corresponding EID lx tunnel router object and triggers updating the stored map information corresponding EID lx, updated, and a mapping server object tunnel routers Stores mapping information between EIDi and EID lx .
  • the MN is attached by the MRI for the first time, and the MRI has been attached, and then the MN is attached to the Map-Server as shown in FIG. 3, wherein the request message generated by the destination tunnel router after receiving the attach request message of the mobile node may be It is a Map-Register message, such as the Map-Register message sent by xTR1 to the mapping server in Figures 2 and 3. If the new MN moves to the MRI under xTR1, the MRI has completed the attachment, and only needs to establish the mapping information of the EID-EID between the new MN and the MRI, and store the mapping entry correspondingly in the Map-Server and The attachment is completed after xTRl. Specifically, it can be implemented with reference to the flow shown in FIG. 5.
  • Step 604 The mapping server receives the query request sent by the destination tunnel router, where the query request is sent after the destination tunnel router receives the data packet sent by the mobile node forwarded by the MRI, and the source address of the data packet is the terminal identifier of the mobile node, and the destination The address is the terminal identifier of the peer node; the query request includes the terminal identifier of the peer node.
  • mapping server receives the query request.
  • Step 605 The mapping server queries, according to the terminal identifier of the peer node, the routing location identifier of the peer tunnel router corresponding to the terminal identifier of the peer node, and returns the routing location identifier to the destination tunnel router, where the peer end The node is located in the management domain of the peer tunnel router.
  • mapping queries the server to obtain the corresponding EID 2 in the mapping information storage location identifier in the routing RLOC 2, then routing xTR2 location query to get back to the identification RLOC 2 xTRl o
  • step 604 and step 603. There is no strict sequence between step 604 and step 603.
  • FIG. 17 is only an exemplary execution manner. In practice, step 604 and step 605 may be directly executed, and step 603 may be executed. Step 604 and step 605 are performed again. If the MN has already sent the data packet through the MRI completion, the MRI performs step 604 and step 605. If the MN first completes the attachment through the MRI and then sends the data packet through the MRI, the MRI performs. Step 601 to step 605.
  • the mapping server causes the destination tunnel router to detect whether the mobile router device completes attachment. If the mobile router device does not complete the attachment, the mobile router device is first attached, and then the destination tunnel router is received.
  • the request message generated after receiving the attach request message of the mobile node completes the attach of the mobile node, if the mobile route After the device has completed attaching, the request message generated by the receiving destination tunnel router after receiving the attach request message of the mobile node completes the attach of the mobile node.
  • the mobile router device managing multiple MNs performs network registration instead of the MN after the mobile handover, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • the embodiment of the present invention further provides a mobile router device 70.
  • the mobile router device 70 includes: a bus 74; and a processor 71, a memory 72, and an interface 73 connected to the bus 74, wherein the interface 73 is used.
  • the memory 72 is for storing computer code
  • the processor 71 is configured to execute the computer code for:
  • the attach request message includes a terminal identifier EID lx of the mobile node accessing the MRI, where the EID lx is used to indicate the terminal identifier of the mobile node x accessing the MRI;
  • the destination tunneling router is configured to allocate the routing location identifier to the MRI and trigger the mapping server to update the stored mapping information of the routing location identifier corresponding to the MRI terminal identifier EID ⁇ n EIDi, and then complete the MRI attachment to the destination tunnel.
  • the router forwards the attach request message, so that the destination tunnel router triggers the destination tunnel router and the mapping server to update the mapping information corresponding to the stored EID lx .
  • the mapping server stores the mapping information of the EIDi and the assigned routing location identifier, and the mapping server And the destination tunnel router stores mapping information of EIDi and EID lx ;
  • the connection request message is forwarded to the destination tunnel router, so that the destination tunnel router triggers the destination tunnel router and the mapping server to update the mapping information corresponding to the stored EID lx . After the update, both the mapping server and the destination tunnel router are updated.
  • the mobile node is moved from the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • mapping information that is stored by the mapping server and includes the routing location identifier further includes identifier information for identifying the routable capability.
  • the processor 71 executes the computer code and is further configured to:
  • a source address of the data packet is a terminal identifier of the mobile node, and a destination address is a terminal identifier of the peer node;
  • the source address of the encapsulated data packet is the routing location identifier corresponding to the mobile node, and the destination address is the routing location identifier corresponding to the peer node.
  • the mobile router device receives the attach request message of the mobile node after the mobile node moves, and triggers the tunnel router to make the mobile router device attach to the mapping server first, and then tunnels to the tunnel if the mobile router device does not complete the attaching.
  • the router forwards the attach request message of the mobile node to enable the mobile node to complete the attach to the mapping server through the mobile router device, and if the mobile router device completes the attach, forward the attach request message of the mobile node to the tunnel router, so that the mobile node completes the attach to the mapping server through the mobile router device.
  • the mobile router device managing multiple MNs performs network registration instead of the mobile switched MN, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • the embodiment of the present invention further provides a tunnel router 80.
  • the tunnel router 80 includes: a bus 84; and a processor 81, a memory 82, and an interface 83 connected to the bus 84, wherein the interface 83 is used for communication.
  • the memory 82 is for storing computer code
  • the processor 81 is configured to execute the computer code for:
  • the mapping server updates the stored mapping information of the MRI-containing terminal identifiers EIDi and the route location identifier corresponding to the EIDi, and then completes the attachment of the MRI, and receives the attachment of the mobile node forwarded by the MRI.
  • the request message, the attach request message includes the terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the terminal identifier of the mobile node X accessing the MRI, update the mapping information corresponding to the stored EID lx , and trigger the mapping server to update the storage.
  • the mapping information corresponding to the EID lx is updated, the mapping server stores the mapping information with the assigned routing location identifier, and the mapping server and the destination tunnel router both store the mapping information of the EIDi and the EID lx ;
  • mapping information EID lx corresponding to update the stored and triggering mapping information mapping server update the stored EID lx corresponding updated, the mapping server and the destination tunnel router are stored EIDi Mapping information with EID lx ;
  • the mobile node is moved from the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • mapping information that is stored by the mapping server and includes the routing location identifier further includes identifier bit information for identifying the routable capability; and the mapping server stores the EIDi and the EID lx.
  • the mapping information further includes identifier bit information for identifying that there is no routable capability.
  • the processor 81 executes the computer code and is further configured to:
  • the source address of the data packet is the terminal identifier of the mobile node, and the destination address is the terminal identifier of the opposite node;
  • the data packet is encapsulated.
  • the source address of the encapsulated data packet is the routing location identifier assigned by the destination tunnel router to the MRI, and the destination address is the routing location identifier of the peer tunnel router.
  • the peer node is located at the peer tunnel router. In the management domain, the route location identifier of the peer tunnel router is obtained by the destination tunnel router from the mapping server according to the terminal identifier of the peer node; and the encapsulated data packet is sent to the peer tunnel router.
  • the tunnel router provided by the embodiment of the present invention first detects whether the mobile router device completes attachment, and if the mobile router device does not complete attachment, the mobile router device completes attachment to the mapping server, and then receives the mobile node attachment request message forwarded by the mobile router device. Afterwards, the mobile node completes the attaching to the mapping server through the mobile router device, and if the mobile router device completes the attach, receives the attach request message of the mobile node forwarded by the mobile router device, and then causes the mobile node to complete the attaching to the mapping server through the mobile router device.
  • the mobile router device that manages multiple MNs replaces the mobile switched MN to perform network registration, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • the embodiment of the present invention further provides a tunnel router 90.
  • the tunnel router 90 includes: a bus 94; and a processor 91, a memory 92 and an interface 93 connected to the bus 94, wherein the interface 93 is used for communication.
  • the memory 92 is for storing computer code
  • the processor 91 is configured to execute the computer code for:
  • a notification message is sent to the tunnel router to which the correspondent node that communicates with the mobile node belongs, and the notification message is used to notify the pair that communicates with the mobile node.
  • the tunnel router to which the end node belongs obtains updated mapping information from the mapping server.
  • the tunnel router After the mobile node switches from the management domain of the tunnel router to the management domain of another tunnel router, the tunnel router sends a notification message to the tunnel router to which the peer node that communicates with the mobile node belongs.
  • the notification message is used to notify the tunnel router to which the peer node that has communicated with the mobile node belongs to obtain the updated mapping information from the mapping server. In this way, the tunnel router can be faster when the mobile node moves and the mapping information changes. Learn and update mapping information about mobile nodes.
  • the embodiment of the present invention further provides a mapping server 100.
  • the mapping server 100 includes: a bus 140; and a processor 110, a memory 120, and an interface 130 connected to the bus 140, wherein the interface 130 is used for communication.
  • the memory 120 is for storing computer code
  • the processor 110 is configured to execute the computer code for:
  • the destination tunnel router allocates the routing location identifier to the MRI and updates the stored mapping information of the routing location corresponding to the MRI terminal identifiers EIDi and EIDi, and then completes the MRI attachment, and the receiving destination tunnel router receives the mobile a request message generated after the attach request message of the node, where the attach request message includes a terminal identifier EID lx of the mobile node accessing the MRI, and the EID lx is used to indicate the terminal identifier of the mobile node x accessing the MRI, and the stored EID lx is updated.
  • mapping information corresponding EID lx corresponding mapping information and trigger object tunnel router updates the stored, updated, mapping server stores £ 10 1 and map the allocated routing information location identifier, the mapping server and the destination tunnel router are stored EIDi and EID lx Mapping information;
  • the receiving object of the tunnel router is generated after receiving the attachment of the mobile node a request message, updating the stored £ 10 1 corresponding EID lx corresponding mapping information and trigger object tunnel router updates the stored mapping information After the update, the mapping server and the destination tunnel router both store mapping information of EIDi and EID lx ;
  • the mobile node is moved from the management domain of the source tunnel router to the management domain of the destination tunnel router.
  • mapping information that is stored by the mapping server and includes the routing location identifier further includes identifier information for identifying the routable capability; and mapping information stored by the mapping server including the Georgia 1 and the EID lx , Identifies the identification bit information that does not have routable capability.
  • the processor 110 executes the computer code and is further configured to:
  • the query request is sent after the destination tunnel router receives the data packet sent by the mobile node forwarded by the MRI, and the source address of the data packet is the terminal identifier of the mobile node, and the destination address is the peer node. Terminal identifier; the query request includes the terminal identifier of the peer node;
  • the peer node is located in the management domain of the peer tunnel router.
  • the mapping server provided by the embodiment of the present invention first enables the destination tunnel router to detect whether the mobile router device completes attachment. If the mobile router device does not complete the attachment, the mobile router device is first attached, and then the destination tunnel router receives the mobile node. The request message generated after the attach request message completes the attach of the mobile node. If the mobile router device has completed attaching, the request message generated by the receiving destination tunnel router after receiving the attach request message of the mobile node completes the attach of the mobile node.
  • the mobile router device managing multiple MNs performs network registration instead of the MN after the mobile handover, which effectively reduces signaling interactions in the network and improves communication efficiency.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a hardware plus software functional unit.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the software functional unit is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the method of various embodiments of the present invention.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • the foregoing storage medium includes: a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program code. .
  • the above function assignment can be completed by different functional modules as needed, that is, the device is installed.
  • the internal structure is divided into different functional modules to perform all or part of the functions described above.

Landscapes

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

Abstract

L'invention concerne un procédé et un instrument de traitement de gestion de mobilité de réseau. Après qu'un nœud mobile se déplace et effectue une commutation, un enregistrement de réseau est réalisé par un instrument de routeur mobile qui gère une pluralité de nœuds mobiles à la place du nœud mobile qui a été déplacé et a subi une commutation, ce qui réduit de manière efficace l'interaction de signalisation dans un réseau et améliore l'efficacité de communication. La technique détaillée est comme suit : un instrument de routeur mobile reçoit un message de requête de rattachement en provenance d'un nœud mobile; si l'instrument de routeur mobile n'accomplit pas un rattachement, un routeur de tunnel en premier amène l'instrument de routeur mobile à accomplir un rattachement à un serveur de mappage, puis le routeur de tunnel amène le nœud mobile à accomplir un rattachement au serveur de mappage par l'intermédiaire de l'instrument de routeur mobile après réception du message de requête de rattachement transféré par l'instrument de routeur mobile; et si l'instrument de routeur mobile accomplit un rattachement, le routeur de tunnel amène le nœud mobile à accomplir un rattachement au serveur de mappage par l'intermédiaire d'un instrument de routeur mobile après réception du message de requête de rattachement transféré par l'instrument de routeur mobile. Les modes de réalisation de la présente invention sont utilisés pour gérer des nœuds mobiles dans un réseau.
PCT/CN2014/078435 2014-05-26 2014-05-26 Procédé et instrument de traitement de gestion de mobilité de réseau Ceased WO2015180024A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2014/078435 WO2015180024A1 (fr) 2014-05-26 2014-05-26 Procédé et instrument de traitement de gestion de mobilité de réseau
CN201480029574.XA CN105308928B (zh) 2014-05-26 2014-05-26 网络移动管理的处理方法和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/078435 WO2015180024A1 (fr) 2014-05-26 2014-05-26 Procédé et instrument de traitement de gestion de mobilité de réseau

Publications (1)

Publication Number Publication Date
WO2015180024A1 true WO2015180024A1 (fr) 2015-12-03

Family

ID=54697811

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/078435 Ceased WO2015180024A1 (fr) 2014-05-26 2014-05-26 Procédé et instrument de traitement de gestion de mobilité de réseau

Country Status (2)

Country Link
CN (1) CN105308928B (fr)
WO (1) WO2015180024A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112218286B (zh) * 2019-07-09 2021-07-23 大唐移动通信设备有限公司 终端能力标识映射方法、终端能力查询方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008037474A2 (fr) * 2006-09-27 2008-04-03 Nec Europe Ltd. Procédé pour prendre en charge la mobilité de flux dans un réseau
CN102984687A (zh) * 2011-09-06 2013-03-20 中兴通讯股份有限公司 一种移动性管理方法和系统
CN103051611A (zh) * 2012-12-11 2013-04-17 北京交通大学 一种身份与位置分离体系下的安全移动性管理方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008037474A2 (fr) * 2006-09-27 2008-04-03 Nec Europe Ltd. Procédé pour prendre en charge la mobilité de flux dans un réseau
CN102984687A (zh) * 2011-09-06 2013-03-20 中兴通讯股份有限公司 一种移动性管理方法和系统
CN103051611A (zh) * 2012-12-11 2013-04-17 北京交通大学 一种身份与位置分离体系下的安全移动性管理方法

Also Published As

Publication number Publication date
CN105308928B (zh) 2018-11-16
CN105308928A (zh) 2016-02-03

Similar Documents

Publication Publication Date Title
CN102196402B (zh) 无线通信系统中终端切换的方法及系统
CN106790732B (zh) 地址转换方法、装置及系统、网络标识控制方法及装置
US20120203856A1 (en) Method for anonymous communication, method for registration, method and system for transmitting and receiving information
TW201212603A (en) Enabling IPV6 mobility with NAT64
JP2013507858A (ja) 情報の取得及び通知、データメッセージの転送とハンドオーバの方法及びアクセスノード
US20150236954A1 (en) Mobile Node Mapping Information Update Triggering Method, MS and MN
CN102088390A (zh) 用户移动性的实现方法
JP5602252B2 (ja) 移動通信の制御方法、システム、マッピング転送サーバ及びアクセスルータ
WO2013071825A1 (fr) Dispositif et procédé de réalisation de réseau de séparation de repère et d'identité
CN104780522B (zh) 一种lisp标识承载接入网支持终端移动接入的方法
CN102025599A (zh) 发起通信、信息/数据报文的转发及路由配置方法/系统
EP2479932A1 (fr) Procédé et système d'affectation d'identificateur de position et d'envoi de message
CN102056236B (zh) 基于Wimax网络架构实现的通信网络及终端接入方法
CN103167463B (zh) 更新报文的处理方法及系统、映射服务器和移动节点
CN105308928B (zh) 网络移动管理的处理方法和设备
CN105530325B (zh) 位置和标识分离协议主机迁移方法及装置
CN100596242C (zh) 转发报文的方法、系统和锚点设备
US20090147759A1 (en) Method and apparatus for supporting mobility of node using layer 2/layer 3 addresses
WO2010051697A1 (fr) Procédé d'enregistrement, système et ancre mobile locale pour un préfixe d'interface dans pmipv6
CN104468305B (zh) 实现三层虚拟专用网方法和设备
CN103166825B (zh) 通过扩展通用路由封装技术实现网络互通的方法和系统
CN103634776B (zh) 一种获取终端的接入标识的方法及身份信息服务器
WO2012103755A1 (fr) Procédé et système pour obtenir l'identité (id) d'un terminal
CN103037351B (zh) 一种在pmip域间漫游时的节点通信方法及通信系统
JP2006114946A (ja) モバイルネットワークシステム

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201480029574.X

Country of ref document: CN

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

Ref document number: 14893126

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

Country of ref document: EP

Kind code of ref document: A1