|Número de publicación||US6530032 B1|
|Tipo de publicación||Concesión|
|Número de solicitud||US 09/401,919|
|Fecha de publicación||4 Mar 2003|
|Fecha de presentación||23 Sep 1999|
|Fecha de prioridad||23 Sep 1999|
|Número de publicación||09401919, 401919, US 6530032 B1, US 6530032B1, US-B1-6530032, US6530032 B1, US6530032B1|
|Inventores||Stephen D. Shew, Kenneth G. Hayward|
|Cesionario original||Nortel Networks Limited|
|Exportar cita||BiBTeX, EndNote, RefMan|
|Citas de patentes (7), Otras citas (2), Citada por (141), Clasificaciones (23), Eventos legales (9)|
|Enlaces externos: USPTO, Cesión de USPTO, Espacenet|
The present invention relates to network fault recovery method and apparatus and is particularly concerned with recovery at higher layers from physical layer faults.
Currently, the traffic reliability of large telecommunications networks such as core networks used for Internet service providers (ISPs) or for major corporate backbones is dependent upon the traffic protection resources built into the network elements. To ensure that the desired availability of network connections is maintained and protected, it is standard practice in the telecommunications industry to rely on routing algorithms for handling link or equipment failures. However, with a typical failure reaction time of 30 seconds, conventional routing protocols are inherently too slow for today's high speed networks. This results in inappropriate transmission down time, particularly for video and voice transmission.
A faster solution conventionally used to protect network connections consists of implementing protection in the physical layer (layer 1) of the network by installing redundant equipment so that if one physical link fails, another can rapidly be switched into place.
By contrast to relying on the routing protocols for protecting the availability of network connections, the installation of redundant equipment results in a much faster failure reaction time which, for example in SONET rings is usually in the neighbourhood of 50 milliseconds.
Redundancy of equipment has long been accepted by carrier grade networks as a way to ensure availability and reliability. However networks not requiring carrier grade protection, still desire rapid recovery from physical failures, particularly in high throughput links such as carried in optical fiber, e.g. OC-192.
However, the use of redundant layer 1 equipment for protection presents a number of disadvantages. First, more network links must be installed. For example, current protection configurations which require the installation of additional fiber links between network nodes include dedicated protection (1 protection fiber for each fiber link also referred to as 1:1 protection), shared protection (1 protection fiber for N fiber links or 1:N protection) and ring protection.
The accommodation of multiple fiber links necessitates replicating some of the equipment relating to optical link budgets at each network node. Duplicating this equipment may prove to have a major impact on the overall cost of the network.
In addition to the high cost associated with installing additional equipment for traffic protection, another drawback of the use of redundant layer 1 equipment is that the additional bandwidth capacity created therefrom is exclusively dedicated to traffic protection and remains unused, or is pre-emptable, in the absence of network failures. This increases the cost of the bandwidth.
In view of the slow reaction time of the routing protocols, the high cost and the inefficient bandwidth management associated with the use of additional layer 1 equipment, it is desirable to provide a cost-effective and efficient protection mechanism which provides adequate reaction time to failures and maximizes the utilization of the available resources present in the network.
An object of the present invention is to provide an improved network fault recovery method and apparatus.
In accordance with the present invention L1/L2/L3 Integration and L1 cut-through path utilization are provided in an apparatus and method of fault recovery.
In accordance with an aspect of the present invention there is provided a switch which combines an IP router with L2 capabilities, and an L1 cross connect (optical or electrical).
In accordance with another aspect of the invention there is provided a network in which switches are configured with label switched paths (LSPS) that correspond to layer 1 (L1) cut-through paths.
Conveniently, a layer 2 (L2) cut-through path is over laid on the L1 cut-through path and the L2 cut-through path is used for IP data flows.
Preferably, the L2 cut-through paths are defined as label switched paths (LSPs). And the L1 cut-through paths are each an end-to-end path established with L1 cross connects associated with each switch.
In accordance with another aspect of the present invention a method is provided in which upon failure of a physical link, all LSP endpoints associated with affected L1 cut-through paths are notified by physical detection methods.
Preferably, label switch paths are defined corresponding to a respective L1 cut-through path, the MPLS entity managing an LSP is notified of LSP failures that correspond to L1 cut-through path failure, and backup procedures are then executed to restore IP forwarding.
According to an aspect of the present invention there is provided a method of fault recovery for a network including the steps of establishing a physical topology for the network, aligning a logical topology for the network with the physical topology, and using a fault indication from the physical topology to effect fault recovery in the logical topology.
In accordance with another aspect of the present invention there is provided an apparatus for data networking comprising a cross connect for switching at a physical layer, a router for redirecting data packets at a logical layer coupled to the cross connect, and a fault recovery mechanism responsive to a fault indication in the physical layer for effecting a recovery in the logical layer.
Conveniently, the router includes an internetworking protocol (IP).
Preferably, the internetworking protocol includes multi-protocol label switching (MPLS).
In accordance with another aspect of the present invention there is provided a network comprising a plurality of nodes, each node including a cross connect for switching at a physical layer, a router for redirecting data packets at a logical layer coupled to the cross connect and a fault recovery mechanism responsive to a fault indication in the physical layer for effecting a recovery in the logical layer, a plurality of physical connections between nodes via the respective cross connects, a plurality of logical routes between nodes via the respective routers, and an alternative logical route for use by the fault recovery mechanism.
In accordance with another embodiment of the present invention there is provided in a network including a plurality of nodes and having a plurality of communications layers, a method of providing fault recovery comprising the steps of aligning at least a first and second layer of the plurality of communications layers, for a given path in the first layer, defining a corresponding path in the second layer and an alternative path in the second layer, the alternative path in the second layer corresponding to an alternative path in the first layer disjoint from the given path, and on detection in the first layer of a fault in the given path, switching in the second layer from the corresponding path to the alternative path, whereby fault recovery in the network is provided
Advantages of the present invention include faster recovery from layer 1 failure than provided by L3 routing algorithms and integration of the layers 1, 2 and 3 networks into a common topology (a network management simplification and potential equipment cost saving).
The present invention will be further understood from the following detailed description, with reference to the drawings in which:
FIG. 1 illustrates a known ATM link between two label switched routers (LSR);
FIGS. 2a) and b) illustrate a network of four routers showing topology and label switched paths respectively;
FIGS. 3a), b) and c) illustrate a physical topology, L3 links and OSPF topology, respectively;
FIG. 4 illustrates connectionless layer 3 internet protocol (IP) forwarding in a network of four routers;
FIG. 5 illustrates label switching in a network of four label switching routers;
FIGS. 6a), b) and c) illustrate routers on SONET ring and how they are typically connected;
FIGS. 7a), b), and c) illustrate routers in a TDM overlay;
FIGS. 8a), b), and c) illustrate a switch in accordance with a first embodiment of the present invention and a physical and logical topologies for two such switches;
FIGS. 9a) and b) illustrate an exemplary network's physical and router topologies made up of switches of FIG. 8;
FIGS. 10a) and b) illustrate the network of FIG. 9a) and b) showing a layer 1 (L1) cut-through path. In the network of FIG. 10, a layer 1 cross connected path is treated as a layer 1 cut-through path by the routers;
FIGS. 11a) and b) illustrate IP packet forwarding using the L1 cut-through path of FIG. 10b);
FIGS. 12a) and b) illustrate the effect of an L1 link failure on the use of layer 1 cut-through path by L3 forwarding;
FIG. 13 illustrates a series of L1 cut-through paths based on the FIG. 10 topology;
FIGS. 14a) and b) illustrate an L1 failure in the network of FIG. 13, and the L3 routing view from the point of router R5;
FIGS. 15a) and b) illustrate the network topology of FIG. 14a) showing only the L1 cut-through path not affected by the failed link and an LSP set up using the L1 cut-through path, respectively;
FIGS. 16a) and b) illustrate routing tables, label tables and cross-connects for the topology of FIG. 15b), and illustrate how data is forwarded on a recovery LSP that uses an L1 cut-through path;
FIG. 17 illustrates an L3 stabilised topology database view after the failure has been used to update the L3 routing tables throughout the network;
FIG. 18 illustrates how a router recovers from the failure of a second L1 cut-through path affected by the failure of FIG. 14;
FIGS. 19a) and b) illustrate a network topology when the failed L1 link recovers and L1 cut-through paths are automatically re-established by original configuration information, respectively.
Referring to FIG. 1, there is illustrated a known ATM link between two label switched routers (LSR). An ATM link 10 runs between LSR 12 and LSR14 and as shown in the expanded link section 16, an ATM link typically carries both connectionless traffic 18 and connection oriented traffic such as MPLS label switched paths 20 and 22. In IP router networks, control and data planes are typically not separated.
IP Control Traffic consists of:
Routing protocol messages such as OSPF Hello, OSPF Link State Advertisements
L3 to L2 Address resolution (ARP), flow control (ICMP)
Many other protocols (traceroute, ping, multicast)
IP Data Traffic consists of:
Host-to-host data exchanged via various TCP and UDP protocols (e.g., file transfer with FTP)
Network-to-network data which is carried in TCP or UDP packets (e.g., BGP4 updates)
Typical router-router links 10 carry both control and data traffic, 18. It is possible to separate IP control and data streams. This could be on separate links or could be on separate channels within a channeled link like ATM.
Separation of control and data is seen in MPLS where:
IP routing control is done in a connectionless manner
IP data can be forwarded on Label Switched Paths that are in different channels than IP connectionless control.
Referring to FIGS. 2a) and b) there are illustrated a network of four routers showing router topology and label switched paths, respectively. In FIG. 2a) routers 30, 32, 34 and 36 are connected by: physical link 38 between routers 30 and 32; physical link 40 between routers 30 and 34; and physical link 42 between routers 30 and 36. In FIG. 2b) routers 30, 32, 34 and 36 are interconnected by: MPLS label switched path (LSP) 50 between routers 30 and 32; LSP 52 between routers 30 and 34; LSP 54 between routers 30 and 36; LSP 56 between routers 32 and 34; LSP 58 between routers 32 and 36; and LSP 60 between routers 34 and 36.
In MPLS, the separation of planes is useful in decoupling the number of IGP (Interior Gateway Protocol ) links from the number of forwarding links in the network.
The Interior Gateway Protocol (i.e., a routing protocol) links carry control traffic for the IGP. Usually the physical topology and the IGP topology coincide as shown in FIG. 2a). MPLS label switched paths are created over physical links to form high mesh connectivity for data forwarding as shown in FIG. 2b).
Referring to FIGS. 3a), b) and c) there are illustrated a physical topology, links topology and OSPF topology database view, respectively.
In FIG. 3a) routers 30, 32, 34 and 36 are connected by: physical link 62 between routers 30 and 32; physical link 64 between routers 30 and 34; physical link 66 between routers 30 and 36; and physical link 68 between routers 32 and 34. In FIG. 3b) routers 30, 32, 34 and 36 are interconnected by links: OSPF link 70 between routers 30 and 32; OSPF link 72 between routers 30 and 34; OSPF link 74 between routers 30 and 36; and static route 76 between routers 32 and 34. In FIG. 3c) the OSPF topology database view of the network consists of: link 80 between routers 30 and 32; link 82 between routers 32 and 36; and link 84 between routers 34 and 36.
In such a network, control and data streams can be separated onto different links. For example, a link 76 between two routers 32 and 34 is used only to carry traffic for static IP routes. No IP routing control traffic passes over this link. However it is not possible to completely separate control and data in this example as other IP control packets could still use the link 76 (e.g., ping).
Currently, L2 and L3 control and data technologies are being combined into IP routers that incorporate switching technologies like ATM. This has made an impact on how packets are forwarded. To understand this impact, L3 forwarding is reviewed.
Referring to FIG. 4 there is illustrated a connectionless layer 3 internet protocol (L3 IP) forwarding in a network of four routers. The network includes routers 88, 90, 92 and 94. For the purposes of discussion and simplification only routing over two links, A link 96 and B link 98 are described.
L3 Forwarding takes IP packets, for example packet 100 and performs a lookup on the destination IP address in an IP forwarding table (102, 104, 106), for example R1 table 102 shows link 94, as the next hop. The packet is sent on link A and arrives at router R2 where another lookup on the destination IP address occurs in R2 table 104. The result of that look up is B link, 98, as next hop. A successful lookup results in an identifier for an outgoing link on which to place the packet. This is repeated at each router until a router is reached which directly supports the destination IP address.
In combined L2/L3 switches, instead of forwarding all IP packets in a hop-by-hop connectionless manner, MPLS and other schemes use additions to IP routing control to leverage L2 forwarding for IP packets. This has several advantages including simplicity of the forwarding operation, and the ability to have packets flow along arbitrary paths (as opposed to just shortest). Multi-Protocol Label Switching MPLS provides a method of setting up L2 forwarding in these switches.
Referring to FIG. 5 there is illustrated a label switched router in a network of four label switched routers. For the network of FIG. 4 a label switched path 108 is defined over links 96, 97, and 99. Note that this is not a path that would have been chosen by the shortest path algorithm of an L3 routing protocol like OSPF (assuming each link was equal cost). This constraint is not necessarily imposed on MPLS LSPs.
In operation, after MPLS Label Switched Paths (LSP) are set up, for example LSP 108, IP packets 110 at the start of an LSP undergo an L3 lookup as part of L3 forwarding e.g., table 102. If they match a Forwarding Equivalence Class (FEC), they are sent to the corresponding LSP 108. An MPLS label is added to the packet 112 and it is sent out a link with this encapsulation. At the next MPLS Label Switched Router (LSR), a label swap occurs in a L2 forwarding table 114 (MPLS Incoming Label Map).
MPLS Forwarding Example:
LSP defined over links 96, 97, 99
Packet 110 arriving at R1 88 destined for R4 94 is handled by L3 forwarding 102 and placed on an LSP 108. At R2 90 and R3 92, forwarding is handled by L2 forwarding tables 114 and 116, respectively (i.e., switching, also called label swapping in this context). At R4 94, the final L2 label lookup occurs as this is the end of the LSP. The packet is decapsulated from the MPLS label and passed to the router IP stack for further processing.
This is sometimes called “route once, switch many”.
Referring to FIG. 6 there is illustrated an example of a typical network. FIG. 6a) illustrates a physical topology for a SONET ring with attached routers. Routers are connected to Add/Drop Muxes (ADMs) around ring. FIG. 6b) illustrates a typical logical full-mesh router topology configured on the SONET ring. Router networks use link facilities that are paths in an underlying L1 physical network. Some of these paths bypass other routers. If multiple router-router links share the same physical segment at some point, they will all go down if that segment fails. FIG. 6c) illustrates the effect of a SONET ring segment failure on the configured router-router links. Networks using such L1 facilities usually request physical diversity in their link service. However, this is not always possible, for example, routers connected over an unprotected SONET ring. With multiple L3 link failures, it can take seconds for the routing protocol to recover IP forwarding. L3 traffic is held up until shortest paths re-established even though bandwidth and connectivity may exist. Thus the effect of a single link failure in L1 can have large impacts on the L3 topology and the time it takes to recover connectionless forwarding.
In a network with TDM switches in Layer 1, routers are similarly connected as. SONET networks. Specifically, cross-connect paths are defined for router-router links. In FIG. 7a), TDM switches S1, S2, S3 form the L1 physical network with 3 physical links. Routers use TDM paths setup over those switches and the logical router topology in FIG. 7. b) shows 5 links. When physical link S1-S2 fails, two router-router links are affected (FIG. 7c) because they shared that L1 link for a common portion of their cross connect paths.
Referring to FIGS. 8a), b), and c) there is illustrated a switch in accordance with a first embodiment of the present invention and physical and logical topologies for two such switches. In FIG. 8a) a switch 150 combines an IP label switching router 152 with a layer one (L1) cross connect 154. The switch 150 is defined as a switch that is a traditional IP router 152 (with some L2 switching) linked with an L1 multiplexor/demultiplexor and cross connect 154. For example:
an IP label switching router and a SONET ADM
an IP label switching router and a TDM cross connect
In this combined switch, traffic can enter the cross connect and pass up to the router where it is forwarded onto another outgoing channel in the cross connect. Traffic can also enter the cross connect and exit without passing up to the router.
FIG. 8b) illustrates a simple network of two switches 160 and 162 of FIG. 8a) connected together by physical link 164, allocating one or more channels to connect the routers on either end of the link. FIG. 8c) illustrates the resulting logical connection between the router portions of the switches of FIG. 8b).
Referring to FIGS. 9a) and b) there are illustrated an exemplary network's physical and router topologies made up of switches of FIG. 8. Integration of L1, L2, and L3 is achieved, i.e., an L1/L2/L3 network is established in the following way.
1. Define an IP network with many interconnected L1/L2/L3 switches. No L1 restoration mechanisms are needed or assumed (e.g., SONET restoral).
2. L3/L2/L1 topologies are aligned. All router-router links are now one physical hop and routers view the physical topology. This network differs from networks where L1 and L2 are separated in that no L1 paths (series of cross connected channels) are used as router-router links.
For L3 forwarding in L1/L2/L3 Network, connectionless forwarding of packets traverses only direct physical links on the router-router channels of those links. L3 connectionless traffic may traverse many hops, e.g., packets from R8 to R3 would traverse R8-R7-R1-R2-R3 in FIG. 9b).
Referring to FIGS. 10a) and b), there is illustrated the network of FIG. 9a) and b) showing a layer 1 (L1) cut-through path. In the network of FIG. 10, an existing use of the L1 path between R8 and R5 would be as a router-router link which carries IP control and data traffic. This is not how this L1 path is used in the present embodiment of this invention.
An L1 cut-through path is illustrated in FIG. 10a). Routers 194,196,198,200, 202, and 204 are each connected to respective add/drop MUXs (ADM) 184, 186, 206, 208, 210, and 212 in a SONET ring 214 without protection. Routers 190 and 192 with TDM fabrics 180 and 182 are linked to ADMs 184 and 212. An L1 cut-through path 170 is defined through cross-connects 180, 182, 184, and 186 associated with routers R8 190, R7 192, R6 194, R5 196.
This is equivalent to a private line between routers R8 and R5.
Other cut-through paths can be defined over shared physical links.
A L1 cut-through path 170 is established as follows:
1) Define a L1 cut-through path 170 that includes normal connections in L1 networks and consists of channels in links 172, 174, and 176 concatenated at cross connect points 180, 182, 184, and 186.
2) Let routers at the L1 cut-through path end points (190 and 196) view L1 cut-through paths as valid next hops available for use in the IP Forwarding table, and not as a router-router links that pass IGP control traffic.
There are two possible ways for the router to view the L1 cut-through path as statically routed links, or, as if they were an L2 switched path (like an MPLS LSP). For example, in the optical domain, paths that bypass SONET boxes are like static LSPs. That is, Label Distribution Protocol cannot create them, and in the optical topology they are analogous to PVCs in an ATM topology.
In a preferred embodiment the router views the L1 cut-through path as an MPLS Label Switched Path. Existence and use of L1 cut-through paths does not preclude the use of MPLS dynamic LSPs. Routers are not aware of L1 cut-through paths that tandem through them (e.g., optical bypass in SONET). In FIG. 10b), router R6 is unaware of the L1 cut-through path 170 defined.
Referring to FIGS. 11a) and b) there is illustrated, using the network topology of FIG. 10b), an example of forwarding on the L1 cut-through path of FIG. 10b). L2 Forwarding in L1/L2/L3 network is accomplished by having:
Routers use L1 cut-through paths by installing ingress points to the path as next hops in the IP Forwarding table.
Entries in the IP Forwarding table (IP prefixes) can be installed as:
Static routes. This is for the case where the L1 cut-through path is viewed as a link between two routers that is not part of the routing protocol topology.
Forwarding Equivalence Class (FEC) elements. This is for the case where the L1 cut-through path is viewed as an MPLS LSP.
Before going out on the L1 cut-through path, the packet is placed into an L2 frame.
This framing happens in all routers for the specific L2 which the packet is to be forwarded on.
The packet is also labelled with an MPLS label as is done for packets being sent down an LSP.
In FIGS. 11a) and b) forwarding on a L1 cut-through path is illustrated. Packet 220 from RS 190 to RS 196 is sent to L1 cut-through path 170 and passes through cross connects 226, 228, 232 and 236, but intermediate switches do not perform label swapping or lookup. The use of the L1 cut-through path thereby eliminates the L3 lookup of connectionless forwarding, as well as the label swapping of L2 forwarding. The packet is unchanged during its transit over the L1 cut-through path.
Referring FIGS. 12a) and b) there is illustrated the router topology of FIG. 10a) in which the cut-through path 170 has been broken by a fault condition 250. When a physical link that is carrying multiple L1 cut-through paths fails, each endpoint (R8 190 and R5 196 for L1 cut-through path 170) of all the paths knows about the failure through physical detection methods specific to the cross connect technology.
In the preferred embodiment, an MPSL LSP is associated with every L1 cut-through path, hence a router that detects an L1 cut-through path failure immediately informs the MPLS process that manages the LSP associated with the path. The path failure causes an interrupt that informs the MPLS software process as soon as possible, of the failure. The router can then adjust the affected next hop fields in the L3 forwarding table for the destination IP prefixes, which use the L1 cut-through path, with other valid routes if they exist. This action can take place more quickly at L2 than the L3 routing protocol reaction time to the failed link because the detection method is based on L1 physical layer detection that spans multiple cross connects. In L3 routing protocols, link failure is propagated from the point of failure to routers farther and farther away. This means that a source router which is far from the failure (many hops), some of whose traffic crossed the failed link, does not find out about the failure for some time. In contrast, the LSRs on the endpoints of L1 cut-through paths, which are affected by a L1 link failure, are informed quickly even though they may be several hops away from the failure.
If link 250 (R7-R6) fails, the router R8 190 immediately detects the failure of L1 cut-through path 170 (R8-R7-R6-R5). Next hop entries, for example in L3 forwarding table 222, which use the affected L1 cut-through path, can be updated to not use the cut-through path 170. The router R8 190 could, for example, replace the next hop with L3 connectionless next hop. That is, just send packets to R7 at L3.
Referring to FIG. 13 there is illustrated an L1/L2/L3 network in accordance with an embodiment of the present invention. The L1/L2/L3 network includes eight routers 190-204, all of which are MPLS capable and are thus Label Switching Routers (LSR). The L1/L2/L3 topology is aligned. L1 components could be SONET Ring, SONET link, TDM, or other similar technology. The following L1 cut-through paths are defined: R5-R4-R3, 252; R5-R4-R3-R2, 254; R5-R6-R1, 256; R4-R3-R2, 258. LSRs are configured with Strict Explicit Routed Label Switched Paths 262, 264, 266, 268, that correspond to the L1 cut-through path, 252-258, respectively. Each LSR knows:
The existence of L1 cut-through paths that originate from it.
Path details for each originating L1 cut-through path, specifically the routers that it bypasses and the terminating LSR. For example, R5 196 knows about three L1 cut-through paths 252, 254, 256 and their constituents R5-R4-R3, R5-R4-R3-R2, R5-R6-R1, respectively.
Summary knowledge of L1 cut-through paths is propagated through the L3 network by the routing protocol. This includes only the endpoints and not the intermediate nodes. For example, router 196, R5, knows about the R4->R2 cut-through path 258, but not the intermediate nodes of that cut-through path.
For the network of FIG. 13, a backup router sequence (BRS) is defined to be a node and link disjoint path for a given L1 cut-through path. This is done over the routing topology, which in this case is also the L1 and L2 topology. For each L1 cut-through path originating on it, an LSR computes or pre-computes a BRS. This can be done dynamically on each LSR in response to topology changes and L1 cut-through path changes. An example of a dynamic computation is to prune physical links and intermediate nodes of each L1 cut-through path, then run a shortest path calculation on the remaining topology. To be able to always have a BRS, there is a restriction on the network of FIG. 13. The L1 topology should be engineered so that for any single link failure, all nodes remain connected over some alternative path.
In operation when a L1 failure occurs, all L1 cut-through paths over that link also fail. LSRs at the end points of those L1 cut-through paths detect this by L1 physical methods. For each failed L1 cut-through path, the LSR has a BRS. The LSR scans remaining L1 cut-through paths that originate from it to see if any of them have endpoints on the BRS. If so, the LSR can use any of them in constructing a new label switched path (LSP) which follow the BRS constituents. LSP setup procedures are used that are similar to those for explicit route (ER) setup with LDP, and follow the BRS from the L1 cut-through path endpoint to the destination of the failed L1 cut-through path.
The LSP could also be constructed in advance, i.e. precomputed. That is, it is a backup LSP that is waiting to be used.
An L1 cut-through path can be selected whose endpoint is furthest in the BRS toward the destination LSR.
If there are no L1 cut-through path whose endpoints lie on the BRS, an ER-LSP is setup following the BRS. The network's LSP could subsequently be re-optimized periodically if desired.
Referring to FIGS. 14a) and b) there are illustrated the network topology of FIG. 13 with a failed link, and a node's instantaneous topology database view after the failure, respectively. In the network of FIG. 14a) a failure 270 has been introduced in link affecting L1 cut-through path 252, 254, 258. The network topology as viewed by router R5 196, is shown in FIG. 14b). Optical link R5-R3 fails. R5 196 immediately detects loss of two L1 cut-through paths 252, 254. Failed L1 cut-through paths are: (R5-R4-R3-R2) 254; (R5-R4-R3) 252; and (R4-R3-R2) 258. The router R5 196 does not immediately know about loss of L1 cut-through path (R4-R3-R2) 258 or link (R3-R4) as this is communicated in the L3 routing protocol.
Referring to FIGS. 15a) and b) there are illustrated the network topology of FIG. 14a) showing only the L1 cut-through path not affected by the failed link and an LSP set up using the L1 cut-through path, respectively.
For L1 cut-through path (R5-R4-R3-R2) 254, its BRS is R5→R6→R1→R2. L1 cut-through path (R5-R6-R1) 256 is on the BRS and is useable for a portion thereof. The router R5 196 establishes an LSP 272 over R5→(R5→R6→R1)→R1→R2 that is stacked over L1 cut-through path (R5-R6-R1) 256.
Referring FIGS. 16a) and b) there is illustrated the router tables, label tables and cross-connects for the topology of FIG. 15b). The backup LSP 272 is now used in the IP Forwarding table 274 for packets 276 whose destination is router R2 202. Label swapping occurs at the router R1 204 using label table 280. Note how the L1 cut-through path (R5-R6-R1) 256 is used as the first hop in the backup LSP 272. When compared to a regular LSP setup over R5→R6→R1→R2, using the L1 cut-through path 256 saves a label swap operation in the router R6.
In parallel with the failure sequence for the L1 cut-through path, the L3 routing protocol is updating the view of the topology through flooding and SPF re-calculation. This eventually produces a stable view of the topology at all LSR. Referring to FIG. 17 there is illustrated an L3 stabilized topology database view after the L3 routing protocol has adjusted to the failure and updated the L3 routing tables throughout the network.
Referring to FIG. 18 there is illustrated how a router recovers from the failure of a second L1 cut-through path affected by the failure of FIG. 14. R5 196 also handles the failure of L1 cut-through path (R5-R4-R3) 252. Its recovery LSP 290 is R5→(R5→R6→R1)→R1→R2→R3
Because the two recovery LSPs 272 and 290 from R5 are separately labeled, they can co-exist over the same L1 cut-through path path 256 that is used by their BRS. The router label table of R2 202 terminates the LSP 290 using the L1 cut-through path 256 (R5-R1-R2) and label swaps LSP R5-R1-R2-R3.
Referring to FIGS. 19a) and b) there is illustrated a network topology when the failed link recovers, L1 cut-through paths are automatically re-established by original configuration information, respectively. In FIG. 19a), when an LSR 196 (R5) sees a new L1 cut-through path (252 and 254), it checks to see if there is an LSP (272 and 290) that originates from the LSR 196 and could use the L1 cut-through path (252 and 254) as a full replacement. This LSP could be going over an existing L1 cut-through path (as in the previous failure scenario). It could also be an LSP just using L3 links. The traffic flow is redirected over the L1 cut-through path (252 and 290) after the SPF recalculates the forwarding table and then the recovery LSP (272 or 290) is either torn down or remains alive but unused.
Recovering to a restored L1 cut-through path (e.g., 252) is exactly like moving from a backup LSP (e.g., 290) to a primary LSP (e.g., 262).
Both LSP are valid entries in the IP Forwarding table, but the primary LSP takes priority due to configured precedence.
The embodiments of the invention described herein above have the following advantages:
Detection of a L1 link failure by LSRs that are not on either end of the link is fast. That is, LSRs several hops away in the topology whose L1 cut-through paths go across the failed link, are informed quickly of the failure. This is relative to the speed at which an L3 routing protocol would inform of the failure.
Use of the L1 cut-through path takes less processing at intermediate nodes than L3 or L2 forwarding.
After a failure detection, the forwarding table can be quickly adjusted to use a backup LSP.
This scheme “retrofits” static connections into the MPLS cut-through path forwarding mode, and thus enables existing MPLS configuration to be used for LSPs that overlay L1 cut-through paths.
It relies on fast connection failure detection and could apply to any L1 network with this characteristic. For example:
SONET networks (rings, point-to-point links)
DWDM networks where L1 cut-through paths are wavelength channels
TDM networks where L1 cut-through paths are TDM paths.
An alternative embodiment has two L1/L2/L3 switches share the same cross connect fabric, e.g., two routers attached to one SONET ADM.
In this case, the link between the two routers consists of one cross connection as opposed to multiple ones in a path. There is no physical link between the two LSRs and if the cross connect fabric itself fails, then this is treated like the failure of all L1 links attached to either LSR. Use of L1 cut-through paths with this switch embodiment works for failure and recovery of other links in the network.
A Backup Router Sequence could be a link disjoint path only as opposed to a node and link disjoint. If so, then the BRS could be affected by a node failure in the steady state L1 cut-through path.
|Patente citada||Fecha de presentación||Fecha de publicación||Solicitante||Título|
|US5995485 *||26 Nov 1996||30 Nov 1999||Mci Communications Corporation||Method and apparatus for isolating network failures by correlating paths issuing alarms with failure spans|
|US6075766 *||26 Nov 1996||13 Jun 2000||Mci Communications Corporation||Method and apparatus for identifying restoral routes in a network|
|US6134671 *||31 Jul 1997||17 Oct 2000||Mci Communications Corporation||System and method for dynamically generating restoration routes within a communications network|
|US6137774 *||31 Jul 1997||24 Oct 2000||Mci Communications Corporation||System and method for dispatching commands to switching elements within a communications network|
|US6327669 *||31 Dic 1996||4 Dic 2001||Mci Communications Corporation||Centralized restoration of a network using preferred routing tables to dynamically build an available preferred restoral route|
|US6374303 *||12 Nov 1998||16 Abr 2002||Lucent Technologies, Inc.||Explicit route and multicast tree setup using label distribution|
|US6430150 *||6 May 1996||6 Ago 2002||Fujitsu Limited||Communication node, restoration method and communication network|
|1||A Framework For Multiprotocol Label Switching, R. Callon et al, Nov. 21, 1997, pp. 1-65.|
|2||Multiprotocol Label Switching Architecture, Eric C. Rosen et al, Apr. 1999, pp. 1-62.|
|Patente citante||Fecha de presentación||Fecha de publicación||Solicitante||Título|
|US6671819 *||6 Abr 2000||30 Dic 2003||Bbnt Solutions Llc||System and methods routing packets on alterate paths|
|US6704279 *||12 Ene 2001||9 Mar 2004||Siemens Aktiengesellschaft||Circuit arrangement for providing a back-up circuit for transmission devices in ring architectures that route MPLS packets|
|US6765921 *||28 Jun 2000||20 Jul 2004||Nortel Networks Limited||Communications network|
|US6766482||31 Oct 2001||20 Jul 2004||Extreme Networks||Ethernet automatic protection switching|
|US6779039||31 Mar 2000||17 Ago 2004||Avaya Technology Corp.||System and method for routing message traffic using a cluster of routers sharing a single logical IP address distinct from unique IP addresses of the routers|
|US6791948 *||3 Jul 1999||14 Sep 2004||Emulex Corporation||Distributed switch and connection control arrangement and method for digital communications network|
|US6829215 *||27 Mar 2001||7 Dic 2004||Marconi Intellectual Property (Ringfence) Inc.||IP multi-homing|
|US6880089||31 Mar 2000||12 Abr 2005||Avaya Technology Corp.||Firewall clustering for multiple network servers|
|US6904018 *||13 Dic 2000||7 Jun 2005||Korea Telecommunication Authority||Method for high speed rerouting in multi protocol label switching network|
|US6944156 *||21 Mar 2001||13 Sep 2005||Nec Corporation||Label request packet transmission method, packet transfer network and method thereof, and packet transfer device|
|US6956816 *||15 Feb 2001||18 Oct 2005||Extreme Networks||Fault tolerant automatic protection switching for distributed routers|
|US6965976 *||4 Mar 2003||15 Nov 2005||Hitachi, Ltd.||Backup method on a hierarchical backup system|
|US6985443 *||12 Jun 2001||10 Ene 2006||Photuris, Inc.||Method and apparatus for alleviating traffic congestion in a computer network|
|US7009987 *||29 Oct 1999||7 Mar 2006||Kabushiki Kaisha Toshiba||Router device and cut-through path control method for realizing load balancing at intermediate routers|
|US7055173 *||1 Abr 2000||30 May 2006||Avaya Technology Corp.||Firewall pooling in a network flowswitch|
|US7068595 *||13 Abr 2001||27 Jun 2006||Sun Microsystems, Inc.||Method and apparatus for facilitating instant failover during packet routing|
|US7088679 *||12 Dic 2001||8 Ago 2006||Lucent Technologies Inc.||Method and system for providing failure protection in a ring network that utilizes label switching|
|US7149426 *||18 Jul 2002||12 Dic 2006||Avanex Corporation||Optical routers and redundancy|
|US7164888 *||23 Dic 2002||16 Ene 2007||Qwest Communications International Inc.||Systems and methods for analyzing critical circuits and associated telecommunication resources|
|US7173936 *||11 Sep 2000||6 Feb 2007||Ciena Corporation||Method and apparatus for partitioning SONET frames into logical channels to optimize bandwidth utilization|
|US7193970 *||9 Ene 2002||20 Mar 2007||Nokia Corporation||Protected routing in a communication network|
|US7206315||22 Dic 2005||17 Abr 2007||Kabushiki Kaisha Toshiba||Router device and cut-through path control method for realizing load balancing at intermediate routers|
|US7280472 *||10 Ene 2003||9 Oct 2007||Lucent Technologies Inc.||Protection switching at a network node|
|US7284148||17 Jun 2004||16 Oct 2007||International Business Machines Corporation||Method and system for self-healing in routers|
|US7289431 *||18 Jul 2002||30 Oct 2007||Hitachi, Ltd.||Packet transmission method|
|US7298693||20 Oct 2000||20 Nov 2007||Tellabs Operations, Inc.||Reverse notification tree for data networks|
|US7315510 *||20 Oct 2000||1 Ene 2008||Tellabs Operations, Inc.||Method and apparatus for detecting MPLS network failures|
|US7336648 *||25 Oct 2000||26 Feb 2008||Fujitsu Limited||Label switching system|
|US7346277 *||26 Jul 2004||18 Mar 2008||Lucent Technologies Inc.||Joint-layer restoration in packet-over-optical networks|
|US7447150 *||16 May 2003||4 Nov 2008||Nortel Networks Limited||Automated path restoration for packet telephony|
|US7522517 *||18 Nov 2003||21 Abr 2009||Sprint Communications Company Lp.||Communication system with multipoint circuit bonding|
|US7535831 *||16 Sep 2003||19 May 2009||Nortel Networks Limited||Method and apparatus for providing grades of service for unprotected traffic in an optical network|
|US7590048 *||17 Oct 2003||15 Sep 2009||Fujitsu Limited||Restoration and protection method and an apparatus thereof|
|US7619966 *||2 Dic 2003||17 Nov 2009||Alcatel Lucent||Hybrid virtual private LAN extensions|
|US7639607 *||26 Oct 2005||29 Dic 2009||Fujitsu Limited||Signaling system for simultaneously and autonomously setting a spare path|
|US7756009 *||1 Nov 2004||13 Jul 2010||Ciena Corporation||Method and apparatus for priority call setup and restoration in an optical communications system|
|US7765294||27 Jul 2010||Embarq Holdings Company, Llc||System and method for managing subscriber usage of a communications network|
|US7796504 *||20 Oct 2000||14 Sep 2010||Tellabs Operations, Inc.||Method for establishing an MPLS data network protection pathway|
|US7804767 *||25 Oct 2000||28 Sep 2010||Tellabs Operations, Inc.||Protection/restoration of MPLS networks|
|US7808918||31 May 2007||5 Oct 2010||Embarq Holdings Company, Llc||System and method for dynamically shaping network traffic|
|US7843831||31 May 2007||30 Nov 2010||Embarq Holdings Company Llc||System and method for routing data on a packet network|
|US7852754 *||27 Abr 2006||14 Dic 2010||Tellabs San Jose, Inc.||Method and apparatus for managing faults in a ring network|
|US7861002 *||26 Ene 2004||28 Dic 2010||Adtran, Inc.||Network router that efficiently switches between a primary data path and a backup data path|
|US7881184||14 Ago 2007||1 Feb 2011||Tellabs Operations, Inc.||Reverse notification tree for data networks|
|US7889660||22 Ago 2007||15 Feb 2011||Embarq Holdings Company, Llc||System and method for synchronizing counters on an asynchronous packet communications network|
|US7940735||31 May 2007||10 May 2011||Embarq Holdings Company, Llc||System and method for selecting an access point|
|US7948909||31 May 2007||24 May 2011||Embarq Holdings Company, Llc||System and method for resetting counters counting network performance information at network communications devices on a packet network|
|US8000318||31 May 2007||16 Ago 2011||Embarq Holdings Company, Llc||System and method for call routing based on transmission performance of a packet network|
|US8015294||31 May 2007||6 Sep 2011||Embarq Holdings Company, LP||Pin-hole firewall for communicating data packets on a packet network|
|US8040811||31 May 2007||18 Oct 2011||Embarq Holdings Company, Llc||System and method for collecting and managing network performance information|
|US8064391||31 May 2007||22 Nov 2011||Embarq Holdings Company, Llc||System and method for monitoring and optimizing network performance to a wireless device|
|US8068425||9 Abr 2009||29 Nov 2011||Embarq Holdings Company, Llc||System and method for using network performance information to determine improved measures of path states|
|US8098579||31 May 2007||17 Ene 2012||Embarq Holdings Company, LP||System and method for adjusting the window size of a TCP packet through remote network elements|
|US8102770||31 May 2007||24 Ene 2012||Embarq Holdings Company, LP||System and method for monitoring and optimizing network performance with vector performance tables and engines|
|US8103753||22 Abr 2003||24 Ene 2012||Microsoft Corporation||Distributing membership information for multi-party application layer sessions|
|US8107366||31 May 2007||31 Ene 2012||Embarq Holdings Company, LP||System and method for using centralized network performance tables to manage network communications|
|US8111692||28 Abr 2010||7 Feb 2012||Embarq Holdings Company Llc||System and method for modifying network traffic|
|US8125897||31 May 2007||28 Feb 2012||Embarq Holdings Company Lp||System and method for monitoring and optimizing network performance with user datagram protocol network performance information packets|
|US8130637||21 Dic 2007||6 Mar 2012||Tellabs Operations, Inc.||Method and apparatus for detecting MPLS network failures|
|US8130793||31 May 2007||6 Mar 2012||Embarq Holdings Company, Llc||System and method for enabling reciprocal billing for different types of communications over a packet network|
|US8144586||31 May 2007||27 Mar 2012||Embarq Holdings Company, Llc||System and method for controlling network bandwidth with a connection admission control engine|
|US8144587||27 Mar 2012||Embarq Holdings Company, Llc||System and method for load balancing network resources using a connection admission control engine|
|US8184549||31 May 2007||22 May 2012||Embarq Holdings Company, LLP||System and method for selecting network egress|
|US8189468||25 Oct 2006||29 May 2012||Embarq Holdings, Company, LLC||System and method for regulating messages between networks|
|US8194555||31 May 2007||5 Jun 2012||Embarq Holdings Company, Llc||System and method for using distributed network performance information tables to manage network communications|
|US8194643||19 Oct 2006||5 Jun 2012||Embarq Holdings Company, Llc||System and method for monitoring the connection of an end-user to a remote network|
|US8199653||31 May 2007||12 Jun 2012||Embarq Holdings Company, Llc||System and method for communicating network performance information over a packet network|
|US8213366||7 Sep 2011||3 Jul 2012||Embarq Holdings Company, Llc||System and method for monitoring and optimizing network performance to a wireless device|
|US8223654||31 May 2007||17 Jul 2012||Embarq Holdings Company, Llc||Application-specific integrated circuit for monitoring and optimizing interlayer network performance|
|US8223655||31 May 2007||17 Jul 2012||Embarq Holdings Company, Llc||System and method for provisioning resources of a packet network based on collected network performance information|
|US8224255||31 May 2007||17 Jul 2012||Embarq Holdings Company, Llc||System and method for managing radio frequency windows|
|US8228791||31 May 2007||24 Jul 2012||Embarq Holdings Company, Llc||System and method for routing communications between packet networks based on intercarrier agreements|
|US8238253||31 May 2007||7 Ago 2012||Embarq Holdings Company, Llc||System and method for monitoring interlayer devices and optimizing network performance|
|US8274905||31 May 2007||25 Sep 2012||Embarq Holdings Company, Llc||System and method for displaying a graph representative of network performance over a time period|
|US8289965||19 Oct 2006||16 Oct 2012||Embarq Holdings Company, Llc||System and method for establishing a communications session with an end-user based on the state of a network connection|
|US8307065||31 May 2007||6 Nov 2012||Centurylink Intellectual Property Llc||System and method for remotely controlling network operators|
|US8358580||8 Dic 2009||22 Ene 2013||Centurylink Intellectual Property Llc||System and method for adjusting the window size of a TCP packet through network elements|
|US8374090||18 Oct 2010||12 Feb 2013||Centurylink Intellectual Property Llc||System and method for routing data on a packet network|
|US8407765||31 May 2007||26 Mar 2013||Centurylink Intellectual Property Llc||System and method for restricting access to network performance information tables|
|US8472326||5 Jul 2012||25 Jun 2013||Centurylink Intellectual Property Llc||System and method for monitoring interlayer devices and optimizing network performance|
|US8477614||31 May 2007||2 Jul 2013||Centurylink Intellectual Property Llc||System and method for routing calls if potential call paths are impaired or congested|
|US8488447||31 May 2007||16 Jul 2013||Centurylink Intellectual Property Llc||System and method for adjusting code speed in a transmission path during call set-up due to reduced transmission performance|
|US8488495||18 Jun 2012||16 Jul 2013||Centurylink Intellectual Property Llc||System and method for routing communications between packet networks based on real time pricing|
|US8509082||16 Mar 2012||13 Ago 2013||Centurylink Intellectual Property Llc||System and method for load balancing network resources using a connection admission control engine|
|US8520603||23 May 2012||27 Ago 2013||Centurylink Intellectual Property Llc||System and method for monitoring and optimizing network performance to a wireless device|
|US8531954||31 May 2007||10 Sep 2013||Centurylink Intellectual Property Llc||System and method for handling reservation requests with a connection admission control engine|
|US8537695||31 May 2007||17 Sep 2013||Centurylink Intellectual Property Llc||System and method for establishing a call being received by a trunk on a packet network|
|US8549405||31 May 2007||1 Oct 2013||Centurylink Intellectual Property Llc||System and method for displaying a graphical representation of a network to identify nodes and node segments on the network that are not operating normally|
|US8570872||18 Abr 2012||29 Oct 2013||Centurylink Intellectual Property Llc||System and method for selecting network ingress and egress|
|US8576722||31 May 2007||5 Nov 2013||Centurylink Intellectual Property Llc||System and method for modifying connectivity fault management packets|
|US8588058 *||15 Dic 2010||19 Nov 2013||Tellabs Operations, Inc.||Reverse notification tree for data networks|
|US8619551 *||10 Ene 2007||31 Dic 2013||Kabushiki Kaisha Toshiba||Protection path reservation method and node unit|
|US8619596||27 Ene 2012||31 Dic 2013||Centurylink Intellectual Property Llc||System and method for using centralized network performance tables to manage network communications|
|US8619600||31 May 2007||31 Dic 2013||Centurylink Intellectual Property Llc||System and method for establishing calls over a call path having best path metrics|
|US8619820||27 Ene 2012||31 Dic 2013||Centurylink Intellectual Property Llc||System and method for enabling communications over a number of packet networks|
|US8670313||13 Dic 2012||11 Mar 2014||Centurylink Intellectual Property Llc||System and method for adjusting the window size of a TCP packet through network elements|
|US8687614||7 Dic 2010||1 Abr 2014||Centurylink Intellectual Property Llc||System and method for adjusting radio frequency parameters|
|US8717911||31 May 2007||6 May 2014||Centurylink Intellectual Property Llc||System and method for collecting network performance information|
|US8737203||5 Ago 2010||27 May 2014||Tellabs Operations, Inc.||Method for establishing an MPLS data network protection pathway|
|US8743700||30 May 2012||3 Jun 2014||Centurylink Intellectual Property Llc||System and method for provisioning resources of a packet network based on collected network performance information|
|US8743703||31 May 2007||3 Jun 2014||Centurylink Intellectual Property Llc||System and method for tracking application resource usage|
|US8750158||9 Ago 2012||10 Jun 2014||Centurylink Intellectual Property Llc||System and method for differentiated billing|
|US8837275||9 Feb 2006||16 Sep 2014||International Business Machines Corporation||System, method and program for re-routing internet packets|
|US8842516||6 Ago 2010||23 Sep 2014||Tellabs Operations, Inc.||Protection/restoration of MPLS networks|
|US8976665||1 Jul 2013||10 Mar 2015||Centurylink Intellectual Property Llc||System and method for re-routing calls|
|US8983286 *||8 Nov 2012||17 Mar 2015||Electronics And Telecommunications Research Institute||Method and apparatus for protection switching in optical transport network|
|US9042370||6 Nov 2013||26 May 2015||Centurylink Intellectual Property Llc||System and method for establishing calls over a call path having best path metrics|
|US9042720 *||13 Dic 2005||26 May 2015||At&T Intellectual Property Ii, L.P.||Joint IP/optical layer restoration after a router failure|
|US9054915||16 Jul 2013||9 Jun 2015||Centurylink Intellectual Property Llc||System and method for adjusting CODEC speed in a transmission path during call set-up due to reduced transmission performance|
|US9054986||8 Nov 2013||9 Jun 2015||Centurylink Intellectual Property Llc||System and method for enabling communications over a number of packet networks|
|US9083551 *||27 Abr 2006||14 Jul 2015||Tellabs Operations, Inc.||Method and apparatus for media distribution using VPLS in a ring topology|
|US9094257||9 Ago 2012||28 Jul 2015||Centurylink Intellectual Property Llc||System and method for selecting a content delivery network|
|US9094261||8 Ago 2013||28 Jul 2015||Centurylink Intellectual Property Llc||System and method for establishing a call being received by a trunk on a packet network|
|US9112734||21 Ago 2012||18 Ago 2015||Centurylink Intellectual Property Llc||System and method for generating a graphical user interface representative of network performance|
|US20010019536 *||5 Mar 2001||6 Sep 2001||Hiroyuki Suzuki||Line restoring method and packet transmission equipment|
|US20010028648 *||21 Mar 2001||11 Oct 2001||Nec Corporation||Label request packet transmission method, packet transfer network and method thereof, and packet transfer device|
|US20020004843 *||21 Dic 2000||10 Ene 2002||Loa Andersson||System, device, and method for bypassing network changes in a routed communication network|
|US20020060985 *||13 Dic 2000||23 May 2002||Lee Jae Yong||Method for high speed rerouting in multi protocol label switching network|
|US20020060987 *||9 Ene 2002||23 May 2002||Nokia Corporation||Protected routing in a communication network|
|US20020133756 *||7 Feb 2002||19 Sep 2002||Maple Optical Systems, Inc.||System and method for providing multiple levels of fault protection in a data communication network|
|US20020150043 *||13 Abr 2001||17 Oct 2002||Perlman Radia J.||Method and apparatus for facilitating instant failover during packet routing|
|US20040114595 *||17 Oct 2003||17 Jun 2004||Masami Doukai||Restoration and protection method and an apparatus thereof|
|US20040153753 *||4 Mar 2003||5 Ago 2004||Hitachi, Ltd.||Backup method on a hierarchical backup system|
|US20040174887 *||2 Dic 2003||9 Sep 2004||Alcatel||Hybrid virtual private LAN extensions|
|US20040203439 *||23 Dic 2002||14 Oct 2004||Qwest Communications International Inc (Patent Prosecution) Law Department||Systems and methods for analyzing critical circuits and associated telecommunication resources|
|US20040215667 *||22 Abr 2003||28 Oct 2004||Taylor John Anthony||Distributing membership information for multi-party application layer sessions|
|US20040240442 *||24 Sep 2002||2 Dic 2004||Jochen Grimminger||Method and device for adapting label-switched paths in packet networks|
|US20050018600 *||23 Ago 2004||27 Ene 2005||Massimiliano Tornar||IP multi-homing|
|US20050021844 *||26 Ene 2004||27 Ene 2005||Roberto Puon||Network router that efficiently switches between a primary data path and a backup data path|
|US20050058064 *||16 Sep 2003||17 Mar 2005||Nortel Networks Limited||Method and apparatus for providing grades of service for unprotected traffic in an optical network|
|US20050063299 *||26 Jul 2004||24 Mar 2005||Atkinson Gary W.||Joint-layer restoration in packet-over-optical networks|
|US20050086385 *||20 Oct 2003||21 Abr 2005||Gordon Rouleau||Passive connection backup|
|US20050283643 *||17 Jun 2004||22 Dic 2005||International Business Machines Corporation||Method and system for self-healing in routers|
|US20060013127 *||22 Dic 2004||19 Ene 2006||Fujitsu Limited||MPLS network system and node|
|US20090257742 *||13 Dic 2005||15 Oct 2009||Chiu Angela L||Joint IP/optical layer restoration after a router failure|
|US20110085440 *||15 Dic 2010||14 Abr 2011||Tellabs Operations, Inc.||Reverse Notification Tree for Data Networks|
|US20130243417 *||8 Nov 2012||19 Sep 2013||Electronics And Telecommunications Research Institute||Method and apparatus for protection switching in optical transport network|
|US20140043959 *||16 Oct 2013||13 Feb 2014||Tellabs Operations, Inc.||Reverse Notification Tree For Data Networks|
|CN101431426B||22 Abr 2004||26 Ene 2011||微软公司||Distributing membership information for multi-party application layer sessions|
|EP1562351A2 *||15 Abr 2004||10 Ago 2005||Microsoft Corporation||Distributing membership information for multi-party application layer sessions|
|WO2003050553A1 *||11 Dic 2002||19 Jun 2003||Riverstone Networks Inc||Method and system for providing failure protection in a ring network that utilizes label switching|
|Clasificación de EE.UU.||714/4.3, 709/239, 370/222, 370/218, 370/225|
|Clasificación internacional||H04L12/56, H04L12/24, H04L29/14|
|Clasificación cooperativa||H04L69/40, H04L41/0663, H04L45/50, H04L45/22, H04L49/557, H04L45/28, H04L49/602, H04L49/251, H04L43/0811|
|Clasificación europea||H04L45/50, H04L45/22, H04L49/55E, H04L45/28, H04L12/24D3, H04L29/14|
|23 Sep 1999||AS||Assignment|
Owner name: NORTEL NETWORKS CORPORATION, CANADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHEW, STEPHEN D.;HAYWARD, KENNETH G.;REEL/FRAME:010275/0986;SIGNING DATES FROM 19990920 TO 19990921
|30 Ago 2000||AS||Assignment|
Owner name: NORTEL NETWORKS LIMITED,CANADA
Free format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706
Effective date: 20000830
|14 Ago 2006||FPAY||Fee payment|
Year of fee payment: 4
|24 Ago 2010||FPAY||Fee payment|
Year of fee payment: 8
|28 Oct 2011||AS||Assignment|
Owner name: ROCKSTAR BIDCO, LP, NEW YORK
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:027164/0356
Effective date: 20110729
|30 Ene 2014||AS||Assignment|
Owner name: ROCKSTAR CONSORTIUM US LP, TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ROCKSTAR BIDCO, LP;REEL/FRAME:032095/0936
Effective date: 20120509
|5 Feb 2014||AS||Assignment|
Owner name: CONSTELLATION TECHNOLOGIES LLC, TEXAS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ROCKSTAR CONSORTIUM US LP;REEL/FRAME:032162/0489
Effective date: 20131113
|25 Ago 2014||FPAY||Fee payment|
Year of fee payment: 12
|9 Feb 2015||AS||Assignment|
Owner name: RPX CLEARINGHOUSE LLC, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROCKSTAR CONSORTIUM US LP;ROCKSTAR CONSORTIUM LLC;BOCKSTAR TECHNOLOGIES LLC;AND OTHERS;REEL/FRAME:034924/0779
Effective date: 20150128