Comprehensive model for VPLS

• US 20060245436A1
• Filed: 04/28/2005
• Published: 11/02/2006
• Est. Priority Date: 04/28/2005
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Sajassi, Ali
• Granted Patent: US 8,213,435 B2
• Time in Patent Office: Days
• US Class Current: 370/395.530
• CPC Class Codes: H04L 12/2898 Subscriber equipments DSL modems H04M11/062; cable modems H04L12/2801
• CPC Class Codes: H04L 12/4645 Details on frame tagging routing of packets H04L45/00; support for virtual LAN H04L49/354
• CPC Class Codes: H04L 12/465 wherein a single frame includes a plurality of VLAN tags
• CPC Class Codes: H04L 12/4691 GVRP [GARP VLAN registration protocol]

Abstract

A VPLS model is implemented in a network-facing provider edge (n-PE) device configured to receive a packet from an access network; the packet having a first Virtual Local Area Network (VLAN) tag of a first predetermined bit length. The n-PE device mapping the service instance identifier of the first VLAN tag into a second VLAN tag of a second predetermined bit length greater than the first predetermined bit length, the second VLAN tag identifying a Virtual Private LAN Service (VPLS) instance. The n-PE device then sends the packet with the second VLAN tag across a service provider (SP) core network via a pseudowire (PW) that functions as a logical link to another PE device. It is emphasized that this abstract is provided to comply with the rules requiring an abstract that will allow a searcher or other reader to quickly ascertain the subject matter of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. 37 CFR 1.72(b).

Claims

1. A processor-implemented method of operation for a network-facing provider edge device (n-PE) of a core network, the method comprising:

receiving a packet from an access network, the packet having a first Virtual Local Area Network (VLAN) tag of a first predetermined bit length; and

mapping the service instance identifier of the first VLAN tag into a second VLAN tag of a second predetermined bit length greater than the first predetermined bit length, the second VLAN tag identifying a Virtual Private LAN Service (VPLS) instance;

sending the packet with the second VLAN tag across a service provider (SP) core network via a pseudowire (PW) that functions as a logical link to another PE device.

2. The processor-implemented method of claim 1 further comprising:

executing an application that exchanges VLAN configuration information with other network devices.

3. The processor-implemented method of claim 2 wherein the application comprises a version of GARP (Generic Attribute Registration Protocol) VLAN Registration Protocol (GVRP).

4. The processor-implemented method of claim 1 wherein core network comprises a Multi-protocol label switching (MPLS)/Internet Protocol (IP) network.

5. A processor-implemented method of operation for a network-facing provider edge device (n-PE) of a core network, the method comprising:

receiving a packet from an access network, the packet being in a first format and including a first Virtual Local Area Network (VLAN) tag of a first predetermined bit length;

converting the packet from the first format into a second format in which the first VLAN tag is mapped into a second VLAN tag having a second predetermined bit length format, the second predetermined bit length being greater than the first predetermined bit length, the second VLAN tag identifying a Virtual Private LAN Service (VPLS) instance;

sending the packet with the second VLAN tag across a service provider (SP) core network via a pseudowire (PW) that functions as a logical link to another PE device.

6. The processor-implemented method of claim 5 wherein the logical link comprises an IEEE 802.1Q-compatible trunk.

7. The processor-implemented method of claim 5 wherein the access network comprises an Ethernet access network.

8. The processor-implemented method of claim 5 further comprising:

executing an application that exchanges VLAN configuration information with other network devices.

9. The processor-implemented method of claim 8 wherein the application comprises a version of GARP (Generic Attribute Registration Protocol) VLAN Registration Protocol (GVRP).

10. A network-facing provider edge (n-PE) device comprising:

a port to receive a packet from an access network, the customer frame having a first Virtual Local Area Network (VLAN) tag of a first predetermined bit length, the first VLAN tag including a service instance identifier; and

a processing unit that converts the packet from the first format into a second format in which the service instance identifier of the first VLAN tag is mapped into a second VLAN tag having a second predetermined bit length format, the second predetermined bit length being greater than the first predetermined bit length, the processing unit being operable to send the packet in the second format across a service provider (SP) core network via a pseudowire (PW) that functions as a logical link to a second n-PE device.

11. The n-PE device of claim 10 wherein the logical link comprises an IEEE 802.1Q-compatible trunk.

12. The n-PE device of claim 10 wherein the processing unit is further operable to execute an application that exchanges VLAN configuration information with the second n-PE device.

13. The n-PE device of claim 12 wherein the application comprises a version of GARP (Generic Attribute Registration Protocol) VLAN Registration Protocol (GVRP).

14. A provider edge device comprising:

a plurality of ports; and

means for receiving a packet received at one of the ports in a first format, the first format including a first Virtual Local Area Network (VLAN) tag of a first predetermined bit length, the first VLAN tag including a service instance identifier, and for converting the packet into a second format in which the service instance identifier of the first VLAN tag is mapped into a second VLAN tag having a second predetermined bit length format, the second predetermined bit length being greater than the first predetermined bit length, the means also for sending the packet in the second format across a service provider (SP) core network via a pseudowire (PW) that functions as an IEEE 802.1Q-compatible trunk to a second n-PE device.

15. A service provider (SP) network, comprising:

a core network that includes a plurality of network-facing provider edge (n-PE) devices connected by a set of pseudowires (PWs), each of the PWs functioning as a logical link between a pair of n-PE devices;

a first access network configured to transmit a packet of a first format that includes a first Virtual Local Area Network (VLAN) tag of a first predetermined bit length to a first n-PE device of the core network, the first n-PE device being operable to convert the packet into a second format in which the first VLAN tag is mapped to a second VLAN tag of a second predetermined bit length greater than the first predetermined bit length that identifies a Virtual Private LAN Service (VPLS) instance, the first n-PE device being further operable to send the packet in the second format across the core network to a second n-PE device via a first PW, the second n-PE device being operable to convert the packet back to the first format;

a second access network configured to deliver the packet received in the first format from the second n-PE device to a user-facing provider edge (u-PE) device that connects with a customer site.

16. The SP network of claim 15 wherein each of the first and second n-PE devices is further operable to execute an application that exchanges VLAN configuration information.

17. The SP network of claim 16 wherein the application comprises a version of GARP (Generic Attribute Registration Protocol) VLAN Registration Protocol (GVRP).

18. The SP network of claim 15 wherein the core network further includes third and fourth n-PE devices connected with the first and second access networks, respectively.

19. The SP network of claim 18 wherein the mesh is a full mesh, wherein a second PW connects the third and fourth n-PE devices, a third PW connects the first and fourth n-PE devices, and a fourth PW connects the third and second and third n-PE devices.

20. The SP network of claim 19 wherein each of the first and third n-PE devices, and the second and fourth n-PE devices, respectively associated with the first and second access networks, are operable to run a local Spanning Tree Protocol (STP).

21. The SP network of claim 18 wherein the second n-PE device is operable to loop back a Bridge Protocol Data Unit (BPDU) packet received from the first n-PE device via the first PW to the third n-PE device via the fourth PE.