US5182744A - Telecommunications network restoration architecture - Google Patents

Telecommunications network restoration architecture Download PDF

Info

Publication number
US5182744A
US5182744A US07/637,244 US63724491A US5182744A US 5182744 A US5182744 A US 5182744A US 63724491 A US63724491 A US 63724491A US 5182744 A US5182744 A US 5182744A
Authority
US
United States
Prior art keywords
nodes
links
connectivity
traffic
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US07/637,244
Inventor
James D. Askew
Chin-Wang Chao
David R. Cochran
Peter M. Dollard
Hossein Eslambolchi
William E. Goodson
Robert P. Guenther
Omar M. Mansour
Liem T. Nguyen
Sarma S. Tanuku
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Bell Labs
AT&T Corp
Original Assignee
AT&T Bell Laboratories Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by AT&T Bell Laboratories Inc filed Critical AT&T Bell Laboratories Inc
Priority to US07/637,244 priority Critical patent/US5182744A/en
Assigned to AMERICAN TELEPHONE AND TELEGRAPH COMPANY, A CORP. OF NY reassignment AMERICAN TELEPHONE AND TELEGRAPH COMPANY, A CORP. OF NY ASSIGNMENT OF ASSIGNORS INTEREST. Assignors: CHAO, CHIN-WANG, COCHRAN, DAVID R., DOLLARD, PETER M., ESLAMBOLCHI, HOSSEIN, GOODSON, WILLIAM E., GUENTHER, ROBERT P., MANSOUR, OMAR M., NGUYEN, LIEM T., TANUKU, SARMA S., ASKEW, JAMES D.
Priority to CA002056298A priority patent/CA2056298C/en
Priority to DE69131041T priority patent/DE69131041T2/en
Priority to EP91311482A priority patent/EP0494513B1/en
Priority to ES91311482T priority patent/ES2130134T3/en
Priority to AT91311482T priority patent/ATE178177T1/en
Priority to AU89690/91A priority patent/AU626226B1/en
Priority to KR1019910024116A priority patent/KR960007668B1/en
Priority to JP3358238A priority patent/JP3009769B2/en
Publication of US5182744A publication Critical patent/US5182744A/en
Application granted granted Critical
Priority to HK98112771A priority patent/HK1011810A1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/64Distributing or queueing
    • H04Q3/66Traffic distributors
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/0016Arrangements providing connection between exchanges
    • H04Q3/0062Provisions for network management
    • H04Q3/0075Fault management techniques
    • H04Q3/0079Fault management techniques involving restoration of networks, e.g. disaster recovery, self-healing networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13141Hunting for free outlet, circuit or channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13164Traffic (registration, measurement,...)
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13166Fault prevention
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13332Broadband, CATV, dynamic bandwidth allocation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q2213/00Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13353Routing table, map memory

Definitions

  • the invention relates to telecommunications networks, and more particularly relates to a network architecture which automatically routes traffic in the event of a network failure.
  • a disruption in telecommunications services in a network is typically caused by an inoperable communications path (link) or equipment within a service providing office (node).
  • a disruption of such services could be very costly to business users who rely on telecommunications services in the operation of their businesses. For example, a particular business could lose revenue as a result of a failure to receive so-called "telemarketing sales" when a disruption in telecommunications services occurs. Moreover, the amount of such lost revenue would be directly proportional to the duration of the disruption. The provider of such telecommunications services would also lose revenue, since the disruption would decrease the number of calls that the associated network could process.
  • the length of the duration is typically based on a number of factors, such as, for example, (a) the amount of time required to identify the location of the service disruption; (b) the amount of time that is used to identify one or more routes that could be used to alternate route affected traffic around the service disruption; and (c) the amount of time that is used to actually establish such routes.
  • Most telecommunications networks typically deal with a service disruption by selecting an alternate route around the inoperable link or service providing node.
  • One goal in doing so is to select the most efficient alternate route, one having the least number of nodes and links.
  • An advance in telecommunications switching is obtained by providing a service restoration facility which quickly locates and deals with a fault such that an interruption in communications services that is caused by the fault is virtually transparent to subscribers.
  • Such restoration is achieved, in accord with the invention, by providing at each service node automatic cross-connect means for terminating the end points of communication links entering and leaving the service node, monitoring the operability of each such link and node to quickly identify a service disruption, and notifying a central facility when such a disruption occurs.
  • the central facility locates spare circuits in individual ones of the links and then establishes, in real time, one or more orders of connectivity (alternate routes) for the rerouting of traffic affected by the interruption, in which the continuity of each such order of connectivity is confirmed before the affected traffic is transferred thereto.
  • FIG. 1 is a broad diagram of a telecommunications network comprising a plurality of nodes and links interconnecting individual pairs of such nodes;
  • FIG. 2 illustrates a table for tracking the spare capacity in individual ones of the links shown in FIG. 1;
  • FIG. 3 is a broad block diagram of a node of FIG. 1 including the inventive service restoration architecture
  • FIGS. 4 and 5 are flow charts of the software which implements the invention in an alarm processor of FIG. 3;
  • FIG. 6 is a flow chart of the software which implements the invention in a central controller of FIG. 3.
  • FIG. 1 there is shown a simplified diagram of a telecommunications network 200, which may be, for example, the AT&T digital network, comprising a plurality of nodes.
  • a telecommunications network 200 which may be, for example, the AT&T digital network, comprising a plurality of nodes.
  • Each such node includes, inter alia, what is commonly referred to as a Digital Cross-connect Arrangement (DCA) of the type known in the art.
  • DCA Digital Cross-connect Arrangement
  • One exemplary arrangement which may be advantageously employed as a DCA is the Digital Access and Cross-Connect System III commercially available from AT&T.
  • service nodes 100-1 through 100-9 are interconnected via respective ones of the links 101 through 111.
  • Such links may be, for example, optical fiber cables.
  • the respective end points of a link e.g., link 103
  • the termination circuitry includes so-called Line Termination Equipment (LTE) designed to interface optical fibers with a DCA.
  • LTE Line Termination Equipment
  • a DCA cross-connects signals that are transported via optical fibers (or other broadband digital transport systems) that are in service, and thereby determines the routing of such signals.
  • a signal received via one link may then be electronically cross-connected (routed) to one of a number of other links also connecting via an LTE to the DCA, in which the cross-connection is based on the destination of the signal, and in which the destination may be the associated node itself or one of the other network nodes.
  • a DCA for example, the DCA contained in node 100-1, operates as a conduit for routing signals from an originating node, for example, node 100-1, to a terminating node, for example, node 100-5.
  • the optical fibers forming a link terminate on an LTE.
  • an LTE may be, for example, the well-known FT series G lightwave system commercially available from AT&T.
  • the FT series G lightwave system is a high-capacity, digital optical-transport system that provides maintenance options and other features such as wavelength and time division multiplexing.
  • a multiplexed group of DS3 signals received via an optical fiber and entering a FT series G terminal is first resynchronized and demultiplexed from the line rate and then supplied individually to the DCA at the DS3 rate so that they may be switched to an appropriate outgoing fiber, or line.
  • an FT series G terminal monitors such signals to track errors as they occur, in which such errors include, for example, framing and synchronization errors.
  • errors include, for example, framing and synchronization errors.
  • a loss of synchronization is typically indicative of fiber failure, e.g., a fiber which has been inadvertently cut.
  • Each node also includes an alarm processor, which monitors key components of its associated node, such as the associated LTE equipment. That is, the alarm processor periodically polls, for example, once a second, the associated LTE equipment for alarms that occurred during a preceding period, in which such alarms are indicative of, for example, the aforementioned framing and synchronization errors. Upon receipt of an alarm, the alarm processor initiates a so-called “leaky bucket” process to track whether the alarm is indicative of either an intermittent or a persistent (hard) fault.
  • the alarm processor increments an associated alarm counter by a predetermined value--illustratively two--and decrements that counter by another predetermined value--illustratively one--at the end of each successive polling session during which no alarm is received.
  • the associated counter would be decremented to a value of zero after the second successive polling session.
  • the value contained in the counter will reach a predetermined threshold value--illustratively 10--within a short period of time.
  • the threshold is adapted downward so that such a failure may be recognized quickly.
  • the alarm processor sends to an associated central controller a message identifying the associated alarm and the failed DS3 circuit.
  • the central controller starts a window timer to await for possible receipt of messages identifying other failed DS3 circuits. That is, if an alarm is indicative of a cable which has been inadvertently cut, then, during the window, the central controller accumulates a list of all of the DS3 circuits contained in the optical fibers which have failed as result of the cut cable.
  • the associated node will activate such spares and transfer the traffic affected by the failed DS3 circuits thereto.
  • the alarm processor notifies the central controller.
  • the central controller responsive to such notification invokes a program implementing a service restoration algorithm which alternate routes traffic that is affected by the failed cable.
  • Such a restoration algorithm although not pertinent to the present invention, could be one that is based on the notion of "knowing" such alternate routes beforehand.
  • the restoration algorithm could be one in which such alternate routes are not known beforehand and are thus established “on the fly”.
  • the restoration algorithm is designed to locate spare DS3 circuits that may be contained in other links, which are then placed in service to establish one or more alternate routes for the rerouting of the affected traffic.
  • One such restoration scheme is disclosed in copending U.S. patent application Ser. No. 504,359, filed on Apr. 4, 1990 on behalf of M. O. Mansour et al.
  • the central controller identifies such alternate routes by (a) determining the identity of the failure-end offices, which in the present example, would be nodes 100-2 and 100-3; (b) then determining in real time the least number of links and associated (intermediate) nodes that may be used to establish a possible loop whose end points terminate at the failure-end offices; (c) then determining the identity of each so-called transfer-end node; and (d) then determining the identities of the intermediate nodes that would be used to establish the loop.
  • each link in the network as well as the identities of the nodes connecting thereto is maintained in a link table, an example of which is shown in FIG. 2.
  • each line of TABLE 1 identifies a respective network link and identifies the nodes which connect to the end points thereof.
  • the last column of TABLE 1 (S-CAP) identifies the number of available spare DS3 circuits in the identified link, in which the number of spare DS3 circuits for a given link is updated as such spares are placed in and out of service, or become faulty, in accordance with status messages received from respective alarm processors. Accordingly, then, it is a simple matter to index TABLE 1 and read out the identities of the failed end offices which connect to respective end points of link 103, which in the present case happen to be nodes 100-2 and 100-3, as shown at line 202.
  • the central controller identifies the shortest loop around the failed link. This is done by mapping, in real time and in the form of a tree-like structure, various paths contained in Table 1, in which the paths begin at one of the failure-end nodes, e.g., node 100-2 and lead to the other failure-end node, e.g., node 100-3.
  • the path which is first to lead (terminate) at node 100-3 is then selected as being the shortest loop around failed link 103.
  • the arrangement determines from lines 202 and 208 that node 100-2 connects to nodes 100-1 and 100-7 via links 102 and 108, respectively, and forms the first level of the tree.
  • the arrangement determines from TABLE 1 (line 207) that node 100-7 connects to node 100-8 via link 109.
  • the arrangement proceeds in a similar manner for node 100-1, and continues building the tree in the manner just described.
  • the central controller terminates the process when one of the paths of the tree is first to reach node 100-3, as shown for the path comprising nodes 100-1, 100-6, 100-4 and links 102, 106, 107 and 104.
  • the first path of the tree which reaches node 100-3 will be the shortest path around the failed link.
  • the central controller then identifies the transfer-end nodes by noting which nodes are contained in both the failed path (i.e., nodes 100-1, 100-2, 100-3 100-4), and the shortest loop (i.e., nodes 100-2, 100-1, 100-6, 100-4 and 100-3).
  • nodes 100-1 and 100-4 would be the transfer-end nodes since they are common to both paths.
  • the arrangement then identifies the intermediate nodes by noting which nodes are contained in the shortest loop between the transfer-end nodes but not in the original path. As such, node 106 would be identified as being the intermediate node. (It is noted that the shortest loop is defined herein as being the first order of connectivity around the failed link, i.e., a connectivity comprising the fewest number of links.)
  • the central controller has identified loop 150 comprising nodes 100-2, 100-1, 100-6, 100-4 and 100-3 and links 106 and 107 as the shortest and most efficient alternate route for rerouting the original traffic around inoperable link 103.
  • each intermediate node e.g., node 100-6 a set of commands causing the DCA contained in that node to cross-connect the spare capacity of link 106 to the spare capacity of link 107 in order to extend the new path defining the alternate route.
  • Each such command comprises a number of fields specifying the order of switching signals to so-called ports on the DCA of node 100-6 which terminate the ends of spare DS3 circuits of link 106 to the ends of the spare DS3 circuits of link 107.
  • the central controller then sends to the DCA at transfer-end node 100-4 a set of commands directing the order of cross-connecting between the ports which terminate the opposite ends of the spare DS3 circuits of link 107 to the ports terminating the DS3s of link 105 which transported the original traffic.
  • the central controller then sends to the DCA of node 100-1 a set of commands directing the order of cross-connecting between the ports terminating the failed DS3s of link 101 and ports terminating the ends of the spare DS3s of link 106 connecting to node 100-1.
  • loop 151 comprising nodes 100-7 through 100-9 and node 100-4 and links 108 through 111.
  • the inventive architecture quickly deals with a service disruption or a degradation in service, thereby making such a disruption nearly transparent to the network user.
  • node 100-N generally represents any one of the nodes forming network 200 and includes DCA 30, alarm processor 40, satellite antenna interface (SAI) 50 for interfacing DCA 30 and processor 40 with antenna 55, and data switch 60 for interfacing DCA 30 and processor 40 with data network 90.
  • SAI satellite antenna interface
  • DCA 30 may be the Digital Access and Cross-Connect system III available from AT&T.
  • Optical fiber cables 10-1 through 10-N represent any one of the links, e.g., links 102, 103, 104, etc., which forms network 200.
  • Each of the DS3 circuits multiplexed on the optical fibers forming cables 10-1 through 10-N connects to a respective port of DCA 30 via one of the LTE 20-1 through 20-N.
  • each LTE is also arranged to monitor the operability and status (in or out of service) of the aforementioned DS3 circuits terminating thereat and, when polled by processor 40, report, via a respective one of the communications busses 41-1 through 41-N, the status of such operability.
  • processor 40 in response to receipt of an alarm, processor 40 initiates a so-called “leaky bucket” process to determine if the associated fault is either an intermittent or persistent (“hard") fault. If processor 40, which may be, for example, the 68000 DELTA series computer available from Motorola, Inc., determines that an alarm might be due to a hard fault, then it sends to central controller (operations system) 300 via bus 42, SAI 50, dish antenna 55 and satellite 56 a report indicative of that fact. (Satellite 56, may be, for example, the well-known AT&T Skynet satellite communications service.) Such a report is formed into a message using the well-known X.25 message protocol resulting in so-called base-band signals representing the data conveyed by the report.
  • processor 40 which may be, for example, the 68000 DELTA series computer available from Motorola, Inc., determines that an alarm might be due to a hard fault, then it sends to central controller (operations system) 300 via bus 42, SAI 50, dish antenna 55 and satellite 56
  • SAI 50 which may be, for example, the Indoor Unit (IDU) available from the Tridom Corporation, modulates such baseband signals using an intermediate frequency (IF) carrier and then modulates the result using a radio frequency (RF) carrier in KU band for presentation to dish antenna 55.
  • IF intermediate frequency
  • RF radio frequency
  • Dish antenna 55 transmits the modulated signals to satellite 56, which then retransmits the signals for receipt by dish antenna 57 connected to SAI 75.
  • SAI 75 which is similar to SAI 50, demodulates the signals and supplies to processor 70 of central controller 300 the resulting processor 40 message.
  • processor 40 may transmit such a message via data network 90, which may be, for example, the AT&T Accunet packet network.
  • processor 40 (or DCA 30) interfaces with network 90 via X.25 data switch 60 comprising a number of data modules such as, for example, data modules models 3001-201 and 2003-001 as well as driving software identified by model number 3709-201 available from the Telematics Corporation.
  • processor 40 supplies the message to data switch 60 for retransmission to processor 70 via network 90.
  • Processor 70 monitors network, or data bus, 90 for messages bearing its address, and removes such message from the bus as they are received.
  • messages may be exchanged with processor 70 via either one of two diverse paths, i.e., satellite or terrestrial.
  • processor 70 Upon receipt of the message, processor 70, which may be, for example, the Hewlett Packard Co. Model 9000-860 computer, updates TABLE 1 of FIG. 2 contained in associated memory (not shown). Processor 70 also updates other such tables (not shown) that are designed to track the status of fibers that are in service. In addition, processor 70, responsive to receipt of a node processor 40 message identifying an inoperable link or a degraded link, invokes the program that is designed to locate spare capacity in order to establish one or more orders of connectivity so that the affected original traffic may be restored to service. As mentioned above, such a restoration algorithm or program could be, for example, the program disclosed in the aforementioned Mansour et al patent application, discussed above.
  • the program When the program locates such capacity, it then sends messages to each DCA that would be involved in establishing such connectivity, as mentioned above. That is, the program supplies to SAI 75 for transmission to a particular DCA a connectivity message, in which the message includes in a header the identity of the DCA and associated node.
  • SAI 75 (which is similar to SAI 50), in turn, modulates, in the manner described above, the signals forming the connectivity message and supplies the result to antenna 57 for transmission to satellite 56. Satellite 56 retransmits the connectivity message, which is received by each of the network nodes via their respective antennas. However, the message is accepted only by that SAI 50 whose associated network node address is contained in the message.
  • the SAI 50 then passes the message to its associated DCA via bus 31 so that the latter may order its switching scheme to establish a portion of the desired restoration loop (alternate route).
  • connectivity messages may be transported via network 90, as mentioned above.
  • processor 70 sends to each processor 40 disposed at respective transfer-end points of a newly established alternate route, one or more messages requesting the processor 40 to confirm the continuity of the established alternate route. If the testing of the alternate route confirms such continuity, then the affected traffic is switched to the alternate route. If the test does not confirm such continuity, then processor 40 sends to processor 70 a message indicative of that fact. Processor 70, in turn, outputs to a terminal a modified version of the received message.
  • a craftperson positioned at the terminal may then direct processor 70 to (a) "dismantle" the established alternate route, (b) search for another alternate route in the manner described above, (c) establish, in the manner described above, the latter alternate route, if available, and (d) request processor 40 to test the continuity of the newly established route. If processor 70 finds that an alternate route is not available, then it outputs to the terminal (not shown) a message indicative of that fact.
  • Processor 40 performs such continuity testing by sending to its associated DCA 30 connectivity messages to establish a test access path to confirm the continuity of a newly established DS3 circuit.
  • processor 40 causes its associated restoration test equipment (RTE) 45 to send over one direction of the newly established circuit test signals defining, inter alia, an identity code, e.g., the identity of DS3 circuit that is being tested.
  • RTE restoration test equipment
  • An RTE 45 disposed at the opposite end of the alternate route established by that circuit and responsive to receipt of the test signals compares the received identity code with a code received from processor 70. If the comparison is found to be true, then the receiving RTE 45 returns an acknowledgement signal.
  • the RTE 45 which sent the test signals Upon receipt of that signal, the RTE 45 which sent the test signals, in turn, notifies, its associated processor 40, which, in turn, notifies processor 70.
  • the RTE 45 disposed at the opposite transfer end point performs a continuity test on the same DS3 circuit in a similar manner, but in the opposite direction.
  • processor 70 sends to the pertinent processor 40, via the aforementioned transmission path, a message to transfer the affected traffic to the newly established alternate route.
  • each RTE 45 which may be, for example, the model 8186 microcomputer commercially available from Intel Corp., connects to a number of DCA 30 port circuits--illustratively fourteen port circuits--via respective communications paths 47-1 through 47-N.
  • an RTE 45 operating in conjunction with an RTE 45 disposed at the opposite end of a newly established alternate route and at the direction of their respective processor 40 may test simultaneously the continuity of fourteen DS3 circuits. That is, responsive to receipt of an appropriate message from processor 70, processor 40 sends to DCA 30 via bus 44 a message designed to cause DCA 30 to establish a cross-connection between a DS3 circuit that is to be tested and one of the RTE 45 ports 47-1 through 47-N.
  • Processor 70 then sends to RTE 45 via processor 40 a message requesting that a continuity test be performed over the selected one of the port, 47-1 through 47-N, in which the message includes the aforementioned identity code.
  • RTE 45 returns to processor 40 via bus 46 the results of the test.
  • processor 40 at the direction of controller 70 may direct RTE 45 to verify a failure. That is, processor 40 may cause RTE 45 to be bridged via one of its connections 47-1 through 47-N onto a DCA 30 circuit for the purpose of determining whether the circuit has indeed failed. If the circuit has failed, then, an upstream node will transmit over the DS3 circuit a so-called alarm indication signal. Thus, the presence of that signal, the presence of a signal which is undecipherable or the absence of any type of signal, provides an indication that the circuit is faulty. This aspect may be best explained by referring to FIG. 1 and assuming that nodes 100-1 and 100-5 are the transfer end points of a route formed by links 102 through 105.
  • nodes 100-1 and 100-4 will transmit over the fibers respectively forming links 102 and 105 the alarm indication signal.
  • the RTEs respectively disposed in nodes 100-2 and 100-5 will detect that signal when bridged onto appropriate ones of the fibers of links 102 and 105 and report the result to central controller 70 via their associated processor 40.
  • processor 40 is arranged to periodically poll LTEs 20-1 through 20-N for alarms that may have occurred following the previous polling interval.
  • the program is entered at block 400 and proceeds to block 401 where it polls its associated LTEs and collects such alarms, if any. If the program receives an alarm from an LTE, e.g., LTE 20-1, then it increments the associated alarm counter in the manner discussed above. After processing such alarms, the program proceeds to block 402 where it obtains the contents of an active alarm counter and then proceeds to block 403.
  • the program compares the value represented by such contents with the aforementioned predetermined threshold. If the value equals or exceeds the threshold, then the program proceeds to block 404. Otherwise, the program proceeds to block 405.
  • the program sends to central controller 300 a message identifying, inter alia, the (a) associated node, (b) alarm types, and (c) circuits which generated the alarm.
  • the program then proceeds to block 405 where it checks to see if it has completed processing all active alarm counters, and exits via block 406 if it finds that to be the case. Otherwise, the program returns to block 402 to process the next alarm counter.
  • FIG. 5 there is shown in flowchart form the processor 40 program which, inter alia, tests the continuity of an alternate route established by central controller 300.
  • the program is entered at block 500 responsive to receipt of a message from central controller 300 requesting a verification of a failure identified by an alarm report priorly sent to central controller 300 and a request to test the continuity of a circuit forming a newly established route identified in the message.
  • the program proceeds to block 501 where it instructs its associated DCA 30 to connect the associated RTE 45 to one or more circuits of the failed link and instructs the RTE to verify the failure, in the manner discussed.
  • the program then proceeds to block 502 to await a response from its associated RTE 45 and proceeds to block 503 if the RTE response verifies the failure. If the response does not verify the failure, then the program proceeds to block 506 where it sends to central controller 300 a message noting that fact.
  • the program in the manner described above, tests the continuity of each circuit forming the newly established route. If all of the circuits "pass" the continuity test then the program proceeds to block 505 where it instructs its associated DCA 30 to transfer the affected traffic to such circuits. In addition, the program causes the associated RTE 45 to monitor the newly established circuits to verify that such circuits are indeed transporting the affected traffic. The program then proceeds to block 506 where it notifies central controller 300 that the affected traffic has been successfully transferred to the newly established route.
  • FIG. 6 there is shown in flowchart form the program which implements the inventive architecture in the processor 70 of central controller 300.
  • the program is entered at block 600 upon receipt of an alarm message transmitted by a particular one of the network alarm processors 40.
  • the program proceeds to block 601 where it opens the aforementioned window to await receipt of other alarms.
  • the program proceeds to block 602.
  • it determines the extent of the failure based on the alarms that it received during the window.
  • the program determines the priorities of the various types of traffic affected by the failure(s) which is the source of the alarms.
  • the program determines if the affected traffic is so-called critical traffic, such as, for example, traffic originated by certain government agencies (high priority), private line traffic (second highest priority), private network traffic (third highest priority), conventional traffic (fourth highest priority) and so on.
  • the program also determines the volume of traffic for each such category.
  • the program then proceeds to block 603 where it invokes a so-called expanding loop program designed to locate spare capacity from which a number of orders of connectivity (alternate routes) may be established to reroute the affected traffic, in which the extent of such connectivity may be, for example, a pair of optical fibers on one or more alternate routes, and in which each optical fiber pair provides, for example, 36 DS3 circuits.
  • such an expanding loop algorithm may be the algorithm disclosed in the aforementioned Mansour et al patent application, which is shown in FIG. 7 of that patent application and which is incorporated herein by reference.
  • the program completes its task at block 603 it then proceeds to block 604 where it establishes, in the manner discussed above, the first-(or next-)order of connectivity.
  • the program then proceeds to block 605, where it sends to the processors 40 associated with the transfer-end nodes involved in establishing the first-(or next-)order of connectivity commands, or messages, requesting a test of the continuity of the established route and identifying the affected traffic that is to be transferred to that route if such continuity is verified, in which the order of transferring such traffic is based on the priority of the traffic and its volume, as mentioned above.
  • the program then proceeds to block 606 upon receipt from the processors 40 involved in the test messages confirming such continuity and that the affected traffic has been transferred thereto. If such messages do not confirm the continuity of the established route, then the program terminates that route, and returns to block 604 to establish the next order of continuity.
  • the program updates its database including Table 1 of FIG. 2 to reflect the change in the configuration of the associated network and then proceeds to block 607.
  • the program "checks" to see if it has established all orders of connectivity located by the program at block 603 and exits via block 608 if it finds that to be the case. Otherwise, the program returns to block 604 to establish the next-order of connectivity.
  • the program at block 604 proceeds to block 606 for each such circuit which fails the continuity test.
  • the program sends to central controller 300 a message identifying the circuit which failed the continuity test.
  • the program then exits via block 607.

Abstract

A restoration system is provided for enhancing the reliability of a telecommunications network such that particular traffic which is disrupted by, for example, a faulty link, may be quickly rerouted via an alternate route established "on the fly". In particular, each node and link forming the network is monitored, and in the event that such monitoring detects a faulty link or node then a central controller is notified. The controller is arranged to locate spare capacity and establish an alternate route, in which the continuity of the alternate route is confirmed before the disrupted traffic is transferred thereto.

Description

TECHNICAL FIELD
The invention relates to telecommunications networks, and more particularly relates to a network architecture which automatically routes traffic in the event of a network failure.
BACKGROUND OF THE INVENTION
A disruption in telecommunications services in a network is typically caused by an inoperable communications path (link) or equipment within a service providing office (node). A disruption of such services could be very costly to business users who rely on telecommunications services in the operation of their businesses. For example, a particular business could lose revenue as a result of a failure to receive so-called "telemarketing sales" when a disruption in telecommunications services occurs. Moreover, the amount of such lost revenue would be directly proportional to the duration of the disruption. The provider of such telecommunications services would also lose revenue, since the disruption would decrease the number of calls that the associated network could process.
The length of the duration is typically based on a number of factors, such as, for example, (a) the amount of time required to identify the location of the service disruption; (b) the amount of time that is used to identify one or more routes that could be used to alternate route affected traffic around the service disruption; and (c) the amount of time that is used to actually establish such routes.
Most telecommunications networks typically deal with a service disruption by selecting an alternate route around the inoperable link or service providing node. One goal in doing so is to select the most efficient alternate route, one having the least number of nodes and links.
Accordingly, there is need for an arrangement which quickly locates a service disruption, identifies alternate routes and then establishes such routes, such that a service disruption minimally affects the telecommunications user (subscriber).
SUMMARY OF THE INVENTION
An advance in telecommunications switching is obtained by providing a service restoration facility which quickly locates and deals with a fault such that an interruption in communications services that is caused by the fault is virtually transparent to subscribers. Such restoration is achieved, in accord with the invention, by providing at each service node automatic cross-connect means for terminating the end points of communication links entering and leaving the service node, monitoring the operability of each such link and node to quickly identify a service disruption, and notifying a central facility when such a disruption occurs. As an aspect of the invention, the central facility locates spare circuits in individual ones of the links and then establishes, in real time, one or more orders of connectivity (alternate routes) for the rerouting of traffic affected by the interruption, in which the continuity of each such order of connectivity is confirmed before the affected traffic is transferred thereto.
BRIEF DESCRIPTION OF THE DRAWINGS
In the drawing:
FIG. 1 is a broad diagram of a telecommunications network comprising a plurality of nodes and links interconnecting individual pairs of such nodes;
FIG. 2 illustrates a table for tracking the spare capacity in individual ones of the links shown in FIG. 1;
FIG. 3 is a broad block diagram of a node of FIG. 1 including the inventive service restoration architecture;
FIGS. 4 and 5 are flow charts of the software which implements the invention in an alarm processor of FIG. 3; and
FIG. 6 is a flow chart of the software which implements the invention in a central controller of FIG. 3.
DETAILED DESCRIPTION
Turning now to FIG. 1, there is shown a simplified diagram of a telecommunications network 200, which may be, for example, the AT&T digital network, comprising a plurality of nodes. For the sake of brevity and clarity only a small number of such nodes is shown in the figure, namely nodes 100-1 through 100-9. Each such node, includes, inter alia, what is commonly referred to as a Digital Cross-connect Arrangement (DCA) of the type known in the art. One exemplary arrangement which may be advantageously employed as a DCA is the Digital Access and Cross-Connect System III commercially available from AT&T.
It is seen from the figure, that service nodes 100-1 through 100-9 are interconnected via respective ones of the links 101 through 111. Such links may be, for example, optical fiber cables. Within network 200, the respective end points of a link, e.g., link 103, terminate at an associated node, e.g., node 100-2, in which the termination circuitry includes so-called Line Termination Equipment (LTE) designed to interface optical fibers with a DCA. In this way, a DCA cross-connects signals that are transported via optical fibers (or other broadband digital transport systems) that are in service, and thereby determines the routing of such signals. What this means is that a signal received via one link may then be electronically cross-connected (routed) to one of a number of other links also connecting via an LTE to the DCA, in which the cross-connection is based on the destination of the signal, and in which the destination may be the associated node itself or one of the other network nodes.
Thus a DCA, for example, the DCA contained in node 100-1, operates as a conduit for routing signals from an originating node, for example, node 100-1, to a terminating node, for example, node 100-5.
As mentioned above, the optical fibers forming a link terminate on an LTE. In an exemplary embodiment of the invention, such an LTE may be, for example, the well-known FT series G lightwave system commercially available from AT&T. In particular, the FT series G lightwave system is a high-capacity, digital optical-transport system that provides maintenance options and other features such as wavelength and time division multiplexing. During transmission, a multiplexed group of DS3 signals received via an optical fiber and entering a FT series G terminal is first resynchronized and demultiplexed from the line rate and then supplied individually to the DCA at the DS3 rate so that they may be switched to an appropriate outgoing fiber, or line. (DS3 stands for Digital Signal, third level and equals a transmission rate of approximately 44.736 Mbs.) From a maintenance standpoint, an FT series G terminal monitors such signals to track errors as they occur, in which such errors include, for example, framing and synchronization errors. A loss of synchronization is typically indicative of fiber failure, e.g., a fiber which has been inadvertently cut.
Each node also includes an alarm processor, which monitors key components of its associated node, such as the associated LTE equipment. That is, the alarm processor periodically polls, for example, once a second, the associated LTE equipment for alarms that occurred during a preceding period, in which such alarms are indicative of, for example, the aforementioned framing and synchronization errors. Upon receipt of an alarm, the alarm processor initiates a so-called "leaky bucket" process to track whether the alarm is indicative of either an intermittent or a persistent (hard) fault. More particularly, for a particular alarm, the alarm processor increments an associated alarm counter by a predetermined value--illustratively two--and decrements that counter by another predetermined value--illustratively one--at the end of each successive polling session during which no alarm is received. Thus, in the case of an intermittent fault the associated counter would be decremented to a value of zero after the second successive polling session. However, if the alarm persists, then the value contained in the counter will reach a predetermined threshold value--illustratively 10--within a short period of time.
The presence of a large number of DS3 alarms accelerates the "leaky bucket" process, in which the threshold is adapted downward so that such a failure may be recognized quickly. When a particular counter reaches a threshold value, then the alarm processor sends to an associated central controller a message identifying the associated alarm and the failed DS3 circuit. Upon receipt of the message, the central controller starts a window timer to await for possible receipt of messages identifying other failed DS3 circuits. That is, if an alarm is indicative of a cable which has been inadvertently cut, then, during the window, the central controller accumulates a list of all of the DS3 circuits contained in the optical fibers which have failed as result of the cut cable.
In the typical instance, where just a few DS3 circuits have failed, and a sufficient number of spare DS3 circuits are available in the associated optical fiber cable, then the associated node will activate such spares and transfer the traffic affected by the failed DS3 circuits thereto. However, in the instance where the list indicates that most of the DS3 circuits in a cable have failed, then the alarm processor notifies the central controller. The central controller responsive to such notification invokes a program implementing a service restoration algorithm which alternate routes traffic that is affected by the failed cable.
Such a restoration algorithm, although not pertinent to the present invention, could be one that is based on the notion of "knowing" such alternate routes beforehand. Alternatively, the restoration algorithm could be one in which such alternate routes are not known beforehand and are thus established "on the fly". In the latter case, the restoration algorithm is designed to locate spare DS3 circuits that may be contained in other links, which are then placed in service to establish one or more alternate routes for the rerouting of the affected traffic. One such restoration scheme is disclosed in copending U.S. patent application Ser. No. 504,359, filed on Apr. 4, 1990 on behalf of M. O. Mansour et al.
Thus, if it is assumed that a particular link, for example, link 103, fails, then the resulting alarms accumulated by the alarm processors contained in nodes 100-2 and 100-3 will cause those processors to send to the central controller (not shown in FIG. 1) messages identifying the failure (alarm). The central controller responsive thereto invokes the restoration program to locate spare capacity in other ones of the links and establish alternate route(s) for the rerouting of the affected traffic.
More specifically, the central controller identifies such alternate routes by (a) determining the identity of the failure-end offices, which in the present example, would be nodes 100-2 and 100-3; (b) then determining in real time the least number of links and associated (intermediate) nodes that may be used to establish a possible loop whose end points terminate at the failure-end offices; (c) then determining the identity of each so-called transfer-end node; and (d) then determining the identities of the intermediate nodes that would be used to establish the loop.
In particular, the identity of each link in the network as well as the identities of the nodes connecting thereto is maintained in a link table, an example of which is shown in FIG. 2. It is seen from the figure, that each line of TABLE 1 identifies a respective network link and identifies the nodes which connect to the end points thereof. In addition, the last column of TABLE 1 (S-CAP) identifies the number of available spare DS3 circuits in the identified link, in which the number of spare DS3 circuits for a given link is updated as such spares are placed in and out of service, or become faulty, in accordance with status messages received from respective alarm processors. Accordingly, then, it is a simple matter to index TABLE 1 and read out the identities of the failed end offices which connect to respective end points of link 103, which in the present case happen to be nodes 100-2 and 100-3, as shown at line 202.
Once the failure-end nodes have been identified, then the central controller identifies the shortest loop around the failed link. This is done by mapping, in real time and in the form of a tree-like structure, various paths contained in Table 1, in which the paths begin at one of the failure-end nodes, e.g., node 100-2 and lead to the other failure-end node, e.g., node 100-3. The path which is first to lead (terminate) at node 100-3 is then selected as being the shortest loop around failed link 103. Specifically, and referring to both FIGS. 1 and 2, the arrangement determines from lines 202 and 208 that node 100-2 connects to nodes 100-1 and 100-7 via links 102 and 108, respectively, and forms the first level of the tree. At a second level of the tree, the arrangement then determines from TABLE 1 (line 207) that node 100-7 connects to node 100-8 via link 109. The arrangement proceeds in a similar manner for node 100-1, and continues building the tree in the manner just described.
The central controller terminates the process when one of the paths of the tree is first to reach node 100-3, as shown for the path comprising nodes 100-1, 100-6, 100-4 and links 102, 106, 107 and 104. As mentioned above, the first path of the tree which reaches node 100-3 will be the shortest path around the failed link.
The central controller then identifies the transfer-end nodes by noting which nodes are contained in both the failed path (i.e., nodes 100-1, 100-2, 100-3 100-4), and the shortest loop (i.e., nodes 100-2, 100-1, 100-6, 100-4 and 100-3). In the present illustrative example, nodes 100-1 and 100-4 would be the transfer-end nodes since they are common to both paths. The arrangement then identifies the intermediate nodes by noting which nodes are contained in the shortest loop between the transfer-end nodes but not in the original path. As such, node 106 would be identified as being the intermediate node. (It is noted that the shortest loop is defined herein as being the first order of connectivity around the failed link, i.e., a connectivity comprising the fewest number of links.)
It is seen in FIG. 1, that the central controller has identified loop 150 comprising nodes 100-2, 100-1, 100-6, 100-4 and 100-3 and links 106 and 107 as the shortest and most efficient alternate route for rerouting the original traffic around inoperable link 103.
Once loop 150 has been identified, then the central controller sends to each intermediate node, e.g., node 100-6 a set of commands causing the DCA contained in that node to cross-connect the spare capacity of link 106 to the spare capacity of link 107 in order to extend the new path defining the alternate route. Each such command comprises a number of fields specifying the order of switching signals to so-called ports on the DCA of node 100-6 which terminate the ends of spare DS3 circuits of link 106 to the ends of the spare DS3 circuits of link 107. The central controller then sends to the DCA at transfer-end node 100-4 a set of commands directing the order of cross-connecting between the ports which terminate the opposite ends of the spare DS3 circuits of link 107 to the ports terminating the DS3s of link 105 which transported the original traffic. The central controller then sends to the DCA of node 100-1 a set of commands directing the order of cross-connecting between the ports terminating the failed DS3s of link 101 and ports terminating the ends of the spare DS3s of link 106 connecting to node 100-1.
In a similar manner, other portions of the total failed traffic carried by failed link 103 which is not restored to service may also be rerouted via a path established from other spare DS3 circuits forming another loop, or order of connectivity, having different pairs of transfer-end nodes, as illustrated by loop 151 comprising nodes 100-7 through 100-9 and node 100-4 and links 108 through 111.
It is seen from the foregoing that the inventive architecture quickly deals with a service disruption or a degradation in service, thereby making such a disruption nearly transparent to the network user.
Turning now to FIG. 3, there is shown in block diagram form an illustrative embodiment of the inventive restoration architecture. In particular, node 100-N generally represents any one of the nodes forming network 200 and includes DCA 30, alarm processor 40, satellite antenna interface (SAI) 50 for interfacing DCA 30 and processor 40 with antenna 55, and data switch 60 for interfacing DCA 30 and processor 40 with data network 90.
As mentioned above, DCA 30 may be the Digital Access and Cross-Connect system III available from AT&T. Optical fiber cables 10-1 through 10-N represent any one of the links, e.g., links 102, 103, 104, etc., which forms network 200. Each of the DS3 circuits multiplexed on the optical fibers forming cables 10-1 through 10-N connects to a respective port of DCA 30 via one of the LTE 20-1 through 20-N. As mentioned above, besides providing termination sites for the individual fibers of a cable, each LTE is also arranged to monitor the operability and status (in or out of service) of the aforementioned DS3 circuits terminating thereat and, when polled by processor 40, report, via a respective one of the communications busses 41-1 through 41-N, the status of such operability.
As also mentioned above, in response to receipt of an alarm, processor 40 initiates a so-called "leaky bucket" process to determine if the associated fault is either an intermittent or persistent ("hard") fault. If processor 40, which may be, for example, the 68000 DELTA series computer available from Motorola, Inc., determines that an alarm might be due to a hard fault, then it sends to central controller (operations system) 300 via bus 42, SAI 50, dish antenna 55 and satellite 56 a report indicative of that fact. (Satellite 56, may be, for example, the well-known AT&T Skynet satellite communications service.) Such a report is formed into a message using the well-known X.25 message protocol resulting in so-called base-band signals representing the data conveyed by the report. SAI 50, which may be, for example, the Indoor Unit (IDU) available from the Tridom Corporation, modulates such baseband signals using an intermediate frequency (IF) carrier and then modulates the result using a radio frequency (RF) carrier in KU band for presentation to dish antenna 55. Dish antenna 55, in turn, transmits the modulated signals to satellite 56, which then retransmits the signals for receipt by dish antenna 57 connected to SAI 75. SAI 75, which is similar to SAI 50, demodulates the signals and supplies to processor 70 of central controller 300 the resulting processor 40 message.
It is noted that if processor 40 (or DCA 30) cannot access antenna 55, for whatever reason, then processor 40 (or DCA 30) may transmit such a message via data network 90, which may be, for example, the AT&T Accunet packet network. In such an instance, processor 40 (or DCA 30) interfaces with network 90 via X.25 data switch 60 comprising a number of data modules such as, for example, data modules models 3001-201 and 2003-001 as well as driving software identified by model number 3709-201 available from the Telematics Corporation. In such an instance, then, processor 40 supplies the message to data switch 60 for retransmission to processor 70 via network 90. Processor 70 monitors network, or data bus, 90 for messages bearing its address, and removes such message from the bus as they are received.
Thus, in accord with an aspect of the inventive restoration architecture, messages may be exchanged with processor 70 via either one of two diverse paths, i.e., satellite or terrestrial.
Upon receipt of the message, processor 70, which may be, for example, the Hewlett Packard Co. Model 9000-860 computer, updates TABLE 1 of FIG. 2 contained in associated memory (not shown). Processor 70 also updates other such tables (not shown) that are designed to track the status of fibers that are in service. In addition, processor 70, responsive to receipt of a node processor 40 message identifying an inoperable link or a degraded link, invokes the program that is designed to locate spare capacity in order to establish one or more orders of connectivity so that the affected original traffic may be restored to service. As mentioned above, such a restoration algorithm or program could be, for example, the program disclosed in the aforementioned Mansour et al patent application, discussed above. When the program locates such capacity, it then sends messages to each DCA that would be involved in establishing such connectivity, as mentioned above. That is, the program supplies to SAI 75 for transmission to a particular DCA a connectivity message, in which the message includes in a header the identity of the DCA and associated node. SAI 75 (which is similar to SAI 50), in turn, modulates, in the manner described above, the signals forming the connectivity message and supplies the result to antenna 57 for transmission to satellite 56. Satellite 56 retransmits the connectivity message, which is received by each of the network nodes via their respective antennas. However, the message is accepted only by that SAI 50 whose associated network node address is contained in the message. The SAI 50 then passes the message to its associated DCA via bus 31 so that the latter may order its switching scheme to establish a portion of the desired restoration loop (alternate route).
(It is noted that, alternatively, such connectivity messages may be transported via network 90, as mentioned above.)
In addition, processor 70 sends to each processor 40 disposed at respective transfer-end points of a newly established alternate route, one or more messages requesting the processor 40 to confirm the continuity of the established alternate route. If the testing of the alternate route confirms such continuity, then the affected traffic is switched to the alternate route. If the test does not confirm such continuity, then processor 40 sends to processor 70 a message indicative of that fact. Processor 70, in turn, outputs to a terminal a modified version of the received message. A craftperson positioned at the terminal may then direct processor 70 to (a) "dismantle" the established alternate route, (b) search for another alternate route in the manner described above, (c) establish, in the manner described above, the latter alternate route, if available, and (d) request processor 40 to test the continuity of the newly established route. If processor 70 finds that an alternate route is not available, then it outputs to the terminal (not shown) a message indicative of that fact.
Processor 40 performs such continuity testing by sending to its associated DCA 30 connectivity messages to establish a test access path to confirm the continuity of a newly established DS3 circuit. In addition, processor 40 causes its associated restoration test equipment (RTE) 45 to send over one direction of the newly established circuit test signals defining, inter alia, an identity code, e.g., the identity of DS3 circuit that is being tested. An RTE 45 disposed at the opposite end of the alternate route established by that circuit and responsive to receipt of the test signals compares the received identity code with a code received from processor 70. If the comparison is found to be true, then the receiving RTE 45 returns an acknowledgement signal. Upon receipt of that signal, the RTE 45 which sent the test signals, in turn, notifies, its associated processor 40, which, in turn, notifies processor 70. The RTE 45 disposed at the opposite transfer end point performs a continuity test on the same DS3 circuit in a similar manner, but in the opposite direction.
If the test proves out be successful, then processor 70 sends to the pertinent processor 40, via the aforementioned transmission path, a message to transfer the affected traffic to the newly established alternate route.
To facilitate such continuity testing, each RTE 45, which may be, for example, the model 8186 microcomputer commercially available from Intel Corp., connects to a number of DCA 30 port circuits--illustratively fourteen port circuits--via respective communications paths 47-1 through 47-N. In this way, an RTE 45 operating in conjunction with an RTE 45 disposed at the opposite end of a newly established alternate route and at the direction of their respective processor 40, may test simultaneously the continuity of fourteen DS3 circuits. That is, responsive to receipt of an appropriate message from processor 70, processor 40 sends to DCA 30 via bus 44 a message designed to cause DCA 30 to establish a cross-connection between a DS3 circuit that is to be tested and one of the RTE 45 ports 47-1 through 47-N. Processor 70 then sends to RTE 45 via processor 40 a message requesting that a continuity test be performed over the selected one of the port, 47-1 through 47-N, in which the message includes the aforementioned identity code. RTE 45 returns to processor 40 via bus 46 the results of the test.
In a similar manner, processor 40 at the direction of controller 70 may direct RTE 45 to verify a failure. That is, processor 40 may cause RTE 45 to be bridged via one of its connections 47-1 through 47-N onto a DCA 30 circuit for the purpose of determining whether the circuit has indeed failed. If the circuit has failed, then, an upstream node will transmit over the DS3 circuit a so-called alarm indication signal. Thus, the presence of that signal, the presence of a signal which is undecipherable or the absence of any type of signal, provides an indication that the circuit is faulty. This aspect may be best explained by referring to FIG. 1 and assuming that nodes 100-1 and 100-5 are the transfer end points of a route formed by links 102 through 105. Since it has been assumed that link 103 has failed, then nodes 100-1 and 100-4 will transmit over the fibers respectively forming links 102 and 105 the alarm indication signal. The RTEs respectively disposed in nodes 100-2 and 100-5 will detect that signal when bridged onto appropriate ones of the fibers of links 102 and 105 and report the result to central controller 70 via their associated processor 40.
Turning now to FIG. 4, there is shown in flowchart form the program which performs the alarm processing function in processor 40 once each polling cycle. As mentioned above, processor 40 is arranged to periodically poll LTEs 20-1 through 20-N for alarms that may have occurred following the previous polling interval. In particular, the program is entered at block 400 and proceeds to block 401 where it polls its associated LTEs and collects such alarms, if any. If the program receives an alarm from an LTE, e.g., LTE 20-1, then it increments the associated alarm counter in the manner discussed above. After processing such alarms, the program proceeds to block 402 where it obtains the contents of an active alarm counter and then proceeds to block 403. At block 403, the program compares the value represented by such contents with the aforementioned predetermined threshold. If the value equals or exceeds the threshold, then the program proceeds to block 404. Otherwise, the program proceeds to block 405.
At block 404, the program sends to central controller 300 a message identifying, inter alia, the (a) associated node, (b) alarm types, and (c) circuits which generated the alarm. The program then proceeds to block 405 where it checks to see if it has completed processing all active alarm counters, and exits via block 406 if it finds that to be the case. Otherwise, the program returns to block 402 to process the next alarm counter.
Turning now to FIG. 5, there is shown in flowchart form the processor 40 program which, inter alia, tests the continuity of an alternate route established by central controller 300.
In particular, the program is entered at block 500 responsive to receipt of a message from central controller 300 requesting a verification of a failure identified by an alarm report priorly sent to central controller 300 and a request to test the continuity of a circuit forming a newly established route identified in the message. At block 500, the program proceeds to block 501 where it instructs its associated DCA 30 to connect the associated RTE 45 to one or more circuits of the failed link and instructs the RTE to verify the failure, in the manner discussed. The program then proceeds to block 502 to await a response from its associated RTE 45 and proceeds to block 503 if the RTE response verifies the failure. If the response does not verify the failure, then the program proceeds to block 506 where it sends to central controller 300 a message noting that fact.
At block 503, the program, in the manner described above, tests the continuity of each circuit forming the newly established route. If all of the circuits "pass" the continuity test then the program proceeds to block 505 where it instructs its associated DCA 30 to transfer the affected traffic to such circuits. In addition, the program causes the associated RTE 45 to monitor the newly established circuits to verify that such circuits are indeed transporting the affected traffic. The program then proceeds to block 506 where it notifies central controller 300 that the affected traffic has been successfully transferred to the newly established route.
Turning now to FIG. 6, there is shown in flowchart form the program which implements the inventive architecture in the processor 70 of central controller 300. In particular, the program is entered at block 600 upon receipt of an alarm message transmitted by a particular one of the network alarm processors 40. At block 600, the program proceeds to block 601 where it opens the aforementioned window to await receipt of other alarms. At the end of the period of time defining the window--illustratively three seconds--the program proceeds to block 602. At block 602, it determines the extent of the failure based on the alarms that it received during the window. The program then determines the priorities of the various types of traffic affected by the failure(s) which is the source of the alarms. That is, the program determines if the affected traffic is so-called critical traffic, such as, for example, traffic originated by certain government agencies (high priority), private line traffic (second highest priority), private network traffic (third highest priority), conventional traffic (fourth highest priority) and so on. The program also determines the volume of traffic for each such category. The program then proceeds to block 603 where it invokes a so-called expanding loop program designed to locate spare capacity from which a number of orders of connectivity (alternate routes) may be established to reroute the affected traffic, in which the extent of such connectivity may be, for example, a pair of optical fibers on one or more alternate routes, and in which each optical fiber pair provides, for example, 36 DS3 circuits.
As also mentioned above, such an expanding loop algorithm may be the algorithm disclosed in the aforementioned Mansour et al patent application, which is shown in FIG. 7 of that patent application and which is incorporated herein by reference.
Once the program completes its task at block 603 it then proceeds to block 604 where it establishes, in the manner discussed above, the first-(or next-)order of connectivity. The program then proceeds to block 605, where it sends to the processors 40 associated with the transfer-end nodes involved in establishing the first-(or next-)order of connectivity commands, or messages, requesting a test of the continuity of the established route and identifying the affected traffic that is to be transferred to that route if such continuity is verified, in which the order of transferring such traffic is based on the priority of the traffic and its volume, as mentioned above. The program then proceeds to block 606 upon receipt from the processors 40 involved in the test messages confirming such continuity and that the affected traffic has been transferred thereto. If such messages do not confirm the continuity of the established route, then the program terminates that route, and returns to block 604 to establish the next order of continuity.
At block 606, the program updates its database including Table 1 of FIG. 2 to reflect the change in the configuration of the associated network and then proceeds to block 607. At block 607, the program "checks" to see if it has established all orders of connectivity located by the program at block 603 and exits via block 608 if it finds that to be the case. Otherwise, the program returns to block 604 to establish the next-order of connectivity.
The program at block 604 proceeds to block 606 for each such circuit which fails the continuity test. In this instance, the program sends to central controller 300 a message identifying the circuit which failed the continuity test. The program then exits via block 607.
The foregoing is merely illustrative of the principles of the invention. Those skilled in the art will be able to devise numerous arrangements, which, although not explicitly shown or described herein, nevertheless embody those principles that are within the spirit and scope of the invention. For example, it can be appreciated from the foregoing detailed discussion that the invention may be readily practiced in systems employing a transmission rate that is either less than or greater than the DS3 rate. Also, the invention may be practiced in a system employing almost any type of digital cross-connect arrangement, such as, for example, the Digital Access and Cross-Connect System IV commercially available from AT&T.

Claims (20)

We claim:
1. A service restoration system for use in a communications network formed from a plurality of nodes interconnected by a plurality of transmission links, said system comprising
means, contained in individual ones of said nodes, for polling associated ones of said nodes and links for alarms indicative of at least a disruption in the flow of traffic, and, responsive to receiving from a particular one of said associated nodes and links at a rate which equals a predetermined threshold one of said alarms, for outputting to one of a number of communications paths a message at least identifying said traffic disruption and its location,
central control means operative, responsive to receipt of said message via said one communications path, for locating spare capacity contained in individual other ones of said links, and for dynamically establishing from said spare capacity a number of orders of connectivity to route said disrupted traffic around said particular one of said associated nodes or links which generated said one alarm condition, and
means, responsive to receipt from said central control means via one of said communications paths a message requesting a continuity test of a particular one of said orders of connectivity, for monitoring said particular one of said associated ones of said nodes and links which generated said one alarm condition to verify said disruption, and for then testing for continuity said one order of connectivity so that either a portion or all of said disrupted traffic may be transferred thereto.
2. The system set forth in claim 1 wherein said one order of connectivity includes transfer end nodes disposed at respective ends of said one order of connectivity, and wherein said continuity test is performed at each of said transfer end nodes.
3. The system set forth in claim 2 wherein said transfer end nodes perform said continuity test by exchanging signals indicative of a predetermined identity code and wherein said continuity is confirmed when said tranfer end nodes receive said identity code from each other.
4. The system set forth in claim 3 wherein said one order of connectivity includes at least one DS3 circuit in which one of said transfer end nodes transmits said identity code over said one circuit in a first direction and the other one of said transfer end nodes transmits said identity code over said one circuit in a second opposite direction.
5. The system set forth in claim 4 wherein said one order of connectivity comprises a plurality of DS3 circuits, and wherein said continuity test is performed on each of said circuits.
6. The system set forth in claim 1 wherein said means for polling includes means responsive to the results of said continuity test confirming said continuity between the transfer end points of said one order of connectivity for then transferring said portion or all of said degraded traffic thereto.
7. The system set forth in claim 6 wherein said means for polling further includes means, responsive to said continuity test not confirming said continuity, for then outputting to one of said communications paths a message indicative of such noncontinuity.
8. The system set forth in claim 7 wherein said central control means includes means, responsive to receipt via said one of said communications path said message indicative of said noncontinuity, for then locating and establishing another order of connectivity as a replacement for said one order of connectivity and for then causing the continuity of said other order of connectivity to be tested.
9. A service restoration system for use in a communications network formed from a plurality of nodes interconnected by a plurality of transmission links, said system comprising
means, contained in individual ones of said nodes, for polling associated ones of said nodes and links for alarms indicative of at least a disruption in the flow of traffic, and, responsive to receiving from a particular one of said associated nodes and links at a rate which equals a predetermined threshold one of said alarms, for outputting to one of a number of communications paths a message at least identifying said traffic disruption and its location, and
central control means operative, responsive to receipt of said message via said one communications path, for locating spare capacity contained in individual other ones of said links, and for dynamically establishing from said spare capacity a number of orders of connectivity to route said disrupted traffic around said particular one of said associated nodes or links which generated said one alarm condition, wherein one of said communications paths is a data network and another one of said communications paths is a satellite link.
10. The arrangement set forth in claim 9 wherein each of said links comprises at least one DS3 circuit.
11. A method of establishing an alternate traffic route in a communications network formed from a plurality of nodes interconnected by a plurality of transmission links, said method comprising the steps of
polling associated ones of said nodes and links for alarms indicative of at least a disruption in the flow of traffic through ones of said associated ones of said nodes and links,
responding to receipt of a particular one of said alarms at a rate which causes a predetermined threshold to be reached by outputting a message identifying at least said disruption and its location to one of a number of communications paths for delivery to a central control location,
responding to receipt of said message at said central control location by locating spare capacity contained in individual ones of said links,
establishing in real time from said spare capacity a number of orders of connectivity to route said degraded traffic around that one of said associated nodes or links which generated said one alarm condition, and
responding to receipt from said central control location via one of said communications paths of a message requesting a continuity test of a particular one of said orders of connectivity by monitoring said particular one of said associated ones of said nodes and links which generated said one alarm condition to verify said disruption, and then testing the continuity of said one order of connectivity to determine if said disrupted traffic may be transferred thereto.
12. The method set forth in claim 11 wherein said one order of connectivity includes transfer end nodes disposed at respective ends of said one order of connectivity, and wherein said step of testing is performed at each of said transfer end nodes.
13. The method set forth in claim 12 wherein said transfer end nodes perform said continuity test step by exchanging signals indicative of a predetermined identity code and by confirming said continuity if said transfer end nodes receive said identity code from each other.
14. The method set forth in claim 13 wherein said step of polling includes the step of responding to said continuity test not confirming said continuity by then outputting to one of said communications paths a message indicative of such noncontinuity.
15. The method set forth in claim 14 wherein said step of establishing includes the step of responding to receipt via said one of said communications path of said message indicative of said noncontinuity by locating and establishing another order of connectivity as a replacement for said one order of connectivity and by causing the continuity of said other/order of connectivity to be tested.
16. A method of establishing an alternate traffic route in a communications network formed from a plurality of nodes interconnected by a plurality of transmission links, said method comprising the steps of
polling associated ones of said nodes and links for alarms indicative of at least a degradation in the flow of traffic through one of said associated ones of said nodes and links,
responding to receipt of a particular one of said alarms at a rate which causes a predetermined threshold to be reached by outputting to one of a number of communications paths for delivery to a central control location a message at least identifying said traffic degradation and its location,
responding to receipt of said message at said central control location by locating spare capacity contained in individual other ones of said links,
establishing in real time from said spare capacity a number of orders of connectivity to route said degraded traffic around that one of said associated nodes or links which generated said one alarm condition,
responding to receipt from said central control location via one of said communications paths a message requesting a continuity test of a particular one of said orders of connectivity by monitoring said particular one of said associated ones of said nodes and links which generated said one alarm condition to verify said degradation, and then testing the continuity of said one order of connectivity to determine if said degraded traffic may be transferred thereto, and wherein said one order of connectivity includes at least one DS3 circuit connected between transfer end nodes, in which one of said transfer end nodes transmits said identity code over one direction of said circuit and the other one of said transfer end nodes transmits said identity code over the other opposite direction of said circuits.
17. The method set forth in claim 12 wherein said one order of connectivity comprises a plurality of DS3 circuits, and wherein said continuity test step is performed on each of said circuits.
18. The method set forth in claim 11 wherein said polling step includes the step of responding to the confirmation of continuity between the transfer end points of said one order of connectivity by then transferring said portion or all of said degraded traffic to said one order of connectivity.
19. A method of establishing and alternate traffic route in a communications network formed from a plurality of nodes interconnected by a plurality of transmission links, said method comprising the steps of
polling associated ones of said nodes and links for alarms indicative of at least a degradation in the flow of traffic through one of said associated ones of said nodes and links,
responding to receipt of a particular one of said alarms at a rate which causes a predetermined threshold to be reached by outputting to one of a number of communications paths for delivery to a central control location a message at least identifying said traffic degradation and its location, in which one of said communications paths is a data network and in which another one of said communications paths is a satellite link,
responding to receipt of said message at said central control location by locating spare capacity contained in individual other ones of said links, and
establishing in real time from said spare capacity a number of orders of connectivity to route said degraded traffic around that one of said associated nodes or links which generated said one alarm condition.
20. The method set forth in claim 19 wherein each of said links comprises at least one DS3 circuit.
US07/637,244 1991-01-03 1991-01-03 Telecommunications network restoration architecture Expired - Lifetime US5182744A (en)

Priority Applications (10)

Application Number Priority Date Filing Date Title
US07/637,244 US5182744A (en) 1991-01-03 1991-01-03 Telecommunications network restoration architecture
CA002056298A CA2056298C (en) 1991-01-03 1991-11-27 Telecommunications network restoration architecture
DE69131041T DE69131041T2 (en) 1991-01-03 1991-12-10 Reinstatement architecture for telecommunications network
EP91311482A EP0494513B1 (en) 1991-01-03 1991-12-10 Telecommunications network restoration architecture
ES91311482T ES2130134T3 (en) 1991-01-03 1991-12-10 RESTORATION ARCHITECTURE FOR A TELECOMMUNICATION NETWORK.
AT91311482T ATE178177T1 (en) 1991-01-03 1991-12-10 REDEPLACEMENT ARCHITECTURE FOR TELECOMMUNICATIONS NETWORK
AU89690/91A AU626226B1 (en) 1991-01-03 1991-12-13 Telecommunications network restoration architecture
KR1019910024116A KR960007668B1 (en) 1991-01-03 1991-12-24 Telecommunication metwork restoration architecture
JP3358238A JP3009769B2 (en) 1991-01-03 1991-12-27 Service restoration system and method for use in telecommunications networks
HK98112771A HK1011810A1 (en) 1991-01-03 1998-12-03 Telecommunications network restoration architecture

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US07/637,244 US5182744A (en) 1991-01-03 1991-01-03 Telecommunications network restoration architecture

Publications (1)

Publication Number Publication Date
US5182744A true US5182744A (en) 1993-01-26

Family

ID=24555138

Family Applications (1)

Application Number Title Priority Date Filing Date
US07/637,244 Expired - Lifetime US5182744A (en) 1991-01-03 1991-01-03 Telecommunications network restoration architecture

Country Status (10)

Country Link
US (1) US5182744A (en)
EP (1) EP0494513B1 (en)
JP (1) JP3009769B2 (en)
KR (1) KR960007668B1 (en)
AT (1) ATE178177T1 (en)
AU (1) AU626226B1 (en)
CA (1) CA2056298C (en)
DE (1) DE69131041T2 (en)
ES (1) ES2130134T3 (en)
HK (1) HK1011810A1 (en)

Cited By (67)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5408649A (en) * 1993-04-30 1995-04-18 Quotron Systems, Inc. Distributed data access system including a plurality of database access processors with one-for-N redundancy
US5420917A (en) * 1993-12-09 1995-05-30 At&T Corp. Automated recovery of telecommunication network elements
US5459716A (en) * 1994-04-15 1995-10-17 Mci Communications Corporation Facility restoration for telecommunications networks
US5463615A (en) * 1994-07-07 1995-10-31 At&T Corp. Node failure restoration tool
US5465294A (en) * 1994-06-30 1995-11-07 At&T Corp. System and method for recovering from a telecommunications disaster
US5504863A (en) * 1994-02-07 1996-04-02 Fujitsu Limited Centralized network monitoring device for monitoring devices via intermediate monitoring devices by means of polling and including display means displaying screens corresponding to heirarchic levels of the monitored devices in a network
US5509004A (en) * 1994-08-01 1996-04-16 Motorola, Inc. Communication method and network with multiple dynamic intraswitching
US5523997A (en) * 1994-06-13 1996-06-04 Motorola, Inc. Communication network with dynamic intraswitching
WO1996021301A1 (en) * 1994-11-15 1996-07-11 Telefonaktiebolaget Lm Ericsson Methods for verification of routing table information
US5546574A (en) * 1994-06-30 1996-08-13 At&T Corporation Peer-to-peer data concurrence processes and apparatus
US5579318A (en) * 1994-06-30 1996-11-26 Bellsouth Corporation Processes and apparatus for maintaining data concurrence between databases in telecommunications networks
US5579384A (en) * 1995-02-17 1996-11-26 Bellsouth Corporation Telecommunications network service central management system interfacing with protocol specific regional stations providing services to subscribers
US5581543A (en) * 1995-02-27 1996-12-03 Motorola, Inc. Communication network and method which respond to a failed link
US5583976A (en) * 1994-02-18 1996-12-10 Bellsouth Corporation Telecommunications network configuration model for data management and allocation
US5586112A (en) * 1993-12-16 1996-12-17 Nec Corporation Digital crossconnect system for selecting alternate communication routes in case of a transmission fault
WO1997001230A1 (en) * 1995-06-22 1997-01-09 Mci Communications Corporation System and method for reconfiguring a telecommunications network to its normal state after repair of fault
WO1997001143A1 (en) * 1995-06-22 1997-01-09 Mci Communications Corporation Spare links optimization in a distributed restoration scheme
US5625866A (en) * 1991-12-12 1997-04-29 Televerket Mobile telecommunication system having an auxiliary routing arrangement
US5627889A (en) * 1995-06-29 1997-05-06 At&T Service restoration technique for telecommunications facilities having a single degree of freedom
US5642396A (en) * 1995-05-10 1997-06-24 Mci Corporation Release cause table for failed calls in SS7/ISDN Networks
US5731887A (en) * 1995-12-22 1998-03-24 Mci Communications Corporation System and method for photonic facility and line protection switching
US5761502A (en) * 1995-12-29 1998-06-02 Mci Corporation System and method for managing a telecommunications network by associating and correlating network events
US5777761A (en) * 1995-12-22 1998-07-07 Mci Communications Corporation System and method for photonic facility and line protection switching using wavelength translation
WO1998029997A2 (en) * 1996-12-31 1998-07-09 Mci Communications Corporation Method and apparatus for automated node-based normalization after network restoration
US5790287A (en) * 1993-03-11 1998-08-04 Lucent Technologies, Inc. Optical communication system with improved maintenance capabilities
US5828978A (en) * 1996-02-23 1998-10-27 Zafarloop, Inc. Line restoration detection for security systems
US5832196A (en) * 1996-06-28 1998-11-03 Mci Communications Corporation Dynamic restoration process for a telecommunications network
US5835711A (en) * 1995-02-01 1998-11-10 International Business Machines Corporation Method and system for implementing multiple leaky bucket checkers using a hybrid synchronous/asynchronous update mechanism
US5838660A (en) * 1996-11-14 1998-11-17 Mci Communications Corporation Dynamic restoration process
US5859836A (en) * 1996-07-29 1999-01-12 At&T Corp Alternate ring restoration technique
US5884017A (en) * 1995-12-29 1999-03-16 Mci Communications Corporation Method and system for optical restoration tributary switching in a fiber network
US5903370A (en) * 1996-06-28 1999-05-11 Mci Communications Corporation System for an optical domain
US5914798A (en) * 1995-12-29 1999-06-22 Mci Communications Corporation Restoration systems for an optical telecommunications network
US5936951A (en) * 1995-04-26 1999-08-10 Telefonaktiebolaget Lm Ericsoon Dynamic infrastructure
WO1999043116A1 (en) * 1998-02-20 1999-08-26 Mci Worldcom, Inc. Method, apparatus, and computer program product for optical network restoration
US6005694A (en) * 1995-12-28 1999-12-21 Mci Worldcom, Inc. Method and system for detecting optical faults within the optical domain of a fiber communication network
US6061807A (en) * 1997-06-27 2000-05-09 International Business Machines Corporation Methods systems and computer products for error recovery of endpoint nodes
US6108113A (en) * 1995-12-29 2000-08-22 Mci Communications Corporation Method and system for transporting ancillary network data
US6188666B1 (en) * 1998-04-28 2001-02-13 At&T Corp. Restoration method for multiplexed circuits
US6215867B1 (en) 1997-06-20 2001-04-10 At&T Corp. Telecommunications network architecture with rapid restoration
US6285475B1 (en) 1995-12-29 2001-09-04 Mci Communications Corporation Method and system for detecting optical faults in a network fiber link
WO2001065823A1 (en) * 2000-02-29 2001-09-07 Quadlogic Controls Corporation System and method for on-line monitoring and billing of power consumption
US6324162B1 (en) 1998-06-03 2001-11-27 At&T Corp. Path-based restoration mesh networks
US6370110B1 (en) * 1998-09-16 2002-04-09 At&T Corp Back-up restoration technique for SONET/SHD rings
US6392989B1 (en) * 2000-06-15 2002-05-21 Cplane Inc. High speed protection switching in label switched networks through pre-computation of alternate routes
US6457050B1 (en) * 1997-08-01 2002-09-24 Mci Communications Corporation System and method for dynamically restoring communications within a network
US6498778B1 (en) 1998-12-17 2002-12-24 At&T Corp. Optimizing restoration capacity
US6507649B1 (en) * 1998-12-18 2003-01-14 Ericsson Inc. Mechanism and method for distributing ISUP stacks over multiple loosely coupled processors
US6594775B1 (en) * 2000-05-26 2003-07-15 Robert Lawrence Fair Fault handling monitor transparently using multiple technologies for fault handling in a multiple hierarchal/peer domain file server with domain centered, cross domain cooperative fault handling mechanisms
US20030147473A1 (en) * 2002-02-06 2003-08-07 Mitsubishi Denki Kabushiki Kaisha Digital signal transmitting device for switching a signal processor of a fault condition for a spare signal processor of a non-fault condition
US20030229803A1 (en) * 2002-06-11 2003-12-11 Comer Erwin P. Communication systems automated security detection based on protocol cause codes
US20040203558A1 (en) * 2002-02-08 2004-10-14 Ntt Docomo, Inc. Communications system, communications device, and communications method
US20040218525A1 (en) * 2003-04-29 2004-11-04 David Elie-Dit-Cosaque Protection scheme for a communications network under multiple failures
US20050135234A1 (en) * 1999-01-15 2005-06-23 Saleh Ali N. Method for routing information over a network
US6947854B2 (en) 2000-02-29 2005-09-20 Quadlogic Controls Corporation System and method for on-line monitoring and billing of power consumption
US6987735B2 (en) 2001-05-24 2006-01-17 International Business Machines Corporation System and method for enhancing the availability of routing systems through equal cost multipath
US20060239262A1 (en) * 2005-04-25 2006-10-26 Lsi Logic Corporation Connection memory for tributary time-space switches
US7187926B1 (en) * 1997-07-01 2007-03-06 Deutsche Telekom Ag Method and system for controlling the use of satellite transmission capacity in terrestrial networks
US20080013570A1 (en) * 2006-07-11 2008-01-17 Smith Barton A Establishing Two Or More Simultaneous Channels of Communication With A User
US20080259805A1 (en) * 2007-04-17 2008-10-23 John Andrew Canger Method and apparatus for managing networks across multiple domains
US7453824B1 (en) * 2003-07-10 2008-11-18 Sprint Communications Company L.P. Method and system for identifying optimal mapping in a network
US8452555B2 (en) 2001-02-28 2013-05-28 Quadlogic Controls Corporation Apparatus and methods for multi-channel metering
US20150085994A1 (en) * 2012-03-30 2015-03-26 British Telecommunications Public Limited Company Cable damage detection
US20150092538A1 (en) * 2013-09-27 2015-04-02 Cisco Technology, Inc. Handling unacceptable asymmetrical communication paths in computer networks
US9081653B2 (en) 2011-11-16 2015-07-14 Flextronics Ap, Llc Duplicated processing in vehicles
US20150200802A1 (en) * 2014-01-15 2015-07-16 Dell Products, L.P. Systems and methods for improved fault tolerance in solicited information handling systems
US10491748B1 (en) 2006-04-03 2019-11-26 Wai Wu Intelligent communication routing system and method

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3439533B2 (en) * 1994-06-24 2003-08-25 富士通株式会社 SDH2-fiber ring optical multiplexer having selective protection function
IL110859A (en) * 1994-09-04 1999-12-31 Rit Techn Ltd Interconnection monitor system for telephone network
DE19511087B4 (en) * 1995-03-25 2006-04-13 Deutsche Telekom Ag Method and arrangement for automatic connection of replacement connections via the IDSN network in the event of faulty leased lines
JP2806374B2 (en) * 1996-08-19 1998-09-30 日本電気株式会社 ATM virtual path switching node
US5881048A (en) * 1996-11-25 1999-03-09 Mci Communication Corporation Method and apparatus for determining maximum network failure spans forrestoration
US5991264A (en) * 1996-11-26 1999-11-23 Mci Communications Corporation Method and apparatus for isolating network failures by applying alarms to failure spans
US6075766A (en) * 1996-11-26 2000-06-13 Mci Communications Corporation Method and apparatus for identifying restoral routes in a network
US5995485A (en) * 1996-11-26 1999-11-30 Mci Communications Corporation Method and apparatus for isolating network failures by correlating paths issuing alarms with failure spans
GB9625020D0 (en) * 1996-11-29 1997-01-15 Northern Telecom Ltd Network restoration
US5943314A (en) * 1996-12-30 1999-08-24 Mci Communications Corporation Method and system of distributed network restoration with multiple failures
US6031819A (en) * 1996-12-30 2000-02-29 Mci Communications Corporation Method and system of distributed network restoration using preferred routes
US5883881A (en) * 1996-12-30 1999-03-16 Mci Communications Corporation Method for selecting preferred nodes for distributed network restoration
US6327669B1 (en) 1996-12-31 2001-12-04 Mci Communications Corporation Centralized restoration of a network using preferred routing tables to dynamically build an available preferred restoral route
US6556538B1 (en) * 1996-12-31 2003-04-29 Mci Communications Corporation Integration of a centralized network restoration system with a distributed network restoration system
CA2276518A1 (en) * 1997-01-09 1998-07-16 At&T Corp. Mesh network with high restorative capacity
US5999103A (en) * 1997-06-30 1999-12-07 Mci Communications Corporation Method and system for assigning spare transmission links to restoral routes
US5958063A (en) * 1997-06-30 1999-09-28 Mci Communications Corporation Method and system for pre-patching a communications network
US6052796A (en) * 1997-06-30 2000-04-18 Mci Communications Corporation Method and system for augmenting communications network with spare capacity
US6091706A (en) * 1997-07-17 2000-07-18 Siemens Information And Communication Networks, Inc. Apparatus and method for preventing network rerouting
US5941992A (en) * 1997-08-13 1999-08-24 Mci Communications Corporation Distributed method and system for excluding components from a restoral route in a communications network
US5959969A (en) * 1997-08-13 1999-09-28 Mci Communications Corporation Method for initiating a distributed restoration process
US6347074B1 (en) 1997-08-13 2002-02-12 Mci Communications Corporation Centralized method and system for excluding components from a restoral route in a communications network
CA2262046C (en) * 1998-02-24 2002-10-22 At&T Corp. Optical layer quasi-centralized restoration
DE69932810T2 (en) * 1998-03-09 2007-02-22 British Telecommunications P.L.C. RESERVES IN A TELECOMMUNICATIONS NETWORK
JP3656806B2 (en) 1999-02-10 2005-06-08 ブリヂストンスポーツ株式会社 Solid golf balls
US6826146B1 (en) * 1999-06-02 2004-11-30 At&T Corp. Method for rerouting intra-office digital telecommunications signals
CN101821990B (en) * 2007-10-09 2012-10-31 Lm爱立信电话有限公司 Arrangement and method for handling failures in network
GB2507994A (en) * 2012-11-16 2014-05-21 Vodafone Ip Licensing Ltd Mobile Device Application Analysis

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3394231A (en) * 1964-11-18 1968-07-23 Bell Telephone Labor Inc Communications network control system
US3870955A (en) * 1972-06-09 1975-03-11 Ericsson Telefon Ab L M Emergency switching equipment for broadband transmission
US4284852A (en) * 1979-06-22 1981-08-18 Northern Telecom Limited Alternate routing for a telephone system
US4345116A (en) * 1980-12-31 1982-08-17 Bell Telephone Laboratories, Incorporated Dynamic, non-hierarchical arrangement for routing traffic
US4680776A (en) * 1983-11-11 1987-07-14 Fujitsu Limited Protection switching system for carrier transmission line
US4704724A (en) * 1985-12-05 1987-11-03 Bell Communications Research, Inc. Routing of network traffic
US4825206A (en) * 1985-11-04 1989-04-25 International Business Machines Corporation Automatic feedback of network topology data
US4853927A (en) * 1986-12-10 1989-08-01 U.S. Philips Corporation Method and circuit arrangement for decentralized controlled transmission rerouting
US4862496A (en) * 1985-12-18 1989-08-29 British Telecommunications Public Limited Company Routing of network traffic
US4885780A (en) * 1988-07-15 1989-12-05 Bell Communications Research, Inc. Method for call routing in a network
US4924459A (en) * 1985-08-26 1990-05-08 At & T Bell Laboratories Digital transmission interconnect signal
US4991204A (en) * 1988-12-05 1991-02-05 Nippon Telegraph And Telephone Corporation Adaptive routing control method
US4999829A (en) * 1989-11-06 1991-03-12 At&T Bell Laboratories Automatic fault recovery in a packet network

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS592467A (en) * 1982-06-28 1984-01-09 Nec Corp Network failure control system in packet exchange network
JPS61263350A (en) * 1985-05-17 1986-11-21 Hitachi Ltd Automatic informing system for communication line failure
US4737983A (en) * 1985-10-02 1988-04-12 American Telephone And Telegraph Company Communications, Inc. Automatic call distributor telephone service
JPH02155334A (en) * 1988-12-07 1990-06-14 Fujitsu Ltd Detouring path retrieval system
JPH02228898A (en) * 1989-03-02 1990-09-11 Fujitsu Ltd Polling supervisory system
JP2689273B2 (en) * 1989-04-25 1997-12-10 富士通株式会社 Failure recovery method

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3394231A (en) * 1964-11-18 1968-07-23 Bell Telephone Labor Inc Communications network control system
US3870955A (en) * 1972-06-09 1975-03-11 Ericsson Telefon Ab L M Emergency switching equipment for broadband transmission
US4284852A (en) * 1979-06-22 1981-08-18 Northern Telecom Limited Alternate routing for a telephone system
US4345116A (en) * 1980-12-31 1982-08-17 Bell Telephone Laboratories, Incorporated Dynamic, non-hierarchical arrangement for routing traffic
US4680776A (en) * 1983-11-11 1987-07-14 Fujitsu Limited Protection switching system for carrier transmission line
US4924459A (en) * 1985-08-26 1990-05-08 At & T Bell Laboratories Digital transmission interconnect signal
US4825206A (en) * 1985-11-04 1989-04-25 International Business Machines Corporation Automatic feedback of network topology data
US4704724A (en) * 1985-12-05 1987-11-03 Bell Communications Research, Inc. Routing of network traffic
US4862496A (en) * 1985-12-18 1989-08-29 British Telecommunications Public Limited Company Routing of network traffic
US4853927A (en) * 1986-12-10 1989-08-01 U.S. Philips Corporation Method and circuit arrangement for decentralized controlled transmission rerouting
US4885780A (en) * 1988-07-15 1989-12-05 Bell Communications Research, Inc. Method for call routing in a network
US4991204A (en) * 1988-12-05 1991-02-05 Nippon Telegraph And Telephone Corporation Adaptive routing control method
US4999829A (en) * 1989-11-06 1991-03-12 At&T Bell Laboratories Automatic fault recovery in a packet network

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
Data Communications, Apr. 1988, W. Cohen et al., pp. 175 183; Building a Private Wide Area, Fiber Backbone Network . *
Data Communications, Apr. 1988, W. Cohen et al., pp. 175-183; "Building a Private Wide-Area, Fiber Backbone Network".
IEEE/IEICE Global Telecom. Conf. 1987, vol. 2 of 3, Nov. 15 18, 1987, S. Hasegawa et al., pp. 1096 1100, Dynamic Reconfiguration of Digital Cross Connect Systems with Network . . . . *
IEEE/IEICE Global Telecom. Conf. 1987, vol. 2 of 3, Nov. 15-18, 1987, S. Hasegawa et al., pp. 1096-1100, "Dynamic Reconfiguration of Digital Cross-Connect Systems with Network . . . ".
Trans. Inst. Electron. Inf. & Commun., vol. J70B, No. 4, pp. 432 442, Apr. 1987, H. Inamori, Performance Evaluation of Mutual . . . . *
Trans. Inst. Electron. Inf. & Commun., vol. J70B, No. 4, pp. 432-442, Apr. 1987, H. Inamori, "Performance Evaluation of Mutual . . . ".

Cited By (84)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5625866A (en) * 1991-12-12 1997-04-29 Televerket Mobile telecommunication system having an auxiliary routing arrangement
US5790287A (en) * 1993-03-11 1998-08-04 Lucent Technologies, Inc. Optical communication system with improved maintenance capabilities
US5621884A (en) * 1993-04-30 1997-04-15 Quotron Systems, Inc. Distributed data access system including a plurality of database access processors with one-for-N redundancy
US5408649A (en) * 1993-04-30 1995-04-18 Quotron Systems, Inc. Distributed data access system including a plurality of database access processors with one-for-N redundancy
US5420917A (en) * 1993-12-09 1995-05-30 At&T Corp. Automated recovery of telecommunication network elements
US5586112A (en) * 1993-12-16 1996-12-17 Nec Corporation Digital crossconnect system for selecting alternate communication routes in case of a transmission fault
US5504863A (en) * 1994-02-07 1996-04-02 Fujitsu Limited Centralized network monitoring device for monitoring devices via intermediate monitoring devices by means of polling and including display means displaying screens corresponding to heirarchic levels of the monitored devices in a network
US5583976A (en) * 1994-02-18 1996-12-10 Bellsouth Corporation Telecommunications network configuration model for data management and allocation
US5459716A (en) * 1994-04-15 1995-10-17 Mci Communications Corporation Facility restoration for telecommunications networks
US5523997A (en) * 1994-06-13 1996-06-04 Motorola, Inc. Communication network with dynamic intraswitching
US5546574A (en) * 1994-06-30 1996-08-13 At&T Corporation Peer-to-peer data concurrence processes and apparatus
US5579318A (en) * 1994-06-30 1996-11-26 Bellsouth Corporation Processes and apparatus for maintaining data concurrence between databases in telecommunications networks
US5465294A (en) * 1994-06-30 1995-11-07 At&T Corp. System and method for recovering from a telecommunications disaster
US5463615A (en) * 1994-07-07 1995-10-31 At&T Corp. Node failure restoration tool
US5509004A (en) * 1994-08-01 1996-04-16 Motorola, Inc. Communication method and network with multiple dynamic intraswitching
WO1996021301A1 (en) * 1994-11-15 1996-07-11 Telefonaktiebolaget Lm Ericsson Methods for verification of routing table information
AU707285B2 (en) * 1994-11-15 1999-07-08 Telefonaktiebolaget Lm Ericsson (Publ) Methods for verification of routing table information
US5835711A (en) * 1995-02-01 1998-11-10 International Business Machines Corporation Method and system for implementing multiple leaky bucket checkers using a hybrid synchronous/asynchronous update mechanism
US5579384A (en) * 1995-02-17 1996-11-26 Bellsouth Corporation Telecommunications network service central management system interfacing with protocol specific regional stations providing services to subscribers
US5581543A (en) * 1995-02-27 1996-12-03 Motorola, Inc. Communication network and method which respond to a failed link
US5936951A (en) * 1995-04-26 1999-08-10 Telefonaktiebolaget Lm Ericsoon Dynamic infrastructure
US5642396A (en) * 1995-05-10 1997-06-24 Mci Corporation Release cause table for failed calls in SS7/ISDN Networks
WO1997001230A1 (en) * 1995-06-22 1997-01-09 Mci Communications Corporation System and method for reconfiguring a telecommunications network to its normal state after repair of fault
WO1997001143A1 (en) * 1995-06-22 1997-01-09 Mci Communications Corporation Spare links optimization in a distributed restoration scheme
US5680326A (en) * 1995-06-22 1997-10-21 Mci Corporation System and method therefor of estimating optimal spare capacity for a distributed restoration scheme
US6222821B1 (en) 1995-06-22 2001-04-24 Mci Communications Corporation System and method for reconfiguring a telecommunications network to its normal state after repair of fault
US5627889A (en) * 1995-06-29 1997-05-06 At&T Service restoration technique for telecommunications facilities having a single degree of freedom
US5731887A (en) * 1995-12-22 1998-03-24 Mci Communications Corporation System and method for photonic facility and line protection switching
US5777761A (en) * 1995-12-22 1998-07-07 Mci Communications Corporation System and method for photonic facility and line protection switching using wavelength translation
US6005694A (en) * 1995-12-28 1999-12-21 Mci Worldcom, Inc. Method and system for detecting optical faults within the optical domain of a fiber communication network
US5761502A (en) * 1995-12-29 1998-06-02 Mci Corporation System and method for managing a telecommunications network by associating and correlating network events
US6108113A (en) * 1995-12-29 2000-08-22 Mci Communications Corporation Method and system for transporting ancillary network data
US5884017A (en) * 1995-12-29 1999-03-16 Mci Communications Corporation Method and system for optical restoration tributary switching in a fiber network
US5914798A (en) * 1995-12-29 1999-06-22 Mci Communications Corporation Restoration systems for an optical telecommunications network
US6285475B1 (en) 1995-12-29 2001-09-04 Mci Communications Corporation Method and system for detecting optical faults in a network fiber link
US5828978A (en) * 1996-02-23 1998-10-27 Zafarloop, Inc. Line restoration detection for security systems
US5832196A (en) * 1996-06-28 1998-11-03 Mci Communications Corporation Dynamic restoration process for a telecommunications network
US5903370A (en) * 1996-06-28 1999-05-11 Mci Communications Corporation System for an optical domain
US5859836A (en) * 1996-07-29 1999-01-12 At&T Corp Alternate ring restoration technique
US5838660A (en) * 1996-11-14 1998-11-17 Mci Communications Corporation Dynamic restoration process
WO1998029997A2 (en) * 1996-12-31 1998-07-09 Mci Communications Corporation Method and apparatus for automated node-based normalization after network restoration
US6018576A (en) * 1996-12-31 2000-01-25 Mci Communications Corporation Method and apparatus for automated node-based normalization after network restoration
WO1998029997A3 (en) * 1996-12-31 1998-10-08 Mci Communications Corp Method and apparatus for automated node-based normalization after network restoration
US6215867B1 (en) 1997-06-20 2001-04-10 At&T Corp. Telecommunications network architecture with rapid restoration
US6061807A (en) * 1997-06-27 2000-05-09 International Business Machines Corporation Methods systems and computer products for error recovery of endpoint nodes
US7187926B1 (en) * 1997-07-01 2007-03-06 Deutsche Telekom Ag Method and system for controlling the use of satellite transmission capacity in terrestrial networks
US6457050B1 (en) * 1997-08-01 2002-09-24 Mci Communications Corporation System and method for dynamically restoring communications within a network
US6377374B1 (en) * 1998-02-20 2002-04-23 Mci Communications Corporation Method apparatus and computer program product for optical network restoration
US6111672A (en) * 1998-02-20 2000-08-29 Mci Communications Corporation Method, apparatus, and computer program product for optical network restoration
WO1999043116A1 (en) * 1998-02-20 1999-08-26 Mci Worldcom, Inc. Method, apparatus, and computer program product for optical network restoration
US6188666B1 (en) * 1998-04-28 2001-02-13 At&T Corp. Restoration method for multiplexed circuits
US6324162B1 (en) 1998-06-03 2001-11-27 At&T Corp. Path-based restoration mesh networks
US6370110B1 (en) * 1998-09-16 2002-04-09 At&T Corp Back-up restoration technique for SONET/SHD rings
US6498778B1 (en) 1998-12-17 2002-12-24 At&T Corp. Optimizing restoration capacity
US6507649B1 (en) * 1998-12-18 2003-01-14 Ericsson Inc. Mechanism and method for distributing ISUP stacks over multiple loosely coupled processors
US7633854B2 (en) * 1999-01-15 2009-12-15 Cisco Technology, Inc. Method for routing information over a network
US20050135234A1 (en) * 1999-01-15 2005-06-23 Saleh Ali N. Method for routing information over a network
US6947854B2 (en) 2000-02-29 2005-09-20 Quadlogic Controls Corporation System and method for on-line monitoring and billing of power consumption
WO2001065823A1 (en) * 2000-02-29 2001-09-07 Quadlogic Controls Corporation System and method for on-line monitoring and billing of power consumption
US6594775B1 (en) * 2000-05-26 2003-07-15 Robert Lawrence Fair Fault handling monitor transparently using multiple technologies for fault handling in a multiple hierarchal/peer domain file server with domain centered, cross domain cooperative fault handling mechanisms
US6392989B1 (en) * 2000-06-15 2002-05-21 Cplane Inc. High speed protection switching in label switched networks through pre-computation of alternate routes
US8452555B2 (en) 2001-02-28 2013-05-28 Quadlogic Controls Corporation Apparatus and methods for multi-channel metering
US6987735B2 (en) 2001-05-24 2006-01-17 International Business Machines Corporation System and method for enhancing the availability of routing systems through equal cost multipath
US20030147473A1 (en) * 2002-02-06 2003-08-07 Mitsubishi Denki Kabushiki Kaisha Digital signal transmitting device for switching a signal processor of a fault condition for a spare signal processor of a non-fault condition
US7133667B2 (en) * 2002-02-08 2006-11-07 Ntt Docomo, Inc. Communications system, communications device, and communications method
US20040203558A1 (en) * 2002-02-08 2004-10-14 Ntt Docomo, Inc. Communications system, communications device, and communications method
US7367055B2 (en) * 2002-06-11 2008-04-29 Motorola, Inc. Communication systems automated security detection based on protocol cause codes
US20030229803A1 (en) * 2002-06-11 2003-12-11 Comer Erwin P. Communication systems automated security detection based on protocol cause codes
US20040218525A1 (en) * 2003-04-29 2004-11-04 David Elie-Dit-Cosaque Protection scheme for a communications network under multiple failures
US7453824B1 (en) * 2003-07-10 2008-11-18 Sprint Communications Company L.P. Method and system for identifying optimal mapping in a network
US7839885B2 (en) * 2005-04-25 2010-11-23 Lsi Corporation Connection memory for tributary time-space switches
US20060239262A1 (en) * 2005-04-25 2006-10-26 Lsi Logic Corporation Connection memory for tributary time-space switches
US10491748B1 (en) 2006-04-03 2019-11-26 Wai Wu Intelligent communication routing system and method
US7769018B2 (en) * 2006-07-11 2010-08-03 International Business Machines Corporation Establishing two or more simultaneous channels of communication with a user
US20080013570A1 (en) * 2006-07-11 2008-01-17 Smith Barton A Establishing Two Or More Simultaneous Channels of Communication With A User
TWI395441B (en) * 2006-07-11 2013-05-01 Ibm Establishing two or more simultaneous channels of communication with a user
US20080259805A1 (en) * 2007-04-17 2008-10-23 John Andrew Canger Method and apparatus for managing networks across multiple domains
US9081653B2 (en) 2011-11-16 2015-07-14 Flextronics Ap, Llc Duplicated processing in vehicles
US9674342B2 (en) * 2012-03-30 2017-06-06 British Telecommunications Public Limited Company Cable damage detection
US20150085994A1 (en) * 2012-03-30 2015-03-26 British Telecommunications Public Limited Company Cable damage detection
US20150092538A1 (en) * 2013-09-27 2015-04-02 Cisco Technology, Inc. Handling unacceptable asymmetrical communication paths in computer networks
US9344355B2 (en) * 2013-09-27 2016-05-17 Cisco Technology, Inc. Handling unacceptable asymmetrical communication paths in computer networks
US9838245B2 (en) * 2014-01-15 2017-12-05 Dell Products, L.P. Systems and methods for improved fault tolerance in solicited information handling systems
US20150200802A1 (en) * 2014-01-15 2015-07-16 Dell Products, L.P. Systems and methods for improved fault tolerance in solicited information handling systems

Also Published As

Publication number Publication date
DE69131041D1 (en) 1999-04-29
CA2056298A1 (en) 1992-07-04
CA2056298C (en) 1996-06-25
KR920015771A (en) 1992-08-27
ES2130134T3 (en) 1999-07-01
JP3009769B2 (en) 2000-02-14
ATE178177T1 (en) 1999-04-15
JPH04304731A (en) 1992-10-28
HK1011810A1 (en) 1999-07-16
AU626226B1 (en) 1992-07-23
EP0494513B1 (en) 1999-03-24
DE69131041T2 (en) 1999-10-21
EP0494513A3 (en) 1994-10-26
KR960007668B1 (en) 1996-06-08
EP0494513A2 (en) 1992-07-15

Similar Documents

Publication Publication Date Title
US5182744A (en) Telecommunications network restoration architecture
US5058105A (en) Network alternate routing arrangement
US5898667A (en) SS7 network management primeship
US7903544B2 (en) Private network link verification procedure in free space optical communication network
US6947376B1 (en) Local information-based restoration arrangement
US5796718A (en) Method of and system for intelligent access line protect switching
US20020054593A1 (en) Access network system
EP1093257A1 (en) Method and apparatus for fast distributed restoration of a communication network
CA2267689C (en) Asynchronous transfer mode layer automatic protection switching mechanism for atm permanent virtual connections
US6687230B1 (en) Routing system and method
US6370110B1 (en) Back-up restoration technique for SONET/SHD rings
JPH11507780A (en) Method and system for identifying a fault location in a communication network
EP0870413A1 (en) Restoration systems for an optical telecommunications network
JP2004533142A (en) Reuse of bandwidth reservation in protection and restoration techniques for dynamically allocated rings
EP1995918A1 (en) Alternative route selection in Telecommunications networks
US7009934B1 (en) Method and apparatus for rerouting an optical network upon fault
US6813240B1 (en) Method of identifying low quality links in a telecommunications network
US6215867B1 (en) Telecommunications network architecture with rapid restoration
EP0621734B1 (en) Method and apparatus for monitoring telecommunication networks
US6717939B1 (en) Virtual transport server in a telecommunication network
US6728204B1 (en) Arrangement, system and method relating to data/telecommunication
US6188666B1 (en) Restoration method for multiplexed circuits
US6418117B1 (en) Out of band messaging in a DRA network
US20070093249A1 (en) SS7 Link failover communications over existing cellular networks
US6614901B1 (en) Method and system for a scaleable virtual switch

Legal Events

Date Code Title Description
AS Assignment

Owner name: AMERICAN TELEPHONE AND TELEGRAPH COMPANY, A CORP.

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST.;ASSIGNORS:ASKEW, JAMES D.;CHAO, CHIN-WANG;COCHRAN, DAVID R.;AND OTHERS;REEL/FRAME:005599/0683;SIGNING DATES FROM 19910123 TO 19910125

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12