System and method to facilitate interoperability between virtual private LAN service (VPLS) and ethernet virtual private network (EVPN) with all-active multi-homing
US-10666459-B1 · May 26, 2020 · US
US10965594B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10965594-B2 |
| Application number | US-201916371476-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 1, 2019 |
| Priority date | Sep 30, 2016 |
| Publication date | Mar 30, 2021 |
| Grant date | Mar 30, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
This application provides a pseudo wire load sharing method and apparatus, applied to a scenario in which a first provider edge PE device is separately connected to at least one second PE device by using at least two PWs. The method comprises receiving, by the first PE device, a data flow from a customer edge CE device, and forwarding the data flow to a PW trunk interface, where the PW trunk interface is associated with at least two active PWs; and performing, by the first PE device, load sharing processing on the data flow, and forwarding the data flow by using the at least two active PWs. This is beneficial to transmission of large data traffic by using the PW.
Opening claim text (preview).
What is claimed is: 1. A pseudo wire (PW) load sharing method comprising: receiving, by a first provider edge (PE) device, a data flow from a customer edge (CE) device; creating, by the first PE device, a PW trunk interface; associating the PW trunk interface with at least two PWs; obtaining, by the first PE device, an active PW quantity parameter, wherein the active PW quantity parameter represents a quantity of PWs in an active state, and is a positive integer greater than or equal to 2; determining at least two active PWs from the at least two PWs according to the active PW quantity parameter; forwarding the data flow to the PW trunk interface, wherein the first PE device is separately connected to at least one second PE device by using the at least two PWs, and the PW trunk interface is associated with at least two active PWs; and performing, by the first PE device, load sharing on the data flow, and forwarding the data flow by using the at least two active PWs. 2. The method of claim 1 , wherein determining at least two active PWs from the at least two PWs according to the active PW quantity parameter comprises: obtaining, by the first PE device, a priority of each PW in the at least two PWs; and determining at least two PWs as active PWs according to the priority of each PW in the at least two PWs and the active PW quantity parameter. 3. The method of claim 2 , wherein determining at least two PWs as active PWs according to the priority of each PW in the at least two PWs and the active PW quantity parameter comprises: obtaining, by the first PE device, the priority of each PW in the at least two PWs; and determining, from the at least two PWs, at least two PWs with higher priority ranks as active PWs according to a descending order of the priorities of the PWs and the active PW quantity parameter, wherein the priority of the PW is used to indicate precedence in using the PW as an active PW. 4. The method of claim 1 , wherein determining at least two active PWs from the at least two PWs according to the active PW quantity parameter comprises: obtaining, by the first PE device, an internet protocol (IP) address of a peer second PE of each PW in the at least two PWs; and determining at least two PWs as active PWs according to the IP address of the peer second PE of each PW in the at least two PWs and the active PW quantity parameter. 5. The method of claim 4 , wherein determining at least two PWs as active PWs according to the IP address of the peer second PE of each PW in the at least two PWs and the active PW quantity parameter comprises: obtaining, by the first PE device, the IP address of the peer second PE of each PW in the at least two PWs; and determining, from the at least two PWs, at least two PWs with higher IP address ranks as active PWs according to an order of the IP addresses of the peer second PEs of the PWs and the active PW quantity parameter. 6. The method of claim 1 , wherein determining at least two active PWs from the at least two PWs according to the active PW quantity parameter comprises: obtaining, by the first PE device, a priority of each PW in the at least two PWs and an IP address of a peer second PE of each PW in the at least two PWs; and determining at least two PWs as active PWs according to the priority of each PW in the at least two PWs, the IP address of the peer second PE of each PW in the at least two PWs, and the active PW quantity parameter. 7. The method of claim 1 , wherein receiving, by the first PE device, a data flow from a CE device, comprises receiving, by the first PE device, the data flow from the CE device through an attachment circuit (AC) interface, and wherein forwarding the data flow to a PW trunk interface comprises forwarding the data flow to the PW trunk interface according to an association relationship between the AC interface and the PW trunk interface. 8. A first provider edge (PE) device separately connected to at least one second PE device by using at least two PWs, the first PE device comprising: a non-transitory memory comprising instructions; a receiver configured to receive a data flow from a customer edge (CE) device; a processor in communication with the non-transitory memory, wherein the instructions cause the processor to: create a PW trunk interface; associate the PW trunk interface with at least two PWs; obtain an active PW quantity parameter, wherein the active PW quantity parameter represents a quantity of PWs in an active state, and is a positive integer greater than or equal to 2; and determine at least two active PWs from the at least two PWs according to the active PW quantity parameter; forward the data flow to the PW trunk interface, wherein the PW trunk interface is associated with the at least two active PWs; and perform load sharing processing on the data flow; and a transmitter configured to forward the data flow by using the at least two active PWs. 9. The first PE device of claim 8 , wherein the instructions further cause the processor to: obtain a priority of each PW in the at least two PWs; and determine the at least two PWs as active PWs according to the priority of each PW in the at least two PWs and the active PW quantity parameter. 10. The first PE device of claim 9 , wherein the instructions further cause the processor to: obtain the priority of each PW in the at least two PWs; and determine, from the at least two PWs, at least two PWs with higher priority ranks as the active PWs according to an order of the priorities of the PWs and the active PW quantity parameter, wherein the priority of the PW is used to indicate precedence in using the PW as an active PW. 11. The first PE device of claim 8 , wherein the instructions further cause the processor to: obtain an internet protocol (IP) address of a peer second PE of each PW in the at least two PWs; and determine at least two PWs as the active PWs according to the IP address of the peer second PE of each PW in the at least two PWs and the active PW quantity parameter. 12. The first PE device of claim 11 , wherein the instructions further cause the processor to: obtain the IP address of the peer second PE of each PW in the at least two PWs; and determine, from the at least two PWs, at least two PWs with higher IP address ranks as the active PWs according to an order of the IP addresses of the peer second PEs of the PWs and the active PW quantity parameter. 13. The first PE device of claim 8 , wherein the instructions further cause the processor to: obtain a priority of each PW in the at least two PWs and an IP address of a peer second PE of each PW in the at least two PWs; and determine at least two PWs as active PWs according to the priority of each PW in the at least two PWs, the IP address of the peer second PE of each PW in the at least two PWs, and the active PW quantity parameter. 14. The first PE device of claim 8 , wherein the receiver is configured to receive the data flow from the CE device through an attachment circuit (AC) interface, and wherein the instructions further cause the processor to: forward the data flow to the PW trunk interface according to an association relationship between the AC interface and the PW trunk interface; and store the association relationship between the AC interface and the PW trunk interface. 15. The first PE device of claim 8 , wherein the receiver is configured to receive the data flow from the CE device through an attachment circuit (AC) interface, and wherein the instructions further cause the processor to: forward the data flow to a virtual switch instance (VSI); sea
Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272) · CPC title
characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks] (wireless communication networks H04W {; arrangements for dividing the transmission path H04W40/00}) · CPC title
Alternate routing · CPC title
Flow based routing · CPC title
Distributed routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.