A method of restoring communication between at least one pair of nodes in a network having a plurality of nodes and a plurality of links interconnecting the nodes, comprising the steps of: (1) sending null messages between adjacent nodes on working and spare links, wherein said null messages comprise a transmitting node ID field and a link ID field; (2) receiving, in at least a first node, a signal-that indicates an alarm in a link between said first node and a second node; (3) starting an alarm validation timer and a holdoff timer, wherein said holdoff timer prevents link restoration due to short-duration hits; (4) inserting by said first node an incoming signal failure (ISF) signal downstream from said link to quiet downstream links in alarm; (5) validating said alarm if said alarm persists through said alarm validation timer; (6) identifying a sender node and a chooser node based on an arbitration between said first node and said second node adjacent to said link; (7) sending by said sender node a flooding message, comprising a sender node ID field, an index field, a chooser node ID field and a hop count field, on one spare link on each logical span between said sender node and any of the plurality of nodes in the network connected to said sender node; (8) after said alarm is validated, starting by said sender node a preactivation timer; (9) after said sender node sends said flooding message on at least one logical span, starting a sender time-out timer; (10) starting by said chooser node a chooser timer for each received flooding message having a unique combination of values in said sender node ID field, said index field and said chooser node ID field; (11) after said chooser timer has expired for a unique received flooding message, selecting by said chooser node a shortest restoration route and sending a reverse linking message on said shortest restoration route, wherein said reverse linking message comprises a sender node ID field, an index field, and a chooser node ID field; (12) identifying by said sender node a link restoration route based on a received reverse linking message; (13) sending by said sender node release messages on all other spare links separate from said link restoration route; (14) after said holdoff timer expires, sending by said sender node a connect message to said chooser node, wherein said connect message comprises a restore from field that identifies said link to said chooser node for correct cross connection; and (15) after said preactivation timer expires, releasing by said sender node any reserved and unused restoration routes.
›2.↳ 1The method of claim 1, wherein said steps (1), (4), (7), (11), (13), (14) and (15) comprise the step of encapsulating messages in the Link Access Prot…d2
The method of claim 1, wherein said steps (1), (4), (7), (11), (13), (14) and (15) comprise the step of encapsulating messages in the Link Access Protocol-D (LAP-D) frame for transport to adjacent nodes.
›3.↳ 1The method of claim 1, wherein said steps (1), (4), (7), (11), (13), (14) and (15) comprise the step of sending messages in a single STS-1 time slot i…d2
The method of claim 1, wherein said steps (1), (4), (7), (11), (13), (14) and (15) comprise the step of sending messages in a single STS-1 time slot in an OC-N link.
›4.↳ 1The method of claim 1, wherein said step (1) comprises the step of sending null messages that comprise a transmitting node ID field, a link ID field, …d2
The method of claim 1, wherein said step (1) comprises the step of sending null messages that comprise a transmitting node ID field, a link ID field, a message type field, a port type field, a link inhibit field, a far end not connected field, a return alarm field, a software revision field, and a exerciser return alarm field.
›5.↳ 1The method of claim 1, wherein said step (1) comprises the step of sending null messages immediately upon a state change and periodically thereafter.d2
The method of claim 1, wherein said step (1) comprises the step of sending null messages immediately upon a state change and periodically thereafter.
›6.↳ 1The method of claim 1, further comprising the step of converting said ISF signal back to an alarm indication signal (AIS) at access/egress ports befor…d2
The method of claim 1, further comprising the step of converting said ISF signal back to an alarm indication signal (AIS) at access/egress ports before said ISF signal leaves the network.
›7.↳ 1The method of claim 1, wherein said step (4) comprises the step of starting an alarm validation timer upon receipt of all STS-Path AISs for said link,…d2
The method of claim 1, wherein said step (4) comprises the step of starting an alarm validation timer upon receipt of all STS-Path AISs for said link, an OC-N loss of signal (LOS), or loss of frame (LOF).
›8.↳ 1The method of claim 1, wherein said step (6) comprises the following steps that are performed by said first node: (a) identifying a node ID for said s…d2
The method of claim 1, wherein said step (6) comprises the following steps that are performed by said first node: (a) identifying a node ID for said second node based on said transmitting node ID field of said null messages; (b) assuming a sender role if said node ID for said second node is smaller then said node ID of said first node, otherwise, said first node assuming a chooser role.
›9.↳ 1The method of claim 1, wherein said step (7) comprises the step of sending a flooding message, comprising a message type field, a sender node ID field…d2
The method of claim 1, wherein said step (7) comprises the step of sending a flooding message, comprising a message type field, a sender node ID field, an index field, a chooser node ID field and a hop count field, on one spare link on each logical span between said sender node and any of the plurality of nodes in the network.
›10.↳ 1The method of claim 1, further comprising the step of said sender node queuing said flooding message if another sender node has sent flooding messages…d2
The method of claim 1, further comprising the step of said sender node queuing said flooding message if another sender node has sent flooding messages on all of said sender node's spare links.
›11.↳ 1The method of claim 1, wherein said step (11) comprises the step of sending a reverse linking message that comprises a message type field, a sender no…d2
The method of claim 1, wherein said step (11) comprises the step of sending a reverse linking message that comprises a message type field, a sender node ID field, an index field, and a chooser node ID field.
›12.↳ 1The method of claim 1, wherein said step (11) comprises the steps of: (a) after said chooser timer has expired, said chooser node selecting said short…d2
The method of claim 1, wherein said step (11) comprises the steps of: (a) after said chooser timer has expired, said chooser node selecting said shortest restoration route based on the received flooding message having the lowest value in said hop count field; and (b) sending said reverse linking message out on the port that received the flooding message having the lowest hop count value.
›13.↳ 1The method of claim 1, further comprising the steps of: (16) receiving one of said flooding messages at a tandem node; (17) said tandem node multicast…d2+1
The method of claim 1, further comprising the steps of: (16) receiving one of said flooding messages at a tandem node; (17) said tandem node multicasting said flooding message into one spare link in all spans except: i) the span that received said flooding message, ii) spans that have already been flooded with another flooding message having the same index, and (iii) spans directly connected to said sender node; (18) decrementing the value in said hop count field by one.
›14.↳ 13The method of claim 13, wherein said step (17) further comprises the step of sending said flooding message into spare links that have not received a f…d3
The method of claim 13, wherein said step (17) further comprises the step of sending said flooding message into spare links that have not received a flooding message.
›15.↳ 1The method of claim 1, further comprising the steps of: (16) receiving one of said reverse linking messages on a first port; (17) associating said rec…d2
The method of claim 1, further comprising the steps of: (16) receiving one of said reverse linking messages on a first port; (17) associating said received reverse linking message with a complimentary flooding message, wherein a flooding message and a reverse linking message are complimentary if said index field, said sender ID field and said chooser ID field are the same; (18) forwarding said reverse linking message to a second port that received said complimentary flooding message; (19) cross connecting said first port and said second port; and (20) replacing multicasted copies of flooding messages having the same index with release messages.
›16.↳ 1The method of claim 1, further comprising the step of labeling unrestored links as unrestored outstanding aim if said sender time-out timer expires pr…d2
The method of claim 1, further comprising the step of labeling unrestored links as unrestored outstanding aim if said sender time-out timer expires prior to the receipt of any of said reverse linking messages.
›17.↳ 1The method of claim 1, further comprising the steps of: (16) starting a drop dead timer in said sender node and said chooser node upon detection of a …d2
The method of claim 1, further comprising the steps of: (16) starting a drop dead timer in said sender node and said chooser node upon detection of a failure in said link; and (17) starting a drop dead timer in a tandem node upon first receipt of a flooding message.
›18.↳ 1The method of claim 1, wherein said step (14) comprises the step of including the value of said link ID field in a previously received null message in…d2
The method of claim 1, wherein said step (14) comprises the step of including the value of said link ID field in a previously received null message into said restore from field.
