IP Library Granted Patent US 7,801,031
Granted Patent B2
US 7,801,031 · App. 11/934,213 · Granted Sep 21, 2010

Rerouting for double-link failure recovery in an internet protocol network

Assignee: Polytechnic Institute of New York University
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,801,031
App. No.
11/934,213
Granted
Sep 21, 2010
Kind
B2
Abstract

A router in a survivable portion of a network may forward packets to a destination node even in the event of a double-link failure. For a given destination node, the router has previously been configured with a primary port, a primary backup port, and a secondary backup port. The router receives a packet addressed to the destination node within the survivable portion of the network, wherein the packet includes information indicating that the packet has encountered a failure. The router then selects one of (A) the primary port, (B) the primary backup port and (C) the secondary backup port on which to forward the received packet, such that a backup path with no dead loops is defined. The router may obtain a recovery distance of at least one of (A) the primary backup port based on a backup path to which it leads, and (B) the secondary backup port based on a backup path to which it leads, and may further obtain counter information in a packet indicative of a failure distance. In this case, the router may select a port whose recovery distance is greater than the failure distance. The router may identify a pattern of the failure. In this case, the router may make its selection using a forwarding policy associated with the identified pattern.

Claims (20)

1. For use by a router in a survivable network portion, a computer-implemented method comprising:

a) receiving a packet addressed to a destination node within the survivable network portion, wherein the packet includes an information indicating that the packet has encountered a failure; and

b) selecting one of (A) a primary port, (B) a primary backup port and (C) a secondary backup port on which to forward the received packet, such that, in the event of a double link failure, a backup path with no dead loops is defined,

wherein the act of selecting one of (A) a primary port, (B) a primary backup port and (C) a secondary backup port for local rerouting includes

1) identifying a pattern of the failure; and

2) selecting, using a forwarding policy associated with the identified pattern, one of (A) a primary port, (B) a primary backup port and (C) a secondary backup port to use for forwarding.

2. The computer-implemented method of claim 1 wherein the pattern of the failure indicates that a second link failure does not affect a backup path used by a sub-graph 3 defined by a first link failure.

3. The computer-implemented method of claim 1 wherein the pattern of the failure indicates that a second link failure is on an exit link of a backup path used by a sub-graph defined by the first link failure.

4. The computer-implemented method of claim 3 wherein the pattern of the failure indicates that first and second link failures create two sub-graphs separated from a graph which includes the destination node, and wherein the two sub-graphs are separated from each other.

5. The computer-implemented method of claim 1 wherein a first link failure defines a graph including the destination node and a disconnected sub-graph, and wherein the pattern of the failure indicates that a second link failure creates a further sub-graph within the defined sub-graph.

6. For use by a router in a survivable network portion, apparatus comprising:

a) means for receiving a packet addressed to a destination node within the survivable network portion, wherein the packet includes an information indicating that the packet has encountered a failure; and

b) means for selecting one of (A) a primary port, (B) a primary backup port and (C) a secondary backup port on which to forward the received packet, such that in the event of a double link failure, a backup path with no dead loops is defined,

wherein the means for selecting one of (A) a primary port, (B) a primary backup port and (C) a secondary backup port for local rerouting include

1) means for identifying a pattern of the failure; and

2) means for selecting, using a forwarding policy associated with the identified pattern, one of (A) a primary port, (B) a primary backup port and (C) a secondary backup port to use for forwarding.

7. The apparatus of claim 6 wherein the pattern of the failure indicates that a second link failure does not affect a backup path used by a sub-graph defined by a first link failure.

8. The apparatus of claim 6 wherein the pattern of the failure indicates that a second link failure is on an exit link of a backup path used by a sub-graph defined by the first link failure.

9. The apparatus of claim 6 wherein the pattern of the failure indicates that first and second link failures create two sub-graphs separated from a graph which includes the destination node, and wherein the two sub-graphs are separated from each other.

10. The apparatus of claim 6 wherein a first link failure defines a graph including the destination node and a disconnected sub-graph, and wherein the pattern of the failure indicates that a second link failure creates a further sub-graph within the defined sub-graph.

Assignments (3)
MERGER Recorded Mar 25, 2026
From: POLYTECHNIC INSTITUTE OF NEW YORK UNIVERSITY
To: NEW YORK UNIVERSITY
Reel/Frame 074177/0601 →
CHANGE OF NAME Recorded Aug 11, 2010
From: POLYTECHNIC UNIVERSITY
To: POLYTECHNIC INSTITUTE OF NEW YORK UNIVERSITY
Reel/Frame 024821/0381 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 28, 2008
From: CHAO, HUNG-HSIANG JONATHAN; XI, KANG
To: POLYTECHNIC UNIVERSITY
Reel/Frame 020427/0719 →
Continuity (2)
Provisional Application 6085677000 · Nov 2, 2006
Related Publication 20080130489A1 · Jun 5, 2008