Route publishing method and device, storage medium and electronic device

Abstract

Embodiments of the present application provide a routing publishing method and device, a storage medium and an electronic device. The method comprises: publishing, by a first router PE1, an EVPN RT-1 per ES route R1b generated based on a first Ethernet segment identifier ESI1 to a second router PE2, wherein the first Ethernet segment identifier ESI1 comprises at least one of a first use ESI determined according to a third sub-interface, a fourth sub-interface on the first router PE1 and a first condition, and the first use ESI determined by the second router PE2 according to a first sub-interface, a second sub-interface and the first condition; and receiving, by the first router PE1, an EVPN RT-1 per ES route R1a published by the second router PE2 and generated based on the first Ethernet segment identifier ESI1, thereby solving the problem of how to publish a route across nodes between different ES segments and solving the problem of how to publish a route across nodes between different ES segments.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, in particular to a route publishing method and device, a storage medium and an electronic device. BACKGROUND

[0002] EVPN is a kind of Layer 2 network interconnection VPN technology, which can be based on scalable virtual local area network tunnel, multi-protocol label switching or carrier backbone bridging technology. EVPN technology transmits media access control / address resolution protocol / route information between Layer 2 networks through the establishment of multi-protocol border gateway protocol neighbors, and performs Layer 2 or Layer 3 message forwarding through generated address forwarding table entries. That is, the transmission of MAC, ARP, route and other entries does not depend on the data plane, but is completed through the EVPN control plane.

[0003] EVPN MAC is transmitted through RT2 MAC route. CE (Customer Edge, user network edge device) dual-homing in the network is solved through EVPN ESI scheme, and Layer 2 dual-homing ESI (Ethernet segment identifier) can carry ESI information through RT2 MAC route, and the remote PE forms ESI-protected forwarding according to the route, and forms local protection on the dual-homing PE. ESI forwarding utilizes DF election to generate DF and NON-DF, and the anti-loop mechanism of non-DF and DF well avoids the broadcast loop on the user side. If multiple ES segments belonging to different CEs exist on the user side, the CEs can broadcast, and such loop risk can be solved through the Evpn Etree scheme, or the horizontal segmentation scheme can be used to avoid the message loop caused by the mutual conversion of broadcast between multiple ES segments.

[0004] The EVPN route ETI field is used to identify the VLAN ID of the Layer 2 AC port of the EVPN VPLS, and in the unqualify mode, the field is 0, and in the qualify mode, the field is filled with the VLAN ID of the AC port.

[0005] At present, when multiple ES segments belong to the same pair of PEs in EVPN, the ACs belonging to the same ES can realize BUM (Broadcast Unknown-Unicast & Multicast) anti-loop, as shown in Figure 2 Different ESs can realize BUM broadcast anti-loop through Etree leaf attribute. In combination with Figure 1 and Figure 2 , the basic working principle of BUM broadcast anti-loop is as follows:

[0006] PE1, PE2 deploy EPVN VPLS instance, PE2 configures AC11, AC12, AC13 belonging to physical port respectively binding ESI1, ESI2, ESI3. PE1 configures AC21, AC22, AC23 belonging to ESI1, ESI2, ESI3 respectively. PE2 and PE1 form VXLAN tunnel. PE2 and PE1 are elected as DF and non-DF according to routing priority; wherein, OLT1 belongs to ES3, OLT2 belongs to ES4. AC13, AC14, AC23, AC24 deploy Etree leaf attribute, and broadcast non-forwarding between ESI3 and ESI4 is realized through leaf label. AC11 and AC12 deploy horizontal segmentation to ensure local multiple ES mutual conversion of broadcast message on BRAS side. Broadcast intercommunication is needed between OLT and BRAS, and broadcast intercommunication is not needed between OLT and BRAS. Broadcast loop between OLT is solved by Evpn Etree leaf attribute. Since OLT and BRAS need to intercommunicate, BRAS side cannot be configured as leaf attribute. BRAS side can be configured with horizontal segmentation. Horizontal segmentation is only local attribute, and only local conversion is effective.

[0007] As Figure 1 , OLT to BRAS request message forwarding process is as follows:

[0008] PE1 receives broadcast message of OLT from AC23, and forwards to AC21, AC22, and carries anti-loop label through VXLAN tunnel to PE2. AC23, AC24 are leaf attributes, and broadcast traffic does not intercommunicate. PE2 judges according to leaf label that the original AC receiving traffic is leaf attribute, and broadcast message of local leaf AC (AC13, AC14) does not intercommunicate. AC11 and AC12 are default ROOT attributes, and broadcast message is forwarded, so as to realize broadcast anti-loop between OLT, and ensure intercommunication of OLT and BRAS.

[0009] BRAS to OLT broadcast reply message forwarding process is as follows:

[0010] PE1 receives broadcast message of BRAS from AC21, and broadcasts to AC22, AC23, AC24, and PE2. AC22 and AC21 are the same horizontal segmentation attribute A, and broadcast does not forward. A23, A24 forward normally. PE2 receives broadcast message and forwards to AC11, AC12, AC13, AC14. According to broadcast ESI label, it is judged that AC11 belongs to the same ESI1 as AC11, and broadcast message of AC11 is not forwarded. AC12, AC13, AC14 can be forwarded.

[0011] The existing two-layer ESI technology can only solve the broadcast loop prevention between the same ESs. The horizontal segmentation solves the broadcast loop prevention between the local different ESs. The broadcast loop between the different ES segments across nodes cannot be solved. For example, Figure 1 The packet of the BRAS-C is forwarded to the OLT through the BRAS-up1. The broadcast traffic of the BRAS-up1 to the PE1 is transferred from the AC22 to the BRAS-up2, and is further forwarded to the BRAS-up2 from the PE1 to the PE2. The BRAS-up2 further uploads the packet to the BRAS-C, causing the loop of the traffic.

[0012] For the related art, how to solve the problem of cross-node publishing routing between different ES segments has not yet been proposed.

[0013] Therefore, it is necessary to improve the related art to overcome the defects in the related art. SUMMARY

[0014] Embodiments of the present application provide a routing publishing method and device, a storage medium and an electronic device to at least solve the problem of how to solve the cross-node publishing routing between different ES segments.

[0015] According to an aspect of the embodiments of the present application, a route publishing method is provided, comprising: publishing, by a second router PE2, an EVPN RT-1 per ES route R1a generated based on a first Ethernet segment identifier ESI1 to a first router PE1, wherein the first Ethernet segment identifier ESI1 comprises at least one of a first use ESI determined according to a first sub-interface, a second sub-interface and a first condition on the second router PE2, and the first use ESI determined according to a third sub-interface, a fourth sub-interface and the first condition on the first router PE1; receiving, by the second router PE2, an EVPN RT-1 per ES route R1b published by the first router PE1 and generated based on the first Ethernet segment identifier ESI1; wherein the first sub-interface and the second sub-interface are not sub-interfaces of a same parent interface, the third sub-interface and the fourth sub-interface are not sub-interfaces of a same parent interface, an ESI label carried in the EVPN RT-1 per ES route R1b is used to instruct the first router PE1 to forward a broadcast, unknown unicast or multicast BUM packet from the first sub-interface or the second sub-interface, and filtering is performed when an egress of the forwarding is the third sub-interface or the fourth sub-interface, the first use ESI is an ESI used for first filtering, the first filtering is filtering performed on BUM packet forwarding between the first sub-interface facing the third sub-interface or the fourth sub-interface, or filtering performed on BUM packet forwarding between the second sub-interface facing the third sub-interface or the fourth sub-interface, and the first filtering is performed according to the ESI label of the first use ESI.

[0016] In an example embodiment, the parent interfaces of the two sub-interfaces of the second router PE2 or the first router PE1 are respectively bound with different second use ESIs, and the first condition is that, in a case where the two sub-interfaces are bound with a same virtual Ethernet segment identifier vESI, the vESI is determined as the first use ESI corresponding to the two sub-interfaces; wherein the second use ESI is an ESI used for unicast forwarding to any one of the two sub-interfaces.

[0017] In an example embodiment, the first condition is that, in a case where the parent interfaces of the two sub-interfaces of the second router PE2 or the first router PE1 are bound with a same second use ESI, the same second use ESI is determined as the first use ESI corresponding to the two sub-interfaces.

[0018] In an example embodiment, the method further comprises: receiving, by the first router PE1, a packet from a third access interface, broadcasting to the second router PE2 in case that the MAC is not found, and encapsulating the ESI label and EVI label of the first use ESI; finding, by the second router PE2, the EVPN VPLS instance according to the EVI label, and finding the ESI according to the ESI label, which is the same as the first use ESI to which the first access interface and the second access interface in the EVPN VPLS instance belong; discarding the traffic broadcasted to the first access interface and the second access interface on the second router PE2; wherein the first router PE1 receives the traffic of the third access interface, determines the third access interface as the forwarding egress of the corresponding first source address by learning the source address, and generates an RT2 route R2-1 and sends it to the second router PE2; the RT2 route R2-1 carries the ESI ID of the ESI bound by the third access interface and the first ETI field of the third access interface; wherein the second router PE2 receives the RT2 route R2-1, finds the first access interface locally according to the ESID and ETI in the RT2 route R2-1 packet received by the second router PE2, and determines the forwarding egress of the first MAC source address as the ESI and ETI to which the first access interface belongs; wherein the first access interface corresponds to the first sub-interface, the second access interface corresponds to the second sub-interface, the third access interface corresponds to the third sub-interface, and the fourth access interface corresponds to the fourth sub-interface.

[0019] In an example embodiment, the first sub-interface and the third sub-interface satisfy a second condition, and the second sub-interface and the fourth sub-interface satisfy the second condition; the filtering is performed by the ESI label of the EVPN RT-1 per ES route R1a, R1b; the second condition is that two sub-interfaces in a first pair of sub-interfaces are located on different PE nodes and have the same VLAN, and the two sub-interfaces can reach each other without passing through any PE node in between, then it is determined that the two sub-interfaces satisfy the second condition, wherein the first pair of sub-interfaces is the first sub-interface and the third sub-interface, or the first pair of sub-interfaces is the second sub-interface and the fourth sub-interface.

[0020] In an example embodiment, in case that the PE1 performs a second processing, the R1a route indicates the PE1 to perform a first processing; the second processing is that the PE2 performs filtering when the forwarding egress is the first sub-interface or the second sub-interface in forwarding broadcast, unknown unicast or group multicast BUM packets from the third sub-interface or the fourth sub-interface.

[0021] In an example embodiment, the method further comprises: binding the first Ethernet segment identifier ESI1 to a first sub-interface and a second sub-interface on the second router PE2 respectively, and binding the first Ethernet segment identifier ESI1 to a parent interface of the first sub-interface and a parent interface of the second sub-interface respectively; binding the first Ethernet segment identifier ESI1 to a third sub-interface and a fourth sub-interface on the first router PE1 respectively, and binding the first Ethernet segment identifier ESI1 to a parent interface of the third sub-interface and a parent interface of the fourth sub-interface respectively.

[0022] In an example embodiment, the method further comprises: assigning a first interface identifier and a second interface identifier to the parent interface of the first sub-interface and the parent interface of the second sub-interface respectively, and publishing, by the second router PE2, EVPN RT-1per EVI routes R11, R12 based on the first Ethernet segment identifier ESI1 and the first interface identifier and the second interface identifier to the first router PE1; and binding the ESI to a parent interface of a third sub-interface and a parent interface of a fourth sub-interface on the first router PE1 respectively, and assigning the first interface identifier and the second interface identifier to the parent interface of the third sub-interface and the parent interface of the fourth sub-interface respectively, and publishing, by the first router PE1, EVPN RT-1per EVI routes R21, R22 based on the ESI and the interface identifiers to the second router PE2.

[0023] In an example embodiment, the interface identifiers are carried in an Ethernet Tag ID field of the EVPN RT-1per EVI routes; the EVPN RT-1per EVI routes R11, R21 carry an ESI ID I1, a first ETI field, an ESI label and an EVI label, and the EVPN RT-1per EVI routes R12, R22 carry the ESI ID I1, a second ETI field, an ESI label and an EVI label; the EVPN RT-1per EVI routes are used together with RT4 routes for DF election of the first router PE1 and the second router PE2.

[0024] In one example embodiment, in the process of configuring the Ethernet virtual private network virtual private local area network service EVPN VPLS instance for the second router PE2 and the first router PE1, the method further comprises: creating the first sub-interface and the second sub-interface for the first physical port and the second physical port of the second router PE2 respectively, and taking the first sub-interface and the second sub-interface as the first access interface and the second access interface of the EVPN VPLS instance; and creating the third sub-interface and the fourth sub-interface for the third physical port and the fourth physical port of the first router PE1 respectively, and taking the third sub-interface and the fourth sub-interface as the third access interface and the fourth access interface of the EVPN VPLS instance; wherein the virtual private local area network address VLAN ID of the first access interface and the third access interface is the same, and the VLAN ID of the second access interface and the fourth access interface is the same.

[0025] In one example embodiment, the first access interface and the second access interface are configured with the same horizontal division attribute; and the third access interface and the fourth access interface are configured with the same horizontal division attribute.

[0026] In one example embodiment, the method further comprises: generating, by the second router PE2, an RT4 route R4-1 based on the ESI, wherein the RT4 route R4-1 carries the DF election rule and the priority of the second router PE2.

[0027] In one example embodiment, the method further comprises: generating, by the first router PE1, an RT4 route R4-2 based on the ESI; and the RT4 route R4-2 carries the DF election rule and the priority of the first router PE1.

[0028] In one example embodiment, the method further comprises: generating the EVI label carried by the EVPN RT-1 per EVI route based on the EVPN VPLS instance, and generating the ESI label based on the ESI instance; wherein the EVI label is used for locally querying the VPLS forwarding label of the EVPN RT-1 per EVI route, the ESI label is used for the egress PE to determine the ESI to which the ingress AC belongs, and the access interface of the EVPN VPLS instance corresponding to the EVI label, the access interface under the EVPN VPLS instance, and the access interface belonging to the same ESI as the ingress AC; wherein the ingress AC is the AC through which the BUM packet is received by the ingress PE, the ingress PE is the PE receiving the BUM packet from the access interface, and the egress PE is the PE forwarding the BUM packet from the access interface.

[0029] In one example embodiment, the method further comprises: receiving, by the first router PE1, the R11 of the second router PE2 and the RT4 route R4-1, finding the second layer interface bound under the ESI as the third access interface and the fourth access interface according to the ESID I1 of the R11, constructing ESI protection in case that the first ETI field of the R11 and the ETI field of the third access interface locally are identical, deciding the DF priority of the first router PE1 as non-DF according to the comparison result of the DF priority of the RT4 route R4-1 and the local priority, wherein the RT4 route R4-1 carries the DF election rule and priority of the second router PE2, and the R4-1 is the RT4 route received by PE1 and sent by PE2.

[0030] In one example embodiment, the method further comprises: in case that the first router PE1 receives the R12 of the second router PE2 and the RT4 route R4-1, determining the second layer interface bound under the ESI as the third access interface and the fourth access interface according to the ESID I1, constructing ESI protection in case that the second ETI field of the R12 and the ETI field of the fourth access interface locally are identical, and comparing the DF priority of the RT4 route R4-1 with the local priority to decide the DF priority of the first router PE1 as non-DF.

[0031] In one example embodiment, the method further comprises: forwarding the destination MAC of the packet B1 as MAC1 from the fifth access interface to the first router PE1, determining the forwarding egress of MAC1 as the third access interface; forwarding the packet B1 directly from the third access interface to the BRAS-UP1; wherein, when the third access interface has a link fault, switching to the backup ESI for forwarding and encapsulating an EVI label; according to the EVI label, finding the physical address MAC forwarding table corresponding to the MAC1 address under the EVPN VPLS instance by the second router PE2 to determine the corresponding egress as the first access interface.

[0032] In one example embodiment, the method further comprises: on the first router PE1, the third access interface and the fourth access interface have no horizontal segmentation attribute; and in case that the ESI bound by the third access interface and the fourth access interface are identical, deciding not to forward the traffic.

[0033] In one example embodiment, the route R11 and R12 carry the ESID I1 and the first ETI field.

[0034] According to a further aspect of the embodiments of the present application, a route publishing device is further provided, comprising: a first publishing module, configured to publish, by a first router PE1, an EVPN RT-1per ES route R1b generated based on a first Ethernet segment identifier ESI1 to a second router PE2, wherein the first Ethernet segment identifier ESI1 comprises at least one of a first use ESI determined according to a third sub-interface, a fourth sub-interface and a first condition on the first router PE1, and the first use ESI determined by the second router PE2 according to a first sub-interface, a second sub-interface and the first condition; and a second publishing module, configured to receive, by the first router PE1, an EVPN RT-1per ES route R1a published by the second router PE2 and generated based on the first Ethernet segment identifier ESI1; wherein the first sub-interface and the second sub-interface do not belong to a same parent interface, the third sub-interface and the fourth sub-interface do not belong to a same parent interface, the EVPN RT-1per ES route R1a is used to instruct the first router PE1 to perform a first processing, the first processing is to encapsulate an ESI label carried in the R1a route when the PE1 forwards a BUM packet from the third sub-interface or the fourth sub-interface to the PE2, the first use ESI is an ESI used for a first filtering, the first filtering is a filtering on a BUM packet transmission between the first sub-interface and the third sub-interface or the fourth sub-interface, or a filtering on a BUM packet between the second sub-interface and the third sub-interface or the fourth sub-interface, and the first filtering is performed according to an ESI label of the first use ESI.

[0035] According to a further aspect of the embodiments of the present application, a computer readable storage medium is further provided, wherein the computer readable storage medium stores a computer program, and the computer program is configured to execute the route publishing method when running.

[0036] According to a further aspect of the embodiments of the present application, an electronic device is further provided, comprising a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the route publishing method through the computer program.

[0037] By the second router PE2, an EVPN RT-1 per ES route R1a generated based on a first Ethernet segment identifier ESI1 is published to the first router PE1, wherein the first Ethernet segment identifier ESI1 comprises at least one of a first use ESI determined according to a first sub-interface, a second sub-interface and a first condition on the second router PE2, and the first use ESI determined according to a third sub-interface, a fourth sub-interface and the first condition on the first router PE1; by the second router PE2, an EVPN RT-1 per ES route R1b generated based on the first Ethernet segment identifier ESI1 is received, which is published by the first router PE1; wherein the first sub-interface and the second sub-interface are not sub-interfaces of the same parent interface, the third sub-interface and the fourth sub-interface are not sub-interfaces of the same parent interface, an ESI label carried in the EVPN RT-1 per ES route R1b is used to instruct the first router PE1 to forward a broadcast, unknown unicast or multicast BUM packet from the first sub-interface or the second sub-interface, and filtering is performed when an egress of the forwarding is the third sub-interface or the fourth sub-interface, the first use ESI is an ESI used for first filtering, the first filtering is filtering performed on BUM packet forwarding between the first sub-interface facing the third sub-interface or the fourth sub-interface, or filtering performed on BUM packet between the second sub-interface facing the third sub-interface or the fourth sub-interface, and the first filtering is performed according to the ESI label of the first use ESI, thereby solving the problem of how to solve cross-node publishing of a route between different ES segments. BRIEF DESCRIPTION OF DRAWINGS

[0038] The accompanying drawings, which are included to provide a further understanding of the present application, constitute a part of this application and illustrate exemplary embodiments of the present application and the description thereof serve to explain the present application and do not limit the present application in any manner. In the drawings:

[0039] Figure 1 is a schematic diagram of working principle of BUM broadcast loop prevention in the related art (one);

[0040] Figure 2 is a schematic diagram of working principle of BUM broadcast loop prevention in the related art (two);

[0041] Figure 3 is a hardware structure block diagram of a computer terminal of a route publishing method according to an embodiment of the present application;

[0042] Figure 4 is a flowchart of a route publishing method according to an embodiment of the present application;

[0043] Figure 5is a schematic diagram of the working principle of a route publishing method according to an embodiment of the present application;

[0044] Figure 6 is a structural block diagram of a route publishing apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to enable persons skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by persons skilled in the art without creative work should fall within the scope of protection of the present application.

[0046] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily indicate a specific order or a chronological sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to the process, method, product or device.

[0047] The method embodiments provided in the embodiments of the present application can be executed in a computer terminal or similar computing device. Taking a computer terminal as an example, Figure 3 is a hardware structural block diagram of a computer terminal of a route publishing method according to an embodiment of the present application. As shown in Figure 3 , the computer terminal can include one or more (only one is shown in Figure 3 ) processors 302 (the processor 302 can include but is not limited to a microprocessor unit (MPU) or a programmable logic device (PLD)) and a memory 304 for storing data. In an exemplary embodiment, the above-mentioned computer terminal can further include a transmission device 306 for communication function and an input and output device 308. Those skilled in the art can understand that Figure 3 The structure shown is only schematic, which does not limit the structure of the above-mentioned computer terminal. For example, the computer terminal can include more or fewer components than those shown in Figure 3 , or have different structures from those shown inFigure 3 the same functions or Figure 3 different configurations that perform more of the functions shown.

[0048] The memory 304 is used to store computer programs, such as software programs of application software and modules, such as a computer program corresponding to the route distribution method in the embodiments of the present application. The processor 302 performs various functional applications and data processing, i.e., implements the above method, by running the computer program stored in the memory 304. The memory 304 can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 304 can further include a memory remotely arranged with respect to the processor 302, which can be connected to the computer terminal through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0049] The transmission device 306 is used to receive or send data via a network. The specific examples of the above network can include a wireless network provided by a communication provider of the computer terminal. In one example, the transmission device 306 includes a network adapter (NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 306 can be a radio frequency (RF) module, which is used to communicate with the Internet in a wireless manner.

[0050] Figure 4 is a flowchart of a route distribution method according to the embodiments of the present application, as Figure 4 shown, the steps of the route distribution method include:

[0051] In step S402, an EVPN RT-1per ES route R1a generated based on a first Ethernet segment identifier ESI1 is distributed to a first router PE1 through a second router PE2, wherein the first Ethernet segment identifier ESI1 includes at least one of a first use ESI determined according to a first sub-interface, a second sub-interface and a first condition on the second router PE2, and the first use ESI determined according to a third sub-interface, a fourth sub-interface and the first condition on the first router PE1.

[0052] Step S404, receiving, by the second router PE2, the EVPN RT-1per ES route R1b generated based on the first Ethernet segment identifier ESI1 and published by the first router PE1; wherein the first sub-interface and the second sub-interface are not sub-interfaces of the same parent interface, the third sub-interface and the fourth sub-interface are not sub-interfaces of the same parent interface, the ESI label carried in the EVPN RT-1per ES route R1b is used to instruct the first router PE1 to forward broadcast, unknown unicast or multicast BUM packets from the first sub-interface or the second sub-interface, and filtering is performed when the egress of the forwarding is the third sub-interface or the fourth sub-interface, the first use ESI is an ESI used for first filtering, the first filtering is filtering of BUM packet forwarding between the first sub-interface and the third sub-interface or the fourth sub-interface, or filtering of BUM packet forwarding between the second sub-interface and the third sub-interface or the fourth sub-interface, and the first filtering is performed according to the ESI label of the first use ESI.

[0053] The embodiments of the present application publish, by the second router PE2, the EVPN RT-1per ES route R1a generated based on the first Ethernet segment identifier ESI1 to the first router PE1, wherein the first Ethernet segment identifier ESI1 includes at least one of the following: a first use ESI determined according to the first sub-interface, the second sub-interface and a first condition on the second router PE2, and the first use ESI determined according to the third sub-interface, the fourth sub-interface and the first condition on the first router PE1; receiving, by the second router PE2, the EVPN RT-1per ES route R1b generated based on the first Ethernet segment identifier ESI1 and published by the first router PE1; wherein the first sub-interface and the second sub-interface are not sub-interfaces of the same parent interface, the third sub-interface and the fourth sub-interface are not sub-interfaces of the same parent interface, the ESI label carried in the EVPN RT-1per ES route R1b is used to instruct the first router PE1 to forward broadcast, unknown unicast or multicast BUM packets from the first sub-interface or the second sub-interface, and filtering is performed when the egress of the forwarding is the third sub-interface or the fourth sub-interface, the first use ESI is an ESI used for first filtering, the first filtering is filtering of BUM packet forwarding between the first sub-interface and the third sub-interface or the fourth sub-interface, or filtering of BUM packet forwarding between the second sub-interface and the third sub-interface or the fourth sub-interface, and the first filtering is performed according to the ESI label of the first use ESI, solving the problem of how to solve the cross-node publishing of routes between different ES segments.

[0054] In one example embodiment, the parent interface of the two sub-interfaces of the second router PE2 or the first router PE1 respectively binds different second use ESI, and the first condition is that in the case that the parent interface of the two sub-interfaces binds the same virtual Ethernet segment identification vESI, the vESI is determined as the first use ESI corresponding to the two sub-interfaces; wherein the second use ESI is the ESI used for unicast forwarding to any one of the two sub-interfaces.

[0055] In one example embodiment, the first condition is that in the case that the parent interface of the two sub-interfaces of the second router PE2 or the first router PE1 binds the same second use ESI, the same second use ESI is determined as the first use ESI corresponding to the two sub-interfaces.

[0056] In one example embodiment, a technical solution is also proposed, and the specific steps include: receiving a packet from a third access interface by the first router PE1, broadcasting to the second router PE2 in the case that the MAC is not found, and encapsulating the ESI label and EVI label of the first use ESI; finding the EVPN VPLS instance according to the EVI label by the second router PE2, and finding that the ESI according to the ESI label is the same as the first use ESI to which the first access interface and the second access interface in the EVPN VPLS instance belong; discarding the flow broadcasted to the first access interface and the second access interface on the second router PE2; wherein the first router PE1 receives the flow of the third access interface, determines the third access interface as the forwarding egress of the corresponding first source address MAC1 by learning the source address, generates an RT2 route R2-1 and sends it to the second router PE2; the RT2 route R2-1 carries the ESID of the ESI bound by the third access interface and the first ETI field of the third access interface; wherein the second router PE2 receives the RT2 route R2-1, finds the local first access interface according to the ESID and ETI in the RT2 route R2-1 packet received by the second router PE2, and determines the forwarding egress of the first MAC source address as the ESI and ETI to which the first access interface belongs; wherein the first access interface corresponds to the first sub-interface, the second access interface corresponds to the second sub-interface, the third access interface corresponds to the third sub-interface, and the fourth access interface corresponds to the fourth sub-interface.

[0057] In an example embodiment, the first sub-interface and the third sub-interface satisfy a second condition, and the second sub-interface and the fourth sub-interface satisfy the second condition; the filtering is filtering by the EVPN RT-1perES route R1a, R1b of the ESI label; the second condition is that when two sub-interfaces are located on different PE nodes and the VLANs of the two sub-interfaces are the same, and the two sub-interfaces can reach each other without passing through any PE node in the middle, it is determined that the two sub-interfaces satisfy the second condition. Wherein, the first pair of sub-interfaces is the first sub-interface and the third sub-interface, or the first pair of sub-interfaces is the second sub-interface and the fourth sub-interface.

[0058] In an example embodiment, in the case that the PE2 performs a second processing, the R1a route indicates the PE2 to perform a first processing; the second processing is that when forwarding a broadcast, unknown unicast or multicast BUM packet from the third sub-interface or the fourth sub-interface, the PE2 performs filtering when the egress of the forwarding is the first sub-interface or the second sub-interface.

[0059] In an example embodiment, a technical solution is also proposed, specifically: binding the first Ethernet segment identifier ESI1 to the parent interface of the first sub-interface and the parent interface of the second sub-interface on the second router PE2 respectively; and binding the first Ethernet segment identifier ESI1 to the parent interface of the third sub-interface and the parent interface of the fourth sub-interface on the first router PE1 respectively.

[0060] In an example embodiment, a technical solution is also proposed, specifically: assigning the first interface identifier and the second interface identifier to the parent interface of the first sub-interface and the parent interface of the second sub-interface respectively, and publishing, by the second router PE2, the EVPN RT-1per EVI route R11, R12 generated based on the first Ethernet segment identifier ESI1 and the first interface identifier and the second interface identifier to the first router PE1; and binding the ESI to the parent interface of the third sub-interface and the parent interface of the fourth sub-interface on the first router PE1 respectively, and assigning the first interface identifier and the second interface identifier to the parent interface of the third sub-interface and the parent interface of the fourth sub-interface respectively, and publishing, by the first router PE1, the EVPN RT-1per EVI route R21, R22 generated based on the ESI and the interface identifier to the second router PE2.

[0061] In an example embodiment, the interface is carried in an Ethernet Tag ID field of the EVPN RT-1 per EVI route; the EVPN RT-1 per EVI routes R11, R21 carry an ESID I1, a first ETI field, an ESI label and an EVI label, and the EVPN RT-1 per EVI routes R12, R22 carry the ESID I1, a second ETI field, an ESI label and an EVI label; the EVPN RT-1 per EVI routes are used together with the RT4 routes for DF election of the first router PE1 and the second router PE2.

[0062] In an example embodiment, in a process of configuring an Ethernet Virtual Private Network (EVPN) Virtual Private Local Area Network (VPLS) instance for the second router PE2 and the first router PE1, the method further comprises: creating the first sub-interface and the second sub-interface for a first physical port and a second physical port of the second router PE2 respectively, and taking the first sub-interface and the second sub-interface as a first access interface and a second access interface of the EVPN VPLS instance; and creating the third sub-interface and the fourth sub-interface for a third physical port and a fourth physical port of the first router PE1 respectively, and taking the third sub-interface and the fourth sub-interface as a third access interface and a fourth access interface of the EVPN VPLS instance; wherein a Virtual Private Local Area Network (VLAN) ID of the first access interface and the third access interface is the same, and a VLAN ID of the second access interface and the fourth access interface is the same.

[0063] In an example embodiment, the first access interface and the second access interface are configured with a same horizontal split attribute; and the third access interface and the fourth access interface are configured with a same horizontal split attribute.

[0064] In an example embodiment, the second router PE2 can further generate an RT4 route R4-1 based on the ESI, wherein the RT4 route R4-1 carries a DF election rule and a priority of the second router PE2.

[0065] In an example embodiment, the first router PE1 can further generate an RT4 route R4-2 based on the ESI; and the RT4 route R4-2 carries a DF election rule and a priority of the first router PE1.

[0066] In one example embodiment, a technical solution is also proposed, and the specific steps include: generating an EVI label carried by the EVPN RT-1 per EVI route based on the EVPNVPLS instance, and generating the ESI label based on the ESI instance; wherein the EVI label is used for locally querying a VPLS forwarding label of the EVPN RT-1 per EVI route, the ESI label is used for an exit PE to determine an ESI to which an entry AC belongs, and an access interface of an EVPN VPLS instance corresponding to the EVI label, and the access interface under the EVPN VPLS instance and belonging to the same ESI as the entry AC are subjected to BUM filtering; wherein the entry AC is an AC through which the BUM packet is received by the entry PE, the entry PE is a PE receiving the BUM packet from the access interface, and the exit PE is a PE forwarding the BUM packet from the access interface.

[0067] In one example embodiment, a technical solution is also proposed, and the specific steps include: generating an EVI label carried by the EVPN RT-1 per EVI route based on the EVPNVPLS instance, and generating the ESI label based on the ESI instance; wherein the EVI label is used for locally querying a VPLS forwarding label of the EVPN RT-1 per EVI route, the ESI label is used for an exit PE to determine an ESI to which an entry AC belongs, and an access interface of an EVPN VPLS instance corresponding to the EVI label, and the access interface under the EVPN VPLS instance and belonging to the same ESI as the entry AC are subjected to BUM filtering; wherein the entry AC is an AC through which the BUM packet is received by the entry PE, the entry PE is a PE receiving the BUM packet from the access interface, and the exit PE is a PE forwarding the BUM packet from the access interface.

[0068] In one example embodiment, a technical solution is also proposed, and the specific steps include: generating an EVI label carried by the EVPN RT-1 per EVI route based on the EVPNVPLS instance, and generating the ESI label based on the ESI instance; wherein the EVI label is used for locally querying a VPLS forwarding label of the EVPN RT-1 per EVI route, the ESI label is used for an exit PE to determine an ESI to which an entry AC belongs, and an access interface of an EVPN VPLS instance corresponding to the EVI label, and the access interface under the EVPN VPLS instance and belonging to the same ESI as the entry AC are subjected to BUM filtering; wherein the entry AC is an AC through which the BUM packet is received by the entry PE, the entry PE is a PE receiving the BUM packet from the access interface, and the exit PE is a PE forwarding the BUM packet from the access interface.

[0069] In one example embodiment, a technical solution is also provided, and the specific steps include: forwarding the destination MAC of the packet B1 as MAC1, from the fifth access interface to the first router PE1, determining the forwarding outlet of MAC1 as the third access interface; forwarding the forwarding packet B1 directly from the third access interface to the BRAS-UP1; wherein when the third access interface has a link fault, switching to the backup ESI for forwarding, and encapsulating an EVI label; determining the corresponding outlet as the first access interface by searching the physical address MAC forwarding table corresponding to the MAC1 address under the EVPN VPLS instance according to the EVI label through the second router PE2.

[0070] In one example embodiment, a technical solution is also provided, and the specific steps include: on the first router PE1, the third access interface and the fourth access interface do not have horizontal segmentation attributes; in the case of determining that the ESI bound by the third access interface and the fourth access interface is the same, determining not to forward the traffic.

[0071] In one example embodiment, the route R11, R12 carries the ESID I1, and a first ETI field.

[0072] In one example embodiment, the method further includes: binding the first Ethernet segment identifier ESI1 to the first sub-interface and the second sub-interface on the second router PE2 respectively, and binding the first Ethernet segment identifier ESI1 to the parent interface of the first sub-interface and the parent interface of the second sub-interface respectively; binding the first Ethernet segment identifier ESI1 to the third sub-interface and the fourth sub-interface on the first router PE1 respectively, and binding the first Ethernet segment identifier ESI1 to the parent interface of the third sub-interface and the parent interface of the fourth sub-interface respectively.

[0073] In one example embodiment, in the process of configuring the Ethernet virtual private network virtual private local area network service EVPN VPLS instance for the second router PE2 and the first router PE1, the method further comprises: creating the first sub-interface and the second sub-interface for the first physical port and the second physical port of the second router PE2 respectively, and taking the first sub-interface and the second sub-interface as the first access interface and the second access interface of the EVPN VPLS instance; and creating the third sub-interface and the fourth sub-interface for the third physical port and the fourth physical port of the first router PE1 respectively, and taking the third sub-interface and the fourth sub-interface as the third access interface and the fourth access interface of the EVPN VPLS instance; wherein the virtual private local area network address VLAN ID of the first access interface and the third access interface is the same, and the VLAN ID of the second access interface and the fourth access interface is the same.

[0074] In one example embodiment, the method further comprises: generating, by the second router PE2, an RT4 route R4-1 based on the ESI, wherein the RT4 route R4-1 carries the DF election rule and the priority of the second router PE2.

[0075] In one example embodiment, the method further comprises: generating, by the first router PE1, an RT4 route R4-2 based on the ESI; the RT4 route R4-2 carries the DF election rule and the priority of the first router PE1.

[0076] Next, the route publishing method is further described in combination with the following embodiments.

[0077] In one embodiment, in combination with Figure 5 The route publishing method is described, the same ESI is configured for multiple interfaces, so that the multiple interfaces belong to the same ES instance; the ESI binding of each ES is mapped by using the ETI field of the EVPN route itself, wherein the ETI field is composed of the VLAN id of the ES interface identification ES-INT and the AC port, so as to guarantee the ESI protection between each independent ES; the single ES protection forwarding is realized at the same time, and the BUM loop prevention between the same ESI is guaranteed.

[0078] The ETI field of the EVPN route is 4 bytes in total, the first byte is used to represent the physical port bound by the ES, and the last three bytes are used to represent the AC port VLAN id (AC-VLAN) bound by the layer 2 instance; the ETI identification is (ES-INT: AC-VLAN); wherein when the AC is a physical port, the AC-VLAN is 0, and the ETI is (ES-INT: 0).

[0079] The physical ports (INT11, INT12, INT13, INT14) to which the four AC ports (AC11, AC12, AC21, AC22) of PE2 and PE1 belong are bound to the same ESI, for example, the ESI1 has an ESID of 10 bytes (00.11.22.33.44.55.66.77.88.99), and the ES-INT of INT11 and INT21 is 1, and the ES-INT of INT12 and INT22 is 2.

[0080] PE2 generates the RT1 route R11 for the AC11 of the Layer 2 port, and R11 carries the ESID of ESI1 and the ETI (ES-INT:AC-VLAN) corresponding to AC11; PE1 receives R11, compares the ESID I1 of R11 with the ETI of the local ESI1, and if they are the same, forms an ESI protection forwarding table with the corresponding ETI (ES-INT:AC-VLAN).

[0081] As shown in Figure 5 , PE2 and PE1 perform DF election based on the ES to generate RT4 routes, PE2 is the DF, and PE1 is the non-DF; PE2 generates the RT1 routes R11 and R12 based on ESI1 and the AC11 and AC12 of the vpls instance; and PE1 generates the RT1 routes R21 and R22 based on ESI1 and the AC21 and AC22 of the vpls instance.

[0082] PE2 receives the R21 and R22 routes, finds AC11 according to the ESID and ETI of the R21 route, forms the ESI protection forwarding of AC11, the primary is AC11, and the backup next hop is PE1; finds AC12 according to the ESID and ETI of the R22 route, forms the ESI protection forwarding of AC12, the primary is AC12, and the backup next hop is PE1.

[0083] PE1 receives the R11 and R12 routes, finds AC21 according to the ESID and ETI of the R11 route, forms the ESI protection forwarding of AC21, the primary is AC21, and the backup next hop is PE2; finds AC12 according to the ESID and ETI of the R12 route, forms the ESI protection forwarding of AC22, the primary is AC22, and the backup next hop is PE2.

[0084] The process of unicast forwarding and the process of broadcast forwarding of PE1 receiving the Layer 2 packet from AC23 for the traffic from OLT to BRAS-C are as follows:

[0085] Unicast: PE1 finds MAC hit export is AC21, AC21 corresponds to form ESI1 protection forwarding, backup next hop is PE1; directly from AC21 forwarding to BRAS-up1; when AC21 interface failure, unicast message from ESI backup forwarding to PE1, PE1 finds MAC export is AC11 and forwards the message from AC11 to BRAS-up1.

[0086] Broadcast: PE1 finds no MAC hit, broadcast forwarding to AC21, AC22, PE2; among which forwarding to PE2 with forwarding ESI label or leaf label; PE2 is DF role, forwarding the broadcast traffic to AC11, AC12, AC13, AC14; AC13 and AC14 are leaf attributes, judging from the leaf label of the broadcast message that the same is leaf broadcast traffic and discarding; AC11, AC12 normally broadcast.

[0087] BRAS to OLT traffic, PE1 receives two-layer message from AC21, unicast MAC forwarding, broadcast forwarding as follows:

[0088] PE1 finds no MAC hit, broadcast forwarding to AC22, AC23, AC24, PE2; among which forwarding to PE2 with forwarding ESI label or leaf label; PE2 is DF role, PE2 receives the message and finds no MAC hit, forwarding to AC11, AC12, AC13, AC14; finding local home ESI bound interface as INT1 and INT2 according to the ESI label in the message, sub-interfaces of home INT1 and INT2 as two-layer ports AC11 and AC12 discarding broadcast traffic carrying ESI label; the traffic will not be forwarded to BRAS; AC13 and AC14 normally broadcast; AC22 and AC21 have the same horizontal segmentation attribute and do not forward; here, the horizontal segmentation attribute can not be configured, judging that AC22 and AC21 belong to ESI1 and broadcast is not forwarded.

[0089] In an optional exemplary embodiment, the routing publishing method of the application can be realized by ETI mapping ESI to solve BUM loop among multiple ESIs, wherein the source and destination MAC for two-layer interworking between OLT and BRAS is (OLT: 0000.AAAA.11111, BRAS: 0000.BBBB.2222), including:

[0090] Step S101: PE2 and PE1 configure an EVPN VPLS instance, and PE2 creates sub-interfaces INT1.11 (VLAN ID 100) and INT2.11 (VLAN ID 200) as AC11 and AC12 of the VPLS instance respectively, and PE1 creates sub-interfaces INT1.21 (VLAN ID 100) and INT2.22 (VLAN ID 200) as AC21 and AC22 of the VPLS instance respectively.

[0091] In the embodiment, the VLAN IDs of AC11 and AC21 are the same, and the VLAN IDs of AC12 and AC22 are the same. The VLAN IDs of AC11 / AC21 and AC12 / AC22 can be the same or different. In the embodiment, the VLAN IDs of AC11 / AC21 and AC12 / AC22 are different for the sake of convenience.

[0092] Step S102: INT3 on PE2 is configured as AC13 of the VPLS instance, and INT3 on PE1 is configured as AC23 of the VPLS instance. The physical ports to which AC13 and AC23 belong are bound to ESI3.

[0093] Step S103: INT21 on PE1 is bound to ESI1 (00.11.22.33.44.55.66.77.88.99) and is specified as ES-INT 1, and INT22 on PE1 is bound to ESI1 and is specified as ES-INT 2. PE1 generates an EVPN RT4 route based on ESI1 and sends the route to PE2.

[0094] Step S104: INT11 on PE2 is bound to ESI1 (00.11.22.33.44.55.66.77.88.99) and is specified as ES-INT 1, and INT12 on PE2 is bound to ESI1 and is specified as ES-INT 2. PE2 generates an EVPN RT4 route based on ESI1 and sends the route to PE1.

[0095] Step S105: AC11 and AC12 are configured with the same horizontal split attribute B, and AC21 and AC22 are configured with the same horizontal split attribute B.

[0096] Step S106: PE2 generates RT1 route R11, R12 based on ESI1 and AC11, AC12 of vpls instance respectively. RT4 route R4-1 is generated based on ESI1. R11 route carries ESID I1 (00.11.22.33.44.55.66.77.88.99), and ETI (1:100), and carries ESI and EVI label. R12 route carries ESID I1 (00.11.22.33.44.55.66.77.88.99), and ETI (2:200), and carries ESI and EVI label. R4-1 carries DF election rule and priority of PE2.

[0097] Step S107: PE1 generates RT1 route R21, R22 based on ESI1 and AC21, AC22 of vpls instance. RT4 route R4-2 is generated based on ESI1. R21 route carries ESID I1 (00.11.22.33.44.55.66.77.88.99), and ETI (1:100), and carries ESI and EVI label. R22 route carries ESID I1 (00.11.22.33.44.55.66.77.88.99), and ETI (2:200), and carries ESI and EVI label. R4-2 carries DF election rule and priority of PE1.

[0098] Wherein, EVI label of RT1 route in step S106 and step S107 is generated based on vpls instance, and ESI label is generated based on ESI instance. VPLS forwarding label is inquired according to EVI label of received message, and ESI instance and AC port to which the ESI label belongs are judged according to ESI label.

[0099] Step S108: PE1 receives RT1 route R11 and R4-1 of PE2, finds AC21 and AC22 bound to ESI under ESID I1 according to R11, judges that ETI (1:100) of R11 route and ETI (1:100) of local AC21 are same, forms ESI protection, AC21 is master, ESI forwarding is backup, next hop is PE2. According to DF priority of route R4-1 and local priority comparison, it is decided that PE1 is non-DF.

[0100] Step S109: PE1 receives the RT1 route R12 and the route R4-2 of PE2, finds the bound two-layer interfaces of the ESI under the ESID II as AC21 and AC22 according to the ESID II, judges that the ETI (2:200) of the R12 route and the ETI (2:200) of the local AC22 are the same, forms ESI protection, the master is AC22, the backup is ESI forwarding, and the next hop is PE2. According to the comparison of the DF priority of the route R4-2 and the local priority, it is decided that PE2 is the DF.

[0101] Step S110: BRAS sends a packet (the source is MAC1:0000.BBBB.2222 and the destination is MAC2:0000.AAAA.1111) from AC21 to PE1, and PE1 is non-DF. PE1 searches the MAC and broadcasts the forwarding, and the traffic is forwarded to AC22, AC23, AC24 and PE2. When the broadcast is given to PE2, the ESI label and EVI are carried, PE2 finds the VPLS instance according to the EVI label, and the broadcast is forwarded to AC11, AC12, AC13 and AC14. Further, according to the ESI label, the corresponding AC ports of the VPLS are found as AC11 and AC12 belonging to the same ESI1. The traffic broadcast to AC11 and AC12 on PE2 is discarded. AC13 and AC14 are normally forwarded.

[0102] Among them, on PE1, AC22 and AC21 belong to the same horizontal division attribute B, and the broadcast traffic is discarded. AC23 and AC24 are normally broadcasted and forwarded.

[0103] Among them, PE1 receives the traffic of AC21, learns MAC1, generates the corresponding MAC1 forwarding egress as AC21, and generates the RT2 route R2-1 through PE2. The route R2-1 carries the ESI1 ESID (00.11.22.33.44.55.66.77.88.99) of the ESI1 bound by AC21 and the ETI (1:100) of AC21.

[0104] Among them, PE2 receives the R2-1 route, finds the local AC11 according to the ESID and ETI in the route message, and generates the forwarding egress of MAC1 as AC11.

[0105] Step S111: BRAS sends a unicast packet to PE1, and searches the MAC forwarding.

[0106] Step S112: OLT sends a packet (the source is MAC2:0000.AAAA.1111 and the destination is MAC1:0000.BBBB.2222) from AC23 to PE1, searches the MAC1 forwarding egress as AC21, and the packet is directly forwarded from AC21 to BRAS-UP1.

[0107] When the AC21 has a link fault, switching to ESI backup forwarding and encapsulating the EVI label. The PE2 looks up the MAC forwarding table corresponding to the MAC1 according to the EVI label under the VPLS instance, and the corresponding export is the AC11. Forwarding from the AC11 to the BRAS-UP1.

[0108] In an example embodiment, in combination with Figure 1 With Figure 5 , referring to the steps S101 to S112 in the above embodiment, a routing distribution method is provided, specifically, referring to the steps S101 to S104 in the above embodiment as steps S201 to S204, which will not be repeated here.

[0109] In this embodiment, no horizontal segmentation attribute is deployed, referring to the steps S105 to S106 in the above embodiment as steps S205 to S206, and referring to the steps S111 to S112 in the above embodiment as steps S211 to S212 of this embodiment.

[0110] In this embodiment, the step S210 includes: on the PE1, the AC22 and the AC21 have no horizontal segmentation attribute, and according to the fact that the ESI bound by the AC22 and the AC21 is the same as the ESI1, it is determined not to forward.

[0111] The above embodiments are all AC ports under a VPLS instance belonging to different ESI, in an example embodiment, a routing distribution method capable of solving the broadcast loop problem of multiple sub-interfaces of a physical port as AC ports under a VPLS instance can also be proposed. This embodiment can generate different ETIs according to different VLAN ids of the sub-interfaces, and combining an ESI and an ETI can be mapped to different AC sub-interfaces under the same ESI.

[0112] Compared with embodiment 1, the difference between this embodiment and embodiment 1 is that the AC11 and the AC12 belong to the same physical port, and the AC21 and the AC22 belong to the same physical port. The specific steps of this embodiment are as follows:

[0113] Step S301: the AC12 of the PE2 belongs to the physical port INT1, the AC22 of the PE1 belongs to the physical port INT1, and the other steps S101 are the same;

[0114] Step S302: the step S102 is the same.

[0115] Step S303: the step S103 is the same.

[0116] Step S304: the step S104 is the same.

[0117] Step S305: the step S105 is the same.

[0118] Step S306: R12 routes carrying ESID I1 (00.11.22.33.44.55.66.77.88.99), and ETI (1:200); other steps are the same as S106.

[0119] Step S307: R22 routes carrying ESID I1 (00.11.22.33.44.55.66.77.88.99), and ETI (1:200); other steps are the same as S107.

[0120] Step S309: PE1 receives the RT1 route R12 and route R4-2 of PE2, finds the bound layer 2 interfaces of AC21 and AC22 according to the ESID I1, judges that the ETI (1:200) of R12 route and the ETI (1:200) of local AC22 are the same, forms ESI protection, the master is AC22, the backup is ESI forwarding, the next hop is PE2; compares the DF priority of route R4-2 and the local priority, decides that PE2 is the DF.

[0121] Those skilled in the art can clearly understand that the method according to the above-mentioned embodiments can be realized by means of software and necessary general hardware platforms, of course, can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a plurality of instructions for making a terminal device (which can be a mobile phone, computer, server, or network device, etc.) execute the method of each embodiment of the present application.

[0122] In the present embodiment, a route publishing device is also provided, which is used to implement the above-mentioned embodiments and preferred embodiments, and will not be described again. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, hardware, or a combination of software and hardware is also possible and is contemplated.

[0123] Figure 6 is a structural block diagram of the route publishing device according to the embodiments of the present application. As shown in Figure 6 , the route publishing device includes:

[0124] The first publishing module 62 is configured to publish, by the first router PE1, an EVPN RT-1 per ES route R1b generated based on a first Ethernet segment identifier ESI1 to the second router PE2, wherein the first Ethernet segment identifier ESI1 comprises at least one of a first use ESI determined according to a third sub-interface, a fourth sub-interface on the first router PE1 and a first condition, and the first use ESI determined according to a first sub-interface, a second sub-interface on the second router PE2 and the first condition.

[0125] The second publishing module 64 is configured to receive, by the first router PE1, an EVPN RT-1 per ES route R1a published by the second router PE2 and generated based on the first Ethernet segment identifier ESI1, wherein the first sub-interface and the second sub-interface do not belong to the same parent interface, the third sub-interface and the fourth sub-interface do not belong to the same parent interface, the EVPN RT-1 per ES route R1a is used to instruct the first router PE1 to perform a first processing, the first processing is that when the PE1 forwards a BUM packet from the third sub-interface or the fourth sub-interface to the PE2, an ESI label carried in the R1a route is encapsulated, the first use ESI is an ESI used for first filtering, the first filtering is filtering of BUM packet forwarding between the first sub-interface and the third sub-interface or the fourth sub-interface, or filtering of BUM packet forwarding between the second sub-interface and the third sub-interface or the fourth sub-interface, and the first filtering is performed according to an ESI label of the first use ESI.

[0126] The device is used for publishing, by the first router PE1, an EVPN RT-1 per ES route R1b generated based on a first Ethernet segment identifier ESI1 to a second router PE2, wherein the first Ethernet segment identifier ESI1 comprises at least one of a first use ESI determined according to a third sub-interface, a fourth sub-interface on the first router PE1 and a first condition, and the first use ESI determined according to a first sub-interface, a second sub-interface on the second router PE2 and the first condition; receiving, by the first router PE1, an EVPN RT-1 per ES route R1a published by the second router PE2 and generated based on the first Ethernet segment identifier ESI1; wherein the first sub-interface and the second sub-interface do not belong to a same parent interface, and the third sub-interface and the fourth sub-interface do not belong to a same parent interface, and the EVPN RT-1 per ES route R1a is used for instructing the first router PE1 to perform a first processing, and the first processing is encapsulating an ESI label carried in the R1a route when the PE1 forwards a BUM packet from the third sub-interface or the fourth sub-interface to the PE2; the first use ESI is an ESI used for first filtering, and the first filtering is filtering of BUM packet forwarding between the first sub-interface and the third sub-interface or the fourth sub-interface, or filtering of BUM packet forwarding between the second sub-interface and the third sub-interface or the fourth sub-interface; and the first filtering is performed according to an ESI label of the first use ESI, thereby solving the problem of how to solve cross-node publishing of a route between different ES segments.

[0127] In an example embodiment, a parent interface of two sub-interfaces of the second router PE2 or the first router PE1 respectively binds different second use ESIs, and the first condition is that, in a case where the two sub-interfaces bind a same virtual Ethernet segment identifier vESI, the vESI is determined as the first use ESI corresponding to the two sub-interfaces; wherein the second use ESI is an ESI used for unicast forwarding to any one of the two sub-interfaces.

[0128] In an example embodiment, the first condition is that, in a case where a parent interface of two sub-interfaces of the second router PE2 or the first router PE1 binds a same second use ESI, the same second use ESI is determined as the first use ESI corresponding to the two sub-interfaces.

[0129] In one example embodiment, the route publishing device further comprises a label broadcasting module, configured to receive a packet from the third access interface by the first router PE1, broadcast to the second router PE2 in case that the MAC is not found, and encapsulate the ESI label and EVI label of the first use ESI; find the EVPN VPLS instance according to the EVI label by the second router PE2, and find the ESI according to the ESI label, which is the same as the first use ESI to which the first access interface and the second access interface in the EVPN VPLS instance belong; discard the traffic broadcasted to the first access interface and the second access interface by the second router PE2; wherein the first router PE1 receives the traffic of the third access interface, determines the third access interface as the forwarding egress of the source address of the first source address learned by the source address, and generates the RT2 route R2-1 and sends it to the second router PE2; the RT2 route R2-1 carries the ESI D of the ESI bound by the third access interface and the first ETI field of the third access interface; wherein the second router PE2 receives the RT2 route R2-1, finds the first access interface locally according to the ESID and ETI in the RT2 route R2-1 received by the second router PE2, and determines the forwarding egress of the first MAC source address as the ESI and ETI to which the first access interface belongs; wherein the first access interface corresponds to the first sub-interface, the second access interface corresponds to the second sub-interface, the third access interface corresponds to the third sub-interface, and the fourth access interface corresponds to the fourth sub-interface.

[0130] In one example embodiment, the first sub-interface and the third sub-interface satisfy a second condition, and the second sub-interface and the fourth sub-interface satisfy the second condition; the filtering is performed by the EVPN RT-1 per ES route R1a, R1b ESI label; the second condition is that two sub-interfaces in a first pair of sub-interfaces are located on different PE nodes and have the same VLAN, and the two sub-interfaces can reach each other without passing through any PE node in between, then it is determined that the two sub-interfaces satisfy the second condition, wherein the first pair of sub-interfaces is the first sub-interface and the third sub-interface, or the first pair of sub-interfaces is the second sub-interface and the fourth sub-interface.

[0131] In an example embodiment, the route publishing device further comprises an indication processing module, configured to instruct the PE1 to perform a first processing via the R1a route in a case that the PE2 performs a second processing; the second processing is that the PE2 performs filtering when a forwarding egress is the first sub-interface or the second sub-interface in forwarding a broadcast, unknown unicast or multicast (BUM) packet from the third sub-interface or the fourth sub-interface.

[0132] In an example embodiment, the route publishing device further comprises an interface binding module, configured to bind the first Ethernet segment identifier (ESI) to a first sub-interface and a second sub-interface on the second router (PE2) respectively, and bind the first Ethernet segment identifier (ESI) to a parent interface of the first sub-interface and a parent interface of the second sub-interface respectively; and bind the first Ethernet segment identifier (ESI) to a third sub-interface and a fourth sub-interface on the first router (PE1) respectively, and bind the first Ethernet segment identifier (ESI) to a parent interface of the third sub-interface and a parent interface of the fourth sub-interface respectively.

[0133] In an example embodiment, the route publishing device further comprises an identifier assigning module, configured to assign a first interface identifier and a second interface identifier to the parent interface of the first sub-interface and the parent interface of the second sub-interface respectively, and publish, by the second router (PE2), an EVPN RT-1per EVI route R11, R12 generated based on the first Ethernet segment identifier (ESI) and the first interface identifier and the second interface identifier to the first router (PE1); and bind the first interface identifier and the second interface identifier to the parent interface of the third sub-interface and the parent interface of the fourth sub-interface on the first router (PE1) respectively, and publish, by the first router (PE1), an EVPN RT-1per EVI route R21, R22 generated based on the first Ethernet segment identifier (ESI) and the interface identifier to the second router (PE2).

[0134] In an example embodiment, the interface identifier is carried in an Ethernet Tag ID field of the EVPN RT-1per EVI route; the EVPN RT-1per EVI route R11, R21 carries an ESI ID I1, a first ETI field, an ESI label and an EVI label, and the EVPN RT-1per EVI route R12, R22 carries the ESI ID I1, a second ETI field, an ESI label and an EVI label; the EVPN RT-1per EVI route and an RT4 route are used for DF election of the first router (PE1) and the second router (PE2) together.

[0135] In an example embodiment, the above routing distribution apparatus further comprises an interface creation module configured to create the first sub-interface and the second sub-interface for the first physical interface and the second physical interface of the second router PE2 respectively, and to set the first sub-interface and the second sub-interface as the first access interface and the second access interface of the EVPN VPLS instance; and to create the third sub-interface and the fourth sub-interface for the third physical interface and the fourth physical interface of the first router PE1 respectively, and to set the third sub-interface and the fourth sub-interface as the third access interface and the fourth access interface of the EVPN VPLS instance; wherein the virtual private local area network address (VLAN ID) of the first access interface and the third access interface is the same, and the VLAN ID of the second access interface and the fourth access interface is the same.

[0136] In an example embodiment, the first access interface and the second access interface are configured with the same horizontal split attribute; and the third access interface and the fourth access interface are configured with the same horizontal split attribute.

[0137] In an example embodiment, the second router PE2 can further generate an RT4 route R4-1 based on the ESI, wherein the RT4 route R4-1 carries the DF election rule and the priority of the second router PE2.

[0138] In an example embodiment, the first router PE1 can further generate an RT4 route R4-2 based on the ESI; and the RT4 route R4-2 carries the DF election rule and the priority of the first router PE1.

[0139] In an example embodiment, the above routing distribution apparatus further comprises a label generation module configured to generate an EVI label carried by the EVPN RT-1 per EVI route based on the EVPN VPLS instance, and to generate an ESI label based on the ESI instance; wherein the EVI label is used for locally querying the VPLS forwarding label of the EVPN RT-1 per EVI route, the ESI label is used for an egress PE to determine the access interface of the EVPN VPLS instance to which an ingress AC belongs, and the EVI label is used for BUM filtering on the access interfaces of the EVPN VPLS instance and belonging to the same ESI as the ingress AC; wherein the ingress AC is an AC through which the BUM packet is received by an ingress PE, the ingress PE is a PE receiving the BUM packet from an access interface, and the egress PE is a PE forwarding the BUM packet from an access interface.

[0140] In an example embodiment, the route publishing device further comprises a first constructing module configured to find the second access interface and the third access interface as the layer 2 interfaces under the ESI according to the ESID I1 of the R11, and construct the ESI protection in the case that the first ETI field of the R11 is determined to be the same as the ETI field of the third access interface locally, and determine the DF priority of the first router PE1 as non-DF according to the comparison result of the DF priority of the RT4 route R4-1 and the local priority, wherein the RT4 route R4-1 carries the DF election rule and priority of the second router PE2, and the R4-1 is the RT4 route sent by PE2 and received by PE1.

[0141] In an example embodiment, the route publishing device further comprises a second constructing module configured to find the second access interface and the third access interface as the layer 2 interfaces under the ESI according to the ESID I1, and construct the ESI protection in the case that the second ETI field of the R12 is determined to be the same as the ETI field of the fourth access interface locally, and determine the DF priority of the first router PE1 as non-DF according to the comparison of the DF priority of the RT4 route R4-1 and the local priority, wherein the RT4 route R4-1 carries the DF election rule and priority of the second router PE2, and the R4-1 is the RT4 route sent by PE2 and received by PE1.

[0142] In an example embodiment, the route publishing device further comprises a forwarding module configured to forward the destination MAC of the packet B1 as MAC1, and determine the third access interface as the forwarding egress of MAC1 from the fifth access interface to the first router PE1, and forward the packet B1 directly from the third access interface to the BRAS-UP1; wherein when the third access interface has a link fault, the third access interface is switched to the backup ESI for forwarding, and an EVI label is encapsulated; and the second router PE2 finds the physical address MAC forwarding table corresponding to MAC1 according to the EVI label to the EVPN VPLS instance, and determines the corresponding egress as the first access interface.

[0143] In an example embodiment, the route publishing device further comprises a determining module configured to determine that the third access interface and the fourth access interface have no horizontal division attribute on the first router PE1, and determine not to forward the traffic in the case that the ESI bound by the third access interface and the fourth access interface is determined to be the same.

[0144] In one example embodiment, the routes R11, R12 carry an ESID I1, and a first ETI field.

[0145] In one example embodiment, the computer readable storage medium described above can include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store computer programs.

[0146] The specific examples in the present embodiment can refer to the examples described in the above embodiments and example embodiments, which will not be described herein again.

[0147] The embodiments of the present application also provide an electronic device, which includes a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to perform the steps in any of the above method embodiments.

[0148] Optionally, in the present embodiment, the processor can be configured to execute the following steps by the computer program:

[0149] S1, publishing, by a second router PE2, an EVPN RT-1 per ES route R1a generated based on a first Ethernet segment identifier ES I1 to a first router PE1, wherein the first Ethernet segment identifier ES I1 includes at least one of a first use ES I determined according to a first sub-interface, a second sub-interface and a first condition on the second router PE2, and the first use ES I determined by the first router PE1 according to a third sub-interface, a fourth sub-interface and the first condition.

[0150] S2, receiving, by the second router PE2, an EVPN RT-1 per ES route R1b generated based on the first Ethernet segment identifier ESI1 and published by the first router PE1; wherein the first sub-interface and the second sub-interface are not sub-interfaces of the same parent interface, the third sub-interface and the fourth sub-interface are not sub-interfaces of the same parent interface, and the ESI label carried in the EVPN RT-1 per ES route R1b is used to indicate that the first router PE1 filters broadcast, unknown unicast or multicast BUM packets from the first sub-interface or the second sub-interface when the egress of the forwarding is the third sub-interface or the fourth sub-interface, the first use ESI is an ESI used for the first filtering, the first filtering is filtering of BUM packet forwarding between the first sub-interface and the third sub-interface or the fourth sub-interface, or filtering of BUM packet forwarding between the second sub-interface and the third sub-interface or the fourth sub-interface, and the first filtering is performed according to the ESI label of the first use ESI.

[0151] In one exemplary embodiment, the electronic device described above can further include a transmission device connected to the processor, and an input / output device connected to the processor.

[0152] The specific examples in the embodiments can refer to the examples described in the above embodiments and exemplary implementation manners, which will not be described herein again.

[0153] Obviously, those skilled in the art should understand that the modules or steps of the present application described above can be realized by general computing devices, which can be concentrated on a single computing device or distributed on a network composed of multiple computing devices, and can be realized by program codes executable by the computing devices, so that they can be stored in storage devices and executed by the computing devices, and in some cases, the steps shown or described can be executed in different order, or they can be manufactured into individual integrated circuit modules or a single integrated circuit module. Therefore, the present application is not limited to any specific combination of hardware and software.

[0154] The above only describes the preferred embodiments of the present application and is not intended to limit the present application. For those skilled in the art, the present application can have various modifications and changes. Any modification, equivalent replacement, improvement, etc. within the principles of the present application shall be included in the protection scope of the present application.

Claims

1. A route distribution method characterized by comprising: Comprising: publishing, by a first router PE1, an EVPN RT-1 per ES route R1b generated based on a first Ethernet segment identity ESI1 to a second router PE2, wherein the first Ethernet segment identity ESI1 comprises at least one of a first use ESI determined according to a third sub-interface, a fourth sub-interface on the first router PE1 and a first condition, the first use ESI determined by the second router PE2 according to a first sub-interface, a second sub-interface and the first condition; receiving, by the first router PE1, the EVPN RT-1 per ES route R1a published by the second router PE2 and generated based on the first Ethernet segment identity ESI1; wherein the first sub-interface and the second sub-interface do not belong to a same parent interface, the third sub-interface and the fourth sub-interface do not belong to a same parent interface, and the EVPN RT-1 per ES route R1a is used to instruct the first router PE1 to perform a first processing, the first processing comprising encapsulating an ESI label of the first use ESI when the PE1 forwards a BUM packet from the third sub-interface or the fourth sub-interface to the PE2; the first use ESI is an ESI used for a first filtering, the first filtering comprising a filtering on a BUM packet forwarding between the first sub-interface and the third sub-interface or the fourth sub-interface, or a filtering on a BUM packet between the second sub-interface and the third sub-interface or the fourth sub-interface, and the first filtering is performed according to an ESI label of the first use ESI.

2. The route distribution method according to claim 1, characterized by, the parent interface of the two sub-interfaces of the second router PE2 or the first router PE1 is respectively bound with a different second use ESI, and the first condition comprises: in a case where the two sub-interfaces are bound with a same virtual Ethernet segment identity vESI, determining the vESI as the first use ESI corresponding to the two sub-interfaces. wherein the second use ESI is an ESI used for a unicast forwarding to any one of the two sub-interfaces.

3. The route distribution method according to claim 1, wherein, the first condition comprises: in a case where the parent interface of the first sub-interface and the parent interface of the second sub-interface of the second router PE2 are bound with a same second use ESI, determining the same second use ESI as the first use ESI corresponding to the two sub-interfaces; and in a case where the parent interface of the third sub-interface and the parent interface of the fourth sub-interface of the first router PE1 are bound with a same second use ESI, determining the same second use ESI as the first use ESI corresponding to the two sub-interfaces.

4. The route distribution method according to claim 3, characterized by, The method further comprises: receiving, by the first router PE1, a packet from a third access interface, broadcasting and forwarding the packet to the second router PE2 in a case where the MAC is not found, and encapsulating an ESI label of the first use ESI and an EVI label. The second router PE2 finds an EVPNVPLS instance according to the EVI label, and the ESI found according to the ESI label is the same as the first use ESI to which the first access interface and the second access interface in the EVPNVPLS instance belong; and the second router PE2 discards the traffic broadcast to the first access interface and the second access interface on the second router PE2; The first router PE1 receives the traffic of the third access interface, determines the third access interface as the forwarding outlet corresponding to the first source address of the learned source address, and generates an RT2 route R2-1 and sends the RT2 route R2-1 to the second router PE2; the RT2 route R2-1 carries an ESID of an ESI bound by the third access interface and a first ETI field of the third access interface; The second router PE2 receives the RT2 route R2-1, finds the first access interface locally according to the ESID and the ETI in the RT2 route R2-1 message received by the second router PE2, and determines the forwarding outlet generating the first MAC source address as the ESI and the ETI to which the first access interface belongs; The first access interface corresponds to the first sub-interface, the second access interface corresponds to the second sub-interface, the third access interface corresponds to the third sub-interface, and the fourth access interface corresponds to the fourth sub-interface.

5. The route distribution method according to claim 2 or 3, characterized by, The first sub-interface and the third sub-interface satisfy a second condition, and the second sub-interface and the fourth sub-interface satisfy the second condition; the filtering is performed by the ESI label of the EVPN RT-1 per ES route R1a, R1b; The second condition is that two sub-interfaces in a first pair of sub-interfaces are located on different PE nodes and have the same VLAN, and the two sub-interfaces can reach each other without passing through any PE node in between, and then it is determined that the two sub-interfaces satisfy the second condition, wherein the first pair of sub-interfaces is the first sub-interface and the third sub-interface, or the first pair of sub-interfaces is the second sub-interface and the fourth sub-interface.

6. The route distribution method according to claim 1, wherein, The R1a is further configured to indicate to the PE1 that the PE2 will perform a second processing, so the PE1 needs to perform a first processing, and the second processing is that the PE2 performs filtering when the forwarding outlet is the first sub-interface or the second sub-interface when forwarding a broadcast, unknown unicast or multicast BUM message from the third sub-interface or the fourth sub-interface.

7. The route distribution method according to claim 4, wherein, The method further comprises: The first interface identifier and the second interface identifier are respectively specified for the parent interface of the first sub-interface and the parent interface of the second sub-interface, and the second router PE2 publishes the EVPN RT-1 per EVI route R11, R12 generated based on the first Ethernet segment identifier ESI1 and the first interface identifier and the second interface identifier to the first router PE1; and the first Ethernet segment identifier ESI1 is bound to the parent interface of the third sub-interface and the parent interface of the fourth sub-interface on the first router PE1 respectively, and the first interface identifier and the second interface identifier are specified for the parent interface of the third sub-interface and the parent interface of the fourth sub-interface respectively, and the EVPN RT-1 per EVI route R21, R22 based on the first Ethernet segment identifier ESI1 and the first interface identifier and the second interface identifier is generated by the first router PE1 and is published to the second router PE2.

8. The route distribution method according to claim 7, wherein, The first interface identifier and the second interface identifier are carried in an Ethernet Tag ID field of the EVPN RT-1 per EVI route; the EVPN RT-1 per EVI route R11, R21 carries an ESI ID I1, a first ETI field, an ESI label and an EVI label, and the EVPN RT-1 per EVI route R12, R22 carries the ESI ID I1, a second ETI field, an ESI label and an EVI label; The EVPN RT-1 per EVI route is used for DF election of the first router PE1 and the second router PE2 together with the RT4 route.

9. The route distribution method according to claim 4, wherein, The first access interface and the second access interface are configured with the same horizontal division attribute; and the third access interface and the fourth access interface are configured with the same horizontal division attribute.

10. The route distribution method according to claim 7, wherein, The method further comprises: The EVI label carried by the EVPN RT-1 per EVI route is generated based on an EVPNVPLS instance, and the ESI label of the EVPN RT-1 per ES route is generated based on an ESI instance; The EVI label carried by the EVPN RT-1 per EVI route is used for locally querying a VPLS forwarding label of the EVPN RT-1 per EVI route, the ESI label of the EVPN RT-1 per ES route is used for an ingress PE to determine an ESI to which an ingress AC belongs, and an access interface of an EVPNVPLS instance corresponding to the EVI label carried by the EVPN RT-1 per EVI route is subjected to BUM filtering, wherein the access interface is under the EVPNVPLS instance and belongs to the same ESI as the ingress AC. The ingress AC is an AC through which the BUM packet is received by an ingress PE, the ingress PE is a PE receiving the BUM packet from an access interface, and the egress PE is a PE forwarding the BUM packet from an access interface.

11. The route distribution method according to claim 8, wherein, The method further comprises: The first router PE1 receives the R11 of the second router PE2 and the RT4 route R4-1, finds the second access interface and the fourth access interface bound under the first ESI according to the ESI ID I1 of the R11, and constructs ESI protection in a case where the first ETI field of the R11 and the ETI field of the third access interface locally are the same. According to a comparison result of a DF priority and a local priority of the RT4 route R4-1, a DF priority of the first router PE1 is determined as non-DF, wherein the RT4 route R4-1 carries a DF election rule and a priority of the second router PE2, and the R4-1 is an RT4 route sent by the second router PE2 and received by the first router PE1.

12. The route distribution method according to claim 8, wherein, The method further comprises: In a case where the first router PE1 receives the R12 of the second router PE2 and the RT4 route R4-1, a second layer interface bound under the first use ESI is determined as the third access interface and the fourth access interface according to an ESI I1 of the R12, and ESI protection is constructed in a case where a second ETI field of the R12 and an ETI field of the local fourth access interface are identical. According to a comparison result of a DF priority and a local priority of the RT4 route R4-1, a DF priority of the first router PE1 is determined as non-DF, wherein the RT4 route R4-1 carries a DF election rule and a priority of the second router PE2, and the R4-1 is an RT4 route sent by the second router PE2 and received by the first router PE1.

13. The route distribution method according to claim 11 or 12, characterized by, The method further comprises: A destination MAC of a forwarding packet B1 is MAC1, and a forwarding outlet of MAC1 is determined as the third access interface from the fifth access interface to the first router PE1. The forwarding packet B1 is directly forwarded from the third access interface to the BRAS-UP1. When the third access interface has a link fault, the third access interface is switched to a backup ESI for forwarding, and an EVI label is encapsulated. According to an EVI label, a physical address MAC forwarding table corresponding to the MAC1 address is found under the EVPNVPLS instance by the second router PE2, and a corresponding outlet is determined as the first access interface.

14. The route distribution method according to claim 4, wherein, The method further comprises: The third access interface and the fourth access interface on the first router PE1 do not have a horizontal segmentation attribute. In a case where the ESI bound by the third access interface and the fourth access interface is determined as being identical, it is determined that no traffic is forwarded.

15. A route distribution apparatus characterized by comprising: The method comprises: A first publishing module is configured to publish, by the first router PE1, an EVPN RT-1 per ES route R1b generated based on a first Ethernet segment identifier ESI1 to a second router PE2, wherein the first Ethernet segment identifier ESI1 comprises at least one of a first use ESI determined according to a third sub-interface, a fourth sub-interface and a first condition on the first router PE1, and the first use ESI determined according to a first sub-interface, a second sub-interface and the first condition on the second router PE2. A second publishing module is configured to receive, by the first router PE1, an EVPN RT-1 per ES route R1a published by the second router PE2 and generated based on the first Ethernet segment identifier ESI1. The first sub-interface and the second sub-interface are not of the same parent interface, the third sub-interface and the fourth sub-interface are not of the same parent interface, the EVPN RT-1 per ES route R1a is used to instruct the first router PE1 to perform a first processing, the first processing is that when the PE1 forwards a BUM packet from the third sub-interface or the fourth sub-interface to the PE2, an ESI label carried in the R1a is encapsulated; the first use ESI is an ESI used for first filtering, the first filtering is filtering of BUM packet forwarding between the first sub-interface and the third sub-interface or the fourth sub-interface, or filtering of BUM packet forwarding between the second sub-interface and the third sub-interface or the fourth sub-interface; and the first filtering is performed according to an ESI label of the first use ESI.

16. A computer readable storage medium, characterized in that, The storage medium has a computer program stored therein, and the computer program is configured to execute the method in any one of claims 1 to 14 when running.

17. An electronic device, comprising: The device comprises a memory and a processor, the memory has a computer program stored therein, and the processor is configured to execute the method in any one of claims 1 to 14 through the computer program.

Images