Optimized fault notification in an overlay mesh network via network knowledge correlation

• US 6,725,401 B1
• Filed: 10/26/2000
• Issued: 04/20/2004
• Est. Priority Date: 10/26/2000
• Status: Expired due to Fees

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Lindhorst-Ko, Gwenda
• Primary Examiner(s): LE, DIEU MINH T
• Application Number:
  US09/695,969
• Time in Patent Office: 1,272 Days
• Field of Search: 714/47, 714/3, 714/4, 714/25, 714/48, 709/104, 709/105, 709/106, 709/224, 709/225, 709/226
• US Class Current: 714/47.3
• CPC Class Codes: H04J 14/0227 Operation, administration, maintenance or provisioning [OAMP] of WDM networks, e.g. media access, routing or wavelength allocation
• CPC Class Codes: H04J 14/0241 Wavelength allocation for communications one-to-one, e.g. unicasting wavelengths
• CPC Class Codes: H04J 14/0284 WDM mesh architectures
• CPC Class Codes: H04J 14/0291 Shared protection at the optical multiplex section (1:1, n:m)

Abstract

Failures within a communications network are compensated for by establishing a set of two or more communications paths across the network between a source node and a destination node. At the source node a status of each one of the set of communications paths is maintained, and the data traffic is load-balanced across those ones of the set of communications paths having an operational status. In the event of failure of a physical network resource, a failure notification message is propagated to the source node, which registers a non-operation status of each path traversing the failed resource. Load-balancing of the data traffic continues across the remaining operational paths. Traffic may be prioritized based on service level agreements and quality of service protection guarantees.

Claims

1. A method of compensating for network resource failures in a communications network, the method comprising the steps of:

a) establishing a set of at least two communications paths across the network between a source node and a destination node, the set of communications paths being at least partially physically diverse;

b) compiling a path database at the source node including information identifying network resources traversed by each communications path;

c) monitoring at the source node a status of each path in the set of communications paths; and

d) load-balancing data traffic across each path in the set of communications paths having an operational status.

2. A method as claimed in claim 1, wherein each communications path comprises any one of an ATM-SVC, and a Label Switched Path (LSP).

3. A method as claimed in claim 1, wherein the step of establishing the set of communications paths comprises, for each communications path, steps of:

a) launching a path setup message from the source node; and

b) receiving a resource allocation message at the source node in response to the path setup message, the resource allocation message including information identifying a network resource traversed by the communications path.

4. A method as claimed in claim 3, wherein the resource allocation message is generated by a node in the communications path as resources of a downstream hop are allocated to the communications path.

5. A method as claimed in claim 3, wherein the step of compiling a path database comprises a step of updating a path array of the path database on the basis of the information identifying the network resource.

6. A method as claimed in claim 5, wherein the path array comprises, for each communications path, a respective path record having a plurality of resource fields respectively corresponding to one or more network resources which may be traversed by the communications path.

7. A method as claimed in claim 6, wherein each network resource comprises any one or more of:

a physical network link;

a physical network node;

a logical connection between a pair of network nodes;

a SONET/SDH section; and

a SONET/SDH line.

8. A method as claimed in claim 6, wherein a resource field identifies a single network resource.

9. A method as claimed in claim 6, wherein a resource field identifies a logical combination of two or more network resources.

10. A method as claimed in claim 6, wherein the step of updating the path array comprises a step of inserting an indicator flag into the resource field associated with the resource identified in the resource allocation message.

11. A method as claimed in claim 10, wherein the indicator flag comprises a binary “

1”

.

12. A method as claimed in claim 6, further comprising a step of verifying a physical diversity of the set of communications paths.

13. A method as claimed in claim 12, wherein the step of verifying a physical diversity of the set of communications paths comprises a step of adding the resource fields of the respective path records, to thereby calculate a number of paths within the set of communications paths that traverse each physical resource of the network.

14. A method as claimed in claim 1, wherein the step of monitoring the status of each path in the set of communications paths comprises steps of:

a) receiving a failure notification message including information indicative of a failed network resource; and

b) setting a non-operational status for each communications path that traverses the failed network resource.

15. A method as claimed in claim 14, further comprising steps of:

a) detecting the failure of a network resource at a detecting node;

b) generating the failure notification message indicative of the failure; and

c) propagating the failure notification message from the detecting node toward the source node.

16. A method as claimed in claim 15, wherein the failure is detected using conventional layer-1 link failure detection.

17. A method as claimed in claim 16, wherein the failure notification message is a layer-1 link failure alarm message including a link identifier indicative of the failed resource.

18. A method as claimed in claim 17, wherein the failure notification is propagated within layer-1 until it is received at the source node.

19. A method as claimed in claim 18, wherein at each node within the network, the failure notification is launched into every upstream link from which the node is receiving traffic, whereby the failure notification is propagated toward every edge node sourcing traffic destined for points downstream of the failed resource.

20. A method as claimed in claim 14, wherein the step of setting a non-operational status for each communications path that traverses the failed network resource comprises the steps of:

a) searching a path array to identify each path that traverses the failed resource; and

b) one of;

i) updating a status field associated with each identified path to indicate a non-operational status of the path; and

ii) deleting a respective path record associated with each identified path from the path array.

21. A method as claimed in claim 20, wherein the step of searching the path array comprises searching the path array using the information indicative of the failed resource as an array index.

22. A method as claimed in claim 20, wherein the step of searching the path array comprises the steps of:

a) generating a mask of the failed resource using the information indicative of the failed resource; and

b) ANDing the mask with each path record of the path.

23. A method as claimed in claim 1, wherein the step of load-balancing data traffic comprises a step of prioritizing the data traffic based on at least one of service level agreements and QoS guarantees associated with the data traffic.

24. A node in a communications network adapted to compensate for network resource failures in the communications network, the node comprising:

a) means for establishing a set of two or more communications paths across the network to a destination node, the set of communications paths being at least partially physically diverse;

b) a path database adapted to maintain information identifying physical network resources traversed by each communications path;

c) means for monitoring a status of each one of the set of communications paths; and

d) means for load-balancing the data traffic across communications paths of the set of paths that have an operational status.

25. A node as claimed in claim 24, wherein each communications path comprises any one of an ATM-SVC, and a Label Switched Path (LSP).

26. A node as claimed in claim 24, wherein the means for establishing the set of communications paths comprises:

a) means for launching a path setup message toward the destination node to initiate a setup of each communications path;

b) means for receiving a resource allocation message in response to each path setup message, the resource allocation messages including information identifying network resources traversed by a communications path; and

c) means for updating the path database using the information identifying the network resource.

27. A node as claimed in claim 26, wherein the resource allocation message is generated by a node in a communications path as network resources of a downstream hop are allocated to the communications path.

28. A node as claimed in claim 24, wherein the path database comprises, for each communications path, a respective path record having a plurality of resource fields, each resource field corresponding to one or more network resources which may be traversed by a communications path.

29. A node as claimed in claim 28, wherein each network resource comprises any one or more of:

a physical network link;

a physical network node;

a logical connection between a pair of network nodes;

a SONET/SDH section; and

a SONET/SDH line.

30. A node as claimed in claim 28, wherein a resource field corresponds to a single network resource.

31. A node as claimed in claim 28, wherein a resource field corresponds to a logical combination of two or more network resources.

32. A node as claimed in claim 28, wherein the means for updating the path array comprises means for inserting an indicator flag into a resource field corresponding to the resource identified in the resource allocation message.

33. A node as claimed in claim 32, wherein the indicator flag comprises a binary “

1”

.

34. A node as claimed in claim 28, further comprising means for verifying a physical diversity of the set of communications paths.

35. A node as claimed in claim 34, wherein the means for verifying a physical diversity of the set of communications paths comprises means for adding the resource fields of the respective path records.

36. A node as claimed in claim 24, wherein the means for monitoring the status of each one of the set of communications paths comprises:

a) means for receiving a failure notification message including information indicative of a failed network resource; and

b) means for setting a non-operational status for each communications path that traverses the failed network resource.

37. A node as claimed in claim 36, wherein the means for setting a non-operational status for each communications path that traverses the failed network resource comprises:

a) means for searching the path database to identify each path that traverses the failed resource; and

b) one of;

i) means for updating a status field associated with each identified path to indicate a non-operational status of the corresponding path; and

ii) means for deleting a respective path record associated with each identified path from the path database.

38. A node as claimed in claim 37, wherein the means for searching the path database comprises:

a) means for identifying a resource field of the path database corresponding to the failed resource using the information indicative of the failed resource as an array index; and

b) means for searching the path database to locate a respective path record associated with each path having an indicator flag in the identified resource field.

39. A node as claimed in claim 37, wherein the means for searching the path database comprises:

a) means for generating a mask of the failed resource using the information indicative of the failed resource; and

b) means for ANDing the mask with each path record.

40. A node as claimed in claim 24, wherein the means for load-balancing data traffic comprises means for prioritizing the traffic based on one or more of predetermined service level agreements and QoS guarantees.

41. A system for compensating for network resource failures in a communications network comprising a plurality of nodes interconnected by links, the system comprising:

a) means for establishing a set of two or more communications paths across the network between a source node and a destination node, the set of communications paths being at least partially physically diverse;

b) a path database adapted to maintain information identifying physical network resources traversed by each communications path;

c) means for monitoring a status of each one of the set of communications paths; and

d) means for load-balancing the data traffic across ones of the set of communications paths having an operational status.

42. A system as claimed in claim 41, wherein each communications path comprises any one of an ATM-SVC, and a Label Switched Path (LSP).

43. A system as claimed in claim 41, wherein the means for establishing the set of communications paths comprises:

a) means for launching a path setup message in respect of a communications path from the source node;

b) means responsive to the path setup message for allocating a network resource to the communications path in a node intermediate the source and destination nodes;

c) means for receiving resource allocation messages at the source node, each resource allocation message including information identifying the network resource allocated to the communications path by the intermediate node; and

d) means for updating the path database maintained by the source node using the information identifying the allocated network resource.

44. A system as claimed in claim 43, wherein a resource allocation message is generated by each node in the communications path as network resources of a downstream hop are allocated to the communications path.

45. A system as claimed in claim 43, wherein the path database comprises, for each communications path, a respective path record having a path identifier field and a plurality of resource fields, each resource field corresponding to one or more network resources which may be traversed by a communications path.

46. A system as claimed in claim 45, wherein each network resource comprises any one or more of:

a physical network link;

a physical network node;

a logical connection between a pair of network nodes;

a SONET/SDH section; and

a SONET/SDH line.

47. A system as claimed in claim 45, wherein a resource field corresponds to a single network resource.

48. A system as claimed in claim 45, wherein a resource field corresponds to a logical combination of at least two network resources.

49. A system as claimed in claim 45, wherein the means for updating the path database comprises means for inserting an indicator flag into the respective resource field corresponding to the resource identified in the resource allocation message.

50. A system as claimed in claim 49, wherein the indicator flag comprises a binary “

1”

.

51. A system as claimed in claim 45, further comprising means for verifying a diversity of each of the set of communications paths.

52. A system as claimed in claim 51, wherein the step of verifying a diversity of each of the set of communications paths comprises a step of adding the resource fields of the respective path records.

53. A system as claimed in claim 41, wherein the means for monitoring the status of each one of the set of communications paths comprises:

a) means for receiving a failure notification message at the source node, the failure notification message including information indicative of a failed network resource; and

b) means for setting a non-operational status of each communications path that traverses the failed network resource.

54. A system as claimed in claim 53, further comprising:

a) means for detecting a failure of a network resource at a detecting node proximal the failed network resource;

b) means for generating the failure notification message indicative of the failure; and

c) means for propagating the failure notification message from the detecting node toward the source node.

55. A system as claimed in claim 54, wherein the failure is detected by the detecting node using a conventional layer-1 link failure detection technique.

56. A system as claimed in claim 55, wherein the failure notification message is a substantially conventional layer-1 link failure alarm message including a link identifier indicative of the failed resource.

57. A system as claimed in claim 56, wherein the failure notification is propagated within layer-1 until it is received at the source node.

58. A system as claimed in claim 57, further comprising means operative in each node for launching the failure notification to every upstream link from which the node is receiving traffic, whereby the failure notification is propagated toward every edge node sourcing traffic destined for points downstream of the failed resource.

59. A system as claimed in claim 53, wherein the means for setting a non-operational status of each communications path that traverses the failed network resource comprises:

a) means for searching the path database to identify each path that traverses the failed resource; and

b) one of;

i) means for updating a respective status field associated with each identified path to indicate a non-operational status of the corresponding path; and

ii) means for deleting a respective path record associated with each identified path from the path database.

60. A system as claimed in claim 59, wherein the wherein the means for searching the path database comprises:

a) means for identifying a resource field of the path database corresponding to the failed resource using the information indicative of the failed resource as an array index; and

b) means for searching the path database to locate a respective path record associated with each path having an indicator flag in the identified resource field.

61. A system as claimed in claim 59, wherein the means for searching the path database comprises:

a) means for generating a mask of the failed resource using the information indicative of the failed resource; and

b) means for ANDing the mask with each path record of the path database.

62. A system as claimed in claim 41, wherein the means for load-balancing data traffic comprises means for prioritizing the data traffic based on at least one of service level agreements and QoS guarantees.