IP Library Granted Patent US 8,040,792
Granted Patent B2
US 8,040,792 · App. 11/833,168 · Granted Oct 18, 2011

Techniques for determining local repair connections

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 8,040,792
App. No.
11/833,168
Granted
Oct 18, 2011
Kind
B2
Abstract

Techniques for configuring a local repair connection for a protected connection including determining a path for the local repair connection. The path traversed by a local repair connection starts at a node in the path associated with the protected connection and ends at a merge point node in the path associated with the protected connection that is downstream from the start node. In one embodiment, the merge point node may even be more than two hops downstream from the start node in the path associated with the protected connection. The local repair path may include zero or more nodes that are not included in the path associated with the protected connection. Techniques are also described for optimizing the path associated with a local repair connection.

Claims (25)

1. A method of facilitating creation of a local repair connection for a first connection, the first connection traversing a first path comprising a plurality of nodes, the method comprising:

determining, by a network device, whether a second path can be established from a first node in the first path to a next-next-hop node to the first node in the first path, where the second path does not include a next-hop node to the first node in the first path and a next-hop link to the first node in the first path;

upon determining that the second path cannot be established, determining, by the network device, whether a third path can be established from the first node to the next-hop node to the first node in the first path, where the third path does not include the next-hop link to the first node in the first path; and

upon determining that the third path cannot be established, determining, by the network device, a fourth path from the first node to a second node in the first path, where the second node is downstream from the next-next-hop node to the first node in the first path,

wherein data is communicated via the first connection using Multi-Protocol Label Switching (MPLS) protocol and the first connection is a label switched path (LSP).

2. The method of claim 1 further comprising causing a second connection to be signaled for the fourth path, wherein the second connection is a local repair connection for the first connection and is usable for diverting data from the first path at the first node and merging the diverted data back to the first path at the second node.

3. The method of claim 1 wherein determining the fourth path comprises:

determining a fifth path from the first node in the first path to a third node in the first path, wherein the third node is upstream to the second node in the first path; and

determining the fourth path from the fifth path.

4. The method of claim 3 wherein determining the fourth path from the fifth path comprises determining the fourth path wherein the fifth path comprises at least one node that is not included in the fourth path.

5. The method of claim 3 wherein determining the fourth path from the fifth path comprises determining the fourth path such that a number of nodes from the first path that are in the fourth path is less than a number of nodes from the first path that are in the fifth path.

6. A system for facilitating creation of a local repair connection for a first connection, the first connection traversing a first path, the system comprising:

a memory configured to store information for the first connection; and

a processor configured to, based upon information stored in the memory:

determine whether a second path can be established from a first node in the first path to a next-next-hop node to the first node in the first path, where the second path does not include a next-hop node to the first node in the first path and a next-hop link to the first node in the first path;

upon determining that the second path cannot be established, determine whether a third path can be established from the first node to the next-hop node to the first node in the first path, where the third path does not include the next-hop link to the first node in the first path; and

upon determining that the third path cannot be established, determine a fourth path from the first node to a second node in the first path, where the second node is downstream from the next-next-hop node to the first node in the first path,

wherein data is communicated via the first connection using Multi-Protocol Label Switching (MPLS) protocol and the first connection is a label switched path (LSP).

7. The system of claim 6 wherein the processor is configured to cause a second connection to be signaled for the fourth path, wherein the second connection is a local repair connection for the first connection and is usable for diverting data from the first path at the first node and merging the diverted data back to the first path at the second node.

8. The system of claim 6 wherein the processor is configured to:

determine a fifth path from the first node in the first path to a third node in the first path, wherein the third node is upstream to the second node in the first path; and

determine the fourth path from the fifth path.

9. The system of claim 8 wherein the processor is configured to determine the fourth path wherein the fifth path comprises at least one node that is not included in the fourth path.

10. The system of claim 8 wherein the processor is configured to determine the fourth path such that a number of nodes from the first path that are in the fourth path is less than a number of nodes from the first path that are in the fifth path.

11. The system of claim 8 included in a switch.

Assignments (7)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 18, 2018
From: BROCADE COMMUNICATIONS SYSTEMS LLC
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047270/0247 →
RELEASE OF SECURITY INTEREST Recorded Jan 22, 2015
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC
Reel/Frame 034804/0793 →
RELEASE OF SECURITY INTEREST Recorded Jan 21, 2015
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: BROCADE COMMUNICATIONS SYSTEMS, INC.; INRANGE TECHNOLOGIES CORPORATION; FOUNDRY NETWORKS, LLC
Reel/Frame 034792/0540 →
CHANGE OF NAME Recorded Jul 21, 2010
From: FOUNDRY NETWORKS, INC.
To: FOUNDRY NETWORKS, LLC
Reel/Frame 024733/0739 →
SECURITY AGREEMENT Recorded Jan 20, 2010
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC; INRANGE TECHNOLOGIES CORPORATION; MCDATA CORPORATION; MCDATA SERVICES CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 023814/0587 →
SECURITY AGREEMENT Recorded Dec 22, 2008
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, INC.; INRANGE TECHNOLOGIES CORPORATION; MCDATA CORPORATION
To: BANK OF AMERICA, N.A. AS ADMINISTRATIVE AGENT
Reel/Frame 022012/0204 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2007
From: HANIF, MOHAMMAD; HSU, IVY
To: FOUNDRY NETWORKS, INC.
Reel/Frame 019641/0347 →