Localized network repair systems and methods
US-2016036520-A1 · Feb 4, 2016 · US
US2016119392A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016119392-A1 |
| Application number | US-201414585745-A |
| Country | US |
| Kind code | A1 |
| Filing date | Dec 30, 2014 |
| Priority date | Oct 27, 2014 |
| Publication date | Apr 28, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In one example, techniques of this disclosure may enable a point of local repair (PLR) network device to signal availability of link protection or node protection to a merge point (MP) network device and enable a network device to actively determine whether or not it is a merge point router. Based on whether or not the network device determines it is a MP, the network device may selectively clean up LSP states when there is an upstream link or node failure. The RSVP-TE protocol may be extended to enable a network device to send a tear down message to a downstream router, which may enable the downstream router to conditionally delete locale LSP state information. In some instances, a PLR network device may directly send a tear down message to a MP network device even though the PLR network device may not have a working bypass LSP.
Opening claim text (preview).
What is claimed is: 1 . A method comprising: receiving, by a network device and from an upstream network device, a resource reservation path message to establish a label switched path, wherein the upstream network device is positioned upstream from the network device along the label switched path; determining, by the network device, based on the resource reservation path message, whether the network device is a candidate merge point for the label switched path; determining, by the network device, whether there a remote hello session between the network device and the upstream device; and responsive to determining that the network device is a candidate merge point and determining that there is the remote hello session with the upstream device, determining, by the network device, that the network device is a merge point for the upstream device. 2 . The method of claim 1 , further comprising: responsive to determining that the first network device is not a candidate merge point or determining that there is no remote hello session with the upstream device, determining, by the first network device, that the first network device is a not merge point for the upstream device. 3 . The method of claim 1 , further comprising: responsive to determining that the first network device is a merge point, storing, by the first network device, remote state information for the label switched path. 4 . The method of claim 3 , wherein the remote state information includes a HOP object, and wherein the HOP object specifies an address of the upstream device. 5 . The method of claim 4 , wherein the upstream device is a previous previous hop of the network device. 6 . The method of claim 3 , further comprising: responsive to receiving, by the network device, from a point of local repair network device associated with the network device, a resource reservation path message specifying that at least one of node protection or link protection is not available, removing, by the network device, the remote state information for the label switched path. 7 . The method of claim 3 , further comprising: responsive to determining, by the network device, that there is a hello session with a point of local repair network device associated with the merge point is down, removing, by the network device, the remote state information for the label switched path. 8 . The method of claim 3 , further comprising: responsive to determining, by the network device, that an upstream network device is unavailable, determining whether a remote hello session with a point of local repair associated with the merge point is up; responsive to determining that the remote hello session is up, retaining, by the network device, the remote state information; and responsive to determining that the remote hello session is down, removing, by the network device, the remote state information. 9 . A network device comprising: one or more network interface cards; and a control unit configured to: receive, from an upstream network device and using at least one of the one or more network interface cards, a resource reservation path message to establish a label switched path, wherein the upstream network device is positioned upstream from the network device along the label switched path; determine, based on the resource reservation path message, whether the network device is a candidate merge point for the label switched path; determine whether there is a remote hello session between the network device and the upstream device; and responsive to determining that the network device is a candidate merge point and determining that there is the remote hello session with the upstream device, determine that the network device is a merge point for the upstream device. 10 . The network device of claim 9 , wherein the control unit is configured to, responsive to determining that the first network device is not a candidate merge point or determining that there is no remote hello session with the upstream device: determine that the first network device is a not merge point for the upstream device. 11 . The network device of claim 9 , wherein the control unit is configured to, responsive to determining that the first network device is a merge point, store remote state information for the label switched path. 12 . The network device of claim 11 , wherein the remote state information includes a HOP object, and wherein the HOP object specifies an address of the upstream device. 13 . The network device of claim 12 , wherein the upstream device is a previous previous hop of the network device. 14 . The network device of claim 11 , wherein the control unit is configured to, responsive to receiving, from a point of local repair network device associated with the network device, a resource reservation path message specifying that at least one of node protection or link protection is not available, remove the remote state information for the label switched path. 15 . The network device of claim 11 , wherein the control unit is configured to, responsive to determining that a hello session with a point of local repair network device associated with the merge point is down, remove the remote state information for the label switched path. 16 . The network device of claim 11 , wherein the control unit is configured to: responsive to determining that an upstream network device is unavailable, determine whether a remote hello session with a point of local repair associated with the merge point is up; responsive to determining that the remote hello session is up, retain the remote state information; and responsive to determining that the remote hello session is down, remove the remote state information. 17 . A non-transitory computer-readable storage medium encoded with instructions for causing one or more processors of a network device to: receive, from an upstream network device, a resource reservation path message to establish a label switched path, wherein the upstream network device is positioned upstream from the network device along the label switched path; determine, based on the resource reservation path message, whether the network device is a candidate merge point for the label switched path; determine whether there is a remote hello session between the network device and the upstream device; and responsive to determining that the network device is a candidate merge point and determining that there is the remote hello session with the upstream device, determine that the network device is a merge point for the upstream device. 18 . The non-transitory computer-readable storage medium of claim 17 further encoded with instructions for causing the one or more processors to: responsive to determining that the first network device is not a candidate merge point or determining that there is no remote hello session with the upstream device: determine that the first network device is a not merge point for the upstream device 19 . The non-transitory computer-readable storage medium of claim 17 further encoded with instructions for causing the one or more processors to: responsive to determining that the first network device is a merge point, store remote state information for the label switched path. 20 . The non-transitory computer-readable storage medium of claim 19 further encoded with instructions for causing the one or more processors to: responsive to determining that an upstream network device is unavailable, determine whether a remo
for backup paths · CPC title
Details of "hello" or keep-alive messages · CPC title
using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title
using route fault recovery · CPC title
Label distribution · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.