Distributed protocol for improving the survivability of telecommunications trunk networks

• US 5,093,824 A
• Filed: 03/27/1990
• Issued: 03/03/1992
• Est. Priority Date: 03/27/1990
• Status: Expired due to Term

• Current Assignee: TTI Inventions A LLC (Intellectual Ventures LLC)
• Original Assignee: Bell Communications Research, Inc. (Telefonaktiebolaget LM Ericsson)
• Inventors: Coan, Brian A., Vecchi, Mario P., Wu, Liang T.
• Primary Examiner(s): Olms, Douglas W.
• Assistant Examiner(s): Jung, Min
• Application Number:
  US07/499,881
• Time in Patent Office: 707 Days
• Field of Search: 370/16, 370/14, 370/60, 370/58.1, 371/11.1, 371/20.1, 371/26, 371/11.2
• US Class Current: 370/228
• CPC Class Codes: H04J 2203/0042 Ring
• 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
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04Q 2213/13141 Hunting for free outlet, circuit or channel
• CPC Class Codes: H04Q 2213/13167 Redundant apparatus
• CPC Class Codes: H04Q 2213/13396 Signaling in general, in-band signalling
• CPC Class Codes: H04Q 3/0016 Arrangements providing connection between exchanges
• CPC Class Codes: H04Q 3/0079 involving restoration of networks, e.g. disaster recovery, self-healing networks

Abstract

A method for reconfiguring a telecommunications network comprising a plurality of reconfigurable cross-connect nodes interconnected by links when a failure event occurs is disclosed. The method comprises storing at each node a precomputed configuration table corresponding to each of a plurality of possible network topologies which can result from a plurality of possible failure events. After a specific failure event occurs, the network is flooded with messages so that each of the nodes is informed as to the specific existing topology of the network resulting from the specific failure event. The nodes are then reconfigurated in accordance with the precomputed configuration tables which correspond to the specific existing network topology.

Claims

1. A method for reconfiguring a telecommunications network comprising a plurality of reconfigurable cross-connect nodes interconnected by links when a failure event occurs, said method comprising the steps of

storing at each node a precomputed configuration table corresponding to each of a plurality of possible network topologies which result from a plurality of possible failure events,

after a specific failure event occurs, flooding the network with messages by sending from node to node messages of the specific failure event generated by the node detecting the specific failure event so that each of the nodes is informed as to the specific existing topology of the network which results from the specific failure event and such that the network nodes converge to a consistent and correct picture of the existing network topology, and

reconfiguring the nodes in accordance with the specific precomputed configuration tables which correspond to the specific existing network topology, wherein reconfiguration of the telecommunication network is accomplished without the use of a separate central network controller.

2. The method of claim 1 wherein said storing step comprises storing at each node a precomputed configuration table for each possible single link failure.

3. The method of claim 2 wherein, when there is a specific single link failure event, said reconfiguring step comprises reconfiguring the nodes in accordance with the precomputed configuration tables corresponding to the specific single link failure event.

4. The method of claim 2 wherein, when there is a failure event involving more than a single link, said reconfiguring step comprises installing at each node one of said single link failure configuration tables in accordance with a consistent rule followed at all of said nodes.

5. The method of claim 4 wherein all of said links in said network have identification numbers, and wherein said consistent rule followed at all of said nodes comprises installing at each node the single link failure configuration table for the failed link having the highest number.

6. The method of claim 1 wherein said storing step comprises storing at each node a precomputed configuration table for each possible single link failure and a precomputed configuration table for the most probable multiple link failures.

7. The method of claim 1 wherein said network is configured initially so there are particular logical connections established in said network, and wherein said configuration tables are computed to maintain said logical connections when corresponding failure events occur.

8. The method of claim 1 wherein said specific failure event comprises failure of one of said nodes.

9. A protocol carried out at each node in a network comprising a plurality of reconfigurable cross-connect nodes interconnected by links to reconfigure the network in the event of a failure event, said protocol comprising the steps of:

at each node, maintaining an array indicating the status of all of the links in the network,

at each node, storing a plurality of predetermined configuration tables corresponding to a plurality of possible patterns of non-working links,

at each node, sequentially testing all of the links associated with the node which are indicated by the array to be working,

if a specific link is determined as a result of the testing step to be non-working, updating the array, sending a message on all links associated with the node indicating that the specific link is non-working, and reconfiguring the node in accordance with the predetermined configuration table corresponding to the pattern of non-working links indicated by the updated array if the node is not already in this configuration,

if a specific link is determined as a result of the testing step to be working, determining if a message has been received via the specific link indicating that another link in the network is non-working and,

if a message has been received via the specific link indicating that another link in the network is non-working and the array does not already indicate that the other link is non-working, updating the array, sending a message on all links associated with the node indicating that the other link is non-working, and reconfiguring the node in accordance with the predetermined configuration table corresponding to the pattern of non-working links indicated by the updated array if the node is not already in this configuration.

10. A protocol carried out continuously at each node in a network comprising a plurality of reconfigurable cross-connect nodes interconnected by links, said protocol comprising the steps of

(a) at each node, sequentially testing all of the links associated with the node which are indicated by a link status array to be working,

(b) if a specific link is determined as a result of said testing step to be non-working, updating the link status array, sending a message on the working links associated with the node that the specific link is non-working, and reconfiguring the node in accordance with a prestored configuration table corresponding to the particular pattern of non-working links indicated by the updated link status array, and

(c) if a specific link is determined as a result of the testing step to be working and a message has been received via the specific link indicating that another link in the network is non-working and the link status array does not already indicate that the other link is non-working, sending a message on the working links associated with the node indicating that the other link is non-working, updating the link status array at the node, and reconfiguring the node in accordance with a prestored configuration table corresponding to the particular pattern of non-working links indicated by the updated link status array.

11. A method of reconfiguring a telecommunications network to maintain a set of logical connections defined in said network in the event of a failure of a component in said network, said method comprising

storing at each node in said network a precomputed configuration table corresponding to each of a plurality of possible network component failures,

after a specific failure of one or more network components, flooding the network with messages by sending from node to node messages of the failure events generated by the nodes detecting the specific failure events so that each of the nodes is informed of the specific failure and the network nodes converge to a consistent and correct picture of the existing network topology, and

reconfiguring the nodes in accordance with the specific precomputed configuration tables corresponding to the specific failure to maintain said set of logical connections.

12. The method of claim 11 wherein said specific failure comprises the failure of a link of said network.

13. The method of claim 11 wherein said specific failure comprises the failure of a node of said network.

14. A method for reconfiguring a telecommunications network comprising a plurality of reconfigurable cross-connect nodes interconnected by links when a failure event occurs, said method comprising the step of

storing at each node a precomputed configuration table corresponding to each of a plurality of possible network topologies which result from a plurality of possible failure events,

after a specific failure event occurs, detecting the specific failure event at a node,

generating messages of the failure event from the node detecting the failure event over the links associated with said detecting node to other nodes connected to said detecting node by associated links,

sending from node to node the messages generated in said generating step such that the network nodes converge to a consistent and correct picture of the existing network topology, and

reconfiguring the nodes in accordance with the specific precomputed configuration tables which correspond to the specific existing network topology.