Extending SONET/SDH automatic protection switching

Information

  • Patent Grant
  • 7570583
  • Patent Number
    7,570,583
  • Date Filed
    Tuesday, February 15, 2005
    19 years ago
  • Date Issued
    Tuesday, August 4, 2009
    15 years ago
Abstract
The invention provides a method and system for coupling a SONET/SDH network to a routing network that does not have a single point of failure. Multiple routers are coupled between the SONET/SDH network and the routing network, one for each data path; for example, a first router for the working data path and a second router for the protection data path. The routers intercommunicate to force APS to switch data paths bidirectionally, so as to allow only a single router for each data path.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


This invention relates to extending SONET/SDH Automatic Protection Switching.


2. Related Art


In a SONET/SDH communication network, redundancy is achieved by assigning one protection data path for a set of N working data paths. In network equipment for SONET/SDH networks using a “one-plus-one” model, there is one protection data. path for each working data path, to provide a redundancy of 100% of working capacity. When a SONET/SDH network link is requested, both working and protection data paths are allocated.


As used herein “SONET/SDH” refers both to the SONET specification and to the SDH specification, and to specifications substantially equivalent thereto.


A switching protocol known as APS (automatic protection switching) provides the capability for the protection data path to substitute for the working data path when necessary. SONET/SDH network connections are bidirectional, so the APS protocol can operate in one of two ways. The APS protocol can be bidirectional, in which case the two directions of the network connection between two SONET/SDH network elements are switched together, or it can be unidirectional, in which case the two directions of the network connection between two SONET/SDH network elements can be switched separately.


One problem in the art occurs when coupling a SONET/SDH network to a layer-three router, such as a router in a routing network. The coupling between the SONET/SDH network and the router is a single point of failure, and the single router is itself another single point of failure. It would be desirable to replicate the SONET/SDH network's use of protection data paths in the routing network, such as by using more than one router to make the connection between the routing network and the SONET/SDH network. Using a plurality of such routers would prevent any one router from being a single point of failure.


As used herein, the phrase “routing network” includes a bridging, switching, or routing aspect of a network. This phrase is intended to include networks in which a router (or bridge, switch, or brouter) is used to forward messages. For example, layer-two or layer-three operations in an ISO/OSI model network, as well as layer-four and layer-five operations, are intended to be included. One example of such a network would be an IP network, and its routing protocols, such as the internet.


However, if multiple routers are used to make the connection between the routing network and the SONET/SDH network, routing to and from the working data path and the protection data path can be different. This makes it difficult to route between the SONET/SDH network and the routing network if data uses the working data path in one direction and the protection data path in the other direction. Much of the network equipment in use for present SONET/SDH networks only implements the APS protocol unidirectionally.


Accordingly, it would be advantageous to provide a method and system for coupling a SONET/SDH network to a routing network that does not have a single point of failure. This advantage is achieved in an embodiment of the invention in which multiple routers are coupled between the SONET/SDH network and the routing network, one for each data path, with the routers intercommunicating to force APS to allow only a single router for each bidirectional data path.


SUMMARY OF THE INVENTION

The invention provides a method and system for coupling a SONET/SDH network to a routing network that does not have a single point of failure. Multiple routers are coupled between the SONET/SDH network and the routing network, one for each data path; for example, a first router for the working data path and a second router for the protection data path. The routers intercommunicate to force APS to switch data paths bidirectionally, so as to allow only a single router for each data path.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows a block diagram of a system for coupling a SONET/SDH network to a routing network using multiple routers.



FIG. 2 shows a process flow diagram for an inter-router protocol which forces APS to switch data paths bidirectionally, so as to couple only a single router to each data path.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. Those skilled in the art would recognize after perusal of this application that embodiments of the invention can be implemented using general or special purpose processors, or other circuits adapted to particular process steps and data structures described herein, and that implementation of the process steps and data structures described herein would not require undue experimentation or further invention.


System Elements



FIG. 1 shows a block diagram of a system for coupling a SONET/SDH network to a routing network using multiple routers.


A system 100 includes a first NE (network equipment) element 110, a second NE element 110, a first router 120, a second router 120, and a routing network 130. In a preferred embodiment, the second NE element 110 comprises an ADM (add-drop multiplexer). ADMs are known in the art of SONET/SDH network equipment.


The first NE element 110 is coupled to the second NE element 110 using a working data path 140 and a protection data path 150. The working data path 140 is bidirectional and includes a first unidirectional working data path 141 and second unidirectional working data path 142. Similarly, the protection data path 150 is bidirectional and includes a first unidirectional protection data path 151 and second unidirectional protection data path 152.


The second NE element 110 is collectively coupled to the first router 120 and the second router 120 using a working data path 140 and a protection data path 150. The working data path 140 is bidirectional and includes a first unidirectional working data path 141 A and second unidirectional working data path 142 B. Data path 141 A transmits data from the first router 120 to the second NE element 110. Data path 142 B transmits data from the second NE element 110 to the first router 120. Similarly, the protection data path 150 is bidirectional and includes a first unidirectional protection data path 151 C and second unidirectional protection data path 152 D. Data path 151 C transmits data from the second router 120 to the second NE element 110. Data path 152 D transmits data from the second NE element 110 to the second router 120.


The first router 120 is coupled to the second router 120 using a communication path 160 in the routing network 130. In a preferred embodiment, the communication path 160 includes a single LAN (local-access network) to which the first router 120 and the second router 120 are both directly coupled.


The first router 120 and the second router 120 are both coupled to the routing network 130 and are configured to route messages from and to end-station devices 170 coupled to the routing network 130, and from and to the second NE element 110. Thus, the first router 120 and the second router 120 operate in conjunction with the second NE element 110 to transfer data between the routing network 130 and a SONET/SDH network 180 coupled to the first NE element 110 and the second NE element 110.


Method of Operation



FIG. 2 shows a process flow diagram for an inter-router protocol which forces APS to switch data paths bidirectionally, so as to couple only a single router to each data path.


A method 200 includes flow points and process steps as described herein, and is performed in conjunction by the second NE element 110, the first router 120, and the second router 120.


At a flow point 210, the second NE element 110 is transmitting data between the routing network 130 and the SONET/SDH network 180 using the working data path 140. The protection data path 150 is held in reserve to protect against the possibility that the working data path 140 will fail, or will sufficiently degrade that the protection data path 150 becomes superior for transmitting data. If the protection data path 150 is used for transmitting data, the working data path 140 will take over the previous role of the protection data path 150. The working data path 140 will thus be held in reserve to protect against the possibility that the protection data path 150 will fail or degrade.


As part of the APS protocol, the second NE element 110 selects one of the two incoming data paths from the routing network 130 (data path 141 A or data path 151 C) for transmission to the SONET/SDH network 180. The second NE element 110 receives data from the selected data path and transmits that data on both of its outgoing data paths (working data path 140 or protection data path 150). Similarly, the second NE element 110 selects on of the two incoming data paths from the SONET/SDH network 180 (working data path 140 or protection data path 150) for transmitting data to the routing network 130. The second NE element 110 receives data from the selected path and transmits that data on both of its outgoing data paths (data path 142 B or data path 152 D).


As part of the APS protocol, the second NE element 110 receives a sequence of K1 and K2 bytes on the data path it does not select for receiving data. Thus, when the second NE element 110 is receiving data from the first NE element 110 on the working data path 140, it is receiving the K1 and K2 bytes on the protection data path 150. Similarly, when the second NE element 110 is receiving data from the first router 120 on the data path 141 A, it is receiving the K1 and K2 bytes on the data path 151 C.


The K1 and K2 bytes are used in the APS protocol to indicate protocol commands, including protocol commands for switching between the working data path 140 (or if there is more than one working data path 140, a selected one thereof) and the protection data path 150. These commands can include one of the following:

    • LOS (loss of signal)—The signal has been lost for the working data path 140.
    • LOF (loss of frame)—The frame has been lost for the working data path 140.
    • AIS (alarm indication signal)—This signal indicates an alarm for the working data path 140.
    • BER (bit error rate)—The bit error rate for the working data path 140 exceeds a selected threshold.


Thus, at the flow point 210, the data path 141 A transmits actual data, the data path 142 B and the data path 152 D transmit (the same) actual data, and the data path 151 C transmits the K1 and K2 bytes. In normal operation, the K1 and K2 bytes indicate that all data paths are working properly.


The APS protocol is further described in the document GR-253-CORE, available from Bellcore, and known ITU documents specifying and documenting SDH. These documents is hereby incorporated by reference as if fully set forth herein.


From the flow point 210, one of four possible line failures (or degradations) can occur.


Data Path A


At a flow point 220, the data path 141 A fails or degrades.


At a step 221, the second NE element 110 notices the failure or degradation of the data path 141 A.


At a step 222, the second NE element 110 switches from receiving data on its working data path 140 to its protection data path 150. Thus, the second NE element 110 switches from receiving data on the data path 141 A to receiving data on the data path 151 C. As part of performing this step 222, the second NE element 110 sends K1 and K2 bytes on the data path 152 D, using the APS protocol, indicating the switch.


At a step 223, the second router 120 receives the K1 and K2 bytes on the data path 152 D.


At a step 224, the second router 120 informs the first router 120 of the change and disables the connection between the first router 120 and the second NE element 110, using a DISABLE protocol message.


At a step 225, the first router 120 receives the DISABLE protocol message, and responsive thereto, stops listening for transmitted data on the data path 142 B.


At a step 226, the first router 120 acknowledges DISABLE protocol message, using a DISABLE-ACK protocol message it sends to the second router 120.


At a step 227, the second router 120 starts listening for transmitted data on the data path 152 D.


At a step 228, the first router 120 and the second router 120 each change their routing tables to reflect the change in connection between the routing network 130 and the SONET/SDH network 180.


This change to the routing tables for the first router 120 and the second router 120 is seen by the rest of the routing network 130 according to routing protocols used by the routing network 130 and implemented by the first router 120 and the second router 120. Many such routing protocols, such as the IGRP routing protocol, are known in the art of computer networks.


The method continues at the flow point 210.


Data Path B


At a flow point 230, the data path 142 B fails or degrades.


At a step 231, the first router 120 notices the failure or degradation of the data path 142 B.


At a step 232, the first router 120 informs the second router 120 of the change, using a LINE-STATE-CHANGE protocol message.


At a step 233, the second router 120 evaluates a priority for the LINE-STATE-CHANGE protocol message, and determines to act on its highest priority. If the second router 120 determines that the LINE-STATE-CHANGE protocol message is not its highest priority, it performs and completes some other task, and the method returns to repeat this step 233. If the second router 120 determines that the LINE-STATE-CHANGE protocol message is its highest priority, the method continues with the step 234.


The second router 120 might determine whether the LINE-STATE-CHANGE protocol message is its highest priority responsive to a number of factors, including (a) whether there is another state change requiring more immediate action, or (b) whether the state change for the data path 142 B is sufficient to warrant propagating the LINE-STATE-CHANGE protocol message as described herein.


At a step 234, the second router 120 disables the connection between the first router 120 and the second NE element 110, using a DISABLE protocol message.


At a step 235, the first router 120 receives the DISABLE protocol message, and responsive thereto, sends an AIS protocol message (using the APS protocol) to the second NE element 110 on the data path 141 A.


At a step 236, the second NE element 110 receives the AIS protocol message, and responsive thereto, switches from its working data path 140 to its protection data path 150. Thus, the second NE element 110 switches from receiving data on the data path 141 A to receiving data on the data path 151 C.


At a step 237, the first router 120 acknowledges the DISABLE protocol message, using a DISABLE-ACK protocol message it sends to the second router 120.


At a step 238, similar to the step 228, the first router 120 and the second router 120 each change their routing tables to reflect the change in connection between the routing network 130 and the SONET/SDH network 180.


At a step 239, the second router 120 starts listening for transmitted data on the data path 152 D.


The method continues at the flow point 210.


Data Path C


At a flow point 240, the data path 151 C fails or degrades.


At a step 241, the second NE element 110 notices the failure or degradation of the data path 151 C.


Because the data path 151 C is a protection data path 150, the second NE element 110 takes no action responsive to the failure or degradation thereof.


The method continues at the flow point 210.


Data Path D


At a flow point 250, the data path 152 D fails or degrades.


At a step 251, the second router 120 notices the failure or degradation of the data path 152 D.


Because the data path 152 D is a protection data path 150, the second router 120 takes no action responsive to the failure or degradation thereof.


The method continues at the flow point 210.


Reversal of Data Path Roles


As shown herein, when the working data path fails or degrades, use is switched over to the protection data path. When the working data path is recovered, the APS protocol can revert back to the working data path, by essentially reversing the switching steps shown herein. Alternatively, the APS protocol can reverse the roles of the working data path and the protection data path, thus making the old protection data path serve the role of a new working data path and making the old working data path serve the role of a new protection data path.


ALTERNATIVE EMBODIMENTS

Although preferred embodiments are disclosed herein, many variations are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those skilled in the art after perusal of this application.


In particular, although a preferred embodiment is shown using a “one plus one” system with the APS protocol, variants using a “one to N” system are within the scope and spirit of the invention. Those skilled in the art would recognize that such systems could be made and used based on this application, and would not require undue experiment or further invention.

Claims
  • 1. A method for communicatively coupling a first network to a second network by using a first device and a second device, the method comprising the steps of: causing first data to be transmitted and second data to be received over a first bidirectional data path but not over a second bidirectional data path, wherein: said first bidirectional data path communicatively couples said first device to said second network;said first device is communicatively coupled to said first network;said second bidirectional data path communicatively couples said second device to said second network;said second device is communicatively coupled to said first network;said first network is associated with a first network type, said second network is associated with a second network type, and said first network type is different than said second network type;based on transmitting said first data and receiving said second data over said first bidirectional data path, determining that one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied: causing said first data to no longer be transmitted and said second data to no longer be received over said first bidirectional data path; andcausing said first data to be transmitted and said second data to be received over said second bidirectional data path but not over said first bidirectional data path;based on transmitting said first data and receiving said second data over said second bidirectional data path, determining that said one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied: causing said first data to no longer be transmitted and said second data to no longer be received over said second bidirectional data path; andcausing said first data to be transmitted and said second data to be received over said first bidirectional data path but not over said second bidirectional data path.
  • 2. The method as recited in claim 1, wherein: said first bidirectional data path includes a first unidirectional sending data path and a first unidirectional receiving data path;said first bidirectional data path is used for transmitting and receiving data between said first network and said second network;said second bidirectional data path includes a second unidirectional sending data path and a second unidirectional receiving data path;said second bidirectional data path is used for transmitting and receiving information for use in determining that the one or more criteria are satisfied;the first network type is a SONET network type;the second network type is not SONET network type; andthe method further comprising the steps of:in response to determining that said one or more criteria are satisfied, causing said second device to send a command to said first device over a third data path; andwherein in response to receiving said command, said first device no longer transmits said first data and no longer receives said second data over said first bidirectional data path.
  • 3. The method as recited in claim 1, wherein; said first bidirectional data path is designated as a working data path;said second bidirectional data path is designated as a protection data path;said first device is a first router;said second device is a second router;said first network type is a routing network type;said second network type is a SONET/SDH network type; andsaid one or more criteria are selected from the group consisting of (a) a first criterion that indicates a failure of a particular data path over which said first data is being transmitted and said second data is being received and (b) a second criterion that indicates an unacceptable degradation in transmitting said first data and receiving said second data over said particular data path.
  • 4. The method as recited in claim 1, wherein: said first bidirectional data path includes a first unidirectional sending data path and a first unidirectional receiving data path;the step of causing first data to be transmitted and second data to be received over said first bidirectional data path but not over said second bidirectional data path includes the steps of: causing said first data to be transmitted from said first device to said second network over said first unidirectional sending data path; andcausing said second data to be received from said second network to said first device over said first unidirectional receiving data path;said second bidirectional data path includes a second unidirectional sending data path and a second unidirectional receiving data path; andthe step of causing said first data to be transmitted and said second data to be received over said second bidirectional data path but not over said first bidirectional data path includes the steps of: causing said first data to be transmitted from said first device to said second network over said second unidirectional sending data path; andcausing said second data to be received from said second network to said first device over said second unidirectional receiving data path.
  • 5. The method as recited in claim 1, further comprising the steps of: causing third data to be transmitted and fourth data to be received over a third bidirectional data path but not over said second bidirectional data path, wherein said third bidirectional data path communicatively couples a third device to said second network;based on transmitting said third data and receiving said fourth data over said third bidirectional data path, determining that said one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied, causing said third data to no longer be transmitted and said fourth data to no longer be received over said third bidirectional data path; andcausing said third data to be transmitted and said fourth data to be received over said second bidirectional data path but not over said third bidirectional data path.
  • 6. An apparatus for communicatively coupling a first network to a second network by using a first device and a second device, the apparatus comprising: means for causing first data to be transmitted and second data to be received over a first bidirectional data path but not over a second bidirectional data path, wherein: said first bidirectional data path communicatively couples said first device to said second network;said first device is communicatively coupled to said first network;said second bidirectional data path communicatively couples said second device to said second network;said second device is communicatively coupled to said first network;said first network is associated with a first network type, said second network is associated with a second network type, and said first network type is different than said second network type;means for determining, based on transmitting said first data and receiving said second data over said first bidirectional data path, that one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied, means for causing said first data to no longer be transmitted and said second data to no longer be received over said first bidirectional data path; andmeans for causing said first data to be transmitted and said second data to be received over said second bidirectional data path but not over said first bidirectional data path;means for determining, based on transmitting said first data and receiving said second data over said second bidirectional data path, that said one or more criteria are satisfied;means for causing, in response to determining that said one or more criteria are satisfied, said first data to no longer be transmitted and said second data to no longer be received over said second bidirectional data path; andmeans for causing, in response to determining that said one or more criteria are satisfied, said first data to be transmitted and said second data to be received over said first bidirectional data path but not over said second bidirectional data path.
  • 7. The apparatus as recited in claim 6, wherein: said first bidirectional data path includes a first unidirectional sending data path and a first unidirectional receiving data path;said first bidirectional data path is used for transmitting and receiving data between said first network and said second network;said second bidirectional data path includes a second unidirectional sending data path and a second unidirectional receiving data path;said second bidirectional data path is used for transmitting and receiving information for use in determining that the one or more criteria are satisfied;the first network type is a SONET network type;the second network type is not SONET network type; andthe apparatus further comprising:means for causing, in response to determining that said one or more criteria are satisfied, said second device to send a command to said first device over a third data path; andwherein in response to receiving said command, said first device no longer transmits said first data and no longer receives said second data over said first bidirectional data path.
  • 8. The apparatus as recited in claim 6, wherein; said first bidirectional data path is designated as a working data path;said second bidirectional data path is designated as a protection data path;said first device is a first router;said second device is a second router;said first network type is a routing network type;said second network type is a SONET/SDH network type; andsaid one or more criteria are selected from the group consisting of (a) a first criterion that indicates a failure of a particular data path over which said first data is being transmitted and said second data is being received and (b) a second criterion that indicates an unacceptable degradation in transmitting said first data and receiving said second data over said particular data path.
  • 9. The apparatus as recited in claim 6, wherein: said first bidirectional data path includes a first unidirectional sending data path and a first unidirectional receiving data path;the means for causing first data to be transmitted and second data to be received over said first bidirectional data path but not over said second bidirectional data path includes: means for causing said first data to be transmitted from said first device to said second network over said first unidirectional sending data path; andmeans for causing said second data to be received from said second network to said first device over said first unidirectional receiving data path;said second bidirectional data path includes a second unidirectional sending data path and a second unidirectional receiving data path; andthe means for causing said first data to be transmitted and said second data to be received over said second bidirectional data path but not over said first bidirectional data path includes: means for causing said first data to be transmitted from said first device to said second network over said second unidirectional sending data path; andmeans for causing said second data to be received from said second network to said first device over said second unidirectional receiving data path.
  • 10. An The apparatus as recited in claim 6, further comprising: means for causing third data to be transmitted and fourth data to be received over a third bidirectional data path but not over said second bidirectional data path, wherein said third bidirectional data path communicatively couples a third device to said second network;means for determining, based on transmitting said third data and receiving said fourth data over said third bidirectional data path, that said one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied, means for causing said third data to no longer be transmitted and said fourth data to no longer be received over said third bidirectional data path; andmeans for causing said third data to be transmitted and said fourth data to be received over said second bidirectional data path but not over said third bidirectional data path.
  • 11. A network equipment element configured for communicatively coupling a first network to a second network by using a first device and a second device, and configured to perform: causing first data to be transmitted and second data to be received over a first bidirectional data path but not over a second bidirectional data path, wherein: said first bidirectional data path communicatively couples said first device to said second network;said first device is communicatively coupled to said first network;said second bidirectional data path communicatively couples said second device to said second network;said second device is communicatively coupled to said first network;said first network is associated with a first network type, said second network is associated with a second network type, and said first network type is different than said second network type;based on transmitting said first data and receiving said second data over said first bidirectional data path, determining that one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied: causing said first data to no longer be transmitted and said second data to no longer be received over said first bidirectional data path; andcausing said first data to be transmitted and said second data to be received over said second bidirectional data path but not over said first bidirectional data path;based on transmitting said first data and receiving said second data over said second bidirectional data path, determining that said one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied: causing said first data to no longer be transmitted and said second data to no longer be received over said second bidirectional data path; andcausing said first data to be transmitted and said second data to be received over said first bidirectional data path but not over said second bidirectional data path.
  • 12. The network equipment element as recited in claim 11, wherein: said first bidirectional data path includes a first unidirectional sending data path and a first unidirectional receiving data path;said first bidirectional data path is used for transmitting and receiving data between said first network and said second network;said second bidirectional data path includes a second unidirectional sending data path and a second unidirectional receiving data path;said second bidirectional data path is used for transmitting and receiving information for use in determining that the one or more criteria are satisfied;the first network type is a SONET network type;the second network type is not SONET network type; andthe network equipment element configured to perform: in response to determining that said one or more criteria are satisfied, causing said second device to send a command to said first device over a third data path; andwherein in response to receiving said command, said first device no longer transmits said first data and no longer receives said second data over said first bidirectional data path.
  • 13. The network equipment element as recited in claim 11, wherein; said first bidirectional data path is designated as a working data path;said second bidirectional data path is designated as a protection data path;said first device is a first router;said second device is a second router;said first network type is a routing network type;said second network type is a SONET/SDH network type; andsaid one or more criteria are selected from the group consisting of (a) a first criterion that indicates a failure of a particular data path over which said first data is being transmitted and said second data is being received and (b) a second criterion that indicates an unacceptable degradation in transmitting said first data and receiving said second data over said particular data path.
  • 14. The network equipment element as recited in claim 11, wherein: said first bidirectional data path includes a first unidirectional sending data path and a first unidirectional receiving data path;further said network equipment element is further configured to perform: causing said first data to be transmitted from said first device to said second network over said first unidirectional sending data path; andcausing said second data to be received from said second network to said first device over said first unidirectional receiving data path;said second bidirectional data path includes a second unidirectional sending data path and a second unidirectional receiving data path; and further said network equipment element is further configured to perform:causing said first data to be transmitted from said first device to said second network over said second unidirectional sending data path; andcausing said second data to be received from said second network to said first device over said second unidirectional receiving data path.
  • 15. The network equipment element as recited in claim 11, further configured to perform: causing third data to be transmitted and fourth data to be received over a third bidirectional data path but not over said second bidirectional data path, wherein said third bidirectional data path communicatively couples a third device to said second network;based on transmitting said third data and receiving said fourth data over said third bidirectional data path, determining that said one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied, causing said third data to no longer be transmitted and said fourth data to no longer be received over said third bidirectional data path; andcausing said third data to be transmitted and said fourth data to be received over said second bidirectional data path but not over said third bidirectional data path.
  • 16. A system for communicatively coupling a first network to a second network, the system comprising: a first device that is communicatively coupled to said second network through a first bidirectional data path, wherein said first device is communicatively coupled to said first network;a second device that is communicatively coupled to said second network through a second bidirectional data path, wherein said second device is communicatively coupled to said first network;wherein:said first network is associated with a first network type, said second network is associated with a second network type, and said first network type is different than said second network type;said first device is configured to transmit first data and receive second data over said first bidirectional data path but said second device is not configured to transmit first data or receive second data said data over said second bidirectional data path;said second device is configured to: determine, based on said first data that is transmitted and said second data that is received over said first bidirectional data path, that one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied: cause said first data to no longer be transmitted and said second data to no longer be received over said first bidirectional data path; andcause said first data to be transmitted and said second data to be received over said second bidirectional data path but not over said first bidirectional data path;said first device is configured to: determine, based on said first data that is transmitted and said second data that is received over said second bidirectional data path, that said one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied: cause said first data to no longer be transmitted and said second data to no longer be received over said second bidirectional data path; andcause said first data to be transmitted and said second data to be received over said first bidirectional data path but not over said second bidirectional data path.
  • 17. The system as recited in claim 16, wherein: said first bidirectional data path includes a first unidirectional sending data path and a first unidirectional receiving data path;said first bidirectional data path is used for transmitting and receiving data between said first network and said second network;said second bidirectional data path includes a second unidirectional sending data path and a second unidirectional receiving data path;said second bidirectional data path is used for transmitting and receiving information for use in determining that the one or more criteria are satisfied;the first network type is a SONET network type;the second network type is not SONET network type;said second device is configured to send, in response to determining that said one or more criteria are satisfied, a command to said first device over a third data path; andsaid first device is configured to, in response to receiving said command, no longer transmit said first data and no longer receive said second data over said first bidirectional data path.
  • 18. The system as recited in claim 16, wherein: said first bidirectional data path is designated as a working data path;said second bidirectional data path is designated as a protection data path;said first device is a first router;said second device is a second router;said first network type is a routing network type;said second network type is a SONET/SDH network type; andsaid one or more criteria are selected from the group consisting of (a) a first criterion that indicates a failure of a particular data path over which said first data is being transmitted and said second data is being received and (b) a second criterion that indicates an unacceptable degradation in transmitting said first data and receiving said second data over said particular data path.
  • 19. The system as recited in claim 16, wherein: said first bidirectional data path includes a first unidirectional sending data path and a first unidirectional receiving data path;said first device being configured to transmit said first data and receive said second data over a first bidirectional data path includes being configured to transmit said first data to said second network over said first unidirectional sending data path and to receive said second data from said second network over said first unidirectional receiving data path;said second bidirectional data path includes a second unidirectional sending data path and a second unidirectional receiving data path; andsaid second device being configured to transmit said first data and receive said second data over said second bidirectional data path includes being configured to transmit said first data to said second network over said second unidirectional sending data path and to receive said second data from said second network over said second unidirectional receiving data path.
  • 20. The system as recited in claim 16, further comprising: a third device that is communicatively coupled to said second network through a third bidirectional data path, wherein said third device is communicatively coupled to said first network;wherein:said third device is configured to transmit third data and receive fourth data over said third bidirectional data path but said second device is not configured to transmit said third data or receive fourth data over said second bidirectional data path;said second device is configured to: determine, based on said third data that is transmitted and said fourth data that is received over said third bidirectional data path, that one or more criteria are satisfied;in response to determining that said one or more criteria are satisfied, cause said third data to no longer be transmitted and said fourth data to no longer be received over said third bidirectional data path; andcause said third data to be transmitted and said fourth data to be received over said second bidirectional data path but not over said third bidirectional data path.
Parent Case Info

This application claims domestic priority under 35 U.S.C. §120 as a continuation of prior U.S. non-provisional application Ser. No. 08/986,250, filed Dec. 5, 1997 now abandoned, entitled “EXTENDNG SONET/SDH AUTOMATIC PROTECTION SWITCHING,” naming Robert Broberg and David Getchell as inventors, the entire disclosure of which is hereby incorporated by reference for all purposes as if fully set forth herein.

US Referenced Citations (242)
Number Name Date Kind
4131767 Weinstein Dec 1978 A
4161719 Parikh et al. Jul 1979 A
4316284 Howson Feb 1982 A
4397020 Howson Aug 1983 A
4419728 Larson Dec 1983 A
4424565 Larson Jan 1984 A
4437087 Petr Mar 1984 A
4438511 Baran Mar 1984 A
4439763 Limb Mar 1984 A
4445213 Baugh et al. Apr 1984 A
4446555 Devault et al. May 1984 A
4456957 Schieltz Jun 1984 A
4464658 Thelen Aug 1984 A
4499576 Fraser Feb 1985 A
4506358 Montgomery Mar 1985 A
4507760 Fraser Mar 1985 A
4532626 Flores et al. Jul 1985 A
4644532 George et al. Feb 1987 A
4646287 Larson et al. Feb 1987 A
4677423 Benvenuto et al. Jun 1987 A
4679189 Olson et al. Jul 1987 A
4679227 Hughes-Hartogs Jul 1987 A
4723267 Jones et al. Feb 1988 A
4731816 Hughes-Hartogs Mar 1988 A
4750136 Arpin et al. Jun 1988 A
4757495 Decker et al. Jul 1988 A
4763191 Gordon et al. Aug 1988 A
4769810 Eckberg, Jr. et al. Sep 1988 A
4769811 Eckberg, Jr. et al. Sep 1988 A
4771425 Baran et al. Sep 1988 A
4819228 Baran et al. Apr 1989 A
4827411 Arrowood et al. May 1989 A
4833706 Hughes-Hartogs May 1989 A
4835737 Herrig et al. May 1989 A
4879551 Georgiou et al. Nov 1989 A
4893306 Chao et al. Jan 1990 A
4903261 Baran et al. Feb 1990 A
4905233 Cain et al. Feb 1990 A
4922486 Lidinsky et al. May 1990 A
4933937 Konishi Jun 1990 A
4960310 Cushing Oct 1990 A
4962497 Ferenc et al. Oct 1990 A
4962532 Kasirai et al. Oct 1990 A
4965767 Kinoshita et al. Oct 1990 A
4965772 Daniel et al. Oct 1990 A
4970678 Sladowski et al. Nov 1990 A
4979118 Kheradpir Dec 1990 A
4980897 Decker et al. Dec 1990 A
4991169 Davis et al. Feb 1991 A
4996685 Farese et al. Feb 1991 A
5003595 Collins et al. Mar 1991 A
5014265 Hahne et al. May 1991 A
5020058 Holden et al. May 1991 A
5033076 Jones et al. Jul 1991 A
5034919 Sasai Jul 1991 A
5054034 Hughes-Hartogs Oct 1991 A
5059925 Weisbloom Oct 1991 A
5072449 Enns et al. Dec 1991 A
5088032 Bosack Feb 1992 A
5095480 Fenner Mar 1992 A
RE33900 Howson Apr 1992 E
5115431 Williams et al. May 1992 A
5115495 Tsuchiya et al. May 1992 A
5128926 Perlman et al. Jul 1992 A
5128945 Enns et al. Jul 1992 A
5136580 Videlock et al. Aug 1992 A
5166930 Braff et al. Nov 1992 A
5189662 Kleine-Altekamp Feb 1993 A
5199049 Wilson Mar 1993 A
5206886 Bingham Apr 1993 A
5208811 Kashio et al. May 1993 A
5212686 Joy et al. May 1993 A
5224099 Corbalis et al. Jun 1993 A
5226120 Brown et al. Jul 1993 A
5228062 Bingham Jul 1993 A
5229994 Balzano et al. Jul 1993 A
5233604 Ahmadi et al. Aug 1993 A
5237564 Lespagnol et al. Aug 1993 A
5241682 Bryant et al. Aug 1993 A
5243342 Kattemalalavadi et al. Sep 1993 A
5243596 Port et al. Sep 1993 A
5247516 Bernstein et al. Sep 1993 A
5249178 Kurano et al. Sep 1993 A
5253251 Aramaki Oct 1993 A
5255291 Holden et al. Oct 1993 A
5260933 Rouse Nov 1993 A
5260978 Fleischer et al. Nov 1993 A
5268592 Bellamy et al. Dec 1993 A
5268900 Hluchyj et al. Dec 1993 A
5271004 Proctor et al. Dec 1993 A
5274631 Bhardwaj Dec 1993 A
5274635 Rahman et al. Dec 1993 A
5274643 Fisk Dec 1993 A
5280470 Buhrke et al. Jan 1994 A
5280480 Pitt et al. Jan 1994 A
5280500 Mazzola et al. Jan 1994 A
5283783 Nguyen et al. Feb 1994 A
5287103 Kasprzyk et al. Feb 1994 A
5287453 Roberts Feb 1994 A
5291482 McHarg et al. Mar 1994 A
5305311 Lyles Apr 1994 A
5307343 Bostica et al. Apr 1994 A
5309437 Perlman et al. May 1994 A
5311509 Heddes et al. May 1994 A
5313454 Bustini et al. May 1994 A
5313582 Hendel et al. May 1994 A
5317562 Nardin et al. May 1994 A
5319644 Liang Jun 1994 A
5325358 Goeldner Jun 1994 A
5325504 Tipley et al. Jun 1994 A
5327421 Hiller et al. Jul 1994 A
5331637 Francis et al. Jul 1994 A
5335224 Cole et al. Aug 1994 A
5345445 Hiller et al. Sep 1994 A
5345446 Hiller et al. Sep 1994 A
5359592 Corbalis et al. Oct 1994 A
5361250 Nguyen et al. Nov 1994 A
5361256 Doeringer et al. Nov 1994 A
5361259 Hunt et al. Nov 1994 A
5365524 Hiller et al. Nov 1994 A
5367517 Cidon et al. Nov 1994 A
5371852 Attanasio et al. Dec 1994 A
5386567 Lien et al. Jan 1995 A
5390170 Sawant et al. Feb 1995 A
5390175 Hiller et al. Feb 1995 A
5394394 Crowther et al. Feb 1995 A
5394402 Ross Feb 1995 A
5400325 Chatwani et al. Mar 1995 A
5408469 Opher et al. Apr 1995 A
5416842 Aziz May 1995 A
5422880 Heitkamp et al. Jun 1995 A
5422882 Hiller et al. Jun 1995 A
5423002 Hart Jun 1995 A
5426636 Hiller et al. Jun 1995 A
5428607 Hiller et al. Jun 1995 A
5430715 Corbalis et al. Jul 1995 A
5430729 Rahnema Jul 1995 A
5432784 Ozveren Jul 1995 A
5436886 McGill Jul 1995 A
5442457 Najafi Aug 1995 A
5442630 Gagliardi et al. Aug 1995 A
5446735 Tobagi et al. Aug 1995 A
5448559 Hayter et al. Sep 1995 A
5452294 Natarajan Sep 1995 A
5452297 Hiller et al. Sep 1995 A
5473599 Li et al. Dec 1995 A
5473607 Hausman et al. Dec 1995 A
5477541 White et al. Dec 1995 A
5479608 Richardson Dec 1995 A
5485455 Dobbins et al. Jan 1996 A
5490140 Abensour et al. Feb 1996 A
5490258 Fenner Feb 1996 A
5491687 Christensen et al. Feb 1996 A
5491804 Heath et al. Feb 1996 A
5497368 Reijnierse et al. Mar 1996 A
5504747 Sweasey Apr 1996 A
5509006 Wilford et al. Apr 1996 A
5517494 Green May 1996 A
5519704 Farinacci et al. May 1996 A
5519858 Walton et al. May 1996 A
5524254 Morgan et al. Jun 1996 A
5526489 Nilakantan et al. Jun 1996 A
5530963 Moore et al. Jun 1996 A
5535195 Lee Jul 1996 A
5539734 Burwell et al. Jul 1996 A
5541911 Nilakantan et al. Jul 1996 A
5546370 Ishikawa Aug 1996 A
5550816 Hardwick et al. Aug 1996 A
5555244 Gupta et al. Sep 1996 A
5561669 Lenney et al. Oct 1996 A
5583862 Callon Dec 1996 A
5590122 Sandorfi et al. Dec 1996 A
5592470 Rudrapatna et al. Jan 1997 A
5598532 Liron Jan 1997 A
5598581 Daines et al. Jan 1997 A
5600798 Cherukuri et al. Feb 1997 A
5602770 Ohira Feb 1997 A
5604868 Komine et al. Feb 1997 A
5608726 Virgile Mar 1997 A
5617417 Sathe et al. Apr 1997 A
5617421 Chin et al. Apr 1997 A
5630125 Zellweger May 1997 A
5631908 Saxe May 1997 A
5632021 Jennings et al. May 1997 A
5633865 Short May 1997 A
5634010 Ciscon et al. May 1997 A
5638359 Peltola et al. Jun 1997 A
5640399 Rostoker et al. Jun 1997 A
5644713 Makishima Jul 1997 A
5644718 Belove et al. Jul 1997 A
5659684 Giavannoni et al. Aug 1997 A
5666353 Klausmeier et al. Sep 1997 A
5673265 Gupta et al. Sep 1997 A
5678006 Valizadeh et al. Oct 1997 A
5680116 Hashimoto et al. Oct 1997 A
5684797 Aznar et al. Nov 1997 A
5687324 Green et al. Nov 1997 A
5689506 Chiussi et al. Nov 1997 A
5691984 Gardner et al. Nov 1997 A
5694390 Yamato et al. Dec 1997 A
5712847 Hata Jan 1998 A
5715237 Akiyoshi Feb 1998 A
5724351 Chao et al. Mar 1998 A
5740097 Satoh Apr 1998 A
5740157 Demiray et al. Apr 1998 A
5742760 Picazo, Jr. et al. Apr 1998 A
5748186 Raman May 1998 A
5748617 McLain, Jr. May 1998 A
5754547 Nakazawa May 1998 A
5774698 Olnowich Jun 1998 A
5793745 Manchester Aug 1998 A
5796742 Klotzbach et al. Aug 1998 A
5802054 Bellenger Sep 1998 A
5835696 Hess Nov 1998 A
5835710 Nagami et al. Nov 1998 A
5841874 Kempke Nov 1998 A
5854903 Morrison et al. Dec 1998 A
5856981 Voelker Jan 1999 A
5859837 Crayford Jan 1999 A
5862338 Walker et al. Jan 1999 A
5867666 Harvey Feb 1999 A
5870382 Tounai et al. Feb 1999 A
5872780 Demiray et al. Feb 1999 A
5884017 Fee Mar 1999 A
5892924 Lyon et al. Apr 1999 A
5898686 Virgile Apr 1999 A
5898687 Harriman et al. Apr 1999 A
5903559 Acharya et al. May 1999 A
5905723 Varghese et al. May 1999 A
5909440 Ferguson et al. Jun 1999 A
5978115 Condict et al. Nov 1999 A
5996021 Civanlar et al. Nov 1999 A
6011780 Vaman et al. Jan 2000 A
6021112 Sugawara Feb 2000 A
6023733 Periasamy et al. Feb 2000 A
6032194 Gai et al. Feb 2000 A
6111877 Wilford et al. Aug 2000 A
6122272 Tomaszewski et al. Sep 2000 A
6144633 Ikeda et al. Nov 2000 A
6219739 Dutt et al. Apr 2001 B1
6229787 Byrne May 2001 B1
6246667 Ballintine et al. Jun 2001 B1
Foreign Referenced Citations (8)
Number Date Country
0384758 Aug 1990 EP
0431751 Jun 1991 EP
0567217 Oct 1993 EP
0570882 Nov 1993 EP
WO 9307569 Apr 1993 WO
WO 9307692 Apr 1993 WO
WO 9401828 Jan 1994 WO
WO 9520850 Aug 1995 WO
Related Publications (1)
Number Date Country
20050141415 A1 Jun 2005 US
Continuations (1)
Number Date Country
Parent 08986250 Dec 1997 US
Child 11059484 US