WO2015165311A1 - Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur - Google Patents

Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur Download PDF

Info

Publication number
WO2015165311A1
WO2015165311A1 PCT/CN2015/074492 CN2015074492W WO2015165311A1 WO 2015165311 A1 WO2015165311 A1 WO 2015165311A1 CN 2015074492 W CN2015074492 W CN 2015074492W WO 2015165311 A1 WO2015165311 A1 WO 2015165311A1
Authority
WO
WIPO (PCT)
Prior art keywords
label
routing message
identifier
bearer network
data packet
Prior art date
Application number
PCT/CN2015/074492
Other languages
English (en)
Chinese (zh)
Inventor
张军林
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2015165311A1 publication Critical patent/WO2015165311A1/fr

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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a method for transmitting a data message and a PE device.
  • EVPN Ethernet Virtual Private Network
  • BGP Border Gateway Protocol
  • MPLS Multi-Protocol Label Switching
  • a customer site (Site) located in a different area is connected to a PE device on the bearer network, for example, an IP (Internet Protocol) network or a PE (Provider Edge) device in the MPLS network, on each PE device.
  • IP Internet Protocol
  • PE Provide Edge
  • EVI EVI
  • the EVPN carries the Ethernet packets between the local site and the remote site through the public network tunnel or the private network tunnel between the PEs.
  • a P2MP LSP Point to Multipoint Label Switch Path
  • MP2MP Multipoint Point to Multipoint Label Switch Path
  • BUM Multipoint to Multipoint Label Switch Path
  • the MP2MP LSP can be an MPLS-based MP2MP tunnel, and is generally used as a public network multicast tunnel in an MPLS network, hereinafter referred to as an MP2MP tunnel.
  • Each MP2MP LSP has a root node and a number of leaf nodes.
  • the MP2MP tunnel is bidirectional in the establishment process. When the leaf node establishes a label forwarding channel to the upstream node to the root node, the upstream node and the leaf node also Establish a reverse label switching channel. BUM traffic between customer sites can be carried out through the same MP2MP tree Load, that is, the MP2MP tunnel is bidirectional. Therefore, compared with the P2MP tunnel, the MP2MP tunnel can reduce the public network multicast state table and forwarding table.
  • a link between a CE (Customer Edge) device and multiple PEs can be bundled into one Ethernet trunk, also called Ethernet segment (ES).
  • Ethernet segment also called Ethernet segment (ES).
  • a link between a CE device and a PE device 1 and a link between the CE device and the PE device 2 are bundled into an Ethernet trunk, that is, a link between the CE device and the PE device 1 and a CE device.
  • the link between PE devices 2 is bundled into an Ethernet trunk.
  • a data message (eg, BUM traffic) sent from the CE device to the PE device can be forwarded via the PE device 1 or the PE device 2.
  • the BUM traffic is sent from the CE device to the PE device 1, and the PE device 1 needs to send the BUM traffic received from the client side to all other PE devices belonging to the same EVPN. For example, after the PE device 2 receives the BUM traffic sent from the PE device 1, the PE device 2 forwards the BUM traffic to the local port connected to the CE device. In this way, the BUM traffic sent from the CE device to the PE device 1 is forwarded back to the CE device via the PE device 2, so that the data message is transmitted back on the client side.
  • the embodiment of the invention provides a method for transmitting a data message and a PE device, which can solve the problem of data packet round-trip transmission on the client side.
  • the first aspect provides a method for transmitting a data packet, where the first PE device receives a data packet sent by the CE device by connecting an ES between the first PE device and the CE device, where the A PE device is a PE device of a bearer network of an Ethernet virtual private network VPN; the first PE device encapsulates the data packet by using a label of an ES connected to the first PE device and a label of an MP2MP tunnel in the bearer network, where Each of the at least one ES connected to the bearer network is connected between a CE device and a plurality of PE devices of the bearer network, and a label of each ES of the at least one ES is allocated by a root node of the MP2MP tunnel.
  • the first PE device sends the data packet through the MP2MP tunnel.
  • the first PE device is the MP2MP The root node of the tunnel
  • the method further includes: the first PE device receiving a first routing message sent by each of the at least one second PE device of the bearer network, where the first routing message carries the first route The identifier of the ES connected to the second PE device of the message; the first PE device assigns a label to the ES connected to each of the at least one second PE device; the first PE device to the at least one second PE device Sending a second routing message, where the second routing message carries the identifier information of the root of the MP2MP tunnel, the identifier of the ES connected to each PE device in the at least one second PE device, and the identifier of the ES of the at least one second PE device The label assigned by the ES of each PE device connected.
  • the first PE device adopts the ES connected by the first PE device
  • the label and the label of the MP2MP tunnel in the bearer network encapsulate the data packet, including: the label of the ES connected by the first PE device, the label of the MP2MP tunnel, and the Ethernet VPN (Virtual Private Network)
  • the label of the broadcast domain of the virtual private network encapsulates the data packet, wherein the label of the broadcast domain of the Ethernet VPN is used to indicate that the data packet belongs to the broadcast domain of the Ethernet VPN, and at least one Ethernet VPN connected by the bearer network
  • the label of the broadcast domain is assigned by the root node of the MP2MP tunnel.
  • the first PE device is a root node of the MP2MP tunnel
  • the method further includes: the first PE device receiving the bearer network At least one third routing message sent by each of the at least one second PE device, the third routing message carrying an identifier of a broadcast domain of the Ethernet VPN connected by the second PE device that sends the third routing message;
  • the first PE device allocates a label to a broadcast domain of an Ethernet VPN connected to each of the at least one second PE device;
  • the first PE device sends a fourth routing message to the at least one second PE device, where the The fourth routing message carries the identification information of the root of the MP2MP tunnel, the identifier of the broadcast domain of the Ethernet VPN connected to each PE device in the at least one second PE device, and each of the at least one PE second PE device.
  • the first PE device adopts an ES label of the first PE device and an interface in the bearer network.
  • the label of the MP2MP tunnel encapsulates the data packet, and the first PE device uses the label of the ES connected to the first PE device as an inner label, and the label of the MP2MP tunnel encapsulates the data packet as an outer label.
  • the data packet is a broadcast, an unknown unicast, or a multicast (BUM) packet.
  • the second aspect provides a method for transmitting a data packet, where the second PE device receives a data packet sent by the first PE device through an MP2MP tunnel in the bearer network in the Ethernet virtual private network VPN, where the data packet
  • the label of the ES of the first PE and the label of the MP2MP tunnel are used, where the first PE device and the second PE device are PE devices of the bearer network, and each of the at least one ES connected by the bearer network
  • the ES is connected between a customer edge (CE) device and a plurality of PE devices of the bearer network, and a label of each ES of the at least one ES is allocated by a root node of the MP2MP tunnel;
  • the second PE device solution Encapsulating the data packet to obtain the label of the ES connected to the first PE device and the label of the MP2MP tunnel; the second PE device determining whether the label is based on the label of the ES connected to the first PE device and the label of the MP2MP tunnel
  • the data packet is sent on the
  • the second PE device determines, according to the label of the ES connected to the first PE device and the label of the MP2MP tunnel, whether the ES is connected to the second PE device. And sending, by the second PE device, the identifier of the ES connected to the first PE device according to the label of the ES connected to the first PE device and the label of the MP2MP tunnel; by comparing the first PE device connection The identifier of the ES is connected to the identifier of the ES connected to the second PE device, and determines whether the data packet is sent on the ES connected to the second PE device, where the method further includes: the ES connected to the first PE device When the identifier of the ES is the same as the identifier of the ES to which the second PE device is connected, the second PE device does not send the data packet on the ES connected to the second PE device; the identifier of the ES connected to the first PE device is When the identifier of the ES connected to the second PE device
  • the first PE device is a root of the MP2MP tunnel
  • the method further includes: the second PE device sends a first routing message in the bearer network, where the first routing message carries an identifier of an ES connected by the second PE device; and the second PE device receives the first PE a second routing message sent by the device, where the second routing message carries the identifier information of the root of the MP2MP tunnel, the identifier of the ES connected to each PE device in the at least one second PE device of the bearer network, and the at least one A label assigned by the ES of each PE device connected to the second PE device.
  • the data packet further includes a label of the broadcast domain of the Ethernet VPN, where the data packet belongs to the Ethernet VPN.
  • the broadcast domain, and the label of the broadcast domain of the at least one Ethernet VPN of the bearer network is allocated by the root node of the MP2MP tunnel.
  • the first PE device is a root node of the MP2MP tunnel
  • the method further includes: the second PE device is on the bearer network Sending a third routing message, where the third routing message carries the identifier of the Ethernet VPN broadcast domain that is connected to the second PE device, and the second PE device receives the fourth routing message that is sent by the first PE device, where the fourth routing message carries the The identification information of the root of the MP2MP tunnel, the identifier of the broadcast domain of the Ethernet VPN connected to each PE device in the at least one second PE device, and each PE device in the at least one second PE device The label assigned by the broadcast domain of the connected Ethernet VPN.
  • the data packet is a broadcast, an unknown unicast, or a multicast BUM packet.
  • a third aspect provides a method for allocating a label, the first PE device receiving a first routing message sent by each of the at least one second PE device, where the first routing message carries the first routing message.
  • the identifier of the ES connected to the second PE device, the first PE device and the at least one second PE device being PE devices of the bearer network of the Ethernet virtual private network VPN, and each ES of the at least one ES connected by the bearer network Connecting between a customer edge (CE) device and a plurality of PE devices of the bearer network; the first PE device assigning a label to an ES connected to each of the at least one second PE device; the first PE The device sends the first to the at least one second PE device a routing message, the second routing message carrying the identifier of the root of the MP2MP tunnel of the bearer network, the identifier of the ES connected to each PE device in the at least one second PE device, and the at least one second PE device The label assigned by the ES connected to each PE device in the middle, and the
  • the method further includes: the first PE device receiving, by the at least one third routing message sent by each of the at least one second PE device, the third The routing message carries the identifier of the broadcast domain of the Ethernet VPN connected to the second PE device that sends the third routing message; the first PE device is the broadcast domain of the Ethernet VPN connected to each of the at least one second PE device Allocating a label; the first PE device sends a fourth routing message to the at least one second PE device, where the fourth routing message carries the identifier of the first PE device, and each PE device in the at least one second PE device is connected.
  • a fourth aspect, a method for allocating a label includes: sending, by a second PE device, a first routing message in a bearer network of an Ethernet virtual private network VPN, where the first routing message carries an identifier of an ES connected by the second PE device
  • Each of the at least one ES connected to the bearer network is connected between a customer edge (CE) device and a plurality of PE devices of the bearer network; the second PE device receives the second route sent by the first PE device a message that the second routing message carries the identifier information of the root of the MP2MP tunnel of the bearer network, the identifier of the ES connected to each PE device in the at least one second PE device, and each of the at least one second PE device A label assigned by the ES connected to the PE device, wherein the first PE device and the at least one second PE device are PE devices of a bearer network of an Ethernet virtual private network VPN, and the first PE device is a root node of the MP2MP tunnel.
  • the method further includes: the second PE device sends a third routing message on the bearer network, where the third routing message carries the Ethernet VPN connected by the second PE device The identifier of the broadcast domain; the second PE device receives the fourth routing message from the first PE device, where the fourth routing message carries the identifier information of the root of the MP2MP tunnel, and at least one second PE device in the bearer network The identity of the broadcast domain of the Ethernet VPN that each PE device is connected to And a label allocated for a broadcast domain of the Ethernet VPN connected to each of the at least one second PE device.
  • the fifth aspect provides a PE device, including: a receiving module, configured to receive, by the CE device, a data packet sent by an ES connected between the PE device and the CE device, where the PE device is an Ethernet virtual private network.
  • a PE device of the bearer network of the VPN configured to encapsulate the data packet by using a label of an ES connected to the PE device and a label of an MP2MP tunnel in the bearer network, where at least one ES of the bearer network is connected
  • Each ES is connected between a CE device and a plurality of PE devices of the bearer network, and a label of each ES of the at least one ES is allocated by a root node of the MP2MP tunnel; and a sending module is configured to pass the MP2MP The tunnel sends the data packet.
  • the PE device is a root node of the MP2MP tunnel, and the PE device further includes: an allocating module, where the receiving module further receives the at least one second PE device of the bearer network. a first routing message sent by each of the PE devices, where the first routing message carries an identifier of an ES connected to the second PE device that sends the first routing message; the allocation module is each of the at least one second PE device An ES distribution label connected to the PE device; the sending module sends a second routing message to the at least one second PE device, where the second routing message carries the identifier information of the root of the MP2MP tunnel, and the at least one second PE device The identifier of the ES connected to each PE device and the label assigned to the ES connected to each of the at least one second PE device.
  • the encapsulating module adopts a label of an ES connected by the PE device,
  • the label of the MP2MP tunnel and the label of the broadcast domain of the Ethernet VPN encapsulate the data packet, where the label of the broadcast domain of the Ethernet VPN is used to indicate that the data packet belongs to the broadcast domain of the Ethernet VPN, and at least the bearer network is connected.
  • the label of the broadcast domain of an Ethernet VPN is assigned by the root node of the MP2MP tunnel.
  • the PE device is a root node of the MP2MP tunnel, and the PE device further includes: an allocating module, where the receiving module further receives the bearer Each of the at least one second PE device in the network sends the Having a third routing message, the third routing message carrying an identifier of a broadcast domain of the Ethernet VPN connected to the second PE device that sends the third routing message; the allocation module is each PE of the at least one second PE device And the at least one second PE device sends a fourth routing message, where the fourth routing message carries the identification information of the root of the MP2MP tunnel, the at least one second An identifier of a broadcast domain of an Ethernet VPN connected to each PE device in the PE device and a label allocated to a broadcast domain of the Ethernet VPN connected to each of the at least one PE second PE device.
  • the PE device uses the label of the ES connected by the PE device as an inner label, and the label of the MP2MP tunnel as an outer label. Encapsulate the data packet.
  • the data packet is a broadcast, an unknown unicast, or a multicast BUM packet.
  • the sixth aspect provides a PE device, including: a receiving module, configured to receive a data packet sent by the first PE device through an MP2MP tunnel in a bearer network in an Ethernet VPN, where the data packet adopts the first PE connection
  • the label of the ES and the label of the MP2MP tunnel, the first PE device and the PE device are PE devices of the bearer network, and each ES of the at least one ES connected to the bearer network is connected to a CE device and the bearer A label of each of the at least one ES is allocated by a root node of the MP2MP tunnel, and a decapsulation module is configured to decapsulate the data packet to obtain the first PE device.
  • the label of the connected ES and the label of the MP2MP tunnel configured to determine whether to send the data packet on the ES connected to the PE device according to the label of the ES connected by the first PE device and the label of the MP2MP tunnel.
  • the determining module determines, according to the label of the ES connected by the first PE device and the label of the MP2MP tunnel, the identifier of the ES connected by the first PE device, and compares The identifier of the ES connected to the first PE device and the identifier of the ES connected to the PE device, determining whether to send the data packet on the ES connected to the PE device, where the PE device further includes: a sending module, configured to When the identifier of the ES to which the first PE device is connected is the same as the identifier of the ES to which the PE device is connected, the datagram is not sent on the ES connected to the PE device. When the identifier of the ES connected to the first PE device is different from the identifier of the ES connected to the PE device, the data packet is sent on the ES connected to the PE device.
  • the first PE device is a root node of the MP2MP tunnel
  • the PE device further includes: a sending module, configured to send a first routing message in the bearer network, where the first routing message carries an identifier of an ES connected by the PE device; the receiving module further receives a second sent by the first PE device a routing message, the second routing message carrying the identifier information of the root of the MP2MP tunnel, the identifier of the ES connected to each PE device in the at least one second PE device of the bearer network, and the identifier of the ES of the at least one second PE device The label assigned by the ES of each PE device connected.
  • the data packet further includes a label of the broadcast domain of the Ethernet VPN, where the data packet belongs to the Ethernet VPN.
  • the broadcast domain, and the label of the broadcast domain of the at least one Ethernet VPN of the bearer network is allocated by the root node of the MP2MP tunnel.
  • the first PE device is a root node of the MP2MP tunnel
  • the PE device further includes: a sending module, where the bearer is used in the bearer
  • the third routing message is sent on the network, and the third routing message carries the identifier of the broadcast domain of the Ethernet VPN that is connected to the PE device.
  • the receiving module further receives the first routing message from the first PE device, where the fourth routing message carries the MP2MP.
  • the identification information of the root of the tunnel, the identifier of the broadcast domain of the Ethernet VPN connected to each PE device in the at least one second PE device, and the connection of each PE device in the at least one second PE device The Ethernet domain's broadcast domain is assigned a label.
  • the data packet is a broadcast, an unknown unicast, or a multicast BUM packet.
  • the seventh aspect provides a PE device, including: a receiving module, configured to receive a first routing message sent by each of the at least one second PE device, where the first routing message carries the first routing message
  • the identifier of the ES connected to the second PE device, the PE device and the at least one second PE device being the PE device of the Ethernet network of the Ethernet VPN, and the at least one ES connected by the bearer network
  • Each of the ESs is connected between a CE device and a plurality of PE devices of the bearer network;
  • an allocating module is configured to allocate a label to an ES connected to each of the at least one second PE device;
  • the receiving module further receives at least one third routing message that is sent by each of the at least one second PE device, where the third routing message carries the first The identifier of the broadcast domain of the Ethernet VPN connected to the second PE device of the third routing message; the allocation module further assigns a label to the broadcast domain of the Ethernet VPN connected to each of the at least one second PE device; the sending module further Transmitting, to the at least one second PE device, a fourth routing message, where the fourth routing message carries an identifier of the PE device, an identifier of a broadcast domain of an Ethernet VPN connected to each PE device in the at least one second PE device, and A label allocated by a broadcast domain of an Ethernet VPN connected to each of the at least one PE second PE device.
  • the eighth aspect provides a sending module, configured to send, in a bearer network of an Ethernet VPN, a first routing message, where the first routing message carries an identifier of an ES connected by the PE device, where the bearer network is connected to at least one ES Each ES is connected between a CE device and a plurality of PE devices of the bearer network; the receiving module is configured to receive a second routing message sent by the first PE device, where the second routing message carries the MP2MP tunnel of the bearer network.
  • the sending module further sends a third routing message on the bearer network, where the third routing message carries an identifier of an Ethernet VPN broadcast domain that is connected to the PE device; the receiving module And receiving, by the first PE device, a fourth routing message, where the fourth routing message carries the identifier information of the root of the MP2MP tunnel, and the Ethernet VPN connected to each PE device in the at least one second PE device in the bearer network.
  • the PE device may encapsulate the data packet received from the customer edge device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet.
  • the data packet is forwarded according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES, so that the data packet can be prevented from being forwarded back to the client edge device that sends the data packet, thereby solving the data packet appearing on the client side.
  • the issue of ⁇ ⁇ transmission The issue of ⁇ ⁇ transmission.
  • FIG. 1 is a schematic structural diagram of an Ethernet VPN according to an embodiment of the present invention.
  • FIG. 2 is a schematic flow chart of a method of transmitting a data message according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of a method for transmitting a data message according to another embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for transmitting a data message according to another embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for transmitting a data message according to another embodiment of the present invention.
  • FIG. 6 is a system architecture diagram of an Ethernet VPN according to another embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a method of transmitting a data message according to still another embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a method of transmitting a data message according to still another embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a PE device according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a PE device according to another embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of a PE device according to another embodiment of the present invention.
  • FIG. 12 is a schematic structural diagram of a PE device according to another embodiment of the present invention.
  • FIG. 13 is a schematic structural diagram of a PE device according to another embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a PE device according to another embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a PE device according to another embodiment of the present invention.
  • FIG. 16 is a schematic structural diagram of a PE device according to another embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of an Ethernet VPN 100 according to an embodiment of the present invention.
  • the embodiment of FIG. 1 illustrates the Ethernet VPN 100 as an EVPN-A.
  • Customer sites located in different regions in EVPN-A communicate through the bearer network 110.
  • the bearer network 110 can be, for example, an IP/MPLS bearer network.
  • the bearer network 110 can include a PE device 110a, a PE device 110b, a PE device 110c, a PE device 110d, and an intermediate network device 110e.
  • EVPN-A corresponds to one EVI (EVPN Instance) on each PE device.
  • the customer site a of EVPN-A includes a CE device 120a and a client device 130a
  • the customer site b of the EVPN-A includes a CE device 120b and a client device 130b.
  • the embodiment of the present invention does not limit the number of EVPNs in the communication system, the number of client sites of each EVPN, and the number of PE devices in the bearer network.
  • client device 130a is coupled to CE device 120a.
  • Each client device can correspond to a MAC address.
  • the CE device 120a is connected to the PE device 110a and the PE device 110b through an ES (Ethernet Segment) 1.
  • the CE device 120b is connected to the PE device 110c and the PE device 110d through ES2.
  • ES1 and ES2 are also called multi-homed links, that is, one CE device is connected to multiple PE devices through an ES.
  • the PE device in the bearer network is used to learn the MAC (Media Access Control) address of the local and remote client sites. For example, the PE device completes MAC learning of the local client device in the data plane, and exchanges MAC routes through BGP signaling to complete MAC learning of the remote client device.
  • the PE device is also used for packet forwarding. For example, the packets received from the local client site are forwarded to other local client endpoints and other PE devices, and the packets received from other PE devices are forwarded. To a local customer site.
  • a multicast tree (for example, an MP2MP tunnel) can be used to carry BUM traffic.
  • the PE device 110a is the root node of the M2MP tunnel
  • the PE device 110d, the PE device 110c, and the PE device 110b are leaf nodes of the M2MP tunnel.
  • BUM traffic sent by client device 130a may be transmitted to client device 130b via the M2MP tunnel described above.
  • the BUM traffic sent by the client device of the client site connected to the leaf node can also be transmitted to the client device of the client site connected to the root node or other leaf nodes through the above M2MP tunnel.
  • the client device 130a is connected to the CE device 120a, and the CE device 120a is respectively connected to the PE device 110a and the PE device 110b through a multi-homed link (for example, ES1), that is, between the CE device 120a and the PE device 110a.
  • ES1 multi-homed link
  • the link and the link between the CE device 120a and the PE device 110b are bundled into an Ethernet trunk, also called ES, that is, a set of links between different PE devices and the same CE device, and a set of these links It can be represented by the same identifier, for example, by Ethernet Segment Identifier (ESI).
  • ESI Ethernet Segment Identifier
  • the BUM traffic sent by the CE device 120a may be forwarded via the PE device 110a or may be forwarded via the PE device 110b, depending on the algorithm for selecting the physical link when the Ethernet TRUNK sends the data message.
  • the PE device 110a needs to forward the BUM traffic to other PE devices in the EVPN network (for example, EVPN-A), for example, PE device 110b, PE device 110c, and PE device 110d.
  • EVPN-A for example, PE device 110b, PE device 110c, and PE device 110d.
  • the BUM traffic may be forwarded back to the local CE device 120a to form a triangular loop on the client side, causing a round-trip transmission of the BUM traffic.
  • a scheme of allocating a global label may be adopted, that is, all PE devices in the bearer network may apply for an ES label (also referred to as an ESI label) or a VPN label to a centrally controlled label manager (Label Manager).
  • the label manager then advertises the label to all PE devices.
  • the PE device needs to reserve label space for the ESI label or VPN label.
  • such a solution requires not only a centrally controlled tag manager, but also the same tag space on all PE devices, plus an additional signaling burden.
  • the scheme used to interpret the inner label in the root node label space identified by the outer P2MP tunnel label is not applicable to the MP2MP tunneling technology.
  • the MP2MP tunnel is bidirectional.
  • the data packet may be sent from the root node or from the non-root node.
  • the egress PE device cannot identify the ingress PE device based on the outer MP2MP tunnel label. Therefore, the inner label cannot be interpreted within the label space of the ingress PE device.
  • the embodiment of the present invention provides a method for transmitting data packets in an Ethernet VPN and a PE device, which can avoid formation on the client side when using an MP2MP tunnel to carry data packets (BUM packets). Triangle loop.
  • FIG. 2 is a schematic flow chart of a method of transmitting a data message according to an embodiment of the present invention.
  • the method of Figure 2 can be performed by the PE device of Figure 1.
  • the first PE device receives the data packet sent by the CE device to the ES between the first PE device and the CE device, where the first PE device is the PE device of the Ethernet VPN bearer network.
  • an Ethernet VPN can include multiple customer sites located in different geographic regions, each of which can be composed of a client device and a CE device.
  • the client device can communicate with the PE device in the bearer network through the CE device.
  • the links between different PEs and the same CE can be bundled into one TRUNK, also known as ES.
  • the CE device can forward the data packets sent by the client device to the PE device through the ES.
  • the ES is also called a multi-homed link of the Ethernet VPN network.
  • the multi-homed link is connected between the CE device of the Ethernet VPN network and the multiple PEs of the bearer network.
  • the first PE device is one of the multiple PEs.
  • the data packet can be broadcast, unknown unicast or multicast BUM message or BUM traffic.
  • the first PE device uses the label of the ES connected to the first PE device and the label encapsulated data packet of the MP2MP tunnel in the bearer network, where each ES of the at least one ES connected to the bearer network is connected to a CE device and Between the multiple PE devices of the bearer network, the label of each ES in at least one ES is allocated by the root node of the MP2MP tunnel.
  • the root node of the MP2MP tunnel can uniformly allocate corresponding labels to different ESs in the Ethernet VPN, and send labels of different ESs to the PEs of the bearer network.
  • each PE device can store the mapping or mapping of the identifiers of all ESs to the labels assigned by the root node to the ES. relationship.
  • the identifier of the ES is called ESI, and the label of the ES can also be called an ESI label.
  • the first PE device sends a data packet by using an MP2MP tunnel.
  • the client device sends a data packet to the bearer network through the local CE device and through the ES between the CE device and the first PE device.
  • the first PE device may determine the root node of the MP2MP tunnel according to the tunnel label of the MP2MP tunnel to be used, and determine that the root node of the MP2MP tunnel is an ES. The assigned label.
  • the first PE device encapsulates the data packet by using the label of the ES and the label of the MP2MP tunnel, and sends the data packet through the MP2MP tunnel.
  • the second PE device After receiving the data packet, the second PE device decapsulates the data packet to obtain the label of the ES and the label of the MP2MP tunnel, and determines, according to the label of the ES, whether the first PE device that sends the data packet is the second The PE device is connected to the same ES.
  • the egress PE device (which sends a data packet to the CE device) can interpret the ESI label within the label space of the root node according to the label of the root node of the MP2MP tunnel in the data packet.
  • the ingress PE device corresponding to the ESI label (which receives the data packet sent by the CE device) is connected to the same ES as the egress PE device, so as to avoid connecting the ingress PE device and the egress EP device to the same ES.
  • the data packet is forwarded back to the client side through the ES, thereby avoiding forming a triangle loop on the client side.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the embodiment of the present invention does not need to set a label manager for centralized control, and can reduce signaling overhead and save label space, compared with the scheme for allocating global labels.
  • the embodiment of the present invention is described by taking any Ethernet VPN in the communication system as an example.
  • the bearer network can transmit messages for multiple Ethernet VPNs.
  • the first PE device and the second PE device are any two PE devices in the bearer network. The operator should understand that there may be more PE devices or other intermediate PE devices in the bearer network.
  • the embodiment of the present invention is described by taking an MP2MP tunnel as an example. It should be understood by those skilled in the art that multiple MP2MP tunnels can be established in the bearer network, and the labels of the MP2MP tunnel are used to distinguish different. Tunnel.
  • the first PE device uses the label of the ES as the inner label and the label of the MP2MP tunnel as the outer label encapsulation data message.
  • the first PE device is a root node of the MP2MP tunnel
  • the method of FIG. 1 further includes: the first PE device receiving the PE device sent by each of the at least one second PE device of the bearer network. a first routing message, where the first routing message carries the identifier of the ES connected to the second PE device that sends the first routing message; the first PE device allocates a label to the ES connected to each of the at least one second PE device; The PE device sends a second routing message to the at least one second PE device, where the second routing message carries the identifier information of the root of the MP2MP tunnel, the identifier of the ES connected to each PE device in the at least one second PE device, and at least A label assigned by the ES of each PE device connected to the second PE device.
  • the PE device that is the root node of the MP2MP tunnel can determine all ESs of the MP2MP tunnel to which the root node belongs according to the ESI carried in the routing message advertised by each PE device.
  • the root node assigns an Ethernet segment identifier ESI label to all ESs, and the ES of the bearer connection corresponds to the ESI label.
  • the root node advertises routing information to the leaf node PE device in the MP2MP tunnel, and the routing information may include identifier information of the Ethernet segment identifier ESI, the ESI label, and the root of the MP2MP tunnel.
  • the root node can notify each PE device of the identification information of the root of the MP2MP tunnel, the binding relationship between the ESI and the ESI label.
  • the root node uniformly allocates labels to all the ESs of the MP2MP tunnel, so as to avoid forming a triangular loop on the client side when the MP2MP tunnel is used to carry BUM packets.
  • the foregoing first routing message may be a dedicated routing message, or a regular routing message may be used to carry the identifier of the ES.
  • the PE device issues a per ESI Ethernet AD Route (each ESI Ethernet AD route) type routing message, and the routing message can carry the local connection of the PE.
  • ES ESI MP2MP
  • the root node can use the routing information to discover the ESI corresponding to the multi-homed link in the EVPN network, that is, discover the ES in the EVPN network.
  • each PE device in the bearer network can use the routing message to allocate a label to the ES of each PE connection when the first PE device receives the first routing message sent by each PE in the bearer network.
  • An ESI label may be allocated for the ESI of the ES carried by the first routing message.
  • the root node of the MP2MP tunnel can assign an ES label to each ES.
  • each ESI can be assigned a unique local label, and the ESI and the corresponding ESI label can be advertised to other PE devices.
  • the foregoing second routing message may be a dedicated routing message, or a conventional routing message may be used to carry the identifier of the ES.
  • a new EVPN NLRI Network Layer Reachability Information
  • a type of routing message is used to advertise the label of the ES, or a new extended route attribute is defined based on the ESI label, and is carried in a routing message of the EVPN type including the Inclusive Multicast Ethernet Tag Route type.
  • the tag information can be bound to the identity of the MP2MP root node or the MP2MP tree root.
  • the ESI label is allocated by node (that is, when a root node is only the root of an MP2MP)
  • the identifier of the root node can be used as the root information
  • the ESI label is bound to the identifier of the MP2MP root node.
  • the ESI label is allocated in the MP2MP tree (that is, when one root node is the root of multiple MP2MPs)
  • the ESI label is bound to the identifier of the MP2MP tree root.
  • the method of FIG. 2 further includes: the first PE device encapsulates the data packet by using the label of the ES connected by the first PE device, the label of the MP2MP tunnel, and the label of the broadcast domain of the Ethernet VPN, where The label of the broadcast domain of the Ethernet VPN is used to indicate that the data message belongs to the broadcast domain of the Ethernet VPN, and the label of the broadcast domain of the at least one Ethernet VPN of the bearer network is allocated by the root node of the MP2MP tunnel.
  • the first PE device uses the label of the broadcast domain of the Ethernet VPN as the middle layer label to encapsulate the data packet.
  • a plurality of broadcast domains of the Ethernet VPN may exist in the communication system.
  • the label of the broadcast domain of the Ethernet VPN may be further encapsulated in the data packet.
  • the label of the broadcast domain of the Ethernet VPN can be used as the middle layer label of the data packet, so that the second PE device forwards the data packet to the broadcast domain of the corresponding Ethernet VPN according to the label of the broadcast domain of the Ethernet VPN.
  • the label of the broadcast domain of the Ethernet VPN needs to be encapsulated, which may also be called an EVPN BUM traffic label, so that the egress PE device can distinguish the BUM packet from being belonged to. Which EVPN broadcast domain.
  • the method of FIG. 2 further includes: the first PE device is a root node of the MP2MP tunnel, and the method further includes: the first PE device receiving each of the at least one second PE device in the bearer network At least one third routing message sent by the PE device, where the third routing message carries the identifier of the broadcast domain of the Ethernet VPN connected to the second PE device that sends the third routing message; the first PE device is in the at least one second PE device.
  • the broadcast domain of the Ethernet VPN connected to each PE device is configured with a label; the first PE device sends a fourth routing message to the at least one second PE device, where the fourth routing message carries the identifier information of the root of the MP2MP tunnel, and the at least one second PE An identifier of a broadcast domain of an Ethernet VPN to which each PE device in the device is connected and a label allocated to a broadcast domain of an Ethernet VPN to which each of the at least one PE second PE device is connected.
  • the manner of allocating and distributing the VPN label of the embodiment of the present invention is similar to the manner of allocating and distributing the ESI label. To avoid repetition, details are not described herein again.
  • the method of FIG. 2 further includes: the first PE device receives the second data packet that is transmitted by the second PE device on the MP2MP tunnel, where the second data packet is connected by using the second PE device.
  • the label of the ES and the label of the MP2MP tunnel determine whether the second data packet is sent on the ES to which the first PE device is connected.
  • the first PE device may determine, according to the label of the MP2MP tunnel obtained in the second data packet, the PE device that allocates the label, that is, the root node of the MP2MP tunnel, thereby determining the label space allocated by the root node of the MP2MP tunnel. Then, the first PE device searches for the label space allocated by the root node of the MP2MP tunnel according to the label of the ES connected to the second PE device obtained in the second data packet, to determine the ES corresponding to the label of the ES connected to the second PE device. Finally, according to the second PE device connection Whether the ES is the same as the ES connected to the first PE device determines whether the second data packet is sent on the ES connected to the first PE device.
  • the first PE device does not send the second data packet on the ES connected to the first PE device, if the ES of the first PE device is connected
  • the ES connected to the second PE device is a different ES, and the first PE device sends the second data packet on the ES connected to the first PE device.
  • the first PE device may further determine, according to the label of the broadcast domain of the Ethernet VPN carried in the data packet, that the second data packet is sent locally to the label. The broadcast domain of the Ethernet VPN.
  • the first PE device determines the identifier of the ES connected to the second PE device according to the label of the ES connected to the second PE device and the label of the MP2MP tunnel; by comparing the ES connected by the second PE device The identifier of the ES connected to the first PE device determines whether the second data packet is sent on the ES connected to the first PE device, where the method method of FIG. 2 further includes: the identifier of the ES connected to the second PE device When the identifier of the ES connected to the first PE device is the same, the first PE device does not send the second data packet on the ES connected to the first PE device, and the identifier of the ES connected to the second PE device is connected to the first PE device. When the identifiers of the ESs are different, the first PE device sends the second data packet on the ES connected to the first PE device.
  • the first PE device may locally save a correspondence table or a mapping relationship table of a label (for example, an ESI label) of an ES allocated by a root node of the MP2MP tunnel and an identifier (for example, ESI) of the ES.
  • the first PE device may first determine the PE device that allocates the label, that is, the root node of the MP2MP tunnel, according to the label of the MP2MP tunnel obtained in the second data packet, thereby determining the MP2MP tunnel.
  • the label space allocated by the root node is, the root node of the MP2MP tunnel, according to the label of the MP2MP tunnel obtained in the second data packet, thereby determining the MP2MP tunnel.
  • the first PE device searches for the label space allocated by the root node of the MP2MP tunnel according to the label of the ES connected to the second PE device obtained in the second data packet, that is, searches the corresponding relationship table or the mapping relationship table to determine the second The identifier of the ES corresponding to the label of the ES connected to the PE device, and finally determining whether the second data is sent on the ES connected to the first PE device according to whether the identifier of the ES connected to the second PE device is the same as the identifier of the ES connected to the first PE device. Message. If the identifier of the ES connected to the first PE device is the same as the identifier of the ES connected to the second PE device, the first PE device is not in the first PE device.
  • the second PE packet is sent on the connected ES. If the identifier of the ES connected to the first PE device is different from the identifier of the ES connected to the second PE device, the first PE device sends the second message on the ES connected to the first PE device. Data message.
  • FIG. 3 is a schematic flowchart of a method for transmitting a data message according to another embodiment of the present invention.
  • the method of FIG. 3 can be performed by the PE device of FIG.
  • the method of FIG. 3 corresponds to the method of FIG. 2, and a detailed description is omitted as appropriate.
  • the second PE device receives the data packet sent by the first PE device through the MP2MP tunnel in the bearer network in the Ethernet VPN, where the data packet is encapsulated by the label of the ES connected by the first PE and the label of the MP2MP tunnel, first.
  • the PE device and the second PE device are PE devices of the bearer network, and each ES of the at least one ES connected to the bearer network is connected between one CE device and multiple PE devices of the bearer network, and each ES of at least one ES The label is assigned by the root node of the MP2MP tunnel.
  • the second PE device decapsulates the data packet, and obtains the label of the ES connected to the first PE device and the label of the MP2MP tunnel.
  • the second PE device determines whether to send a data packet on the ES connected to the second PE device according to the label of the ES connected to the first PE device and the label of the MP2MP tunnel.
  • the second PE device may determine, according to the label of the MP2MP tunnel obtained in the data packet, the PE device that allocates the label, that is, the root node of the MP2MP tunnel, thereby determining the label space allocated by the root node of the MP2MP tunnel. Then, the second PE device searches for the label space allocated by the root node of the MP2MP tunnel according to the label of the ES connected to the first PE device obtained in the data packet, to determine the ES corresponding to the label of the ES connected to the first PE device, and finally according to the ES Whether the first PE device connects to the ES is the same as the ES connected to the second PE device, and determines whether to send a data packet on the ES connected to the second PE device.
  • the second PE device does not send data packets on the ES connected to the second PE device, and if the ES of the second PE device is connected to the ES If the ES connected to the PE device is a different ES, the second PE device sends a data packet on the ES connected to the first PE device. Further, in a case where the different Ethernet VPNs share the MP2MP tunnel, the second PE device may further perform the Ethernet VPN according to the data packet.
  • the label of the broadcast domain determines that the data message is sent to the local broadcast domain of the Ethernet VPN corresponding to the label.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the second PE device determines the identifier of the ES corresponding to the label of the ES according to the label of the ES and the label of the MP2MP tunnel, and compares the identifier of the ES corresponding to the label of the ES with the second PE device.
  • the identifier of the connected ES determines whether to send a data packet on the ES connected to the second PE device.
  • the method of FIG. 3 further includes: when the identifier of the ES corresponding to the label of the ES is the same as the identifier of the ES connected to the second PE device, the second PE device is not connected to the second PE device.
  • the second PE device sends a data packet on the ES connected to the second PE device.
  • the second PE device may locally save a correspondence table or a mapping relationship table of a label (for example, an ESI label) of an ES allocated by a root node of the MP2MP tunnel and an identifier (for example, ESI) of the ES.
  • a label for example, an ESI label
  • ESI identifier
  • the second PE device searches for the label space allocated by the root node of the MP2MP tunnel according to the label of the ES connected to the first PE device obtained in the data packet, that is, searches the corresponding relationship table or the mapping relationship table to determine the first PE device.
  • the second PE device does not send a data packet on the ES connected to the second PE device. If the identifier of the ES connected to the second PE device is different from the identifier of the ES connected to the first PE device, The second PE device sends a data packet on the ES connected to the second PE device.
  • the first PE device is a root node of the MP2MP tunnel
  • the method of FIG. 3 further includes: the second PE device sends the first routing message in the bearer network, where the first routing message carries the second PE.
  • the data packet further includes a label of the broadcast domain of the Ethernet VPN, and is used to indicate that the data packet belongs to the broadcast domain of the Ethernet VPN, and the label of the broadcast domain of the at least one Ethernet VPN that is connected by the bearer network. It is assigned by the root node of the MP2MP tunnel.
  • the first PE device is a root node of the MP2MP tunnel
  • the method of FIG. 3 further includes: the second PE device sends a third routing message on the bearer network, where the third routing message carries the second PE device.
  • the method of FIG. 3 further includes: the second PE device receives the second data packet transmitted on the ES connected to the second PE device; and the second PE device adopts the ES connected to the second PE device.
  • the label of the MP2MP tunnel encapsulates the second data packet, and the second PE device sends the second data packet on the MP2MP tunnel.
  • the data message is a broadcast, an unknown unicast or a multicast BUM message.
  • FIG. 4 is a schematic flowchart of a method for transmitting a data message according to another embodiment of the present invention.
  • the method of Figure 4 can be performed by the PE device of Figure 1.
  • the method of FIG. 4 corresponds to the process of assigning the label of the ES and the label of the broadcast domain of the Ethernet VPN in the method of FIG. 2, and a detailed description is omitted as appropriate.
  • the first PE device receives the first routing message sent by each of the at least one second PE device, where the first routing message carries the identifier of the ES connected by the second PE device that sends the first routing message, and the first PE
  • the device and the at least one second PE device are PE devices of the Ethernet VPN bearer network, and each ES of the at least one ES connected to the bearer network is connected between one CE device and multiple PE devices of the bearer network.
  • the first routing message may include not only the identification information of the ES but also other routing related information.
  • the first PE device allocates a label to an ES connected to each of the at least one second PE device.
  • the first PE device sends a second routing message to the at least one second PE device, where the second routing message carries the identifier information of the root of the MP2MP tunnel of the bearer network, and is connected to each PE device of the at least one second PE device.
  • the second routing message may include not only the above information, but also other routing related information.
  • the PE device that is the root node of the MP2MP tunnel can determine all ESs of the MP2MP tunnel to which the root node belongs according to the ESI carried in the routing message advertised by each PE device.
  • the root node assigns an Ethernet segment identifier ESI label to all ESs, and the ES of the bearer connection corresponds to the ESI label.
  • the root node advertises routing information to the leaf node PE device in the MP2MP tunnel, and the routing information may include identifier information of the Ethernet segment identifier ESI, the ESI label, and the root of the MP2MP tunnel.
  • the root node can notify each PE device of the identification information of the root of the MP2MP tunnel, the binding relationship between the ESI and the ESI label.
  • the root node uniformly allocates labels to all the ESs of the MP2MP tunnel, so as to avoid forming a triangular loop on the client side when the MP2MP tunnel is used to carry BUM packets.
  • the foregoing first routing message may be a dedicated routing message, or a regular routing message may be used to carry the identifier of the ES.
  • ALL-Active for multi-homing access defined in the EVPN protocol the PE device will issue a per ESI Ethernet AD Route (each ESI Ethernet AD route) type routing message.
  • the routing message can carry the ESI of the local ES connected to the PE.
  • the MP2MP root node can use the routing information to discover the EVPN network.
  • the ESI corresponding to the multi-homed link in the medium is the ES in the EVPN network.
  • the first PE device may allocate a label for the ES of each PE connection, specifically, the ESI of the ES that may be carried by the first routing message. Assign an ESI tag.
  • the root node of the MP2MP tunnel can assign an ES label to each ES.
  • each ESI can be assigned a unique local label, and the ESI and the corresponding ESI label can be advertised to other PE devices.
  • the foregoing second routing message may be a dedicated routing message, or a conventional routing message may be used to carry the identifier of the ES.
  • a new EVPN NLRI Network Layer Reachability Information
  • a type of routing message is used to advertise the label of the ES, or a new extended route attribute is defined based on the ESI label, and is carried in a routing message of the EVPN type including the Inclusive Multicast Ethernet Tag Route type.
  • the tag information can be bound to the identity of the MP2MP root node or the MP2MP tree root.
  • the ESI label is allocated by node (that is, when a root node is only the root of an MP2MP)
  • the identifier of the root node can be used as the root information
  • the ESI label is bound to the identifier of the MP2MP root node.
  • the ESI label is allocated in the MP2MP tree (that is, when one root node is the root of multiple MP2MPs)
  • the ESI label is bound to the identifier of the MP2MP tree root.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the method of FIG. 4 further includes: the first PE device receives at least one third routing message sent by each of the at least one second PE device, where the third routing message carries the sending The identifier of the broadcast domain of the Ethernet VPN connected to the second PE device of the third routing message; the first PE device allocates a label to the broadcast domain of the Ethernet VPN connected to each of the at least one second PE device; the first PE device The at least one second PE device sends a fourth routing message, where the fourth routing message carries the identifier of the first PE device, the identifier of the broadcast domain of the Ethernet VPN connected to each PE device in the at least one second PE device, and is at least one PE A label assigned by the broadcast domain of the Ethernet VPN to which each PE device of the second PE device is connected.
  • the manner of allocating and distributing the VPN label of the embodiment of the present invention is similar to the manner of allocating and distributing the ESI label. To avoid repetition, details are not described herein again.
  • FIG. 5 is a schematic flowchart of a method for transmitting a data message according to another embodiment of the present invention.
  • the method of Figure 5 can be performed by the PE device of Figure 1.
  • the method of FIG. 4 corresponds to the process of assigning the label of the ES and the label of the broadcast domain of the Ethernet VPN in the method of FIG. 2, and a detailed description is omitted as appropriate.
  • the second PE device sends a first routing message in the bearer network of the Ethernet VPN, where the first routing message carries the identifier of the ES connected to the second PE device, and each ES in the at least one ES connected by the bearer network is connected to a CE. Between the device and multiple PE devices in the bearer network.
  • the second PE device receives the second routing message sent by the first PE device, where the second routing message carries the identifier information of the root of the MP2MP tunnel of the bearer network, and the ES connected to each PE device in the at least one second PE device. And a label allocated to the ES connected to each of the at least one second PE device, wherein the first PE device and the at least one second PE device are PE devices of the Ethernet VPN, and the first PE device is The root node of the MP2MP tunnel.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the method of FIG. 5 further includes: the second PE device sends a third routing message on the bearer network, where the third routing message carries the identifier of the Ethernet VPN broadcast domain connected by the second PE device;
  • the PE device receives the fourth routing message from the first PE device, and the fourth routing message carries the identifier information of the root of the MP2MP tunnel, and the broadcast domain of the Ethernet VPN connected to each PE device in the at least one second PE device in the bearer network.
  • FIG. 6 is a system architecture diagram of an Ethernet VPN according to another embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a method of transmitting a data message according to still another embodiment of the present invention.
  • the embodiment of Figure 7 is an example of the method of Figures 2, 3, 4 and 5.
  • the embodiment of Figure 7 is described below in conjunction with the system architecture diagram of Figure 6.
  • the bearer network of the EVPN-A includes four PE devices: PE1 to PE4. Assume that PE1 is the root node of the MP2MP tunnel, and PE2, PE3, and PE4 are the leaf nodes of the MP2MP tunnel.
  • the CE device CE1 is connected to PE1 and PE2 through the multi-homed link ES1, and the CE device CE2 is connected to PE3 and PE4 through the multi-homed link ES2.
  • a PE When a PE receives a BUM packet from the local ES, it can determine the root node of the MP2MP tunnel based on the MP2MP tunnel used to carry the BUM packet, and then determine the label assigned by the root node to the local ES. This is called the ESI label. . Then, the PE uses the determined ESI label as the innermost label, and the MP2MP tunnel label serves as the outermost label, encapsulates the BUM message, and sends the encapsulated BUM message to other PE devices in the MP2MP tunnel.
  • the embodiment of the present invention adopts a centralized upstream label allocation mode, that is, the root node of the MP2MP tunnel uniformly allocates an upstream label for the ESI and the EVPN, and the downstream node interprets the allocated ESI or VPN label within the label space of the MP2MP root node. .
  • the MP2MP root node needs to discover the broadcast domain of the ESI or Ethernet VPN in the EVPN network before assigning the upstream label to the ESI or EVPN.
  • the following steps 705 to 720 are the process of discovering and allocating the ESI label by the PE1
  • the steps 725 to 765 are the process of transmitting the BUM message between the PE devices.
  • the PE1 receives the routing message carrying the ESI issued by the PE2 in the bearer network.
  • the PE1 receives the routing message carrying the ESI that is advertised by the PE3 in the bearer network.
  • PE1 obtains the routing message advertised by each leaf node (for example, PE2 and PE3), or PE2 and PE3 advertise the ESI of the ES connected to it through the routing message.
  • PE2 and PE3 can use dedicated routing information to issue ESI.
  • PE2 and PE3 may also use the per ESI Ethernet A-D Route type routing message to issue ESI.
  • the routing message sent by PE2 and PE3 carries the ESI of the local ES. Therefore, PE1 can discover the ES in the EVPN according to the obtained routing message carrying the ESI.
  • PE1 allocates a label for the ES in the EVPN.
  • the root node PE1 After the root node PE1 discovers the ES connected to the PE device of the MP2MP tunnel, it assigns a unique label to each ES, that is, assigns a label to each ES's ESI, hereinafter referred to as an ESI label.
  • PE1 assigns a label of 1024 to ES1 and a label of 1025 to ES2.
  • PE1 can also assign labels to EVPNs that share the MP2MP tunnel.
  • the method of assigning a label to an EVPN is similar to the method of assigning an ESI label to an ES, and details are not described herein again.
  • PE1 issues the ESI and the corresponding ESI label to PE2.
  • PE1 issues ESI and corresponding ESI label to PE3.
  • the root node PE1 issues the ESI and the corresponding ESI label to the leaf nodes PE2 and PE3.
  • dedicated routing information may be used to issue an ESI label, for example, to define a new EVPN NLRI type routing message to issue an ESI label.
  • a new extended route attribute may be defined, and the attribute information is carried in a routing message including a type of the Inclusive Multicast Ethernet Tag Route.
  • the label information of the ES can be bound to the root node of the MP2MP tunnel or the identifier of the MP2MP tree root.
  • the label of the ES and the label of the root node of the MP2MP tunnel can be Identity binding.
  • the identifier of the root node may be used to identify the MP2MP tunnel, that is, the identifier information of the root of the MP2MP tunnel may be the identifier of the root node, and multiple root nodes are associated with each other.
  • Different tree root identifiers are used to identify different MP2MP tunnels.
  • PE1 can also send EVPN labels to each leaf node.
  • the label of the root node of the MP2MP tunnel or the correspondence between the identifier and the label of each ES is stored in each leaf node. Further, the mapping between the label or the identifier of the root node and the EVPN label may be stored in each leaf node.
  • PE1 receives a BUM packet from CE1.
  • CE1 forwards BUM packets sent by the client device to PE1 through ES1.
  • the PE1 encapsulates the BUM message by using the ESI label and the label of the MP2MP tunnel.
  • the PE1 stores the labels allocated by the root nodes of different MP2MP tunnels for each ES and EVPN. That is, for each root node of the MP2MP tunnel, the correspondence between the ESI and the ESI label of each ES and the identifier of each EVPN are stored. Correspondence of EVPN labels.
  • PE1 determines the root node of the MP2MP tunnel according to the MP2MP tunnel to be used, and uses the root node of the MP2MP tunnel (PE1 in this embodiment) to allocate the ESI label 1024 for ES1 as the most.
  • the inner label and the label of the MP2MP tunnel are used as the outermost label to encapsulate the BUM message.
  • the label allocated by the root node for the EVPN may be used as the middle layer label to encapsulate the BUM message.
  • the PE2 receives the encapsulated BUM packet sent by the PE1.
  • the PE1 sends the encapsulated BUM packet to the PE2 through the MP2MP tunnel.
  • the PE2 decapsulates the BUM packet.
  • PE2 decapsulates the outermost label in the BUM packet to obtain the label of the root node of the MP2MP tunnel, decapsulates the middle layer label in the BUM packet to obtain the EVPN label, and decapsulates the innermost label of the BUM packet to obtain the ESI label. And get the decapsulated BUM message.
  • the PE2 determines whether to forward the BUM packet to the local CE.
  • the PE2 stores the labels allocated by the root nodes of different MP2MP tunnels for each ES and EVPN. That is, for each root node of the MP2MP tunnel, the correspondence between the ESI and the ESI label of each ES and the identifier of each EVPN are stored. Correspondence of EVPN labels. Based on the outermost label (the label of the MP2MP tunnel), the PE2 determines that the root node of the MP2MP tree is PE1, and interprets the innermost ESI label in the label space allocated by the PE1, so that the label corresponding to the ESI label can be determined. Know ES1. The ES1 is the local ES connected to the PE2. Therefore, the PE2 does not forward BUM packets to the ES1.
  • the PE1 forwards the encapsulated BUM packet to the PE3.
  • the PE1 sends the encapsulated BUM packet to the PE3 through the MP2MP tunnel.
  • the PE3 decapsulates the BUM packet.
  • the PE3 determines whether to forward the BUM packet to the local CE.
  • the PE3 stores the labels of the root nodes of different MP2MP tunnels for each ES and EVPN. That is, for each root node of the MP2MP tunnel, the corresponding relationship between the ESI and the ESI label of each ES and the identifier of each EVPN are stored. Correspondence of EVPN labels. For example, PE3 determines that the root node of the MP2MP tree is PE1 according to the outermost label (MP2MP tunnel label), and interprets the innermost ESI label (for example, 1025) in the label space allocated by PE1, and thus can determine the corresponding ESI label. Identifies ES2. ES2 is a local ES connected to PE3. Because ES2 is different from ES1, PE3 can forward BUM packets to the ES2.
  • the EVPN label needs to be encapsulated, so that the egress PE device can distinguish which EVPN broadcast domain the BUM message belongs to.
  • the PE3 can determine, according to the EVPN label carried in the BUM packet, which EUM BUM packet is the BUM packet, and forward the BUM packet only to the EVPN.
  • the PE3 forwards the BUM packet to the CE2.
  • the PE3 forwards the decapsulated BUM packet to the CE2 through the ES2.
  • the embodiment of the present invention uses an MP2MP tunnel to carry BUM packets, and the root node PE device allocates labels for all ESs of the MP2MP tunnel to avoid forming a triangular loop.
  • the embodiment of the present invention provides an achievable manner for carrying BUM packets in an EVPN network, and can implement interworking between multiple PE devices without saving multiple tree state tables and forwarding tables.
  • FIG. 8 is a schematic flowchart of a method of transmitting a data message according to still another embodiment of the present invention.
  • the embodiment of Figure 8 is an example of the method of Figures 2, 3, 4 and 5.
  • the embodiment of Figure 8 is described below in conjunction with the system architecture diagram of Figure 6.
  • Steps 805 to 820 are the process of discovering and assigning the ESI label to the PE1, and step 705 to The steps of 720 are the same and will not be described here.
  • Steps 825 to 850 are processes for transmitting BUM messages between PE devices.
  • the PE1 receives the routing message carrying the ESI issued by the PE2 in the bearer network.
  • the PE1 receives the routing message carrying the ES that is advertised by the PE3 in the bearer network.
  • PE1 allocates a label for the ES in the EVPN.
  • PE1 issues ESI and corresponding ESI label to PE2.
  • PE1 issues ESI and corresponding ESI label to PE3.
  • the PE3 receives the BUM packet from the CE2.
  • the PE3 uses the ESI label allocated by the PE1 and the label of the MP2MP tunnel to encapsulate the BUM packet.
  • the PE3 uses the ESI label 1025 assigned to the ES2 as the innermost layer label and the MP2MP tunnel label as the outermost label to encapsulate the BUM message, using the root node of the MP2MP tunnel (in this embodiment, PE1).
  • the EVPN label can also be used as the middle layer label to encapsulate the BUM message.
  • PE2 receives PE3 and sends a BUM packet.
  • the PE3 sends the encapsulated BUM packet to the PE2 through the MP2MP tunnel.
  • the PE2 decapsulates the BUM packet.
  • PE2 decapsulates the outermost label in the BUM packet to obtain the label of the root node of the MP2MP tunnel, decapsulates the middle layer label in the BUM packet to obtain the EVPN label, and decapsulates the innermost label of the BUM packet to obtain the ESI label. And get the decapsulated BUM message.
  • the PE2 determines whether to forward the BUM packet to the CE1.
  • the PE2 stores the labels allocated by the root nodes of different MP2MP tunnels for each ES and EVPN. That is, for each root node of the MP2MP tunnel, the correspondence between the ESI and the ESI label of each ES and the identifier of each EVPN are stored. Correspondence of EVPN labels. For example, PE2 determines that the root node of the MP2MP tree is PE1 according to the outermost label (MP2MP tunnel label), and interprets the innermost ESI label (for example, 1025) in the label space allocated by PE1, and thus can determine the corresponding ESI label. Identifies ES2. ES1 is the local ES connected to PE2. Since ES1 is different from ES2, Therefore, PE3 can forward BUM packets to the ES1.
  • the PE2 can determine, according to the EVPN label carried in the BUM packet, which EUM BUM packet is the BUM packet, and forward the BUM packet only to the EVPN.
  • the PE2 forwards the decapsulated BUM packet to the CE1.
  • PE2 sends the decapsulated BUM packet to CE1 through ES1.
  • the embodiment of the present invention uses an MP2MP tunnel to carry BUM packets, and the root node PE device allocates labels for all ESs of the MP2MP tunnel to avoid forming a triangular loop.
  • the embodiment of the present invention provides an achievable manner for carrying BUM packets in an EVPN network, and can implement interworking between multiple PE devices without saving multiple tree state tables and forwarding tables.
  • FIG. 9 is a schematic structural diagram of a PE device 900 according to an embodiment of the present invention.
  • the PE device 900 includes a receiving module 910, a packaging module 920, and a sending module 930.
  • the receiving module 910 is configured to receive the data packet sent by the CE device by using the ES generated by the PE device 900 and the CE device, where the PE device 900 is the PE device of the Ethernet VPN bearer network.
  • the encapsulation module 920 is configured to use the label of the ES connected by the PE device 900 and the label encapsulation data packet of the MP2MP tunnel in the bearer network, where each ES of the at least one ES connected to the bearer network is connected to one CE device and bearer. Between multiple PE devices of the network, the label of each ES in at least one ES is allocated by the root node of the MP2MP tunnel.
  • the sending module 930 is configured to send a data packet by using an MP2MP tunnel.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the encapsulation module 920 adopts the label of the ES as an inner layer label,
  • the label of the MP2MP tunnel encapsulates the data packet as the outer label.
  • the PE device 900 of FIG. 9 further includes: an allocation module 940.
  • the PE device 900 is the root node of the MP2MP tunnel, and the receiving module 910 further receives the first routing message sent by each of the at least one second PE device of the bearer network, where the first routing message carries the second message that sends the first routing message.
  • the identifier of the ES connected to the PE device the distribution module 940 assigns a label to the ES connected to each of the at least one second PE device, and the sending module 930 further sends a second routing message to the at least one second PE device, the second route
  • the message carries the identification information of the root of the MP2MP tunnel, the identifier of the ES connected to each of the at least one second PE device, and the label assigned to the ES connected to each of the at least one second PE device.
  • the encapsulating module 920 encapsulates the data packet by using the label of the ES connected by the PE device 900, the label of the MP2MP tunnel, and the label of the broadcast domain of the Ethernet VPN, where the label of the broadcast domain of the Ethernet VPN is used.
  • the indication data message belongs to the broadcast domain of the Ethernet VPN, and the label of the broadcast domain of the at least one Ethernet VPN of the bearer network is allocated by the root node of the MP2MP tunnel.
  • the PE device 900 of FIG. 9 further includes: an allocation module 940.
  • the PE device 900 is the root node of the MP2MP tunnel, and the receiving module 910 further receives at least one third routing message sent by each of the at least one second PE device in the bearer network, where the third routing message carries the third routing message.
  • the PE device 900 of FIG. 9 further includes: a decapsulation module 960 and a determination module 970.
  • the receiving module 910 further receives the second data packet that is transmitted by the second PE device on the MP2MP tunnel, where the second data packet is encapsulated by the label of the ES connected by the second PE device and the label of the MP2MP tunnel; and the decapsulation module 960 is decapsulated.
  • the second data message gets the second The label of the ES connected to the PE device and the label of the MP2MP tunnel; the determining module 970 determines whether to send the second data packet on the ES connected to the PE device 900 according to the label of the ES connected to the second PE device and the label of the MP2MP tunnel.
  • the determining module 970 determines the identifier of the ES connected to the second PE device according to the label of the ES connected to the second PE device and the label of the MP2MP tunnel, and compares the identifier of the ES connected to the second PE device with the PE.
  • the identifier of the ES connected to the device 900 determines whether the second data packet is sent on the ES connected to the PE device 900.
  • the sending module 930 also determines that the identifier of the ES connected to the second PE device is the same as the identifier of the ES connected to the PE device 900.
  • the PE device 900 does not send the second data packet on the ES connected to the PE device 900.
  • the PE device 900 is connected to the PE device 900.
  • the second data packet is sent on the ES.
  • the data message is a broadcast, an unknown unicast or a multicast BUM message.
  • FIG. 10 is a schematic structural diagram of a PE device 1000 according to another embodiment of the present invention.
  • the PE device 1000 of FIG. 10 includes a receiving module 1010, a decapsulation module 1020, and a determining module 1030.
  • the receiving module 1010 receives the data packet sent by the first PE device through the MP2MP tunnel in the bearer network in the Ethernet VPN, where the data packet is encapsulated by the label of the ES connected by the first PE and the label of the MP2MP tunnel, and the first PE device and The PE device 1000 is a PE device of the bearer network.
  • Each ES of the at least one ES connected to the bearer network is connected between one CE device and multiple PE devices of the bearer network.
  • the label of each ES in at least one ES is determined by The root node of the MP2MP tunnel is assigned.
  • the decapsulation module 1020 decapsulates the data packet to obtain the label of the ES connected to the first PE device and the label of the MP2MP tunnel.
  • the determining module 1030 determines whether to send a data message on the ES connected to the PE device 1000 according to the label of the ES connected by the first PE device and the label of the MP2MP tunnel.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. , forwarding the number according to the label of the ES in the data packet According to the message.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the determining module 1030 determines the identifier of the ES of the first PE device connected according to the label of the ES connected by the first PE device and the label of the MP2MP tunnel, and compares the identifier of the ES connected with the first PE device with the PE.
  • the identifier of the ES connected to the device 1000 determines whether the data packet is sent on the ES connected to the PE device 1000.
  • the PE device 1000 further includes: a sending module 1040, the identifier of the ES connected to the first PE device, and the PE device.
  • the identifiers of the 800 connected ESs are the same, the data packets are not sent on the ES connected to the PE device 1000.
  • the PE device 1000 is different from the PE device 1000.
  • a data packet is sent on the connected ES.
  • the first PE device is a root node of the MP2MP tunnel
  • the PE device 1000 further includes: a sending module 1040, configured to send a first routing message in the bearer network, where the first routing message carries the PE device.
  • the identifier of the connected ES where the receiving module 1010 further receives the second routing message sent by the first PE device, where the second routing message carries the identifier information of the root of the MP2MP tunnel, and each of the at least one second PE device of the bearer network
  • the data packet further includes a label of the broadcast domain of the Ethernet VPN, and is used to indicate that the data packet belongs to the broadcast domain of the Ethernet VPN, and the label of the broadcast domain of the at least one Ethernet VPN that is connected by the bearer network. It is assigned by the root node of the MP2MP tunnel.
  • the first PE device is a root node of the MP2MP tunnel
  • the PE device 1000 further includes: a sending module 1040, configured to send a third routing message on the bearer network, where the third routing message carries the PE device connection.
  • the identifier of the broadcast domain of the Ethernet VPN where the receiving module 1010 further receives the first routing information sent by the first PE device, where the fourth routing message carries the identifier information of the root of the MP2MP tunnel, and at least one second PE device in the bearer network.
  • the PE device 1000 further includes: a sending module 1040 and a packaging module 1050, where the receiving module 1010 further receives a second data packet transmitted on the ES connected to the PE device; and the encapsulating module 1050 uses the PE device.
  • the label of the connected ES and the label of the MP2MP tunnel encapsulate the second data packet; the sending module 1040 sends the second data packet on the MP2MP tunnel.
  • the data message is a broadcast, an unknown unicast or a multicast BUM message.
  • FIG. 11 is a schematic structural diagram of a PE device 1100 according to another embodiment of the present invention.
  • the PE device 1100 of FIG. 11 includes a receiving module 1110, an allocating module 1120, and a transmitting module 1130.
  • the receiving module 1110 receives the first routing message sent by each of the at least one second PE device, where the first routing message carries the identifier of the ES connected by the second PE device that sends the first routing message, and the PE device and the at least A second PE device is a PE device of a bearer network of the Ethernet VPN, and each ES of the at least one ES connected to the bearer network is connected between one CE device and multiple PE devices of the bearer network.
  • the allocation module 1120 assigns a label to an ES connected to each of the at least one second PE device.
  • the sending module 1130 sends a second routing message to the at least one second PE device, where the second routing message carries the identifier information of the root of the tunnel of the MP2MP of the bearer network, and the ES of each of the at least one second PE device And a label assigned to the ES connected to each of the at least one second PE device, the PE device being a root node of the MP2MP tunnel.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the receiving module 1110 further receives at least one third routing message sent by each of the at least one second PE device, where the third routing message carries the second PE that sends the third routing message.
  • the distribution module 1120 also And assigning a label to the broadcast domain of the Ethernet VPN that is connected to each of the at least one second PE device;
  • the sending module 1130 further sends a fourth routing message to the at least one second PE device, where the fourth routing message carries the identifier of the PE device, An identifier of a broadcast domain of an Ethernet VPN connected to each of the at least one second PE device and a label allocated to a broadcast domain of the Ethernet VPN connected to each of the at least one PE second PE device.
  • FIG. 12 is a schematic structural diagram of a PE device 1200 according to another embodiment of the present invention.
  • the PE device 1200 of FIG. 12 includes a transmitting module 1210 and a receiving module 1220.
  • the sending module 1210 sends a first routing message in the bearer network of the Ethernet VPN, where the first routing message carries the identifier of the ES connected to the PE device, and each ES of the at least one ES connected to the bearer network is connected to a CE device and the bearer network. Between multiple PE devices.
  • the receiving module 1220 receives the second routing message sent by the first PE device, where the second routing message carries the identifier information of the root of the MP2MP tunnel of the bearer network, the identifier of the ES connected to each PE device in the at least one second PE device, and a label assigned to an ES connected to each of the at least one second PE device, wherein the first PE device and the at least one second PE device are PE devices of an Ethernet VPN bearer network, and the first PE device is an MP2MP tunnel Root node.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the sending module 1210 further sends a third routing message on the bearer network, where the third routing message carries the identifier of the Ethernet VPN broadcast domain connected by the PE device.
  • the receiving module 1220 further receives, by the first PE device, a fourth routing message, where the fourth routing message carries the identifier information of the root of the MP2MP tunnel, and each of the at least one second PE device in the bearer network is connected.
  • FIG. 13 is a schematic structural diagram of a PE device 1300 according to another embodiment of the present invention.
  • the PE device 900 includes a processor 1310, a memory 1320, a transceiver 1330, and a bus 1340.
  • the transceiver 1330 is configured to receive a data packet sent by the CE device by using an ES connected between the PE device 1300 and the CE device, where the PE device 1300 is a PE device of the Ethernet VPN bearer network.
  • the processor 1310 calls the code stored in the memory 1320 via the bus 1340 to encapsulate the data message with the label of the ES connected by the PE device 1300 and the label of the MP2MP tunnel in the bearer network, wherein each of the at least one ES of the bearer network connection
  • the ESs are connected between a CE device and a plurality of PE devices of the bearer network, and the labels of each ES in at least one ES are allocated by the root node of the MP2MP tunnel.
  • the transceiver 1330 is configured to send a data packet by using an MP2MP tunnel.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the processor 1310 uses the label of the ES as the inner layer label and the label of the MP2MP tunnel as the outer label to encapsulate the data message.
  • the PE device 1300 is a root node of the MP2MP tunnel
  • the receiver 1330 further receives a first routing message sent by each of the at least one second PE device of the bearer network, the first route.
  • the message carries the identifier of the ES connected to the second PE device that sends the first routing message
  • the processor 1310 further allocates a label to the ES connected to each of the at least one second PE device
  • the transceiver 1330 also goes to the at least one second
  • the PE device sends a second routing message, where the second routing message carries the identifier information of the root of the MP2MP tunnel, and each PE in the at least one second PE device The identifier of the ES to which the device is connected and the label assigned to the ES connected to each of the at least one second PE device.
  • the processor 1310 encapsulates the data packet by using the label of the ES connected by the PE device 1300, the label of the MP2MP tunnel, and the label of the broadcast domain of the Ethernet VPN, where the label of the broadcast domain of the Ethernet VPN is used.
  • the indication data message belongs to the broadcast domain of the Ethernet VPN, and the label of the broadcast domain of the at least one Ethernet VPN of the bearer network is allocated by the root node of the MP2MP tunnel.
  • the PE device 1300 is a root node transceiver 1330 of the MP2MP tunnel, and further receives at least one third routing message sent by each of the at least one second PE device in the bearer network, where The third routing message carries the identifier of the broadcast domain of the Ethernet VPN connected to the second PE device that sends the third routing message; the processor 1310 further allocates a label to the broadcast domain of the Ethernet VPN connected to each PE device of the at least one second PE device.
  • the transceiver 1330 further sends a fourth routing message to the at least one second PE device, where the fourth routing message carries the identification information of the root of the MP2MP tunnel, and the broadcast of the Ethernet VPN connected to each PE device in the at least one second PE device.
  • the transceiver 1330 further receives a second data packet that is transmitted by the second PE device on the MP2MP tunnel, where the second data packet uses the ES label and the MP2MP that are connected by the second PE device.
  • the tag encapsulation of the tunnel; the processor 1310 further decapsulates the second data packet, and obtains the label of the ES connected to the second PE device and the label of the MP2MP tunnel, and determines according to the label of the ES connected by the second PE device and the label of the MP2MP tunnel. Whether the second data packet is sent on the ES connected to the PE device 1300.
  • the processor 1310 determines the identifier of the ES connected to the second PE device according to the label of the ES connected to the second PE device and the label of the MP2MP tunnel, and compares the identifier of the ES connected to the second PE device with the PE.
  • the identifier of the ES connected to the device 1300 determines whether the second data packet is sent on the ES connected to the PE device 1300.
  • PE device 1300 is not The PE device 1300 sends the second data packet on the ES connected to the PE device 1300.
  • the PE device 1300 sends the second message on the ES connected to the PE device 1300. Data message.
  • the data message is a broadcast, an unknown unicast or a multicast BUM message.
  • FIG. 14 is a schematic structural diagram of a PE device 1400 according to another embodiment of the present invention.
  • the PE device 1400 of FIG. 14 includes a processor 1410, a memory 1420, a transceiver 1430, and a bus 1440.
  • the transceiver 1430 receives the data packet sent by the first PE device through the MP2MP tunnel in the bearer network in the Ethernet VPN, where the data packet is encapsulated by the label of the ES connected by the first PE and the label of the MP2MP tunnel, and the first PE device and The PE device is a PE device of the bearer network.
  • Each ES of the at least one ES connected to the bearer network is connected between one CE device and multiple PE devices of the bearer network.
  • the label of each ES in at least one ES is MP2MP.
  • the root node of the tunnel is assigned.
  • the processor 1410 decapsulates the data packet, and obtains the label of the ES connected to the first PE device and the label of the MP2MP tunnel, and determines whether the ES of the PE device is connected according to the label of the ES connected to the first PE device and the label of the MP2MP tunnel. Send a data message.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the processor 1410 determines the identifier of the ES connected to the first PE device according to the label of the ES connected to the first PE device and the label of the MP2MP tunnel, and compares the identifier of the ES connected with the first PE device with the PE.
  • the identifier of the ES connected to the device determines whether the data packet is sent on the ES connected to the PE device.
  • the PE device further includes: the transceiver 1330 is further configured to connect the identifier of the ES connected to the first PE device to the ES connected to the PE device. When the identity is the same, not with PE A data packet is sent on the ES connected to the device.
  • the identifier of the ES connected to the first PE device is different from the identifier of the ES connected to the PE device, the data packet is sent on the ES connected to the PE device.
  • the first PE device is a root node of the MP2MP tunnel.
  • the transceiver 1430 is further configured to send the first routing message in the bearer network, where the first routing message carries the identifier of the ES connected by the PE device, and receives the second routing message sent by the first PE device, where the second routing message carries the MP2MP tunnel.
  • the data packet further includes a label of the broadcast domain of the Ethernet VPN, and is used to indicate that the data packet belongs to the broadcast domain of the Ethernet VPN, and the label of the broadcast domain of the at least one Ethernet VPN that is connected by the bearer network. It is assigned by the root node of the MP2MP tunnel.
  • the first PE device is a root node of the MP2MP tunnel
  • the transceiver 1430 is further configured to send a third routing message on the bearer network, where the third routing message carries the broadcast domain of the Ethernet VPN connected by the PE device.
  • the fourth routing message carries the identifier information of the root of the MP2MP tunnel, and the Ethernet VPN connected by each PE device in the at least one second PE device in the bearer network An identifier of the broadcast domain and a label assigned to the broadcast domain of the Ethernet VPN to which each of the at least one second PE device is connected.
  • the transceiver 1430 is further configured to receive the second data packet transmitted on the ES connected to the PE device; the processor 1410 further adopts the label of the ES connected by the PE device and the label encapsulation of the MP2MP tunnel.
  • the second data packet is sent by the sending module on the MP2MP tunnel.
  • the data message is a broadcast, an unknown unicast or a multicast BUM message.
  • FIG. 15 is a schematic structural diagram of a PE device 1500 according to another embodiment of the present invention.
  • the PE device 1500 of FIG. 15 includes a processor 1510, a memory 1520, a transceiver 1530, and a bus 1540.
  • the receiver 1530 receives the first route sent by each of the at least one second PE device.
  • the message that the first routing message carries the identifier of the ES connected to the second PE device that sends the first routing message, and the PE device and the at least one second PE device are the PE devices of the Ethernet network of the Ethernet VPN, and at least one ES connected to the bearer network Each ES is connected between a CE device and a plurality of PE devices of the bearer network.
  • the processor 1510 calls the code stored in the memory 1520 via the bus 1540 to assign a label to the ES connected to each of the at least one second PE device.
  • the transceiver 1530 further sends a second routing message to the at least one second PE device, where the second routing message carries the identifier information of the root of the tunnel of the MP2MP of the bearer network, and the ES of each of the at least one second PE device And a label assigned to an ES connected to each of the at least one second PE device, the PE device being a root node of the MP2MP tunnel.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the transceiver 1530 further receives at least one third routing message sent by each of the at least one second PE device, where the third routing message carries the second PE that sends the third routing message.
  • FIG. 16 is a schematic structural diagram of a PE device 1600 according to another embodiment of the present invention.
  • the PE device 1600 of FIG. 16 includes a processor 1610, a memory 1620, a transceiver 1630, and a bus 1640.
  • the processor 1610 controls the transceiver 1630 to send the first routing message in the bearer network of the Ethernet VPN through the bus 1640.
  • the first routing message carries the identifier of the ES connected by the PE device, and receives the second routing message sent by the first PE device.
  • the second routing message carries the identifier information of the root of the MP2MP tunnel of the bearer network, the identifier of the ES connected to each of the at least one second PE device, and the ES connected to each of the at least one second PE device.
  • each of the at least one ES of the bearer network connection is connected between a CE device and a plurality of PE devices of the bearer network, and the first PE device and the at least one second PE device are the bearer network of the Ethernet VPN.
  • the PE device, the first PE device is the root node of the MP2MP tunnel.
  • the PE device may encapsulate the data packet received from the CE device by using the label of the ES allocated by the root node of the MP2MP tunnel, and send the data packet through the MP2MP tunnel.
  • the other PE device receives the data packet. And forwarding the data packet according to the label of the ES in the data packet.
  • the other PE device can determine whether the data packet is from the same ES according to the label of the ES. Therefore, the data packet can be prevented from being forwarded back to the CE device that sends the data packet, thereby solving the triangle loop on the client side. problem.
  • the transceiver 1630 further sends a third routing message on the bearer network, where the third routing message carries the identifier of the Ethernet VPN broadcast domain connected by the PE device, and receives the first PE device to send the fourth routing message.
  • the fourth routing message carries the identifier information of the root of the MP2MP tunnel, the identifier of the broadcast domain of the Ethernet VPN connected to each PE device in the at least one second PE device in the bearer network, and is in the at least one second PE device.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read only memory (ROM, Read-Only) Memory, random access memory (RAM), disk or optical disk, and other media that can store program code.

Landscapes

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

Abstract

Selon certains modes de réalisation, la présente invention concerne un procédé permettant de transmettre un paquet de données, et un dispositif côté fournisseur (PE). Le procédé comprend les étapes suivantes : un premier dispositif PE reçoit un paquet de données envoyé par un dispositif côté client (CE) via un segment Ethernet (ES) connecté entre le premier dispositif PE et le dispositif CE, le premier dispositif PE étant un dispositif PE dans un réseau support d'un réseau privé virtuel Ethernet (EVPN) ; le premier dispositif PE adopte une étiquette d'un segment ES connecté au premier dispositif PE et une étiquette d'un tunnel multipoint à multipoint (MP2MP) dans le réseau support pour encapsuler le paquet de données, chaque ES dans au moins un ES connecté au réseau support étant connecté entre un dispositif CE et plusieurs dispositifs PE dans le réseau support, et une étiquette de chaque ES dans le ou les ES étant attribuée par un noeud racine du tunnel MP2MP ; et le premier dispositif PE envoie le paquet de données via le tunnel MP2MP. Le schéma technique de la présente invention peut empêcher l'apparition d'un anneau de forme triangulaire côté client.
PCT/CN2015/074492 2014-04-30 2015-03-18 Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur WO2015165311A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410182560.3 2014-04-30
CN201410182560.3A CN105099846B (zh) 2014-04-30 2014-04-30 传输数据报文的方法和供应商边缘设备

Publications (1)

Publication Number Publication Date
WO2015165311A1 true WO2015165311A1 (fr) 2015-11-05

Family

ID=54358147

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/074492 WO2015165311A1 (fr) 2014-04-30 2015-03-18 Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur

Country Status (2)

Country Link
CN (1) CN105099846B (fr)
WO (1) WO2015165311A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3471347A4 (fr) * 2016-12-29 2019-05-15 Huawei Technologies Co., Ltd. Procédé, dispositif et système de traitement de paquet vxlan
WO2019105461A1 (fr) * 2017-11-30 2019-06-06 中兴通讯股份有限公司 Procédé et appareil d'envoi et de traitement de paquets, nœud pe et nœud
CN111628921A (zh) * 2019-02-27 2020-09-04 华为技术有限公司 一种报文的处理方法、报文转发装置以及报文处理装置
WO2021134434A1 (fr) 2019-12-31 2021-07-08 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et système de filtrage d'horizon divisé de réseau privé virtuel ethernet (evpn)
US11277281B2 (en) 2017-12-18 2022-03-15 Telefonaktiebolaget Lm Ericsson (Publ) Provider edge device and method implemented thereon for ethernet virtual private network
CN114430393A (zh) * 2020-10-16 2022-05-03 华为技术有限公司 报文处理方法、装置及存储介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108259333B (zh) * 2016-12-29 2021-07-09 华为技术有限公司 一种bum流量控制方法、相关装置以及系统
CN108696414A (zh) * 2017-04-05 2018-10-23 中兴通讯股份有限公司 多归接入方法、装置及多归属节点
CN108259356B (zh) 2017-04-25 2020-08-04 新华三技术有限公司 路由控制方法和装置
CN108259303B (zh) * 2017-12-25 2020-12-04 新华三技术有限公司 一种报文转发方法及装置
CN108718276B (zh) * 2018-04-10 2021-04-27 新华三技术有限公司 一种报文转发方法和装置
CN113055295A (zh) * 2018-08-01 2021-06-29 华为技术有限公司 通信方法、通信设备和通信系统
CN111447131B (zh) * 2019-01-16 2022-11-08 中兴通讯股份有限公司 报文解封装方法及装置、报文封装方法及装置
CN112311643B (zh) * 2019-07-24 2023-04-18 深圳市中兴微电子技术有限公司 一种evpn报文转发方法、系统、存储介质和终端
CN112104547B (zh) * 2020-08-05 2022-07-12 新华三技术有限公司 Evpn多归属组网避免环路的方法及装置
CN114666267A (zh) * 2020-12-07 2022-06-24 中兴通讯股份有限公司 以太虚拟专用网的数据处理方法、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070053284A1 (en) * 2005-09-07 2007-03-08 Sbc Knowledge Ventures Lp System and method for fault-tolerance in an inter-carrier network interface
CN101562552A (zh) * 2009-05-27 2009-10-21 华为技术有限公司 一种虚拟专用局域网环路检测的方法、系统和设备
CN101674241A (zh) * 2009-09-15 2010-03-17 杭州华三通信技术有限公司 一种ce双归属网络中避免rip环路的方法及设备

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103209125B (zh) * 2013-04-07 2016-03-02 杭州华三通信技术有限公司 一种标签信息的传输方法和设备
CN103312611B (zh) * 2013-06-03 2016-12-28 华为技术有限公司 报文处理方法、设备标签处理方法及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070053284A1 (en) * 2005-09-07 2007-03-08 Sbc Knowledge Ventures Lp System and method for fault-tolerance in an inter-carrier network interface
CN101562552A (zh) * 2009-05-27 2009-10-21 华为技术有限公司 一种虚拟专用局域网环路检测的方法、系统和设备
CN101674241A (zh) * 2009-09-15 2010-03-17 杭州华三通信技术有限公司 一种ce双归属网络中避免rip环路的方法及设备

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3471347A4 (fr) * 2016-12-29 2019-05-15 Huawei Technologies Co., Ltd. Procédé, dispositif et système de traitement de paquet vxlan
US11075774B2 (en) 2016-12-29 2021-07-27 Huawei Technologies Co., Ltd. VXLAN packet processing method, device, and system
WO2019105461A1 (fr) * 2017-11-30 2019-06-06 中兴通讯股份有限公司 Procédé et appareil d'envoi et de traitement de paquets, nœud pe et nœud
RU2735725C1 (ru) * 2017-11-30 2020-11-06 Зте Корпорейшн Способ и устройство обработки и отправки пакетов, узел pe и узел
US11374862B2 (en) 2017-11-30 2022-06-28 Zte Corporation Packet sending and processing method and apparatus, PE node, and node
US11277281B2 (en) 2017-12-18 2022-03-15 Telefonaktiebolaget Lm Ericsson (Publ) Provider edge device and method implemented thereon for ethernet virtual private network
CN111628921A (zh) * 2019-02-27 2020-09-04 华为技术有限公司 一种报文的处理方法、报文转发装置以及报文处理装置
US11683272B2 (en) 2019-02-27 2023-06-20 Huawei Technologies Co., Ltd. Packet processing method, packet forwarding apparatus, and packet processing apparatus
WO2021134434A1 (fr) 2019-12-31 2021-07-08 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et système de filtrage d'horizon divisé de réseau privé virtuel ethernet (evpn)
EP4085578A4 (fr) * 2019-12-31 2023-09-27 Telefonaktiebolaget LM Ericsson (publ.) Procédé et système de filtrage d'horizon divisé de réseau privé virtuel ethernet (evpn)
CN114430393A (zh) * 2020-10-16 2022-05-03 华为技术有限公司 报文处理方法、装置及存储介质
CN114430393B (zh) * 2020-10-16 2022-12-06 华为技术有限公司 报文处理方法、装置及存储介质

Also Published As

Publication number Publication date
CN105099846A (zh) 2015-11-25
CN105099846B (zh) 2018-10-19

Similar Documents

Publication Publication Date Title
WO2015165311A1 (fr) Procédé permettant de transmettre un paquet de données et dispositif côté fournisseur
US10484203B2 (en) Method for implementing communication between NVO3 network and MPLS network, and apparatus
EP4131872A1 (fr) Procédé et appareil de transmission de trafic de multidiffusion, noeud de communication et support de stockage
CN104135420B (zh) 一种报文转发的方法、设备及系统
WO2017162095A1 (fr) Procédé, dispositif et système de communication basés sur un protocole de spécification de flux
EP2945330B1 (fr) Procédé de gestion d'itinéraires, procédé d'itinéraires, contrôleur de réseau et routeur
WO2016173271A1 (fr) Procédé, dispositif et système de traitement de messages
EP3863233B1 (fr) Procédé et dispositif utilisés pour un réseau privé virtuel ethernet
CN107026796B (zh) 一种vpn路由通告方法、数据流转发方法及相关设备
WO2015192501A1 (fr) Procédé et appareil de libération d'informations d'adresse
CN102413060B (zh) Vpls网络中用户专线通信方法及设备
WO2014194711A1 (fr) Procédé de traitement de paquets, procédé et dispositif de traitement d'étiquette de dispositif
WO2017113772A1 (fr) Procédé de gestion d'étiquette, et procédé et dispositif pour traiter un flux de données
CN105453513B (zh) 报文转发方法、转发表项下发方法及网络设备
WO2013139270A1 (fr) Procédé, dispositif et système pour implémenter un réseau privé virtuel en couche 3
CN110417655B (zh) 一种数据报文转发的方法及装置
CN102571375B (zh) 组播转发方法、装置及网络设备
CN105553810A (zh) 一种转发专线业务报文的方法及装置
US11929923B2 (en) Packet transmission method and apparatus
CN102469010B (zh) 一种分配mpls标签的方法和网络设备
CN113726653B (zh) 报文处理方法及装置
CN103634210B (zh) 发现vpls实例的对端pe设备的方法及设备
WO2023050932A1 (fr) Procédé d'annonce de routage, dispositif de réseau et support de stockage informatique
WO2024001553A1 (fr) Procédé de publication de routage, dispositif électronique et support de stockage lisible par ordinateur
WO2023050929A1 (fr) Procédé de distribution de route, procédé de transfert de paquet, dispositif et système

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15786539

Country of ref document: EP

Kind code of ref document: A1