WO2014194749A1 - 边缘设备的vpn实现处理方法及装置 - Google Patents
边缘设备的vpn实现处理方法及装置 Download PDFInfo
- Publication number
- WO2014194749A1 WO2014194749A1 PCT/CN2014/077585 CN2014077585W WO2014194749A1 WO 2014194749 A1 WO2014194749 A1 WO 2014194749A1 CN 2014077585 W CN2014077585 W CN 2014077585W WO 2014194749 A1 WO2014194749 A1 WO 2014194749A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- vpn
- identifier
- information
- entry
- edge device
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0272—Virtual private networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/64—Hybrid switching systems
- H04L12/6418—Hybrid transport
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/04—Interdomain routing, e.g. hierarchical routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/14—Routing performance; Theoretical aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
- H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
Definitions
- the present invention relates to the field of communications, and in particular, to a virtual private network (VPN) implementation method and apparatus for an edge device.
- VPN virtual private network
- the IETF standards organization has newly established an Interface to the Routing System (I2RS) working group to study an interface oriented to a routing system, in order to make the existing routing system compatible.
- I2RS Routing System
- RAIB Routing Information Base
- the approximate I2RS model described in the existing individual draft of the relevant I2RS is shown in Figure 1.
- the dotted line in the lower half of the figure represents a router internal implementation component.
- the I2RS proxy (Agent) is to support the I2RS to add a new component to the router, so that the I2RS client (Client) can obtain the configuration management and topology routing information of the router through the I2RS agent, and also supports the I2RS client through the I2RS.
- the agent sends configuration information such as configuration and routing entries to the router.
- One of the biggest differences between the working group and the Open Source Foundation (0 F), which is implemented by the Software Defined Network (SDN), is that I2RS is not directly forwarded to the data plane.
- the forwarding table in the Forwarding Information Base (FIB) affects the final forwarding table by affecting the information of the protocol routing table, so that it can be better compatible with existing routers.
- FIB Forwarding Information Base
- the VPN is used for the logical network isolation technology in the physical network.
- the implementation of the Multi-Protocol Label Switching (MPLS) VPN of the current router generally provides the Layer 2 VPN service or the Layer 3 VPN service to the customer through the provider.
- MPLS and Border Gateway Protocol BGP
- the operator provides the VPN service-related attribute information to the customer, and the customer can perform the user edge device according to the information.
- Customer Edge referred to as CE
- CE Customer Edge
- CE is configured or authorized by the operator to be configured on the CE by the operator, and the operator is responsible for the connectivity of the carrier network required for the VPN service provided to the customer.
- a method for processing a VPN implementation of an edge device including: acquiring a VPN application request, where the VPN application request carries VPN attribute configuration information; receiving each edge device from a VPN
- the VPN routing information is sent to the edge device, where the VPN routing control information is routing information obtained by performing centralized calculation processing on the attribute configuration information and the VPN routing information.
- the VPN routing information or the routing control information includes at least one of the following: a VPN Table ID and an entry of the entry, where the VPN Table ID is used to locally identify the entry number generated by the VPN routing information.
- the entry of the entry includes at least one of the following: the key value of the entry, the next hop, the outbound interface, the protocol type, the VPN identifier, the VPN forwarding plane identifier, the primary and secondary identifiers, the load sharing identifier, and the effective time.
- the entry of the entry in the VPN routing information and the entry of the entry in the routing control information are the same or completely different.
- the key values of the above entries include: The destination address of the data packet.
- the next hop is the direct next hop identifier of the edge device or the peer identifier of the multi-hop neighbor.
- the outbound interface is the local VPN binding interface or the local device identifier of the edge device when the edge device sends the network management system.
- the mapping identifier includes at least one of the following: an identifier of the remote edge device, a logical outbound interface identifier of the edge device to the remote edge device, or a physical outgoing interface identifier.
- the above protocol types are used to identify the routing system interface I2RS protocol and/or other routing protocols than the I2RS protocol.
- the VPN forwarding plane identifier is used to identify the data plane packet after encapsulation or decapsulation.
- the primary backup identifier is used to identify multiple next hops carried in the key value of the same entry as the primary and backup. The above VPN identifier corresponds to the VPN on the control plane.
- the load balancing identifier is used to identify multiple next hops carried in the key value of the same entry.
- the above-mentioned effective time is implemented in at least one of the following ways: It takes effect according to the configuration of the edge device or the default lifetime; the synchronization takes effect on the edge device according to the effective time period delivered by the network management system; The time for the routing information to be validly sent or revoked.
- the foregoing attribute configuration information includes at least one of the following: a VPN identifier, a route target (RT) value setting information, a PE site identifier information to be activated, a routing protocol type information to be enabled, a priority configuration information, and a policy. information.
- the foregoing policy information includes at least one of the following: a filtering or changing policy based on the contents of the entry of the entry, a time preset policy, a primary standby policy, and a load sharing policy.
- the edge device includes one of the following: a provider edge PE device and a user edge CE device.
- a VPN implementation processing method for an edge device including: transmitting VPN routing information to a network management system; receiving VPN routing control information from a network management system, where the VPN routing control information is The VPN routing information obtained by centrally calculating and processing the VPN routing information and the attribute configuration information of the VPN obtained by the network management system from the VPN application request; configuring the edge device according to the VPN routing control information.
- the foregoing VPN routing information or routing control information includes at least one of the following:
- the VPN table ID is used to identify the entry number generated by the VPN routing information.
- the entry of the entry includes at least one of the following: a key value of the entry, a next hop, an outbound interface, a protocol type, a VPN identifier, a VPN forwarding plane identifier, a primary backup identifier, a load sharing identifier, and an effective time;
- the destination address of the data packet is: and/or the next hop is the direct next hop identifier of the edge device or the peer identifier of the multi-hop neighbor; and/or the outbound interface is sent by the edge device to the network management system.
- the local VPN binding interface or local device ID of the edge device is sent when the network management system sends the edge device.
- the mapping identifier of the remote edge device; and/or the protocol type is used to identify the routing system interface I2RS protocol and/or other routing protocols other than I2RS; and/or the VPN forwarding surface identifier is used for encapsulation or decapsulation
- the data plane packet is identified; and/or the primary and secondary identifiers are used to identify multiple next hops carried in the key value of the same entry as primary and backup respectively; and/or the VPN identifier is corresponding to the VPN on the control plane.
- the load sharing identifier is used to identify multiple next hops carried by the same entry key value.
- the entry of the entry in the VPN routing information and the entry of the entry in the routing control information are the same or completely different.
- the mapping identifier includes at least one of the following: an identifier of the remote edge device, a logical outbound interface identifier of the edge device to the remote edge device, or a physical outgoing interface identifier.
- the above-mentioned effective time is implemented in at least one of the following ways: It takes effect according to the configuration of the edge device or the default lifetime; the synchronization takes effect on the edge device according to the effective time period delivered by the network management system; The time for the routing information to be validly sent or revoked.
- the foregoing attribute configuration information includes at least one of the following: a VPN identifier, an RT value setting information, an edge device site identification information that needs to be activated by the VPN, a routing protocol type information to be enabled, a priority configuration information, and policy information.
- the foregoing policy information includes at least one of the following: a filtering or changing policy based on the contents of the entry of the entry, a time preset policy, a primary standby policy, and a load sharing policy.
- a VPN implementation processing apparatus for an edge device includes: an obtaining module, configured to acquire a VPN application request, where the VPN application request carries a VPN attribute configuration information; a receiving module, setting In order to receive VPN routing information from each edge device under the VPN, the sending module is configured to send VPN routing control information to the edge device, where the VPN routing control information is obtained by performing centralized calculation processing on the attribute configuration information and the VPN routing information. Routing information.
- the receiving module and the sending module are respectively configured to receive VPN routing information and send VPN routing control information when the VPN routing information and/or the VPN routing control information includes at least one of the following: a VPN list identifier, a Table ID, and an entry, where the VPN The table ID is used to locally identify the entry number generated by the VPN user information.
- the receiving module and the sending module are respectively configured to receive the VPN routing information and send the VPN routing control information when the entry of the entry includes at least one of the following: the key value of the entry, the next hop, the outbound interface, the protocol type, the VPN identifier, and the VPN forwarding.
- the key value of the entry includes: the destination address of the data packet; and/or the next hop is the direct next hop identifier of the edge device or the peer identifier of the multi-hop neighbor; and/or the outbound interface is sent on the edge device.
- the VPN forwarding plane identifier is used to identify data plane packets after encapsulation or decapsulation; and/or the primary and secondary identifiers are used for key values of the same entry
- the multiple next hops that are carried are respectively identified as primary and backup; and/or the VPN identifier is corresponding to the VPN-on-one at the control plane; and/or the load-sharing identifier is used to carry multiple multiples of the same entry key value. Jump to identify.
- a VPN implementation processing apparatus for an edge device including: a sending module, configured to send VPN routing information to a network management system; and a receiving module configured to receive a VPN route from the network management system Control information, where the VPN routing control message is routing information obtained by centrally calculating and processing the VPN routing information and the attribute configuration information of the VPN obtained by the network management system from the VPN application request; the configuration module is set to control information according to the VPN routing Configure the edge device.
- the receiving module and the sending module are respectively configured to receive the VPN routing control information and send the VPN routing information when the VPN routing control information and/or the VPN routing information includes at least one of the following: a VPN list identifier, a Table ID, and an entry, where the VPN The table ID is used to locally identify the entry number generated by the VPN routing information.
- the receiving module and the sending module are respectively configured to receive the VPN routing control information and send the VPN routing information when the entry of the entry includes at least one of the following: the key value of the entry, the next hop, the outbound interface, the protocol type, the VPN identifier, and the VPN forwarding.
- the key values of the entry include: the destination address of the data packet; and/or the next hop is the direct next hop identifier of the edge device or the multi-hop neighbor.
- the peer ID is identified; and/or the outbound interface is the local VPN binding interface or the local device identifier of the edge device when the edge device sends the network management system, and is the mapping identifier of the remote edge device when the network management system sends the edge device
- the protocol type is used to identify the routing system interface I2RS protocol and/or other routing protocols other than I2RS
- the VPN forwarding plane identifier is used to identify the data plane message after encapsulation or decapsulation;
- the primary and secondary identifiers are used to identify multiple next hops carried in the key value of the same entry as primary and backup respectively; and/or the VPN identifier is And a control surface corresponding to VPN-; and / or load sharing identification for identifying the next hop of the plurality of entries of the same key value is carried.
- the embodiment of the present invention solves the problem that the VPN automatic control scheme exists in the related technology by using the centralized calculation processing of the VPN application request and the VPN routing information of the edge device, and the obtained configuration and routing control information are delivered.
- Technical problems such as configuration and the contents of the entries are complex, so that the unified control can be The simpler configuration of the automatic control is delivered, and the centralized management of the entries and the delivery of the entries are reduced, which reduces the configuration of existing devices and the capacity of the entries.
- FIG. 1 is a schematic diagram of an I2RS model according to the related art
- FIG. 2 is a flowchart of a VPN implementation processing method of an edge device according to an embodiment of the present invention
- FIG. 3 is a VPN implementation of an edge device according to an embodiment of the present invention
- FIG. 4 is another block diagram of a VPN implementation processing method for an edge device according to an embodiment of the present invention
- FIG. 5 is another structural block diagram of a VPN implementation processing device for an edge device according to an embodiment of the present invention
- 6 is a topological schematic diagram of an I2RS network according to a preferred embodiment of the present invention
- FIG. 7 is another topological schematic diagram of an I2RS network according to a preferred embodiment of the present invention
- FIG. 8 is an implementation of automatic control of a VPN network according to a preferred embodiment of the present invention.
- Step S202 Acquire a VPN application request, where The VPN application request carries the attribute configuration information of the VPN.
- the method for obtaining the VPN application request may be implemented by, for example, receiving the VPN application request from the VPN side device, or receiving the VPN application request from the upper layer service.
- Step S204 Receive VPN routing information from each edge device under the VPN. The routing information generally includes but is not limited to a route from a local CE device.
- Step S206 Send VPN routing control information to the edge device, where the VPN routing control information is routing information obtained by performing centralized calculation processing on the attribute configuration information and the VPN routing information.
- the execution order between the above steps S202 and S204 is not limited thereto. For example, step S204 may be performed first, and then step S202 may be performed.
- the VPN application request and the VPN user information of the edge device are subjected to centralized calculation processing, that is, unified control, so that the simpler configuration can be automatically controlled and distributed in the unified control platform.
- the edge device before receiving the VPN user information (mainly represented as routing information) from the edge device, the edge device may be determined according to the VPN application request and the local network topology information. After the foregoing edge device is determined according to the foregoing VPN application request and the local network topology information, the VPN configuration information is generated according to the specified information and the topology information collected by the network management system, and the VPN configuration information is sent to the edge device, where the edge device is configured according to the edge device. The VPN configuration information generates the VPN user information.
- the VPN user information mainly represented as routing information
- the edge device may be determined according to the VPN application request and the local network topology information.
- the VPN configuration information is generated according to the specified information and the topology information collected by the network management system, and the VPN configuration information is sent to the edge device, where the edge device is configured according to the edge device.
- the VPN configuration information generates the VPN user information.
- the VPN user information includes at least one of the following: a VPN Table ID, and an entry of the entry, where the VPN Table ID is used to locally identify the entry number generated by the VPN user information, so that the I2RS Client directly reads and writes the VPN related entries.
- the entry of the entry includes at least one of the following: the key value of the entry, the next hop, the outbound interface, the protocol type, the VPN identifier, the VPN forwarding plane identifier, the primary and secondary identifiers, the load sharing identifier, and the effective time.
- the VPN routing control information is the VPN routing information processed by the network management system via the policy calculation, and can be expressed as a change of the entry of the two entries.
- the entry of the entry in the VPN routing information is the same as or completely different from the entry of the entry in the routing control information.
- the key values of the above entries include: The destination address of the data packet.
- the L2VPN is represented by a media access control (MAC) address, which is represented by an IP address in the L3 VPN, and is not limited to the destination address, and may be parsed from the data packet as needed. Valid fields such as source address, port number, etc. are also supported.
- the next hop is the direct next hop identifier of the edge device or the peer identifier of the multi-hop neighbor.
- the ID of the remote edge device that advertises the key value of the entry to the peer device is the IP address of the loopback that identifies the remote edge device or the IP address of the link-building interface.
- the outbound interface is a local VPN binding interface or a local device identifier of the edge device when the edge device sends the network management system to the edge device, and is a mapping identifier of the remote edge device when the network management system sends the edge device.
- the mapping identifier includes at least one of the following: an identifier of the remote edge device, a logical outbound interface identifier of the edge device to the remote edge device, or a physical outgoing interface identifier.
- the mapping identifier may be a local tunnel identifier (ID), where the local tunnel ID indicates an end-to-end connection from the local to the remote edge device, and may be a Generic Routing Encapsulation (GRE) tunnel ID.
- GRE Generic Routing Encapsulation
- RSVP Resource Reserve Protocol
- TE Traffic Engineering
- LSP Label Switched Paths
- the above protocol types are used to identify the I2RS protocol and/or other routing protocols than the I2RS protocol.
- the VPN forwarding plane identifier is used to identify the data plane packet after encapsulation or decapsulation.
- the primary backup identifier is used to identify multiple next hops carried in the key value of the same entry as the primary and backup, respectively, so that multiple next hops are respectively carried by the primary backup identifier.
- the VPN identifier is corresponding to the VPN on the control plane, that is, the VPN identifier is used to globally uniquely identify a VPN on the control plane, including but not limited to using the RT method.
- the load balancing identifier is used to identify multiple next hops carried in the key value of the same entry, so that multiple next hops of the key value of the same entry can take effect at the same time.
- the above-mentioned effective time is implemented in at least one of the following ways: According to the configuration of the edge device or the default time-to-live time, the time-to-live time of the entry is valid. For example: Use the timer that comes with the PE device.
- the entry After the generation (for example, the countdown to the storage time is 300s), when the update is not received, the entry is considered to be aging.
- the synchronization is valid on the edge device according to the effective time period delivered by the NMS.
- the time period delivered by the NMS where the entry is valid within the time range (for example, 8:00-8:30), and the entry is placed in the RIB table within the effective time of the edge device synchronization.
- the I2RS client of the network management system is sent and revoked when the effective time of the network management system ends.
- the information of the specified entry that is, the time management is maintained on the I2RS client. Only when the time is valid, the entry is sent, and when it is not valid, the entry is revoked.
- the application request includes an opening request of an upper layer service and/or a policy: a VPN service, a traffic matching filtering, a load sharing, a time value, and the like.
- the foregoing attribute configuration information includes at least one of the following: a VPN identifier, a routing destination (RT) value setting information, a PE site identifier information that needs to be activated by the VPN, routing protocol type information to be enabled, priority configuration information, and policy information.
- the policy information includes at least one of the following: a filtering or changing policy based on the content of the entry of the entry, a time preset policy, a primary standby policy, and a load sharing policy.
- the forwarding device includes one of the following: a PE device and a CE device.
- the foregoing VPN user information includes at least one of the following: VPN identification information, routing target RT value setting information,
- FIG. 3 is a structural block diagram of a VPN implementation processing apparatus of an edge device according to an embodiment of the present invention.
- the device may be, but is not limited to, applied to the network management system.
- the method includes: an obtaining module 30, connected to the sending module 34, configured to obtain a VPN application request, where the VPN application request carries a VPN attribute configuration
- the receiving module 32 is connected to the sending module 34, and configured to receive VPN routing information from each edge device under the VPN; the sending module 34 is configured to send VPN routing control information to the edge device, where the VPN routing control
- the information is the routing information obtained by performing the centralized calculation processing on the attribute configuration information and the VPN routing information.
- the functions implemented by the above modules can also be automatically controlled under the unified control platform to be sent in a simpler configuration.
- the table management and the entry are delivered, which reduces the configuration of existing devices and the capacity of the entries.
- the receiving module 32 and the sending module 34 are respectively configured to receive the VPN routing information and send the VPN routing control information when the VPN routing information and/or the VPN routing control information includes at least one of the following: a VPN list identifier
- the receiving module and the sending module are respectively configured to receive the VPN routing information and send the VPN routing control information when the entry includes at least one of the following: The key value of the entry, the next hop, the outgoing interface, the protocol type, the VPN identifier, the VPN forwarding plane identifier, the primary and secondary identifiers, the load balancing identifier, and the effective time.
- the key values of the entry include: the destination address of the data packet.
- next hop is a direct next hop identifier of the edge device or a peer identifier of the multi-hop neighbor; and/or the outgoing interface is the edge device sent to the network management system
- the local VPN binding interface or the local device identifier of the edge device is a mapping identifier of the remote edge device when the network management system sends the edge device; and/or the protocol type is used to identify the routing system interface I2RS protocol and/or And other routing protocols other than the I2RS; and/or the VPN forwarding plane identifier is used to identify the data plane packet after encapsulation or decapsulation; and/or the primary backup identifier is used to use the same entry.
- the plurality of next hops carried by the key value are respectively identified as the primary and the standby; and/or the VPN identifier is corresponding to the VPN on the control plane; and/or the load sharing identifier is used to key to the same entry. Multiple next hops carried by the value are identified.
- each of the foregoing modules may be implemented by a corresponding processor, for example, may be implemented by one processor, or may be partially or completely integrated into one processor, but is not limited to the above combination.
- a method for processing a virtual private network VPN of an edge device is provided. As shown in FIG. 4, the method includes: Step S402: Send VPN routing information to a network management system; Step S404, receive a network management system from the network management system.
- the VPN routing control information is: the VPN routing control information is the VPN routing information obtained by performing centralized calculation processing on the VPN routing information and the attribute configuration information of the VPN obtained by the network management system from the VPN application request; Step S406, according to the VPN routing control Information is configured for the edge device.
- the VPN routing information or the routing control information includes at least one of the following: a VPN list identifier, a table ID, and an entry, where the VPN Table ID is used to locally identify the entry number generated by the VPN routing information.
- the entry of the entry includes at least one of the following: a key value of the entry, a next hop, an outbound interface, a protocol type, a VPN identifier, a VPN forwarding plane identifier, a primary backup identifier, a load sharing identifier, and an effective time;
- the destination address of the data packet is: and/or the next hop is the direct next hop identifier of the edge device or the peer identifier of the multi-hop neighbor; and/or the outbound interface is sent by the edge device to the network management system.
- the local VPN binding interface or local device identifier of the edge device which is the mapping identifier of the remote edge device when the network management system sends the edge device; and/or the protocol type is used to identify the I2RS protocol and/or other than the I2RS Routing protocol; and/or VPN
- the forwarding plane identifier is used to identify the data plane packet that is encapsulated or decapsulated; and/or the primary backup identifier is used to identify multiple next hops carried by the key value of the same entry as primary and backup respectively;
- the VPN identifier is configured to correspond to the VPN on the control plane; and/or the load sharing identifier is used to identify multiple next hops carried by the key value of the same entry.
- the entry of the entry in the VPN routing information and the entry of the entry in the routing control information are the same or completely different.
- the mapping identifier includes at least one of the following: an identifier of the remote edge device, a logical outbound interface identifier of the edge device to the remote edge device, or a physical outgoing interface identifier.
- the above-mentioned effective time is implemented in at least one of the following ways: It takes effect according to the configuration of the edge device or the default lifetime; the synchronization takes effect on the edge device according to the effective time period delivered by the network management system; The time for the routing information to be validly sent or revoked.
- the foregoing attribute configuration information includes at least one of the following: a VPN identifier, a routing target RT value setting information, an edge device site identification information that needs to be activated by the VPN, routing protocol type information to be enabled, priority configuration information, and policy information.
- the foregoing policy information includes at least one of the following: a filtering or changing policy based on the contents of the entry of the entry, a time preset policy, a primary standby policy, and a load sharing policy.
- the embodiment further provides a VPN implementation processing device for an edge device. As shown in FIG. 5, the device includes: a sending module 50, connected to the receiving module 52, configured to send VPN routing information to the network management system.
- the receiving module 52 is connected to the configuration module 54 and configured to receive VPN routing control information from the network management system, where the VPN routing control message is to request the VPN application by using the VPN routing information and the network management system.
- the routing information obtained by the centralized configuration processing of the attribute configuration information of the VPN is obtained; the configuration module 54 is configured to configure the edge device according to the VPN routing control information.
- the sending module 50 and the receiving module 52 respectively send the VPN routing information and receive the routing control information when the VPN routing information and/or the routing control information includes at least one of the following: a VPN list identifier, a table ID, and an entry. An entry, where the VPN Table ID is used to locally identify an entry number generated by the VPN routing information.
- the receiving module 52 and the sending module 50 are respectively configured to receive the VPN routing information and send the VPN routing control information when the entry includes at least one of the following: The key value of the entry, the next hop, the outgoing interface, the protocol type, the VPN identifier, the VPN forwarding plane identifier, the primary and secondary identifiers, the load balancing identifier, and the effective time.
- the key values of the entry include: the destination address of the data packet.
- next hop is a direct next hop identifier of the edge device or a peer identifier of the multi-hop neighbor; and/or the outgoing interface is the edge device sent to the network management system
- the local VPN binding interface or the local device identifier of the edge device is a mapping identifier of the remote edge device when the network management system sends the edge device; and/or the protocol type is used to identify the routing system interface I2RS protocol and/or And other routing protocols other than the I2RS; and/or the VPN forwarding plane identifier is used to identify the data plane packet after encapsulation or decapsulation; and/or the primary backup identifier is used to use the same entry.
- Embodiment 1 An IP/MPLS network dynamically establishes and manages a VPN service through a network management system.
- the network management system receives an application request of a VPN service, and performs unified control on an entry of an operator's edge forwarding device through an interface, including: After receiving the VPN routing information sent by the operator's edge device, the system collects the received information and performs the centralized calculation processing in combination with the application request, and generates the calculated information and sends the information to the forwarding device.
- the VPN routing information includes the VPN table ID and the entry of the entry.
- the content of the entry includes but is not limited to: the key value of the entry, the next hop, the outbound interface, the VPN identifier, the VPN forwarding plane identifier, the protocol type, and the primary backup. Some or all of the contents such as identification, load sharing identification, and effective time.
- the network management system includes a forwarding device information interaction module, an application interaction module, a calculation module, and a storage module.
- the forwarding device information interaction module is configured to perform information collection or information delivery interaction on the forwarding device, and may be an I2RS client module.
- the forwarding device includes an network management system interaction module, and may be an I2RS agent module.
- the carrier edge forwarding device can be a PE or a CE.
- the above application requests are the opening request of the upper layer service and the policy, including the VPN service, the traffic matching filtering, the load sharing, the time value and other policy requests.
- the centralized calculation processing includes performing centralized calculation processing on the calculation and storage module according to the application request, and collecting the information combined with the forwarding device information and storing the information locally.
- the VPN forwarding plane identifier is used for encapsulation and decapsulation of data plane packets, including but not limited to being expressed in the form of a label.
- the above protocol types are used to identify the Routing System Interface (I2RS) protocol and/or other routing protocols other than the I2RS protocol, such as the bgp protocol.
- the primary backup identifier is used to simultaneously deliver the optimal sub-optimal path identifier for forming protection.
- the load balancing identifier is used to identify multiple next hops carried in the key value of the same entry, so that multiple next hops of the key value of the same entry can be valid at the same time, so that multiple paths form load sharing.
- a communication device for an IP/MPLS network is also provided, including a network management system interaction module.
- the network management system interaction module sends a locally received VPN routing information to the network management system, and receives the remote VPN routing information from the network management system to establish a VPN user connection.
- the VPN routing information is composed of the VPN Table ID and the entry of the entry.
- the entry in the entry includes but is not limited to: the key value of the entry, the next hop, the outbound interface, the VPN identifier, the VPN forwarding plane identifier, and the primary standby identifier. Some or all of the contents of the load sharing identification, effective time, etc.
- the communication device creates an entry to maintain VPN routing information.
- the foregoing creation entry includes: generating a locally unique VPN Table ID to identify the unique VPN identifier entry, where the entry of the entry is composed of part or all of the content of the foregoing entry; the maintenance entry may be a local real-time update or
- the client (Client) is controlled by a proxy.
- the embodiment further provides a network management system: a forwarding device information interaction module, an application interaction module, a calculation module, and a storage module.
- the application interaction module is mainly used for receiving an application request of an upper layer service, and the forwarding device information interaction module is configured to interact with the forwarding device, and may be an I2RS client module.
- the information obtained by the application request information and the forwarding device information interaction module is used for centralized calculation, and the information generated by the calculation result information device is generated through centralized calculation, and a new information is sent to the forwarding device.
- the new information is mainly composed of the table ID and the entry of the entry.
- the entry in the entry includes but is not limited to: the key value of the entry, the next hop, the outbound interface, the VPN identifier, the VPN forwarding plane identifier, the primary standby identifier, Some or all of the contents of the load sharing identification, effective time, etc.
- Embodiment 2 L3 VPN automatic control and related entries are issued As shown in Figure 6, the site 1 and the site 3 belong to the same VPN1. The site 2 and the site 4 belong to the same VPN 2.
- VPN access is performed on each PE
- the existing implementation needs to be performed on each PE.
- the routes of the VPM and the routes of the VPN2 are maintained on the PEs through different entries.
- the RTs with matching attributes are imported and exported to the corresponding VPN forwarding table.
- the PE1, PE2, and PE3 are advertised in the VPN messages carried by the BGP.
- the virtual routing and forwarding Instance (VRF) route is advertised.
- the message is also received on PE2, but the message is completely invalid for PE2 and takes up the bandwidth transmission and protocol packet filtering processing time.
- the configuration is as follows: 1. Configure the address of loopback1 and interface IF1 on CE1 and establish an external border gateway protocol with PE1.
- vrf vpnl on PE1, bind IF1 to vrf vpnl, configure the address, configure loopbackl, IF2 address, and configure Open Shortest Path First (OSPF) to advertise the IF2 interface address.
- OSPF Open Shortest Path First
- MPBGP Multi-Protocol Border Gateway Protocol
- LDP Label Distribution Protocol
- the router-id for LDP The configuration of the VPN includes: ip vrfvpnl, routing distinguishing (Route Distinguisher, RD for short), and RT (to identify the identifier carried in the imported and exported routes);
- the interface is connected to the CE side.
- the route learned by the interface is a private network route.
- the MPBGP neighbor relationship is established. This function is used to determine the neighbors and distribute the labels to the local private network routes.
- the neighboring IDs are used to find the outer labels.
- the user can propose the requirement according to the application layer provided in the I2RS model.
- the user of VPN1 proposes to the network management system through the application layer that the sites 1 and 3 need to be opened through the VPN.
- the network management system knows that the PEs connected to the sites 1 and 3 are the PE1 and the PE3. Then, the network management system returns the interfaces and configuration information of the PE1 and the PE3 to the user.
- the network management system is interconnected with the directly connected CE side.
- the configuration of the corresponding VPN1 is delivered to PE1 and PE3 through the configuration module, including: 1.
- Startup of the VRF Configuring the VRF instance, configuring the RD, RT (Route Target) attribute (the import and export value settings)
- the RD and RT configurations in this step are optional.
- This step involves VRF routing. Import and export configuration.
- the value of the VPN identifier is sent by the client.
- different RT identifiers are sent. Different VPNs can know each other through policies. Communication.
- the public network route and the label link are opened.
- the CE and the P device are configured as described above for the VPN implementation interface, routing, and label protocol.
- the configuration of VPN1 is sent to the corresponding device.
- the PE obtains the configuration of the VPN
- the local device generates a table ID of the corresponding VRF route to store the local and remote routes advertised by the VPN user.
- the network management system has the requirements of the upper-layer application, it is necessary to directly rewrite the routing entry information of the related VPN Table ID. Therefore, the mapping between the VPN identifier and the table ID needs to be fed back to the client through the PE.
- the client can learn the maintenance IDs of the entries of different VRFs on each PE, and directly read and write the contents of the entries with the same RT value.
- the content of the entry is as follows: key value, outbound interface, VPN ID, routing protocol type, priority, and metric.
- the IP addresses are IP1, IP2, and IP3, and only two terminals in the site 3 are accessed, and the IP addresses are IP5 and IP6, respectively.
- the entries of the learned CE1 route are: Table 1
- the key value of the entry is the user route of the local CE.
- the IP address of the remote device is sent to the IP address of the user.
- the outgoing interface is the interface directly connected to CE1.
- the entry is stored on PE1.
- the table ID is 2, and the VRF routing protocol is EBGP.
- the value of the RT inbound and outbound directions set by the VPN is 100: 1.
- PE1 will send the Table ID to 2
- the RT import export value of 100 is the same as the specific item information of the entry to the client through the local agent module.
- the entries of the CE3 side route learned on PE3 are as follows:
- the key value of the entry is the user route on the local CE side, and the outbound interface indicates the interface directly connected to CE3.
- the table ID of the entry is 3, and the VRF routing protocol is OSPF.
- the value of the RT inbound and outbound directions of the VPN is 100: 1.
- PE3 will send the Table ID to 3
- the RT import export value will be 100:1.
- the specific entry information of the entry is sent to the client through the local agent module.
- the network management system collects all the routes of the VPN1 through the client and adds them to the VPN forwarding plane identifier.
- the outgoing interface is replaced with the unique identifier of the PE connected to the route.
- the loopback address of the PE is preferred.
- the network management system advertises the user routing information of the remote PE to the PEs through the client, and the notification part of the content of the entry.
- the advertised routing protocol type of the client is BGP
- the IBGP is preferred.
- the level is modified accordingly.
- the type of the routing protocol here can also be of the I2RS type.
- the corresponding priority may be 10. The smaller the value of the priority, the better.
- the outgoing interface can be the router-id of the remote PE that is connected locally, or the tunnel that is specified by the client to the remote PE.
- the tunnel can be directly connected to the remote PE.
- the tunnel can pass the specified tunnel ID. Said.
- the client writes the learned PE3 route to the table with the Table ID of PE1: Table 4
- the tunnel 100 indicates that the client knows that the PE3 to the PE1 can be directly transmitted through the tunnel 100.
- the tunnel can be a gre tunnel or an lsp te tunnel. Of course, it can be an lsp.
- the routing information of the PEs is configured in the centralized configuration, the routing information of each PE can be sent through the I2RS client.
- the PEs do not need to synchronize information through BGP.
- the client delivers the corresponding PEs to the same VPN user according to the RT attribute, thus reducing the protocol packet processing on the PE.
- the entry can be directly read and written by the client.
- ACL access control list
- Embodiment 3 On the basis of Embodiment 1, the client proposes a policy application process with traffic filtering and time period requirements. As shown in FIG. 6, on the basis of the description of Embodiment 1, when the user proposes a VPN service provisioning request with a traffic filtering request. Time. Specifically, users of VPN1 require some clients between different sites to provide direct access, and some clients cannot access them across sites.
- the IP addresses are IP1, IP2, and IP3, and only two terminals in Site 3 are connected.
- the IP addresses are IP5 and IP6, respectively.
- IP1 and IP2 are required to communicate with IP5.
- IP3 and IP6 can only communicate with members in the same site.
- the client sends the relevant VPN entry, so that IP1 and IP2 in the site 1 send and drop entries on the PE3, so that only the PE3 can learn.
- the address prefixes of IP1 and IP2 from the PE1 in the same VPN are forwarded.
- the IP5 in the site 3 sends an entry to the PE1.
- the IP5 prefix on the remote PE3 is learned only on PE1.
- the function does not need to configure related ACL entries on each PE and the configuration of the BGP protocol process to invoke the policy.
- the entries that can be formed according to the application are as follows: Table 6
- IP3 and IP6 cannot be advertised.
- the remote user entry of the corresponding PE1 contains only IP5, as follows:
- the upper-layer client can deliver the corresponding entry or delete the entry according to the timer on the client. You can also carry the time parameter in the entry or corresponding configuration.
- the traffic filtering request described in the first paragraph of the second example is accompanied by a time requirement, that is, partial client cross-site access is only available during working hours, and non-normal working hours are not allowed to communicate with each other. Therefore, to implement the policy with the valid time period, the client can send the corresponding remote end entry information to the local device during the working hours, or carry the valid timestamp identifier in the entry, or can carry the valid time identifier through configuration. to realise. Relative to the collation of the contents of the table, here is the addition and deletion of the entry of the table item in the figure, and the time content in the item can be selected as part of the content implementation. Table 9
- Embodiment 4 On the basis of Embodiment 1, the client proposes a dual-homing access request, and the L3 VPN protection function is required to be implemented. As shown in FIG. 7, on the basis of the description of Embodiment 1, when the VPN1 user proposes the terminal under the site 1 The service is more important. When a VPN service provisioning application with a dual-homing request is required, the application is applied to the network management system. The network management system provides site 1 with two nearby PEs according to the network topology. The corresponding configuration is delivered, and the specific entry management is managed by the I2RS Client.
- the destination address prefix PE3 is used to establish the MPBGP loopback address of the peer PE.
- the optimal next hop is to reach the CE3 connected to the remote PE3 through the IF2 directly connected to the P1.
- the next hop of the CE3 connected to the remote PE3 is sent to the PE4.
- the route that is hopped to P1 is marked with the primary identity, and the next hop is the secondary identity of PE4.
- the optimal path is invalid, the traffic forwarded by PE1 can reach the remote CE3 through PE4 through the sub-optimal route.
- the return traffic PE3 can be returned through PE1 and PE4. Due to the original default implementation, such as CE1 dual access
- PE1, PE4, and PE3 learn the same VPNV4 routing information from PE1 and PE4, they will enter accordingly. If the route is forwarded, the FRR is guaranteed to be returned. Perceptual failure, calculation of new routes, inevitably will result in packet loss. In this case, if you want to implement the protection request for the return traffic, the client needs to send the two publishers on the CE1 that advertise the same prefix IP1 to PE3, one for PE1 and one for PE4. The routes advertised by the publishers are all written in the routing entries.
- the VPN FRR function is enabled to enable the return traffic to be quickly switched through the protection mode. When the forwarding table is delivered, the two different next hops are used.
- Embodiment 5 On the basis of Embodiment 1, the client proposes a dual-homing access request, and the VPN load sharing function is required to be implemented. As shown in FIG. 7, on the basis of the description of Embodiment 1, when the VPN1 user proposes the terminal under the site 1 The service is more important. When a VPN service provisioning application with a dual-homing request is required, the application is applied to the network management system. The network management system provides site 1 with two nearby PEs according to the network topology. The corresponding configuration is delivered, and the specific entry management is managed by the I2RS Client. As shown in Table 11, because there are many terminals under the site 1, the service is busy and the priority is high, then two nearby PEs are provided, and PE1 and PE4 provide dual-homing access.
- PE3 For the remote PE3 site, It can be connected to CE1 through PE1 and PE4 at the same time. Therefore, when PE3 has a VPN load balancing application, PE3 can forward traffic to CE1 through PE1 and PE4.
- the original default implementation mode for example, when CE1 is dual-homed to PE1 and PE4, and PE3 learns the same VPNV4 routing information from PE1 and PE4, the route priority comparison is performed accordingly, and only the optimal route is selected.
- the forwarding table is sent, which results in the failure to provide the load sharing guarantee for the return traffic.
- the PE3 senses the failure and calculates a new route. Generate a packet loss.
- the client needs to send the two publishers on the CE1 that advertise the same prefix IP1 to PE3, one for PE1 and one for PE4.
- the routes advertised by the two publishers are all written in the routing table.
- the load balancing function is enabled.
- the forwarding table is delivered, the two different next hops are used to search for different public network labels.
- the return traffic can be up to CE1 on both links, so that when there is more than one link bandwidth traffic, no packet loss occurs.
- the implementation adds a load sharing identifier to the basic information of the content of the entry. Table 14
- Embodiment 6 L2 VPN automatic control and related entries are delivered. Compared with the implementation of the L3 VPN in the first embodiment, the difference between the L2 VPN implementation is as follows: The user does not need to perceive the configuration of the carrier network and directly access the Layer 2 access.
- the approximate existing L2 VPN configuration includes:
- the user of the VPN1 proposes to the network management system to open the interworking of the sites 1 and 3 through the VPN through the application layer, and the network management system passes the topology. Collect and know that the PEs connected to Sites 1 and 3 are PE1 and PE3. Then, the NMS returns the interface configuration related to PE1 and PE3. At the same time, the corresponding VPN1 is delivered to PE1 and PE3 through the configuration module.
- the related configuration includes the binding of the AC-side interface and the establishment of the original pseudo-line.
- the internal label distribution involved in the establishment of the pseudo-line can be uniformly delivered by the client.
- the outer label can be uniformly delivered.
- each PE After obtaining the VPN-related configuration, each PE generates a Table ID of the corresponding VPN MAC to store the MAC addresses advertised by the VPN user. Because the I2RS client needs to directly rewrite the MAC entry information in the related table ID, the mapping between the VPN ID and the table ID needs to be fed back to the client through the PE. The client can learn the IDs of the different VPN entries on each PE and directly read and write the contents of the same VPN ID.
- the content of the entry is as follows: the destination MAC address, the peer PE ID, the private network label, the public network label, and the local outbound interface. Specifically, as shown in FIG.
- the learned MAC entries on the CE1 side are: Table 15
- FIG. 8 is a flowchart of a method for implementing automatic control of a VPN network according to a preferred embodiment of the present invention. As shown in FIG.
- Step S802 The VPN application sends a VPN service request to the network management system (carrying the location and original configuration information of all client side border nodes CE of the VPN, policy request, etc.); Step S804, the network management system Determining a corresponding PE according to the received VPN service request information and the network topology information collected locally; Step S806, performing VPN configuration on the selected PE (including VPN instance configuration, interface ip and vrf binding configuration, and client access)
- the side vrf is connected to the routing protocol configuration, the public network label routing configuration, and the BGP VPN configuration.
- step S808 the flow is divided into two processes, one directly proceeds to step S808, and ends; the other proceeds to step S810, and continues; step S808, configuration
- the module returns the related configuration of the PE access side to the application.
- step S810 the PE forms a local forwarding table of the VPN.
- the entry ID and the RT in the VPN are mapped locally. After the PE and the CE are successfully connected, the local learning can be learned.
- step S812 the PE sends the route, the RT, and the entry ID in the VPN forwarding table to the I2RS client;
- Step S816 According to the policy request, the forwarding device interaction module sends a VPN-related route sent by other PEs in the same VPN to the table on the PE.
- the foregoing embodiments can be used to implement the following beneficial effects: According to the topology information resources that can be obtained by the I2RS client, the automation effect can be more conveniently provided and the policy control can be implemented more timely than the manual configuration related implementation.
- each PE device can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
- they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明提供了一种边缘设备的VPN实现处理方法及装置,其中,该方法包括:获取VPN应用请求,其中,上述VPN应用请求中携带有VPN的属性配置信息;接收来自VPN下的各个边缘设备的VPN路由信息;向边缘设备发送VPN路由控制信息,其中,VPN路由控制信息为通过对属性配置信息和VPN路由信息进行集中计算处理得到的路由信息。采用本发明提供的上述方案,解决了相关技术中,VPN自动控制方案存在配置及表项内容较为复杂等技术问题,从而可以在统一控制平台下自动控制更简单的配置下发,更集中的表项管理和表项下发,减少了现有设备的配置及表项容量。
Description
边缘设备的 VPN实现处理方法及装置 技术领域 本发明涉及通信领域, 具体而言, 具体涉及一种边缘设备的虚拟私有网 (Virtual Private Network, 简称为 VPN) 实现处理方法及装置。 背景技术 现在 IETF标准组织新成立的一个路由系统接口 (Interface to the Routing System, 简称为 I2RS)工作组, 致力于研究一种面向路由系统的接口, 目的是为了给现有路由 系统一个兼容的、 对路由器的策略配置和路由信息库的路由信息表 (Routing Information Base, 简称为 RIB)等可进行直接读写的接口。现有相关 I2RS的个人草案 中描述的大致 I2RS模型如图 1,其中下半图的虚线框内表示一个路由器内部实现元件。 其中 I2RS 代理(Agent)是为了支持 I2RS在路由器上新增的一个元件, 以便 I2RS 客 户端 (Client) 可以通过 I2RS Agent获取路由器的配置管理、 拓扑路由等相关信息, 同时也要支持 I2RS Client通过 I2RS Agent给路由器下发配置、 路由条目指定等信息。 该工作组跟现在软件定义网络 (Software Defined Network, 简称为 SDN) 相关实现的 标准组织开放网络组织 (Open Network Foundation, 简称为 0 F) 的一个最大不同在 于, I2RS不是直接下发数据面的转发信息库(Forwarding Information Base,简称为 FIB) 中的转发表, 而是通过影响协议路由表的信息影响最终的转发表, 如此能更好的跟现 有的路由器实现兼容。
VPN 是用于物理网络中的逻辑网络隔离技术, 当前路由器的多协议标签交换 (Multi-Protocol Label Switching, 简称为 MPLS) VPN的实现一般通过提供商向客户 提供二层 VPN业务或三层 VPN业务来实现, 这些业务一般通过 MPLS及边界网关协 议 (Border Gateway Protocol, 简称为 BGP) 来实现, 具体包括: 运营商向客户提供 VPN业务相关的属性信息,客户可以自己根据这些信息来进行用户边缘设备 (Customer Edge, 简称为 CE) 配置或通过向运营商授权托管来由运营商代其在 CE上进行配置, 而运营商则负责打通为该客户提供的 VPN业务所需的运营商网络的连通性,包括提供 商(又称为运营商)边缘(Provider Edge,简称为 PE)设备及网络内部提供商(Provider, 简称为 P)设备上的 VPN相关连接及配置。 由于手动配置存在其配置不灵活、 延时大 的特性, 想要通过自动配置方式来实现。 当前的自动配置实现也是在现有配置的基础 上通过后台远程下发的方式来实现。 并且想要在现有路由器上实现 PE表项条目的减 少或策略功能, 需要在 BGP网络中提供集中的路由反射器 (Router Reflector, 简称为
RR) 功能, 然后继续在反射器上进行复杂的策略配置来实现。 而想要实现 VPN的保 护功能, 则要在本地和远端都启用相应的保护功能, 才能实现双向保护。 针对相关技术中的上述问题, 目前尚未提出有效的解决方案。 发明内容 针对相关技术中, VPN自动控制方案存在配置及表项内容较为复杂等技术问题, 本发明实施例提供了一种边缘设备的 VPN 实现处理方法及装置, 以至少解决上述问 题。 根据本发明的一个实施例, 提供了一种边缘设备的 VPN实现处理方法, 包括: 获取 VPN应用请求, 其中, 上述 VPN应用请求中携带有 VPN的属性配置信息; 接收 来自 VPN下的各个边缘设备的 VPN路由信息; 向边缘设备发送 VPN路由控制信息, 其中, VPN路由控制信息为通过对属性配置信息和 VPN路由信息进行集中计算处理 得到的路由信息。 上述 VPN路由信息或路由控制信息包括以下至少之一: VPN Table ID、表项条目, 其中, VPN Table ID用于在本地标识 VPN路由信息生成的表项号。 上述表项条目包括以下至少之一: 表项关键值、下一跳、 出接口、协议类型、 VPN 标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间。 上述 VPN路由信息中的表项条目和路由控制信息中的表项条目部分相同或完全 不同。 上述表项关键值包括: 数据报文的目的地址。 上述下一跳为边缘设备的直连下一跳标识或多跳邻居的对等体标识。 上述出接口在边缘设备发送给网络管理系统时为边缘设备的本地 VPN 绑定接口 或本地设备标识, 在网络管理系统给边缘设备发送时为远端边缘设备的映射标识。 上述映射标识包括以下至少之一: 远端边缘设备的标识; 边缘设备到远端边缘设 备的逻辑出接口标识或物理出接口标识。 上述协议类型用于标识路由系统接口 I2RS协议和 /或除 I2RS协议之外的其它路由 协议。
上述 VPN转发面标识用于对进行封装或解封装后的数据面报文进行标识。 上述主备用标识用于对同一表项关键值携带的多个下一跳分别标识为主用和备 用。 上述 VPN标识为在控制面与 VPN——对应。 上述负荷分担标识用于对同一表项关键值携带的多个下一跳进行标识。 上述生效时间通过以下至少之一方式实现: 根据边缘设备配置或默认的存活时间 生效计时; 根据网络管理系统下发的生效时间段在边缘设备上同步生效; 通过在在网 络管理系统上根据本地生效时间进行路由信息的生效发送或撤销发送。 上述属性配置信息包括以下至少之一: VPN标识、 路由目标(Route Target, 简称 为 RT) 值设置信息、 需要开通 VPN的 PE站点标识信息、 需要启用的路由协议类型 信息、 优先级配置信息、 策略信息。 上述策略信息包括以下至少之一: 基于表项条目内容的过滤或更改策略、 时间预 置策略、 主备用策略、 负荷分担策略。 上述边缘设备包括以下之一: 提供商边缘 PE设备、 用户边缘 CE设备。 根据本发明的另一个实施例, 提供了一种边缘设备的 VPN实现处理方法, 包括: 向网络管理系统发送 VPN路由信息; 接收来自网络管理系统的 VPN路由控制信息, 其中, VPN路由控制信为通过对 VPN路由信息和网络管理系统从 VPN应用请求中获 取的 VPN的属性配置信息进行集中计算处理得到的 VPN路由信息;根据 VPN路由控 制信息对边缘设备进行配置。 上述 VPN路由信息或路由控制信息包括以下至少之一:
VPN列表标识(Table ID)、表项条目, 其中, VPN Table ID用于在本地标识 VPN 路由信息生成的表项号。 上述表项条目包括以下至少之一: 表项关键值、下一跳、 出接口、协议类型、 VPN 标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间; 其中, 表项关键值包括: 数据报文的目的地址; 和 /或下一跳为边缘设备的直连下 一跳标识或多跳邻居的对等体标识; 和 /或出接口在边缘设备发送给网络管理系统时为 边缘设备的本地 VPN绑定接口或本地设备标识,在网络管理系统给边缘设备发送时为
远端边缘设备的映射标识; 和 /或协议类型用于标识路由系统接口 I2RS 协议和 /或除 I2RS之外的其它路由协议; 和 /或 VPN转发面标识用于对进行封装或解封装后的数据 面报文进行标识; 和 /或主备用标识用于对同一表项关键值携带的多个下一跳分别标识 为主用和备用;和 /或 VPN标识为在控制面与 VPN—一对应;和 /或负荷分担标识用于 对同一表项关键值携带的多个下一跳进行标识。 上述 VPN路由信息中的表项条目和路由控制信息中的表项条目部分相同或完全 不同。 上述映射标识包括以下至少之一: 远端边缘设备的标识; 边缘设备到远端边缘设 备的逻辑出接口标识或物理出接口标识。 上述生效时间通过以下至少之一方式实现: 根据边缘设备配置或默认的存活时间 生效计时; 根据网络管理系统下发的生效时间段在边缘设备上同步生效; 通过在在网 络管理系统上根据本地生效时间进行路由信息的生效发送或撤销发送。 上述属性配置信息包括以下至少之一: VPN标识、 RT值设置信息、需要开通 VPN 的边缘设备站点标识信息、 需要启用的路由协议类型信息、 优先级配置信息、 策略信 息。 上述策略信息包括以下至少之一: 基于表项条目内容的过滤或更改策略、 时间预 置策略、 主备用策略、 负荷分担策略。 根据本发明的又一个实施例,提供了一种边缘设备的 VPN实现处理装置包括: 获 取模块, 设置为获取 VPN应用请求, 其中, VPN应用请求中携带有 VPN的属性配置 信息; 接收模块, 设置为接收来自 VPN下的各个边缘设备的 VPN路由信息; 发送模 块, 设置为向边缘设备发送 VPN路由控制信息, 其中, VPN路由控制信息为通过对 属性配置信息和 VPN路由信息进行集中计算处理得到的路由信息。 上述接收模块和发送模块, 分别设置为在 VPN路由信息和 /或 VPN路由控制信息 包括以下至少之一时接收 VPN路由信息和发送 VPN路由控制信息: VPN列表标识 Table ID、 表项条目, 其中, VPN Table ID用于在本地标识 VPN用户信息生成的表项 号。 上述接收模块和发送模块分别用于在表项条目包括以下至少之一时,接收 VPN路 由信息和发送 VPN路由控制信息: 表项关键值、 下一跳、 出接口、 协议类型、 VPN 标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间;
其中, 表项关键值包括: 数据报文的目的地址; 和 /或下一跳为边缘设备的直连下 一跳标识或多跳邻居的对等体标识; 和 /或出接口在边缘设备发送给网络管理系统时为 边缘设备的本地 VPN绑定接口或本地设备标识,在网络管理系统给边缘设备发送时为 远端边缘设备的映射标识; 和 /或协议类型用于标识路由系统接口 I2RS 协议和 /或除 I2RS之外的其它路由协议; 和 /或 VPN转发面标识用于对进行封装或解封装后的数据 面报文进行标识; 和 /或主备用标识用于对同一表项关键值携带的多个下一跳分别标识 为主用和备用;和 /或 VPN标识为在控制面与 VPN—一对应;和 /或负荷分担标识用于 对同一表项关键值携带的多个下一跳进行标识。 根据本发明的再一个实施例, 提供了一种边缘设备的 VPN实现处理装置, 包括: 发送模块, 设置为向网络管理系统发送 VPN路由信息; 接收模块, 设置为接收来自网 络管理系统的 VPN路由控制信息, 其中, VPN路由控制信为通过对 VPN路由信息和 网络管理系统从 VPN应用请求中获取的 VPN的属性配置信息进行集中计算处理得到 的路由信息; 配置模块, 设置为根据 VPN路由控制信息对边缘设备进行配置。 上述接收模块和发送模块分别设置为在 VPN路由控制信息和 /或 VPN路由信息包 括以下至少之一时,接收 VPN路由控制信息和发送 VPN路由信息: VPN列表标识 Table ID、 表项条目, 其中, VPN Table ID用于在本地标识 VPN路由信息生成的表项号。 上述接收模块和发送模块分别设置为在表项条目包括以下至少之一时, 接收 VPN 路由控制信息和发送 VPN路由信息: 表项关键值、 下一跳、 出接口、 协议类型、 VPN 标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间; 其中, 表项关键值包括: 数据报文的目的地址; 和 /或下一跳为边缘设备的直连下 一跳标识或多跳邻居的对等体标识; 和 /或出接口在边缘设备发送给网络管理系统时为 边缘设备的本地 VPN绑定接口或本地设备标识,在网络管理系统给边缘设备发送时为 远端边缘设备的映射标识; 和 /或协议类型用于标识路由系统接口 I2RS 协议和 /或除 I2RS之外的其它路由协议; 和 /或 VPN转发面标识用于对进行封装或解封装后的数据 面报文进行标识; 和 /或主备用标识用于对同一表项关键值携带的多个下一跳分别标识 为主用和备用;和 /或 VPN标识为在控制面与 VPN—一对应;和 /或负荷分担标识用于 对同一表项关键值携带的多个下一跳进行标识。 通过本发明实施例, 采用对 VPN应用请求和边缘设备的 VPN路由信息进行的集 中计算处理,将得到的配置及路由控制信息进行下发的技术手段,解决了相关技术中, VPN自动控制方案存在配置及表项内容较为复杂等技术问题, 从而可以在统一控制平
台下自动控制更简单的配置下发, 更集中的表项管理和表项下发, 减少了现有设备的 配置及表项容量。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中: 图 1为根据相关技术的 I2RS模型示意图; 图 2为根据本发明实施例的边缘设备的 VPN实现处理方法的流程图; 图 3为根据本发明实施例的边缘设备的 VPN实现处理装置的结构框图; 图 4为根据本发明实施例的边缘设备的 VPN实现处理方法的另一流程图; 图 5为根据本发明实施例的边缘设备的 VPN实现处理装置的另一结构框图; 图 6为根据本发明优选实施例的 I2RS网络的拓扑示意图; 图 7为根据本发明优选实施例的 I2RS网络的另一拓扑示意图; 以及 图 8为根据本发明优选实施例的 VPN网络自动控制实现的方法流程图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 图 2为根据本发明实施例的边缘设备的 VPN实现处理方法的流程图。本实施例中 的方法可以但不限于应用于网络管理系统 (又称为网管系统, Network Management System, 简称为 NMS), 如图 2所示, 该方法包括: 步骤 S202, 获取 VPN应用请求, 其中, 该 VPN应用请求中携带有 VPN的属性 配置信息。在具体实施时, 获取 VPN应用请求的方式有多种, 例如可以通过接收来自 VPN侧设备的上述 VPN应用请求实现, 还可以通过接收来自上层业务的上述 VPN应 用请求实现;
步骤 S204, 接收来自 VPN下的各个边缘设备的 VPN路由信息; 此处路由信息一 般包括但不限于来自于本地 CE侧设备的路由, 具体路由信息包括前缀、 掩码、 下一 跳、 出接口、 路由协议类型、 优先级、 度量值、 主用备用标识、 负荷分担标识。 步骤 S206, 向边缘设备发送 VPN路由控制信息, 其中, 该 VPN路由控制信息为 通过对上述属性配置信息和上述 VPN路由信息进行集中计算处理得到的路由信息。 需要说明的是, 上述步骤 S202和步骤 S204之间的执行顺序并不限于此, 例如可 以先执行步骤 S204, 再执行步骤 S202。 通过上述各个处理步骤, 由于对 VPN应用请求和边缘设备的 VPN用户信息进行 了集中计算处理, 即统一控制, 因此, 可以在统一控制平台下自动控制更简单的配置 下发, 更集中的表项管理和表项下发, 减少了现有设备的配置及表项容量。 在本实施例中, 在接收来自边缘设备的 VPN用户信息(主要表现为路由信息)之 前,还可以根据 VPN应用请求和本地网络拓扑信息确定上述边缘设备。根据上述 VPN 应用请求和本地网络拓扑信息确定上述边缘设备之后, 根据上述指定信息及网管系统 已收集的拓扑信息, 生成 VPN配置信息; 向上述边缘设备下发 VPN配置信息, 其中, 上述边缘设备根据上述 VPN配置信息生成上述 VPN用户信息。 在本实施例中, VPN用户信息包括以下至少之一: VPN Table ID、 表项条目, 其 中, VPN Table ID用于在本地标识 VPN用户信息生成的表项号, 以便 I2RS Client直 接读写所述 VPN相关表项。 上述表项条目包括以下至少之一: 表项关键值、下一跳、 出接口、协议类型、 VPN 标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间。 通过上述实施例可以看出, VPN路由控制信息为网管系统经由策略计算处理的 VPN路由信息, 可以表现为两者表项条目的变化。 即上述 VPN路由信息中的表项条 目和上述路由控制信息中的表项条目部分相同或完全不同。 上述表项关键值包括: 数据报文的目的地址。 具体在 L2VPN 中表现为媒体接入 控制 (Media Access Control, 简称为 MAC)地址, 在 L3 VPN中表现为 IP地址, 当然 也不局限于目的地址, 还可以是根据需要由数据报文中解析出来的有效字段, 如源地 址, 端口号等亦可支持。
上述下一跳为边缘设备的直连下一跳标识或多跳邻居的对等体标识。 对等体标识 具体表现为和边缘设备建立邻居的发布该表项关键值的远端边缘设备的标识, 一般为 标识远端边缘设备的 loopback的 IP地址, 或建链接口的 IP地址。 上述出接口在边缘设备发送给上述网络管理系统时为上述边缘设备的本地 VPN 绑定接口或本地设备标识, 在网络管理系统给边缘设备发送时为远端边缘设备的映射 标识。 上述映射标识包括以下至少之一: 远端边缘设备的标识; 边缘设备到远端边缘 设备的逻辑出接口标识或物理出接口标识。 具体地, 上述映射标识可以表现为本地隧 道标识 (ID), 该本地隧道 ID表明本地到远端边缘设备的端到端连接, 可以为通用路 由封装(Generic Routing Encapsulation,简称为 GRE)隧道 ID、资源预留协议(Resource Reserve Protocol, 简称为 RSVP)流量工程(Traffic Engineering, 简称为 TE)隧道 ID、 标签交换路径 (Label Switched Paths, 简称为 LSP) 隧道 ID。 上述协议类型用于标识 I2RS协议和 /或除该 I2RS协议之外的其它路由协议。上述 VPN转发面标识用于对进行封装或解封装后的数据面报文进行标识。 上述主备用标识用于对同一表项关键值携带的多个下一跳分别标识为主用和备 用, 以便多个下一跳分别携带主用备用标识下发。
VPN标识为在控制面与 VPN——对应, 即 VPN标识用以在控制面全局唯一标识 一个 VPN, 其包括但不限于用 RT方式来实现。 负荷分担标识用于对同一表项关键值携带的多个下一跳进行标识, 以便同一表项 关键值的多个下一跳能同时生效。 上述生效时间通过以下至少之一方式实现: 根据边缘设备配置或默认的存活时间生效计时, 即以表项下发的存活时间生效记 时, 例如: 利用 PE设备自带的计时器, 在表项生成后 (如以保存时间倒数 300s) 计 时, 当为 0时还没有接收更新时, 则认为表项老化。 根据网管系统下发的生效时间段在边缘设备上同步生效表示。 网管系统下发的时 间段, 其中, 在该时间段内 (例如 8:00-8:30) 内表项生效, 则在边缘设备同步的有效 时间内将该条目放入 RIB表。 通过在在网络管理系统上根据本地生效时间进行路由信息的生效发送或撤销发 送, 其中, 在网络管理系统的生效时间结束时, 网络管理系统的 I2RS Client下发撤销
指定表项的信息,即计时管理在 I2RS Client上维护,只需要时间生效的时候下发条目, 不生效的时候撤销条目。 在本实施例中, 上述应用请求包括上层业务和 /或策略的开通请求: VPN业务、流 量匹配过滤、 负荷分担、 时间值等策略请求。 上述属性配置信息包括以下至少之一: VPN标识、 路由目标 (RT) 值设置信息、 需要开通 VPN的 PE站点标识信息、需要启用的路由协议类型信息、优先级配置信息、 策略信息。 其中, 该策略信息包括以下至少之一: 基于表项条目内容的过滤或更改策 略、 时间预置策略、 主备用策略、 负荷分担策略。 上述转发设备包括以下之一: PE设备、 CE设备。 上述 VPN用户信息包括以下至少之一: VPN标识信息,路由目标 RT值设置信息,
VPN客户端侧 CE的位置信息、 CE接入的配置信息、 策略请求。 图 3为根据本发明实施例的边缘设备的 VPN实现处理装置的结构框图。该装置可 以但不限于应用于网络管理系统, 如图 3所示, 包括: 获取模块 30, 连接至发送模块 34, 设置为获取 VPN应用请求, 其中, 该 VPN应 用请求中携带有 VPN的属性配置信息; 接收模块 32, 连接至发送模块 34, 设置为接收来自上述 VPN下的各个边缘设备 的 VPN路由信息; 发送模块 34, 设置为向上述边缘设备发送 VPN路由控制信息, 其中, 该 VPN路 由控制信息为通过对上述属性配置信息和上述 VPN路由信息进行集中计算处理得到 的路由信息; 通过上述各个模块所实现的功能, 同样可以在统一控制平台下自动控制更简单的 配置下发, 更集中的表项管理和表项下发, 减少了现有设备的配置及表项容量。 优选地, 上述接收模块 32和上述发送模块 34, 分别设置为在上述 VPN路由信息 和 /或上述 VPN路由控制信息包括以下至少之一时接收上述 VPN路由信息和发送上述 VPN路由控制信息: VPN列表标识 Table ID、表项条目, 其中, 该 VPN Table ID用于 在本地标识所述 VPN用户信息生成的表项号。 所述接收模块和所述发送模块分别设置为在所述表项条目包括以下至少之一时, 接收所述 VPN路由信息和发送所述 VPN路由控制信息:
表项关键值、 下一跳、 出接口、 协议类型、 VPN标识、 VPN转发面标识、 主备用 标识、 负荷分担标识、 生效时间; 其中, 所述表项关键值包括: 数据报文的目的地址; 和 /或所述下一跳为边缘设备 的直连下一跳标识或多跳邻居的对等体标识; 和 /或所述出接口在边缘设备发送给所述 网络管理系统时为所述边缘设备的本地 VPN绑定接口或本地设备标识,在网络管理系 统给边缘设备发送时为远端边缘设备的映射标识; 和 /或所述协议类型用于标识路由系 统接口 I2RS协议和 /或除所述 I2RS之外的其它路由协议; 和 /或所述 VPN转发面标识 用于对进行封装或解封装后的数据面报文进行标识; 和 /或所述主备用标识用于对同一 表项关键值携带的多个下一跳分别标识为主用和备用; 和 /或所述 VPN标识为在控制 面与 VPN—一对应; 和 /或所述负荷分担标识用于对同一表项关键值携带的多个下一 跳进行标识。 需要说明的是, 上述各个模块是可以通过相应的处理器实现的, 例如可以分别对 应一个处理器实现, 当然也可以部分或全部集成于一个处理器实现, 但不限于上述组 合。 在本实施例中提供一种边缘设备的虚拟私有网 VPN实现处理方法, 如图 4所示, 该方法包括: 步骤 S402, 向网络管理系统发送 VPN路由信息; 步骤 S404, 接收来自网络管理系统的 VPN路由控制信息, 其中, VPN路由控制 信为通过对 VPN路由信息和网络管理系统从 VPN应用请求中获取的 VPN的属性配置 信息进行集中计算处理得到的 VPN路由信息; 步骤 S406, 根据 VPN路由控制信息对边缘设备进行配置。 上述 VPN路由信息或路由控制信息包括以下至少之一: VPN列表标识 Table ID、 表项条目, 其中, VPN Table ID用于在本地标识 VPN路由信息生成的表项号。 上述表项条目包括以下至少之一: 表项关键值、下一跳、 出接口、协议类型、 VPN 标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间; 其中, 表项关键值 包括: 数据报文的目的地址; 和 /或下一跳为边缘设备的直连下一跳标识或多跳邻居的 对等体标识; 和 /或出接口在边缘设备发送给网络管理系统时为边缘设备的本地 VPN 绑定接口或本地设备标识, 在网络管理系统给边缘设备发送时为远端边缘设备的映射 标识;和 /或协议类型用于标识 I2RS协议和 /或除 I2RS之外的其它路由协议;和 /或 VPN
转发面标识用于对进行封装或解封装后的数据面报文进行标识; 和 /或主备用标识用于 对同一表项关键值携带的多个下一跳分别标识为主用和备用; 和 /或 VPN标识为在控 制面与 VPN—一对应; 和 /或负荷分担标识用于对同一表项关键值携带的多个下一跳 进行标识。 上述 VPN路由信息中的表项条目和路由控制信息中的表项条目部分相同或完全 不同。 上述映射标识包括以下至少之一: 远端边缘设备的标识; 边缘设备到远端边缘 设备的逻辑出接口标识或物理出接口标识。 上述生效时间通过以下至少之一方式实现: 根据边缘设备配置或默认的存活时间 生效计时; 根据网络管理系统下发的生效时间段在边缘设备上同步生效; 通过在在网 络管理系统上根据本地生效时间进行路由信息的生效发送或撤销发送。 上述属性配置信息包括以下至少之一: VPN标识、 路由目标 RT值设置信息、 需 要开通 VPN的边缘设备站点标识信息、需要启用的路由协议类型信息、优先级配置信 息、 策略信息。 上述策略信息包括以下至少之一: 基于表项条目内容的过滤或更改策略、 时间预 置策略、 主备用策略、 负荷分担策略。 为实现上述方法, 本实施例还提供一种边缘设备的 VPN 实现处理装置, 如图 5 所示, 该装置包括: 发送模块 50, 连接至接收模块 52, 设置为向网络管理系统发送 VPN路由信息; 接收模块 52, 连接至配置模块 54, 设置为接收来自网络管理系统的 VPN路由控 制信息, 其中, 所述 VPN路由控制信为通过对所述 VPN路由信息和所述网络管理系 统从 VPN应用请求中获取的 VPN的属性配置信息进行集中计算处理得到的路由信息; 配置模块 54, 设置为根据所述 VPN路由控制信息对所述边缘设备进行配置。 在本实施例中, 发送模块 50和接收模块 52分别在上述 VPN路由信息和 /或路由 控制信息包括以下至少之一时发送上述 VPN路由信息和接收上述路由控制信息: VPN 列表标识 Table ID、表项条目, 其中, 该 VPN Table ID用于在本地标识所述 VPN路由 信息生成的表项号。 上述接收模块 52和所述发送模块 50分别设置为在所述表项条目包括以下至少之 一时, 接收所述 VPN路由信息和发送所述 VPN路由控制信息:
表项关键值、 下一跳、 出接口、 协议类型、 VPN标识、 VPN转发面标识、 主备用 标识、 负荷分担标识、 生效时间; 其中, 所述表项关键值包括: 数据报文的目的地址; 和 /或所述下一跳为边缘设备 的直连下一跳标识或多跳邻居的对等体标识; 和 /或所述出接口在边缘设备发送给所述 网络管理系统时为所述边缘设备的本地 VPN绑定接口或本地设备标识,在网络管理系 统给边缘设备发送时为远端边缘设备的映射标识; 和 /或所述协议类型用于标识路由系 统接口 I2RS协议和 /或除所述 I2RS之外的其它路由协议; 和 /或所述 VPN转发面标识 用于对进行封装或解封装后的数据面报文进行标识; 和 /或所述主备用标识用于对同一 表项关键值携带的多个下一跳分别标识为主用和备用; 和 /或所述 VPN标识为在控制 面与 VPN—一对应; 和 /或所述负荷分担标识用于对同一表项关键值携带的多个下一 跳进行标识。 为了更好地理解上述实施例, 以下结合优选实施例和相关附图详细说明。 实施例 1 一种 IP/MPLS网络通过网管系统进行 VPN业务动态建立和管理的方法, 网管系 统接收 VPN业务的应用请求,通过接口对运营商边缘转发设备业务的表项进行统一控 制, 包括: 网管系统接收运营商边缘设备发送来的 VPN路由信息后,将接收到的信息结合应 用请求进行集中计算处理, 生成计算处理后的信息下发给转发设备。 其中 VPN路由信息包括 VPN Table ID、表项条目,表项条目中的内容包括但不限 于:表项关键值、 下一跳、 出接口、 VPN标识、 VPN转发面标识、 协议类型、 主用备 用标识、 负荷分担标识、 生效时间等其中部分项或全部项内容。 上述网管系统包含转发设备信息交互模块、应用交互模块、计算模块和存储模块。 其中转发设备信息交互模块用以对转发设备进行信息收集或信息下发的交互, 可以为 I2RS Client模块。 上述转发设备包含网管系统交互模块, 可以为 I2RS Agent模块。 其中运营商边缘 转发设备可为 PE或 CE。 上述应用请求为上层业务及策略的开通请求, 包括 VPN业务、流量匹配过滤、 负 荷分担、 时间值等策略请求。
上述集中计算处理包括根据应用请求, 结合转发设备信息收集到的信息在计算及 存储模块进行集中的计算处理并本地存储。 上述 VPN转发面标识用于数据面报文的封装解封装, 包括但不限于以 label形式 表现。 上述协议类型用于标识路由系统接口 (I2RS) 协议和 /或除所述 I2RS协议之外的 其它路由协议, 如 bgp协议等。 上述主用备用标识主要用于同时下发最优次优路径标识, 用于形成保护。 负荷分担标识用于对同一表项关键值携带的多个下一跳进行标识, 以便同一表项 关键值的多个下一跳能同时生效, 以使多条路径形成负荷分担。 本实施例中,还提供一种用于 IP/MPLS网络的通信设备,包括网管系统交互模块。 网管系统交互模块通过向网管系统发送本地接收到的 VPN路由信息,并从网管系统接 收远端的 VPN路由信息, 建立 VPN用户连接。 其中 VPN路由信息由 VPN Table ID、 表项条目组成, 表项条目中的内容包括但不限于: 表项关键值、下一跳、 出接口、 VPN 标识、 VPN转发面标识、 主用备用标识、 负荷分担标识、 生效时间等其中部分项或全 部项内容。 该通信设备创建表项用以维护 VPN路由信息。 上述创建表项包括生成本地唯一的 VPN Table ID用以标识所述唯一 VPN标识表 项, 表项条目由上述表项内容中的部分内容或全部内容组成; 维护表项可以是本地实 时更新或由客户端 (Client) 来通过代理 (Agent) 控制。 本实施例还提供一种网管系统: 包含转发设备信息交互模块、 应用交互模块、 计 算模块和存储模块。 其中应用交互模块主要用于接收上层业务的应用请求, 转发设备 信息交互模块用以跟转发设备进行交互, 可以为 I2RS Client模块。 通过应用请求信息 和转发设备信息交互模块获取的信息进行集中计算, 生成计算结果信息设备过来的信 息通过集中计算, 生成新的信息下发转发设备。 其中新的信息主要由 Table ID、 表项 条目组成,表项条目中的内容包括但不限于:表项关键值、下一跳、出接口、 VPN标识、 VPN转发面标识、 主用备用标识、 负荷分担标识、 生效时间等其中部分项或全部项内 容。 实施例 2: L3 VPN自动控制及相关表项下发
如图 6所示, 站点 (site) 1和站点 3是同属于 VPN1的, 站点 2和站点 4是属于 同一个 VPN2的,在各 PE上做 VPN接入时,现有实现需要在各 PE上手动配置 VPN1 和 VPN2的信息, 配置完成后 VPM的路由和 VPN2的路由在各 PE上通过不同的表 项来维护, 携带各有相匹配属性的 RT导入导出到相应的 VPN转发表中, 以实现 VPN 的隔离。 这般隔离在 PE1、 PE2和 PE3上, 都会在 BGP携带的 VPN消息中将本地的 所有生效的虚拟路由 /转发情况(virtual Routing & Forwarding Instance, 简称为 VRF) 路由发布出去, 如 PE1上的 VPN1消息在 PE2上也会收到, 但该消息其实对于 PE2 来讲是完全无效且占用了带宽传输及协议报文过滤处理的时间的。 对比参考现有 CE1和 CE3打通 VPN1的连通性配置为例, 配置参考如下: 1. 在 CE1上配置 loopbackl和接口 IF1 的地址, 与 PE1建立外部边界网关协议
(External Border Gateway Protocol,简称为 EBGP)邻居, 并将 loopback在 BGP中通告。
2. 在 PE1上配置 vrf vpnl,将 IF1绑定在 vrf vpnl中并配置地址、配置 loopbackl、 接口 IF2的地址、 配置开放式最短路径优先(Open Shortest Path First, 简称为 OSPF), 通告 IF2 接口地址所在网段、 与 PE3 起多协议边界网关协议 (Multi-Protocol Border Gateway Protocol , 简称为 MPBGP)邻居、 与 CE1建立 EBGP邻居、 接口 IF2起标记 分发协议(Label Distribution Protocol,简称为 LDP),指定 loopbackl为 LDP的 router-id。 VPN相关配置包括: VRF实例配置中包括 ip vrfvpnl ,路由区分(Route Distinguisher, 简称为 RD) (用以唯一标识 VPN)、 RT (用以标识导入导出路由携带的标识); 接口 绑定 VRF (表示该接口和 CE侧相连, 该接口学习到的路由为私网路由)、 MPBGP邻 居建立(用以判断邻居起来后给本地私网路由分发标签,并用该建链邻居 ID来查找外 层标签。)
3.在 P上配置建链接口的地址;配置 OSPF,通告接口地址所在网段;接口起 LDP, 配置 loopbackl, 并指定 loopbackl为 LDP的 router-id。
4.在 PE3上配置 vrf vpnl、将 IF1绑定在 vrf vpnl中并配置地址、 配置 loopbackl、 IF2的地址、 配置 OSPF、 通告公网地址所在网段、 与 PE1起 MPBGP邻居、 与 CE3 建立 OSPF邻居、 接口 IF2起 LDP。
5.在 CE3上配置 loopbackl和接口的地址, 配置 OSPF, 通告接口地址所在网段和 loopback地址。 在 I2RS的框架中, 如图 6, 用户可以根据 I2RS模型中提供的应用层提出所述需 求,比如 VPN1的用户通过应用层给网管系统提出需要通过 VPN开通站点 1和 3的互
通, 网管系统通过拓扑收集, 知道站点 1和 3连接的 PE为 PE1和 PE3, 那么网管系 统返回 PE1和 PE3相关的接口及配置信息给用户 (当然也可以是应用层根据 CE侧的 配置同步给网管系统), 使其与直连的 CE侧形成互联互通。 同时通过配置模块给 PE1 和 PE3的下发相应 VPN1相关配置, 包括: 1、 VRF的启动: VRF实例的启用、实例下 RD、 RT (Route Target)属性(其 import、 export值设置) 的配置 (该步骤中的 RD、 RT配置为可选, 当路由条目的导入导出完 全由 I2RS Client集中控制时, 无需启用该步骤; 当需要跟现有路由器兼容时, 需要启 用该步骤。 该步骤涉及 VRF路由的导入导出配置, 当完全集中控制时, 需要由 Client 下发一个该 VPN标识的值, 当有不同 VPN之间需要通信时, 携带不同 RT标识发送, 不同 VPN之间通过策略知道相互之间可以通信。)
2、 VRF接口的绑定
3、 VRF接入路由协议配置
4、 BGP下的相关 VPN使能: 添加 VRF地址族, 建立 VPN邻居, 通过 BGP VPN 邻居导入导出 VRF路由 (该步骤为可选, 当导入导出完全由 I2RS Client集中控制时, 无需启用该步骤; 当需要跟现有路由器兼容时, 需要启用该步骤, 该步骤的启用涉及 到私网标签的分配, 当 VPN邻居建立成功, 开始给本地 CE侧路由分配私网标签, 当 完全集中控制时, 则由 Client来下发各路由的私网标签)
5、 公网路由和标签链路的打通 同时给 CE和 P设备进行如上描述相关 VPN实现接口、路由、标签协议所需配置。 同理 VPN2的用户通过应用提出需求后, 如 VPN1的配置下发给相应设备。 各 PE获取到 VPN相关配置时, 本地产生一个相应 VRF路由的 Table ID, 用以存 放该 VPN用户的本地及远端通告过来的路由。 由于网管系统有来自于上层应用的需求可能需要直接改写相关 VPN Table ID下的 路由条目信息, 故对于 VPN标识和 Table ID的映射关系, 需要通过 PE反馈给 Client。 Client由此可以学习到各 PE上不同 VRF的表项维护 ID, 并对具有相同 RT值的表项 内容进行直接读写。 表项内容覆盖如下图中的表项关键值、 出接口、 VPN标识、 路由 协议类型, 优先级, 度量值。 具体当如图 6描述: 站点 1内有 3个客户侧终端接入, 其 IP分别为 IP1、 IP2、 IP3, 站点 3内只有两个终端接入, 其 IP分别为 IP5、 IP6, 那 么 PE1上学习到的 CE1侧路由的表项有:
表 1
其中表项关键值表现为本地 CE侧的用户路由, 用于远端的数据报文发往用户的 目的地址 IP标识, 出接口表示 PE1跟 CE1直连的接口, 该表项存放在 PE1上的 Table ID为 2, 接入的 VRF路由协议为 EBGP, VPN设置的 RT进出方向值均为: 100: 1。 那 么 PE1将 Table ID为 2, RT的 import export值均为 100: 1的信息协同该表项的具体条 目信息通过本地 Agent模块发送给 Client。 同理, PE3上学习到的 CE3侧路由的表项有: 表 2
其中表项关键值表现为本地 CE侧的用户路由, 出接口表示 PE3跟 CE3直连的接 口。 该表项存放在 PE3上的 Table ID为 3, 接入的 VRF路由协议为 OSPF, VPN设置 的 RT进出方向值均为: 100: 1。 同样, PE3将 Table ID为 3, RT的 import export值均 为 100: 1的信息协同该表项的具体条目信息通过本地 Agent模块发送给 Client。 网管系统通过 Client汇总该 VPN1下的所有路由并给它们打上 VPN转发面标识, 出接口替换为该路由所接入 PE的唯一标识, 最好用 PE的 loopback地址: 表 3
3 IP5 PE3 ospf 110 10 100
export: 100: 1
import: 100: 1
3 IP6 PE3 ospf 110 10 101
export: 100: 1 汇总之后网管系统通过 Client向各 PE通告远端 PE侧的用户路由信息,表项内容 的通告部分, 若 Client通告路由协议类型通过 BGP实现方式来的, 则表现为 IBGP, 优先级相应修改,此处的路由协议类型也可以是 I2RS类型的,可能相应优先级可以为 10, 优先级的值越小越优。 同时出接口可以是本地连接的远端 PE的 router-id标识, 也可以是由 Client经过查找后指定到远端 PE的隧道,表明通过该隧道可直达对端 PE, 隧道可以通过指定的 Tunnel ID表示。 根据相同的 RT值, Client将学习到的 PE3侧的 路由写入 PE1的 Table ID为 2的表项中: 表 4
同理, 也会把相关表项内容下发给 PE3的 Table 3, 里面具体内容为将本地的两条 路由携带 Client给它分配的标签下发, 远端 PE1侧过来的路由条目: 表 5
此处 Tunnel 100表示 Client经过查找知道由 PE3到 PE1可以通过 Tunnel 100直达, 该 Tunnel可以是一个 gre的 tunnel, 也可以是一个 lsp te的 tunnel, 当然更可以是一条 lsp。 在该集中配置并表项统一管理情况下, 进一步的, 由于各 PE 的路由信息都可以 通过 I2RS Client来下发, 那么 PE间无需再通过 BGP来同步信息, 通过将本地信息集 中反馈给 Client, Client根据 RT属性情况, 将属于同一个 VPN用户的路由选择下发 相应的 PE, 由此减少 PE上的协议报文处理。 由于表项可直接由 Client进行读写, 当 有特殊应用申请时, 如访问控制列表 (Access Control Lists, 简称为 ACL)的流量过滤, 时间段要求、 特殊场景部署如双归等, 具体如下实施例, Client根据用户需求并网络
动荡情况进行相关条目的修改, 无需给 PE上形成复杂配置, 直接进行相关表条目的 添加删除或下一跳指定改写。 由此实现 VPN相关的策略配置实现。 实施例 3 : 在实施例 1基础上客户提出带流量过滤及时间段要求的策略申请处理 如图 6所示,在实施例 1描述基础上, 当用户提出带有流量过滤请求的 VPN业务 开通申请时。 具体如 VPN1的用户要求其不同站点间有部分客户端才可以提供直接访 问, 有部分客户端不可跨站点访问。 如站点 1内有 3个客户侧终端接入, 其 IP分别为 IP1、 IP2、 IP3 , 站点 3 内只有两个终端接入, 其 IP分别为 IP5、 IP6, 要求 IP1、 IP2 可以和 IP5通信, IP3、 IP6只能和同一站点内的成员通信, 那么根据该流量过滤的请 求, 通过 Client下发相关 VPN条目, 使站点 1内的 IP1、 IP2在 PE3上下发条目, 以 使在 PE3上只学习到远端同一 VPN下的 PE1过来的 IP1和 IP2的地址前缀,使站点 3 内的 IP5在 PE1上下发条目, 使 PE1上只学习到远端 PE3上的 IP5前缀。 该功能相比 当前实现, 不需要在各 PE上进行相关 ACL条目的配置并 BGP协议进程对该策略的 调用配置等即可实现。 在上实施例 Client收集的基础上, 根据应用可以形成的表项为: 表 6
下发相应 PE3的远端用户表项条目只有 IP1和 IP2:
表 8
当该流量过滤只在上午或下午的工作时间生效时, 上层 Client可以根据 Client上 的定时器及时下发相应条目或删除条目。 也可以在表项或相应配置中携带时间参数下 发。 具体比如该实例二第一段描述的流量过滤请求是附带了时间要求, 即部分客户跨 站点的访问只有在上班时间才可, 非正常上班时间均不允许互访。 因此要实现该有生 效时间段的策略, Client可以在上班时间中下发相应可达远端的条目信息给本地, 也 可以在表项中携带有效时间戳标识, 或可通过配置携带有效时间标识来实现。 相对表 项内容的整理, 此处涉及到如图中表项条目的添加删除, 表项中时间内容可选其中部 分内容实现。 表 9
表 10
实施例 4: 在实施例 1基础上客户提出双归接入请求, 要求实现 L3 VPN保护功 能 如图 7所示, 在实施例 1描述基础上, 当 VPN1用户下的提出站点 1的下的终端 比较多, 业务比较重要, 需要带有双归请求的 VPN业务开通申请时, 应用给网管系统 下发相应申请, 网管系统根据网络拓扑情况给站点 1提供附近的两个 PE接入, 由配 置模块下发相应配置, 具体表项管理由 I2RS Client来进行管理。
如表 11所示, 由于站点 1下的终端多, 业务繁忙并优先级较高, 那么提供附近的 两个 PE, PEl和 PE4给它提供双归接入, 希望在两个 PE上形成保护, 当希望形成保 护功能时, 只需要在上层提出保护申请, Client感知整网拓扑后, 给 PE1和 PE4都下 发一个 FRR (Fast -reroute)表项, 表明存在一个次优路径的下一跳到形成双归绑定关 系的 PE节点, 即在 PE1上下发一条到远端站点的下一跳为 PE4的路由, 该路由相比 现有最优路由, 通过在下发的表项中携带的主用、备用标识识别, 两条表项同时下发, 当主路径失效后, 不需要重新计算路径。 具体表项在 PE1上如表 12所示: 表 12
此处目的地址前缀 PE3表现为对端 PE建立 MPBGP的 loopback地址, 用于查找 公网标签用。 最优下一跳是通过和 P1直连的 IF2到达远端 PE3连接的 CE3, 此时要在 PE1上 下发一个次优路径到达远端 PE3连接的 CE3的下一跳为到 PE4的, 下一跳为 P1的路 由给打上主用标识,下一跳为 PE4的给打上备用标识。当感知到最优路径失效时, PE1 转发的流量可以通过次优路由通过 PE4可达远端 CE3。 相应的, 当要求该场景下同一站点内的远端站点具备 VPN FRR保护时, 即返程 流量 PE3可以通过 PE1和 PE4返回。 由于原有的默认实现方式, 比如 CE1双归接入
PE1、 PE4, PE3上学习到 PE1和 PE4传递过来的同一 VPNV4路由信息时, 会相应进
行路由优先级比较, 只选择最优的一条路由下发转发表, 这样就导致无法提供返回流 量的 FRR保证, 当返回的流量超出最优路径的链路带宽或最优路径失效时, 从 PE3 感知失效, 计算出新的路由, 不可避免的会产生丢包。 在该情形下, 想要实现返程流量的保护申请, Client 需要根据申请要求, 给 PE3 同时下发发布相同前缀 IP1的 CE1上路由的两个发布者, 一个为 PE1, 一个为 PE4, 将这两个发布者发布的路由均写入路由表项中, 启用 VPN FRR功能, 以使该返回流 量通过保护方式快速切换, 最终在下发转发表的时候, 会根据这两个不同的下一跳用 来查找不同的公网标签, 当有到 PE1的链路中断或 PE1的节点失效, 可以及时切换到 PE4 的链路上传输流量, 以保证流量的及时可达性。 该实现对于表项内容的主要在基 础信息上增加了主用 /备用标识。 表 13
实施例 5: 在实施例 1基础上客户提出双归接入请求, 要求实现 VPN负荷分担功 能 如图 7所示, 在实施例 1描述基础上, 当 VPN1用户下的提出站点 1的下的终端 比较多, 业务比较重要, 需要带有双归请求的 VPN业务开通申请时, 应用给网管系统 下发相应申请, 网管系统根据网络拓扑情况给站点 1提供附近的两个 PE接入, 由配 置模块下发相应配置, 具体表项管理由 I2RS Client来进行管理。 如表 11所示, 由于站点 1下的终端多, 业务繁忙并优先级较高, 那么提供附近的 两个 PE, PE1和 PE4给它提供双归接入, 对于远端 PE3站点来讲, 是可以通过 PE1 和 PE4同时到 CE1的。 因此当 PE3有 VPN的负荷分担申请时, 即 PE3可以同时通过 PE1和 PE4转发流量给 CE1。由于原有的默认实现方式,比如 CE1双归接入 PE1、PE4, PE3上学习到 PE1和 PE4传递过来的同一 VPNV4路由信息时, 会相应进行路由优先 级比较, 只选择最优的一条路由下发转发表, 这样就导致无法提供返回流量的负荷分 担保证,当返回的流量超出最优路径的链路带宽或最优路径失效时,从 PE3感知失效, 计算出新的路由, 不可避免的会产生丢包。
在该情形下, 想要实现返程流量的负荷分担申请, Client 需要根据申请要求, 给 PE3同时下发发布相同前缀 IP1的 CE1上路由的两个发布者,一个为 PE1,一个为 PE4, 将这两个发布者发布的路由均写入路由表项中, 启用负荷分担功能, 最终在下发转发 表的时候, 会根据这两个不同的下一跳用来查找不同的公网标签, 以使该返回流量可 以两条链路可达 CE1, 这样当有超过单条链路带宽的流量传输时, 不至于产生丢包。 该实现对于表项内容的主要在基础信息上增加了负荷分担标识。 表 14
实施例 6: L2 VPN自动控制及相关表项下发 相比实施例 1的 L3 VPN实现描述, L2 VPN的实现区别主要在于: 用户无需感知运营商网络的配置, 直接通过二层接入。 大致现有的 L2 VPN配置 包括:
1.配置 PE1和 PE2之间直连接口或远程会话接口。
2.配置路由协议。
3.配置 LDP协议。 4.配置二层 VPN实例, 注意 VPN传输伪线的 neighbor要和 ldp的 neighbor—致。 这其中主要包括接入侧电路(Access Circuit, 简称为 AC)侧接口的绑定和伪线邻居的 配置。 13951711825廖婷 由于现有的二层 VPN实例配置也都是需要在全网的互通的 PE上需要指定 PW邻 居的配置, 和 LDP邻居的配置或 BGP邻居的配置又得兼容, 配置量相当大并且需要 精细配置, 当出现手动配置错误的情况下, 会使同一 VPN的用户不能互通。 在 I2RS的框架下, 如图 6, 用户根据 I2RS模型中提供的应用层提出所述需求, 比如 VPN1的用户通过应用层给网管系统提出需要通过 VPN开通站点 1和 3的互通, 网管系统通过拓扑收集, 知道站点 1和 3连接的 PE为 PE1和 PE3, 那么网管系统返 回 PE1和 PE3相关的接口配置。 同时通过配置模块给 PE1和 PE3的下发相应 VPN1
相关配置主要包括: AC 侧接口的绑定、 其中原有的伪线的邻居建立, 在现有环境下 不再需要, 因为伪线建立涉及的内层标签分配可以由 Client来统一下发。 中间传输路 由和标签协议的配置, 若中间 P节点上面也都由 Client来进行控制, 外层标签也可以 统一下发。 各 PE获取到 VPN相关配置后, 本地产生一个相应 VPN MAC的 Table ID, 用以 存放该 VPN用户的本地及远端通告过来的 MAC。 由于 I2RS Client有需求可能需要直接改写相关 Table ID下的 MAC条目信息, 故 对于 VPN ID和 Table ID的映射关系, 需要通过 PE反馈给 Client。 Client由此可以学 习到各 PE上的不同 VPN的表项维护 ID, 并对同一个 VPN ID的表项内容进行直接读 写。 表项内容覆盖如下图中的目的 MAC地址、 对端 PE标识、 私网标签、 公网标签、 本地出接口等。 具体当如图 6描述: 站点 1 内有 3个客户侧终端接入, 其 MAC分别 为 MAC1、 MAC2、 MAC3 , 站点 3 内只有两个终端接入, 其 MAC分别为 MAC5、 MAC6, 那么 PE1上学习到的 CE1侧的 MAC表项有: 表 15
同样 PE3上也会有这样一张表,当把表项携带 VPN ID及表项 ID都汇总给 Client, 并由 Client给它们分配公私网标签, 则汇总的 VPN表项为: 表 16
在有 I2RS模型可能跟本发明内容不一致时, 若其均为通过 I2RS协议的外部设备 (可覆盖服务器或超级路由器等设备) 接口对路由系统进行的配置下发及表项下发或 获取, 外部本发明亦可覆盖。 实施例 7 图 8为根据本发明优选实施例的 VPN网络自动控制实现的方法流程图。 如图 8 所示, 该方法包括: 步骤 S802, VPN应用向网管系统发送 VPN业务请求(携带了本 VPN所有客户侧 边界节点 CE的位置及原始配置信息、 策略请求等); 步骤 S804, 网管系统根据接收到的 VPN业务请求信息、 本地已收集到的网络拓 扑信息确定相应的 PE; 步骤 S806, 对所选 PE执行 VPN相关配置 (包括 VPN实例配置、 接口 ip及 vrf 绑定配置、 客户接入侧 vrf对接路由协议配置、 公网标签路由相关配置及 BGP VPN配 置) .在此分为两个流程, 一个直接转入步骤 S808, 结束; 另一个转入步骤 S810, 继 续进行; 步骤 S808, 配置模块将 PE接入侧相关配置返回给应用; 步骤 S810, PE形成本地该 vpn的转发表,表项 ID和 VPN中的 RT在本地会有映 射, 当 PE和 CE成功对接后, 可以学习到本地 CE侧的相关私网路由; 步骤 S812, PE将 VPN转发表下的路由、 RT和表项 ID发送给 I2RS Client; 步骤 S814, 转发设备信息交互模块获取到同一 VPN的 PE上送的所有本地 CE侧 路由;
步骤 S816, 根据策略请求,转发设备交互模块给 PE上的该表下同一 VPN下其它 PE上送的 VPN相关路由。 通过上述实施例可以看出, 本发明实施例实现了以下有益效果: 根据 I2RS Client 可以获取的拓扑信息资源, 与手工配置相关实现相比,可以更便捷的提供自动化效果, 更及时的实现策略控制请求, 同时简化各 PE设备所需配置, 并能同时提供用户信息 下发写表功能。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技术人 员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的任何 修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内 工业实用性 本发明提供的上述技术方案,可以应用于边缘设备的虚拟私有网 VPN实现处理过 程中, 采用对 VPN应用请求和边缘设备的 VPN路由信息进行的集中计算处理, 将得 到的配置及路由控制信息进行下发的技术手段, 解决了相关技术中, VPN自动控制方 案存在配置及表项内容较为复杂等技术问题, 从而可以在统一控制平台下自动控制更 简单的配置下发, 更集中的表项管理和表项下发,减少了现有设备的配置及表项容量。
Claims
1. 一种边缘设备的虚拟私有网 VPN实现处理方法, 包括:
获取 VPN应用请求,其中,所述 VPN应用请求中携带有 VPN的属性配置 信息;
接收来自所述 VPN下的各个边缘设备的 VPN路由信息;
向所述边缘设备发送 VPN路由控制信息, 其中, 所述 VPN路由控制信息 为通过对所述属性配置信息和所述 VPN路由信息进行集中计算处理得到的路 由信息。
2. 根据权利要求 1所述的方法,其中,所述 VPN路由信息或所述路由控制信息包 括以下至少之一:
VPN列表标识 Table ID、 表项条目, 其中, 所述 VPN Table ID用于在本地 标识所述 VPN路由信息生成的表项号。
3. 根据权利要求 2所述的方法, 其中, 所述表项条目包括以下至少之一:
表项关键值、 下一跳、 出接口、 协议类型、 VPN标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间。
4. 根据权利要求 2所述的方法,其中,所述 VPN路由信息中的表项条目和所述路 由控制信息中的表项条目部分相同或完全不同。
5. 根据权利要求 3所述的方法, 其中, 所述表项关键值包括: 数据报文的目的地 址。
6. 根据权利要求 3所述的方法, 其中, 所述下一跳为边缘设备的直连下一跳标识 或多跳邻居的对等体标识。
7. 根据权利要求 3所述的方法, 其中, 所述出接口在边缘设备发送给所述网络管 理系统时为所述边缘设备的本地 VPN绑定接口或本地设备标识,在网络管理系 统给边缘设备发送时为远端边缘设备的映射标识。
8. 根据权利要求 7所述的方法, 其中, 所述映射标识包括以下至少之一:
所述远端边缘设备的标识;
所述边缘设备到所述远端边缘设备的逻辑出接口标识或物理出接口标识。
9. 根据权利要求 3所述的方法, 其中, 所述协议类型用于标识路由系统接口 I2RS 协议和 /或除所述 I2RS协议之外的其它路由协议。
10 根据权利要求 3所述的方法,其中,所述 VPN转发面标识用于对进行封装或解 封装后的数据面报文进行标识。
11. 根据权利要求 3所述的方法, 其中, 所述主备用标识用于对同一表项关键值携 带的多个下一跳分别标识为主用和备用。
12. 根据权利要求 3所述的方法, 其中, 所述 VPN标识为在控制面与 VPN—一对 应。
13. 根据权利要求 3所述的方法, 其中, 所述负荷分担标识用于对同一表项关键值 携带的多个下一跳进行标识。
14. 根据权利要求 3所述的方法,其中,所述生效时间通过以下至少之一方式实现: 根据所述边缘设备配置或默认的存活时间生效计时;
根据所述网络管理系统下发的生效时间段在边缘设备上同步生效; 通过在在网络管理系统上根据本地生效时间进行路由信息的生效发送或撤 销发送。
15. 根据权利要求 1所述的方法,其中,所述属性配置信息包括以下至少之一: VPN 标识、 路由目标 RT值设置信息、 需要开通 VPN的 PE站点标识信息、 需要启 用的路由协议类型信息、 优先级配置信息、 策略信息。
16. 根据权利要求 15所述的方法, 其中, 所述策略信息包括以下至少之一:
基于表项条目内容的过滤或更改策略、 时间预置策略、 主备用策略、 负荷 分担策略。
17. 根据权利要求 1-16任一项所述的方法, 其中, 所述边缘设备包括以下之一: 提 供商边缘 PE设备、 用户边缘 CE设备。
18. 一种边缘设备的虚拟私有网 VPN实现处理方法, 包括:
向网络管理系统发送 VPN路由信息;
接收来自网络管理系统的 VPN路由控制信息, 其中, 所述 VPN路由控制 信为通过对所述 VPN路由信息和所述网络管理系统从 VPN应用请求中获取的 VPN的属性配置信息进行集中计算处理得到的 VPN路由信息;
根据所述 VPN路由控制信息对所述边缘设备进行配置。
19. 根据权利要求 18所述的方法, 其中, 所述 VPN路由信息或所述路由控制信息 包括以下至少之一:
VPN列表标识 Table ID、 表项条目, 其中, 所述 VPN Table ID用于在本地 标识所述 VPN路由信息生成的表项号。
20. 根据权利要求 19所述的方法, 其中, 所述表项条目包括以下至少之一:
表项关键值、 下一跳、 出接口、 协议类型、 VPN标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间;
其中, 所述表项关键值包括: 数据报文的目的地址; 和 /或所述下一跳为边 缘设备的直连下一跳标识或多跳邻居的对等体标识;和 /或所述出接口在边缘设 备发送给所述网络管理系统时为所述边缘设备的本地 VPN绑定接口或本地设 备标识, 在网络管理系统给边缘设备发送时为远端边缘设备的映射标识; 和 / 或所述协议类型用于标识路由系统接口 I2RS协议和 /或除所述 I2RS之外的其它 路由协议; 和 /或所述 VPN转发面标识用于对进行封装或解封装后的数据面报 文进行标识;和 /或所述主备用标识用于对同一表项关键值携带的多个下一跳分 别标识为主用和备用; 和 /或所述 VPN标识为在控制面与 VPN—一对应; 和 / 或所述负荷分担标识用于对同一表项关键值携带的多个下一跳进行标识。
21. 根据权利要求 19所述的方法, 其中, 所述 VPN路由信息中的表项条目和所述 路由控制信息中的表项条目部分相同或完全不同。
22. 根据权利要求 20所述的方法, 其中, 所述映射标识包括以下至少之一:
所述远端边缘设备的标识;
所述边缘设备到所述远端边缘设备的逻辑出接口标识或物理出接口标识。
23. 根据权利要求 20所述的方法,其中,所述生效时间通过以下至少之一方式实现: 根据所述边缘设备配置或默认的存活时间生效计时;
根据所述网络管理系统下发的生效时间段在边缘设备上同步生效;
通过在在网络管理系统上根据本地生效时间进行路由信息的生效发送或撤 销发送。
24. 根据权利要求 18 所述的方法, 其中, 所述属性配置信息包括以下至少之一: VPN标识、路由目标 RT值设置信息、需要开通 VPN的边缘设备站点标识信息、 需要启用的路由协议类型信息、 优先级配置信息、 策略信息。
25. 根据权利要求 24所述的方法, 其中, 所述策略信息包括以下至少之一:
基于表项条目内容的过滤或更改策略、 时间预置策略、 主备用策略、 负荷 分担策略。
26. 一种边缘设备的虚拟私有网 VPN实现处理装置, 包括:
获取模块, 设置为获取 VPN应用请求, 其中, 所述 VPN应用请求中携带 有 VPN的属性配置信息;
接收模块,设置为接收来自所述 VPN下的各个边缘设备的 VPN路由信息; 发送模块, 设置为向所述边缘设备发送 VPN路由控制信息, 其中, 所述 VPN路由控制信息为通过对所述属性配置信息和所述 VPN路由信息进行集中 计算处理得到的路由信息。
27. 根据权利要求 26所述的装置, 其中, 所述接收模块和所述发送模块, 分别设置 为在所述 VPN路由信息和 /或所述 VPN路由控制信息包括以下至少之一时接收 所述 VPN路由信息和发送所述 VPN路由控制信息:
VPN列表标识 Table ID、 表项条目, 其中, 所述 VPN Table ID用于在本地 标识所述 VPN用户信息生成的表项号。
28. 根据权利要求 27所述的装置,其中,所述接收模块和所述发送模块分别设置为 在所述表项条目包括以下至少之一时,接收所述 VPN路由信息和发送所述 VPN 路由控制信息:
表项关键值、 下一跳、 出接口、 协议类型、 VPN标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间;
其中, 所述表项关键值包括: 数据报文的目的地址; 和 /或所述下一跳为边 缘设备的直连下一跳标识或多跳邻居的对等体标识;和 /或所述出接口在边缘设 备发送给所述网络管理系统时为所述边缘设备的本地 VPN绑定接口或本地设 备标识, 在网络管理系统给边缘设备发送时为远端边缘设备的映射标识; 和 /
或所述协议类型用于标识路由系统接口 I2RS协议和 /或除所述 I2RS之外的其它 路由协议; 和 /或所述 VPN转发面标识用于对进行封装或解封装后的数据面报 文进行标识;和 /或所述主备用标识用于对同一表项关键值携带的多个下一跳分 别标识为主用和备用; 和 /或所述 VPN标识为在控制面与 VPN—一对应; 和 / 或所述负荷分担标识用于对同一表项关键值携带的多个下一跳进行标识。
29. 一种边缘设备的虚拟私有网 VPN实现处理装置, 包括:
发送模块, 设置为向网络管理系统发送 VPN路由信息;
接收模块, 设置为接收来自网络管理系统的 VPN路由控制信息, 其中, 所 述 VPN路由控制信为通过对所述 VPN路由信息和所述网络管理系统从 VPN应 用请求中获取的 VPN的属性配置信息进行集中计算处理得到的路由信息; 配置模块, 设置为根据所述 VPN路由控制信息对所述边缘设备进行配置。
30. 根据权利要求 29所述的装置,其中,所述接收模块和所述发送模块分别设置为 在所述 VPN路由控制信息和 /或所述 VPN路由信息包括以下至少之一时,接收 所述 VPN路由控制信息和发送所述 VPN路由信息:
VPN列表标识 Table ID、 表项条目, 其中, 所述 VPN Table ID用于在本地 标识所述 VPN路由信息生成的表项号。
31. 根据权利要求 30所述的装置,其中,所述接收模块和所述发送模块分别设置为 在所述表项条目包括以下至少之一时,接收所述 VPN路由控制信息和发送所述 VPN路由信息:
表项关键值、 下一跳、 出接口、 协议类型、 VPN标识、 VPN转发面标识、 主备用标识、 负荷分担标识、 生效时间;
其中, 所述表项关键值包括: 数据报文的目的地址; 和 /或所述下一跳为边 缘设备的直连下一跳标识或多跳邻居的对等体标识;和 /或所述出接口在边缘设 备发送给所述网络管理系统时为所述边缘设备的本地 VPN绑定接口或本地设 备标识, 在网络管理系统给边缘设备发送时为远端边缘设备的映射标识; 和 / 或所述协议类型用于标识路由系统接口 I2RS协议和 /或除所述 I2RS之外的其它 路由协议; 和 /或所述 VPN转发面标识用于对进行封装或解封装后的数据面报 文进行标识;和 /或所述主备用标识用于对同一表项关键值携带的多个下一跳分 别标识为主用和备用; 和 /或所述 VPN标识为在控制面与 VPN—一对应; 和 / 或所述负荷分担标识用于对同一表项关键值携带的多个下一跳进行标识。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/896,024 US20160134591A1 (en) | 2013-06-05 | 2014-05-15 | VPN Implementation Processing Method and Device for Edge Device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201310222321.1 | 2013-06-05 | ||
CN201310222321.1A CN104219147B (zh) | 2013-06-05 | 2013-06-05 | 边缘设备的vpn实现处理方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014194749A1 true WO2014194749A1 (zh) | 2014-12-11 |
Family
ID=52007526
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2014/077585 WO2014194749A1 (zh) | 2013-06-05 | 2014-05-15 | 边缘设备的vpn实现处理方法及装置 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20160134591A1 (zh) |
CN (1) | CN104219147B (zh) |
WO (1) | WO2014194749A1 (zh) |
Families Citing this family (65)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10749711B2 (en) | 2013-07-10 | 2020-08-18 | Nicira, Inc. | Network-link method useful for a last-mile connectivity in an edge-gateway multipath system |
US10454714B2 (en) | 2013-07-10 | 2019-10-22 | Nicira, Inc. | Method and system of overlay flow control |
CN105897584B (zh) * | 2014-06-09 | 2018-11-30 | 华为技术有限公司 | 路径规划方法和控制器 |
CN105871719B (zh) * | 2015-01-22 | 2021-01-26 | 中兴通讯股份有限公司 | 路由状态和/或策略信息的处理方法及装置 |
US9774524B2 (en) * | 2015-02-17 | 2017-09-26 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for fast reroute, control plane and forwarding plane synchronization |
US10425382B2 (en) * | 2015-04-13 | 2019-09-24 | Nicira, Inc. | Method and system of a cloud-based multipath routing protocol |
US10498652B2 (en) | 2015-04-13 | 2019-12-03 | Nicira, Inc. | Method and system of application-aware routing with crowdsourcing |
US10135789B2 (en) | 2015-04-13 | 2018-11-20 | Nicira, Inc. | Method and system of establishing a virtual private network in a cloud service for branch networking |
CN106713098A (zh) * | 2015-07-27 | 2017-05-24 | 中兴通讯股份有限公司 | 路由目标处理方法及装置 |
CN106712987A (zh) * | 2015-08-12 | 2017-05-24 | 中兴通讯股份有限公司 | 网络控制的处理方法、装置及软件定义网络系统 |
CN111030929A (zh) * | 2015-10-16 | 2020-04-17 | 华为技术有限公司 | 一种路由处理方法、设备及系统 |
CN105471735B (zh) * | 2015-12-28 | 2018-07-13 | 迈普通信技术股份有限公司 | 数据流量路由控制方法和装置 |
CN111355661B (zh) * | 2015-12-31 | 2021-12-10 | 华为技术有限公司 | 一种vpn的处理方法和pe设备以及系统 |
CN106470143A (zh) * | 2016-08-26 | 2017-03-01 | 杭州迪普科技股份有限公司 | 一种mpls vpn流量过滤的方法和装置 |
CN107872387B (zh) * | 2016-09-26 | 2020-10-13 | 中国电信股份有限公司 | 发送vpn路由的方法和系统 |
US20180219765A1 (en) | 2017-01-31 | 2018-08-02 | Waltz Networks | Method and Apparatus for Network Traffic Control Optimization |
US10992568B2 (en) | 2017-01-31 | 2021-04-27 | Vmware, Inc. | High performance software-defined core network |
US20200036624A1 (en) | 2017-01-31 | 2020-01-30 | The Mode Group | High performance software-defined core network |
US11252079B2 (en) | 2017-01-31 | 2022-02-15 | Vmware, Inc. | High performance software-defined core network |
US11706127B2 (en) | 2017-01-31 | 2023-07-18 | Vmware, Inc. | High performance software-defined core network |
US10778528B2 (en) | 2017-02-11 | 2020-09-15 | Nicira, Inc. | Method and system of connecting to a multipath hub in a cluster |
US10516550B2 (en) * | 2017-02-27 | 2019-12-24 | Futurewei Technologies, Inc. | Traffic engineering service mapping |
US10389635B2 (en) | 2017-05-31 | 2019-08-20 | Juniper Networks, Inc. | Advertising selected fabric paths for service routes in virtual nodes |
US10659352B2 (en) * | 2017-05-31 | 2020-05-19 | Juniper Networks, Inc. | Signaling private context forwarding tables for a private forwarding layer |
US10432523B2 (en) | 2017-05-31 | 2019-10-01 | Juniper Networks, Inc. | Routing protocol signaling of multiple next hops and their relationship |
US10382333B2 (en) | 2017-05-31 | 2019-08-13 | Juniper Networks, Inc. | Fabric path context-based forwarding for virtual nodes |
US10476817B2 (en) | 2017-05-31 | 2019-11-12 | Juniper Networks, Inc. | Transport LSP setup using selected fabric path between virtual nodes |
US10523539B2 (en) | 2017-06-22 | 2019-12-31 | Nicira, Inc. | Method and system of resiliency in cloud-delivered SD-WAN |
US11115480B2 (en) | 2017-10-02 | 2021-09-07 | Vmware, Inc. | Layer four optimization for a virtual network defined over public cloud |
US10686625B2 (en) | 2017-10-02 | 2020-06-16 | Vmware, Inc. | Defining and distributing routes for a virtual network |
US10999100B2 (en) | 2017-10-02 | 2021-05-04 | Vmware, Inc. | Identifying multiple nodes in a virtual network defined over a set of public clouds to connect to an external SAAS provider |
CN107566196A (zh) * | 2017-10-20 | 2018-01-09 | 北京星河星云信息技术有限公司 | 组网方法和组网装置、用户边缘设备及可读存储介质 |
US11223514B2 (en) | 2017-11-09 | 2022-01-11 | Nicira, Inc. | Method and system of a dynamic high-availability mode based on current wide area network connectivity |
CN109104364B (zh) * | 2017-11-27 | 2020-11-06 | 新华三技术有限公司 | 一种指定转发者选举方法和装置 |
CN108011759B (zh) * | 2017-12-05 | 2021-06-18 | 锐捷网络股份有限公司 | 一种vpn管理方法、装置及系统 |
US10666461B2 (en) * | 2018-06-07 | 2020-05-26 | Adva Optical Networking Se | VLAN reflection |
CN114745319A (zh) | 2018-06-30 | 2022-07-12 | 华为技术有限公司 | 一种避免环路的通信方法、设备和系统 |
CN109257285B (zh) * | 2018-10-31 | 2021-06-29 | 中国联合网络通信集团有限公司 | 路由存储方法及装置 |
US11121985B2 (en) | 2019-08-27 | 2021-09-14 | Vmware, Inc. | Defining different public cloud virtual networks for different entities based on different sets of measurements |
CN112671646B (zh) * | 2019-10-16 | 2023-01-10 | 中国移动通信有限公司研究院 | 一种信息处理方法、装置、设备及计算机可读存储介质 |
US11044190B2 (en) | 2019-10-28 | 2021-06-22 | Vmware, Inc. | Managing forwarding elements at edge nodes connected to a virtual network |
US11489783B2 (en) | 2019-12-12 | 2022-11-01 | Vmware, Inc. | Performing deep packet inspection in a software defined wide area network |
US11394640B2 (en) | 2019-12-12 | 2022-07-19 | Vmware, Inc. | Collecting and analyzing data regarding flows associated with DPI parameters |
US11722925B2 (en) | 2020-01-24 | 2023-08-08 | Vmware, Inc. | Performing service class aware load balancing to distribute packets of a flow among multiple network links |
CN113726651B (zh) * | 2020-05-25 | 2022-12-13 | 华为技术有限公司 | 一种路由管理方法、设备及系统 |
CN111800338B (zh) * | 2020-06-01 | 2022-09-16 | 锐捷网络股份有限公司 | 跨as的evpn路由交互方法及装置 |
US11477127B2 (en) | 2020-07-02 | 2022-10-18 | Vmware, Inc. | Methods and apparatus for application aware hub clustering techniques for a hyper scale SD-WAN |
CN114079670B (zh) * | 2020-07-30 | 2023-07-11 | 华为技术有限公司 | 传输路由信息的方法、装置和通信系统 |
US11709710B2 (en) | 2020-07-30 | 2023-07-25 | Vmware, Inc. | Memory allocator for I/O operations |
US11575591B2 (en) | 2020-11-17 | 2023-02-07 | Vmware, Inc. | Autonomous distributed forwarding plane traceability based anomaly detection in application traffic for hyper-scale SD-WAN |
US11575600B2 (en) | 2020-11-24 | 2023-02-07 | Vmware, Inc. | Tunnel-less SD-WAN |
US11929903B2 (en) | 2020-12-29 | 2024-03-12 | VMware LLC | Emulating packet flows to assess network links for SD-WAN |
US11792127B2 (en) | 2021-01-18 | 2023-10-17 | Vmware, Inc. | Network-aware load balancing |
US11979325B2 (en) | 2021-01-28 | 2024-05-07 | VMware LLC | Dynamic SD-WAN hub cluster scaling with machine learning |
US12009987B2 (en) | 2021-05-03 | 2024-06-11 | VMware LLC | Methods to support dynamic transit paths through hub clustering across branches in SD-WAN |
US11388086B1 (en) | 2021-05-03 | 2022-07-12 | Vmware, Inc. | On demand routing mesh for dynamically adjusting SD-WAN edge forwarding node roles to facilitate routing through an SD-WAN |
US11729065B2 (en) | 2021-05-06 | 2023-08-15 | Vmware, Inc. | Methods for application defined virtual network service among multiple transport in SD-WAN |
US11489720B1 (en) | 2021-06-18 | 2022-11-01 | Vmware, Inc. | Method and apparatus to evaluate resource elements and public clouds for deploying tenant deployable elements based on harvested performance metrics |
US12015536B2 (en) | 2021-06-18 | 2024-06-18 | VMware LLC | Method and apparatus for deploying tenant deployable elements across public clouds based on harvested performance metrics of types of resource elements in the public clouds |
US12047282B2 (en) | 2021-07-22 | 2024-07-23 | VMware LLC | Methods for smart bandwidth aggregation based dynamic overlay selection among preferred exits in SD-WAN |
US11375005B1 (en) | 2021-07-24 | 2022-06-28 | Vmware, Inc. | High availability solutions for a secure access service edge application |
CN115914094A (zh) * | 2021-09-30 | 2023-04-04 | 华为技术有限公司 | 一种路由发布方法、报文转发方法、设备及系统 |
US11943146B2 (en) | 2021-10-01 | 2024-03-26 | VMware LLC | Traffic prioritization in SD-WAN |
US11909815B2 (en) | 2022-06-06 | 2024-02-20 | VMware LLC | Routing based on geolocation costs |
US12034587B1 (en) | 2023-03-27 | 2024-07-09 | VMware LLC | Identifying and remediating anomalies in a self-healing network |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050188106A1 (en) * | 2004-02-11 | 2005-08-25 | Alcatel | Managing L3 VPN virtual routing tables |
CN101355516A (zh) * | 2008-09-09 | 2009-01-28 | 中兴通讯股份有限公司 | 一种为不同虚拟专用网提供服务质量策略的方法和系统 |
CN102882758A (zh) * | 2011-07-12 | 2013-01-16 | 华为技术有限公司 | 虚拟私云接入网络的方法、网络侧设备和数据中心设备 |
CN103095543A (zh) * | 2011-11-07 | 2013-05-08 | 华为技术有限公司 | 用于域间虚拟专用网络对接的方法和设备 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3945297B2 (ja) * | 2001-04-24 | 2007-07-18 | 株式会社日立製作所 | システム及び管理システム |
US7450598B2 (en) * | 2003-12-15 | 2008-11-11 | At&T Intellectual Property I, L.P. | System and method to provision MPLS/VPN network |
CN100384172C (zh) * | 2004-01-20 | 2008-04-23 | 华为技术有限公司 | 基于网络的虚拟专用网中保证服务质量的系统及其方法 |
KR100693059B1 (ko) * | 2005-01-24 | 2007-03-12 | 삼성전자주식회사 | Mpls 기반의 vpn 제공 장치 및 방법 |
US7990888B2 (en) * | 2005-03-04 | 2011-08-02 | Cisco Technology, Inc. | System and methods for network reachability detection |
US8995446B2 (en) * | 2009-12-21 | 2015-03-31 | Cisco Technology, Inc. | Efficient generation of VPN-based BGP updates |
ES2565827T3 (es) * | 2011-07-22 | 2016-04-07 | Huawei Technologies Co., Ltd. | Método de control de enrutamiento, aparato y sistema de red privada virtual de capa 3 |
CN102611574A (zh) * | 2012-02-23 | 2012-07-25 | 成都飞鱼星科技开发有限公司 | Vpn自动配置系统及配置方法 |
-
2013
- 2013-06-05 CN CN201310222321.1A patent/CN104219147B/zh not_active Expired - Fee Related
-
2014
- 2014-05-15 WO PCT/CN2014/077585 patent/WO2014194749A1/zh active Application Filing
- 2014-05-15 US US14/896,024 patent/US20160134591A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050188106A1 (en) * | 2004-02-11 | 2005-08-25 | Alcatel | Managing L3 VPN virtual routing tables |
CN101355516A (zh) * | 2008-09-09 | 2009-01-28 | 中兴通讯股份有限公司 | 一种为不同虚拟专用网提供服务质量策略的方法和系统 |
CN102882758A (zh) * | 2011-07-12 | 2013-01-16 | 华为技术有限公司 | 虚拟私云接入网络的方法、网络侧设备和数据中心设备 |
CN103095543A (zh) * | 2011-11-07 | 2013-05-08 | 华为技术有限公司 | 用于域间虚拟专用网络对接的方法和设备 |
Also Published As
Publication number | Publication date |
---|---|
US20160134591A1 (en) | 2016-05-12 |
CN104219147A (zh) | 2014-12-17 |
CN104219147B (zh) | 2018-10-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014194749A1 (zh) | 边缘设备的vpn实现处理方法及装置 | |
US11936552B2 (en) | Method and device for implementing VPN cross-domain, and border node | |
CN107222449B (zh) | 基于流规则协议的通信方法、设备和系统 | |
CN111865796B (zh) | 用于网络业务的路径计算单元中央控制器(pcecc) | |
EP3133778B1 (en) | Method and device for realizing communication between nvo3 network and mpls network | |
WO2019105462A1 (zh) | 报文的发送、处理方法及装置,pe节点,节点 | |
US20110013637A1 (en) | Method, System and Gateway for Remotely Accessing MPLS VPN | |
US20110110370A1 (en) | Compressed virtual routing and forwarding in a communications network | |
WO2016058329A1 (zh) | 业务传送方法及装置 | |
WO2006005260A1 (fr) | Reseau prive virtuel et procede de commande et de transmission d'acheminement | |
WO2012088982A1 (zh) | 路由信息发布方法、设备及虚拟专用网系统 | |
CN107018076B (zh) | 一种报文监控方法和装置 | |
WO2015055016A1 (zh) | 网元设备配置和管理方法、装置及网元设备 | |
EP2926507A1 (en) | Methods and routers for connectivity setup between provider edge routers | |
WO2006002598A1 (fr) | Systeme vpn de reseau federateur hybride a site hybride et son procede de mise en oeuvre | |
WO2014194711A1 (zh) | 报文处理方法、设备标签处理方法及设备 | |
WO2007003088A1 (fr) | Méthode et système de mise à jour d’une route | |
WO2013139270A1 (zh) | 实现三层虚拟专用网络的方法、设备及系统 | |
Chen | Design and implementation of secure enterprise network based on DMVPN | |
US10212075B1 (en) | Convergence optimization of local switching for flexible cross-connect in ethernet virtual private network (EVPN) environments | |
WO2015027736A1 (zh) | 分层虚拟专用局域网服务的实现方法及装置 | |
CN113904981B (zh) | 一种路由信息处理方法、装置、电子设备和存储介质 | |
WO2005125103A1 (fr) | Systeme de reseau prive virtuel d'un site hybride et reseau de base hybride et procede de mise en oeuvre associe | |
WO2023082779A1 (zh) | 报文转发方法、电子设备及存储介质 | |
Wu et al. | Research on the application of cross-domain VPN technology based on MPLS BGP |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14807371 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14896024 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14807371 Country of ref document: EP Kind code of ref document: A1 |