WO2016066072A1 - 实现nvo3网络与mpls网络之间通信的方法和装置 - Google Patents

实现nvo3网络与mpls网络之间通信的方法和装置 Download PDF

Info

Publication number
WO2016066072A1
WO2016066072A1 PCT/CN2015/092876 CN2015092876W WO2016066072A1 WO 2016066072 A1 WO2016066072 A1 WO 2016066072A1 CN 2015092876 W CN2015092876 W CN 2015092876W WO 2016066072 A1 WO2016066072 A1 WO 2016066072A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
mpls
nvo3
asbr
address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2015/092876
Other languages
English (en)
French (fr)
Inventor
郝卫国
梁乾灯
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP15853776.1A priority Critical patent/EP3133778B1/en
Publication of WO2016066072A1 publication Critical patent/WO2016066072A1/zh
Priority to US15/393,049 priority patent/US10484203B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4675—Dynamic sharing of VLAN information amongst network nodes
    • H04L12/4679—Arrangements for the registration or de-registration of VLAN attribute values, e.g. VLAN identifiers, port VLAN membership
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5061—Pools of addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2212/00—Encapsulation of packets

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and apparatus for implementing communication between an NVO3 network and an MPLS network.
  • NVO3 Network Virtualization over Layer 3
  • This technology can virtualize a physical network so that it can be used by different tenants.
  • the NVO3 encapsulation header contains a 24-bit virtual network ID (VN ID). Different VN IDs are used to identify different virtual networks (VNs). Different VN IDs can be used to isolate different tenants belonging to different VNs. The traffic between.
  • VN ID virtual network ID
  • Typical data encapsulation in the NVO3 technology includes VXLAN (Virtual eXtensible Local Area Network), NVGRE (Network virtualization Generic Routing Encapsulation), etc., where VXLAN adopts MAC (Media Access Control).
  • VXLAN Virtual eXtensible Local Area Network
  • NVGRE Network virtualization Generic Routing Encapsulation
  • MAC Media Access Control
  • UDP User Datagram Protocol
  • GRE Generic Routing Encapsulation
  • the edge device of the NVO3 network is called the Network Virtualization Edge (NVE).
  • the NVE is connected to the Tenants Terminal System (TES).
  • the TES can be referred to as the Tenant System (TS) for short.
  • NVE is similar to PE (Provider Edge) in BGP (Multi-Protocol Label Switching) IP (Internet Protocol) VPN (Virtual Private Network) network.
  • the device is similar to the CE (Customer Edge) device in the BGP/MPLS IP VPN network.
  • NVE can On a server or physical network device, the TS can be a virtual machine of the server, or a physical server, or a value-added service device such as a firewall or a load balancer.
  • MPLS VPN networks are widely deployed.
  • MPLS VPNs include L2 (Layer 2) VPNs and L3 (Layer 3) VPNs. Users have access to the data center through the MPLS VPN network.
  • the MPLS VPN network and the NVO3 network generally belong to two Autonomous System (AS) domains. When accessing the data center through the MPLS VPN network, cross-domain interworking is involved.
  • AS Autonomous System
  • Option C is a way to achieve cross-domain network interconnection.
  • the BGP LSP Label Switch Path
  • the VPN routing information is directly transmitted between the source PE and the sink PE through the multi-hop MP-EBGP.
  • the Autonomous System Border Router ASBR
  • ASBR Autonomous System Border Router
  • an inter-AS LSP is set up between the PEs in different ASs.
  • the LDP Label Distribution Protocol
  • the inter-domain EBGP Extra Border Gateway Protocol
  • the border gateway protocol distributes labels.
  • PEs in different ASs use the multi-hop MP (Multiprotocol)-EBGP to propagate VPN routing information.
  • MP Multiprotocol
  • Layer 3 labels are used in the domain
  • ASBRs in the two ASs are used.
  • Two-layer label forwarding is used. Because the MPLS network needs to be deployed in the two AS domains that communicate with each other, the OPTION C mode can only interconnect the MPLS VPN homogeneous networks.
  • Embodiments of the present invention provide a method and apparatus for implementing communication between an NVO3 network and an MPLS network, so as to implement cross-domain communication between the NVO3 network and the MPLS network.
  • a first aspect of the present invention provides a method for implementing communication between an NVO3 network and an MPLS network.
  • the first autonomous system AS deploys an NVO3 network
  • the second AS deploys an MPLS network.
  • the method includes:
  • the autonomous domain edge router ASBR in the NVO3 network obtains the identifier of the carrier edge PE device in the MPLS network and the MPLS label allocated by the ASBR in the MPLS network, and the MPLS label allocated by the ASBR in the MPLS network will be The outer label of the MPLS encapsulation packet sent by the ASBR to the PE device in the NVO3 network;
  • the ASBR in the NVO3 network allocates an IP address to the MPLS label from the local address pool, the ASBR in the NVO3 network communicates with the network virtual edge NVE in the NVO3 network, and the NVE-connected tenant terminal system TES
  • the user edge CE device connected to the PE device belongs to the same virtual private network VPN;
  • the ASBR in the NVO3 network saves a correspondence between the MPLS label and the allocated IP address
  • the ASBR in the NVO3 network sends routing information to the NVE, where the routing information includes an identifier of the PE device and the allocated IP address, and the allocated IP address is used to send the TES to the CE.
  • the outer destination address of the packet encapsulated by the NVO3 device is used to send the TES to the CE.
  • the ASBR in the NVO3 network obtains the identifier of the PE device in the MPLS network and the MPLS label allocated by the ASBR in the MPLS network, including:
  • the ASBR in the NVO3 network receives the BGP packet sent by the ASBR in the MPLS network, and the BGP packet sent by the ASBR in the MPLS network carries the identifier of the PE device and the ASBR in the MPLS network.
  • the assigned MPLS label is the assigned MPLS label.
  • the method further includes: receiving, by the ASBR in the NVO3 network, the NVO3 encapsulation of the NVE transmission
  • the outer address of the NVO3 encapsulated packet is the IP address of the packet
  • the outer source address of the NVO3 encapsulated packet is the IP address of the NVE
  • the NVO3 encapsulated packet The file further includes a virtual network identifier VN ID, the VN ID is an MPLS VPN label advertised by the PE device, the MPLS VPN label is used to identify a VPN to which the CE device belongs, and the ASBR in the NVO3 network generates a packet.
  • the generated packet carries two layers of MPLS labels, and the MPLS label allocated by the ASBR in the MPLS network is used as an outer label in the two layers of MPLS labels, and the VN ID is used as the two layers of MPLS labels.
  • the inner layer label, the generated packet does not include the outer layer destination address and the outer layer source address, and the generated packet further carries a payload of the NVO3 encapsulated packet; the NVO3
  • the ASBR in the network sends to the ASBR in the MPLS network Said packets generated.
  • the method further includes: the ASBR in the NVO3 network is the NVE The identifier of the MPLS label is allocated; the ASBR in the NVO3 network sends a BGP packet to the ASBR in the MPLS network, and the BGP sent to the ASBR in the MPLS network The packet carries the identifier of the NVE and the MPLS label allocated for the identifier of the NVE; the ASBR in the NVO3 network saves the identifier of the NVE and the MPLS label allocated for the identifier of the NVE relationship.
  • the method further includes: receiving, by the ASBR in the NVO3 network, an ASBR forwarded packet in the MPLS network
  • the packet forwarded by the ASBR in the MPLS network is from the PE device, and the inner label in the packet forwarded by the ASBR in the MPLS network is the VN ID of the virtual network to which the TES belongs.
  • the outer label in the packet forwarded by the ASBR in the MPLS network is the MPLS label allocated for the identifier of the NVE; the ASBR in the NVO3 network generates an NVO3 encapsulated packet, and the generated NVO3 encapsulation
  • the outer destination address of the packet is the IP address of the NVE
  • the outer source address of the generated NVO3 encapsulated packet is the IP address of the ASBR in the NVO3 network, and the generated NVO3 encapsulated report
  • the message also carries the VN ID of the virtual network to which the TES belongs
  • the generated NVO3 encapsulated packet also carries the payload of the packet forwarded by the ASBR in the MPLS network; the ASBR in the NVO3 network
  • the NVE sends the generated NVO3 encapsulated message.
  • the identifier of the PE device is IP address.
  • the second aspect of the present invention provides another method for implementing communication between an NVO3 network and an MPLS network.
  • the first autonomous system AS deploys an NVO3 network
  • the second AS deploys an MPLS network.
  • the method includes:
  • the network virtual edge NVE in the NVO3 network receives the routing information sent by the autonomous domain edge router ASBR in the NVO3 network, where the routing information includes the correspondence between the IP address and the identifier of the carrier edge PE device in the MPLS network.
  • the relationship is that the IP address is allocated by the ASBR in the NVO3 network to the PE device from the local address pool, and is used as a user edge CE device to which the tenant terminal system TES of the NVE connection is sent to the PE device.
  • the outer-layer destination address of the packet encapsulated by the NVO3, the user-edge CE device connected to the NUE-connected tenant terminal system TES and the PE device belongs to the same virtual private network VPN;
  • the NVE receives an MPLS VPN label advertised by the PE device and an identifier of the CE device, where the MPLS VPN label is used to identify a VPN to which the CE device belongs;
  • the NVE generates VPN routing information, where the VPN routing information includes an identifier of the CE device, The assigned IP address and the VN ID, the VN ID is the MPLS VPN label, and the allocated IP address is used as an outer destination address of the NVO3 encapsulation.
  • the method further includes: the NVE receiving a packet sent by the TES to the PE device, and the packet sent to the PE device
  • the NVI carries the identifier of the CE device
  • the NVE encapsulates the packet sent by the TES to the PE device to perform NVO3 encapsulation to generate an NVO3 encapsulated packet, where the outer address of the packet encapsulated by the NVO3 is
  • the IP address of the NVO3 encapsulated packet is the IP address of the NVE
  • the NVO3 encapsulated packet further includes a VN ID, where the VN ID is the MPLS advertised by the PE device.
  • a VPN label the MPLS VPN label is used to identify a VPN to which the CE device belongs, and the NVE sends the NVO3 encapsulated packet to an ASBR in the NVO3 network.
  • the method further includes: the NVE sending a VPN route to the PE device, where the VPN The route carries the MPLS VPN label and the identifier of the TES, and the MPLS VPN label carried in the VPN route is a VN ID of the virtual network to which the TES belongs.
  • the method further includes: receiving, by the NVE, an NVO3 encapsulated packet sent by an ASBR in the NVO3 network,
  • the outbound destination address of the NVO3 encapsulated packet received by the NVE is an IP address of the NVE
  • the outer source address of the NVO3 encapsulated packet received by the NVE is an ASBR in the NVO3 network.
  • the NVO3 encapsulated packet received by the NVE also carries the VN ID of the virtual network to which the TES belongs; the NVE decapsulates the received NVO3 encapsulated packet according to the TES The VN ID of the associated virtual network sends the decapsulated message to the TES in the NVO3 network.
  • the identifier of the PE device is IP address.
  • the third aspect of the present invention provides an autonomous domain edge router ASBR.
  • the first autonomous system AS deploys a three-layer network virtualized NVO3 network
  • the second autonomous system AS deploys a multi-protocol label switching MPLS network, where the ASBR is the first AS.
  • the ASBR includes:
  • a receiving module configured to obtain an identifier of a carrier edge PE device in the MPLS network, and an MPLS label allocated by an ASBR in the MPLS network, where the ASBR in the MPLS network is allocated
  • the MPLS label is used as an outer label of the MPLS encapsulated packet sent by the ASBR to the PE device in the NVO3 network;
  • An allocating module configured to allocate an IP address to the MPLS label from a local address pool, where an ASBR in the NVO3 network communicates with a network virtual edge NVE in the NVO3 network, and the NVE-connected tenant terminal system TES and The user edge CE device connected to the PE device belongs to the same virtual private network VPN.
  • a storage module configured to save a correspondence between the MPLS label and the allocated IP address
  • a sending module configured to send routing information to the NVE, where the routing information includes an identifier of the PE device and the allocated IP address, where the allocated IP address is used to send the TES to the CE device The outer destination address of the NVO3 encapsulated packet.
  • the receiving module is configured to receive a BGP packet sent by an ASBR in the MPLS network, where the ASBR in the MPLS network sends the The BGP packet carries the identifier of the PE device and the MPLS label allocated by the ASBR in the MPLS network.
  • the receiving module is further configured to receive an NVO3 encapsulated packet sent by the NVE, where The outer address of the NVO3 encapsulated packet is the assigned IP address, the outer source address of the NVO3 encapsulated packet is the IP address of the NVE, and the NVO3 encapsulated packet further includes a virtual network.
  • the VN ID is an MPLS VPN label advertised by the PE device, and the MPLS VPN label may be used to identify a VPN to which the CE device belongs;
  • the ASBR further includes a generating module, configured to generate a packet, The generated packet carries two layers of MPLS labels, and the MPLS label allocated by the ASBR in the MPLS network is used as an outer label in the two layers of MPLS labels, and the VN ID is used as the two layers of MPLS labels.
  • the inner layer label, the generated packet does not include the outer layer destination address and the outer layer source address, and the generated packet further carries the payload of the NVO3 encapsulated packet; the sending module Also used to send to the ASBR in the MPLS network The generated message.
  • the allocating module is further configured to allocate an MPLS label to the identifier of the NVE.
  • the sending module is further configured to send a BGP packet to the ASBR in the MPLS network, where the BGP packet sent to the ASBR in the MPLS network carries the identifier of the NVE.
  • the MPLS label allocated for the identifier of the NVE; the storage module is further configured to save a correspondence between the identifier of the NVE and the MPLS label allocated for the identifier of the NVE.
  • the receiving module is further configured to receive, by the ASBR, the packet forwarded by the ASBR in the MPLS network,
  • the packet forwarded by the ASBR in the MPLS network is from the PE device, and the inner label in the packet forwarded by the ASBR in the MPLS network is the VN ID of the virtual network to which the TES belongs.
  • the outer label in the packet forwarded by the ASBR in the MPLS network is the MPLS label allocated for the identifier of the NVE; the generating module is further configured to generate an NVO3 encapsulated packet, and the generated NVO3 encapsulation
  • the outer destination address of the packet is the IP address of the NVE
  • the outer source address of the generated NVO3 encapsulated packet is the IP address of the ASBR in the NVO3 network, and the generated NVO3 encapsulated report
  • the message also carries the VN ID of the virtual network to which the TES belongs, and the generated NVO3 encapsulated packet also carries the payload of the packet forwarded by the ASBR in the MPLS network; the sending module is further used to The NVE sends the generated NVO3 encapsulated message.
  • the fourth aspect of the present invention provides a network virtual edge NVE, wherein the first autonomous system AS deploys a three-layer network virtualized NVO3 network, and the second autonomous system AS deploys a multi-protocol label switching MPLS network, and the NVE is used in the first
  • the NVE includes: a receiving module, configured to receive routing information sent by an autonomous domain edge router ASBR in the NVO3 network, where the routing information includes an IP address and a carrier edge PE device in the MPLS network.
  • the IP address is allocated by the ASBR in the NVO3 network to the PE device from the local address pool, and the tenant terminal system TES serving as the NVE connection is sent to the PE device.
  • the information about the VPN routing information includes the identifier of the CE device, the allocated IP address, and the VN ID, where the VN ID is the MPLS VPN label, and the allocated IP address is used as an outer layer of the NVO3 encapsulation. address.
  • the receiving module is further configured to receive a packet sent by the TES to the PE device, and the packet sent to the PE device An identifier of the CE device, and a generating module, configured to send a packet sent by the TES to the PE device
  • the NVO3 is encapsulated to generate an NVO3 encapsulated packet, and the outer address of the NVO3 encapsulated packet is the assigned IP address, and the outer source address of the NVO3 encapsulated packet is the IP address of the NVE.
  • the NVO3 encapsulated packet further includes a VN ID, where the VN ID is an MPLS VPN label advertised by the PE device, the MPLS VPN label is used to identify a VPN to which the CE device belongs, and a sending module is used to The ASBR in the NVO3 network sends the NVO3 encapsulated packet.
  • VN ID is an MPLS VPN label advertised by the PE device
  • MPLS VPN label is used to identify a VPN to which the CE device belongs
  • a sending module is used to The ASBR in the NVO3 network sends the NVO3 encapsulated packet.
  • the NVE further includes: a route sending module, configured to send a VPN route to the PE device,
  • the VPN route carries an MPLS VPN label and an identifier of the TES, and the MPLS VPN label carried in the VPN route is a VN ID of the virtual network to which the TES belongs.
  • the receiving module is further configured to receive an NVO3 encapsulation sent by an ASBR in the NVO3 network.
  • a packet, the outer destination address of the NVO3 encapsulated packet received by the NVE is an IP address of the NVE, and an outer source address of the NVO3 encapsulated packet received by the NVE is the NVO3 network
  • the IP address of the ASBR in the NVE, the packet of the NVO3 encapsulation received by the NVE also carries the VN ID of the virtual network to which the TES belongs; the sending module is further configured to report the received NVO3 encapsulation
  • the encapsulation packet is sent to the TES in the NVO3 network according to the VN ID of the virtual network to which the TES belongs.
  • a fifth aspect of the present invention provides a computer network device, comprising: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer to execute an instruction, and the processor and the memory pass The bus connection, the processor executing the computer-executed instructions stored by the memory to cause the computer device to perform an NVO3 network and MPLS as described in the first aspect of the invention when the computer device is running A method of communication between networks, or a method of implementing communication between an NVO3 network and an MPLS network as described in the second aspect of the present invention.
  • the ASBR in the NVO3 network receives the MPLS label allocated by the ASBR in the MPLS network to the PE device in the MPLS network, the ASBR in the NVO3 network no longer allocates MPLS for the PE device.
  • the label is assigned an IP address from the local address pool instead of the MPLS label, and the corresponding relationship between the IP address and the MPLS label (that is, the exchange entry) is generated for forwarding the traffic packet from the NVO3 network to the MPLS network.
  • the MPLS label allocated by the ASBR is used as an outer label of a packet sent by the ASBR in the NVO3 network to the PE device, and the allocated IP address is used as a TES in the MPLS network and sent to the MPLS network.
  • the outer destination address of the NVO3 encapsulated packet of the CE device is used as an outer label of a packet sent by the ASBR in the NVO3 network to the PE device, and the allocated IP address is used as a TES in the MPLS network and sent to the MPLS network.
  • the solution of the embodiment of the present invention does not need to configure a VRF (VPN Routing and Forwarding) and a sub-interface for each VPN on the ASBR.
  • the ASBR does not need to save and maintain the VPN route, and only needs to save and maintain the PE.
  • FIG. 1 is a flowchart of a method for implementing communication between an NVO3 network and an MPLS network according to Embodiment 1 of the present invention
  • FIG. 2 is a flowchart of a method for implementing communication between an NVO3 network and an MPLS network according to Embodiment 2 of the present invention
  • FIGS. 3a-3d are schematic diagrams of network architecture and communication in Embodiment 3 of the present invention.
  • FIGS. 4a-4b are schematic diagrams of network architectures in Embodiment 4 of the present invention.
  • FIG. 5 is a schematic structural diagram of an ASBR according to Embodiment 5 of the present invention.
  • FIG. 5b is a schematic structural diagram of another ASBR according to Embodiment 5 of the present invention.
  • FIG. 6 is a schematic structural diagram of an NVE according to Embodiment 6 of the present invention.
  • FIG. 6b is a schematic structural diagram of another NVE according to Embodiment 6 of the present invention.
  • FIG. 7 is a schematic diagram of a logical structure of a computer device according to an embodiment of the present invention.
  • the embodiments of the present invention provide a method and apparatus for implementing communication between an NVO3 network and an MPLS network, so as to implement cross-domain communication between the NVO3 network and the MPLS network.
  • an embodiment of the present invention provides a method for implementing communication between an NVO3 network and an MPLS network, where the method is used for communication between an NVO3 network and an MPLS network, and the NVO3 network is deployed in the first autonomous system (first AS). , AS1), the MPLS network is deployed in the second autonomous system (second AS, AS2); the method may include:
  • the ASBR (Autonomous System Border Router) in the NVO3 network obtains the identifier of the PE (Provider Edge, Router Edge) device in the MPLS network and the ASBR allocation in the MPLS network.
  • An MPLS label the MPLS label allocated by the ASBR in the MPLS network, which is used as an outer label of the MPLS encapsulated packet sent by the ASBR to the PE device in the NVO3 network;
  • the ASBR in the NVO3 network allocates an IP address to the MPLS label from the local address pool, and the ASBR in the NVO3 network communicates with the NVE (Network Virtualization Edge) in the NVO3 network.
  • the CE (Customer Edge) device connected to the PE device of the NVE connection belongs to the same VPN (virtual private network);
  • the ASBR in the NVO3 network saves a correspondence between the MPLS label and the allocated IP address.
  • the ASBR in the NVO3 network sends routing information to the NVE, where the routing information includes an identifier of the PE device (the IP address of the PE itself) and the allocated IP address, and the allocation The IP address is used as the outer destination address of the NVO3 encapsulation message sent by the TES to the CE device.
  • the ASBR in the NVO3 network receives the MPLS label allocated by the MPLS network ASBR to the PE device
  • the ASBR in the NVO3 network is no longer the same as the traditional MPLS Option C cross-domain interconnection scheme.
  • the PE device continues to allocate MPLS labels. Instead, it allocates an IP address from the local address pool instead of the MPLS label, and generates an IP address and an MPLS label exchange entry for forwarding traffic packets from the NVO3 network to the MPLS network.
  • the MPLS label allocated by the ASBR in the MPLS network is used as an outer label of the packet sent by the ASBR in the NVO3 network to the PE device, and the allocated IP address is used as the MPLS network.
  • the outer destination address of the packet sent by the NVO3 encapsulation of the CE device in the MPLS network It can be seen that in the VPN cross-domain interconnection communication between the NVO3 network and the MPLS network, the NVO3 network replaces the label encapsulation (ie, MPLS encapsulation) of the traditional MPLS Option C cross-domain with the NVO3 encapsulation.
  • the solution of the embodiment of the present invention does not need to configure a VRF and a sub-interface for each VPN on the ASBR, and the ASBR does not need to save and maintain the VPN route, and only needs to save and maintain the PE/NVE route and a small number of MPLS labels and NVO3 packages.
  • the table entry is converted, and therefore, the solution of the present invention can alleviate the burden of the ASBR and has better scalability.
  • an embodiment of the present invention provides another method for implementing communication between an NVO3 network and an MPLS network, where the method is used for communication between an NVO3 network and an MPLS network, and the NVO3 network is deployed in the first autonomous system (first AS, AS1), the MPLS network is deployed in the second autonomous system (second AS, AS2); the method may include:
  • the NVE in the NVO3 network receives the routing information sent by the ASBR in the NVO3 network, where the routing information includes a correspondence between an IP address and an identifier of the PE device in the MPLS network, where the IP address is
  • the ASBR in the NVO3 network is allocated from the local address pool to the PE device, and is used as the NVO3 encapsulation packet of the user edge CE device connected to the PE device.
  • the NVE receives the MPLS VPN label advertised by the PE device and the identifier of the CE device, where the MPLS VPN label can be used to identify the VPN to which the CE device belongs.
  • the NVE generates VPN routing information, where the VPN routing information includes an identifier of the CE device, the allocated IP address, and a VN ID, where the VN ID is the MPLS VPN label, and the allocated IP address is The destination address of the outer layer of the NVO3 package.
  • the ASBR in the NVO3 network receives the MPLS label allocated by the ASBR in the MPLS network for the PE device, the ASBR in the NVO3 network is no longer
  • the MPLS label is further allocated to the PE device, and an IP address is allocated from the local address pool instead of the MPLS label, and an exchange entry of the IP address and the MPLS label is generated, and routing information including the correspondence between the IP address and the MPLS label is sent.
  • the NVE can also obtain the MPLS VPN label advertised by the PE device in the MPLS network and the identifier of the CE device, so that the NVE can generate an identifier including the CE device and the allocated IP address.
  • the VPN routing information of the VN ID that is, the MPLS VPN label
  • the NVE may perform NVO3 encapsulation of the packet sent by the TES in the NVO3 network to the CE device of the MPLS network according to the VPN routing information; that is, in the NVO3 network.
  • the NVO3 network replaces the label encapsulation in the traditional MPLS Option C cross-domain with the NVO3 encapsulation.
  • the present invention does not need to configure a VRF and a sub-interface for each VPN on the ASBR, and the ASBR does not need to save and maintain the VPN route, and only needs to save and maintain the PE/NVE route and a small number of MPLS labels and NVO3 encapsulation conversion entries. Therefore, the solution of the present invention can alleviate the burden of the ASBR and has better scalability.
  • the method of communication between the NVO3 network and the MPLS network can be divided into a control plane scheme and a data plane scheme.
  • the data plane can include two directions, that is, an uplink direction from the NVO3 network to the MPLS network, and a downlink direction from the MPLS network to the NVO3 network.
  • the network architecture includes: a first AS (AS1) and a second AS (AS2), the first AS deploys an NVO3 network, and the second AS deploys an MPLS network.
  • the ASBR of the NVO3 network (represented by ASBR1 in the figure) communicates with the NVE, and the NVE connects, for example, two TESs, TES1 and TES2.
  • the ASBR of the MPLS network (represented by ASBR2 in the figure) communicates with the PE device, and the PE device connects, for example, two CE devices, CE1 and CE2.
  • TES1 and CE1 belong to the same VPN and are represented by VPN1; TES2 and CE2 belong to the same VPN and are represented by VPN2.
  • IBGP Interior Border Gateway Protocol
  • IBGP session exchange routing information is also established between ASBR2 and PE2 of the MPLS network.
  • An EBGP (External Border Gateway Protocol) session is exchanged between ASBR1 and ASBR2.
  • An MP-EBGP session is directly established between the NVE and the PE to exchange VPN routes and distribute and issue VPN label information to each other.
  • a Label Distribution Protocol (LDP) protocol can be deployed in the MPLS network to distribute labels for the IGP (Interior Gateway Protocol).
  • LDP Label Distribution Protocol
  • the solution for the control plane of the uplink packet may include:
  • Each node device of the MPLS network allocates an MPLS label (that is, a BGP MPLS public network label) to the PE in turn, and advertises it to the next level.
  • an MPLS label that is, a BGP MPLS public network label
  • the IP address of the PE is 20.1.1.1, assuming that the IP address of the ASBR2 is 200.1.1.1, assuming that the IP address of the ASBR1 is 100.1.1.1, assuming that the IP address of the NVE is 10.1.1.1.
  • the MPLS label 50 is assigned to the MPLS label, and the BGP label is advertised to the ASBR2 through the BGP label.
  • the ASBR2 assigns the MPLS label 150 to the IP address 20.1.1.1 of the PE and advertises the MPLS label to the ASBR1 through the BGP label.
  • the ASBR of the NVO3 network that is, the ASBR1 obtains the identifier of the PE device in the MPLS network, and the MPLS label allocated by the ASBR in the MPLS network, that is, the MPLS label from the local address pool. Assign an IP address.
  • the step of allocating may include: the ASBR1 receiving the BGP packet sent by the ASBR2 in the MPLS network, where the BGP packet carries the identifier of the PE device and the MPLS allocated by the ASBR2 label.
  • the MPLS label allocated by the ASBR (ASBR2) in the MPLS network will be used as the outer label of the MPLS encapsulated packet sent by the ASBR (ASBR1) to the PE device in the NVO3 network.
  • the identifier of the PE device may specifically be an IP address of the PE device.
  • the ASBR1 is also The mapping between the MPLS label allocated by the ASBR2 and the IP address assigned by the ASBR1 may be saved, and the IP address allocated by the ASBR1 and the forwarding entry of the MPLS label allocated by the ASBR2 are generated (from the NVO3 network side). Go to the MPLS network side, that is, the uplink direction).
  • the ASBR1 sends routing information to the NVE (NVE1 in the figure), where the routing information includes the identifier of the PE device and the allocated IP address and their corresponding relationships.
  • the allocated IP address is used as an outer destination address of the message sent by the TES to the NVO3 encapsulation of the CE device.
  • routing information about multiple PE devices may be carried in a routing message.
  • the ASBR1 can advertise the routing information to the NVE through the BGP label routing.
  • the routing information includes the IP address of the PE. 20.1.1.1 and the IP address of the ASBR1, which is 30.1.1.1 (for example, 30.1.1.1/24). .
  • ASBR1 to NVE can define a new type of route attribute or BGP extended team attribute or new NLRI (network layer reachability information) type, or use defined IPv4Address Specific Extended Community or Opaque Extended One of the two attributes of the community carries the local IP address assigned to PE2, which may be an IPv4 address or an IPv6 address.
  • a new type of NLRI may be composed of one or more ⁇ length, NVO3Tunnel IP, prefix> triplets, and carried in the MP_REACH_NLRI or MP_UNREACH_NLRI attribute, where length represents the length of the NVO3Tunnel IP and the prefix in the triplet, and the NVO3Tunnel IP is the The local IP address assigned to the PE, and the prefix is the IP address prefix corresponding to the PE identifier.
  • the PE is an identifier of the CE1, for example, an IP address prefix or a MAC address of the CE1, and an MPLS VPN label is allocated.
  • the MPLS VPN label is used to identify the VPN to which the CE1 device belongs (ie, VPN1), and the assigned MPLS VPN is configured.
  • the label and the identifier advertised by CE1, such as the IP address prefix or MAC address of CE1, are advertised to the NVE.
  • the NVE receives the MPLS VPN label advertised by the PE device and the identifier of the CE device that is advertised by the CE (for example, an IP address prefix or a MAC address of the CE1), where the MPLS VPN label can be used to identify that the CE device belongs to The VPN, or the interface of the PE device connected to the CE device, or the identifier of the CE device.
  • the MPLS VPN label can be used to identify that the CE device belongs to The VPN, or the interface of the PE device connected to the CE device, or the identifier of the CE device.
  • the NVE can generate the VPN routing information, that is, the identifier of the CE device that is advertised by the PE, for example, the IP address prefix or the MAC address of the CE device, is imported into the local VPN routing forwarding table, where the VPN routing information includes The identifier of the CE device (for example, the IP address prefix or MAC address of the CE device) Address, the assigned IP address, and the VN ID, the VN ID is the MPLS VPN label, and the allocated IP address is used as an outer destination address of the NVO3 encapsulation.
  • the VPN routing information includes The identifier of the CE device (for example, the IP address prefix or MAC address of the CE device) Address, the assigned IP address, and the VN ID, the VN ID is the MPLS VPN label, and the allocated IP address is used as an outer destination address of the NVO3 encapsulation.
  • the NVE may iterate out an outer destination address (the IP address) of the NVO3 tunnel of the CE device according to the identifier of the PE, and use the MPLS VPN label as an NVO3 tunnel.
  • the VN ID is the MPLS VPN label advertised by the PE.
  • the destination of the NVO3 tunnel is the IP address assigned by the ASBR1 from the local address pool.
  • the source address is the IP address of the NVE.
  • the VNID is the MPLS VPN label advertised by the PE.
  • the solution for the data plane of the uplink packet may include:
  • the NVE receives the packet sent by the TES1 to the CE device, and the packet sent to the PE device carries the identifier of the CE device, searches the VPN routing forwarding table, and then performs NVO3 encapsulation to generate an NVO3 encapsulated packet.
  • the packet payload is used to indicate the packet sent by TES1 to the CE device.
  • the NVE encapsulates the packet payload with NVO3, and generates an NVO3 encapsulated packet.
  • the outer destination address of the NVO3 encapsulated packet is the allocated IP address (for example, 30.1.1.1), and the NVO3 encapsulated packet.
  • the outer source address of the text is the IP address of the NVE (for example, 10.1.1.1)
  • the NVO3 encapsulated packet further includes a VN ID, where the VN ID is an MPLS VPN label (for example, 2000) advertised by the PE.
  • the MPLS VPN label may be used to identify a VPN to which the CE device belongs (ie, VPN1).
  • the NVE searches the VPN routing forwarding table according to the VN ID, and sends the NVO3 encapsulated packet to the ASBR1.
  • A202 The ASBR1 receives the NVO3 encapsulated packet sent by the NVE, and generates a packet encapsulation (ie, MPLS encapsulation).
  • a packet encapsulation ie, MPLS encapsulation
  • the outer address of the NVO3 encapsulated packet is the assigned IP address
  • the outer source address of the NVO3 encapsulated packet is the IP address of the NVE
  • the NVO3 encapsulated packet further includes the VN. ID
  • the VN ID is an MPLS VPN label advertised by the PE device, and the MPLS VPN label may be used to identify a VPN to which the CE device belongs.
  • the ASBR1 decapsulates the NVO3 encapsulated packet, and searches for the corresponding MPLS label (that is, the MPLS label assigned by the ASBR2, for example, 150) according to the allocated IP address (for example, 30.1.1.1). Performing label encapsulation (ie, MPLS encapsulation) on the decapsulated packet payload, and obtaining a packet encapsulated packet, where the packet encapsulated packet carries two layers of MPLS labels, where the MPLS network
  • the MPLS label (for example, 150) allocated by the ASBR2 is used as an outer label in the two-layer MPLS label, and the VN ID (for example, 2000) is used as an inner label in the two-layer MPLS label, and the generated label
  • the encapsulated packet does not include the outer destination address and the outer source address, and the generated packet encapsulated packet further carries the payload of the NVO3 encapsulated packet.
  • the ASBR1 sends the generated packet encapsulated packet to the ASBR2 according to
  • the ABR and the ASBR2 receive the packet encapsulated by the ASBR1, and the packet is translated into a Layer 3 label and sent to the PE.
  • the PE removes all label encapsulation and sends the packet payload to CE1.
  • the packets encapsulated by the Layer 3 label include the Layer 3 label.
  • the outer label is the LDP label.
  • the middle label is the MPLS label assigned by the PE (for example, BGP MPLS public network label).
  • the inner label is the VN ID (for example, 2000). ).
  • the solution for the control plane of the downlink packet may include:
  • the ASBR1 of the NVO3 network allocates an MPLS label (specifically, a BGP MPLS public network label) to the identifier of each NVE in the NVO3 network, and allocates an MPLS label and a corresponding NVE to which the ASBR1 is the identifier of the NVE.
  • the identifier is carried in the BGP packet and sent to the ASBR2 in the MPLS network.
  • the ASBR1 may further store a correspondence between the identifier of the NVE and the MPLS label allocated for the identifier of the NVE, and generate a forwarding table corresponding to the MPLS label allocated by the ASBR1 to the identifier of the NVE. Item (from the MPLS network side to the NVO3 network side).
  • the identifier of the NVE may specifically be an IP address of the NVE, such as an IPv4 address or an IPv6 address.
  • B102 and ASBR2 receive the BGP packets sent by ASBR1 and allocate MPLS labels.
  • the NVE sends a VPN route to the PE device, where the VPN route carries an identifier of the TES and an MPLS VPN label, where the MPLS VPN label carried in the VPN route is The identifier VN ID of the NVO3 network to which the TES belongs.
  • the VN ID cannot exceed 20 bits, that is, the value of the VN ID used for interworking between the NVO3 network and the MPLS network cannot be greater than 2 times of 20 times.
  • Square (1,048,576) the identifier of the TES may be an IP address prefix or a MAC address of the TES.
  • the PE device may import the IP address prefix or MAC address of the TES carried in the local L2/L3 VPN forwarding table.
  • the NVE assigns an MPLS VPN label 1000 to the IP address of the TES1, which is the VN ID of the NVO3 virtual network.
  • the solution for the data plane of the downlink packet may include:
  • the B201 and the PE receive the packet sent by the CE1 to the TES1, and the packet sent by the CE1 to the TES1 is encapsulated in the Layer 3 label, and then sent to the ASBR2.
  • the ASBR2 is translated into a two-layer label encapsulation, and the packet encapsulated by the two layers is generated and sent to the packet. ASBR1.
  • the packet encapsulated by the PE includes three layers of labels.
  • the outermost label is the LDP label.
  • the middle layer label is the MPLS label assigned by the ASBR2 (for example, 200, that is, the BGP MPLS public network label).
  • the layer label is the VN ID (for example, 1000) of the virtual network to which the TES1 belongs.
  • the packet encapsulated by the ASBR2 includes two layers of labels.
  • the inner label is the VN ID of the virtual network to which the TES1 belongs (for example, 1000)
  • the outer label is the MPLS label allocated by the ASBR1 for the identifier of the NVE. For example, 100).
  • the label forwarding scheme from CE1 to ASBR2 can refer to the traditional Option C scheme, and will not be described in detail herein.
  • B202 and ASBR1 receive the packet encapsulated by the ASBR2, decapsulate the packet payload, and encapsulate the packet payload in NVO3 to generate the NVO3 encapsulated packet.
  • the inner label of the packet forwarded by the ASBR2 in the MPLS network is the VN ID (for example, 1000) of the virtual network to which the TES belongs, and the outer label in the packet forwarded by the ASBR2 in the MPLS network.
  • the MPLS label e.g., 100 assigned to the identity of the NVE.
  • the outer address of the NVO3 encapsulated packet is the IP address of the NVE (for example, 10.1.1.1), and the outer source address is the IP address of the ASBR1 in the NVO3 network (for example, 100.1.1.1).
  • the NVO3 encapsulated packet further carries the VN ID (for example, 1000) of the virtual network to which the TES belongs.
  • the NVO3 encapsulated packet further carries the packet forwarded by the ASBR1 in the MPLS network. Load.
  • the ASBR1 sends the generated NVO3 to the NVE Encapsulated message.
  • the NVE receives the packet of the NVO3 encapsulation sent by the ASBR1, decapsulates the packet encapsulated by the NVO3, and sends the decapsulated packet to the packet according to the VN ID of the virtual network to which the TES belongs. TES in the NVO3 network.
  • the NVE after receiving the NVO3 encapsulated packet sent by the ASBR1, the NVE can find the local VRF according to the VN ID (for example, 1000), determine the receiving end TES1, decapsulate the packet, and send the packet payload to the TES1.
  • VN ID for example, 1000
  • FIGS. 3a-3d are only some preferred manners of the present invention, and are not intended to limit the present invention. .
  • a local address pool may be deployed on ASBR1 of the NVO3 network.
  • the address resource of the local address pool can be valid only in the NVO3 network, and the corresponding route is not advertised to the external network. That is, the local IP address pool can use the IP address of the private address network segment. However, it should be understood that the local IP address pool can also use the IP address of the public network address segment.
  • the ASBR1 can distribute the IP prefix route corresponding to the local address pool to the routing neighbors in the NVO3 network by means of the BGP/IGP protocol distribution, so that each network device in the NVO3 network knows the IP address corresponding to the local address pool. Prefix routing.
  • the ASBR1 can be configured with a local command, an NMS (Network Management System) configuration, or a dynamic protocol to discover the NVE of the AS domain, and allocate an MPLS label to the NVE of the AS domain.
  • the CE device and the TES in the NVO3 network belong to the same VPN. It can be understood that the CE and the TES can be interconnected by searching for a Layer 2 MAC forwarding entry or a Layer 3 IP routing entry. If interworking is achieved through IP, it is L3VPN.
  • the ASBR1 may save the correspondence between the local IP address allocated by the PE and the identifier of the PE, or an association.
  • the NVE may associate the identifier of the PE (for example, a public network IP address). And the assigned IP address, such that when the NVE of the NVO3 network performs NVO3 encapsulation on the packet sent by the tenant terminal system in the NVO3 network to the PE, the local IP allocated for the PE may be used.
  • the address is the destination address of the outer IP header of the NVO3 encapsulation.
  • the NVE and the PE directly establish an MP-EBGP session, and the VPN is exchanged between the NVE or the GW and the remote PE.
  • the information includes: allocating an MPLS VPN label to the peer VPN instance discovered by the local configuration or the BGP AD mechanism, and distributing the MPLS VPN label and the L2 or L3 routing information to the PE, and receiving the MPLS distributed by the PE VPN tag and L2 (MAC) or L3 (IP) routing information.
  • the NVE when the NVE receives the traffic message from the TES in the NVO3 network to the CE device in the MPLS network, the NVE can query the forwarding information table of the VPN according to the destination identifier of the packet to obtain the PE.
  • the NVO3 encapsulation of the packet wherein the destination address of the outer IP header of the NVO3 encapsulation is filled with the local IP address assigned by the PE, and the source address of the outer IP header is filled with the IP address of the NVE, and the VN ID is filled.
  • the MPLS VPN label advertised for the PE is
  • the network node of the NVO3 network forwards according to the destination address of the outer IP header of the packet encapsulated by the NVO3, and the ASBR1 receives the packet encapsulated by the NVO3, according to the outer layer.
  • the destination address of the IP header is used to find the next hop information obtained by the routing of the public IP address of the egress PE, including the MPLS label corresponding to the IP address of the PE.
  • the ASBR1 can receive the packet encapsulated by the CE device in the MPLS network to the TES in the NVO3 network; the packet should be encapsulated with two layers of labels: the outer label is an MPLS label (corresponding to the egress NVE) Routing), the inner label is the MPLS VPN label. Then, the ASBR1 can convert the packet encapsulated by the two-layer label into a packet encapsulated by the NVO3 and send the packet to the NVE.
  • the outer label is an MPLS label (corresponding to the egress NVE) Routing)
  • the inner label is the MPLS VPN label.
  • the NVE may directly strip the NVO3 encapsulation and send the packet payload according to the VN ID in the NVO3 encapsulation. TES in the NVO3 network.
  • the technical solution of the embodiment of the present invention is compared with the traditional OPTION C cross-domain solution.
  • the ASBR in the NVO3 network receives the MPLS label allocated by the ASBR in the MPLS network to the PE device in the MPLS network, the NVO3 network is used.
  • the ASBR no longer allocates MPLS labels to the PE device, but allocates an IP address from the local address pool instead of the MPLS label, and generates a correspondence between the IP address and the MPLS label (that is, an exchange entry) for the NVO3 network. Forwarding traffic to the MPLS network.
  • the ASBR of the NVO3 network allocates an MPLS label to each NVE, and advertises the correspondence between the label and the NVE identifier to the ASBR of the MPLS network, and generates an MPLS label and The exchange entry of the NVE identifier is used for traffic forwarding from the MPLS network to the NVO3 network.
  • the ASBR of the NVO3 network needs to map the VN ID in the NVO3 data encapsulation to the MPLS encapsulation inner MPLS VPN label.
  • the VN ID value is copied to the MPLS.
  • Inner label When the packet is transmitted from the MPLS network to the NVO3 network, the inner MPLS VPN label is copied to the VN ID of the NVO3 data encapsulation.
  • the technical solution of the embodiment of the present invention does not need to configure a VRF and a sub-interface for each VPN on the ASBR, and the ASBR does not need to save and maintain the VPN route, and only needs to save and maintain the PE/NVE route and a small number of MPLS labels and NVO3 package conversion tables. Therefore, the solution of the present invention can alleviate the burden of the ASBR and has better scalability.
  • the technical solution of the embodiment of the present invention can implement the cross-domain communication between the NVO3 network and the MPLS network by performing NVO3 encapsulation and label encapsulation on the ASBR of the NVO3 network, and solves the problem that the general NVO3 network device does not support label forwarding, and cannot The problem of using the traditional OPTION C cross-domain solution to communicate with the MPLS network.
  • FIG. 4a and 4b are network architecture diagrams of the present embodiment, and the network architecture diagrams shown in FIG. 3a-3d in the third embodiment are different in that a centralized controller (NVA) is added to the NVO3 network.
  • the AS1 ie DC1 deploying the NVO3 network can be centrally controlled by the NVAController.
  • the NVA can be used to forward and forward the routing data through the OpenFlow protocol (such as the Open VSwtich Database).
  • the VXLAN Virtual EXtensible Local Area Network
  • the NVA can be used to forward and forward tenant data packets. Save information about all TES, tenants, and connected NVEs.
  • An EBGP session is established between the AS and the ASBR2 in the AS to exchange public network routing information.
  • the local address pool is configured on the NVA.
  • the NVA allocates an MPLS label to each NVE, and advertises the NVE identifier and the MPLS label to the ASBR of the MPLS network.
  • the NVA is Each MPLS label corresponding to the PE identifier is assigned a local IP address.
  • IBGP session exchange routing information is still established between ASBR2 and PE2.
  • the LDP protocol deployed on AS2 distributes labels for IGP routes.
  • the solution for the control plane of the uplink packet may include:
  • Each node device of the MPLS network allocates an MPLS label (that is, a BGP MPLS public network label) to the PE in turn, and advertises it to the next level.
  • an MPLS label that is, a BGP MPLS public network label
  • This step is the same as step A101 in the embodiment of Fig. 3a.
  • the IP address of the PE is 20.1.1.1
  • the IP address of the ASBR2 is 200.1.1.1
  • the IP address of the ASBR1 is 100.1.1.1
  • the IP address of the NVE is 10.1.1.1.
  • the MPLS label 50 is assigned to the MPLS label 50 through the BGP label.
  • the ASBR2 assigns the MPLS label 150 to the IP address 20.1.1.1 of the PE and advertises the MPLS label to the NVA through the BGP label.
  • the NVA allocates an IP address to the PE in the MPLS network from the local address pool, and sends an association between the MPLS label and the assigned IP address to the ASBR1, and is used for converting the NVO3 encapsulated packet to the MPLS packet.
  • the NVA sends the routing information and the corresponding NVO3 encapsulation entries advertised by the CE2 to the NVE. Specifically, the NVA sends the routing information to the NVE1, where the routing information includes the correspondence between the identifier of the PE device and the assigned IP address, and is used for NVO3 encapsulation.
  • the function of the ASBR1 is replaced by the NVA, and the IP address of the PE in the MPLS network is allocated from the local address pool.
  • the step of allocating the network includes: receiving, by the NVA, the first BGP packet sent by the ASBR2 in the MPLS network, where the first BGP packet carries the identifier of the PE device and the first MPLS label allocated by the ASBR2
  • the first MPLS label is used as an outer label of the packet sent by the ASBR1 to the PE device; the NVA allocates an IP address to the first MPLS label.
  • the identifier of the PE device may specifically be an IP address of the PE device.
  • the NVA can advertise the routing information to the NVE.
  • the routing information includes the IP address of the PE 20.1.1.1 and the IP address assigned by the NVA 30.1.1.1.
  • the PE assigns an MPLS VPN label to the identifier of the CE1, for example, an IP address prefix or a MAC address, where the MPLS VPN label is used to identify the VPN to which the CE1 device belongs (ie, VPN1), and the assigned MPLS VPN label (and, It can also be advertised to the NVA by the IP address prefix or MAC address advertised by the PE, and sent to the NVE by the NVA.
  • the NVE can import the IP address prefix or MAC address advertised by the PE delivered by the NVA into the local VPN routing forwarding table.
  • the solution for the data plane of the uplink packet may include:
  • the scheme of the data plane of the uplink packet is the same as that of FIG. 3b and the corresponding step A2 of the third embodiment.
  • the scheme of the data plane of the uplink packet is the same as that of FIG. 3b and the corresponding step A2 of the third embodiment.
  • the solution for the control plane of the downlink packet may include:
  • the NVA of the NVO3 network allocates an MPLS label (specifically, a BGP MPLS public network label) to the identifier of each NVE in the NVO3 network, and carries the MPLS label and the corresponding NVE identifier in the BGP packet. Transmitted to ASBR2 in the MPLS network.
  • the identifier of the NVE may specifically be an IP address of the NVE, such as IPv4 or IPv6.
  • the NVA also sends the mapping entry corresponding to the MPLS label and the corresponding NVE identifier to the ASBR1 for MPLS packet to NVO3 encapsulation packet conversion.
  • F102 and ASBR2 receive the BGP packets sent by ASBR1 and allocate MPLS labels.
  • the NVA allocates an MPLS VPN label to the TES, where the MPLS VPN label is an identifier VN ID of the NVO3 virtual network to which the TES belongs, and sends a VPN route to the PE device, where the VPN route carries the identifier of the TES.
  • MPLS VPN tags may be an IP address prefix or a MAC address of the TES.
  • the PE device may import the IP address prefix or MAC address of the TES carried in the local L2/L3 VPN forwarding table.
  • the NVA assigns an MPLS VPN label 1000 to the IP address of the TES1, which is the VN ID of the NVO3 virtual network.
  • the NVA sends the NVO3 tunnel decapsulation entry and the routing entry corresponding to the TES1 to the NVE, including the MPLS VPN label and the TES identifier allocated by the TES.
  • the solution for the data plane of the downlink packet may include:
  • the scheme of the data plane of the downlink packet is the same as that of FIG. 3d and the corresponding step B2 of the third embodiment.
  • the scheme of the data plane of the downlink packet is the same as that of FIG. 3d and the corresponding step B2 of the third embodiment.
  • the solution of the present invention does not need to configure a VRF and a sub-interface for each VPN on the ASBR, and the ASBR does not need to save and maintain the VPN route, and only needs to save and maintain the PE/NVE route and a small number of MPLS labels and NVO3 package conversion.
  • the entry therefore, the solution of the present invention can alleviate the burden of the ASBR and has better scalability.
  • the technical solution of the present invention can implement cross-domain communication between the NVO3 network and the MPLS network by performing NVO3 encapsulation and label encapsulation on the ASBR of the NVO3 network, and solves the problem that the general NVO3 network device does not support label forwarding, and cannot adopt the traditional The OPTION C cross-domain solution communicates with the MPLS network.
  • an embodiment of the present invention provides an autonomous domain edge router (ASBR).
  • the first AS deploys an NVO3 network, and the second AS deploys an MPLS network.
  • the ASBR is an edge router in the first AS.
  • the ASBR 500 can include:
  • the receiving module 501 is configured to obtain an identifier of a carrier edge PE device in the MPLS network and an MPLS label allocated by an ASBR in the MPLS network, where an MPLS label allocated by an ASBR in the MPLS network is used as the NVO3 The outer label of the MPLS encapsulated packet sent by the ASBR to the PE device in the network;
  • the allocating module 502 is configured to allocate an IP address for the MPLS label from a local address pool, where the ASBR in the NVO3 network communicates with a network virtual edge NVE in the NVO3 network, and the NVE connected tenant terminal system
  • the user edge CE device connected to the PE device by the TES belongs to the same virtual private network VPN;
  • a storage module 503, configured to save a correspondence between the MPLS label and the allocated IP address
  • the sending module 504 is configured to send routing information to the NVE, where the routing information includes an identifier of the PE device and the allocated IP address, where the allocated IP address is used to send the TES to the CE The outer destination address of the packet encapsulated by the NVO3 device.
  • the receiving module 501 is specifically configured to receive a BGP packet sent by an ASBR in the MPLS network, where the BGP packet sent by the ASBR in the MPLS network carries the PE The identity of the device and the MPLS label assigned by the ASBR in the MPLS network.
  • the ASBR 500 may further include: a generating module 505;
  • the receiving module 501 is further configured to receive an NVO3 encapsulated packet sent by the NVE, where an outer destination address of the NVO3 encapsulated packet is the allocated IP address, and the NVO3 encapsulated packet is external to the packet.
  • the layer source address is an IP address of the NVE
  • the NVO3 encapsulated packet further includes a VN ID, where the VN ID is an MPLS VPN label advertised by the PE device, and the MPLS VPN label may be used to identify the CE VPN to which the device belongs;
  • the generating module 505 is configured to generate a packet, where the generated packet carries two layers of MPLS labels, and the MPLS label allocated by the ASBR in the MPLS network is used as an outer label in the two layers of MPLS labels.
  • the VN ID is used as an inner layer label in the two-layer MPLS label, and the generated packet does not include the outer layer destination address and the outer layer source address, and the generated packet further carries the The payload of the NVO3 encapsulated message;
  • the sending module 504 is further configured to send the generated packet to an ASBR in the MPLS network.
  • the allocating module 502 is further configured to allocate an MPLS label to the identifier of the NVE
  • the sending module 502 is further configured to send a BGP packet to the ASBR in the MPLS network.
  • the BGP packet sent to the ASBR in the MPLS network carries the identifier of the NVE and the MPLS label allocated for the identifier of the NVE.
  • the storage module 503 is further configured to save the NVE. Correspondence between the identifier and the MPLS label assigned to the identifier of the NVE.
  • the receiving module 501 is further configured to receive the packet forwarded by the ASBR in the MPLS network, where the packet forwarded by the ASBR in the MPLS network is from the PE device, and the ASBR in the MPLS network forwards the packet.
  • the inner label in the packet is an identifier ID of the virtual network VN to which the TES belongs, and the outer label in the packet forwarded by the ASBR in the MPLS network is allocated for the identifier of the NVE.
  • the generating module 505 is further configured to generate an NVO3 encapsulated packet, where the outer address of the generated NVO3 encapsulated packet is an IP address of the NVE, and the outer layer of the generated NVO3 encapsulated packet
  • the source address is the IP address of the ASBR in the NVO3 network
  • the generated NVO3 encapsulated packet further carries the VN ID of the virtual network to which the TES belongs, and the generated NVO3 encapsulated packet also carries the packet.
  • the payload of the packet forwarded by the ASBR in the MPLS network;
  • the sending module 504 is further configured to send the generated NVO3 encapsulated packet to the NVE.
  • the present invention does not need to configure a VRF and a sub-interface for each VPN on the ASBR, and the ASBR does not need to save and maintain the VPN route, and only needs to save and maintain the PE/NVE route and a small number of MPLS labels and NVO3 encapsulation conversion entries. Therefore, the solution of the present invention can alleviate the burden of the ASBR and has better scalability.
  • an embodiment of the present invention provides a network virtualization edge node (NVE).
  • the first AS deploys an NVO3 network
  • the second AS deploys an MPLS network.
  • the NVE is used in the first AS, and the NVE600 is used.
  • the receiving module 601 is configured to receive routing information sent by an ASBR in the NVO3 network, where the routing information includes an IP address and an identifier of a PE device in the MPLS network, where the IP address is an ASBR in the NVO3 network.
  • the receiving module 601 is further configured to receive an MPLS VPN label advertised by the PE device and an identifier of the CE device, where the MPLS VPN label may be used to identify a VPN to which the CE device belongs;
  • the routing module 602 is configured to generate VPN routing information, where the VPN routing information includes an identifier of the CE device, the allocated IP address, and a VN ID, where the VN ID is the MPLS VPN label, and the allocated IP address The address is used as the outer destination address of the NVO3 encapsulation.
  • the NVE 600 may further include: a generating module 603 and a sending module 604;
  • the receiving module 601 is further configured to receive a packet sent by the TES to the PE device, where the packet sent to the PE device carries an identifier of the CE device;
  • the generating module 603 is configured to perform NVO3 encapsulation on the packet sent by the TES to the PE device to generate an NVO3 encapsulated packet, where an outer destination address of the NVO3 encapsulated packet is the allocated IP address.
  • the outer source address of the NVO3 encapsulated packet is the IP address of the NVE, and the NVO3 encapsulated packet further includes a VN ID, where the VN ID is an MPLS VPN label advertised by the PE device, and the MPLS The VPN label can be used to identify the VPN to which the CE device belongs.
  • the sending module 604 is configured to send the NVO3 encapsulated packet to the ASBR in the NVO3 network.
  • the NVE 600 may further include:
  • the route sending module 605 is configured to send a VPN route to the PE device, where the VPN route carries an MPLS VPN label and an identifier of the TES, where the MPLS VPN label carried in the VPN route belongs to the TES The VN ID of the virtual network.
  • the receiving module 601 is further configured to receive an NVO3 encapsulated packet sent by the ASBR in the NVO3 network, where an outer destination address of the NVO3 encapsulated packet received by the NVE is an IP address of the NVE.
  • the outer source address of the NVO3 encapsulated packet received by the NVE is an IP address of the ASBR in the NVO3 network, and the NVO3 encapsulated packet received by the NVE further carries the TES to which the TES belongs.
  • VN ID of the virtual network
  • the sending module 604 is further configured to: decapsulate the received NVO3 encapsulated packet, and send the decapsulated packet to the TES in the NVO3 network according to the VN ID of the virtual network to which the TES belongs. .
  • the present invention does not need to configure a VRF and a sub-interface for each VPN on the ASBR, and the ASBR does not need to save and maintain the VPN route, and only needs to save and maintain the PE/NVE route and a small number of MPLS labels and NVO3 encapsulation conversion entries. Therefore, the solution of the present invention can alleviate the burden of the ASBR and has better scalability.
  • the embodiment of the present invention further provides a computer storage medium, where the computer storage medium may store a program, and the program includes some or all of the steps of the VPN cross-domain communication method described in Embodiment 1 of the foregoing method.
  • an embodiment of the present invention further provides a computer device 700, which may include:
  • Processor 710 memory 720, communication interface 730, bus 740;
  • the memory 720 is configured to store computer execution instructions
  • the processor 710 is coupled to the memory 720 via the bus 740, and when the computer device is running, the processor 710 executes the memory stored in the memory 720
  • the computer executes instructions to cause the computer device to perform the method of communicating between the NVO3 network and the MPLS network as described in the above embodiments.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: ROM, RAM, disk or CD.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开了一种实现NVO3网络与MPLS网络之间通信的方法和装置，以实现NVO3网络和MPLS VPN网络跨域通信。在本发明一些可行的实施方式中，方法包括：NVO3网络中的ASBR获得MPLS网络中的PE设备的标识和MPLS网络中的ASBR分配的MPLS标签，MPLS标签将用作NVO3网络中的ASBR发往PE设备的MPLS封装的报文的外层标签；从本地地址池中为MPLS标签分配IP地址，保存MPLS标签与分配的IP地址的对应关系；向NVE发送路由信息，路由信息包括PE设备的标识和分配的IP地址，分配的IP地址用作NVO3网络中的TES发往MPLS网络中的PE设备连接的CE设备的NVO3封装的报文的外层目的地址。

Description

实现NVO3网络与MPLS网络之间通信的方法和装置
本申请要求于2014年10月27日提交中国专利局、申请号为CN201410584292.8、发明名称为“实现NVO3网络与MPLS网络之间通信的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，具体涉及一种实现NVO3网络与MPLS网络之间通信的方法和装置。
背景技术
三层网络虚拟化(Network Virtualization over Layer3，NVO3)是一种实现网络虚拟化的技术，通过该技术可以将一个物理网络进行虚拟化，使之可以被不同租户共同使用。NVO3封装头中包含24bit的虚拟网络标识(Virtual Network ID，VN ID)，不同的VN ID用于标识不同的虚拟网络(Virtual Network，VN)，不同的VN ID可用于隔离属于不同VN的不同租户之间的流量。
NVO3技术中典型的数据封装包括VXLAN(Virtual eXtensible Local Area Network，虚拟扩展局域网)、NVGRE(Network virtualization Generic Routing Encapsulation，网络虚拟化通用路由封装)等，其中，VXLAN采用MAC(Media Access Control，媒体接入控制)In UDP(User Datagram Protocol，用户数据报协议)封装方式，NVGRE采用MAC In GRE(Generic Routing Encapsulation，通用路由封装)封装方式。
NVO3网络的边缘设备称为网络虚拟边缘(Network Virtualization Edge，NVE)，NVE接入有租户终端系统(Tenants Terminal system，TES)，TES可简称为租户系统(Tenant system，TS)。NVE类似于BGP(Border Gateway Protocol，边界网关协议)/MPLS(Multiprotocol label switching，多协议标签交换)IP(Internet protocol，网际协议)VPN(Virtual private network，虚拟私有网络)网络中的PE(Provider Edge，运营商边缘)设备，TS类似于BGP/MPLS IP VPN网络中的CE(Customer Edge，用户边缘)设备。NVE可 以位于服务器或物理网络设备上，TS可以为服务器的虚拟机、或物理服务器、或防火墙、或负载均衡器等增值业务设备。
NVO3网络在数据中心(Data Center，DC)中得到了越来越广泛的应用。
传统电信网络中，广泛部署MPLS VPN网络，MPLS VPN包括L2(二层)VPN和L3(三层)VPN。用户有通过MPLS VPN网络访问数据中心的需求。而MPLS VPN网络和NVO3网络一般属于两个AS(Autonomous System，自治系统)域，通过MPLS VPN网络访问数据中心时，就涉及跨域互通的问题。
Option C是一种实现跨域网络互联的方式。Option C方式中，PE设备之间首先建立BGP LSP(Label Switch Path，标签交换路径)，然后再交换VPN路由。通过多跳的MP-EBGP直接在源端PE、宿端PE之间传递VPN路由信息。Option C方式中，AS域边缘的不需要在ASBR(Autonomous System Border Router，自治域边缘路由器)不需要保存VPN路由，将VPN路由的处理压力分散到PE上，扩展性较好。
但是，Option C方式中，需要在不同AS域的PE之间建立跨域的LSP，域内采用LDP(Label Distribution Protocol，标签分发协议)分发标签，域间采用单跳EBGP(External Border Gateway Protocol，外部边界网关协议)分发标签，不同AS域的PE通过多跳MP(Multiprotocol，多协议)-EBGP传播VPN路由信息；在进行报文转发时，域内使用三层标签转发，两个AS域的ASBR之间采用两层标签转发。由于相互通信的两个AS域都需要部署MPLS网络，因此，OPTION C方式只能实现MPLS VPN同构网络之间的互联。
发明内容
本发明实施例提供一种实现NVO3网络与MPLS网络之间通信的方法和装置，以实现NVO3网络和MPLS网络跨域通信。
本发明第一方面提供一种实现NVO3网络与MPLS网络之间通信的方法，第一自治系统AS部署NVO3网络，第二AS部署MPLS网络，所述方法包括：
所述NVO3网络中的自治域边缘路由器ASBR获得所述MPLS网络中的运营商边缘PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签，所述MPLS网络中的ASBR分配的MPLS标签将用作所述NVO3网络中的ASBR发往所述PE设备的MPLS封装的报文的外层标签；
所述NVO3网络中的ASBR从本地地址池中为所述MPLS标签分配IP地址，所述NVO3网络中的ASBR与所述NVO3网络中的网络虚拟边缘NVE通信，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
所述NVO3网络中的ASBR保存所述MPLS标签与所述分配的IP地址的对应关系；
所述NVO3网络中的ASBR向所述NVE发送路由信息，所述路由信息包括所述PE设备的标识和所述分配的IP地址，所述分配的IP地址用作所述TES发往所述CE设备的NVO3封装的报文的外层目的地址。
结合本发明第一方面，在第一种可能的实现方式中，所述NVO3网络中的ASBR获得所述MPLS网络中的PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签，包括：所述NVO3网络中的ASBR接收所述MPLS网络中的ASBR发送的BGP报文，所述MPLS网络中的ASBR发送的所述BGP报文携带所述PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签。
结合本发明第一方面或者第一方面的第一种可能的实现方式，在第二种可能的实现方式中，所述方法还包括：所述NVO3网络中的ASBR接收所述NVE发送的NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括虚拟网络标识VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签用于标识所述CE设备所属的VPN；所述NVO3网络中的ASBR生成报文，所述生成的报文携带两层MPLS标签，所述MPLS网络中的ASBR分配的所述MPLS标签作为所述两层MPLS标签中的外层标签，所述VN ID作为所述两层MPLS标签中的内层标签，所述生成的报文中不包括所述外层目的地址和所述外层源地址，所述生成的报文还携带所述NVO3封装的报文的载荷；所述NVO3网络中的ASBR向所述MPLS网络中的ASBR发送所述生成的报文。
结合本发明第一方面或者第一方面的第一种或第二种可能的实现方式，在第三种可能的实现方式中，所述方法还包括：所述NVO3网络中的ASBR为所述NVE的标识分配MPLS标签；所述NVO3网络中的ASBR向所述MPLS网络中的ASBR发送BGP报文，所述向所述MPLS网络中的ASBR发送的所述BGP 报文携带所述NVE的标识以及为所述NVE的标识分配的所述MPLS标签；所述NVO3网络中的ASBR保存所述NVE的标识与为所述NVE的标识分配的所述MPLS标签的对应关系。
结合本发明第一方面的第三种可能的实现方式，在第四种可能的实现方式中，所述方法还包括：所述NVO3网络中的ASBR接收所述MPLS网络中的ASBR转发的报文，所述MPLS网络中的ASBR转发的所述报文来自所述PE设备，所述MPLS网络中的ASBR转发的所述报文中的内层标签是所述TES所属的虚拟网络的VN ID，所述MPLS网络中的ASBR转发的报文中的外层标签是为所述NVE的标识分配的所述MPLS标签；所述NVO3网络中的ASBR生成NVO3封装的报文，所述生成的NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述生成的NVO3封装的报文的外层源地址是所述NVO3网络中的ASBR的IP地址，所述生成的NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID，所述生成的NVO3封装的报文还携带所述MPLS网络中的ASBR转发的所述报文的载荷；所述NVO3网络中的ASBR向所述NVE发送所述生成的NVO3封装的报文。
结合本发明第一方面或第一方面的第一种至第四种可能的实现方式中的任一种，在第五种可能的实现方式中，所述PE设备的标识是所述PE设备的IP地址。
本发明第二方面提供另一种实现NVO3网络与MPLS网络之间通信的方法，第一自治系统AS部署NVO3网络，第二AS部署MPLS网络，所述方法包括：
所述NVO3网络中的网络虚拟边缘NVE接收所述NVO3网络中的自治域边缘路由器ASBR发送的路由信息，所述路由信息包括IP地址和所述MPLS网络中的运营商边缘PE设备的标识的对应关系，所述IP地址是所述NVO3网络中的ASBR从本地地址池中为所述PE设备分配的，用作所述NVE连接的租户终端系统TES发往所述PE设备连接的用户边缘CE设备的NVO3封装的报文的外层目的地址，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
所述NVE接收所述PE设备通告的MPLS VPN标签和所述CE设备的标识，所述MPLS VPN标签用于标识所述CE设备所属的VPN；
所述NVE生成VPN路由信息，所述VPN路由信息包括所述CE设备的标识、 所述分配的IP地址和VN ID，所述VN ID是所述MPLS VPN标签，所述分配的IP地址作为NVO3封装的外层目的地址。
结合本发明第二方面，在第一种可能的实现方式中，所述方法还包括：所述NVE接收所述TES发往所述PE设备的报文，所述发往所述PE设备的报文携带所述CE设备的标识；所述NVE对所述TES发往所述PE设备的报文进行NVO3封装以生成NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签用于标识所述CE设备所属的VPN；所述NVE向所述NVO3网络中的ASBR发送所述NVO3封装的报文。
结合本发明第二方面或第二方面的第一种可能的实现方式，在第二种可能的实现方式中，所述方法还包括：所述NVE向所述PE设备发送VPN路由，所述VPN路由中携带MPLS VPN标签和所述TES的标识，所述VPN路由中携带的所述MPLS VPN标签是所述TES所属的虚拟网络的VN ID。
结合本发明第二方面的第二种可能的实现方式，在第三种可能的实现方式中，所述方法还包括：所述NVE接收所述NVO3网络中的ASBR发送的NVO3封装的报文，所述NVE接收的所述NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述NVE接收的所述NVO3封装的报文的外层源地址是所述NVO3网络中的ASBR的IP地址，所述NVE接收的所述NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID；所述NVE对接收到的所述NVO3封装的报文解封装，根据所述TES所属的虚拟网络的VN ID将解封装后的报文发送给所述NVO3网络中的TES。
结合本发明第二方面或第二方面的第一种至第三种可能的实现方式中的任一种，在第四种可能的实现方式中，所述PE设备的标识是所述PE设备的IP地址。
本发明第三方面提供一种自治域边缘路由器ASBR，第一自治系统AS部署三层网络虚拟化NVO3网络，第二自治系统AS部署多协议标签交换MPLS网络，所述ASBR是所述第一AS中的边缘路由器BR，所述ASBR包括：
接收模块，用于获得所述MPLS网络中的运营商边缘PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签，所述MPLS网络中的ASBR分配的 MPLS标签将用作所述NVO3网络中的所述ASBR发往所述PE设备的MPLS封装的报文的外层标签；
分配模块，用于从本地地址池中为所述MPLS标签分配IP地址，所述NVO3网络中的ASBR与所述NVO3网络中的网络虚拟边缘NVE通信，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
存储模块，用于保存所述MPLS标签与所述分配的IP地址的对应关系；
发送模块，用于向所述NVE发送路由信息，所述路由信息包括所述PE设备的标识和所述分配的IP地址，所述分配的IP地址用作所述TES发往所述CE设备的NVO3封装的报文的外层目的地址。
结合本发明第三方面，在第一种可能的实现方式中，所述接收模块，具体用于接收所述MPLS网络中的ASBR发送的BGP报文，所述MPLS网络中的ASBR发送的所述BGP报文携带所述PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签。
结合本发明第三方面或第三方面的第一种可能的实现方式，在第二种可能的实现方式中，所述接收模块，还用于接收所述NVE发送的NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括虚拟网络标识VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN；所述ASBR还包括生成模块，用于生成报文，所述生成的报文携带两层MPLS标签，所述MPLS网络中的ASBR分配的所述MPLS标签作为所述两层MPLS标签中的外层标签，所述VN ID作为所述两层MPLS标签中的内层标签，所述生成的报文中不包括所述外层目的地址和所述外层源地址，所述生成的报文还携带所述NVO3封装的报文的载荷；所述发送模块，还用于向所述MPLS网络中的ASBR发送所述生成的报文。
结合本发明第三方面或第三方面的第一种或第二种可能的实现方式，在第三种可能的实现方式中，所述分配模块，还用于为所述NVE的标识分配MPLS标签；所述发送模块，还用于向所述MPLS网络中的ASBR发送BGP报文，所述向所述MPLS网络中的ASBR发送的所述BGP报文携带所述NVE的标识以 及为所述NVE的标识分配的所述MPLS标签；所述存储模块，还用于保存所述NVE的标识与为所述NVE的标识分配的所述MPLS标签的对应关系。
结合本发明第三方面或第三方面的第三种可能的实现方式，在第四种可能的实现方式中，所述接收模块，还用于接收所述MPLS网络中的ASBR转发的报文，所述MPLS网络中的ASBR转发的所述报文来自所述PE设备，所述MPLS网络中的ASBR转发的所述报文中的内层标签是所述TES所属的虚拟网络的VN ID，所述MPLS网络中的ASBR转发的所述报文中的外层标签是为所述NVE的标识分配的所述MPLS标签；生成模块，还用于生成NVO3封装的报文，所述生成的NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述生成的NVO3封装的报文的外层源地址是所述NVO3网络中的ASBR的IP地址，所述生成的NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID，所述生成的NVO3封装的报文还携带所述MPLS网络中的ASBR转发的所述报文的载荷；所述发送模块，还用于向所述NVE发送所述生成的NVO3封装的报文。
本发明第四方面提供一种网络虚拟边缘NVE，其特征在于，第一自治系统AS部署三层网络虚拟化NVO3网络，第二自治系统AS部署多协议标签交换MPLS网络，所述NVE用在第一AS中，所述NVE包括：接收模块，用于接收所述NVO3网络中的自治域边缘路由器ASBR发送的路由信息，所述路由信息包括IP地址和所述MPLS网络中的运营商边缘PE设备的标识的对应关系，所述IP地址是所述NVO3网络中的ASBR从本地地址池中为所述PE设备分配的，用作所述NVE连接的租户终端系统TES发往所述PE设备连接的用户边缘CE设备的NVO3封装的报文的外层目的地址，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；所述接收模块，还用于接收所述PE设备通告的MPLS VPN标签和所述CE设备的标识，所述MPLS VPN标签用于标识所述CE设备所属的VPN；路由模块，用于生成VPN路由信息，所述VPN路由信息包括所述CE设备的标识、所述分配的IP地址和VN ID，所述VN ID是所述MPLS VPN标签，所述分配的IP地址作为NVO3封装的外层目的地址。
结合本发明第四方面，在第一种可能的实现方式中，所述接收模块，还用于接收所述TES发往所述PE设备的报文，所述发往所述PE设备的报文携带所述CE设备的标识；生成模块，用于对所述TES发往所述PE设备的报文进行 NVO3封装以生成NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签用于标识所述CE设备所属的VPN；发送模块，用于向所述NVO3网络中的ASBR发送所述NVO3封装的报文。
结合本发明第四方面或第四方面的第一种可能的实现方式，在第二种可能的实现方式中，所述NVE还包括：路由发送模块，用于向所述PE设备发送VPN路由，所述VPN路由中携带MPLS VPN标签和所述TES的标识，所述VPN路由中携带的所述MPLS VPN标签是所述TES所属的虚拟网络的VN ID。
结合本发明第四方面或第四方面的第二种可能的实现方式，在第三种可能的实现方式中，所述接收模块，还用于接收所述NVO3网络中的ASBR发送的NVO3封装的报文，所述NVE接收的所述NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述NVE接收的所述NVO3封装的报文的外层源地址是所述NVO3网络中的ASBR的IP地址，所述NVE接收的所述NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID；所述发送模块，还用于对接收到的所述NVO3封装的报文解封装，根据所述TES所属的虚拟网络的VN ID将解封装后的报文发送给所述NVO3网络中的TES。
本发明第五方面提供一种计算机网络设备，其特征在于，所述计算机设备包括处理器、存储器、总线和通信接口；所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算机设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述计算机设备执行如本发明第一方面所述的实现NVO3网络与MPLS网络之间通信的方法，或者如本发明第二方面所述的实现NVO3网络与MPLS网络之间通信的方法。
由上可见，本发明实施例通过采用上述技术方案，使得：
相对于传统的OPTION C跨域方案，当NVO3网络中的ASBR接收到MPLS网络中的ASBR为MPLS网络中的PE设备分配的MPLS标签时，NVO3网络中的ASBR不再为该PE设备继续分配MPLS标签，而是从本地地址池中分配一个IP地址来代替MPLS标签，生成IP地址和MPLS标签的对应关系(即交换表项)，用于从NVO3网络到MPLS网络方向流量报文的转发，即：将MPLS网络中的 ASBR分配的MPLS标签用作所述NVO3网络中的ASBR向所述PE设备发送的报文的外层标签，将所述分配的IP地址用作所述MPLS网络中的TES发往所述MPLS网络中的CE设备的NVO3封装的报文的外层目的地址。
从而取得了以下技术效果：
通过在NVO3网络的ASBR上进行NVO3封装与标签封装的转换，实现NVO3网络与MPLS网络之间的跨域通信，解决了一般NVO3网络设备不支持标签转发，不能采用传统OPTION C跨域方案与MPLS网络通信的问题。
并且，本发明实施例的方案不需要在ASBR上为每个VPN配置VRF(VPN Routing and Forwarding，VPN路由转发表)和子接口，ASBR也不需要保存和维护VPN路由，只需要保存和维护到达PE/NVE路由以及少量的MPLS标签和NVO3封装转换表项，因此，本发明方案能够减轻ASBR的负担，具有较好的扩展性。
附图说明
为了更清楚地说明本发明实施例技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1是本发明实施例一提供的一种实现NVO3网络与MPLS网络之间通信的方法的流程图；
图2是本发明实施例二提供的一种实现NVO3网络与MPLS网络之间通信的方法的流程图；
图3a-3d，是本发明实施例三中的网络架构图及通信示意图；
图4a-4b是本发明实施例四中的网络架构示意图；
图5a是本发明实施例五提供的一种ASBR的结构示意图；
图5b是本发明实施例五提供的另一种ASBR的结构示意图；
图6a是本发明实施例六提供的一种NVE的结构示意图；
图6b是本发明实施例六提供的另一种NVE的结构示意图；
图7是本发明实施例提供的一种计算机设备的逻辑结构示意图。
具体实施方式
本发明实施例提供本发明实施例提供一种实现NVO3网络与MPLS网络之间通信的方法和装置，以实现NVO3网络和MPLS网络跨域通信。
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
下面通过具体实施例，分别进行详细的说明。
实施例一
请参考图1，本发明实施例提供一种实现NVO3网络与MPLS网络之间通信的方法，该方法用于NVO3网络和MPLS网络之间的通信，NVO3网络部署于第一自治系统(第一AS，AS1)，MPLS网络部署于第二自治系统(第二AS，AS2)；所述方法可包括：
110、所述NVO3网络中的ASBR(Autonomous System Border Router，自治域边缘路由器)获得所述MPLS网络中的PE(Provider Edge，运营商边缘路由器)设备的标识和所述MPLS网络中的ASBR分配的MPLS标签，所述MPLS网络中的ASBR分配的MPLS标签将用作所述NVO3网络中的所述ASBR发往所述PE设备的MPLS封装的报文的外层标签；
120、所述NVO3网络中的ASBR从本地地址池中为所述MPLS标签分配IP地址，所述NVO3网络中的ASBR与所述NVO3网络中的NVE(Network Virtualization Edge，网络虚拟边缘)通信，所述NVE连接的TES(Tenants Terminal system，租户终端系统)与所述PE设备连接的CE(Customer Edge，用户边缘)设备属于同一VPN(virtual private network，虚拟私有网络)；
130、所述NVO3网络中的ASBR保存所述MPLS标签与所述分配的IP地址的对应关系；
140、所述NVO3网络中的ASBR向所述NVE发送路由信息，所述路由信息包括所述PE设备的标识(PE自身的IP地址)和所述分配的IP地址，所述分配 的IP地址用作所述TES发往所述CE设备的NVO3封装报文的外层目的地址。
由上可见，本发明实施例中，对比传统MPLS Option C跨域互联方案，当NVO3网络中的ASBR接收到MPLS网络ASBR为该PE设备分配的MPLS标签时，NVO3网络中的ASBR不再为该PE设备继续分配MPLS标签，而是从本地地址池中分配一个IP地址来代替MPLS标签，生成IP地址和MPLS标签的交换表项，用于从NVO3网络到MPLS网络方向流量报文的转发，即：将MPLS网络中的ASBR分配的MPLS标签用作所述NVO3网络中的所述ASBR向所述PE设备发送的报文的外层标签，将所述分配的IP地址用作所述MPLS网络中的TES发往所述MPLS网络中的CE设备的NVO3封装的报文的外层目的地址。可见，在NVO3网络和MPLS网络之间的VPN跨域互联通信中，NVO3网络中以NVO3封装取代传统MPLS Option C跨域中的标签封装(即MPLS封装)。
因此，本发明技术方案取得了以下技术效果：
通过在NVO3网络的ASBR上进行NVO3封装与标签封装的转换，实现了NVO3网络与MPLS网络之间的跨域通信，解决了一般NVO3网络设备不支持标签转发，不能采用传统OPTION C跨域方案与MPLS网络通信的问题；
并且，本发明实施例的方案不需要在ASBR上为每个VPN配置VRF和子接口，ASBR也不需要保存和维护VPN路由，只需要保存和维护到达PE/NVE路由以及少量的MPLS标签和NVO3封装转换表项,因此，本发明方案能够减轻ASBR的负担，具有较好的扩展性。
实施例二
请参考图2，本发明实施例提供另一种实现NVO3网络与MPLS网络之间通信的方法，该方法用于NVO3网络和MPLS网络之间的通信，NVO3网络部署于第一自治系统(第一AS，AS1)，MPLS网络部署于第二自治系统(第二AS，AS2)；所述方法可包括：
210、所述NVO3网络中的NVE接收所述NVO3网络中的ASBR发送的路由信息，所述路由信息包括IP地址和所述MPLS网络中的PE设备的标识的对应关系，所述IP地址是所述NVO3网络中的ASBR从本地地址池中为所述PE设备分配的，用作所述NVE连接的租户终端系统TES发往所述PE设备连接的用户边缘CE设备的NVO3封装的报文的外层目的地址，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
220、所述NVE接收所述PE设备通告的MPLS VPN标签和所述CE设备的标识，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN；
230、所述NVE生成VPN路由信息，所述VPN路由信息包括所述CE设备的标识、所述分配的IP地址和VN ID，所述VN ID是所述MPLS VPN标签，所述分配的IP地址作为NVO3封装的外层目的地址。
由上可见，本发明实施例中，对比传统MPLS Option C跨域互联方案，当NVO3网络中的ASBR接收到MPLS网络中的ASBR为该PE设备分配的MPLS标签时，NVO3网络中的ASBR不再为该PE设备继续分配MPLS标签，而是从本地地址池中分配一个IP地址来代替MPLS标签，生成IP地址和MPLS标签的交换表项，将包括IP地址和MPLS标签的对应关系的路由信息发送给NVO3网络中的NVE，所述NVE还能够获取MPLS网络中的PE设备通告的MPLS VPN标签和所述CE设备的标识，从而NVE可以生成包括所述CE设备的标识、所述分配的IP地址和VN ID(即所述MPLS VPN标签)的VPN路由信息，NVE可以根据该VPN路由信息将NVO3网络中的TES发往MPLS网络的CE设备的报文进行NVO3封装；也就是说，在NVO3网络和MPLS网络之间的VPN跨域互联通信中，NVO3网络中以NVO3封装取代传统MPLS Option C跨域中的标签封装。
因此，本发明技术方案取得了以下技术效果：
通过在NVO3网络的ASBR上进行NVO3封装与标签封装的转换，实现了NVO3网络与MPLS网络之间的跨域通信，解决了一般NVO3网络设备不支持标签转发，不能采用传统OPTION C跨域方案与MPLS网络通信的问题；
并且，本发明方案不需要在ASBR上为每个VPN配置VRF和子接口，ASBR也不需要保存和维护VPN路由，只需要保存和维护到达PE/NVE路由以及少量的MPLS标签和NVO3封装转换表项,因此，本发明方案能够减轻ASBR的负担，具有较好的扩展性。
实施例三
NVO3网络与MPLS网络之间通信的方法可以分为控制面的方案和数据面的方案。并且，数据面可以包括两个方向，即，从NVO3网络到MPLS网络的上行方向，以及，从MPLS网络到NVO3网络的下行方向。
本实施例中，结合具体的网络架构图，分别从控制面和数据面以及不同的方向，对本发明技术方案进行具体说明。
请参考图3a-3d，是本实施例中的网络架构以及通信示意图，网络架构包括：第一AS(AS1)和第二AS(AS2)，第一AS部署NVO3网络，第二AS部署MPLS网络。NVO3网络的ASBR(图中用ASBR1表示)与NVE通信，NVE连接例如两个TES即TES1和TES2。MPLS网络的ASBR(图中用ASBR2表示)与PE设备通信，PE设备连接例如两个CE设备即CE1和CE2。其中，TES1和CE1属于同一个VPN，用VPN1表示；TES2和CE2属于同一个VPN，用VPN2表示。
设定NVO3网络内NVE和ASBR1之间建IBGP(Interior Border Gateway Protocol，内部BGP协议)会话交换路由信息。MPLS网络的ASBR2和PE2之间也建立IBGP会话交换路由信息。ASBR1和ASBR2之间建EBGP(External Border Gateway Protocol，外部边界网关协议)会话交换路由信息。NVE和PE之间直接建立MP-EBGP会话交换VPN路由并分配和相互发布VPN标签信息。MPLS网络内可部署LDP(Label Distribution Protocol，标签分发协议)协议为IGP(Interior Gateway Protocol，内部网关协议)路由分发标签。
A1、针对上行方向报文的控制面的方案可以包括：
A101、MPLS网络的各节点设备依次为PE分配MPLS标签(即BGP MPLS公网标签)，并通告给下一级。
例如，请参考图3a，假设PE(即图中的PE2)的IP地址是20.1.1.1，假设ASBR2的IP地址是200.1.1.1，假设ASBR1的IP地址是100.1.1.1，假设NVE的IP地址是10.1.1.1。假设PE为20.1.1.1分配MPLS标签50，通过BGP标签路由通告给ASBR2；ASBR2为PE的IP地址20.1.1.1分配MPLS标签150，并通过BGP标签路由通告给ASBR1。
A102、所述NVO3网络的ASBR(即ASBR1)获得所述MPLS网络中的PE设备的标识和所述MPLS网络中的ASBR(即ASBR2)分配的MPLS标签，从本地地址池中为所述MPLS标签分配IP地址。本发明一些实施例中，该分配步骤具体可以包括：所述ASBR1接收所述MPLS网络中的ASBR2发送的BGP报文，所述BGP报文携带所述PE设备的标识和所述ASBR2分配的MPLS标签。所述MPLS网络中的ASBR(ASBR2)分配的MPLS标签将用作所述NVO3网络中的所述ASBR(ASBR1)发往所述PE设备的MPLS封装的报文的外层标签。其中，所说的PE设备的标识具体可以是PE设备的IP地址。并且，所述ASBR1还 可以保存所述ASBR2分配的MPLS标签与所述ASBR1分配的IP地址的对应关系，生成所述ASBR1分配分配的IP地址和所述ASBR2分配的MPLS标签的出方向的转发表项(从NVO3网络侧到MPLS网络侧，即上行方向)。
请参考图3a，假设ASBR1为20.1.1.1分配的IP地址是30.1.1.1。
A103、ASBR1向NVE(即图中的NVE1)发送路由信息，所述路由信息包括所述PE设备的标识和所述分配的IP地址及其对应关系。所述分配的IP地址用作所述TES发往所述CE设备的NVO3封装的报文的外层目的地址。可选的，关于多个PE设备的路由信息可以携带在一个路由消息中。
请参考图3a，ASBR1可以通过BGP标签路由将路由信息通告给NVE，路由信息中包括PE的IP地址20.1.1.1，以及ASBR1分配的IP地址30.1.1.1(例如具体可以是30.1.1.1/24)。
ASBR1向NVE可以通过定义一种新的路由属性类型或BGP扩展团队属性或新的NLRI(network layer reachability information，网络层可通达性信息)的类型，或者使用已定义的IPv4Address Specific Extended Community或Opaque Extended Community两个属性中的一个来携带分配给PE2的本地的IP地址，该本地的IP地址可以是IPv4地址，也可以是IPv6地址。新类型的NLRI可以由一个或多个<length,NVO3Tunnel IP,prefix>三元组组成，在MP_REACH_NLRI或MP_UNREACH_NLRI属性中携带，其中length表示三元组中NVO3Tunnel IP和prefix的长度，NVO3Tunnel IP为所述的分配给PE的本地IP地址，prefix为PE标识对应的IP地址前缀。
A104、PE为CE1通告的标识，例如CE1的IP地址前缀或者MAC地址，分配MPLS VPN标签，所述MPLS VPN标签用于标识所述CE1设备所属的VPN(即VPN1)，并将分配的MPLS VPN标签和CE1通告的标识，例如CE1的IP地址前缀或者MAC地址，通告给NVE。所述NVE接收所述PE设备通告的MPLS VPN标签和所述CE通告过来的CE设备的标识(例如CE1的IP地址前缀或者MAC地址)，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN，或者所述PE设备连接所述CE设备的接口，或者所述CE设备的标识。然后，NVE可以生成VPN路由信息，即：将PE通告过来的所述CE设备的标识，例如所述CE设备的IP地址前缀或者MAC地址，导入本地VPN路由转发表中，所述VPN路由信息包括所述CE设备的标识(例如所述CE设备的IP地址前缀或者MAC地 址)、所述分配的IP地址和VN ID，所述VN ID是所述MPLS VPN标签，所述分配的IP地址作为NVO3封装的外层目的地址。
具体的，所述NVE可以根据所述PE的标识迭代(iterate)出所述CE设备IP地址前缀或者MAC地址的NVO3隧道的外层目的地址(所述IP地址)，将MPLS VPN标签作为NVO3隧道的VN ID，生成VPN本地路由转发表，NVO3隧道的目的是ASBR1从本地地址池中分配的IP地址，源地址为NVE的IP地址，VNID为PE通告的MPLS VPN标签。
请参考图3a，假设PE分配的用于标识VPN1的MPLS VPN标签是2000。
A2、针对上行方向报文的数据面的方案可以包括：
A201、NVE接收TES1发往CE设备的报文，所述发往所述PE设备的报文携带所述CE设备的标识，查找VPN路由转发表，然后进行NVO3封装，生成NVO3封装的报文。
请参考图3b，图中用报文载荷表示TES1发往CE设备的报文。NVE对所述报文载荷进行NVO3封装，生成NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址(例如30.1.1.1)，所述NVO3封装的报文的外层源地址是所述NVE的IP地址(例如10.1.1.1)，所述NVO3封装的报文还包括VN ID，所述VN ID是所述PE通告的MPLS VPN标签(例如2000)，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN(即VPN1)。NVE根据VN ID查找VPN路由转发表，将所述NVO3封装的报文发送给ASBR1。
A202、ASBR1接收所述NVE发送的NVO3封装的报文，生成标签封装(即MPLS封装)的报文。
所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN。
ASBR1对NVO3封装的报文解封装，根据所述分配的IP地址(例如30.1.1.1)，查找对应的MPLS标签(即ASBR2分配的MPLS标签，例如150)。对解封装得到的报文载荷进行标签封装(即MPLS封装)，得到标签封装的报文，所述标签封装的报文携带两层MPLS标签，其中，所述MPLS网络中的 ASBR2分配的所述MPLS标签(例如150)作为所述两层MPLS标签中的外层标签，所述VN ID(例如2000)作为所述两层MPLS标签中的内层标签，所述生成的标签封装的报文中不包括所述外层目的地址和所述外层源地址，所述生成的标签封装的报文还携带所述NVO3封装的报文的载荷。ASBR1根据ASBR2分配的所述MPLS标签(例如150)的指示，将生成的标签封装的报文发送给ASBR2。
A203、ASBR2接收ASBR1发送的标签封装的报文，转换成为三层标签封装的报文发送给PE，PE去除所有标签封装，将报文载荷发送给CE1。
三层标签封装的报文包括三层标签，最外层标签是LDP标签，中间层标签是PE分配的MPLS标签(例如50，即BGP MPLS公网标签)，内层标签是VN ID(例如2000)。从ASBR2到CE1的标签转发方案，可参考传统的Option C方案，本文不再详细赘述。
B1、针对下行方向报文的控制面的方案可以包括：
B101、所述NVO3网络的ASBR1为所述NVO3网络中的每个NVE的标识分配MPLS标签(具体是BGP MPLS公网标签)，并将ASBR1为所述NVE的标识分配的MPLS标签和对应的NVE的标识携带在BGP报文中发送给所述MPLS网络中的ASBR2。所述ASBR1还可以保存所述NVE的标识与为所述NVE的标识分配的所述MPLS标签的对应关系，生成NVE的标识与所述ASBR1为所述NVE的标识分配的MPLS标签对应的转发表项(从MPLS网络侧到达NVO3网络侧)。所说的NVE的标识具体可以是NVE的IP地址，例如IPv4地址或者IPv6地址。
例如，请参考图3c，本文假设PE的IP地址是20.1.1.1，假设ASBR2的IP地址是200.1.1.1，假设ASBR1的IP地址是100.1.1.1，假设NVE的IP地址是10.1.1.1。假设ASBR1为NVE的标识10.1.1.1分配的第二MPLS标签是100，并通过BGP标签路由通告给ASBR2。
B102、ASBR2接收ASBR1发送的BGP报文，并分配MPLS标签。
例如，请参考图3c，假设ASBR2为ASBR1的标识10.1.1.1分配MPLS标签200，并通过BGP标签路由通告给PE2。
B103、所述NVE向所述PE设备发送VPN路由，所述VPN路由中携带TES的标识和MPLS VPN标签，所述VPN路由中携带的所述MPLS VPN标签是所述 TES所属的NVO3网络的标识VN ID。优选的，为了保证VN ID能够正确转换为MPLS VPN标签，VN ID长度不能超过20比特(bit)，即用于所述NVO3网络和所述MPLS网络互通的VN ID的值不能大于2的20次方(1，048，576)。可选的，所述TES的标识可以是所述TES的IP地址前缀或MAC地址。所述PE设备可以在收到VPN路由后，将其中携带的所述TES的IP地址前缀或者MAC地址导入本地L2/L3VPN转发表。
例如，请参考图3c，NVE为TES1的IP地址分配MPLS VPN标签1000，该MPLS VPN标签即是NVO3虚拟网络的VN ID。
B2、针对下行方向报文的数据面的方案可以包括：
B201、PE接收CE1发往TES1的报文，对CE1发往TES1的报文进行三层标签封装后，发给ASBR2，ASBR2转换为两层标签封装，生成两层标签封装的报文，发送给ASBR1。
例如，请参考图3d，PE生成的标签封装的报文包括三层标签，最外层标签是LDP标签，中间层标签是ASBR2分配的MPLS标签(例如200，即BGP MPLS公网标签)，内层标签是所述TES1所属的虚拟网络的VN ID(例如1000)。ASBR2生成的标签封装的报文包括两层标签，内层标签是所述TES1所属的虚拟网络的VN ID(例如1000)，外层标签是ASBR1为所述NVE的标识分配的所述MPLS标签(例如100)。需要说明的是，从CE1到ASBR2的标签转发方案，可参考传统的Option C方案，本文不再详细赘述。
B202、ASBR1接收ASBR2发送的标签封装的报文，解封装得到报文载荷，对报文载荷进行NVO3封装，生成NVO3封装的报文。
所述MPLS网络中的ASBR2转发的所述报文中的内层标签是所述TES所属的虚拟网络的VN ID(例如1000)，所述MPLS网络中的ASBR2转发的报文中的外层标签是为所述NVE的标识分配的所述MPLS标签(例如100)。
所述NVO3封装的报文的外层目的地址是所述NVE的IP地址(例如10.1.1.1)，外层源地址是所述NVO3网络中的所述ASBR1的IP地址(例如100.1.1.1)，所述NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID(例如1000)，当然，所述NVO3封装的报文还携带所述所述MPLS网络中的所述ASBR1转发的报文的载荷。所述ASBR1向所述NVE发送所述生成的NVO3 封装的报文。
B203、所述NVE接收所述ASBR1发送的NVO3封装的报文，对所述NVO3封装的报文解封装，根据所述TES所属的虚拟网络的VN ID将解封装后的报文发送给所述NVO3网络中的TES。
例如图3d所示，NVE收到ASBR1发送的NVO3封装的报文后，可根据VN ID(例如1000)查找本地VRF，确定接收端TES1，将报文解封装，将报文载荷发送给TES1。
以上，结合作为示例的网络架构图3a-3d，对本发明实施例技术方案进行了详细的说明，但是，需要理解的是，图3a-3d只是本发明的一些优选方式，并不用于限制本发明。
由上可见：
本发明一些实施例中，可以在NVO3网络的ASBR1上部署本地地址池。该本地地址池的地址资源可以仅在所述NVO3网络中生效，而不向外部网络发布对应的路由，即，该本地IP地址池可以使用私有地址网段的IP地址。但需要理解的是，该本地IP地址池也可以使用公网地址网段的IP地址。所述ASBR1可以借助于BGP/IGP协议的分发扩散，向NVO3网络内部的路由邻居分发扩散该本地地址池对应的IP前缀路由，使得NVO3网络内部的各网络设备均获知该本地地址池对应的IP前缀路由。
本发明一些实施例中，所述ASBR1可通过本地命令配置，NMS(Network Management System，网络管理系统)配置，或动态协议发现本AS域的NVE,并为本AS域的NVE分配MPLS标签。所述的CE设备与NVO3网络中的TES属于同一VPN，可以理解为，CE和TES可以通过查找二层MAC转发表项或三层IP路由表项实现互通，如果通过MAC实现互通则为L2VPN，如果通过IP实现互通,则为L3VPN。所述ASBR1可保存为该PE分配的本地的IP地址和该PE的标识的对应关系，或者说关联关系(association)。
本发明一些实施例中，所述NVE获得所述ASBR1发送的、携带PE的标识和为PE分配的本地的IP地址的对应关系的路由信息后，可关联该PE的标识(例如公网IP地址)和分配的IP地址，这样，在所述NVO3网络的NVE对所述NVO3网络中的租户终端系统发往所述PE的报文进行NVO3封装时，可以用为所述PE分配的本地的IP地址作为NVO3封装的外层IP头的目的地址。
本发明一些实施例中，参考了传统MPLS Option C跨域互联方案，由所述NVE和所述PE直接建立MP-EBGP会话，实现在所述NVE或者GW与所述远端PE之间交换VPN信息，包括：为通过本地配置或BGP AD机制发现的对端VPN实例分配MPLS VPN标签，并向所述PE分发扩散该MPLS VPN标签和L2或L3路由信息，以及，接收所述PE分发的MPLS VPN标签和L2(MAC)或L3(IP)路由信息。
本发明一些实施例中，所述NVE从用户侧接口收到NVO3网络内TES到MPLS网络内CE设备的流量报文时，可根据报文的目的标识查询所述VPN的转发信息表，获得PE的信息，对报文进行NVO3封装，其中：NVO3封装的外层IP头的目的地址填充为PE分配的本地的IP地址，外层IP头的源地址填充所述NVE的IP地址，VN ID填充为所述PE通告的MPLS VPN标签。
本发明一些实施例中，所述NVO3网络的网络节点根据所述NVO3封装的报文的外层IP头的目的地址进行转发，所述ASBR1收到所述NVO3封装的报文后，根据外层IP头的目的地址查找路由获得出口PE的公网IP地址对应路由迭代得到的下一跳信息，包括所述PE的IP地址对应的MPLS标签。
本发明一些实施例中，所述ASBR1可接收MPLS网络内CE设备到NVO3网络内TES的标签封装的报文；该报文应封装了2层标签：外层标签为MPLS标签(对应到出口NVE的路由)，内层标签为MPLS VPN标签。然后，所述ASBR1可将所述经两层标签封装的报文转换为NVO3封装的报文，发送给所述NVE。
本发明一些实施例中，所述NVE从网络侧接口收到所述ASBR1发送的经NVO3封装的报文后，可直接剥掉NVO3封装，根据NVO3封装中的VN ID，将报文载荷发往NVO3网络中的TES。
由上可见，本发明实施例的技术方案相对于传统的OPTION C跨域方案，当NVO3网络中的ASBR接收到MPLS网络中的ASBR为MPLS网络中的PE设备分配的MPLS标签时，NVO3网络中的ASBR不再为该PE设备继续分配MPLS标签，而是从本地地址池中分配一个IP地址来代替MPLS标签，生成IP地址和MPLS标签的对应关系(即交换表项)，用于从NVO3网络到MPLS网络方向流量的转发。另外，NVO3网络的ASBR为每个NVE分配MPLS标签，将该标签和NVE标识的对应关系通告给MPLS网络的ASBR，并且生成MPLS标签和 NVE标识的交换表项，用于从MPLS网络到NVO3网络方向的流量转发。NVO3网络的ASBR在进行报文转发时候,需要将NVO3数据封装中的VN ID和MPLS封装内层MPLS VPN标签进行映射，即报文从NVO3向MPLS网络传送时候，将VN ID数值拷贝到MPLS的内层标签。报文从MPLS网络向NVO3网络传送时候，将内层MPLS VPN标签拷贝到NVO3数据封装的VN ID。
从而，本发明实施例技术方案取得了以下技术效果：
本发明实施例技术方案不需要在ASBR上为每个VPN配置VRF和子接口，ASBR也不需要保存和维护VPN路由，只需要保存和维护到达PE/NVE路由以及少量的MPLS标签和NVO3封装转换表项，因此，本发明方案能够减轻ASBR的负担,具有较好的扩展性。
并且，本发明实施例技术方案可以通过在NVO3网络的ASBR上进行NVO3封装与标签封装的转换，实现NVO3网络与MPLS网络之间的跨域通信，解决了一般NVO3网络设备不支持标签转发，不能采用传统OPTION C跨域方案与MPLS网络通信的问题。
实施例四
本实施例中，结合具体的网络架构图4a和4b，分别从控制面和数据面以及不同的方向，对本发明技术方案进行具体说明。
图4a和4b是本实施例的网络架构图，与实施例三中图3a-3d所示的网络结构图的区别在于：在NVO3网络中增加了一个集中控制器(Network ation Authority，NVA)，部署NVO3网络的AS1(即DC1)可以通过NVAController进行集中式控制。
NVA通过OpenFlow协议(也可以通过OVSDB(Open vSwtich Database)等协议下发路由转发表项。在NVO3网络内部可以用VXLAN(Virtual eXtensible Local Area Network，虚拟可扩展局域网)封装转发租户数据报文。NVA上保存所有TES，所属租户以及连接的NVE的信息。
NVA和AS2中的ASBR2之间建EBGP会话交换公网路由信息。NVA上配置本地地址池，对于NVO3网络到MPLS网络方向，NVA为每个NVE分配MPLS标签，并将NVE标识和MPLS标签对应关系通告给MPLS网络的ASBR，对于MPLS网络到NVO3网络方向，NVA为每个PE标识对应的MPLS标签分配本地IP地址。NVA和PE2之间建MP-EBGP会话交换VPN路由并分配以及发布 MPLS VPN标签信息。ASBR2和PE2之间仍建IBGP会话交换路由信息。AS2内部部署LDP协议为IGP路由分发标签。
E1、针对上行方向报文的控制面的方案可以包括：
E101、MPLS网络的各节点设备依次为PE分配MPLS标签(即BGP MPLS公网标签)，并通告给下一级。
本步骤与图3a实施例中的步骤A101相同。例如，请参考图4a，假设PE的IP地址是20.1.1.1，假设ASBR2的IP地址是200.1.1.1，假设ASBR1的IP地址是100.1.1.1，假设NVE的IP地址是10.1.1.1。假设PE为20.1.1.1分配MPLS标签50，通过BGP标签路由通告给ASBR2；ASBR2为PE的IP地址20.1.1.1分配MPLS标签150，并通过BGP标签路由通告给NVA。
E102、NVA从本地地址池中为所述MPLS网络中的PE分配IP地址，给ASBR1下发MPLS标签和分配的IP地址的对应关系，用于NVO3封装报文到MPLS报文转换。以及，NVA给NVE下发CE2通告过来的路由信息和对应NVO3封装表项。具体的，NVA向NVE1下发路由信息，所述路由信息包括所述PE设备的标识和所述分配的IP地址的对应关系，用于做NVO3封装。
本实施例中，由NVA代替ASBR1的功能，包括：从本地地址池中为所述MPLS网络中的PE分配IP地址。该分配步骤具体可以包括：所述NVA接收所述MPLS网络中的ASBR2发送的第一BGP报文，所述第一BGP报文携带所述PE设备的标识和所述ASBR2分配的第一MPLS标签，所述第一MPLS标签将用作所述ASBR1向所述PE设备发送的报文的外层标签；NVA为所述第一MPLS标签分配IP地址。其中，所说的PE设备的标识具体可以是PE设备的IP地址。
请参考图4a，假设NVA为20.1.1.1分配的IP地址是30.1.1.1。NVA可以将路由信息通告给NVE，路由信息中包括PE的IP地址20.1.1.1，以及NVA分配的IP地址30.1.1.1。
E103、PE为CE1通告的标识例如IP地址前缀或者MAC地址分配MPLS VPN标签，所述MPLS VPN标签用于标识所述CE1设备所属的VPN(即VPN1)，并将分配的MPLS VPN标签(以及，还可以包括PE通告过来的IP地址前缀或者MAC地址)通告给NVA，由NVA下发给NVE。NVE可以将NVA下发的PE通告过来的IP地址前缀或者MAC地址导入本地VPN路由转发表中。
请参考图3a，假设PE分配的用于标识VPN1的MPLS VPN标签是2000。
E2、针对上行方向报文的数据面的方案可以包括：
该上行方向报文的数据面的方案，与图3b及其对应的实施例三的步骤A2相同，详细内容请参考前文，此处不再详细赘述。
F1、针对下行方向报文的控制面的方案可以包括：
F101、所述NVO3网络的NVA为所述NVO3网络中的每个NVE的标识分配MPLS标签(具体是BGP MPLS公网标签)，并将分配的MPLS标签和对应的NVE的标识携带在BGP报文中发送给所述MPLS网络中的ASBR2。所说的NVE的标识具体可以是NVE的IP地址，例如IPv4或者IPv6。
NVA还将分配的MPLS标签和对应的NVE的标识对应的映射表项下发给ASBR1，用于MPLS报文到NVO3封装报文转换。
例如，请参考图4b，本文假设PE的IP地址是20.1.1.1，假设ASBR2的IP地址是200.1.1.1，假设ASBR1的IP地址是100.1.1.1，假设NVE的IP地址是10.1.1.1。假设NVA为NVE1的标识10.1.1.1分配的MPLS标签是100，并通过BGP标签路由通告给ASBR2。
F102、ASBR2接收ASBR1发送的BGP报文，并分配MPLS标签。
例如，请参考图3c，假设ASBR2为ASBR1的标识10.1.1.1分配MPLS标签200，并通过BGP标签路由通告给PE2。
F103、所述NVA为TES分配MPLS VPN标签，所述MPLS VPN标签是所述TES所属的NVO3虚拟网络的标识VN ID，并向所述PE设备发送VPN路由，所述VPN路由中携带TES的标识和MPLS VPN标签。可选的，所述TES的标识可以是所述TES的IP地址前缀或MAC地址。所述PE设备可以在收到VPN路由后，将其中携带的所述TES的IP地址前缀或MAC地址导入本地L2/L3VPN转发表。
例如，请参考图4b，NVA为TES1的IP地址分配MPLS VPN标签1000，该MPLS VPN标签即是NVO3虚拟网络的VN ID。
NVA给NVE下发NVO3隧道解封装表项和TES1对应的路由表项，其中，包括TES分配的MPLS VPN标签和TES的标识。
F2、针对下行方向报文的数据面的方案可以包括：
该下行方向报文的数据面的方案，与图3d及其对应的实施例三的步骤B2相同，详细内容请参考前文，此处不再详细赘述。
由上可见，本发明方案不需要在ASBR上为每个VPN配置VRF和子接口，ASBR也不需要保存和维护VPN路由，只需要保存和维护到达PE/NVE路由以及少量的MPLS标签和NVO3封装转换表项，因此，本发明方案能够减轻ASBR的负担,具有较好的扩展性。
并且，本发明技术方案可以通过在NVO3网络的ASBR上进行NVO3封装与标签封装的转换，实现NVO3网络与MPLS网络之间的跨域通信，解决了一般NVO3网络设备不支持标签转发，不能采用传统OPTION C跨域方案与MPLS网络通信的问题。
为了更好的实施本发明实施例的上述方案，下面还提供用于配合实施上述方案的相关装置。
实施例五
请参考图5a，本发明实施例提供一种自治域边缘路由器(ASBR)，第一AS部署NVO3网络，第二AS部署MPLS网络，所述ASBR是所述的第一AS中的边缘路由器(BR)，所述ASBR500可包括：
接收模块501，用于获得所述MPLS网络中的运营商边缘PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签，所述MPLS网络中的ASBR分配的MPLS标签将用作所述NVO3网络中的所述ASBR发往所述PE设备的MPLS封装的报文的外层标签；
分配模块502，用于从本地地址池中为所述MPLS标签分配IP地址，所述NVO3网络中的所述ASBR与所述NVO3网络中的网络虚拟边缘NVE通信，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
存储模块503，用于保存所述MPLS标签与所述分配的IP地址的对应关系；
发送模块504，用于向所述NVE发送路由信息，所述路由信息包括所述PE设备的标识和所述分配的IP地址，所述分配的IP地址用作所述TES发往所述CE 设备的NVO3封装的报文的外层目的地址。
在本发明的一些实施例中，所述接收模块501，具体用于接收所述MPLS网络中的ASBR发送的BGP报文，所述MPLS网络中的ASBR发送的所述BGP报文携带所述PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签。
请参考图5b，在本发明的一些实施例中，所述ASBR500还可以包括：生成模块505；
所述接收模块501，还用于接收所述NVE发送的NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN；
所述生成模块505，用于生成报文，所述生成的报文携带两层MPLS标签，所述MPLS网络中的ASBR分配的所述MPLS标签作为所述两层MPLS标签中的外层标签，所述VN ID作为所述两层MPLS标签中的内层标签，所述生成的报文中不包括所述外层目的地址和所述外层源地址，所述生成的报文还携带所述NVO3封装的报文的载荷；
所述发送模块504，还用于向所述MPLS网络中的ASBR发送所述生成的报文。
在本发明的一些实施例中，所述分配模块502，还用于为所述NVE的标识分配MPLS标签；所述发送模块502，还用于向所述MPLS网络中的ASBR发送BGP报文，所述向所述MPLS网络中的ASBR发送的所述BGP报文携带所述NVE的标识以及为所述NVE的标识分配的所述MPLS标签；所述存储模块503，还用于保存所述NVE的标识与为所述NVE的标识分配的所述MPLS标签的对应关系。
在本发明的一些实施例中，
所述接收模块501，还用于接收所述MPLS网络中的ASBR转发的报文，所述MPLS网络中的ASBR转发的所述报文来自所述PE设备，所述MPLS网络中的ASBR转发的所述报文中的内层标签是所述TES所属的虚拟网络VN的标识ID，所述MPLS网络中的ASBR转发的所述报文中的外层标签是为所述NVE的标识分配的所述MPLS标签；
所述生成模块505，还用于生成NVO3封装的报文，所述生成的NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述生成的NVO3封装的报文的外层源地址是所述NVO3网络中的所述ASBR的IP地址，所述生成的NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID，所述生成的NVO3封装的报文还携带所述MPLS网络中的ASBR转发的所述报文的载荷；
所述发送模块504，还用于向所述NVE发送所述生成的NVO3封装的报文。
可以理解，本发明实施例的ASBR的各个功能模块的功能可根据上述方法实施例中的方法具体实现，其具体实现过程可参照上述方法实施例中的相关描述，此处不再赘述。
由上可见，在本发明的一些可行的实施方式中，通过采用上述技术方案，取得了以下技术效果：
通过在NVO3网络的ASBR上进行NVO3封装与标签封装的转换，实现了NVO3网络与MPLS网络之间的跨域通信，解决了一般NVO3网络设备不支持标签转发，不能采用传统OPTION C跨域方案与MPLS网络通信的问题；
并且，本发明方案不需要在ASBR上为每个VPN配置VRF和子接口，ASBR也不需要保存和维护VPN路由，只需要保存和维护到达PE/NVE路由以及少量的MPLS标签和NVO3封装转换表项,因此，本发明方案能够减轻ASBR的负担,具有较好的扩展性。
实施例六
请参考图6a，本发明实施例提供一种网络虚拟化边缘节点(NVE)，第一AS部署NVO3网络，第二AS部署MPLS网络，所述NVE用在所述第一AS中，所述NVE600可包括：
接收模块601，用于接收所述NVO3网络中的ASBR发送的路由信息，所述路由信息包括IP地址和所述MPLS网络中的PE设备的标识，所述IP地址是所述NVO3网络中的ASBR从所述ASBR的本地地址池中为所述PE设备分配的，用作所述NVE连接的租户终端系统TES发往所述PE设备连接的用户边缘CE设备的NVO3封装的报文的外层目的地址，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
所述接收模块601，还用于接收所述PE设备通告的MPLS VPN标签和所述CE设备的标识，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN；
路由模块602，用于生成VPN路由信息，所述VPN路由信息包括所述CE设备的标识、所述分配的IP地址和VN ID，所述VN ID是所述MPLS VPN标签，所述分配的IP地址作为NVO3封装的外层目的地址。
请参考图6b，在本发明的一些实施例中，所述NVE600还可以包括：生成模块603和发送模块604；
所述接收模块601，还用于接收所述TES发往所述PE设备的报文，所述发往所述PE设备的报文携带所述CE设备的标识；
生成模块603，用于对所述TES发往所述PE设备的报文进行NVO3封装以生成NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN；
发送模块604，用于向所述NVO3网络中的ASBR发送所述NVO3封装的报文。
请参考图6b，在本发明的一些实施例中，所述NVE600还可以包括：
路由发送模块605，用于向所述PE设备发送VPN路由，所述VPN路由中携带MPLS VPN标签和所述TES的标识，所述VPN路由中携带的所述MPLS VPN标签是所述TES所属的虚拟网络的VN ID。
请参考图6b，在本发明的一些实施例中，
所述接收模块601，还用于接收所述NVO3网络中的ASBR发送的NVO3封装的报文，所述NVE接收的所述NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述NVE接收的所述NVO3封装的报文的外层源地址是所述NVO3网络中的所述ASBR的IP地址，所述NVE接收的所述NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID；
所述发送模块604，还用于对接收到的所述NVO3封装的报文解封装，根据所述TES所属的虚拟网络的VN ID将解封装后的报文发送给所述NVO3网络中的TES。
可以理解，本发明实施例的NVE的各个功能模块的功能可根据上述方法实施例中的方法具体实现，其具体实现过程可参照上述方法实施例中的相关描述，此处不再赘述。
由上可见，在本发明的一些可行的实施方式中，通过采用上述技术方案，取得了以下技术效果：
通过在NVO3网络的ASBR上进行NVO3封装与标签封装的转换，实现了NVO3网络与MPLS网络之间的跨域通信，解决了一般NVO3网络设备不支持标签转发，不能采用传统OPTION C跨域方案与MPLS网络通信的问题；
并且，本发明方案不需要在ASBR上为每个VPN配置VRF和子接口，ASBR也不需要保存和维护VPN路由，只需要保存和维护到达PE/NVE路由以及少量的MPLS标签和NVO3封装转换表项,因此，本发明方案能够减轻ASBR的负担,具有较好的扩展性。
本发明实施例还提供一种计算机存储介质，该计算机存储介质可存储有程序，该程序执行时包括上述方法实施例一中记载的VPN跨域通信方法的部分或全部步骤。
请参考图7，本发明实施例还提供一种计算机设备700，可包括：
处理器710，存储器720，通信接口730，总线740；
所述存储器720用于存储计算机执行指令，所述处理器710与所述存储器720通过所述总线740连接，当所述计算机设备运行时，所述处理器710执行所述存储器720存储的所述计算机执行指令，以使所述计算机设备执行如上述实施例中所述的实现NVO3网络与MPLS网络之间通信的方法。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详细描述的部分，可以参见其它实施例的相关描述。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述动作顺序的限制，因为依据本发明，某些步骤可以采用其它顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：ROM、RAM、磁盘或光盘等。
以上对本发明实施例所提供的本发明实施例提供的一种实现NVO3网络 与MPLS网络之间通信的方法和装置进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (21)

  1. 一种实现三层网络虚拟化NVO3网络与多协议标签交换MPLS网络之间通信的方法，其特征在于，第一自治系统AS部署NVO3网络，第二AS部署MPLS网络，所述方法包括：
    所述NVO3网络中的自治域边缘路由器ASBR获得所述MPLS网络中的运营商边缘PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签，所述MPLS网络中的ASBR分配的MPLS标签将用作所述NVO3网络中的ASBR发往所述PE设备的MPLS封装的报文的外层标签；
    所述NVO3网络中的ASBR从本地地址池中为所述MPLS标签分配IP地址，所述NVO3网络中的ASBR与所述NVO3网络中的网络虚拟边缘NVE通信，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
    所述NVO3网络中的ASBR保存所述MPLS标签与所述分配的IP地址的对应关系；
    所述NVO3网络中的ASBR向所述NVE发送路由信息，所述路由信息包括所述PE设备的标识和所述分配的IP地址，所述分配的IP地址用作所述TES发往所述CE设备的NVO3封装的报文的外层目的地址。
  2. 根据权利要求1所述的方法，其特征在于，所述NVO3网络中的ASBR获得所述MPLS网络中的PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签，包括：
    所述NVO3网络中的ASBR接收所述MPLS网络中的ASBR发送的BGP报文，所述MPLS网络中的ASBR发送的所述BGP报文携带所述PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签。
  3. 根据权利要求1或2所述的方法，其特征在于，还包括：
    所述NVO3网络中的ASBR接收所述NVE发送的NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括虚拟网络标识VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签用于标识所述CE设备所属的VPN；
    所述NVO3网络中的ASBR生成报文，所述生成的报文携带两层MPLS标签，所述MPLS网络中的ASBR分配的所述MPLS标签作为所述两层MPLS标签中的外层标签，所述VN ID作为所述两层MPLS标签中的内层标签，所述生成的报文中不包括所述外层目的地址和所述外层源地址，所述生成的报文还携带所述NVO3封装的报文的载荷；
    所述NVO3网络中的ASBR向所述MPLS网络中的ASBR发送所述生成的报文。
  4. 根据权利要求1-3任一所述的方法，其特征在于，还包括：
    所述NVO3网络中的ASBR为所述NVE的标识分配MPLS标签；
    所述NVO3网络中的ASBR向所述MPLS网络中的ASBR发送BGP报文，所述向所述MPLS网络中的ASBR发送的所述BGP报文携带所述NVE的标识以及为所述NVE的标识分配的所述MPLS标签；
    所述NVO3网络中的ASBR保存所述NVE的标识与为所述NVE的标识分配的所述MPLS标签的对应关系。
  5. 根据权利要求4所述的方法，其特征在于，还包括：
    所述NVO3网络中的ASBR接收所述MPLS网络中的ASBR转发的报文，所述MPLS网络中的ASBR转发的所述报文来自所述PE设备，所述MPLS网络中的ASBR转发的所述报文中的内层标签是所述TES所属的虚拟网络的VN ID，所述MPLS网络中的ASBR转发的报文中的外层标签是为所述NVE的标识分配的所述MPLS标签；
    所述NVO3网络中的ASBR生成NVO3封装的报文，所述生成的NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述生成的NVO3封装的报文的外层源地址是所述NVO3网络中的ASBR的IP地址，所述生成的NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID，所述生成的NVO3封装的报文还携带所述MPLS网络中的ASBR转发的所述报文的载荷；
    所述NVO3网络中的ASBR向所述NVE发送所述生成的NVO3封装的报文。
  6. 根据权利要求1-5任一所述的方法，其特征在于，
    所述PE设备的标识是所述PE设备的IP地址。
  7. 一种实现三层网络虚拟化NVO3网络与多协议标签交换MPLS网络之间 通信的方法，其特征在于，第一自治系统AS部署NVO3网络，第二AS部署MPLS网络，所述方法包括：
    所述NVO3网络中的网络虚拟边缘NVE接收所述NVO3网络中的自治域边缘路由器ASBR发送的路由信息，所述路由信息包括IP地址和所述MPLS网络中的运营商边缘PE设备的标识的对应关系，所述IP地址是所述NVO3网络中的ASBR从本地地址池中为所述PE设备分配的，用作所述NVE连接的租户终端系统TES发往所述PE设备连接的用户边缘CE设备的NVO3封装的报文的外层目的地址，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
    所述NVE接收所述PE设备通告的MPLS VPN标签和所述CE设备的标识，所述MPLS VPN标签用于标识所述CE设备所属的VPN；
    所述NVE生成VPN路由信息，所述VPN路由信息包括所述CE设备的标识、所述分配的IP地址和VN ID，所述VN ID是所述MPLS VPN标签，所述分配的IP地址作为NVO3封装的外层目的地址。
  8. 根据权利要求7所述的方法，其特征在于，还包括：
    所述NVE接收所述TES发往所述PE设备的报文，所述发往所述PE设备的报文携带所述CE设备的标识；
    所述NVE对所述TES发往所述PE设备的报文进行NVO3封装以生成NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签用于标识所述CE设备所属的VPN；
    所述NVE向所述NVO3网络中的ASBR发送所述NVO3封装的报文。
  9. 根据权利要求7或8所述的方法，其特征在于，还包括：
    所述NVE向所述PE设备发送VPN路由，所述VPN路由中携带MPLS VPN标签和所述TES的标识，所述VPN路由中携带的所述MPLS VPN标签是所述TES所属的虚拟网络的VN ID。
  10. 根据权利要求9所述的方法，其特征在于，还包括：
    所述NVE接收所述NVO3网络中的ASBR发送的NVO3封装的报文，所述NVE接收的所述NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述 NVE接收的所述NVO3封装的报文的外层源地址是所述NVO3网络中的ASBR的IP地址，所述NVE接收的所述NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID；
    所述NVE对接收到的所述NVO3封装的报文解封装，根据所述TES所属的虚拟网络的VN ID将解封装后的报文发送给所述NVO3网络中的TES。
  11. 根据权利要求7-10任一所述的方法，其特征在于，
    所述PE设备的标识是所述PE设备的IP地址。
  12. 一种自治域边缘路由器ASBR，其特征在于，第一自治系统AS部署三层网络虚拟化NVO3网络，第二自治系统AS部署多协议标签交换MPLS网络，所述ASBR是所述第一AS中的边缘路由器BR，所述ASBR包括：
    接收模块，用于获得所述MPLS网络中的运营商边缘PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签，所述MPLS网络中的ASBR分配的MPLS标签将用作所述NVO3网络中的所述ASBR发往所述PE设备的MPLS封装的报文的外层标签；
    分配模块，用于从本地地址池中为所述MPLS标签分配IP地址，所述NVO3网络中的所述ASBR与所述NVO3网络中的网络虚拟边缘NVE通信，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
    存储模块，用于保存所述MPLS标签与所述分配的IP地址的对应关系；
    发送模块，用于向所述NVE发送路由信息，所述路由信息包括所述PE设备的标识和所述分配的IP地址，所述分配的IP地址用作所述TES发往所述CE设备的NVO3封装的报文的外层目的地址。
  13. 根据权利要求12所述的ASBR，其特征在于，
    所述接收模块，具体用于接收所述MPLS网络中的ASBR发送的BGP报文，所述MPLS网络中的ASBR发送的所述BGP报文携带所述PE设备的标识和所述MPLS网络中的ASBR分配的MPLS标签。
  14. 根据权利要求12或13所述的ASBR，其特征在于，
    所述接收模块，还用于接收所述NVE发送的NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括虚拟网络标识 VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签可以用于标识所述CE设备所属的VPN；
    所述ASBR还包括生成模块，用于生成报文，所述生成的报文携带两层MPLS标签，所述MPLS网络中的ASBR分配的所述MPLS标签作为所述两层MPLS标签中的外层标签，所述VN ID作为所述两层MPLS标签中的内层标签，所述生成的报文中不包括所述外层目的地址和所述外层源地址，所述生成的报文还携带所述NVO3封装的报文的载荷；
    所述发送模块，还用于向所述MPLS网络中的ASBR发送所述生成的报文。
  15. 根据权利要求12-14任一所述的ASBR，其特征在于，
    所述分配模块，还用于为所述NVE的标识分配MPLS标签；
    所述发送模块，还用于向所述MPLS网络中的ASBR发送BGP报文，所述向所述MPLS网络中的ASBR发送的所述BGP报文携带所述NVE的标识以及为所述NVE的标识分配的所述MPLS标签；
    所述存储模块，还用于保存所述NVE的标识与为所述NVE的标识分配的所述MPLS标签的对应关系。
  16. 根据权利要求15所述的ASBR，其特征在于，
    所述接收模块，还用于接收所述MPLS网络中的ASBR转发的报文，所述MPLS网络中的ASBR转发的所述报文来自所述PE设备，所述MPLS网络中的ASBR转发的所述报文中的内层标签是所述TES所属的虚拟网络的VN ID，所述MPLS网络中的ASBR转发的所述报文中的外层标签是为所述NVE的标识分配的所述MPLS标签；
    生成模块，还用于生成NVO3封装的报文，所述生成的NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述生成的NVO3封装的报文的外层源地址是所述NVO3网络中的所述ASBR的IP地址，所述生成的NVO3封装的报文还携带所述TES所属的虚拟网络的VN ID，所述生成的NVO3封装的报文还携带所述MPLS网络中的ASBR转发的所述报文的载荷；
    所述发送模块，还用于向所述NVE发送所述生成的NVO3封装的报文。
  17. 一种网络虚拟边缘NVE，其特征在于，第一自治系统AS部署三层网络虚拟化NVO3网络，第二自治系统AS部署多协议标签交换MPLS网络，所述NVE用在第一AS中，所述NVE包括：
    接收模块，用于接收所述NVO3网络中的自治域边缘路由器ASBR发送的路由信息，所述路由信息包括IP地址和所述MPLS网络中的运营商边缘PE设备的标识的对应关系，所述IP地址是所述NVO3网络中的ASBR从本地地址池中为所述PE设备分配的，用作所述NVE连接的租户终端系统TES发往所述PE设备连接的用户边缘CE设备的NVO3封装的报文的外层目的地址，所述NVE连接的租户终端系统TES与所述PE设备连接的用户边缘CE设备属于同一虚拟私有网络VPN；
    所述接收模块，还用于接收所述PE设备通告的MPLS VPN标签和所述CE设备的标识，所述MPLS VPN标签用于标识所述CE设备所属的VPN；
    路由模块，用于生成VPN路由信息，所述VPN路由信息包括所述CE设备的标识、所述分配的IP地址和VN ID，所述VN ID是所述MPLS VPN标签，所述分配的IP地址作为NVO3封装的外层目的地址。
  18. 根据权利要求17所述的NVE，其特征在于，
    所述接收模块，还用于接收所述TES发往所述PE设备的报文，所述发往所述PE设备的报文携带所述CE设备的标识；
    生成模块，用于对所述TES发往所述PE设备的报文进行NVO3封装以生成NVO3封装的报文，所述NVO3封装的报文的外层目的地址是所述分配的IP地址，所述NVO3封装的报文的外层源地址是所述NVE的IP地址，所述NVO3封装的报文还包括VN ID，所述VN ID是所述PE设备通告的MPLS VPN标签，所述MPLS VPN标签用于标识所述CE设备所属的VPN；
    发送模块，用于向所述NVO3网络中的ASBR发送所述NVO3封装的报文。
  19. 根据权利要求17或18所述的NVE，其特征在于，还包括：
    路由发送模块，用于向所述PE设备发送VPN路由，所述VPN路由中携带MPLS VPN标签和所述TES的标识，所述VPN路由中携带的所述MPLS VPN标签是所述TES所属的虚拟网络的VN ID。
  20. 根据权利要求19所述的NVE，其特征在于，
    所述接收模块，还用于接收所述NVO3网络中的ASBR发送的NVO3封装的报文，所述NVE接收的所述NVO3封装的报文的外层目的地址是所述NVE的IP地址，所述NVE接收的所述NVO3封装的报文的外层源地址是所述NVO3网络中的ASBR的IP地址，所述NVE接收的所述NVO3封装的报文还携带所述 TES所属的虚拟网络的VN ID；
    所述发送模块，还用于对接收到的所述NVO3封装的报文解封装，根据所述TES所属的虚拟网络的VN ID将解封装后的报文发送给所述NVO3网络中的TES。
  21. 一种计算机网络设备，其特征在于，所述计算机设备包括处理器、存储器、总线和通信接口；
    所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述计算机设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述计算机设备执行如权利要求1-6中任一项所述的实现NVO3网络与MPLS网络之间通信的方法，或者如权利要求7-11中任一项所述的实现NVO3网络与MPLS网络之间通信的方法。
PCT/CN2015/092876 2014-10-27 2015-10-26 实现nvo3网络与mpls网络之间通信的方法和装置 Ceased WO2016066072A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15853776.1A EP3133778B1 (en) 2014-10-27 2015-10-26 Method and device for realizing communication between nvo3 network and mpls network
US15/393,049 US10484203B2 (en) 2014-10-27 2016-12-28 Method for implementing communication between NVO3 network and MPLS network, and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410584292.8 2014-10-27
CN201410584292.8A CN104518940B (zh) 2014-10-27 2014-10-27 实现nvo3网络与mpls网络之间通信的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/393,049 Continuation US10484203B2 (en) 2014-10-27 2016-12-28 Method for implementing communication between NVO3 network and MPLS network, and apparatus

Publications (1)

Publication Number Publication Date
WO2016066072A1 true WO2016066072A1 (zh) 2016-05-06

Family

ID=52793700

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/092876 Ceased WO2016066072A1 (zh) 2014-10-27 2015-10-26 实现nvo3网络与mpls网络之间通信的方法和装置

Country Status (4)

Country Link
US (1) US10484203B2 (zh)
EP (1) EP3133778B1 (zh)
CN (1) CN104518940B (zh)
WO (1) WO2016066072A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240007400A1 (en) * 2021-03-19 2024-01-04 Huawei Technologies Co., Ltd. Traffic control method and related device

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931548B (zh) * 2009-06-24 2012-09-19 华为技术有限公司 一种接入网络标签管理方法、装置和系统
CN104518940B (zh) 2014-10-27 2017-12-29 华为技术有限公司 实现nvo3网络与mpls网络之间通信的方法和装置
CN106209553B (zh) 2015-04-30 2019-07-23 华为技术有限公司 报文处理方法、设备及系统
CN106341298B (zh) 2015-07-06 2019-03-22 中兴通讯股份有限公司 报文发送方法及装置
CN106572021B (zh) * 2015-10-09 2021-07-06 中兴通讯股份有限公司 一种实现网络虚拟化叠加的方法与网络虚拟化边缘节点
CN106921573B (zh) * 2015-12-28 2020-04-14 华为技术有限公司 NVo3网络中用于发布租户路由的方法及装置
CN106936681A (zh) * 2015-12-29 2017-07-07 中国移动通信集团公司 一种数据处理方法和装置
US10225189B2 (en) * 2016-04-26 2019-03-05 Juniper Networks, Inc. Egress peer engineering using IPv4-mapped IPv6 addresses
CN107360089B (zh) * 2016-05-10 2021-03-19 新华三技术有限公司 一种路由建立方法、业务数据转换方法及装置
US10027589B1 (en) * 2016-06-30 2018-07-17 Juniper Network, Inc. Apparatus, system, and method for achieving redundancy and load-balancing across communication layers within networks
US10567276B2 (en) 2016-08-05 2020-02-18 Huawei Technologies Co., Ltd. Virtual network pre-configuration in support of service-based traffic forwarding
US10142223B2 (en) * 2016-09-28 2018-11-27 Juniper Networks, Inc. Symmetric intersubnet traffic load balancing in multihomed networks
US10356131B2 (en) 2016-12-09 2019-07-16 Nutanix, Inc. Service chaining for multiple uplink bridges
US11089066B2 (en) 2016-12-09 2021-08-10 Nutanix, Inc. System and method for dynamic medium access control (MAC) relating to a virtualization environment
US10659352B2 (en) * 2017-05-31 2020-05-19 Juniper Networks, Inc. Signaling private context forwarding tables for a private forwarding layer
CN107342941B (zh) * 2017-06-01 2019-11-12 杭州迪普科技股份有限公司 一种vxlan控制平面的优化方法及装置
US10291433B2 (en) * 2017-07-07 2019-05-14 Juniper Networks, Inc. Signaling multicast information to a redundant multi-homing router for a layer 2 virtual private network
CN107645445B (zh) * 2017-09-15 2019-11-22 安徽大学 一种基于虚拟节点技术的sdn网络跨域通信方法
CN110535766B (zh) * 2018-05-25 2021-10-22 华为技术有限公司 一种生成路由的方法和设备
CN114844828A (zh) 2019-10-31 2022-08-02 华为技术有限公司 发送报文的方法、装置及系统
CN111083033B (zh) * 2019-12-20 2021-09-24 瑞斯康达科技发展股份有限公司 基于多协议标签交换协议的三层虚拟专用网
CN119728517A (zh) * 2020-09-30 2025-03-28 华为技术有限公司 一种路由处理方法及网络设备
CN112737947B (zh) * 2020-12-29 2022-08-30 优刻得科技股份有限公司 基于mpls的虚拟网络跨域传输方法、系统、设备和介质
US12028248B2 (en) 2021-05-27 2024-07-02 Cisco Technology, Inc. Using global virtual network instance (VNI) labels to signal a service chain
CN113746739B (zh) * 2021-08-20 2022-10-21 新华三信息安全技术有限公司 一种路由表创建方法、pe设备、电子设备及存储介质
US12519724B2 (en) * 2022-11-15 2026-01-06 Cisco Technology, Inc. Inter-realm routing within a shaft

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103200069A (zh) * 2013-03-29 2013-07-10 华为技术有限公司 一种报文处理的方法和设备
WO2013185644A1 (zh) * 2012-07-24 2013-12-19 中兴通讯股份有限公司 虚拟网络自动发现和自动配置的方法及其装置
CN103685026A (zh) * 2012-08-31 2014-03-26 中兴通讯股份有限公司 一种虚拟网络的接入方法和系统
US20140086253A1 (en) * 2012-09-26 2014-03-27 Futurewei Technologies, Inc. Overlay Virtual Gateway for Overlay Networks
CN104104534A (zh) * 2013-04-12 2014-10-15 中兴通讯股份有限公司 一种虚拟网络管理的实现方法和系统
CN104518940A (zh) * 2014-10-27 2015-04-15 华为技术有限公司 实现nvo3网络与mpls网络之间通信的方法和装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7733876B2 (en) * 2005-02-11 2010-06-08 Cisco Technology, Inc. Inter-autonomous-system virtual private network with autodiscovery and connection signaling
US8179905B1 (en) * 2006-09-27 2012-05-15 At&T Intellectual Property Ii, L.P. Method and apparatus for providing communication for virtual private networks
US20120224579A1 (en) * 2011-03-01 2012-09-06 Futurewei Technologies, Inc. Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN) Over Routed Ethernet Backbone
CN103841023B (zh) * 2012-11-22 2017-03-08 华为技术有限公司 数据转发的方法和设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013185644A1 (zh) * 2012-07-24 2013-12-19 中兴通讯股份有限公司 虚拟网络自动发现和自动配置的方法及其装置
CN103685026A (zh) * 2012-08-31 2014-03-26 中兴通讯股份有限公司 一种虚拟网络的接入方法和系统
US20140086253A1 (en) * 2012-09-26 2014-03-27 Futurewei Technologies, Inc. Overlay Virtual Gateway for Overlay Networks
CN103200069A (zh) * 2013-03-29 2013-07-10 华为技术有限公司 一种报文处理的方法和设备
CN104104534A (zh) * 2013-04-12 2014-10-15 中兴通讯股份有限公司 一种虚拟网络管理的实现方法和系统
CN104518940A (zh) * 2014-10-27 2015-04-15 华为技术有限公司 实现nvo3网络与mpls网络之间通信的方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240007400A1 (en) * 2021-03-19 2024-01-04 Huawei Technologies Co., Ltd. Traffic control method and related device
US12470484B2 (en) * 2021-03-19 2025-11-11 Huawei Technologies Co., Ltd. Traffic control method and related device

Also Published As

Publication number Publication date
CN104518940B (zh) 2017-12-29
US20170118043A1 (en) 2017-04-27
CN104518940A (zh) 2015-04-15
US10484203B2 (en) 2019-11-19
EP3133778A1 (en) 2017-02-22
EP3133778B1 (en) 2018-09-12
EP3133778A4 (en) 2017-06-14

Similar Documents

Publication Publication Date Title
EP3133778B1 (en) Method and device for realizing communication between nvo3 network and mpls network
EP3836490B1 (en) Vpn cross-domain implementation method, device, and border node
US12206577B2 (en) Multicast traffic transmission method and apparatus, communication node, and storage medium
KR102054338B1 (ko) 개별 관리들을 이용하는 vlan 태깅된 패킷들의 가상 포워딩 인스턴스들의 원단 주소들로의 라우팅
WO2020052230A1 (zh) 一种传输控制方法、节点、网络系统及存储介质
WO2020156105A1 (zh) 数据转发方法及相关装置
CN110050445B (zh) 发送和接收消息的方法、设备和系统
WO2015165311A1 (zh) 传输数据报文的方法和供应商边缘设备
CN107995083B (zh) 实现L2VPN与VxLAN互通的方法、系统及设备
WO2020212998A1 (en) Network address allocation in a virtual layer 2 domain spanning across multiple container clusters
CN106572021A (zh) 一种实现网络虚拟化叠加的方法与网络虚拟化边缘节点
CN103326915A (zh) 实现三层虚拟专用网络的方法、设备及系统
EP3437266A1 (en) Method and apparatus for pseudo-wire setup and maintenance using intermediate system to intermediate system (is-is)
WO2023082779A1 (zh) 报文转发方法、电子设备及存储介质
WO2019205836A1 (zh) 一种数据报文转发的方法及装置
CN102394804A (zh) 虚拟私有网络系统的构建方法及虚拟私有网络系统
WO2021017590A1 (zh) 一种实现dci三层通信的方法、系统及第一gw
CN113904981B (zh) 一种路由信息处理方法、装置、电子设备和存储介质
WO2020152691A1 (en) Multi-network internet protocol version 6 (ipv6) duplicate address detection using ethernet virtual private network (evpn)
CN112910771B (zh) 连接建立方法、装置、设备和存储介质
CN121486263A (zh) 一种报文处理方法及装置
Rabadan et al. Usage and Applicability of BGP MPLS-Based Ethernet VPN
WO2023050929A1 (zh) 一种路由发布方法、报文转发方法、设备及系统
CN115460141A (zh) 网络互通方法及装置
CN115460140A (zh) 网络互通方法及装置

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

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2015853776

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2015853776

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE