Methods and systems for providing MPLS-based layer-2 virtual private network services
View Patent ↗Methods and systems for forwarding packets over Label Switched Paths (LSPs) in a Virtual Private Network (VPN) are implemented within a Layer-2 architecture. A system includes a number of multi-purpose nodes connected by a number of multi-protocol label switching (MPLS) LSP links. Each multi-purpose node contains at least one bridging module (BM) that runs an extension of a bridging protocol (BP) contained in the IEEE 802.1d standard. The BP is used to establish MPLS LSPs between the BMs. The BP then generates a spanning tree using a spanning tree program to establish an optimal number of active LSPs. The remaining LSPs are then set to “inactive” The BM de-allocates the resources assigned to inactive LSPs and makes the resources available to other active LSPs.
1. A processing unit for forwarding data packets over a bi-directional Label Switched Path (LSP) comprising at least one bridging module (BM) that:
generates a spanning tree for a plurality of Virtual Private Networks (VPN) to indicate an optimal set of bi-directional LSPs;
determines a number of active, bidirectional LSPs required to provide full network connectivity for all of the VPNs and inactive LSPs within the VPNs; and
reallocates resources associated with inactive bi-directional LSPs for forwarding data packets.
2. The processing unit of claim 1 , wherein the BM further receives packets from a subscriber, wherein the packets are based on a Layer-2 address.
3. The processing unit of claim 1 , wherein the BM further generates a spanning tree for the VPNs to indicate an optimal set of active, bi-directional LSPs for transferring data packets between a plurality of BMs.
4. The processing unit of claim 3 , wherein the BM further generates the spanning tree by:
determining a root BM for each VPN; and
determining a designated BM and a non-designated BM for pairs of BMs connected by an active, bi-directional LSP.
5. The processing unit of claim 4 , wherein the BM further:
determines whether a bi-directional LSP connection is active between two BMs;
for the active bi-directional LSPs, performing a first sequence, comprising:
sending a control message from the non-designated BM to the designated BM;
setting a resource flag in the control message to a first value at the non-designated BM; and
setting a flag at the designated BM to a first value indicating that the designated BM can receive information packets from the non-designated BM on the LSP connection; and
for the inactive, bi-directional LSPs, performing a second sequence, comprising:
setting the resource flag in the control message to a second value at the non-designated BM; and
setting the flag at the designated BM to a second value indicating that the designated BM cannot receive information packets from the non-designated BM on the LSP connection.
6. The processing unit of claim 5 , wherein the BM further:
reallocates bandwidth associated with the bi-directional LSP between the non-designated BM and the designated BM; and
maintains a control channel for transmitting the control messages.
7. The processing unit of claim 4 , wherein the BM further determines a root BM by:
determining an administrative priority field that specifies the priority for the BM to become the root BM in each VPN; and
selecting the BM that has the highest priority.
8. The processing unit of claim 7 , wherein the administrative priority field comprises:
a plurality of administrative preference parameters used to identify the preference of the BM in becoming a root BM in each VPN; and
a lock key parameter associated with at least one administrative preference parameter, wherein the lock key parameter is used to maintain the BM as the root BM.
9. The processing unit of claim 8 , wherein the administrative preference parameter is selected from a group consisting of a geographic preference parameter, packet processing load parameter, a bandwidth availability parameter, and a load balancing parameter.
10. The processing unit of claim 4 , wherein the BM further:
determines bandwidth associated with the bi-directional LSPs in each VPN; and
sums the inverse of the bandwidth associated with the bi-directional LSPs from the BM to the root BM.
11. The processing unit of claim 4 , wherein the BM further:
determines a total number of hops for the bi-directional LSP in each VPN; and
calculates a hop count by summing hops from the BM to the root BM.
12. The processing unit of claim 3 , wherein the BM further generates the spanning tree by setting the bi-directional LSPs between a root BM and non-root BMs as active.
13. The processing unit of claim 2 further comprising at least one interface operable to connect a Multi-Protocol Label Switching (MPLS) node to other MPLS nodes.
14. The processing unit of claim 13 wherein the interface is selected from a list consisting of a physical interface, a MPLS-LPS, and an Internet Protocol Security (IPSec) interface.
15. The processing unit of claim 3 , wherein the data packet is encapsulated by an outer MPLS label and an inner MPLS label, wherein the outer MPLS label identifies a node and the inner MPLS label identifies a VPN.
16. A method for forwarding data packets over a bi-directional Label Switched Path (LSP) comprising:
generating a spanning tree for a plurality of Virtual Private Networks (VPN) to indicate an optimal set of bi-directional LSPs;
determining a number of active bi-directional LSPs required to provide full network connectivity and inactive LSPs within each VPN; and
reallocating resources associated with inactive bi-directional LSPs for forwarding data packets.
17. The method of claim 16 further comprising receiving packets from a subscriber, wherein the packets are based on a Layer-2 address.
18. The method of claim 16 further comprising generating a spanning tree for each VPN to indicate the optimal set of active bi-directional LSPs for transferring a data packet between a plurality of BMs.
19. The method of claim 18 further comprising:
determining a root BM for each VPN; and
determining a designated BM and a non-designated BM for pairs of BMs connected by an active, bi-directional LSP.
20. The method of claim 19 further comprising:
determining whether a bi-directional LSP connection is active between two BMs;
for the active bi-directional LSPs, performing a first sequence, comprising:
sending a control message from the non-designated BM to the designated BM;
setting a resource flag in the control message to a first value at the non-designated BM;
setting a flag at the designated BM to a first value indicating that the designated BM can receive information packets from the non-designated BM on the LSP connection; and
for the inactive bi-directional LSPs, performing a second sequence, comprising:
setting the resource flag in the control message to a second value at the non-designated BM; and
setting the flag at the designated BM to a second value indicating that the designated BM cannot receive information packets from the non-designated BM on the LSP connection.
21. The method of claim 20 further comprising:
reallocating bandwidth associated with the bi-directional LSP between the non-designated BM and the designated BM; and
maintaining a control channel for transmitting the control messages.
22. The method of claim 19 , wherein determining the root BM comprises:
determining an administrative priority field that specifies the priority for the BM to become the root BM in each VPN; and
selecting the BM that has the highest priority.
23. The method of claim 22 , wherein the administrative priority field comprises:
a plurality of administrative preference parameters used to identity the preference of the BM in becoming a root BM in the VPN; and
a lock key parameter associated with at least one administrative preference parameter, wherein the lock key parameter is used to maintain the BM as the root BM.
24. The method of claim 23 , wherein the administrative preference parameter is selected from a group consisting of a geographic preference parameter, packet processing load parameter, a bandwidth availability parameter, and a load balancing parameter.
25. The method of claim 19 , wherein generating the spanning tree comprises:
determining bandwidth associated with the bi-directional LSPs in the VPN; and
summing the inverse of the bandwidth associated with the bi-directional LSPs from the BM to the root BM.
26. The method as in claim 19 , wherein generating the spanning tree comprises:
determining a total number of hops for the bi-directional LSP in each VPN; and
calculating a hop count by summing hops from the BM to the root BM.
27. The method of claim 18 , wherein generating the spanning tree comprises setting the bi-directional LSPs between the root BM and non-root BMs as active.
28. The method of claim 17 , further comprising connecting a Multi-Protocol Label Switching (MPLS) node to other MPLS nodes.
29. The method of claim 18 , wherein the data packet is encapsulated by an outer MPLS label and an inner MPLS label, and wherein the outer MPLS label identifies a node and the inner MPLS label identifies a VPN.