Method of protecting traffic in a mesh network

• US 20020075873A1
• Filed: 12/20/2000
• Published: 06/20/2002
• Est. Priority Date: 12/20/2000
• Status: Active Grant

• Current Assignee: Ciena Corporation
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Dallaire, Michel, Lindhorst-Ko, Gwenda, Lo, Waichi
• Granted Patent: US 6,853,641 B2
• Time in Patent Office: Days
• US Class Current: 370/394
• 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/24 Multipath
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 47/34 ensuring sequence integrity, e.g. using sequence numbers

Abstract

Method and apparatus for protection of traffic in a mesh network are disclosed. A source node sends duplicate copies of data packets of the protected traffic on physically diverse paths through the network. The data packets include a sequence number for determining their position in the protected traffic. A destination node receives the data packets from the paths, selects the next data packet in the sequence and transfers that packet to a receiving queue, while duplicate packets are discarded, and later packets in the sequence are held in a holding queue for future selection. The method does not require a synchronization function between the paths to perform a switchover in the event of a fault, and therefore the method is simple to implement. The method is also scalable to provide multiple physically diverse paths in order to achieve greater degrees of protection.

Claims

1. A method of protecting traffic in a mesh network, the method comprising the steps of:

establishing at least two physically diverse paths from a source node to a destination node for transmitting data packets of the traffic;

tagging, at the source node, each of said data packets with a sequence number;

transmitting, by the source node, the tagged data packets onto the paths;

receiving, at the destination node, the data packets transmitted over the paths; and

reconstructing, at the destination node, the traffic from the received data packets.

2. The method of claim 1 wherein the destination node includes a receiving queue and the step of reconstructing the traffic comprises the steps of:

retrieving the sequence number of data packets received by the destination node;

delivering a first data packet to the receiving queue responsive to the sequence number of the first data packet being equal to an expected sequence number; and

updating the expected sequence number in accordance with the sequence number of the first data packet.

3. The method of claim 2 wherein the destination node further includes a holding queue and the step of reconstructing the traffic further comprises the steps of:

delivering a second data packet to the holding queue responsive to the sequence number of the second data packet being greater than the expected sequence number; and

delivering the second data packet from the holding queue to the receiving queue responsive to the sequence number of the second data packet being equal to the expected sequence number.

4. The method of claim 3 wherein the step of reconstructing further comprises the steps of:

starting a timer for each data packet that is delivered to the holding queue; and

delivering, responsive to a timer expiring, the data packet corresponding to the expired timer to the receiving queue.

5. The method of claim 4 wherein the step of reconstructing further comprises the step of discarding a particular data packet responsive to the sequence number of the particular data packet being less than the expected sequence number, or responsive to the sequence number of the particular data packet being equal to the sequence number of another data packet in the holding queue.

6. A method of receiving traffic in a mesh network, the method comprising the steps of:

establishing at least two physically diverse paths from a source node to a destination node for carrying data packets of the traffic;

receiving, at the destination node, the data packets transmitted over the paths; and

reconstructing, at the destination node, the traffic from the received data packets.

7. The method of claim 6 wherein the destination node includes a receiving queue and the step of reconstructing the traffic comprises the steps of:

retrieving the sequence number of data packets received by the destination node;

delivering a first data packet to the receiving queue responsive to the sequence number of the first data packet being equal to an expected sequence number; and

updating the expected sequence number in accordance with the sequence number of the first data packet.

8. The method of claim 7 wherein the destination node further includes a holding queue and the step of reconstructing the traffic further comprises the steps of:

delivering a second data packet to the holding queue responsive to the sequence number of the second data packet being greater than the expected sequence number; and

delivering the second data packet from the holding queue to the receiving queue responsive to the sequence number of the second data packet being equal to the expected sequence number.

9. The method of claim 8 wherein the step of reconstructing further comprises the steps of:

starting a timer for each data packet that is delivered to the holding queue; and

delivering, responsive to a timer expiring, the data packet corresponding to the expired timer to the receiving queue.

10. The method of claim 9 wherein the step of reconstructing further comprises the step of discarding a particular data packet responsive to the sequence number of the particular data packet being less than the expected sequence number, or responsive to the sequence number of the particular data packet being equal to the sequence number of another data packet in the holding queue.

11. A network node for receiving protected traffic carried over physically diverse paths in a mesh network, the node comprising:

a plurality of receivers, each one of said receivers for connecting to one of the paths and being operable to receive data packets of the traffic, each of said data packets having a sequence number corresponding to its position in the traffic;

a controller being operable to maintain an expected sequence number, the expected sequence number corresponding to the position in the traffic of a next data packet to be received; and

a receiving queue for receiving said data packets,

the controller being operable to cause a particular data packet to be delivered from any one of the receivers to the receiving queue responsive to the particular data packet having a sequence number equal to the expected sequence number.

12. The network node of claim 11 further comprising:

a holding queue for storing one copy of each data packet having a sequence number greater than the expected sequence number, and wherein the controller is further operable to cause a stored data packet having a sequence number equal to the expected sequence number to be delivered from the holding queue to the receiving queue.

13. The network node of claim 12 wherein the controller is further operable to maintain a timer for each data packet that is stored in the holding queue, and to cause a particular stored data packet corresponding to an expired timer to be delivered to the receiving queue.

14. The network node of claim 13 wherein the controller is further operable to discard any data packet having a sequence number less than the expected sequence number, or having a sequence number equal to the sequence number of a data packet stored in the holding queue.