CN102868618A - Detaching method, detaching device and mapping server - Google Patents

Abstract

The invention provides a detaching method which is applied to an identity and position separation agreement (lisp) network. The detaching method includes the steps: transmitting a detaching request carrying terminal indicating information to a mapping server by a network element with functions of a tunnel router; and requesting the mapping server delete terminal identifier/routing position mapping corresponding to a terminal indicated by the terminal indicating information. The mapping server deletes the terminal identifier/routing position mapping corresponding to the terminal indicated by the locally stored terminal indicating information after receiving the detaching request carrying the terminal indicating information transmitted by the network element with the functions of the tunnel router. The invention further provides a detaching device and the mapping server, wherein the detaching device is applied to the network element with the functions of the tunnel router.

Description

A detachment method, device and mapping server

technical field

The present invention relates to the field of network technology, in particular to a detachment method, device and mapping server.

Background technique

The size of the DFZ (Default Free Zone, default free zone) routing table increases at a gradual rate, which impairs the scalability of routing and the execution of routing aggregation. The problem of routing scalability has attracted great interest from both industry and academia.

IAB (Internet Architecture Board, Internet Structure Committee) members discussed that the deep reason for the increase of DFZ routing table is caused by the dual semantics of IP addresses. In the existing network, IP addresses are both identifiers and locations. At present, IRTF RRG (Internet Research Task ForceRouting Research Group, Internet Research Task Force Routing Working Group) is committed to developing new routing and address architectures to support multi-homing, traffic engineering and mobility. Lisp (Location/ID Separation Protocol, Identity and Location Separation Protocol) is a new routing system framework proposed by Cisco based on the needs of RRG for routing and address research. By separating the current IP address into terminal identification (EIDs, End- identifiers) and routing locations (RLOCs, Routing Locators) to reduce the size of the DFZ routing table, increase the extension and reduce the number of globally visible and routing prefixes.

The network structure of Lisp is shown in Figure 1. The basic idea of LISP is to encapsulate a layer of IP packet headers outside the IP layer to reduce the impact of routes generated by the increase of edge network users on the backbone network routing table and to 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 ("TunnelRouters"). Tunnel routers are divided into ingress tunnel routers (Ingress Tunnel Router, ITR) and Egress Tunnel Router (ETR). Both the ITR and the ETR need to register the binding of the EID and the RLOC in the mapping server (Map-Server, MS). For the host on the ETR side, the ETR is responsible for registering the binding of the host's EID and RLOC, and the ITR is responsible for caching the EID/RLOC binding of the host on the ETR side. Also for the host on the ITR side, the ITR registers the binding between the EID of the host and the RLOC. In addition, the ITR in Lisp is responsible for data encapsulation and mapping search, and searches for the corresponding RLOC information according to the target EID information. 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, but 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-homing.

lisp-MN (LISP Motion Node, Lisp Mobile Node) is a mobility solution for Lisp. lisp-MN defines the nodes in the lisp network as lisp-MN. Lisp-MN is different from ordinary MN (Motion Node, mobile node). Lisp-MN has the function of ETR/ITR. Figure 2 is based on Lisp-MN Schematic diagram of the network structure. When the lisp-MN moves to other networks, the lisp-MN registers its EID/RLOC mapping with its MS.

Contents of the invention

The technical problem to be solved by the present invention is to provide a lisp-MN detachment method, device and mapping server to improve the utilization rate of system resources.

In order to solve the above problems, the present invention provides a method for detachment, which is applied in the Identity and Location Separation Protocol (lisp) network, including:

The network element with the tunnel router function sends a detach request carrying terminal indication information to the mapping server, requesting the mapping server to delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information.

Further, the above method may also have the following feature, the terminal indication information is a terminal identifier.

Further, the above method may also have the following features, the network element having the function of tunnel router is an identity and location separation protocol mobile node (lisp-MN), or an ingress tunnel router, or an egress tunnel router.

Further, the above method may also have the following features, the detachment request also carries one or more routing locations.

The present invention also provides a detachment method, which is applied to a lisp network, comprising: after the mapping server receives a detachment request carrying terminal indication information sent by a network element with a tunnel router function, deleting the locally stored terminal indication information Terminal ID/routing location mapping corresponding to the indicated terminal.

Further, the above method may also have the following feature, when the detachment request does not carry a routing location, the mapping server deletes all terminal identifier/routing location mappings corresponding to the terminal indicated by the terminal indication information stored locally.

Further, the above method may also have the following feature, when the detachment request carries one or more routing locations, the mapping server deletes the locally stored terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information in the same mapping as the one or more routing locations.

Further, the above method may also have the following feature, the terminal indication information is a terminal identifier.

The present invention also provides a detachment device applied to a network element with a tunnel router function, and the device includes:

a generating unit, configured to generate a detach request, where the detach request carries terminal indication information;

A sending unit, configured to send the detachment request to a mapping server, and request the mapping server to delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information.

Further, the above-mentioned device may also have the following feature, the terminal indication information is a terminal identifier.

Further, the above-mentioned apparatus may also have the following feature, the generating unit further carries one or more routing locations in the detach request.

The present invention also provides a mapping server, which includes a receiving unit and a deleting unit, wherein:

The receiving unit is configured to receive a detachment request carrying terminal indication information sent by a network element with a tunnel router function, and notify the deleting unit;

The deleting unit is configured to: after receiving the notification, delete the locally stored terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information.

Further, the above-mentioned mapping server may also have the following features, the deleting unit is also configured to delete all terminal identifiers corresponding to the terminal indicated by the terminal indication information stored locally when the detachment request does not carry a routing location /routing location mapping;

or,

When the detachment request carries one or more routing locations, delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information that is stored locally and whose routing location is the same as the one or more routing locations Terminal ID/routing location mapping.

Further, the above-mentioned mapping server may also have the following feature, the terminal indication information is a terminal identifier.

The present invention releases relevant resources in the original MS in time when the lisp MN/ITR/ETR leaves the network, thereby improving the utilization rate of system resources.

Description of drawings

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

Figure 2 is a schematic diagram of a network structure based on lisp-MN;

Fig. 3 is a schematic diagram of lisp-MN deattachment process;

Fig. 4 is a schematic diagram of lisp deattachment process;

Fig. 5 is a schematic diagram of the format of a detachment request message;

Fig. 6 is a block diagram of deattachment device;

Fig. 7 is a block diagram of a mapping server.

Detailed ways

In order to make the purpose, technical solution and advantages of the present invention more clear, the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined arbitrarily with each other.

After the lisp-MN is moved, the original MS still retains its related mapping information, occupying system resources.

An embodiment of the present invention provides a detachment method, which is applied to a lisp network, and performs the following operations on the side of a tunnel router or a network element with a tunnel router function:

The network element with the tunnel router function sends a detach request carrying terminal indication information to the mapping server, requesting the mapping server to delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information.

Wherein, the terminal indication information may be an terminal identification (EID), or other information capable of identifying the terminal.

Wherein, the network element having the tunnel router function is a lisp-MN, or an ingress tunnel router or an egress tunnel router,

Wherein, the detach request also carries one or more routing locations. It is also possible not to carry the routing location.

In the detachment method provided by the embodiment of the present invention, the following operations are performed on the mapping server side:

After receiving the detach request carrying the terminal indication information sent by the network element with the tunnel router function, the mapping server deletes the locally stored terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information.

Wherein, when the detachment request carries one or more routing locations, the mapping server deletes the locally stored terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information that is associated with the one or more routing locations. Mappings with the same location.

Wherein, when the detach request does not carry a routing location, the mapping server deletes all terminal identifier/routing location mappings of the terminal indicated by the terminal indication information stored locally.

An embodiment including two-side flow is given below.

When the lisp-MN/ITR/ETR does not need to continue to attach to the network (the user needs to shut down or the user needs to actively interrupt the network connection and the subscription is limited), the lisp-MN/ITR/ETR initiates the detachment process, including:

lisp-MN/ITR/ETR sends a detach request to the MS, the detach request carries the terminal identifier, and requests the MS to delete the EID/RLOC mapping corresponding to the terminal identifier stored in it;

After receiving the detach request, the MS deletes the locally stored EID/RLOC mapping corresponding to the terminal identifier and sends a detach response to the lisp-MN/ITR/ETR, and the detach process is completed.

Embodiment one

The architecture of this embodiment is shown in FIG. 3 , including lisp network, communication node lisp-MN (lisp-MN has the function of ETR/ITR network element in lisp protocol) and mapping server MS. Wherein the mapping server MS stores the EID/RLOC mapping that the lisp-MN registers on it. In this embodiment, the detachment request is a mapping deregistration request, including:

Step 301: lisp-MN sends a Map-Unregister Request (mapping unregister request, equivalent to the above-mentioned unattach request) to MS, wherein, this message carries the EID of lisp-MN, and requests to delete the EID stored in MS. EID/RLOC mapping of lisp-MN;

Step 302: After the MS receives the Map-Unregister Request request, the MS deletes the mapping of the EID/RLOC corresponding to the EID stored locally and sends a Map-Unregister Response (mapping de-registration response) to the lisp-MN (this message carries a message indicating that the deletion is successful) or failed instructions). The deattachment process is complete.

The above embodiment is described using Lisp-MN as an example, and the same function can also be implemented on the ITR/ETR network element of the LISP protocol to complete the detachment process of the user, and the ETR is used as an example for illustration.

Embodiment two

Present embodiment is based on the basic agreement of the lisp described in Fig. 1, present embodiment is shown in Fig. 4, mainly comprises the following steps:

Step 401: ETR sends Map-Unregister Request to MS (carrying the EID of MN in this message), requests MS to delete the EID/RLOC mapping corresponding to this EID stored in it;

Step 402: After the MS receives the Map-Unregister Request, the MS deletes the EID/RLOC mapping corresponding to the EID stored locally and sends a Map-Unregister Response to the ETR. This message carries an indication indicating whether the deletion was successful or failed. The deattachment process is complete.

Map in the embodiment of the present invention refers to EID/RLOC Mapping (EID/RLOC mapping).

Let's explain the format of Map-Unregister Request.

Define a lisp message type in lisp:

LISP Map-Unregister: 6 b′0110′

Here, the LISP Map-Unregister message type is defined as 6, and this message type can also be any other binary number.

Define a Map-Unregister Message Format in lisp, as shown in Figure 5, where:

In the message format, the value of the type (Type) field is 6, indicating that the message is a Map-Unregister message.

In addition, the EID-prefix field in the message includes the case that the length of the prefix is 0, and the EID-prefix at this time is the EID, that is, the message includes the two cases of the EID and the EID-prefix.

Since a user's EID may correspond to multiple RLOCs, there are two cases for a user to register. One case is to delete all RLOCs under this EID. In this case, the Map-Unregister Message Format in Figure 7 does not contain the locator field; the other case is to delete one or more RLOCs under this EID. In this case, the locator field in the Map-Unregister Message Format in Figure 7 carries one or more RLOCs to be deleted.

As shown in FIG. 6, it is a block diagram of a detachment device provided by an embodiment of the present invention, which is applied to a network element with a tunnel router function, and the device includes:

a generating unit, configured to generate a detach request, where the detach request carries terminal indication information;

A sending unit, configured to send the detachment request to a mapping server, and request the mapping server to delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information.

Wherein, the terminal indication information is a terminal identifier.

Wherein, the generating unit also carries one or more routing locations in the detach request.

The embodiment of the present invention also provides a network element with a tunnel router function including the above-mentioned detachment device, that is, provides an ITR/ETR/Lisp-MN including the above-mentioned detachment device.

As shown in Figure 7, the block diagram of the mapping server provided by the embodiment of the present invention includes: a receiving unit and a deleting unit, wherein:

The receiving unit is configured to receive a detachment request carrying terminal indication information sent by a network element with a tunnel router function, and notify the deleting unit;

The deleting unit is configured to: after receiving the notification, delete the locally stored terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information.

Wherein, the deleting unit is further configured to, when the detachment request does not carry a routing location, delete all terminal identifier/routing location mappings corresponding to the terminal indicated by the terminal indication information stored locally;

or,

When the detachment request carries one or more routing locations, delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information that is stored locally and whose routing location is the same as the one or more routing locations Terminal ID/routing location mapping.

Those skilled in the art can understand that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk or an optical disk, and the like. Optionally, all or part of the steps in the foregoing embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiments may be implemented in the form of hardware, or may be implemented in the form of software function modules. The present invention is not limited to any specific combination of hardware and software.

Claims (14)

1. A method for deattachment, applied in identity and location separation protocol (lisp) network, is characterized in that, comprising: The network element with the tunnel router function sends a detach request carrying terminal indication information to the mapping server, requesting the mapping server to delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information. 2. The method according to claim 1, wherein the terminal indication information is a terminal identifier. 3. The method according to claim 1 or 2, wherein the network element having the tunnel router function is an identity and location separation protocol mobile node (lisp-MN), or an ingress tunnel router, or an egress tunnel router. 4. The method according to claim 1 or 2, wherein the detach request further carries one or more routing locations. 5. A detachment method, which is applied in a lisp network, is characterized in that, comprising: after the mapping server receives a detachment request carrying terminal indication information sent by a network element having a tunnel router function, deletes the locally stored terminal The terminal identifier/routing location mapping corresponding to the terminal indicated by the indication information. 6. The method according to claim 5, wherein when the detach request does not carry a routing location, the mapping server deletes all terminal identifiers/routes corresponding to the terminal indicated by the terminal indication information stored locally location map. 7. The method according to claim 5, wherein when the detach request carries one or more routing locations, the mapping server deletes the locally stored terminal identifier corresponding to the terminal indicated by the terminal indication information The same mapping as the one or more routing locations in the /routing location mapping. 8. The method according to any one of claims 5 to 7, wherein the terminal indication information is a terminal identifier. 9. A detachment device applied to a network element having a tunnel router function, characterized in that the device comprises: a generating unit, configured to generate a detach request, where the detach request carries terminal indication information; A sending unit, configured to send the detachment request to a mapping server, and request the mapping server to delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information. 10. The device according to claim 9, wherein the terminal indication information is a terminal identifier. 11. The device according to claim 9 or 10, wherein the generating unit further carries one or more routing locations in the detach request. 12. A mapping server, characterized in that, the mapping server includes a receiving unit and a deleting unit, wherein: The receiving unit is configured to receive a detachment request carrying terminal indication information sent by a network element with a tunnel router function, and notify the deleting unit; The deleting unit is configured to: after receiving the notification, delete the locally stored terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information. 13. The mapping server of claim 12, wherein: The deleting unit is further configured to, when the detach request does not carry a routing location, delete all terminal identifier/routing location mappings corresponding to the terminal indicated by the terminal indication information stored locally; or, When the detachment request carries one or more routing locations, delete the terminal identifier/routing location mapping corresponding to the terminal indicated by the terminal indication information that is stored locally and whose routing location is the same as the one or more routing locations Terminal ID/routing location mapping. 14. The mapping server according to claim 12 or 13, wherein the terminal indication information is a terminal identifier.

Images