WO2013007130A1 - Location/id separation protocol motion node, motion control method and motion node - Google Patents

Abstract

A location/ID separation protocol (Lisp)-motion node (MN), a motion control method and a motion node, the method comprising: after a motion occurs to the Lisp-MN and a new routing locator (RLOC) is obtained, sending an end-identifier (EID) and RLOC mapping update request to a correspondent node. After the motion occurs, the Lisp-MN timely notifies the correspondent node to update the EID and RLOC mapping, ensuring that the correspondent node directly uses the new encapsulated RLOC data packet and transmits data during the subsequent data transmission, thus reducing time delay and packet loss.

Description

 Identity and location separation protocol mobile node and mobile control method, mobile node

Technical field

 The present invention relates to the field of network technologies, and in particular, to a mobile control method for a lisp (Location/ID Separation Protocol)-MN (Motion Node) and a Lisp-MN and a mobile node.

Background technique

 The size of the DFZ (Default Free Zone) routing table increases at an increasing rate, which compromises the scalability of the route and the execution of route aggregation. Routing scalability issues have generated great interest in industry and academia.

 Members of the IAB (Internet Architecture Board) discussed that the underlying reason for the increase in the DFZ routing table is the dual semantics of IP addresses. In existing networks, IP addresses are both identifiers and locations.

 The IRTF RRG (Internet Research Task Force Routing Research Grou) is currently working on new routing and address architectures to support multi-hole, traffic engineering and mobility.

 Lisp is a new routing framework based on RRG's requirements for routing and address research, which is based on Cisco's separation of current IP addresses into terminal identifiers (EIDs, End-identifiers) and routing locations (RLOCs, Routing Locators). Reduce the size of the DFZ routing table, increase the expansion and reduce the number of globally visible, routing prefixes.

The network structure of Lisp is shown in Figure 1. The basic idea of LISP is to encapsulate an IP packet header outside the IP layer to reduce the impact of routes generated by the increase of edge network users on the routing table of the backbone network and maintain the stability of the backbone network (BGP) routing table. Lisp divides the existing IP address system into terminal identification (EID) and routing location (RLOC), and introduces the concept of tunnel routers ("Tunnel Routers"). The tunnel routers are divided into Ingress Tunnel Routers (ITRs). And Egress Tunnel Router (ETR). Both ITR and ETR need to register the binding of EID and RLOC in the mapping server (Map-Server, MS). Come to the host on the ETR side Said ETR is responsible for registering the EID of this host and RLOC binding, ITR is responsible for buffering the EID/RLOC binding of the ETR side host. Similarly for the ITR side host, the ITR registers the binding of the EID of this host to the RLOC. In addition, the ISR in Lisp is responsible for the encapsulation and mapping of data, and searches for the corresponding RLOC information according to the destination EID information. The ETR in Lisp is responsible for decapsulating data packets.

 The original intention of the LISP protocol is to solve the scale of the routing table, and it cannot solve the mobility of the network. With the development of the network, the mobility of the network is necessary, and the requirements of the Lisp design must be able to solve the mobility and multi-hole.

 lisp-MN is a mobility solution for Lisp. Lisp-MN defines the nodes in the lis network as lisp-MN, lisp-MN is different from the ordinary MN, lisp-MN has the function of ETR/ITR, and Figure 2 is a schematic diagram of the network structure of Lisp-MN. When lisp-MN moves to another network, lisp-MN registers its EID/RLOC mapping with its MS.

 In the communication process of the lisp network, if the lisp-MN moves from the location A to the new location A', when the downlink data of the lisp-MN is sent, the packet sent by the communication peer to the lisp-MN may be lost or delayed. Summary of the invention

 The embodiment of the present invention provides a lisp-MN and a mobile control method thereof, and a mobile node, which solves a network delay or occurs when a communication peer sends data to the lisp-MN when the location of the lisp-MN moves during the communication process. The problem of packet loss.

 In order to solve the above problem, an embodiment of the present invention provides a mobile node control method for identity and location separation protocol, including:

 After the identity and location separation protocol mobile node (Lisp-MN) moves and acquires a new routing location, the terminal identifier and routing location mapping update request are sent to its communication peer.

 The above method may also have the following feature: the terminal identifier/route location mapping update request carries the terminal identifier of the Lisp-MN and the new routing location mapping.

The method may further include the following feature, the method further includes: after receiving the terminal identifier and routing location mapping update request, the communication peer end replaces the locally saved terminal identifier and routing location mapping of the Lisp-MN with The terminal identifier is mapped to a new routing location. The above method may further have the following features, the method further comprising: after the mobile device acquires a new routing location, the Lisp-MN sends a terminal identity/routing location mapping registration request to the mapping server.

 An embodiment of the present invention further provides an identity and location separation protocol mobile node, where the identity and location separation protocol mobile node (Lisp-MN) includes a notification unit, and the notification unit is configured to: move in the Lisp-MN and After obtaining the new routing location, the terminal identifier and the routing location mapping update request are sent to the communication peer. The foregoing identity and location separation protocol mobile node may also have the following feature: the terminal identifier and the routing location mapping update request carry the terminal identifier/new routing location mapping of the Lisp-MN.

 The foregoing identity and location separation protocol mobile node may also have the following features, the Lisp-MN further includes a registration unit, and the registration unit is configured to: after the Lisp-MN moves and acquires a new routing location, the terminal identifier is transmitted/ The route location maps the registration request to the mapping server.

 The embodiment of the present invention further provides a mobile node, including an update unit, configured to receive a terminal identifier and a route location map sent by the Lisp-MN during communication with an identity and location separation protocol mobile node (Lisp-MN). After the update request, the terminal identifier and routing location mapping of the Lisp-MN are updated.

 The foregoing mobile node may also have the following feature, the updating unit is configured to update the terminal identifier and the routing location mapping of the Lisp-MN according to the following manner: replacing the locally saved terminal identifier and routing location mapping of the Lisp-MN with And mapping the terminal identifier and the new route location carried in the terminal identifier and the routing location mapping update request.

The lisp-MN in the embodiment of the present invention promptly informs the communication peer to update the EID/RLOC mapping after the movement occurs, so as to ensure that the communication peer directly uses the new RLOC to encapsulate the data packet and transmit the data in the subsequent data transmission process, thereby reducing the number of packets. Delay and packet loss.

BRIEF abstract

 Figure 1 is a schematic diagram of a lisp network structure;

Figure 2 is a schematic diagram of the network structure of Lisp-MN; 3 is a schematic diagram of a lisp-MN mobile control process according to an embodiment of the present invention;

 Figure 4 is a block diagram of a lisp-MN embodiment of the present invention.

Preferred embodiment of the invention

 Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

 An embodiment of the present invention provides a Lisp-MN mobility control method, including:

 After the Lisp-MN moves and acquires a new routing location, the sending terminal identity/route location mapping update request is sent to its communication peer.

 The terminal identifier/route location mapping update request carries the terminal identifier of the Lisp-MN and a new routing location mapping.

 The method further includes: after receiving the terminal identifier and routing location mapping update request, the communication peer end replaces the locally saved terminal identifier and routing location mapping of the Lisp-MN with the terminal identifier and the new Route location mapping.

 The method further includes: after the mobile device acquires a new routing location, the Lisp-MN further sends a terminal identity/routing location mapping registration request to the mapping server.

 The embodiment of the invention provides a method for implementing mapping update in a lisp network, including:

 During Lis network communication, when lisp-MN moves from location A to new location A', lisp-MN registers the mapping of updated EID and RLOC in the MS; and, lisp-MN sends EID and RLOC mapping update request message to it. The peer end notifies the communication peer that it has moved. After receiving the EID and RLOC mapping update request message, the communication peer CN updates its cached EID and ORLOC (ORLOC is the RLOC before the lisp-MN move) to the EID. Mapping with NLROC (NRLOC is the RLOC after lisp-MN moves).

The architecture of the embodiment of the present invention is as shown in FIG. 3, and includes a lisp network, a lisp-MN, a communication peer CN, and a mapping server MS. The mapping server MS is configured to store the EID and RLOC mapping of the lisp-MN in its registration. During the communication, the lisp-MN moves from the location A to the location Α', including: Step 301: The lisp-MN sends an EID and a RLOC Register Request to the MS, and updates the EID and RLOC mapping of the lisp-MN; Step 302, the MS sends an EID and a RLOC Register Response to the lisp-MN;

 Step 303: The lisp-MN sends an EID/RLOC mapping update request (Update Request) message to the communication peer CN of the lisp-MN, carrying the EID and the NLROC, instructing the CN to update the cached ESR and ORLEC mapping of the lisp-MN to EID and NLROC mapping;

 Step 303 and step 301 have no precedence;

 Step 304: The CN updates its cached EID and ORLOC mapping to an EID/NRLOC mapping, and returns an EID/RLOC Mapping Update Response (Update Response) message to the lisp-MN.

The embodiment of the present invention further provides a lisp-MN, as shown in FIG. 4, including a notification unit and a registration unit, where:

 The notification unit is configured to: after the Lisp-MN moves and acquires a new routing location, send a terminal identifier/routing location mapping update request to the communication peer end;

 The registration unit is configured to: after the Lisp-MN moves and acquires a new routing location, send a terminal identity/routing location mapping registration request to the mapping server.

 The terminal identifier and the routing location mapping update request carry the terminal identifier and the new routing location mapping of the Lisp-MN.

 An embodiment of the present invention further provides a mobile node, where the mobile node includes an update unit, configured to receive a terminal identifier sent by the Lisp-MN during communication with an identity and location separation protocol mobile node (Lisp-MN). After the routing location mapping update request, the terminal identifier and routing location mapping of the Lisp-MN are updated.

 The updating unit is configured to update the terminal identifier and the routing location mapping of the Lisp-MN according to the following manner: replacing the locally saved terminal identifier and routing location mapping of the Lisp-MN with the terminal identifier/routing location Mapping the terminal identifier carried in the update request with the new routing location mapping.

After the LIsp-MN is moved by the lisp-MN in the embodiment of the present invention, the lisp-MN registers the EID of the lisp-MN with the NLROC in the MS, and the lisp-MN directly reports the EID and the NLROC mapping to the communication peer CN, and the CN updates the cache therein. The mapping of the EID and ORLOC of lisp-MN is the mapping of EID and NLROC. This ensures that during the communication process, after the lisp-MN moves, the CN directly encapsulates the data packet with the NSROC of the lisp-MN and transmits the data during the downlink data transmission process of the lisp-MN, and the CN does not need to search for the lisp-MN through the MS. NRLOC saves the CN's mapping search process in the MS, improves the efficiency of data transmission, avoids delays and packet loss, and improves the switching efficiency of the lisp network.

 One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program instructing the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

Industrial Applicability The lisp-MN in the embodiment of the present invention promptly informs its communication peer to update the EID and RLOC mapping after the movement occurs, so as to ensure that the communication peer directly uses the new RLOC to encapsulate the data packet and send the data during the subsequent data transmission. , reducing latency and packet loss.

Claims

1. An identity and location separation protocol mobile node (Lisp-MN) mobility control method, which comprises:  After the Lisp-MN moves and acquires a new routing location, the sending terminal identifier and the routing location mapping update request are sent to its communication peer.  2. The method according to claim 1, wherein the terminal identifier and the routing location mapping update request carry the terminal identifier of the Lisp-MN and a new routing location mapping.  3. The method according to claim 2, the method further comprising: after receiving the terminal identifier and routing location mapping update request, the communication peer end locally stores the terminal identifier and routing location of the Lisp-MN The mapping is replaced with the terminal identity and the new routing location mapping.  The method according to any one of claims 1 to 3, the method further comprising: after the movement occurs and acquiring a new routing location, the Lisp-MN sends a terminal identity and routing location mapping registration request to the mapping server. 5. An identity and location separation protocol mobile node (Lisp-MN), comprising a notification unit, wherein the notification unit is configured to: after the Lisp-MN moves and acquires a new routing location, the sending terminal identifier and routing location Map update requests to their correspondent peers.  The Lisp-MN according to claim 5, wherein the terminal identifier and the routing location mapping update request carry the terminal identifier of the Lisp-MN and a new routing location mapping. 7. The Lisp-MN according to claim 5 or 6, further comprising a registration unit, the registration unit being configured to: after the Lisp-MN moves and acquires a new routing location, the sending terminal identifier and the routing location mapping Register the request to the mapping server.  8. A mobile node, comprising an update unit, the update unit configured to: receive a terminal identifier and route sent by the Lisp-MN during communication with an identity and location separation protocol mobile node (Lisp-MN) After the location mapping update request, the terminal identifier and routing location mapping of the Lisp-MN are updated. 9. The mobile node according to claim 8, wherein the update unit is configured to update the terminal identity and routing location mapping of the Lisp-MN according to the following manner: The terminal identifier and the routing location mapping of the Lisp-MN are replaced with the terminal identifier and the new routing location mapping carried in the terminal identifier and routing location mapping update request.