Protection switching in a communications network employing label switching

• US 20030063560A1
• Filed: 10/02/2001
• Published: 04/03/2003
• Est. Priority Date: 10/02/2001
• Status: Active Grant

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Network Communications Incorporated (Fujitsu Limited)
• Inventors: Widjaja, Indra, Jenq, Yau-Ren
• Granted Patent: US 7,039,005 B2
• Time in Patent Office: Days
• US Class Current: 370/216
• CPC Class Codes: H04L 2012/5627 Fault tolerance and recovery
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/302 Route determination based on requested QoS
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]

Abstract

A system and method of protection switching in a communications network that makes more efficient use of resources in the network and reduces the loss of data traffic carried by the network. The communications network includes an established working path and an established protect path interconnecting a source node and a sink node. The source node and the sink node are configured to perform label switching on the network. The source node receives primary data traffic and secondary data traffic over one or more communications paths. In a fault-free condition, the source node sends the primary data traffic over the working path to the sink node, and sends the secondary data traffic over the protect path to the sink node. In the event of a fault or switchover condition in the working path, the source node performs traffic trunk and label merging on the primary and secondary traffic, and sends the merged traffic over the protect path to the sink node.

Claims

1. A method of protection switching for use in a communications system including a source node, a sink node, a first communications path configured to interconnect the source and sink nodes, and a second communications path configured to interconnect the source and sink nodes, comprising the steps of:

receiving at least one first incoming data unit and at least one second incoming data unit at the source node, the at least one first incoming data unit and the at least one second incoming data unit having a first label and a second label, respectively, associated therewith;

determining whether the first communications path is in a predetermined state;

in the event the first communications path is in the predetermined state, identifying the at least one first and second incoming data units for transmission over the first and second communications paths based upon the respective first and second labels, and sending first outgoing data corresponding to the at least one first incoming data unit from the source node to the sink node over the first communications path, and sending second outgoing data corresponding to the at least one second incoming data unit from the source node to the sink node over the second communications path; and

in the event the first communications path is not in the predetermined state, identifying the at least one first incoming data unit and at least some of the second incoming data units for transmission over the second communications path based upon the respective first and second labels, associating a first common label with the first and second outgoing data, respectively, and sending the first outgoing data and at least some of the second outgoing data along with the associated first common label from the source node to the sink node over the second communications path.

2. The method of claim 1 further including the steps of, in the event the first communications path is in the predetermined state, associating a third label with the first outgoing data before sending the first outgoing data from the source node to the sink node over the first communications path, and associating a fourth label with the second outgoing data before sending the second outgoing data from the source node to the sink node over the second communications path.

3. The method of claim 2 further including the steps of receiving third and fourth incoming data corresponding to the first and second outgoing data, respectively, at the sink node, identifying the third and fourth incoming data for transmission over a third communications path based upon the respective third and fourth labels, associating a second common label with the third and fourth incoming data, and sending third and fourth outgoing data corresponding to the third and fourth incoming data, respectively, along with the associated second common label from the sink node to a subsequent node over the third communications path.

4. The method of claim 1 further including the step of, in the event the first communications path is not in the predetermined state, sending a first notification message that the first communications path is not in the predetermined state from the sink node to the source node over a communications link coupling the source and sink nodes.

5. The method of claim 4 further including the step of sending a first acknowledgment message in response to the first notification message from the source node to the sink node over the communications link coupling the source and sink nodes.

6. The method of claim 4 further including the step of sending a second notification message that the first communications path is not in the predetermined state from a node included in the first communications path to the sink node over a portion of the first communications path.

7. The method of claim 6 further including the step of sending a second acknowledgment message in response to the second notification message from the sink node to the node included in the first communications path over the portion of the first communications path.

8. The method of claim 6 wherein the step of determining whether the first communications path is in the predetermined state is performed by the node included in the first communications path.

9. The method of claim 1 further including the step of, in the event the first communications path is not in the predetermined state, sending a plurality of notification messages that the first communications path is not in the predetermined state from the sink node to the source node over a plurality of respective communications paths interconnecting the source and sink nodes.

10. The method of claim 9 further including the step of sending at least one acknowledgment message in response to at least one of the plurality of notification messages from the source node to the sink node over at least one of the plurality of respective communications paths interconnecting the source and sink nodes.

11. The method of claim 1 further including the steps of, in the event the step of sending the first and second outgoing data along with the associated common label over the second communications path causes traffic congestion on the second communications path, establishing an alternate communications path configured to interconnect the source and sink nodes, and sending a selected one of the first and second outgoing data from the source node to the sink node over the alternate communications path while sending the other outgoing data from the source node to the sink node over the second communications path.

12. A communications system configured to provide protection switching, comprising:

a source node configured to receive at least one first incoming data unit and at least one second incoming data unit, the at least one first incoming data unit and the at least one second incoming data unit having a first label and a second label, respectively, associated therewith;

a sink node;

a first communications path configured to interconnect the source and sink nodes, the first path including at least one node; and

a second communications path configured to interconnect the source and sink nodes,

wherein the at least one node included in the first path and the sink node are configurable to determined whether the first path is in a predetermined state,

wherein, in the event the first path is in the predetermined state, the source node is further configured to identify the at least one first and second incoming data units for transmission over the first and second paths based upon the respective first and second labels, to send first outgoing data corresponding to the at least one first incoming data unit from the source node to the sink node over the first path, and to send second outgoing data corresponding to the at least one second incoming data unit from the source node to the sink node over the second path, and

wherein, in the event the first path is not in the predetermined state, the source node is further configured to identify the at least one first and second incoming data units for transmission over the second path based upon the respective first and second labels, to associate a common label with the first and second outgoing data, respectively, and to send the first and second outgoing data along with the associated common label from the source node to the sink node over the second path.

13. The system of claim 12 wherein the first and second paths comprise explicitly routed paths.

14. The system of claim 12 wherein the first and second incoming data units are part of the same forwarding equivalence class.

15. The system of claim 12 wherein the at least one first incoming data unit comprises at least one first traffic flow of a first predetermined quality of service level, and the at least one second incoming data unit comprises at least one second traffic flow of a second predetermined quality of service level.

16. The system of claim 15 wherein the first predetermined quality of service level is a constant bit rate service.

17. The system of claim 15 wherein the second predetermined quality of service level is a best effort service.

18. The system of claim 15 wherein the second path is further configured to accommodate respective bandwidths required by the first and second predetermined quality of service levels.