CN113660151A

CN113660151A - L2VPN cross-service communication method, device, electronic equipment and readable medium

Info

Publication number: CN113660151A
Application number: CN202110907601.0A
Authority: CN
Inventors: 王俊; 祖翔; 马晓乾; 袁刚; 王鹏; 李华楠
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2021-08-09
Filing date: 2021-08-09
Publication date: 2021-11-16
Anticipated expiration: 2041-08-09
Also published as: CN113660151B

Abstract

The present disclosure provides an L2VPN cross-service communication method, apparatus, electronic device and readable medium, wherein the L2VPN cross-service communication method includes: implementing a first L2VPN service of a first network based on an MPLS VLL; implementing a second L2VPN service of a second network based on an EVPN VPWS instance programmed by SRv6, wherein a data link is arranged between a first leaf node of the first network and a first edge routing device of the second network; determining an association relationship between a VC interface of the MPLS VLL and an AC interface of the EVPN VPWS instance; expanding the identifier of a first leaf node of the first network into a communication identifier of a two-layer cross-connection endpoint between the first network and the second network; and the first leaf node and the first edge routing equipment realize the L2VPN service data interaction between the first network and the second network according to the incidence relation and the communication identifier. By the embodiment of the disclosure, the expandability of the communication network is improved, and the maintenance is facilitated.

Description

L2VPN cross-service communication method, device, electronic equipment and readable medium

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for L2VPN cross-service communication, an electronic device, and a readable medium.

Background

At present, IP (Internet Protocol, Protocol context interconnected between networks) data transmission in a bearer network is mainly implemented based on MPLS (Multi-Protocol Label Switching, Multi-Label Protocol interaction), but MPLS (Multi-Protocol Label Switching ) needs to use an independent signaling Protocol to allocate a Label to each node in the network, a configuration process is relatively complex, and configuration information needs to be issued for all node modes of an end-to-end connection path each time data transmission is performed, transmission efficiency is low, finally each node needs to maintain a state of each connection, and service expansion is difficult.

In the related art, with the mature deployment and application of Ipv6(Internet Protocol Version 6 Internet Protocol Version six), SRv6 (i.e. Segment Routing + Ipv6, Segment Routing generation six) can directly forward data through an Ipv6 tunnel without using an additional MPLS tunnel for data forwarding. In the current general MPLS service and SRv 6L 2VPN service interworking scenario, a cross-domain VPN-OptionA scheme is used to implement, and SRv 6L 2VPN traffic needs to be introduced into the MPLS L2VPN via a Virtual Local Area Network (VLAN).

The MPLS L2VPN provides a two-layer VPN service based on an MPLS Network, so that an operator can provide a two-layer VPN (Virtual Private Network) based on different data link layers on a uniform MPLS Network.

In short, MPLS L2VPN transparently transports user layer two data across an MPLS network. From the user's perspective, an MPLS network is a two-layer switching network that can establish two-layer connections between different nodes.

However, the above cross-service interaction scheme has poor expandability, adopts ordinary IP address forwarding, and needs to use different interfaces for each cross-domain VPN, which not only increases the requirements for the devices, but also causes the problems of complex operation and maintenance, high cost, and the like.

It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

An object of the present disclosure is to provide an L2VPN cross-service communication method, apparatus, electronic device and readable medium for overcoming, at least to some extent, the problem of poor network scalability due to the limitations and drawbacks of the related art.

According to a first aspect of an embodiment of the present disclosure, there is provided an L2VPN cross-service communication method, including: implementing a first L2VPN service of a first network based on an MPLS VLL; implementing a second L2VPN service of a second network based on an EVPN VPWS instance programmed by SRv6, wherein a data link is arranged between a first leaf node of the first network and a first edge routing device of the second network; determining an association relationship between a VC interface of the MPLS VLL and an AC interface of the EVPN VPWS instance; expanding the identifier of a first leaf node of the first network into a communication identifier of a two-layer cross-connection endpoint between the first network and the second network; and the first leaf node and the first edge routing equipment realize the L2VPN service data interaction between the first network and the second network according to the incidence relation and the communication identifier.

In an exemplary embodiment of the present disclosure, implementing, by the first leaf node and the first edge routing device, the L2VPN traffic data interaction between the first network and the second network according to the association relationship and the communication identifier includes: if the first leaf node is detected to receive the L2VPN data packet, determining a first identifier of a VC interface for sending the L2VPN data packet; determining a second identifier of an AC interface of a target EVPN VPWS instance corresponding to the first identifier according to the incidence relation; performing data conversion processing on the L2VPN data packet to obtain a first data packet after conversion processing; and forwarding the first data packet to an AC interface of the target EVPN VPWS instance through a VC interface corresponding to the first identifier according to the second identifier.

In an exemplary embodiment of the present disclosure, performing data conversion processing on the L2VPN packet to obtain a first converted packet includes: when the first leaf node sends the L2VPN data packet to the first edge routing device, writing a communication identifier of the two-layer cross connection end point at the stack bottom; and the first edge routing equipment removes an IPv6 header and an extension header from the L2VPN data packet according to the communication identification of the two layers of cross connection endpoints to obtain the first data.

In an exemplary embodiment of the present disclosure, the implementing, by the first leaf node and the first edge routing device, the L2VPN traffic data interaction between the first network and the second network according to the association relationship and the communication identifier further includes: if the first edge routing equipment is detected to receive the data packet sent by the AC interface of the EVPN VPWS instance, determining a third identifier of the AC interface for sending the data packet; determining a fourth identifier of a VC interface of the MPLS VLL corresponding to the third identifier according to the incidence relation; performing data conversion processing on the data packet sent by the AC interface to obtain a second data packet after conversion processing; and forwarding the second data packet to a VC interface of the MPLS VLL through an AC interface corresponding to the third identifier according to the fourth identifier.

In an exemplary embodiment of the present disclosure, performing data conversion processing on a data packet sent by the AC interface to obtain a second data packet after conversion processing includes: when the first edge routing equipment sends the data packet sent by the AC interface to the first leaf node, writing a communication identifier of the two-layer cross connection endpoint at the stack bottom; and the first leaf node removes an IPv6 header and an extension header from a data packet sent by the AC interface according to the communication identification of the two-layer cross connection endpoint so as to obtain the second data.

In an exemplary embodiment of the present disclosure, implementing the first L2VPN service of the first network based on the MPLS VLL includes: controlling the terminal equipment to access a second leaf node of the first network through a first virtual link; and the first L2VPN service is realized between the first leaf node and the second leaf node through the MPLS VLL.

In an exemplary embodiment of the disclosure, implementing the second L2VPN service of the second network based on the EVPN VPWS instance programmed at SRv6 includes: the first leaf node accessing the second network; the second network further comprises a second edge routing device, and the second L2VPN service is implemented between the first edge routing device and the second edge routing device through the SRv6 programmed EVPN VPWS instance.

According to a second aspect of the embodiments of the present disclosure, there is provided an L2VPN cross-service communication apparatus including: the first communication module is used for realizing a first L2VPN service of a first network based on the MPLS VLL; a second communication module, configured to implement a second L2VPN service of a second network based on an EVPN VPWS instance programmed by SRv6, where a data link is provided between a first leaf node of the first network and a first edge routing device of the second network; an association module, configured to determine an association relationship between a VC interface of the MPLS VLL and an AC interface of the EVPN VPWS instance; the expansion module is used for expanding the identifier of the first leaf node of the first network into a communication identifier of a two-layer cross connection endpoint between the first network and the second network; and the interaction module is used for realizing the L2VPN service data interaction between the first network and the second network by the first leaf node and the first edge routing equipment according to the incidence relation and the communication identifier.

According to a third aspect of the present disclosure, there is provided an electronic device comprising: a memory; and a processor coupled to the memory, the processor configured to perform the method of any of the above based on instructions stored in the memory.

According to a fourth aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a program which, when executed by a processor, implements the L2VPN cross-traffic communication method as set forth in any one of the above.

In the embodiment of the present disclosure, by determining an association relationship between a VC interface of the MPLS VLL and an AC interface of the EVPN VPWS instance, and expanding an identifier of a first leaf node of the first network to a communication identifier of a two-layer cross connection endpoint between the first network and the second network, the first leaf node and the first edge routing device implement L2VPN service data interaction between the first network and the second network according to the association relationship and the communication identifier, that is, the association and smooth docking of the SRV6 and the L2VPN instance of MPLS is implemented on one device, which improves scalability of a communication network and facilitates maintenance.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

Fig. 1 is a flow chart of a L2VPN cross-traffic communication method in an example embodiment of the present disclosure;

fig. 2 is a flowchart of a L2VPN cross-traffic communication method in another exemplary embodiment of the present disclosure;

fig. 3 is a flowchart of a L2VPN cross-traffic communication method in another exemplary embodiment of the present disclosure;

fig. 4 is a flowchart of an L2VPN cross-traffic communication method in another exemplary embodiment of the present disclosure;

fig. 5 is a flowchart of a L2VPN cross-traffic communication method in another exemplary embodiment of the present disclosure;

fig. 6 is a flowchart of a L2VPN cross-traffic communication method in another exemplary embodiment of the present disclosure;

fig. 7 is a flowchart of a L2VPN cross-traffic communication method in another exemplary embodiment of the present disclosure;

fig. 8 is a schematic diagram of an L2VPN cross-traffic communication architecture in an example embodiment of the present disclosure;

fig. 9 is an interaction diagram of a L2VPN cross-service communication method in an exemplary embodiment of the present disclosure;

fig. 10 is an interaction diagram of an L2VPN cross-service communication method in another exemplary embodiment of the present disclosure;

fig. 11 is a flowchart of a L2VPN cross-traffic communication method in another exemplary embodiment of the present disclosure;

fig. 12 is a flowchart of an L2VPN cross-traffic communication method in another exemplary embodiment of the present disclosure;

fig. 13 is a block diagram of an L2VPN cross-service communication device in an exemplary embodiment of the present disclosure;

fig. 14 is a block diagram of an electronic device in an exemplary embodiment of the disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Further, the drawings are merely schematic illustrations of the present disclosure, in which the same reference numerals denote the same or similar parts, and thus, a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

The following detailed description of exemplary embodiments of the disclosure refers to the accompanying drawings.

Fig. 1 is a flowchart of an L2VPN cross-traffic communication method in an exemplary embodiment of the present disclosure.

Referring to fig. 1, the L2VPN cross-service communication method may include:

step S102, implementing a first L2VPN service of a first network based on the MPLS VLL.

In an exemplary embodiment of the present disclosure, MPLS (Multiprotocol Label Switching) is an ip (internet protocol) backbone technology, and VLL (Virtual Leased Line) provides a point-to-point L2VPN service on an MPLS network.

Step S104, implementing a second L2VPN service of a second network based on the EVPN VPWS instance programmed by SRv6, where a data link is provided between a first leaf node of the first network and a first edge routing device of the second network.

In an exemplary embodiment of the present disclosure, an EVPN VPWS (Ethernet Virtual Private Network Virtual Private Wire Service) provides a P2P (peer to peer) L2VPN Service scheme based on an EVPN Service architecture, which multiplexes and simplifies the original EVPN technology, and uses an MPLS tunnel technology to traverse a backbone Network to provide a two-layer packet forwarding manner without looking up MAC (Media Access Control, or physical address) forwarding entries for connections between ac (Access circuits), where the EVPN VPWS basic architecture is composed of the following parts:

(1) AC: an AC is a separate link or circuit connecting the CE and PE. The AC interface may be a physical interface or a logical interface. The AC attributes include the encapsulation type, maximum Transmission unit mtu (maximum Transmission unit), and interface parameters for a particular link type.

Wherein, the pe (provider edge) router: the service provider edge router, which is an edge device of the service provider network, is directly connected to the customer's CE. In an MPLS network, all processing of VPNs occurs at the PEs.

Wherein, the ce (customer edge) device: the user network edge device has an interface directly connected with the SP (Service provider). The CE may be a router or a switch, or may be a host. The CE does not "perceive" the existence of VPNs nor does it need to support MPLS.

Wherein, the p (provider) router: backbone routers in the service provider network are not directly connected to the CEs. The P device only needs to have basic MPLS forwarding capability.

(2) Example EVPL: EVPL instances are one-to-one with ACs, each with a service ID. The EVPL instance of the home PE corresponds to the EVPL instance of the remote PE one-to-one. Forwarding table entries are constructed by mutually sending EVPN routes with service IDs between PEs, and are used for forwarding or receiving service flows of different ES (Ethernet Segment) routes, so that point-to-point interconnection is realized.

(3) EVPN VPWS example: an EVPN VPWS instance is deployed on a boundary PE and has a service combination with common access or network side attributes, a BGP-EVPN (a routing type) address family determines the transceiving and filtering of a VPN Route based on RD (Route-distingguicher) and RT (Route-Target, which are important attributes carried by the VPNv4 Route and configured in each instance, and the PE distinguishes the Route between different VPNs depending on the RT attribute) attribute transfer Route.

(4) Tunnel: a network side MPLS tunnel or an SR (Segment Routing) tunnel.

Step S106, determining the association relationship between the VC interface of the MPLS VLL and the AC interface of the EVPN VPWS instance.

In an exemplary embodiment of the present disclosure, the working principle of the MPLS VLL is to allocate different VC interfaces to each point-to-point two-layer connection of a client, where a pair of VC interfaces simulates a virtual line, a VC label is marked on a PE device for a client two-layer data frame, and then the client two-layer data frame is sent to a destination PE, and when the client two-layer data frame is forwarded through an MPLS tunnel, one or more layers of outer labels may need to be added, and after a packet reaches the destination PE, the outer tunnel encapsulation and the VC label of the packet are stripped off, and the initial two-layer frame data is restored, and further, through an association relationship between the VC interfaces and the AC interfaces, smooth docking and cross-service data interaction between a first network and a second network are achieved.

Step S108, expanding the identifier of the first leaf node of the first network into a communication identifier of a two-layer cross-connection endpoint between the first network and the second network.

In an exemplary embodiment of the present disclosure, the communication identifier of the two-layer cross-connect endpoint, i.e. the new end.dx2l SID applied to the interworking between MPLS and SRv6, the PE can remove the IPv6 header and all extension headers according to this end.dx2l SID and forward to the corresponding AC interface or VC interface.

Step S110, the first leaf node and the first edge routing device implement, according to the association relationship and the communication identifier, L2VPN service data interaction between the first network and the second network.

Furthermore, the L2VPN cross-service communication method disclosed by the invention has strong expansibility, can support flexible intercommunication of a new technology and a traditional technology, and has random selection capability. New device networking and legacy devices can be smoothly interfaced through the present disclosure, facilitating network operations and continued evolution, especially when the devices are not fully supported SRv 6.

The following describes each step of the L2VPN cross-service communication method in detail with reference to fig. 2 to 12.

As shown in fig. 2, the implementing, by the first leaf node and the first edge routing device according to the association relationship and the communication identifier, the L2VPN service data interaction between the first network and the second network includes:

step S202, if it is detected that the first leaf node receives an L2VPN packet, determining a first identifier of a VC interface that transmits the L2VPN packet.

Step S204, determining a second identifier of the AC interface of the target EVPN VPWS instance corresponding to the first identifier according to the incidence relation.

Step S206, perform data conversion processing on the L2VPN data packet to obtain a first data packet after conversion processing.

Step S208, according to the second identifier, forwarding the first packet to the AC interface of the target EVPN VPWS instance through the VC interface corresponding to the first identifier.

In an exemplary embodiment of the present disclosure, after receiving an L2VPN packet, an AC interface of a target EVPN VPWS instance is determined through an association relationship between a VC interface and an AC interface, thereby implementing cross-service interworking of the L2VPN packet.

As shown in fig. 3, performing data conversion processing on the L2VPN packet to obtain a first converted packet includes:

step S302, when the first leaf node sends the L2VPN packet to the first edge routing device, writing a communication identifier of the two-layer cross connection endpoint at the stack bottom.

Step S304, the first edge routing device removes an IPv6 header and an extension header from the L2VPN packet according to the communication identifier of the two-layer cross-connect endpoint, so as to obtain the first data.

In an exemplary embodiment of the present disclosure, the IPv6 header includes, but is not limited to, a version number, a traffic class, a flow label, a payload length, a next header, a hop limit, a source address, and a destination address.

In an exemplary embodiment of the present disclosure, the IPv6 extension header includes, but is not limited to, an IPv6 header, a hop-by-hop option header, a destination option header (applied to the first destination of the IPv6 destination address field and additional destinations listed in the routing header), a routing header, a segment header, an authentication header, an ESP header, a destination option header (applied only to the final destination of the packet when using the routing header), and an upper layer header.

In an exemplary embodiment of the present disclosure, when a first leaf node device forwards an L2VPN packet to a first edge routing device to implement cross-service transmission, an association relationship between a VC ID and an AC interface is determined, and the first edge routing device removes an IPv6 header and an extension header from the L2VPN packet based on a communication identifier of a two-layer cross connection endpoint at the bottom of a stack, and forwards the packet to a corresponding AC interface.

As shown in fig. 4, the implementing, by the first leaf node and the first edge routing device, the L2VPN service data interaction between the first network and the second network according to the association relationship and the communication identifier further includes:

step S402, if it is detected that the first edge routing device receives the data packet sent by the AC interface of the EVPN VPWS instance, determining a third identifier of the AC interface that sends the data packet.

Step S404, determining, according to the association relationship, that a VC interface of the MPLS VLL corresponding to the third identifier is a fourth identifier.

Step S406, performing data conversion processing on the data packet sent by the AC interface to obtain a second data packet after conversion processing.

Step S408, according to the fourth identifier, forwarding the second packet to the VC interface of the MPLS VLL through the AC interface corresponding to the third identifier.

In an exemplary embodiment of the present disclosure, after receiving a data packet sent by an AC interface of an EVPN VPWS instance, a VC interface of a target MPLS VLL is determined through an association relationship between the VC interface and the AC interface, thereby implementing cross-service interworking of L2VPN data packets.

As shown in fig. 5, performing data conversion processing on the data packet sent by the AC interface to obtain a second data packet after conversion processing includes:

step S502, when the first edge routing device sends the data packet sent by the AC interface to the first leaf node, writing the communication identifier of the two-layer cross connection endpoint at the stack bottom.

Step S504, the first leaf node removes the IPv6 header and the extension header from the data packet sent to the AC interface according to the communication identifier of the two-layer cross-connect endpoint, so as to obtain the second data.

In an exemplary embodiment of the disclosure, when the first edge routing device forwards a packet sent by the EVPN VPWS instance to the first leaf node device to implement cross-service transmission, determining an association relationship between the VC ID and the AC interface, and the first leaf node device removes an IPv6 header and an extension header from the L2VPN packet based on the communication identifier of the two-layer cross-connect endpoint at the bottom of the stack and forwards the packet to the corresponding VC interface.

As shown in fig. 6, implementing the first L2VPN service of the first network based on the MPLS VLL includes:

step S602, controlling the terminal device to access a second leaf node of the first network through the first virtual link.

Step S604, the first L2VPN service is implemented between the first leaf node and the second leaf node through the MPLS VLL.

In an exemplary embodiment of the disclosure, the first leaf node and the second leaf node belong to the same spine-leaf topology network, and the spine-leaf topology network adds a corresponding switching network on a layer of horizontal network structure by adding the layer of horizontal network structure parallel to the longitudinal network structure of the backbone. All links of the spine-leaf topology network are used for forwarding traffic, and a common spanning tree protocol such as transparent interconnection of lots of links (TRILL) or Shortest Path Bridging (SPB) is also used. The TRILL and SPB protocols forward all connection traffic, but also maintain a loop-free network topology, similar to a routed network.

As shown in fig. 7, implementing the second L2VPN service of the second network based on the EVPN VPWS instance programmed at SRv6 includes:

step S702, the first leaf node accesses the second network.

Step S704, the second network further includes a second edge routing device, and the second L2VPN service is implemented between the first edge routing device and the second edge routing device through the EVPN VPWS instance programmed by the SRv 6.

In an exemplary embodiment of the present disclosure, the first leaf node is accessed to the second network, the EVPN VPWS instance programmed by the SRv6 between the first edge routing device and the second edge routing device is used to implement the second L2VPN service, and a network layer address of a link layer protocol and an interface is configured before the EVPN VPWS instance is configured, so that a network layer of an adjacent node is reachable.

As shown in fig. 8, the networking method of L2VPN cross-service communication includes the following steps:

(1) the user terminal 8062 is accessed to the U device 8064 by means of A VLAN, the U device 8064 is connected to the A-Leaf/STN-B8024 through the STN-A device 8028, and the L2VPN is implemented between the U device 8064 and the A-Leaf/STN-B8024 by means of an MPLS VLL, where A PW is A virtual link from A connection point to A point.

In addition, the STN 802 further includes an STN controller 8028, and the STN controller 8028 is configured to control data interaction and processing steps of each node in the STN 802.

In addition, the first Leaf node device of the present disclosure is B-Leaf/STN-B8022, the second Leaf node device of the present disclosure is a-Leaf/STN-B8024, and the STN 802 further includes a Spine/ER device 8026.

(2) A-Leaf/STN-B8024 is accessed into B-Leaf/STN-B8022 through Spine/ER 8026, L2VPN is realized between the A-Leaf/STN-B8024 and the B-Leaf/STN-B8022 through MPLS VLL, L2VPN splicing is carried out at two ends of the A-Leaf/STN-B8024, the B-Leaf/STN-B8022 is expanded into new END.DX2 SID, and the STN controller 8028 and the backbone network controller 8048 realize cross-service data interaction based on the END.DX2 SID.

(3) The B-Leaf/STN-B8022 accesses the PE device 8042 of the backbone network 804, and implements L2VPN with the cloud PE device 8044 by using SRv6 EVPN VPWS, where the PE device 8042 of the backbone network 804 is an implementation manner of the first edge routing device of the present disclosure, the backbone network 804 further includes a P device 8046 and a backbone network controller 8048, and the backbone network controller 8048 is configured to control data interaction and data processing of each node in the backbone network 804.

(4) Backbone network cloud PE8044 is interconnected with POP switch 8064 in cloud 806 through VLAN, POP switch 8064 is interconnected with cloud intranet 8062 through VXLAN.

The vxlan (virtual Extensible lan) is a network virtualization technology, and is based on an IP network and adopts a two-layer VPN technology in a "MAC in UDP" encapsulation form, so that the problem of expansion in deployment of large cloud computing is improved, and the vlan is an expansion of the vlan.

In addition, the VXLAN technology creates a large number of virtual extensible local area networks on the existing Network architecture by establishing a VXLAN tunnel, and different virtual extensible local area networks are identified by using VNI (virtual extensible local area Network Identifier), so that two-layer interconnection can be provided for scattered physical sites based on the existing service provider or enterprise IP Network, and service isolation can be provided for different tenants.

As shown in FIG. 9, the networking is a dual-homing network of CE1 and C2, the redundancy mode between PE1 and PE2 is single active and the E-Trunk function is configured. Since an E-Trunk function is deployed between PE1 and PE2, DF election is not triggered, the primary-secondary relationship between PE1 and PE2 is determined by the E-Trunk function configured between PE1 and PE2, and the protocol packet interaction flow under this scenario is as follows:

an EVPL instance 906 and an EVPN-VPWS instance 904 are configured on each PE device, where the EVPL instance 906 needs to be bound with the AC port 902 and the EVPN-VPWS instance 904, respectively, and each EVPL instance 906 needs to be configured with a local service ID and a remote service ID. After configuration is completed, forwarding association table entries for the AC port 902 and the EVPL instance 906 are generated on the local PE.

And the PE1 and the PE2 mutually transmit an ES route, and the ES route carries RD, RT, ESI and Source IP. After receiving the ES route, DF election is not triggered between PE1 and PE2, and the primary-standby relationship between PE1 and PE2 is determined by the E-Trunk configured between PE1 and PE 2.

PE1 and PE2 receive an EVI (Ethernet Virtualization interconnection) AD route from the opposite end, respectively, match the RT to cross to the corresponding EVPN-VPWS instance, and iterate MPLS or SRv4 tunnels according to the next hop information, or iterate SRv6 Tunnel according to SRv6 SID.

PE1 and PE2 send ES AD routes to PE3, carrying RD, RT, next hop, and multi-Active mode information (All-Active).

Wherein the end.dx2 SID represents a two-layer cross-connect SID (system identifier) for identifying an endpoint. The forwarding action corresponding to the end.dx2 SID is to remove the IPv6 header and its extension header, and then forward the remaining message to the egress interface corresponding to the SID, where the end.dx2 SID can be used in the EVPN VPWS scenario.

Based on the end.dxl 2 shown in fig. 9, the present disclosure further proposes an end.dxl 2 SID for cross-service interaction of L2VPN packets, as shown in fig. 10, which is a usage introduction of the end.dxl 2 SID. The STN/IPRAN network adopts a Spine-Leaf topology network, CE1 interacts with Spine/ER through MPLS VLL, B-Leaf/STN-B interacts with Spine/ER through IP protocol, PE3 and B-Leaf/STN-B are EVPN VPWS instance 1006 and EPVL instance 1008, and association between VC ID1002 and AC interface 1004 is established.

As shown in fig. 10 and 11, the L2VPN cross-service communication step includes:

in step S1102, it is determined whether SL is 0 and the stack bottom position, if so, step S1104 is executed, and if not, step S1106 is executed.

In step S1104, the header IPv6 and all extension headers are removed, and step S1108 is performed.

In step S1106, "ICMP Parameter protocol" is transmitted to the Source Address.

Step S1108, forwarding the ethernet frame to the AC interface associated with the end.dx2 SID.

Specifically, when the B-Leaf/STN-B receives an L2VPN packet from which the VC ID is "a", and sends the packet to PE3, an end.dx2 SID is added at the bottom of the stack, and PE3 removes the IPv6 header and all extension headers according to the end.dx2 SID, and forwards the packet to the corresponding AC interface.

As shown in fig. 10 and 12, the L2VPN cross-service communication step includes:

in step S1202, it is determined whether SL is 0 and the stack bottom position, if so, step S1104 is executed, and if not, step S1106 is executed.

In step S1204, the header IPv6 and all extension headers are removed, and step S1208 is performed.

In step S1206, "ICMP Parameter protocol" is transmitted to the Source Address.

And step S1208, forwarding the Ethernet frame to the VC ID associated with the END.DX2L SID.

Specifically, when the PE3 receives a packet from the AC interface and sends the packet to the B-Leaf/STN-B, the end.dxd2l SID added at the bottom of the stack, and the B-Leaf/STN-B removes the IPv6 header and all extension headers according to the end.dx2l SID, forwards the packet to the corresponding VC interface according to the association relationship between the EVPN VPWS instance and the VC ID, and directs the traffic to enter the MPLS L2 VPN.

Corresponding to the method embodiment, the present disclosure further provides an L2VPN cross-service communication apparatus, which may be used to execute the method embodiment.

Fig. 13 is a block diagram of an L2VPN cross-service communication device in an exemplary embodiment of the present disclosure.

Referring to fig. 13, the L2VPN cross-service communication device 1300 may include:

a first communication module 1302, configured to implement a first L2VPN service of a first network based on an MPLS VLL.

A second communication module 1304, configured to implement a second L2VPN service of a second network based on the EVPN VPWS instance programmed by SRv6, where a data link is provided between a first leaf node of the first network and a first edge routing device of the second network.

An associating module 1306, configured to determine an association relationship between a VC interface of the MPLS VLL and an AC interface of the EVPN VPWS instance.

An expansion module 1308, configured to expand the identifier of the first leaf node of the first network to be a communication identifier of a two-layer cross connection endpoint between the first network and the second network.

An interaction module 1310, configured to implement, by the first leaf node and the first edge routing device, L2VPN service data interaction between the first network and the second network according to the association relationship and the communication identifier.

In an exemplary embodiment of the disclosure, the interaction module 1310 is further configured to: if the first leaf node is detected to receive the L2VPN data packet, determining a first identifier of a VC interface for sending the L2VPN data packet; determining a second identifier of an AC interface of a target EVPN VPWS instance corresponding to the first identifier according to the incidence relation; performing data conversion processing on the L2VPN data packet to obtain a first data packet after conversion processing; and forwarding the first data packet to an AC interface of the target EVPN VPWS instance through a VC interface corresponding to the first identifier according to the second identifier.

In an exemplary embodiment of the disclosure, the interaction module 1310 is further configured to: when the first leaf node sends the L2VPN data packet to the first edge routing device, writing a communication identifier of the two-layer cross connection end point at the stack bottom; and the first edge routing equipment removes an IPv6 header and an extension header from the L2VPN data packet according to the communication identification of the two layers of cross connection endpoints to obtain the first data.

In an exemplary embodiment of the disclosure, the interaction module 1310 is further configured to: if the first edge routing equipment is detected to receive the data packet sent by the AC interface of the EVPN VPWS instance, determining a third identifier of the AC interface for sending the data packet; determining that a VC interface of the MPLS VLL corresponding to the third identifier is a fourth identifier according to the incidence relation; performing data conversion processing on the data packet sent by the AC interface to obtain a second data packet after conversion processing; and forwarding the second data packet to a VC interface of the MPLS VLL through an AC interface corresponding to the third identifier according to the fourth identifier.

In an exemplary embodiment of the disclosure, the interaction module 1310 is further configured to: when the first edge routing equipment sends the data packet sent by the AC interface to the first leaf node, writing a communication identifier of the two-layer cross connection endpoint at the stack bottom; and the first leaf node removes an IPv6 header and an extension header from a data packet sent by the AC interface according to the communication identification of the two-layer cross connection endpoint so as to obtain the second data.

In an exemplary embodiment of the disclosure, the first communication module 1302 is further configured to: controlling the terminal equipment to access a second leaf node of the first network through a first virtual link; and the first L2VPN service is realized between the first leaf node and the second leaf node through the MPLS VLL.

In an exemplary embodiment of the present disclosure, the second communication module 1304: the first leaf node accessing the second network; the second network further comprises a second edge routing device, and the second L2VPN service is implemented between the first edge routing device and the second edge routing device through the SRv6 programmed EVPN VPWS instance.

Since the functions of the apparatus 1300 have been described in detail in the corresponding method embodiments, the disclosure is not repeated herein.

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

An electronic device 1400 according to this embodiment of the invention is described below with reference to fig. 14. The electronic device 1400 shown in fig. 14 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 14, the electronic device 1400 is embodied in the form of a general purpose computing device. The components of the electronic device 1400 may include, but are not limited to: the at least one processing unit 1410, the at least one memory unit 1420, and the bus 1430 that couples the various system components including the memory unit 1420 and the processing unit 1410.

Wherein the storage unit stores program code that is executable by the processing unit 1410, such that the processing unit 1410 performs steps according to various exemplary embodiments of the present invention described in the above section "exemplary methods" of the present specification. For example, the processing unit 1410 may perform a method as shown in the embodiments of the present disclosure.

The storage unit 1420 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)14201 and/or a cache memory unit 14202, and may further include a read only memory unit (ROM) 14203.

Storage unit 1420 may also include a program/utility 14204 having a set (at least one) of program modules 14205, such program modules 14205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 1430 may be any type of bus structure including a memory cell bus or memory cell controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 1400 may also communicate with one or more external devices 1440 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 1400, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 1400 to communicate with one or more other computing devices. Such communication can occur via an input/output (I/O) interface 1450. Also, the electronic device 1400 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 1460. As shown, the network adapter 1460 communicates with the other modules of the electronic device 1400 via the bus 1430. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 1400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.

The program product for implementing the above method according to an embodiment of the present invention may employ a portable compact disc read only memory (CD-ROM) and include program codes, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A method for cross-service communication of L2 VPNs is characterized by comprising the following steps:

implementing a first L2VPN service of a first network based on an MPLS VLL;

implementing a second L2VPN service of a second network based on an EVPN VPWS instance programmed by SRv6, wherein a data link is arranged between a first leaf node of the first network and a first edge routing device of the second network;

determining an association relationship between a VC interface of the MPLS VLL and an AC interface of the EVPN VPWS instance;

expanding the identifier of a first leaf node of the first network into a communication identifier of a two-layer cross-connection endpoint between the first network and the second network;

and the first leaf node and the first edge routing equipment realize the L2VPN service data interaction between the first network and the second network according to the incidence relation and the communication identifier.

2. The L2VPN cross-traffic communication method according to claim 1, wherein the first leaf node and the first edge routing device implementing L2VPN traffic data interaction between the first network and the second network according to the association relationship and the communication identification comprises:

if the first leaf node is detected to receive the L2VPN data packet, determining a first identifier of a VC interface for sending the L2VPN data packet;

determining a second identifier of an AC interface of a target EVPN VPWS instance corresponding to the first identifier according to the incidence relation;

performing data conversion processing on the L2VPN data packet to obtain a first data packet after conversion processing;

and forwarding the first data packet to an AC interface of the target EVPN VPWS instance through a VC interface corresponding to the first identifier according to the second identifier.

3. The L2VPN cross-service communication method according to claim 2, wherein performing data conversion processing on the L2VPN packet to obtain a first converted packet comprises:

when the first leaf node sends the L2VPN data packet to the first edge routing device, writing a communication identifier of the two-layer cross connection end point at the stack bottom;

and the first edge routing equipment removes an IPv6 header and an extension header from the L2VPN data packet according to the communication identification of the two layers of cross connection endpoints to obtain the first data.

4. The L2VPN cross-traffic communication method according to claim 1, wherein the first leaf node and the first edge routing device implementing L2VPN traffic data interaction between the first network and the second network according to the association relationship and the communication identification further comprises:

if the first edge routing equipment is detected to receive the data packet sent by the AC interface of the EVPN VPWS instance, determining a third identifier of the AC interface for sending the data packet;

determining a fourth identifier of a VC interface of the MPLS VLL corresponding to the third identifier according to the incidence relation;

performing data conversion processing on the data packet sent by the AC interface to obtain a second data packet after conversion processing;

and forwarding the second data packet to a VC interface of the MPLS VLL through an AC interface corresponding to the third identifier according to the fourth identifier.

5. The L2VPN cross-service communication method according to claim 4, wherein the performing data conversion processing on the data packet sent by the AC interface to obtain a second data packet after conversion processing comprises:

when the first edge routing equipment sends the data packet sent by the AC interface to the first leaf node, writing a communication identifier of the two-layer cross connection endpoint at the stack bottom;

and the first leaf node removes an IPv6 header and an extension header from a data packet sent by the AC interface according to the communication identification of the two-layer cross connection endpoint so as to obtain the second data.

6. The L2VPN cross-service communication method of any one of claims 1-5, wherein implementing the first L2VPN service for the first network based on an MPLS VLL comprises:

controlling the terminal equipment to access a second leaf node of the first network through a first virtual link;

and the first L2VPN service is realized between the first leaf node and the second leaf node through the MPLS VLL.

7. The L2VPN cross-service communication method of any one of claims 1-5, wherein implementing the second L2VPN service of the second network based on the SRv6 programmed EVPN VPWS instance comprises:

the first leaf node accessing the second network;

the second network further comprises a second edge routing device, and the second L2VPN service is implemented between the first edge routing device and the second edge routing device through the SRv6 programmed EVPN VPWS instance.

8. An L2VPN cross-service communication device, comprising:

the first communication module is used for realizing a first L2VPN service of a first network based on the MPLS VLL;

a second communication module, configured to implement a second L2VPN service of a second network based on an EVPN VPWS instance programmed by SRv6, where a data link is provided between a first leaf node of the first network and a first edge routing device of the second network;

an association module, configured to determine an association relationship between a VC interface of the MPLS VLL and an AC interface of the EVPN VPWS instance;

the expansion module is used for expanding the identifier of the first leaf node of the first network into a communication identifier of a two-layer cross connection endpoint between the first network and the second network;

and the interaction module is used for realizing the L2VPN service data interaction between the first network and the second network by the first leaf node and the first edge routing equipment according to the incidence relation and the communication identifier.

9. An electronic device, comprising:

a memory; and

a processor coupled to the memory, the processor configured to perform the L2VPN cross-traffic communication method of any of claims 1-7 based on instructions stored in the memory.

10. A computer-readable storage medium on which a program is stored, the program, when executed by a processor, implementing the L2VPN cross-service communication method according to any one of claims 1 to 7.