Implementations consistent with the principles of the invention relate generally to communications networks and, more particularly, to providing fast re-routing in communications networks.
A typical communications network includes many different types of network devices. For example, a typical communications network may include host devices, which act as the source or destination of a particular flow of traffic, routers and/or switches, which act to forward traffic flows toward their appropriate destinations, and security devices, which provide, for example, firewall or other security functionality. These different types of network devices may be interconnected via links.
When a link or path in the communications network fails, it is important that re-routing around the failed link or path occurs as quickly as possible so that the loss of traffic is minimized. When the network devices are communicating via Multi-Protocol Label Switching (MPLS) using Circuit Cross-Connect technology, the network devices are notified of a failure of a link or path via layer 2 signaling, which may take up to 10 seconds for the appropriate network devices to become aware of the failure and begin re-routing traffic. When network devices are notified of a failure of a link or path via layer 3 signaling, it may take up to a minute for the appropriate network devices to become aware of the failure.
In a first implementation consistent with the principles of the invention, a method includes determining, via a provider device, that a failure has occurred in a link or path; and notifying, via the provider device, a customer device of the failure, where the customer device becomes aware of the failure in less than one second.
In another implementation consistent with the principles of the invention, a system includes a provider device and a customer device. The provider device is configured to determine that a failure has occurred in a link or path, and send a first layer 1 message in response to determining that a failure has occurred in a link or path. The customer device is configured to receive the first layer 1 message from the provider device, and transmit a second layer 1 message to the provider device in response to receiving the first layer 1 message. The second layer 1 message instructs the provider device to shut down an interface coupled to the customer device. The provider device ignores the second layer 1 message.
In still another implementation consistent with the principles of the invention, a network device includes an interface coupled to a second network device. The interface is configured to transmit a Synchronous Optical Network (SONET) alarm indication signal-path (AIS-P) signal to the second network device and receive a SONET remote defect indication-path (RDI-P) signal from the second network device after transmitting the SONET AIS-P signal. The interface ignores the SONET RDI-P signal.
In yet another implementation consistent with the principles of the invention, a method includes determining, via a first network device, that a failure has occurred in a link or path; transmitting, via the first network device, a SONET AIS-P signal to a second network device in response to the determining; receiving, via the first network device, a SONET RDI-P signal from the second network device after transmitting the SONET AIS-P signal; and ignoring the SONET RDI-P signal.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an embodiment of the invention and, together with the description, explain the invention. In the drawings,
The following detailed description of implementations consistent with the principles of the invention refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims and their equivalents.
Systems and methods consistent with the principles of the invention improve traffic re-routing in a communications network. In an exemplary implementation, layer 1 signaling (i.e., physical layer signaling) is used to notify a network device of a failure of a communications link or path. In this way, a network device may become aware of the failed link or path much quicker than previously possible, thereby allowing for re-routing of traffic to occur much more quickly.
Customer devices 110 may include one or more network devices that may be associated with a customer's network. Customer devices 110 may receive data units (e.g., Internet Protocol (IP) packets) from customer equipment or provider devices 120 and forward the data units toward their destination(s). In one implementation, customer devices 110 may include customer edge routers. In one implementation consistent with the principles of the invention, customer devices 110 connect to provider devices 120 via one or more optical links. Customer devices 110 may transmit/receive data to/from provider devices 120 according to one of several protocols, such as the synchronous optical network (SONET) standard.
Provider devices 120 may include one or more network devices that may be associated with a service provider's network. Provider devices 120 may receive data units from customer devices 110 or other provider devices 120 and forward the data units toward their destination(s). In one implementation, provider devices 120 may include provider edge routers. As set forth above, provider devices 120 may transmit/receive data to/from customer devices 110 according to one of several protocols, such as the SONET standard.
Network 130 may include one or more networks capable of forwarding data units. Network 130 may include, for example, a local area network (LAN), a wide area network (WAN), a telephone network, such as the Public. Switched Telephone Network (PSTN), an intranet, the Internet, or a combination of networks. In one implementation, traffic may be routed through network 130 using Multi-Protocol Label Switching (MPLS).
RE 230 may perform high level management functions for network device 200. For example, RE 230 may communicate with other networks and/or systems connected to network device 200 to exchange information regarding network topology. RE 230 may create routing tables based on network topology information, create forwarding tables based on the routing tables, and forward the forwarding tables to PFEs 210. PFEs 210 may use the forwarding tables to perform route lookups for incoming packets. RE 230 may also perform other general control and monitoring functions for network device 200. For example, as will be described in detail below, RE 230 may determine whether or not an interface (also referred to as an input/output (I/O) unit) is to be brought down in response to receiving a path failure notification.
PFEs 210 may each connect to RE 230 and switch fabric 220. PFEs 210 may receive packet data on physical links connected to a network, such as a wide area network (WAN), a local area network (LAN), or another type of network. Each physical link could be one of many types of transport media, such as optical fiber or Ethernet cable. The data on the physical link is formatted according to one of several protocols, such as the SONET standard, an asynchronous transfer mode (ATM) technology, or Ethernet. The data may take the form of data units, where each data unit may include all or a portion of a packet.
A PFE 210-x (where PFE 210-x refers to one of PFEs 210) may process incoming data units prior to transmitting the data units to another PFE or the network. To facilitate this processing, PFE 210-x may reassemble the data units into a packet and perform a route lookup for the packet using the forwarding table from RE 230 to determine destination information. If the destination indicates that the packet should be sent out on a physical link connected to PFE 210-x, then PFE 210-x may prepare the packet for transmission by, for example, segmenting the packet into data units, adding any necessary headers, and transmitting the data units from the port associated with the physical link.
Packet processor 310 may perform routing functions and handle packet transfers to and from I/O units 320 and switch fabric 220. For each packet it handles, packet processor 310 may perform the previously-discussed route lookup function and may perform other processing-related functions.
An I/O unit 320-y (where I/O unit 320-y refers to one of I/O units 320) may operate as an interface between a physical link and packet processor 310. Different I/O units may be designed to handle different types of physical links. For example, one of I/O units 320 may be an interface for a SONET link while another one of I/O units 320 may be an interface for an Ethernet link.
Processing may begin with customer device 110A and customer device 110B communicating via a primary path 505, as illustrated in
Assume that a failure 510 occurs on a path between customer device 110A and provider device 120A, as illustrated in
In one implementation consistent with the principles of the invention, provider device 120A may transmit the path failure notification message across network 130 using the Resource Reservation Protocol (RSVP) or another protocol. The path failure notification message may include, for example, a circuit cross connect down (CCC-DOWN) message 515, as illustrated in
Provider device 120B may receive the path failure notification message from provider device 120A (act 405,
By transmitting the path failure notification message at the layer 1 level, the speed at which customer device 110B is notified of the failure is greatly increased. For example, if provider device 120B transmitted the path failure notification message to customer device 110B at the layer 3 level, it may take on the order of a minute for customer device 110B to become aware of failure 510. Alternatively, if provider device 120B transmitted the path failure notification message to customer device 110B at the layer 2 level, it may take from, for example, about 13 seconds to about 30 seconds for customer device 110B to become aware of failure 510. By transmitting the path failure notification message to customer device 110B at the layer 1 level (e.g., the SONET level in the example above), it is possible for customer device 110B to become aware of failure 510 in about 110 milliseconds (up to about 1 second). In one implementation, customer device 110B may become aware of failure 510 in about 500 milliseconds. As a result, much less traffic will be lost by notifying customer device 110B at the layer 1 level.
In response to receiving AIS-P message 520, customer device 110B may logically shut down the interface on which AIS-P message 520 was received (acts 415 and 420,
Returning to
Provider device 120B may receive RDI-P message 535 via, for example, I/O unit 320-A (act 430,
When the link between customer device 110A and provider device 120A has been restored, provider device 120A may transmit a path restoration message to provider device 120B. In one implementation consistent with the principles of the invention, the path restoration message may include, for example, a CCC-UP message. It will be appreciated that the path restoration message may include other types of messages.
Provider device 120B may determine whether a path restoration message has been received from provider device 120A (act 440). If a path restoration message has not been received, processing may return to act 410 with provider device 120B transmitting another layer 1 AIS-P message to customer device 110B.
If, on the other hand, provider device 120B has received a path restoration message, as illustrated by CCC-UP message 550 in
When customer device 110B determines that a layer 1 AMS-P message 520 has not been received (act 415,
While the above example focused on a fault or failure occurring between a customer device and a provider device, implementations consistent with the principles of the invention are not so limited. For example, in other implementations consistent with the principles of the invention, the fault or failure may occur between two provider devices.
Assume, as illustrated in
Customer device 110B may transmit a layer 1 RDI-P message 640 to provider device 120B in response to receiving AIS-P message 630. RDI-P message 640 would normally cause provider device 120B's interface to customer device 110B to shut down. However, in implementations consistent with the principles of the invention, the provider device 120B keeps the interface up so that once the path between provider devices 120A and 120B comes back up, provider device 120B can report this fact to provider device 120A.
Also, in response to receiving RDI-P message 640 from customer device 110B, provider device 120B may transmit a CCC-DOWN message 650 to provider device 120A. Upon receipt of CCC-DOWN message 650, provider device 120A may transmit a layer 1 AIS-P message 660 to customer device 110A. AIS-P message 660 may cause customer device 110A to transmit a layer 1 RDI-P message 670 to provider device 120A. RDI-P message 670 would normally cause provider device 120A's interface to customer device 110A to shut down. However, in implementations consistent with the principles of the invention, provider device 120A ignores RDI-P message 670 and keeps the interface up. In this way, the appropriate interfaces of both provider devices 120A and 120B are immediately available when the failed path is restored.
Systems and methods consistent with the principles of the invention improve the re-routing of traffic in a communications network. In an exemplary implementation, customer devices are notified of link (or path) failures using layer 1 signaling. As a result, the customer devices may be notified of the failures in the order of milliseconds, which greatly decreases the amount of traffic that is lost and greatly increase the speed at which the customer devices begin re-routing traffic on alternate routes.
The foregoing description of exemplary implementations consistent with the principles of the invention provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. For example, while the above-description focused on SONET messaging, it will be appreciated that other layer 1 protocols can alternatively be used. Moreover, while the above description focused on using AIS-P and RDI-P signaling to notify customer devices and provider devices, respectively, of link (or path) failures, it will be appreciated that other types of signaling may alternatively be used. For example, other types of signals that may alternatively be used may include loss of frame (LOF) signaling, loss of signal (LOS) signaling, a line alarm indication signal (AIS-L), bit error rate-signal degrade (BER-SD) signaling, bit error rate-signal fault (BER-SF) signaling, loss of pointer (LOP) signaling, path unequipped (UNEQ-P) signaling, path label mismatch (PLM-P) signaling, loss of cell delineation (LOCD) signaling, etc.
While the above description focused on the transmission of signals between a customer device and a provider device, it will be appreciated that the above processing may alternatively be performed between two provider devices or even two customer devices in other implementations consistent with the principles of the invention.
While a series of acts has been described with regard to
It will be apparent to one of ordinary skill in the art that aspects of the invention, as described above, may be implemented in many different forms of software, firmware, and hardware in the implementations illustrated in the figures. The actual software code or specialized control hardware used to implement aspects consistent with the principles of the invention is not limiting of the invention. Thus, the operation and behavior of the aspects of the invention were described without reference to the specific software code—it being understood that one of ordinary skill in the art would be able to design software and control hardware to implement the aspects based on the description herein.
Further, certain portions of the invention may be implemented as “logic” that performs one or more functions. This logic may include hardware, such as an application specific integrated circuit or a field programmable gate array, software, or a combination of hardware and software.
No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “one” or similar language is used. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
This application is a continuation of U.S. patent application Ser. No. 11/336,861, filed Jan. 23, 2006, which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
7035262 | Joshi | Apr 2006 | B1 |
7089012 | Harris et al. | Aug 2006 | B2 |
7212492 | Au et al. | May 2007 | B1 |
7260324 | Passier et al. | Aug 2007 | B2 |
7286490 | Saleh et al. | Oct 2007 | B2 |
7359331 | Takamichi | Apr 2008 | B2 |
7602700 | Bakhru | Oct 2009 | B1 |
20030228093 | Notani | Dec 2003 | A1 |
20040160895 | Holmgren et al. | Aug 2004 | A1 |
20050185956 | Emongkonchai | Aug 2005 | A1 |
20060013210 | Bordogna et al. | Jan 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
20090323538 A1 | Dec 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11336861 | Jan 2006 | US |
Child | 12550876 | US |