Shared mesh signaling algorithm and apparatus

• US 6,917,759 B2
• Filed: 01/31/2002
• Issued: 07/12/2005
• Est. Priority Date: 01/31/2002
• Status: Expired due to Term

• Current Assignee: Ciena Corporation, Ciena Luxembourg S.a.r.l. (Ciena Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Trudel, Richard, de Boer, Evert E., Shields, James A.
• Primary Examiner(s): Chan, Jason
• Assistant Examiner(s): Leung, Christina Y
• Application Number:
  US10/059,344
• Publication Number:
  US 20040208118A1
• Time in Patent Office: 1,258 Days
• Field of Search: 398/4, 398/5, 398/61, 398/62, 398/63, 398/64, 398/58, 370/216, 370/217, 370/225, 370/227, 370/229
• US Class Current: 398/5
• CPC Class Codes: H04J 2203/0053 Routing
• CPC Class Codes: H04J 2203/006 Fault tolerance and recovery
• CPC Class Codes: H04J 3/085 for ring networks, e.g. SDH/SONET rings, self-healing rings, meashed SDH/SONET networks

Abstract

A shared mesh protection scheme defines an associated protection path when a working connection is established. During the protection path definition, the corresponding protection path information is sent down to a switch card of network elements making up the protection path. Upon detection of the failure, the network elements using an overhead byte message will inform the routing source network element of the connection of the failure in the working path. The overhead bytes used are interrupt driven bytes located in the line and path overhead of network traffic. The routing source node of the connection will then send the corresponding overhead byte messages down the protection path to provide for protection path establishment according to the preloaded data located at the switch card. It should be noted that each connection can have a source and termination element which relates to the source from where the corresponding connection was set-up rather than the direction of the payload transmission. Therefore, once the failure has occurred the source elements will send messages using overhead bytes to the corresponding network elements along the protection path. Accordingly, routing tables located at the switch card of the network elements, set-up when the working path connections were initially established, determine this dynamically allocated protection path environment.

Claims

1. In an optical mesh network, a controller for providing a 1:

N shared mesh protection system to define a protection path associated with N working paths, the controller comprising;

a) a first link for connecting the controller to a control layer of the network to monitor network traffic communicated in a path layer of the network;

b) a second link for connecting the controller to the path layer of the network, the path layer including a plurality of interconnected network elements for providing the associated protection path and working paths;

c) a connection table accessible by the controller, the connection table for having connection information of the network elements associated with the protection path and the working paths, the connection information including a first identity assignable to the protection path and a distinctive second identity assignable to each of the working paths; and

d) a failure indicator for providing the first identity and the second identity relatable to a network failure of the corresponding working path to at least one of the network elements associated with the controller, the failure indicator for insertion into an interrupt driven overhead byte of the network traffic for communication between the network elements;

wherein the failure indicator is communicated in the overhead byte of the network traffic to provide for the establishment of the associated protection path after the network failure has been detected in the corresponding working path.

2. The controller according to claim 1, wherein the first identity is a group number uniquely identifying a defined protection group and the second identity is a member number uniquely identifying a defined member of the protection group.

3. The controller according to claim 2, wherein the group number defines the protection path and the member number defines a corresponding one of the working paths.

4. The controller according to claim 3 further comprising the failure indicator including a pair of overhead bytes.

5. The controller according to claim 4, wherein the first byte of the pair of overhead bytes has the group number and the second byte of the pair of overhead bytes has the member number.

6. The controller according to claim 5, wherein the first byte is selected from one of a K1-K2 byte pair and the second byte is selected from the other one of the K1-K2 byte pair.

7. The controller according to claim 3, wherein use of the overhead bytes for the failure indicator provides for a protection switching time of less than 200 msec.

8. The controller according to claim 2, wherein the failure indicator is used in a signaling message selected from the group comprising:

a switch request, an acknowledgement of a switch request, a negative acknowledgement of a switch request, a revert back to working request, and an acknowledgement of a revert back to working request.

9. The controller according to claim 1 further associated with a routing table for storing the failure indicator, the routing table coupled to the network element associated with the controller.

10. The controller according to claim 9, wherein the routing table includes protection switching information corresponding to respective ports associated with the respective network element.

11. The controller according to claim 9, wherein the routing table is defined when the working paths are established in the network.

12. The controller according to claim 11, wherein the protection switching information contained in the routing table is supplied by the controller.

13. The controller according to claim 9 further associated with a source element of the network elements for coordinating the establishment of protection switches corresponding to the protection switching information contained in the routing table.

14. The controller according to claim 13, wherein the failure indicator is used by the source element for a signaling message selected from the group comprising:

a switch request, an acknowledgement of a switch request, a negative acknowledgement of a switch request, a revert back to working request, and an acknowledgement of a revert back to working request.

15. The controller according to claim 9, wherein the first identity is a group number uniquely identifying a defined protection group and the second identity is a member number uniquely identifying a defined member of the protection group.

16. The controller according to claim 15, wherein the group number defines the protection path and the member number defines a corresponding one of the working paths.

17. The controller according to claim 16 further comprising the failure indicator including a pair of overhead bytes.

18. The controller according to claim 17, wherein the first byte of the pair of overhead bytes has the group number and the second byte of the pair of overhead bytes has the member number.

19. The controller according to claim 18, wherein the first byte is selected from one of a K1-K2 byte pair and the second byte is selected from the other one of the K1-K2 byte pair.

20. The controller according to claim 9, wherein the contents of the connection table are distributed in the network.

21. The controller according to claim 9, wherein the contents of the routing table are distributed in the network.

22. In an optical mesh network, a method for providing a 1:

N shared mesh protection system to define a protection path associated with N working paths, the method comprising the steps of;

a) interconnecting a plurality of network elements for providing the protection path and the working paths in a path layer of the network;

b) monitoring by a control layer the network traffic communicated in the path layer;

c) defining a connection table accessible by the control layer for containing connection information of the network elements associated with the protection path and working paths, the connection information including a first identity assigned to the protection path and a distinctive second identity assigned to each of the working paths;

d) providing a failure indicator having the first identity and the second identity related to a detected network failure of the corresponding working path to at least one of the network elements; and

e) inserting the failure indicator into an interrupt driven overhead byte of the network traffic for communication between the network elements;

wherein the failure indicator is communicated in the overhead byte of the network traffic to provide for the establishment of the associated protection path after the network failure has been detected in the corresponding working path.

23. The method according to claim 22, wherein the overhead byte location is selected from the group comprising:

a line overhead and a path overhead of the network traffic.

24. The method according to claim 23 further comprising the step of storing in the failure indicator the first identity as a group number uniquely identifying a defined protection group and the second identity as a member number uniquely identifying a member of the protection group.

25. The method according to claim 24 further comprising the step of defining the group number as the protection path and the member number as a corresponding one of the working paths.

26. The method according to claim 25 further comprising the step of defining the failure indicator as a pair of overhead bytes.

27. The method according to claim 26 further comprising the step of defining the first byte of the pair of overhead bytes as the group number and the second byte of the pair of overhead bytes as the member number.

28. The method according to claim 27, wherein the first byte is selected from one of a K1-K2 byte pair and the second byte is selected from the other one of the K1-K2 byte pair.

29. The method according to claim 25, wherein use of the overhead bytes provides for a protection switching time of less than 200 msec.

30. The method according to claim 24 further comprising the step of selecting a first one of the working paths to become a first member of the protection group and selecting a second working path to become a second member of the same selected group.

31. The method according to claim 23 further comprising the step of employing the failure indicator in a signaling message selected from the group comprising:

a switch request;

an acknowledgement of a switch request;

a negative acknowledgement of a switch request;

a revert back to working request; and

an acknowledgement of a revert back to working request.

32. The method according to claim 23 further comprising the step of providing a routing table for storing the failure indicator, the routing table coupled to at least one of the network elements.

33. The method according to claim 32 further comprising the step of storing protection switching information in the routing table corresponding to respective ports associated with the respective network element.

34. The method according to claim 32 further comprising the step of defining the routing table when the working paths are established in the network.

35. The method according to claim 34, wherein the protection switching information contained in the routing table is supplied by the control layer.

36. The method according to claim 35 further comprising the step of coordinating the establishment of protection switches corresponding to the protection switching information contained in the routing table.

37. The method according to claim 32 further comprising the step of storing in the failure indicator the first identity as a group number uniquely identifying a defined protection group and the second identity as a member number uniquely identifying a member of the protection group.

38. The method according to claim 37 further comprising the step of defining the group number as the protection path and the member number as a corresponding one of the working paths.

39. The method according to claim 38 further comprising the step of defining the failure indicator as a pair of overhead bytes.

40. The method according to claim 39, wherein the first byte is selected from one of a K1-K2 byte pair and the second byte is selected from the other one of the K1-K2 byte pair.

41. The method according to claim 37, wherein the selection of the first and second working paths is associated with the step of defining of the connection table.

42. The method according to claim 32 further comprising the step of configuring a protection switch corresponding to the protection switching information included in the network elements.

43. The method according to claim 32 further comprising the step of detecting the network failure.

44. The method according to claim 43 further comprising the step of accessing the routing table and inserting the failure indicator into the overhead byte for transmission over the network.

45. The method according to claim 44 further comprising the step of receiving an acknowledgement pertaining to the overhead byte message for indicating the suitability of the protection path.

46. The method according to claim 45 further comprising the step of establishing the protection path for subsequent routing of the network traffic over the protection path.

47. The method according to claim 45 further comprising the step of submitting an alarm indicating a message failure of a protection path request in the event of a time out.

48. The method according to claim 45 further comprising the step of selecting an alternate protection path in the event of not receiving an acknowledgement of the transmitted overhead byte transmission.

49. In an optical mesh network, a computer program product for providing a 1:

N shared mesh protection system to define a protection path associated with N working paths, the product comprising;

a) computer readable medium;

b) a first link module stored on the computer readable medium for connecting a controller to a control layer of the network to monitor network traffic communicated in a path layer of the network;

c) a second link module coupled to the first link layer module for connecting the controller to the path layer of the network, the path layer including a plurality of interconnected network elements for providing the associated protection path and working paths;

d) a connection table module coupled to the first link module accessible by the controller, the connection table module for having connection information of the network elements associated with the protection path and the working paths, the connection information including a first identity assignable to the protection path and a distinctive second identity assignable to each of the working paths; and

e) a failure indicator module coupled to the connection table module for providing the first identity and the second identity relatable to a network failure of the corresponding working path to at least one of the network elements associated with the controller, the failure indicator module for inserting a failure message into an interrupt driven overhead byte of the network traffic for communication between the network elements;

wherein the failure message is communicated in the overhead byte of the network traffic to provide for the establishment of the associated protection path after the network failure has been detected in the corresponding working path.

50. A network element for providing an indication of a network failure in an optical mesh network, the network having a 1:

N shared mesh protection system to define a protection path associated with N working paths, the network element comprising;

a) a link for connecting the network element to a path layer of the network, the path layer including a plurality of interconnected elements for providing the associated protection path and working paths;

b) a routing table accessible by the network element, the routing table having routing information associated with the protection path and the working path;

c) a first identity assignable to the protection path and a distinctive second identity assignable to each of the working paths, the identities associated with the routing information; and

d) a failure indicator for providing the first identity and the second identity relatable to a network failure of the corresponding working path to at least one of the interconnected elements, the failure indicator for insertion into an interrupt driven overhead byte of network traffic transmitted over the mesh network for communication between the interconnected elements;

wherein the failure indicator is communicated in the overhead byte of the network traffic to help initiate the establishment of the associated protection path after the network failure has been detected in the corresponding working path.