VPN Implementation Processing Method and Device for Edge Device

Patent metadata

Field	Value
Publication number	US-2016134591-A1
Application number	US-201414896024-A
Country	US
Kind code	A1
Filing date	May 15, 2014
Priority date	Jun 5, 2013
Publication date	May 12, 2016
Grant date	—

Abstract

The present disclosure discloses a Virtual Private Network (VPN) implementation processing method and device for an edge device. The method includes that: a VPN application request is acquired, wherein the VPN application request carries attribute configuration information about a VPN; VPN routing information is received from each edge device in the VPN; and VPN routing control information is sent to the edge devices, wherein the VPN routing control information is routing information obtained by performing centralized calculation and processing on the attribute configuration information and the VPN routing information. Adopting the above solution provided in the present disclosure solves the technical problems in the prior art that there are more complex configuration and table item contents in an automatic control solution for the VPN, etc., thereby being able to automatically control simpler configuration issuing, more intensive table item management and table item issuing under a uniform control platform, so that the configuration and table item capacity of the existing device are reduced.

First claim

What is claimed is:

1 . A Virtual Private Network (VPN) implementation processing method for an edge device, comprising:
acquiring a VPN application request, wherein the VPN application request carries attribute configuration information about a VPN; receiving VPN routing information from each edge device in the VPN; and sending VPN routing control information to the each edge device, wherein the VPN routing control information is routing information obtained by performing centralized calculation and processing on the attribute configuration information and the VPN routing information.

2 . The method according to claim 1 , wherein the VPN routing information or the routing control information comprises at least one piece of the following:
a VPN Table Identity (ID) and table item entries, wherein the VPN Table ID is used for locally identifying a table item number generated according to the VPN routing information.

3 . The method according to claim 2 , wherein the table item entries comprise at least one of the following:
a key value of table item, a next hop, an outgoing interface, a protocol type, a VPN ID, a VPN forwarding plane ID, a master/slave ID, a load sharing ID and effective time.

4 . The method according to claim 2 , wherein the table item entries in the VPN routing information and the table item entries in the routing control information are partly same or totally different.

5 . The method according to claim 3 , wherein the key value of table item comprises: a destination address of a data message.

6 . The method according to claim 3 , wherein the next hop is a direct next hop ID of the edge device or a peer ID of a multi-hop neighbour.

7 . The method according to claim 3 , wherein the outgoing interface from the edge device to a Network Management System (NMS) is a local VPN binding interface or a local device ID of the edge device, and the outgoing interface from the NMS sends to the edge device is a mapping ID of a remote edge device.

8 . The method according to claim 7 , wherein the mapping ID comprises at least one of the following:
the ID of the remote edge device; a logical outgoing interface ID or a physical outgoing interface ID of the edge device to the remote edge device.

9 . The method according to claim 3 , wherein the protocol type is used for identifying a Routing System (I2RS) protocol and/or other routing protocols except the I2RS protocol.

10 . The method according to claim 3 , wherein the VPN forwarding plane ID is used for identifying an encapsulated or de-encapsulated data plane message.

11 . The method according to claim 3 , wherein the master/slave ID is used for respectively identifying multiple next hops with the same key value of table item as master and slave.

12 . The method according to claim 3 , wherein the VPN ID is in one-to-one correspondence with the VPN on a control plane.

13 . The method according to claim 3 , wherein the load sharing ID is used for identifying the multiple next hops with the same key value of table item.

14 . The method according to claim 3 , wherein the effective time is realized by at least one of the following ways:
taking effect and timing according to time to live which is configured by the edge device or defaulted; synchronously taking effect on the edge device according to an effective time period which is issued by the NMS; sending or cancelling sending the routing information in the NMS according to local effective time.

15 . The method according to claim 1 , wherein the attribute configuration information comprises at least one piece of the following: a VPN ID, information about setting of a Routing Target (RT) value, information about ID of a Provider Edge (PE) site requiring opening the VPN, information about a type of a routing protocol needing to be enabled, priority configuration information and policy information.

16 . The method according to claim 15 , wherein the policy information comprises at least one piece of the following:
a filtering or changing policy based on table item entry contents, a time presetting policy, a master/slave policy and a load sharing policy.

17 . The method according to any one of claims 1 to 16 , wherein the edge devices comprise at least one of the following: a PE and a Customer Edge (CE).

18 . A Virtual Private Network (VPN) implementation processing method for an edge device, characterized by comprising:
sending VPN routing information to a Network Management System (NMS); receiving VPN routing control information from the NMS, wherein the VPN routing control information is VPN routing information obtained by performing centralized calculation and processing on the VPN routing information and attribute configuration information about a VPN which is obtained by the NMS from a VPN application request; configuring the edge device according to the VPN routing control information.

19 . The method according to claim 18 , wherein the VPN routing information or the routing control information comprises at least one piece of the following:
a VPN Table Identity (ID) and table item entries, wherein the VPN Table ID is used for locally identifying a table item number generated according to the VPN routing information.

20 . The method according to claim 19 , wherein the table item entries comprise at least one of the following:
a key value of table item, a next hop, an outgoing interface, a protocol type, a VPN ID, a VPN forwarding plane ID, a master/slave ID, a load sharing ID and effective time; wherein, the key value of table item comprises: a destination address of a data message; and/or the next hop is a direct next hop ID of the edge device or a peer ID of a multi-hop neighbour; and/or the outgoing interface from the edge device to the NMS is a local VPN binding interface or a local device ID of the edge device and the outgoing interface from the NMS sends to the edge device is a mapping ID of a remote edge device; and/or the protocol type is used for identifying a Routing System (I2RS) protocol and/or other routing protocols except the I2RS protocol; and/or the VPN forwarding plane ID is used for identifying a encapsulated or de-encapsulated data plane message; and/or the master/slave ID is used for respectively identifying multiple next hops with the same key value of table item as master and slave; and/or the VPN ID is in one-to-one correspondence with the VPN on a control plane; and/or the load sharing ID is used for identifying the multiple next hops with the same key value of table item.

21 . The method according to claim 19 , wherein the table item entries in the VPN routing information and the table item entries in the routing control information are partly same or totally different.

22 . The method according to claim 20 , wherein the mapping ID comprises at least one of the following:
an ID of the remote edge device; a logical outgoing interface ID or a physical outgoing interface ID of the edge device to the remote edge device.

23 . The method according to claim 20 , wherein the effective time is realized by at least one of the following ways:
taking effect and timing according to time to live which is configured by the edge device or defaulted; synchronously taking effect in the edge device according to an effective time period which is issued by the NMS; sending or cancelling sending the routing information in the NMS according to local effective time.

Assignees

• Zte Corp

Inventors

• Liao ting
• Wu Bo
• Dai Xuehui

Classifications

• H04L41/122

  of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV] · CPC title

• H04L41/0895

  Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title

• H04L63/0272 Primary

  Virtual private networks · CPC title

• H04L45/14

  Routing performance; Theoretical aspects · CPC title

• H04L45/04

  Interdomain routing, e.g. hierarchical routing · CPC title