WO2020168854A1

WO2020168854A1 - Evpn multicast method, apparatus and system

Info

Publication number: WO2020168854A1
Application number: PCT/CN2020/071291
Authority: WO
Inventors: 王海林; 段方红
Original assignee: 华为技术有限公司
Priority date: 2019-02-19
Filing date: 2020-01-10
Publication date: 2020-08-27
Also published as: CN111585899A

Abstract

Disclosed are an EVPN multicast method, apparatus and system. The burden on a PE is reduced through simple configuration, and the switching performance is improved when a link or a node fails. The specific solution is: a leaf node PE receiving the same multicast traffic from a first root node PE and a second root node PE respectively; and the leaf node PE forwarding the multicast traffic according to reception instruction information, wherein the reception instruction information is used for instructing to perform the forwarding of the multicast traffic received from one root node PE in the first root node PE and the second root node PE, and the discarding of the multicast traffic received from the other root node PE.

Description

An EVPN multicast method, device and system

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office of China, the application number is 201910128906.4, and the application name is "An EVPN multicast method, device and system" on February 19, 2019, the entire content of which is by reference Incorporated in this application.

Technical field

The embodiments of the present application relate to the field of communication technology, and in particular to an Ethernet Virtual Private Network (EVPN) multicast method, device, and system.

Background technique

Figure 1 shows the EVPN multicast network architecture. As shown in Figure 1, the provider edge device (PE) 1 is configured as the root node of the multicast service, PE2～PE4 are the leaf nodes of the multicast service, and PE1 uses It is the root of itself, and PE2 to PE4 are leaves, and a point-to-multiple point (P2MP) tunnel is established. After that, the multicast traffic received by PE1 from CE1 can be imported into the P2MP tunnel, replicated in the tunnel, and transmitted to the leaf nodes PE2 to PE4.

Video multicast services cannot tolerate phenomena such as jams and screens. Therefore, operators have higher requirements for the reliability of EVPN multicast services. Currently, the EVPN multicast service adopts the EVPN multicast network architecture shown in Figure 2. In this architecture, CE 201 is dual-homed to the root node PE 202 and root node PE 203, providing the root node PE 202 and root node PE 203 respectively The two root tunnels transmit multicast traffic to improve transmission reliability. In the EVPN multicast network architecture shown in Figure 2, a local Ethernet link aggregation interface (Eth-Trunk) is configured for CE 201, and a root node PE 202 and root node PE 203 are configured with cross-device Ethernet link aggregation interfaces (E-Trunk) , If the multicast service is realized through dual-active mode or single-active mode. In the dual-active mode, the E-Trunk works in dual-active mode, and the access control (AC) side interfaces of the root node PE 202 and the root node PE 203 are both active (UP); in single-active mode. E-Trunk works in single-active mode, and the AC-side interfaces of the root node PE 202 and root node PE 203 only have one UP.

In order to ensure the handover performance when a link or node fails, a bidirectional forwarding detection (BFD) session is usually configured in the primary PE. One of the BFD sessions is connected to the local access controller (AC) interface (Eth- Trunk main interface) linkage, and another BFD session is configured with linkage quick cut under the Eth-Trunk main interface. When the AC interface is disconnected, the associated BFD session is associated and dropped. The non-primary PE senses that the BFD session is offline and informs the primary PE to switch quickly to reduce the packet loss time due to AC interface failure.

However, the above-mentioned method of configuring a BFD session to implement switching is very complicated, which increases the burden on the PE. When a link or node fails, the switching performance is not high.

Summary of the invention

This application provides an EVPN multicast method, device, and system, which reduce the burden on the PE through simple configuration and improve the switching performance when a link or node fails.

In order to achieve the foregoing objectives, the following technical solutions are adopted in the embodiments of this application:

In the first aspect, an EVPN multicast method is provided, which is applied to a leaf node PE in an EVPN multicast network. The EVPN multicast method provided in this application may include: the leaf node PE receives the same multicast traffic from the first root node PE and the second root node PE respectively; the leaf node PE forwards the multicast traffic according to the receiving instruction information. Wherein, the receiving instruction information is used to instruct to forward the multicast traffic received from one of the first root node PE and the second root node PE, and discard the multicast traffic received from the other root node PE.

Through the EVPN multicast method provided by this application, the leaf node PE receives the same multicast traffic from the first root node PE and the second root node PE, and selects the dual-root traffic according to the instructions of the receiving instruction information, and then forwards the multicast traffic. Complete the multicast service. Therefore, in the event of a link or node failure, you only need to configure the instruction content of the receiving instruction information to realize the switch when the dual-root traffic is selectively received. This process is time-consuming and short. The configuration is simple, and it does not burden the PE and is very good. Improved switching performance.

The EVPN multicast network further includes a first root node PE and a second root node PE; the leaf node PE that executes the EVPN multicast method provided in this application is any leaf node in the EVPN multicast system. The first node PE is the main root node, and the main root node PE is mainly responsible for the transmission of multicast traffic; the second root node PE is the alternate root node, and the alternate root node PE serves as the backup of the main root node. When the main root node PE fails, obtain the link When the path fails, the leaf node PE switches to forward the multicast traffic received from the alternate root node PE.

With reference to the first aspect, in a possible implementation manner, the EVPN multicast method provided in this application may further include: the leaf node PE receives type indication information sent by the first root node PE or the second root node PE, and the type indication The information is used to indicate that the first root node PE is the main root node, or the second root node PE is an alternative root node; the leaf node PE is configured to receive indication information, so that the reception indication information is used to indicate to forward the group received from the first root node PE Broadcast traffic, discard the multicast traffic received from the second root node PE. This implementation provides a specific solution for configuring the instruction content of the receiving instruction information, that is, in the initial configuration stage of the EVPN multicast system, the receiving instruction information is configured according to the active/standby type, which is used to preferentially receive multicast traffic from the primary root node PE Complete the multicast service.

With reference to the first aspect or any of the foregoing possible implementation manners, in a possible implementation manner, the EVPN multicast method provided in this application may further include: the leaf node PE receives the first root node PE or the second root node PE The routing information sent; the routing information includes type indication information; the routing information may also include at least one of the following information: tunnel type, tunnel identifier, and address of the root node PE that sends the routing information; the leaf nodes PE separately according to the routing information Establish a multicast label distribution protocol (multicast label distribution protocol, MLDP) tunnel with the first root node PE and the second root node PE.

In combination with the first aspect or any of the foregoing possible implementation manners, in a possible implementation manner, the foregoing routing information is an integrated multicast (inclusive multicast ethernet tag, IMET) routing, and the foregoing type indication information is included in the IMET routing The flag field of the operator's multicast service interface (provider multicast service interface, PMSI) attribute.

With reference to the first aspect or any of the foregoing possible implementation manners, in a possible implementation manner, the reception indication information is used to instruct to forward the multicast traffic received from the first root node PE, and discard the multicast traffic received from the second root node PE. When receiving multicast traffic, the EVPN multicast method provided in this application may further include: the leaf node PE determines that the disconnection duration of the first root node PE is greater than or equal to the first preset duration, and the leaf node PE configures the receiving instruction information so that the receiving The indication information is used to instruct to forward the multicast traffic received from the second root node PE, and discard the multicast traffic received from the first root node PE. This implementation provides a specific solution for configuring the instruction content of receiving instruction information, that is, when the link where the primary root node of the EVPN multicast system is located fails, the leaf node PE configures receiving instruction information and switches to the secondary root node PE Selectively receive multicast traffic to complete the multicast service.

With reference to the first aspect or any of the foregoing possible implementation manners, in a possible implementation manner, the reception indication information is used to indicate the multicast traffic received from the second root node PE, and the multicast traffic received from the first root node PE is discarded. For multicast traffic, the EVPN multicast method provided in this application may further include: the leaf node PE receives the multicast traffic sent by the first root node PE; the leaf node PE determines the second preset duration, and the leaf node PE configures the receiving instruction information , So that the reception indication information is used to indicate to forward the multicast traffic received from the first root node PE, and discard the multicast traffic received from the second root node PE. This implementation provides a specific solution for configuring the instruction content of the receiving instruction information, that is, due to the link failure of the primary root node PE of the EVPN multicast system, switch to the standby root node PE to selectively receive multicast traffic to complete the multicast After the service, if the leaf node PE receives multicast traffic from the primary root node PE again, the leaf node PE configures the receiving instruction information, and switches to selectively receive multicast traffic from the primary root node PE to complete the multicast service.

Combining the first aspect or any of the foregoing possible implementations, in a possible implementation, after the primary root node PE resumes traffic, the leaf node PE waits for the second preset period of time, and then configures the receiving instruction to switch to the secondary root node PE selectively receives multicast traffic. This application does not specifically limit the content of the second preset duration.

With reference to the first aspect or any of the foregoing possible implementation manners, in a possible implementation manner, a timer may be set, and the timer may time out, so that the leaf node PE waits for the second preset time period.

In combination with the first aspect or any of the foregoing possible implementation manners, in a possible implementation manner, the second preset duration may be between the time when the main root node PE resumes traffic and the time when the alternate root node PE is cut off. time interval. This application does not specifically limit the content of the second preset duration.

Combining the first aspect or any of the foregoing possible implementations, in one possible implementation, a detection period T can be configured, and the leaf node PE uses T as the period to perform traffic statistics to determine whether the root node is disconnected or recovers the traffic. .

In the second aspect, another EVPN multicast method is provided, which is applied to the customer edge device (CE) in the EVPN multicast network, the member port of the first outgoing port in the CE, and the first root node PE and the second The root node PE is connected separately, and the first outgoing port is configured to enable dual sending. The EVPN multicast method may include: the CE receives the multicast traffic and the destination address of the multicast traffic; if the first egress port in the broadcast table corresponds to the destination address, the CE sends the multicast to each member port of the first egress port flow. Among them, the broadcast table includes the address corresponding to each outgoing port in the CE.

Through the EVPN multicast method provided in this application, the outgoing port of the root node PE connected to the active and standby in the CE is configured to enable dual transmission, and the same source and dual transmission is realized on the CE to ensure the active and standby root node PEs. The root node PE receives two copies of the same multicast traffic from the same source and sends them to the leaf node PE; the leaf node PE selects and receives the dual-root traffic according to the instructions of the receiving instruction information, and forwards the multicast traffic to complete the multicast service, and then Realize the multicast service that has no burden on the PE and improves the switching performance.

Wherein, the EVPN multicast network also includes a first root node PE, a second root node PE, and two or more leaf nodes PE; the first root node PE is the main root node, and the second root node PE is the backup root node .

With reference to the second aspect, in a possible implementation manner, the CE is dual homed to the first root node PE and the second root node PE, and the CE configures the first egress port and binds the first root node PE and the second root node. The AC port of the PE serves as the member port of the first outgoing port.

In combination with the second aspect or any of the foregoing possible implementation manners, in a possible implementation manner, the first outgoing port is configured with enabling dual sending, which can be specifically implemented as follows: configuring enabling dual sending under the first outgoing port Command issued.

With reference to the second aspect or any of the foregoing possible implementation manners, in a possible implementation manner, the EVPN multicast method provided in this application may further include: the control plane of the CE generates the first The dual-transmission mark of an outgoing port is sent to the broadcast table record to indicate that the first outgoing port is configured with the same-origin dual transmission.

In the third aspect, another EVPN multicast method is provided, which is applied to the root node PE in an EVPN multicast network; the EVPN multicast network includes a first root node PE, a second root node PE, CE, and two or two The above leaf node PE; the root node PE that executes the EVPN multicast method is the first root node PE or the second root node PE. The first node PE is the main root node, and the second root node PE is the backup root node. The EVPN multicast method may include: the root node PE receives multicast traffic from the CE, and the multicast traffic is dual-transmitted from the CE to the first root node PE and the second root node PE; the root node PE passes between the leaf nodes PE The MLDP tunnel that sends the multicast traffic to the leaf node PE.

Through this EVPN multicast method, the primary and backup root node PEs receive two identical multicast traffic from the same source and send them to the leaf node PE, so that the leaf node PE selects from the dual-root traffic according to the instructions of the receiving instruction information. The multicast traffic is forwarded to complete the multicast service, thereby realizing the multicast service that has no burden on the PE and improves the switching performance.

With reference to the third aspect, in a possible implementation manner, the EVPN multicast method provided in this application may further include: the root node PE sends routing information to each leaf node PE, and the routing information includes at least one of the following information : Tunnel type, tunnel identifier, and address of the root node PE; the routing information is used to instruct the leaf node PE to establish an MLDP tunnel with the root node PE.

With reference to the third aspect or any possible implementation manner, in a possible implementation manner, the routing information is IMET routing.

With reference to the third aspect or any possible implementation manner, in a possible implementation manner, the routing information may further include type indication information, and the type indication information is used to indicate that the root node PE is the main root node or an alternative root node.

With reference to the third aspect or any possible implementation manner, in a possible implementation manner, the EVPN multicast method provided in this application may further include: the root node PE sends type indication information to each leaf node PE. The indication information is used to indicate that the root node PE is the main root node or alternative root node.

In a fourth aspect, another EVPN multicast method is provided, which is characterized by being applied to an EVPN multicast system. The EVPN multicast system includes a CE, a first root node PE, a second root node PE, and two or two The above leaf node PE. The member port of the first egress port in the CE is respectively connected to the first root node PE and the second root node PE, and the first egress port is configured to enable dual transmission. The EVPN multicast method may include: the CE receives the multicast traffic and the destination address of the multicast traffic; if the first egress port in the broadcast table corresponds to the destination address, the CE sends the multicast traffic to each member port of the first egress port; Among them, the broadcast table includes the address corresponding to each outgoing port in the CE. The first node PE receives multicast traffic from CE, and the first root node PE sends multicast traffic to the leaf node PE through the MLDP tunnel with each leaf node PE; the second root node PE receives the same source from CE The second root node PE sends multicast traffic to the leaf node PE through the MLDP tunnel between each leaf node PE; each leaf node PE receives the first root node PE and the second root node PE respectively The same multicast traffic; each leaf node PE forwards the multicast traffic according to the receiving instruction information. Wherein, the receiving instruction information is used to instruct to forward the multicast traffic received from one of the first root node PE and the second root node PE, and discard the multicast traffic received from the other root node PE.

It should be noted that the specific implementation of the EVPN multicast method provided by the fourth aspect may refer to the specific implementations of the aforementioned first aspect to the third aspect, which will not be repeated here.

In the fifth aspect, an embodiment of the present application also provides an EVPN multicast device for implementing the method described in the first aspect. The EVPN multicast device is a leaf node PE or a communication device that supports the leaf node PE to implement the method described in the first aspect. For example, the communication device includes a chip system. For example, the EVPN multicast device includes: a receiving unit, a processing unit, and a sending unit. The receiving unit is configured to receive the same multicast traffic from the first root node PE and the second root node PE respectively; the processing unit is configured to forward the received multicast traffic through the sending unit according to the instruction of the receiving instruction information. The receiving instruction information is used to instruct to forward the multicast traffic received from one of the first root node PE and the second root node PE, and discard the multicast traffic received from the other root node PE.

It should be noted that the specific implementation of each unit in the fifth aspect is the same as the corresponding method description in the first aspect, and will not be repeated here.

In the sixth aspect, the embodiments of the present application also provide an EVPN multicast device for implementing the method described in the second aspect. The EVPN multicast device is a CE or a communication device that supports the CE to implement the method described in the second aspect. For example, the communication device includes a chip system. For example, the EVPN multicast device includes: a receiving unit, a processing unit, and a sending unit. The receiving unit is configured to receive multicast traffic and the destination address of the multicast traffic; the processing unit is configured to, if the first outgoing port in the broadcast table corresponds to the destination address, send the sending unit to each member of the first outgoing port Port to send the multicast traffic. Among them, the broadcast table includes the address corresponding to each outgoing port in the CE.

It should be noted that the specific implementation of the sixth aspect is the same as the corresponding description in the second aspect, and will not be repeated here.

In the seventh aspect, the embodiments of the present application also provide an EVPN multicast device for implementing the method described in the third aspect. The EVPN multicast device is a root node PE or a communication device that supports the root node PE to implement the method described in the third aspect. For example, the communication device includes a chip system. For example, the EVPN multicast device includes: a receiving unit, a processing unit, and a sending unit. The receiving unit is used to receive multicast traffic from the CE; the processing unit is used to send the multicast traffic to the leaf node PE through the MLDP tunnel with the leaf node PE using the sending unit.

It should be noted that the specific implementation of the seventh aspect is the same as the corresponding description in the third aspect, and will not be repeated here.

In an eighth aspect, this application provides an EVPN multicast system. The EVPN multicast system includes a CE, a first root node PE, a second root node PE, and two or more leaf nodes PE. The member port of the first egress port in the CE is respectively connected to the first root node PE and the second root node PE, and the first egress port is configured to enable dual transmission. Among them, CE is used to receive multicast traffic and the destination address of the multicast traffic; if the first egress port in the broadcast table corresponds to the destination address, send the multicast traffic to each member port of the first egress port; where, broadcast The table includes the address corresponding to each outgoing port in the CE; the first root node PE is used to receive multicast traffic from the CE, and send multicast traffic to the leaf node PE through the MLDP tunnel with each leaf node PE; The second root node PE is used to receive multicast traffic from the CE and send multicast traffic to the leaf node PE through the MLDP tunnel with each leaf node PE; the leaf node PE is used to receive the group from the first root node PE Broadcast traffic, receiving multicast traffic from the second root node PE; forwarding the received multicast traffic according to the receiving instruction information; wherein the receiving instruction information is used to instruct forwarding from one of the first root node PE and the second root node PE The multicast traffic received by the root node PE discards the multicast traffic received from another root node PE.

It should be noted that the functional modules of the fifth, sixth, seventh, and eighth aspects described above can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions. For example, the transceiver is used to complete the functions of the receiving unit and the transmitting unit, the processor is used to complete the function of the processing unit, and the memory is used to process the program instructions of the method of the embodiment of the present application. The processor, the transceiver, and the memory are connected through a bus and communicate with each other.

In a ninth aspect, this application provides an EVPN multicast device, which can implement the function of the leaf node PE in the above method example. The function can be implemented by hardware or by hardware executing corresponding software. . The hardware or software includes one or more modules corresponding to the aforementioned functions. The EVPN multicast device can exist in the form of a chip product.

With reference to the ninth aspect, in a possible implementation manner, the structure of the EVPN multicast device includes a processor and a transceiver, and the processor is configured to support the EVPN multicast device to perform corresponding functions in the foregoing method. The transceiver is used to support communication between the EVPN multicast device and other devices. The EVPN multicast device may further include a memory, which is used for coupling with the processor and stores the necessary program instructions and data of the EVPN multicast device.

In a tenth aspect, this application provides an EVPN multicast device, which can implement the function of the CE in the foregoing method example, and the function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. The EVPN multicast device can exist in the form of a chip product.

With reference to the tenth aspect, in a possible implementation manner, the structure of the EVPN multicast device includes a processor and a transceiver, and the processor is configured to support the EVPN multicast device to perform corresponding functions in the foregoing method. The transceiver is used to support communication between the EVPN multicast device and other devices. The EVPN multicast device may further include a memory, which is used for coupling with the processor and stores the necessary program instructions and data of the EVPN multicast device.

In an eleventh aspect, this application provides an EVPN multicast device, which can implement the function of the root node PE in the above method example. The function can be implemented by hardware, or the corresponding software can be executed by hardware. achieve. The hardware or software includes one or more modules corresponding to the aforementioned functions. The EVPN multicast device can exist in the form of a chip product.

With reference to the eleventh aspect, in a possible implementation manner, the structure of the EVPN multicast device includes a processor and a transceiver, and the processor is configured to support the EVPN multicast device to perform corresponding functions in the foregoing method. The transceiver is used to support communication between the EVPN multicast device and other devices. The EVPN multicast device may further include a memory, which is used for coupling with the processor and stores the necessary program instructions and data of the EVPN multicast device.

In a twelfth aspect, a leaf node PE is provided, and the leaf node PE includes an EVPN multicast device that executes the EVPN multicast method provided in the first aspect or any one of the possible implementations of the first aspect.

In a thirteenth aspect, a CE is provided, and the CE includes an EVPN multicast device that executes the EVPN multicast method provided by the second aspect or any one of the possible implementation manners of the second aspect.

In a fourteenth aspect, a root node PE is provided, and the root node PE includes an EVPN multicast device that executes the EVPN multicast method provided by the third aspect or any one of the possible implementation manners of the third aspect.

In a fifteenth aspect, this application provides an EVPN multicast system, including two or more leaf nodes PE described in any one of the foregoing aspects or any possible implementation manner, and any one of the foregoing aspects or any one of the possible The CE described in the implementation mode, the root node PE described in any one of the foregoing aspects or any possible implementation mode configured as the primary root node, any one of the foregoing aspects or any possible implementation mode configured as an alternative root node Description of the root node PE of the description.

In a sixteenth aspect, a computer-readable storage medium is provided, including instructions, which when run on a computer, cause the computer to execute the EVPN multicast method provided by any one of the foregoing aspects or any possible implementation manner.

In a seventeenth aspect, a computer program product containing instructions is provided, which when running on a computer, causes the computer to execute the EVPN multicast method provided by any one of the above aspects or any possible implementation manner.

Among them, it should be noted that various possible implementation manners of any one of the above aspects can be combined on the premise that the solutions are not contradictory.

Description of the drawings

Figure 1 is a schematic diagram of an EVPN multicast network architecture;

Figure 2 is a schematic diagram of another EVPN multicast network architecture;

FIG. 3 is a schematic structural diagram of a PE provided by an embodiment of the application;

FIG. 4 is a schematic structural diagram of a CE provided by an embodiment of this application;

FIG. 5 is a schematic flowchart of an EVPN multicast method provided by an embodiment of this application;

6 is a schematic structural diagram of an EVPN multicast device provided by an embodiment of the application;

FIG. 7 is a schematic structural diagram of another EVPN multicast device provided by an embodiment of the application;

FIG. 8 is a schematic structural diagram of still another EVPN multicast device provided by an embodiment of this application;

FIG. 9 is a schematic structural diagram of another EVPN multicast device provided by an embodiment of this application;

FIG. 10 is a schematic structural diagram of another EVPN multicast device provided by an embodiment of this application;

FIG. 11 is a schematic structural diagram of another EVPN multicast device provided by an embodiment of this application;

FIG. 12 is a schematic structural diagram of a leaf node PE provided by an embodiment of this application;

FIG. 13 is a schematic structural diagram of a CE provided by an embodiment of this application;

FIG. 14 is a schematic structural diagram of a root node PE provided by an embodiment of this application;

FIG. 15 is a schematic structural diagram of an EVPN multicast system provided by an embodiment of this application.

detailed description

The terms "first", "second", and "third" in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to limit a specific order.

In the embodiments of the present application, words such as "exemplary" or "for example" are used as examples, illustrations, or illustrations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as "exemplary" or "for example" are used to present related concepts in a specific manner.

In order to make the description of the following embodiments clear and concise, a brief introduction of related technologies is first given:

EVPN technology is a point-to-point proprietary network technology virtualized on the public data network through tunnel technology. The basic principle of VPN is to use tunneling technology to encapsulate messages in tunnels and use the EVPN backbone network to establish a dedicated data transmission channel to achieve transparent transmission of messages.

Multicast (Multicast) transmission refers to the point-to-multipoint network connection between the sender and each receiver, which improves the efficiency of data transmission and reduces the possibility of congestion in the backbone network.

Video multicast services have been widely used in Internet protocol (IP) radio access networks (RAN), and EVPN is used to implement video multicast services. EVPN uses IMET routing to guide multicast traffic forwarding, and PEs send IMET routes to each other to form a multicast traffic member table to realize P2MP tunnel forwarding of multicast traffic, improve traffic forwarding efficiency and save public network bandwidth.

In order to improve the reliability of the multicast service, an EVPN multicast network architecture with CE dual-homing to PE as shown in Figure 2 is adopted. The dual-homing architecture improves transmission reliability by providing two tunnels with two root node PEs as the root respectively to transmit multicast traffic. However, when the tunnel of a certain root fails, the multicast service is switched to another root, which reflects the reliability of the multicast service. As mentioned above, in the EVPN multicast network architecture shown in Figure 2, the current switch is implemented by configuring a BFD session, which not only complicates the implementation and increases the burden on the PE, but also has low switching performance.

Based on this, the embodiment of the application provides an EVPN multicast method, the basic principle of which is: the root node PE of CE dual-homing is configured as the active and standby root node, and the two tunnels rooted at the active and standby root nodes transmit the same Multicast traffic is selectively received by the leaf node PE. When a link or node fails, the leaf node PE implements switching through selective reception, without increasing the burden on the PE and simply improving the switching performance.

Among them, the primary root node PE is mainly responsible for the transmission of multicast traffic, and the alternate root node PE serves as the backup of the primary root node. When the primary root node PE fails to obtain the link failure, the leaf node PE switches to forwarding the data received from the alternate root node PE Multicast traffic.

The EVPN multicast method provided in this application can be applied to the EVPN multicast network architecture shown in Figure 2. One of the two root nodes PE in the EVPN multicast network architecture is configured as the primary root node and the other as the alternate root. node. As shown in Figure 2, the EVPN multicast network architecture includes CE 301, root node PE 202 (configured as the primary root node), root node PE 203 (configured as an alternate root node), multiple leaf nodes PE 204, multiple CE 205 and P node 206.

Among them, CE 201 is used as a switch or router device connected to the multicast video server. The root node PE 202 and the root node PE 203 are routers close to the multicast source side and serve as the root node of the EVPN MLDP tunnel, that is, the entrance of the tunnel. The root node PE 203 serves as an alternative PE of the root node PE 202. CE 201 is dual homed to root node PE 202 and root node PE 203. Multiple leaf nodes PE 204 are routers on the user side, and serve as leaf nodes of the EVPN MLDP tunnel, that is, the exit of the tunnel. Multiple CEs 205 are switches or routers that connect video multicast service users. The P node 206 is a public network switching node with a heavy EVPN multicast network architecture.

It should be noted that Figure 2 is only an example description of the EVPN multicast network architecture, and the number of nodes included in the network architecture can be configured according to actual requirements.

Specifically, the root node PE 202 and the root node PE 203 include an EVPN module, and the leaf node PE 204 includes a label distribution protocol (label distribution protocol, LDP) module.

In the initial stage of EVPN multicast, the root node PE 202 and the root node PE 203 will notify the LDP module of the IMET route through the EVPN module to notify the leaf node PE 204 to create a P2MP MLDP tunnel. After the leaf node PE 204 receives the IMET route of each root node, the LDP module of the leaf node PE 204 triggers the creation of a P2MP MLDP tunnel from the leaf to the root. The leaf node searches for the route to the root node and sends the label map one hop The (label mapping) message indicates the completion of the tunnel establishment. Among them, IMET routing may include information such as tunnel type, tunnel identifier, and address of the root node PE.

It should be noted that, in the embodiment of this application, the process of establishing a tunnel between the root node PE and the leaf node PE will not be repeated. For the specific process, please refer to Request for Comments (RFC) 6388.

In the process of EVPN multicast, EVPN multicast traffic is carried on the public network P2MP MLDP tunnel, as shown by the black tree-shaped arrow line in Figure 2. When the CE 201 device receives the multicast traffic from the multicast source server, it sends the multicast traffic to the root node PE 202 and the root node PE 203 from the same source. The root node PE 202 and the root node PE 203 both import the multicast traffic into their respective MLDP tunnels for multicast stream distribution, and finally the leaf nodes receive the same duplicate multicast streams. The leaf node PE 204 selects traffic according to the received instruction information, forwards the multicast traffic received from one root node PE of the root node PE 202 and root node PE 203, and discards the multicast traffic received from the other root node PE to prevent Multi-packet traffic.

It should be noted that after the root node PE receives the multicast traffic from the CE, it encapsulates the multicast traffic into a message, and imports the message into the MLDP tunnel for multicast stream distribution. The message includes the root node PE and the leaf nodes Ingress label of the tunnel between PEs. Multicast traffic can be used as the payload of packets. In the full text of this application, the description of the root node PE sending multicast traffic is equivalent to the root node PE encapsulating the multicast traffic into a message to send; the leaf node PE receiving the multicast traffic is equivalent to the leaf node PE receiving from the tunnel. Packets of multicast traffic. The process of encapsulating the message by the root node PE will not be repeated in this embodiment of the application. The equivalent content can be substituted for each other. This will not be explained one by one later.

It should be noted that the actual product form of each network element in FIG. 2 can be configured according to actual requirements, and FIG. 2 only illustrates the type of each network element by way of example, and does not specifically limit this.

The embodiments of the present application will be described in detail below in conjunction with the drawings.

On the one hand, an embodiment of the present application provides a PE 30. FIG. 3 shows a type of PE 30 related to various embodiments of the present application. As shown in FIG. 3, the PE 30 may include a processor 301, a memory 302, and a transceiver 303.

The following describes the components of PE 30 in detail with reference to Figure 3:

The memory 302 may be a volatile memory (volatile memory), such as random-access memory (RAM); or a non-volatile memory (non-volatile memory), such as read-only memory (read-only memory). memory, ROM), flash memory (flash memory), hard disk (HDD) or solid-state drive (solid-state drive, SSD); or a combination of the above-mentioned types of memory, used to store materials that can implement the method of this application Program code, configuration files or other content.

The processor 301 is the control center of the PE 30, which can be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or is configured to implement the embodiments of this application One or more integrated circuits, such as one or more microprocessors (digital digital processors, DSP), or one or more field programmable gate arrays (FPGA).

The transceiver 303 is used for communication with other devices and data transmission.

In a possible implementation, PE 30 can be configured as a leaf node PE 204 in the EVPN multicast network architecture shown in FIG. 2. The processor 301 runs or executes software programs and/or modules stored in the memory 302, and calls The data stored in the memory 302 performs the following functions:

Receive the same multicast traffic from the first root node PE and the second root node PE through the transceiver 303; forward the multicast traffic according to the receiving instruction information, and the receiving instruction information is used to instruct the forwarding from the first root node PE and the second root node The multicast traffic received by one root node PE in the PE discards the multicast traffic received from another root node PE.

In a possible implementation, the PE 30 can be configured as the root node PE 202 or the root node PE 203 in the EVPN multicast network architecture shown in FIG. 2, and the processor 301 runs or executes the software program and/or stored in the memory 302 Or module, and call the data stored in the memory 302, perform the following functions:

The transceiver 303 receives multicast traffic from the CE, and sends the multicast traffic to the leaf node PE through the MLDP tunnel with each leaf node PE.

On the other hand, an embodiment of the present application provides a CE 40. Figure 4 shows a CE 40 related to various embodiments of the present application. As shown in FIG. 4, the CE 40 may include: a processor 401, a memory 402, and a transceiver 403.

The following is a detailed introduction to the components of CE 40 in conjunction with Figure 4:

The memory 402 may be a volatile memory (volatile memory), such as RAM; or a non-volatile memory, such as read-only memory (ROM), flash memory (flash memory), HDD or SSD; or the above A combination of different types of memories is used to store program codes and configuration files that can implement the method of the present application.

The processor 401 is the control center of the CE 40. It can be a CPU, an ASIC, or one or more integrated circuits configured to implement the embodiments of the present application, such as one or more DSPs, or, one or Multiple FPGAs. The processor 401 can execute various functions of the CE 40 by running or executing software programs and/or modules stored in the memory 402, and calling data stored in the memory 402.

The transceiver 403 is used for the CE 40 to interact with other units.

Specifically, the processor 401 executes the following functions by running or executing software programs and/or modules stored in the memory 402, and calling data stored in the memory 402:

The multicast traffic and the destination address of the multicast traffic are received through the transceiver 403; if the outgoing port corresponding to the destination address in the broadcast table is configured with dual sending enabled, the multicast traffic is sent to each member port of the outgoing port.

In another aspect, the embodiments of the present application provide an EVPN multicast method, which is applied to an EVPN multicast system. The EVPN multicast system includes a CE, a first root node PE, a second root node PE, and two or more Leaf node PE. Among them, the CE is dual homed to the first root node PE and the second root node PE; the member port of the first egress port in the CE is connected to the first root node PE and the second root node PE respectively, and the first egress port is configured with an enable Double shot. The first node PE is configured as the main root node, and the second root node PE is configured as the alternate root node. In the following, a process in which the CE, the first root node PE, the second root node PE, and the leaf node PE implement a multicast service through interaction is taken as an example to describe the EVPN multicast method provided in this application in detail.

The EVPN multicast system can be the EVPN multicast network architecture shown in Figure 2. The CE in the following content can be CE 201 in Figure 2, and the first root node PE can be the root node as the master root node in Figure 2. PE 202, the second root node PE may be the root node PE 203 as a candidate root node in FIG. 2, and the leaf node PE may be the leaf node PE 204 in FIG. 2.

Before multicasting, you need to configure the EVPN multicast system, which is briefly described below.

First, the administrator configures the attributes of the PE to configure the primary root node, alternative root nodes, and leaf nodes.

Exemplarily, the following configuration may be performed on the first root node PE, and the attributes of the first root node PE may be configured as the main root node:

evpn vpn-instance xxx

inclusive-provider-tunnel

root

master

Exemplarily, the following configuration may be performed on the second root node PE, and the attributes of the second root node PE may be configured as candidate root nodes:

evpn vpn-instance xxx

inclusive-provider-tunnel

root

slave

Exemplarily, the following configuration can be performed on the leaf node PE, and the attribute of the leaf node PE is configured as the leaf node:

evpn vpn-instance xxx

inclusive-provider-tunnel

leaf

It should be noted that the configuration content of the foregoing example is only an example and does not constitute a specific limitation.

In the initial stage, the root node PE sends an IMET route to the leaf node PE. After receiving the IMET route, the leaf node PE triggers the creation of a P2MP MLDP tunnel from the leaf to the root according to the content of the IMET route, which is used to carry multicast traffic.

Secondly, the administrator configures CE to achieve dual transmission from the same source. Specifically, you can configure the first egress port on the CE, configure the same-source dual command under the Eth-Trunk interface, and connect the first egress port and the CE to the AC ports of the first root node PE and the second root node PE. Binding, as the member port of the first out port. The control plane of the CE obtains the configured dual-source command of the same source, generates a dual-transfer flag of the first outgoing port, and downloads the dual-transfer flag to the broadcast table for recording to instruct the first outgoing port to perform dual-source dual sending.

Exemplarily, the same-source dual-sending command can be configured as: multicast-dual-sending enable. The first outgoing port is the Eth-Trunk interface.

The following describes the specific multicast process. As shown in FIG. 5, the EVPN multicast method provided by the embodiment of the present application may include:

S501. The CE receives the multicast traffic and the destination address of the multicast traffic.

Specifically, in S501, the CE receives the multicast traffic and the destination address of the multicast traffic from the multicast video server. Among them, the multicast traffic is business data of the current multicast service, and the destination address is used to indicate the destination device to which the multicast traffic is sent. The CE can query the broadcast table according to the destination address, determine the outgoing port corresponding to the destination address in the broadcast table, and then send the multicast traffic out through the outgoing port. The outgoing port is connected to the root node PE of the EVPN network, and the multicast traffic can be sent to the root node PE.

Among them, the broadcast table is a layer 2 forwarding table, used to instruct the CE to send multicast traffic. The broadcast table includes the address corresponding to each egress port in the CE. In the broadcast table, one address can correspond to at least one egress port. When the CE receives multicast traffic, it searches for the corresponding egress port in the broadcast table according to the destination address of the multicast traffic, and sends the multicast traffic from the corresponding egress port to realize the transmission of multicast traffic. The broadcast table is configured by the CE operator according to the EVPN network architecture. This application does not limit the specific content and configuration process of the broadcast table.

S502: If the first egress port in the broadcast table corresponds to the destination address, the CE sends multicast traffic to each member port of the first egress port.

Wherein, since the first outgoing port is recorded in the broadcast table for dual transmission of the same origin, if the first outgoing port in the broadcast table corresponds to the destination address, it indicates that the multicast traffic received by the CE in S501 is dual transmitted from the same origin.

Specifically, the member port of the first egress port is the AC port connecting the first root node PE and the second root node PE, and the CE sends multicast traffic to each member port of the first egress port, then the multicast traffic is sent Arriving at the first root node PE and the second root node PE, the first root node PE and the second root node PE have received two copies of the same multicast traffic from the same source.

S503. The first root node PE receives the multicast traffic from the CE, and the first root node PE sends the multicast traffic to the leaf node PE through the MLDP tunnel with each leaf node PE.

S504. The second root node PE receives the multicast traffic from the CE, and the second root node PE sends the multicast traffic to the leaf node PE through the MLDP tunnel with each leaf node PE.

Among them, the multicast traffic received by the first root node PE/second root node PE in S503 and S504 is the multicast traffic of the same source and dual transmission of CE in S502.

Specifically, in S503 and S504, the first root node PE/the second root node PE sends multicast traffic to the leaf node PE through the MLDP tunnel with each leaf node PE, which can be specifically implemented as: the first root node PE /The second root node PE encapsulates the multicast traffic carrying the incoming label of the MLDP tunnel between it and the leaf node PE into a message, and sends the encapsulated message to the leaf node PE. The incoming label in the message is used for the message to be forwarded in the MLDP tunnel according to the label forwarding protocol.

S505: The leaf node PE receives the same multicast traffic from the first root node PE and the second root node PE.

The multicast traffic received by the leaf node PE in S505 is the multicast traffic in the packet sent by the first root node PE/second root node PE in S503 and S504 encapsulated and sent.

S506: The leaf node PE forwards the multicast traffic according to the receiving instruction information.

Wherein, the receiving instruction information is used to indicate which root node the leaf node PE is currently receiving multicast traffic from. It can also be understood that the receiving instruction information is used to instruct the leaf node PE to forward the multicast traffic received from which root node. Specifically, the receiving instruction information is used to instruct to forward the multicast traffic received from one of the first root node PE and the second root node PE, and discard the multicast traffic received from the other root node PE.

Specifically, in S505, the leaf node PE forwards the multicast traffic received from the root node PE that receives the multicast traffic indicated by the receiving instruction information to the video multicast service user side according to the destination address according to the instruction of the receiving instruction information. CE to complete the multicast service; the leaf node PE discards the multicast traffic received from the root node PE that discards the multicast traffic indicated by the receiving instruction information, so as to prevent the traffic from being multi-packetized.

In a possible implementation, the reception indication information may be X-bit indication information, and different values are assigned to the reception indication information to indicate different content. The value of X can be configured according to actual needs, which is not specifically limited in the embodiment of the present application.

Exemplarily, the receiving indication information may be 1-bit indication information. Assign a value of 0 to the reception indication information to indicate to forward the multicast traffic received from the first root node PE, and discard the multicast traffic received from the second root node PE; to assign a value of 1 to the reception indication information to indicate to forward the multicast traffic received from the first root node PE The multicast traffic received by the root node PE discards the multicast traffic received from the second root node PE.

In a possible implementation, the receiving indication information may be a root node PE working state mapping relationship. In the mapping relationship, the identifiers of the first root node PE and the second root node PE correspond to their respective working states, and the working state Assign different values to indicate whether to forward the multicast traffic sent by the root node PE.

Wherein, the identifiers of the first root node PE and the second root node PE are used to uniquely identify the root node PE, and the content of the identifiers of the first root node PE and the second root node PE is not specifically limited in this application.

In a possible implementation, the identifiers of the first root node PE and the second root node PE may be the inbound labels of the MLDP tunnel between the PE and the leaf node PE.

In another possible implementation, the identifiers of the first root node PE and the second root node PE may be their addresses. The address can be an IP address or a MAC address.

Exemplarily, Table 1 illustrates a mapping relationship of the working state of the root node PE. In the mapping relationship shown in Table 1, the identifiers of the first root node PE and the second root node PE can be the inbound label of the MLDP tunnel between the PE and the leaf node PE, and the working state assignment 1 indicates that the packet containing the corresponding inbound label is forwarded. For the multicast traffic in the text, the working status is assigned 0 to indicate that the packet containing its corresponding incoming label is discarded.

Table 1

It should be noted that Table 1 merely illustrates the solution of receiving the indication information as the working state mapping relationship of the root node PE by way of example, and does not specifically limit the content and form of the mapping relationship.

Specifically, the configuration for receiving the indication information can be configured according to actual requirements, which is not specifically limited in the embodiment of the present application.

The following describes several specific implementations (the following three implementations) for configuring the instruction content of the leaf node PE to receive the instruction information. The configuration of the leaf node PE to receive the instruction information refers to that the service node PE adjusts the instruction content of the receiving instruction information and changes the root node PE of the leaf node PE to selectively receive multicast traffic.

The first implementation: In the initial stage of the EVPN network, the leaf node PE receives the type indication information sent by the first root node PE or the second root node PE. The type indication information is used to indicate the attributes of the root node PE, that is, to indicate the first root node PE. The node PE is the main root node or the second root node PE is the candidate root node. Based on this, the leaf node PE configures the receiving instruction information, so that the receiving instruction information is used to instruct to forward the multicast traffic received from the first root node PE and discard the multicast traffic received from the second root node PE.

Optionally, the type indication information may be separately sent by the root node PE to the leaf node PE. The type indication information can be sent by the first root node PE to the leaf node PE, can also be sent by the second root node PE to the leaf node PE, and can also be sent by the first root node PE and the second node PE to the leaf node. For example, the leaf node PE receives the first root node PE sent by the first root node PE as the master root node, or the leaf node PE receives the second root node sent by the second root node PE as the candidate root node.

Optionally, the type indication information may be included in the routing information sent by the root node PE to the leaf node PE for establishing the tunnel.

In a possible implementation, the leaf node PE receives routing information sent by the first root node PE and the second root node PE, and the routing information includes the foregoing type indication information. The routing information is used to instruct the leaf node PE to respectively establish MLDP tunnels with the first root node PE and the second root node PE. The routing information may also include at least one of the following information: tunnel type, tunnel identifier, and the address of the root node PE that sends the routing information.

Exemplarily, the foregoing routing information may be an IMET route, and the foregoing type indication information is included in a flag field of the PTMSI attribute in the IMET route. For example, in the Flag field of the extended PTMSI attribute, the 6th bit in the Flag field, 1 represents Master, that is, the primary root, and 0 represents Slave, that is, the backup root.

The foregoing example only illustrates the position and form of the type indication information in the routing information by way of example, and does not specifically limit this. The position of the type indication information in the routing information is not specifically limited in the embodiment of the present application, and can be configured according to actual requirements.

The second implementation: when the receiving instruction information is used to instruct to forward the multicast traffic received from the first root node PE and discard the multicast traffic received from the second root node PE, if the leaf node PE determines that the first root node PE is disconnected The flow duration is greater than or equal to the first preset duration, that is, the leaf node PE determines that the link where the primary root node PE is located is faulty and cannot receive multicast traffic (including the primary root node PE failure, or the AC port of the primary root node PE connected to the CE fails. , Or other reasons), at this time, the leaf node PE is configured to receive instruction information, so that the receiving instruction information is used to instruct to forward the multicast traffic received from the second root node PE, and discard the multicast traffic received from the first root node PE.

Among them, the value of the first preset duration can be configured according to actual needs, which is not specifically limited in the embodiment of the present application.

The third implementation: when the receiving instruction information is used to indicate the multicast traffic received from the second root node PE, and the multicast traffic received from the first root node PE is discarded, the leaf node PE receives the transmission from the first root node PE again If the multicast traffic of the primary root node PE is restored, the leaf node PE determines the second preset duration and configures the receiving instruction information so that the receiving instruction information is used to instruct to forward the multicast received from the first root node PE Traffic, discarding the multicast traffic received from the second root node PE, that is, switching back to receiving the multicast traffic sent by the primary root node PE.

In a possible implementation manner, after the primary root node PE restores traffic, the leaf node PE waits for the second preset period of time, and then configures receiving instruction information to switch to selectively receiving multicast traffic from the primary root node PE. This application does not specifically limit the content of the second preset duration, and the value of the second preset duration can be configured according to actual needs.

Exemplarily, a timer may be set, and the timer may time out, so that the leaf node PE waits for the second preset period of time.

In a possible implementation manner, the second preset duration may be the time interval between the time when the main root node PE resumes traffic and the time when the candidate root node PE cuts off traffic.

Further, a detection period T can be configured, and the leaf node PE uses T as the period to perform traffic statistics to determine whether the root node is disconnected.

The value of T can be configured according to actual requirements, which is not specifically limited in the embodiment of the present application. The shorter the T configuration, the shorter the switching time. For example, assuming that T is set to 20ms, when a fault occurs, the switching time does not exceed 50ms, which can meet the reliability requirements of the video multicast service.

In a possible implementation, the leaf node PE records the multicast traffic counted in the period T as a traffic statistics value. The traffic statistics value can be recorded separately or combined with the working state mapping relationship of the root node PE. This embodiment of the application There is no specific limitation on this.

Exemplarily, Table 2 illustrates a recording method for the leaf node PE to perform traffic statistics.

Table 2

It should be noted that the above three implementations only enumerate several possible situations of configuring receiving instruction information, but do not specifically limit the configuration receiving instruction information.

It should be noted that in the EVPN multicast network architecture, each leaf node PE performs the same operation. In the following embodiments, only the process of one leaf node PE performing the EVPN multicast method is described, and the rest will not be described one by one.

It should also be noted that the execution order of the steps included in FIG. 5 can be configured according to actual requirements. FIG. 5 only illustrates a possible execution order of the steps, and is not a specific limitation on this.

The foregoing mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various network elements. It can be understood that, in order to realize the above functions, the PE and CE included in the above-mentioned EVPN multicast system include hardware structures and/or software modules corresponding to each function. The functional unit in PE and CE that implements the above-mentioned EVPN multicast method is called an EVPN multicast device. Those skilled in the art should easily realize that in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiments of the present application may divide the EVPN multicast device into functional modules according to the foregoing method examples. For example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

In the case of dividing each functional module corresponding to each function, FIG. 6 shows a possible schematic structural diagram of the EVPN multicast device 60 deployed in the leaf node PE involved in the foregoing embodiment. The EVPN multicast device 60 may be the leaf node PE itself, or may be a functional module or chip in the leaf node PE. As shown in FIG. 6, the EVPN multicast device 60 may include: a receiving unit 601, a processing unit 602, and a sending unit 603. The receiving unit 601 is used to perform the process S505 in FIG. 5; the processing unit 602 is used to perform the process S506 in FIG. 5 through the sending unit 603. Among them, all relevant content of each step involved in the above method embodiment can be cited in the function description of the corresponding function module, and will not be repeated here.

Further, as shown in FIG. 6, the EVPN multicast device 60 may further include a configuration unit 604 and an establishment unit 605. Wherein, the configuration unit 604 is used to configure the receiving instruction information; the establishing unit 605 is used to establish an MLDP tunnel with the first root node PE and the second root node PE.

In the case of using an integrated unit, FIG. 7 shows a possible schematic structural diagram of the EVPN multicast device 70 deployed in the leaf node PE involved in the foregoing embodiment. The EVPN multicast device 70 may be the leaf node PE itself, or may be a functional module or chip in the leaf node PE. The EVPN multicast device 70 may include: a processing module 701 and a communication module 702. The processing module 701 is used to control and manage the actions of the EVPN multicast device 70. For example, the processing module 701 is used to execute the process S506 in FIG. 5; the communication module 702 is used to execute the process S505 in FIG. The EVPN multicast device 70 may further include a storage module 703 for storing program codes and data of the EVPN multicast device 70.

The processing module 701 may be the processor 301 in the physical structure of the PE 30 shown in FIG. 3, and may be a processor or a controller. For example, it may be a CPU, a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application. The processor 701 may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication module 702 may be the transceiver 303 in the physical structure of the PE 30 shown in FIG. 3, and the communication module 702 may be a communication port, or may be a transceiver, a transceiver circuit, or a communication interface. Alternatively, the above-mentioned communication interface may realize communication with other devices through the above-mentioned element having a transceiver function. The above-mentioned elements with transceiving functions can be implemented by antennas and/or radio frequency devices. The storage module 703 may be the memory 303 in the physical structure of the PE 30 shown in FIG. 3.

When the processing module 701 is a processor, the communication module 702 is a transceiver, and the storage module 703 is a memory, the EVPN multicast device 70 involved in FIG. 7 in the embodiment of the present application may be the PE 30 shown in FIG. 3.

As mentioned above, the EVPN multicast device 60 or the EVPN multicast device 70 provided by the embodiments of the present application can be used to implement the functions of the leaf node PE in the methods implemented in the above embodiments of the present application. For ease of description, only the For the relevant parts of the application embodiment, and the specific technical details are not disclosed, please refer to each embodiment of the application.

In the case of dividing each functional module corresponding to each function, FIG. 8 shows a possible schematic structural diagram of the EVPN multicast device 80 deployed in the CE involved in the foregoing embodiment. The EVPN multicast device 80 may be the CE itself, or a functional module or chip in the CE. As shown in FIG. 8, the EVPN multicast device 80 may include: a receiving unit 801, a processing unit 802, and a sending unit 803. The receiving unit 801 is configured to execute the process S501 in FIG. 5; the processing unit 802 is configured to execute the process S502 in FIG. 5 through the sending unit 803. Among them, all relevant content of each step involved in the above method embodiment can be cited in the function description of the corresponding function module, and will not be repeated here.

In the case of using an integrated unit, FIG. 9 shows a schematic diagram of a possible structure of the EVPN multicast device 90 deployed in the CE involved in the foregoing embodiment. The EVPN multicast device 90 may be the CE itself, or a functional module or chip in the CE. The EVPN multicast device 90 may include: a processing module 901 and a communication module 902. The processing module 901 is used to control and manage the actions of the EVPN multicast device 90. For example, the processing module 901 is used to execute the process S501 in FIG. 5; the communication module 902 is used to execute the process S502 in FIG. The EVPN multicast device 90 may further include a storage module 903 for storing program codes and data of the EVPN multicast device 90.

The processing module 901 may be the processor 401 in the physical structure of the CE 40 shown in FIG. 4, and may be a processor or a controller. For example, it may be a CPU, a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application. The processor 901 may also be a combination that implements computing functions, for example, it includes a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication module 902 may be the transceiver 403 in the physical structure of the CE 40 shown in FIG. 4, and the communication module 902 may be a communication port, or may be a transceiver, a transceiver circuit, or a communication interface. Alternatively, the above-mentioned communication interface may realize communication with other devices through the above-mentioned element having a transceiver function. The above-mentioned elements with transceiving functions can be implemented by antennas and/or radio frequency devices. The storage module 903 may be the memory 403 in the physical structure of the CE 40 shown in FIG. 4.

When the processing module 901 is a processor, the communication module 902 is a transceiver, and the storage module 903 is a memory, the EVPN multicast device 90 involved in FIG. 9 of the embodiment of the present application may be the CE 40 shown in FIG. 4.

As mentioned above, the EVPN multicast device 80 or the EVPN multicast device 90 provided by the embodiments of the present application can be used to implement the functions of the CE in the methods implemented by the various embodiments of the present application. For ease of description, only the implementation of the present application is shown. For the relevant parts of the example, and the specific technical details are not disclosed, please refer to the embodiments of this application.

In the case of dividing each functional module corresponding to each function, FIG. 10 shows a possible schematic structural diagram of the EVPN multicast device 100 deployed in the root node PE involved in the foregoing embodiment. The EVPN multicast device 100 may be the root node PE itself, or may be a functional module or chip in the root node PE. As shown in FIG. 10, the EVPN multicast device 100 may include: a receiving unit 1001, a processing unit 1002, and a sending unit 1003. The receiving unit 1001 is used to execute the processes S503 and S504 in FIG. 5; the processing unit 1002 is used to execute the processes S503 and S504 in FIG. 5 through the sending unit 1003. Among them, all relevant content of each step involved in the above method embodiment can be cited in the function description of the corresponding function module, and will not be repeated here.

In the case of using an integrated unit, FIG. 11 shows a schematic diagram of a possible structure of the EVPN multicast device 110 deployed in the root node PE involved in the foregoing embodiment. The EVPN multicast device 110 may be the root node PE itself, or may be a functional module or chip in the root node PE. The EVPN multicast device 110 may include: a processing module 1101 and a communication module 1102. The processing module 1101 is used to control and manage the actions of the EVPN multicast device 110. For example, the processing module 1101 is used to execute the processes S503 and S504 in FIG. 5; the communication module 1102 is used to execute the processes S503 and S504 in FIG. The EVPN multicast device 110 may further include a storage module 1103 for storing program codes and data of the EVPN multicast device 110.

The processing module 1101 may be the processor 301 in the physical structure of the PE 30 shown in FIG. 3, and may be a processor or a controller. For example, it may be a CPU, a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application. The processor 1101 may also be a combination that implements computing functions, for example, includes a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication module 1102 may be the transceiver 303 in the physical structure of the PE 30 shown in FIG. 3, and the communication module 1102 may be a communication port, or may be a transceiver, a transceiver circuit, or a communication interface. Alternatively, the above-mentioned communication interface may realize communication with other devices through the above-mentioned element having a transceiver function. The above-mentioned elements with transceiving functions can be implemented by antennas and/or radio frequency devices. The storage module 1103 may be the memory 303 in the physical structure of the PE 30 shown in FIG. 3.

When the processing module 1101 is a processor, the communication module 1102 is a transceiver, and the storage module 1103 is a memory, the EVPN multicast device 110 involved in FIG. 11 in the embodiment of the present application may be the PE 30 shown in FIG. 3.

As mentioned above, the EVPN multicast device 100 or the EVPN multicast device 110 provided in the embodiments of the present application can be used to implement the functions of the root node PE in the methods implemented in the various embodiments of the present application. For ease of description, only the For the relevant parts of the embodiments and the specific technical details that are not disclosed, please refer to the embodiments of this application.

As shown in FIG. 12, an embodiment of the present application provides a leaf node PE 120, which includes an EVPN multicast device 60 or an EVPN multicast device 70.

As shown in FIG. 13, an embodiment of the present application provides a CE 130, which includes an EVPN multicast device 80 or an EVPN multicast device 90.

As shown in FIG. 14, an embodiment of the present application provides a root node PE 140, which includes an EVPN multicast device 100 or an EVPN multicast device 110.

The embodiment of the application provides an EVPN multicast system, which includes two or more leaf nodes PE 120 and CE 130, a root node PE 140 configured as a primary root node, and a root node PE 140 configured as an alternate root node.

As shown in FIG. 15, an embodiment of the present application provides an EVPN multicast system 150, which includes a CE 1501, a first root node PE 1502, a second root node PE 1503, and two or more leaf nodes PE 1504. Among them, the member port of the first egress port in CE 1501 is respectively connected to the first root node PE 1502 and the second root node PE 1503, and the first egress port is configured to enable dual transmission.

Among them, CE 1501 is used to receive multicast traffic and the destination address of the multicast traffic; if the first egress port in the broadcast table corresponds to the destination address, send the multicast traffic to each member port of the first egress port; where, The broadcast table includes the address corresponding to each egress port in the CE.

The first node PE 1502 is used to receive multicast traffic from CE 1501, and send multicast traffic to the leaf node PE 1504 through the MLDP tunnel with each leaf node PE 1504.

The second root node PE 1503 is used to receive multicast traffic from the CE 1501, and send multicast traffic to the leaf node PE 1504 through the MLDP tunnel with each leaf node PE 1504.

The leaf node PE 1504 is used to receive multicast traffic from the first root node PE 1502, and receive multicast traffic from the second root node PE 1502; forward the received multicast traffic according to the receiving instruction information; among them, the receiving instruction information is used To instruct to forward the multicast traffic received from one of the first root node PE and the second root node PE, and discard the multicast traffic received from the other root node PE.

As another form of this embodiment, a computer-readable storage medium is provided, and an instruction is stored thereon. When the instruction is executed, the intention processing method in the foregoing method embodiment is executed.

As another form of this embodiment, a computer program product containing instructions is provided, and when the instructions are executed, the intention processing method in the foregoing method embodiment is executed.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

Those skilled in the art should be aware that in one or more of the above examples, the functions described in this application can be implemented by hardware, software, firmware or any combination thereof. When implemented by software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on the computer-readable medium. The computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer. Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical or other forms.

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, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may be separately physically included, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional units.

The above-mentioned integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The above-mentioned software functional unit is stored in a storage medium and includes several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute some steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application. The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention. It should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

An EVPN multicast method, characterized in that it is applied to a leaf node operator boundary device PE in an Ethernet virtual private network EVPN multicast network, and the method includes:

The leaf node PE receives multicast traffic from the first root node PE;

The leaf node PE receives the multicast traffic from the second root node PE;

The leaf node PE forwards the multicast traffic according to receiving instruction information, where the receiving instruction information is used to instruct to forward all received from one of the first root node PE and the second root node PE. The multicast traffic is discarded from the multicast traffic received from another root node PE.
The method of claim 1, wherein the method further comprises:

The leaf node PE receives type indication information sent by the first root node PE or the second root node PE, where the type indication information is used to indicate that the first root node PE is the master root node or the second root node PE The root node PE is a candidate root node;

The leaf node PE configures the receiving instruction information so that the receiving instruction information is used to instruct to forward the multicast traffic received from the first root node PE, and discard all the received from the second root node PE. The multicast traffic.
The method according to claim 1 or 2, wherein the receiving instruction information is used to instruct to forward the multicast traffic received from the first root node PE, and discard the multicast traffic received from the second root node PE. When the multicast traffic is received, the method further includes:

The leaf node PE determines that the disconnection duration of the first root node PE is greater than or equal to the first preset duration, and the leaf node PE configures the receiving instruction information so that the receiving instruction information is used to instruct forwarding from the The multicast traffic received by the second root node PE discards the multicast traffic received from the first root node PE.
The method according to claim 3, wherein the receiving instruction information is used to instruct the multicast traffic received from the second root node PE to discard all the multicast traffic received from the first root node PE When the multicast traffic is described, the method further includes:

The leaf node PE receives the multicast traffic sent by the first root node PE;

The leaf node PE determines a second preset duration, configures the reception instruction information so that the reception instruction information is used to instruct to forward the multicast traffic received from the first root node PE, and discard the multicast traffic received from the first root node PE. The multicast traffic received by the second root node PE.
The method of claim 2, wherein the method further comprises:

The leaf node PE receives routing information sent by the first root node PE or the second root node PE; the routing information includes the type indication information; the routing information further includes at least one of the following information : Tunnel type, tunnel identifier, and address of the root node PE that sends the routing information;

The leaf node PE separately establishes a multicast label forwarding protocol MLDP tunnel with the first root node PE and the second root node PE according to the routing information.
An EVPN multicast method, characterized in that it is applied to an Ethernet virtual private network EVPN multicast system. The EVPN multicast system includes a user border device CE, a first root node PE, a second root node PE, and two or Two or more leaf nodes PE, member ports of the first egress port in the CE are respectively connected to the first root node PE and the second root node PE, and the first egress port is configured to enable dual transmission, The method includes:

The CE receives the multicast traffic and the destination address of the multicast traffic;

If the first egress port in the broadcast table corresponds to the destination address, the CE sends the multicast traffic to each member port of the first egress port, where the broadcast table includes the CE’s The address corresponding to each out port;

The first root node PE receives the multicast traffic from the CE, and the first root node PE transmits the multicast label distribution protocol MLDP tunnel with each of the leaf nodes PE to the leaf node PE Sending the multicast traffic;

The second root node PE receives the multicast traffic from the CE, and the second root node PE sends the multicast traffic to the leaf node PE through the MLDP tunnel with each of the leaf nodes PE flow;

Each of the leaf nodes PE receives the multicast traffic from the first root node PE;

Each of the leaf nodes PE receives the multicast traffic from the second root node PE;

Each of the leaf nodes PE forwards the multicast traffic according to receiving instruction information; wherein, the receiving instruction information is used to instruct the forwarding to receive from one of the first root node PE and the second root node PE And discard the multicast traffic received from another root node PE.
An EVPN multicast device, characterized in that the device includes a receiving unit, a processing unit, and a sending unit, wherein,

The receiving unit is configured to receive the same multicast traffic from the first root node PE and the second root node PE respectively;

The processing unit is configured to forward the multicast traffic received by the receiving unit through the sending unit according to receiving instruction information, and the receiving instruction information is used to instruct to forward the multicast traffic received from the first root node PE, the The multicast traffic received by one root node PE in the second root node PE discards the multicast traffic received from another root node PE.
The device according to claim 7, wherein:

The receiving unit is further configured to receive type indication information sent by the first root node PE or the second root node PE, where the type indication information is used to indicate that the first root node PE is the main root node or The second root node PE is a candidate root node;

The device further includes a configuration unit, configured to configure the reception indication information when the receiving unit receives the type indication information, so that the reception indication information is used to instruct to forward the reception from the first root node PE And discard the multicast traffic received from the second root node PE.
The apparatus according to claim 7 or 8, wherein the receiving instruction information is used to instruct to forward the multicast traffic received from the first root node PE, and discard the multicast traffic received from the second root node PE When the multicast traffic is received, the apparatus further includes:

The configuration unit is configured to configure the receiving instruction information when it is determined that the PE disconnection duration of the first root node is greater than or equal to the first preset duration, so that the receiving instruction information is used to instruct forwarding from the second root node The multicast traffic received by the node PE discards the multicast traffic received from the first root node PE.
The apparatus according to claim 9, wherein the receiving instruction information is used to indicate that the multicast traffic received from the second root node PE is discarded the multicast traffic received from the first root node PE When, the configuration unit is also used to:

When the receiving unit receives the multicast traffic sent by the first root node PE, it determines a second preset duration, and configures the receiving instruction information so that the receiving instruction information is used to instruct forwarding from the first root node PE. The multicast traffic received by the root node PE discards the multicast traffic received from the second root node PE.
The device according to claim 8, wherein:

The receiving unit is further configured to: receive routing information sent by the first root node PE or the second root node PE; the routing information includes the type indication information; the routing information further includes the following information At least one item: tunnel type, tunnel identifier, and address of the root node PE that sends the routing information;

The device further includes an establishment unit, configured to establish a multicast label forwarding protocol MLDP tunnel with the first root node PE and the second root node PE, respectively, according to the routing information.